We've got a Call-manager/Unity installation that needs to send/receive messages from an Octel system. We're trying to get AMIS to work, but when the Octel system sends the C tone, the Unity system never responds with the D tone. Any idea why this would be??<br><br>
We have a 2610 running 12.2.5a with a 5ESS PRI connected to our Siemens PBX which is, in turn, connected to the Octel VMX. Calls through this gateway work fine. The gateway is configured as an H.323 gateway, not MGCP.
Also, I can call the Octel's Amis port from the IP Phones and get the C Tone. We've also tapped into the call on the analog side and hear Unity answer (with the standard greeting), hear the Octel send the C tone, but never hear the Unity server send the D tone.
I'm not exactly sure if the StatusMonitor.exe will show AMIS activity, but I think it might. Try opening the StatusMonitor.exe and watching the activity. If the SA ports page has AMIS enabled for the port, it should work. If that doesn't work, you might want to get a TAC case opened so we can get tracing of the call.
I worked on a nasty AMIS case where it turned out to be an issue with the IOS. 12.1.3a-XI6 ended up being the code that we recommended for use with AMIS. If the Unity is getting the C tone we need to make sure that it is transmitting and D tone. We should look in the CCM trace to see if the Unity TSP is transmitting a D tone before pointing at the gateway. Can you rip open a CCM trace and tell me if you see this? You can search throught the trace for 'KeypadButton kpButton=D'.
Keith Chambers Unity Technical Lead Unified Voice Team, San Jose Cisco Systems email@example.com
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.