Unity 3.1.5, Exchange 2000 off-box, dual integration with SMDI and CCM 3.3(2) spC, TSP 6.0.2b.
We just upgraded from CCM 3.1.4(b) to 3.3(2) spC, and Unity has been acting fine except for these messages, which occur frequently when Unity is under a heavy load:
Event Type: Warning
Event Source: AvCiscoTsp_MC
Event Category: None
Event ID: 111
Time: 3:15:59 PM
The description for Event ID ( 111 ) in Source ( AvCiscoTsp_MC ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: 28, RELEASE, Reorder.
I'm not quite sure what this is indicating - is Unity sending the reorder or receiving it? I've looked in the trace logs for the skinnyTSP, and I'm seeing where the messages come up, but there's nothing jumping out at me as to why they're happening. Maybe a TSP upgrade is needed? I'm not getting complaints from people (yet), but this didn't happen with our older version of CCM.
Unity can't "send" reorder. The PBX/CallManager will instruct Unity to play reorder. Did you copy this event log message directly off of the Unity server? The unity skinny traces will never tell you why you're receiving reorder. Have you checked the CCM traces? Make sure the extension that Unity is trying to call exists, and that Unity's calling search space includes the partition that extension is in.
Yes, the error message is copied directly off of the Unity server. I've checked the CSS on the VM ports, and all is correct. Here's what the CCM trace shows at the exact moment that the error message pops up on Unity (6701 is the DN for our first VM port):
I'm not exactly sure what's going on in this trace. Is this taken from the callmanager that Unity is registered to when the error occurs? What is the tracing level set to? It should be set to Detailed. Are the clocks on the Unity and CallManager servers synced up? Otherwise you could be copying in something from before or after the real incident occurred. Email me the entire trace file along with calling/called numbers, and I can tell you for certain what's going on.
I found out what was going on...someone had set a pager message notification device, and the only characters set on it were ".,"; every time it tried to dial a comma and a period, Unity would receive a reorder (duh). I found it by running dbWalker on Unity, corrected the problem, and haven't had the error message since.
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...