Extension mobility with same DN for different profiles
I would like to implement for an airport the extension mobility to manage shared counters (equipped with 7911 IP Phones on Airport Cisco cluster) used by different airlines compagnies. The airlines compagnies have their own telephone system (Cisco, Nortel, centrex, etc...) on the site for their admin phones to be integrated (trunk) with the counters (airport cluster).
I would like to keep the same DN (Ex: 6121 for counter #121 and 6223 for counter #223) in the logged-out AND logged-in mode.
In the logged-out mode, we are in the airport "dial plan", internal, 911 and local calls permitted.
In the logged-in mode, I want to keep the same DN but with the profile of the airline compagnies, with CSS and Partition specific to the compagny to be able when they push 9 to reach their telephone system or a shared PRI (for the small compagnies) for long distance. The airport will use Avotus to rebill the compagny for the long distance if they use the shared PRI based on the partition (because they use the same DN and Phone).
So, the same DN (Ex: 6121) will always be used at the counter #121, always the same IP Phone at the same location but with a different profile per compagny for different gateway access and call accounting.
I ask for any feedback if you think we can have issues or if this scenario is or not supported.
Re: Extension mobility with same DN for different profiles
You should be able to do this, create your seperate profiles with the same DNs but different parition, then each profile should use a different CSS at the DN level with access to route patterns specific to their environemtn.
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.