Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Unity Reorder Tones

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

Date: 8/19/2003

Time: 3:15:59 PM

User: N/A

Computer: UNITY

Description:

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.

Any thoughts/ideas would be greatly appreciated.

TMH

4 REPLIES
New Member

Re: Unity Reorder Tones

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.

adam

New Member

Re: Unity Reorder Tones

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):

08/20/2003 11:36:34.238 CCM|CTI: RoutePatternToCtiCallOrigin::store() : RP=6701:, bRc=1, CallOrigin=7, T=restart0_StationStimTransfer(), #entries=1|<:NTHSCM-CLUSTER><:192.168.234.12>

08/20/2003 11:36:34.253 CCM|CTI: RoutePatternToCtiGlobalCallID::findValue(): RP=6701:, bRc=0, T=, #entries=0|<:NTHSCM-CLUSTER><:192.168.234.12>

08/20/2003 11:36:34.253 CCM|CTI: RoutePatternToCtiCallOrigin::findValue() : RP=6701:, bRc=1, CallOrigin=7, T=, #entries=1|<:NTHSCM-CLUSTER><:192.168.234.12>

08/20/2003 11:36:34.253 CCM|CTI: RoutePatternToCtiCallOrigin::remove() : RP=6701:; bRc=1, T=await_ci_res_CcCiRes(), #entries=0|<:NTHSCM-CLUSTER><:192.168.234.12>

08/20/2003 11:36:34.269 CCM|CTI: RoutePatternToCtiCommandData::findValue() : RP=6701:, bRc=0, T=, #entries=0|<:NTHSCM-CLUSTER><:192.168.234.12>

08/20/2003 11:36:34.269 CCM|CTI: RoutePatternToCtiCommandData::findValue() : RP=6701:, bRc=0, T=, #entries=0|<:NTHSCM-CLUSTER><:192.168.234.12>

08/20/2003 11:36:37.753 CCM|CTI: RoutePatternToCtiCallOrigin::store() : RP=6701:, bRc=1, CallOrigin=7, T=restart0_StationStimTransfer(), #entries=1|<:NTHSCM-CLUSTER><:192.168.234.12>

08/20/2003 11:36:37.769 CCM|CTI: RoutePatternToCtiGlobalCallID::findValue(): RP=6701:, bRc=0, T=, #entries=0|<:NTHSCM-CLUSTER><:192.168.234.12>

08/20/2003 11:36:37.769 CCM|CTI: RoutePatternToCtiCallOrigin::findValue() : RP=6701:, bRc=1, CallOrigin=7, T=, #entries=1|<:NTHSCM-CLUSTER><:192.168.234.12>

08/20/2003 11:36:37.769 CCM|CTI: RoutePatternToCtiCallOrigin::remove() : RP=6701:; bRc=1, T=await_ci_res_CcCiRes(), #entries=0|<:NTHSCM-CLUSTER><:192.168.234.12>

08/20/2003 11:36:38.738 CCM|CTI: RoutePatternToCtiCommandData::findValue() : RP=6701:, bRc=0, T=, #entries=0|<:NTHSCM-CLUSTER><:192.168.234.12>

08/20/2003 11:36:38.972 CCM|CTI: RoutePatternToCtiCallOrigin::store() : RP=6701:, bRc=1, CallOrigin=7, T=restart0_StationStimTransfer(), #entries=1|<:NTHSCM-CLUSTER><:192.168.234.12>

08/20/2003 11:36:38.988 CCM|CTI: RoutePatternToCtiCallOrigin::remove() : RP=6701:; bRc=1, T=restart0_LmKeyReleaseReq(), #entries=0|<:NTHSCM-CLUSTER><:192.168.234.12>

TMH

New Member

Re: Unity Reorder Tones

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.

adam

New Member

Re: Unity Reorder Tones

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.

Thanks for all of your help...

TMH

119
Views
0
Helpful
4
Replies