Okay I have a scenerio where I am transitioning a site from an old TDM phone system to cisco.
DN's are 8 digit where the first 4 represent the site code.
Lets say the old legacy system is 1111xxxx and the new is 2222xxxx, intrasite dialing is 4 digit.
The problem is the execs that have been transitioned to the new system are not happy with dialing 8 digits to get folks on the legacy system. So the 4 digit translation on the cisco says [1-6]xxx and then prefixes with 2222
I have put a [1-6]xxx with a 1111 prefix in a lower partition in the calling search space in hopes that the cisco will look for say extension 2222-1000 in its local partition but if it doesnt find it then it changes it to 1111-1000 and sends it to the older system. Thus allowing 4 digit dialing between systems.
problem is that it doesnt work. It always matches the first translation and then waves off when that DN doesnt exist and never goes to the alternate match.....How do I make it hit that second match?
(a lot of hoops to jump through for 4 digits, I know)
You need to break which extensions are on which system and build specific translations/route patterns. If you want the Cisco to be default (you need to pick default side) you can use the [1-6]xxx for that, but to reach the extensions on legacy side you will need more explicit matches. No way around it.
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.