09-19-2002 01:26 PM - edited 03-12-2019 08:52 PM
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.
Any ideas ?
09-19-2002 07:20 PM
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).
adam
09-20-2002 05:59 AM
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.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide