03-03-2003 10:19 AM - edited 03-12-2019 10:54 PM
I have a Unity 3.1(3) dual switch integration that has been functioning for a while - a power outage brought all the servers down and now Unity does not see the ports for the Call Manager.
It is a 16 port system - I have the registry keys for the dialogic so only 12 ports are being used for the analog. Unity did come up a long time before CallManager..... Only the 12 analog ports show up on the ports page and I am getting the following in the Event Viewer for each of the IP ports.
Event ID 109 - AvCiscoTSP_MC
AvCiscoTsp device XX: Device Registrations are Disabled - Unregistering with Callmanager
Any Ideas?
Solved! Go to Solution.
03-03-2003 10:34 AM
When Unity is starting up, you can expect to see that message per AvSkinny TSP port t. However, once the rest of Unity has started up, you should see another message stating that the ports have registered.
If Unity came up before CCM, then I would not expect you to have any AvSkinny ports working. At startup, if the ports attempt to register but fail because CCM is down, Unity will have to restart when CCM is up.
03-03-2003 10:34 AM
When Unity is starting up, you can expect to see that message per AvSkinny TSP port t. However, once the rest of Unity has started up, you should see another message stating that the ports have registered.
If Unity came up before CCM, then I would not expect you to have any AvSkinny ports working. At startup, if the ports attempt to register but fail because CCM is down, Unity will have to restart when CCM is up.
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