I have got Unity 4.02 TSP 7.02. Dual integration with NEC pbx and 3.3CCM. Dialgic board D/240PCI T1. I have used lower/upper bound in the registry to use 3 ports in the V-card. I have 21 soft ports with CCM. I am licenced for 32 ports in Unity. The problem is that on the softports I go only up to 8. In other words since Unity is licenced for 32 ports it thinks I have 24 port Dialogic and 8 port with CCM. I have defined all the ports correctly in CCM/TSP and UNITY. Each port is answering correctly indivitually. I have feeling that the lower bound /higher bound statements in the registry will tell the Dialogic driver to use only 3 ports...Cisco TSP does not know anything about that or somwhere around that line. In event viewer I have got warnings that port 47 does not answer. That is why I am thinking 24V-port + 21 soft ports...In reality there are only 32 ports. Any ideas...
Well, something is definitely out of whack if UTIM has 3 ports for your Dialogic integration and 21 ports for your IP integration but is somehow getting 3 + 21 = 32 ports in use.
Without a closer look at the system I won't venture any guesses. Everything *should* be handled by UTIM without any tricks. I've set this up on my test system without a problem. Those registry settings you added were only needed in 3.x. I would suggest having TAC take a stab at it.
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...
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 discusses the bas...