Remote destination profile for Mobility connection
In Remote destination profile for mobility connection we have [ Ingone presentation indicator ( internal calls only ) ], even when check or un-check the box I am not able to find any difference in connected line ID, please let me know what is the use of this "Ingone presentation indicator ( internal calls only )" in Remote Destination Profile.
Re: Remote destination profile for Mobility connection
First, from the remote destination profile "help for this page"
Check the check box if you want to ignore the connected line ID presentation. Use this configuration for internal calls.
Second, From the Help for this page of a route pattern:
Connected Line ID Presentation
Cisco Unified Communications Manager uses connected line ID presentation (COLP/COLR) as a supplementary service to allow or restrict the called party phone number on a call-by-call basis.
Choose whether you want Cisco Unified Communications Manager to allow or restrict the display of the connected party phone number on the calling party phone display for this route pattern.
Choose Default if you do not want to change the connected line ID presentation. Choose Allowed if you want to display the connected party phone number. Choose Restricted if you want Cisco Unified Communications Manager to block the display of the connected party phone number.
This setting impacts the calling phone not the destination phone. This is used mainly for PLAR or translation situations where you don't want an internal caller to know the final DN of a call - like in a hotel perhaps.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.