Here's the situation I'm about to run into...<br><br>I'm running Call Manager 220.127.116.11 (Bravo EFT) with Unity 2.4.5. I have currently have all of my corporate office in production on unity (about 400 phones), and I'm about to roll it out to all of my remote sites (about 1200 phones in 25 locations) all of these remote sites use overlapping extensions (i.e. customer service at every site is ext. 101). I need a way to differentiate between sites without going away from a 3-digit extension. I noticed in Bravo that there is a field that you can set on each line of the phone to tell the VM system if the box for that phone differs from the phone extension; however, upon testing it in a lab scenario it failed to produce the results I was looking for. When I pulled up port monitor on Unity all Unity saw was a call coming in from ext. 101. What I'm trying to do is setup all mailboxes as the fully qualified DID of the phone it belongs to. (i.e. ext. 101's mailbox would be npa-nxx-x101 as setup in Unity instead of just 101). I can make it so that when you dial the voicemail system from the phone the route pattern sends with it the DID of the phone so that when you hit your messages button you get through fine. But when a call is forwarded on a no-answer timeout Unity sees it as just the ext and not the DID.<br><br>Any suggestions would be much appreciated.<br><br>Jeremy<br><br><br>
Unity 2.4.5 with Bravo is not even close to a supported configuration. I am not sure which TSP version you have running on the Unity server, but I thought that the latest released version was 18.104.22.168. It surprises me that TSP 22.214.171.124 can even register with a Bravo CCM (unless 126.96.36.199 will acccept the registration, earlier Bravo versions won't).
Unity 2.4.5 or even 2.4.6 is not going to be able to handle multiple boxes for the same extension. True, in Bravo there is the "voice mail number" field that can be applied if the voice mail ID differs from the phone DN, but TSP 188.8.131.52 logic isn't going to look there.
From what you are describing, it sounds like this is a totally unsupported configuration. What is the version of TSP?
You are correct it is unsupported, which is why I'm looking for all the help I can get here. My EFT agreement doesn't provide any support beyond the realm of Call Manager. I'm using TSP 184.108.40.206 and have no problems regestering with Bravo.
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.