I just completed an installation of 3.1(4) W/cm 3.2 . I have a 16 port Unity and the second port is busy. You can dial each port directly but the second port is busy. I have tried deleting the port out of CM and recreating it still no go.
Regular busy or fast busy? If you look at the port on Call Manager, does it show registered? If you go into performance monitor on Call Manager and pull up the Cisco Lines performance object, do you see the second port's extension in there? Does it show up like "Rem-7002" where 7002 is the extension?
What do you see on the ports page in the System Manager on the Unity server? What do you see in the app even log when the box boots up or when a call comes in on that port? You should look for the AvCiscoTsp warnings and messages referring to device 6 (port 2).
I solved the problem. What got me thinking is I deleted all voicemail ports. Then when you dial 9000 which is the pilot you would get a busy signal which you should. But when you dialed 9001 the port giving me proglems you would get a busy signal but, you still got the description Voicemail . Rebooted the call manager add the voicemail ports back now everything is happy.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
[toc:faq]CUCM Database Replication is an area in which Cisco customers
and partners have asked for more in-depth training in being able to
properly assess a replication problem and potentially resolve an issue
without involving TAC. This document discusse...