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

CM Centralized, MWI issues at remote site

I have CM cluster 3.1(3a)SP 'C' running with a single Unity 2.4.6(161) TSP 6.0.1.<br><br>There are issues with remote office MWI lamps. They work intermittantly across the frame relay network. Frame traffic on the link is nominal. The Unity server does not appear to send MWI for a normal voicemail, although when I use status monitor to send one I can see it going out.<br><br>The users do have the 'Message Waiting Indicators' turned on for their subscriber accounts.<br><br>What other information do you need from me? Any immediate ideas?<br><br>Matt Slaga <img src="/images/icons/wink.gif"><br>Dimension Data US<br><font color=red>MCNE</font color=red>, <font color=blue>MCSE2k</font color=blue>, <font color=purple>CCIE #8629 Unity Systems Engineer</font color=purple>

6 REPLIES
Gold

Re: CM Centralized, MWI issues at remote site

When Unity lights MWI it goes off hook *AS* the line that it is lighting MWI for. CallManager then tells the line to turn its lamp on and records the lamp state in SQL. The fact that the phone happens to be connect for a frame link doesn't really make a difference. Even if you were to move that phone over to the main site it would still have the same issue.

Can you post a CCM trace of Unity lighting the MWI for this phone?

Keith

Keith Chambers
Unity Technical Lead
Unified Voice Team, San Jose
Cisco Systems

New Member

Re: CM Centralized, MWI issues at remote site

Exactly which trace field should I check to capture only MWI information?

Matt Slaga
Dimension Data US
MCNE, MCSE2k, CCIE #8629 Unity Systems Engineer

Gold

Re: CM Centralized, MWI issues at remote site

You will need to run the CCM trace:
http://www.cisco.com/warp/public/788/AVVID/cm_trace.html

You can check 'Device Name Based Trace Monitoring' and then chose 'Cisco Voice Mail Port' and your ports to limit the trace down.

Keith

Keith Chambers
Unity Technical Lead
Unified Voice Team, San Jose
Cisco Systems

New Member

Re: CM Centralized, MWI issues at remote site

I ran the trace, and I get the following lamp on entries:

03/29/2002 16:59:40.710 Cisco CallManager|StationD: 6876e04 SetLamp stimulus=9(Line) stimulusInstance=1 lampMode=2(LampOn).CLID::SS-DUR-CM01-Cluster-NID::10.1.24.12-T::1,100,95,1.447167-IP::10.1.24.15-DEV::Unity-VI15

03/29/2002 16:59:47.991 Cisco CallManager-StationD - StationOutputSetLamp ignored-LID::SS-DUR-CM01-Cluster-NID::10.1.24.12-CT::1,100,95,1.447261-IP::10.1.24.15-DEV::Unity-VI15

This Unity system is running in a very busy production environment, so I am not sure which lamp on signals are for the test phones I set. There does not appear to be any designator in these traces for what phone is being affected.
I had to edit these trace entries (remove the greater than/less than signs) in order for them to appear above completely.

In your previous message, you said that being in a remote site should not affect a user's MWI setting. I fully agree with your thinking, but I am also seeing that phones in a remote site are having MWI issues whereas local phones are not.

Matt Slaga
Dimension Data US
MCNE, MCSE2k, CCIE #8629 Unity Systems Engineer

Gold

Re: CM Centralized, MWI issues at remote site

The trace that we are looking for is going to be far more verbose that what you posted. When I get back in the office I will post a trace of Unity lighting a lamp to show you what it looks like.

Keith

Keith Chambers
Unity Technical Lead
Unified Voice Team, San Jose
Cisco Systems

Gold

Re: CM Centralized, MWI issues at remote site

Some basics:
CallManager uses the SCCP (Skinny Client Control Protocol) to communicate with Unity and IP phones. To the CallManager Unity is just another IP phone. The SCCP protocol is a master slave protocol meaning that CallManager controls the end point.

The SCCP protocol allows Unity to spoof the DN for the phone it is lighting the lamp for. Basically the Unity goes off hook as the phone and dials the on or off DN that is configured in CallManager. CallManager then tells the DN to light its lamp.

In the trace:
StationD: = Message from CallManager to the device.
StationInit: = Message from the device to the CallManager.
Digit analysis: = This is call route lookup engine of CallManager.

Every StationD and StationInit is followed by a TCP handle. (i.e. StationD: 71224d9). The TCP hanle represents the device.

The TCP handle for my Unity port is this trace is 70124d0 and the DN is 2001. The TCP handle for my phone is 70122dc and the DN is 8000. My MWI on DN is 8998.

On to the trace...



04/04/2002 16:45:01.900 Cisco CallManager|StationD: 70124d0 SetLamp stimulus=9(Line) stimulusInstance=1 lampMode=2(LampOn).|<:7830-1-CLUSTER><:172.16.16.9><:1><:172.16.16.151><:A-U-CLTS-VI2>
The phone (Unity port) went off hook and CallManager told it to turn its lamp on. Unity doesn’t have a lamp so it just ignores that message. Remember that CallManager thinks Unity is a phone.
04/04/2002 16:45:01.910 Cisco CallManager|StationInit: 70124d0 KeypadButton kpButton=8.|<:7830-1-CLUSTER><:172.16.16.9><:1><:172.16.16.151><:A-U-CLTS-VI2>
Unity dials 8.
04/04/2002 16:45:01.910 Cisco CallManager|StationInit: 70124d0 KeypadButton kpButton=9.|<:7830-1-CLUSTER><:172.16.16.9><:1><:172.16.16.151><:A-U-CLTS-VI2>
Unity dials 9.
04/04/2002 16:45:01.910 Cisco CallManager|StationInit: 70124d0 KeypadButton kpButton=9.|<:7830-1-CLUSTER><:172.16.16.9><:1><:172.16.16.151><:A-U-CLTS-VI2>
Unity dials 9.
04/04/2002 16:45:01.910 Cisco CallManager|StationInit: 70124d0 KeypadButton kpButton=8.|<:7830-1-CLUSTER><:172.16.16.9><:1><:172.16.16.151><:A-U-CLTS-VI2>
Unity dials 8.
04/04/2002 16:45:01.910 Cisco CallManager|StationD: 70124d0 CallState callState=1 lineInstance=1 callReference=16777648|<:7830-1-CLUSTER><:172.16.16.9><:1><:172.16.16.151><:A-U-CLTS-VI2>
04/04/2002 16:45:01.910 Cisco CallManager|StationD: 70124d0 DisplayPromptStatus timeOutValue=0 promptStatus='Enter Number' content='Enter Number' lineInstance=1 callReference=16777648 ver=0.|<:7830-1-CLUSTER><:172.16.16.9><:1><:172.16.16.151><:A-U-CLTS-VI2>
04/04/2002 16:45:01.910 Cisco CallManager|StationD: 70124d0 SelectSoftKeys instance=1 reference=16777648 softKeySetIndex=4 validKeyMask=-1.|<:7830-1-CLUSTER><:172.16.16.9><:1><:172.16.16.151><:A-U-CLTS-VI2>
04/04/2002 16:45:01.910 Cisco CallManager|StationD: 70124d0 ActivateCallPlane lineInstance=1.|<:7830-1-CLUSTER><:172.16.16.9><:1><:172.16.16.151><:A-U-CLTS-VI2>
04/04/2002 16:45:01.910 Cisco CallManager|Insert an entry into CiCcp table, now this table has 1 entries|<:7830-1-CLUSTER><:172.16.16.9><:1><:172.16.16.151><:A-U-CLTS-VI2>
04/04/2002 16:45:01.910 Cisco CallManager|Insert an entry into CiCcp table, now this table has 2 entries|<:7830-1-CLUSTER><:172.16.16.9><:1><:172.16.16.151><:A-U-CLTS-VI2>
04/04/2002 16:45:01.910 Cisco CallManager|Digit analysis: match(fqcn="2001", cn="8000", pss="", dd="")|<:7830-1-CLUSTER><:172.16.16.9><:1><:172.16.16.151><:A-U-CLTS-VI2>
Unity did this dialing much fast than a person ever could and now CallManager is catching up with digit analysis. First CallManager does digit analysis on 'null'...
04/04/2002 16:45:01.910 Cisco CallManager|Digit analysis: potentialMatches=PotentialMatchesExist|<:7830-1-CLUSTER><:172.16.16.9><:1><:172.16.16.151><:A-U-CLTS-VI2>
Which returns 'PotentialMatchesExist' so digit analysis waits for the next digit.
04/04/2002 16:45:01.920 Cisco CallManager|StationD: 70124d0 StartTone tone=33(InsideDialTone), direction=0.|<:7830-1-CLUSTER><:172.16.16.9><:1><:172.16.16.151><:A-U-CLTS-VI2>
CallManager tells the phone (Unity) to play dial tone. Unity doesn't need dial tone and takes no action on this message.
04/04/2002 16:45:01.920 Cisco CallManager|StationD: 70124d0 StopTone.|<:7830-1-CLUSTER><:172.16.16.9><:1><:172.16.16.151><:A-U-CLTS-VI2>
Here CallManager tells the phone (Unity) to stop playing dial tone because a digit has been dialed. Once again Unity does all of the dialing much faster than any person can so CallManager needs to catch up a bit.
04/04/2002 16:45:01.920 Cisco CallManager|StationD: 70124d0 SelectSoftKeys instance=1 reference=16777648 softKeySetIndex=6 validKeyMask=-1.|<:7830-1-CLUSTER><:172.16.16.9><:1><:172.16.16.151><:A-U-CLTS-VI2>
04/04/2002 16:45:01.920 Cisco CallManager|Digit analysis: match(fqcn="2001", cn="8000", pss="", dd="8")|<:7830-1-CLUSTER><:172.16.16.9><:1><:172.16.16.151><:A-U-CLTS-VI2>
CallManager does digit analysis on the dialed number 8... Note (fqcn="2001", cn="8000", pss="", dd="8"). SCCP allows Unity to spoof its calling number. Unity spoofs the DN it is lighting the lamp for.
04/04/2002 16:45:01.920 Cisco CallManager|Digit analysis: potentialMatches=PotentialMatchesExist|<:7830-1-CLUSTER><:172.16.16.9><:1><:172.16.16.151><:A-U-CLTS-VI2>
Which returns 'PotentialMatchesExist' so digit analysis waits for the next digit.
04/04/2002 16:45:01.920 Cisco CallManager|Digit analysis: match(fqcn="2001", cn="8000", pss="", dd="89")|<:7830-1-CLUSTER><:172.16.16.9><:1><:172.16.16.151><:A-U-CLTS-VI2>
CallManager does digit analysis on the dialed number 9...
04/04/2002 16:45:01.920 Cisco CallManager|Digit analysis: potentialMatches=PotentialMatchesExist|<:7830-1-CLUSTER><:172.16.16.9><:1><:172.16.16.151><:A-U-CLTS-VI2>
Which returns 'PotentialMatchesExist' so digit analysis waits for the next digit.
04/04/2002 16:45:01.930 Cisco CallManager|Digit analysis: match(fqcn="2001", cn="8000", pss="", dd="899")|<:7830-1-CLUSTER><:172.16.16.9><:1><:172.16.16.151><:A-U-CLTS-VI2>
CallManager does digit analysis on the dialed number 9...
04/04/2002 16:45:01.930 Cisco CallManager|Digit analysis: potentialMatches=PotentialMatchesExist|<:7830-1-CLUSTER><:172.16.16.9><:1><:172.16.16.151><:A-U-CLTS-VI2>
Which returns 'PotentialMatchesExist' so digit analysis waits for the next digit.
04/04/2002 16:45:01.930 Cisco CallManager|Digit analysis: match(fqcn="2001", cn="8000", pss="", dd="8998")|<:7830-1-CLUSTER><:172.16.16.9><:1><:172.16.16.151><:A-U-CLTS-VI2>
CallManager does digit analysis on the dialed number 8...
04/04/2002 16:45:01.930 Cisco CallManager|Digit analysis: analysis results|<:7830-1-CLUSTER><:172.16.16.9><:1><:172.16.16.151><:A-U-CLTS-VI2>
And finds a match.
04/04/2002 16:45:01.930 Cisco CallManager||PretransformCallingPartyNumber=8000
Notice it chooses to route the call (in this case MWI on code) to the DN 8000 which is my phone.
|CallingPartyNumber=8000
|DialingPartition=
|DialingPattern=
|DialingRoutePatternRegularExpression=
|DialingWhere=
|PatternType=Unknown
|PotentialMatches=NoPotentialMatchesExist
|DialingSdlProcessId=(0,0,0)
|PretransformDigitString=8998
|PretransformTagsList=
|PretransformPositionalMatchList=
|CollectedDigits=
|UnconsumedDigits=
|TagsList=
|PositionalMatchList=
|VoiceMailbox=
|VoiceMailCallingSearchSpace=
|VoiceMailPilotNumber=
|DisplayName=
|RouteBlockFlag=BlockThisPattern
|InterceptPartition=
|InterceptPattern=8998
|InterceptWhere=
|InterceptSdlProcessId=(1,50,1)
|InterceptSsType=16777225
|InterceptSsKey=6966|<:7830-1-CLUSTER><:172.16.16.9><:1><:172.16.16.151><:A-U-CLTS-VI2>
04/04/2002 16:45:01.930 Cisco CallManager|Insert an entry into MonitorPartyTable, now this table has 1 entries|<:7830-1-CLUSTER><:172.16.16.9><:1><:172.16.16.151><:A-U-CLTS-VI2>
04/04/2002 16:45:01.930 Cisco CallManager|Insert an entry into TransTable, now this table has 1 entries|<:7830-1-CLUSTER><:172.16.16.9><:1><:172.16.16.151><:A-U-CLTS-VI2>
04/04/2002 16:45:01.930 Cisco CallManager|Delete entries from TransTable, now this table has 0 entries|<:7830-1-CLUSTER><:172.16.16.9><:1><:172.16.16.151><:A-U-CLTS-VI2>
04/04/2002 16:45:01.930 Cisco CallManager|MessageWaitingManager - findInterceptTableEntry - Found Intercept table entry for dn= 8998, InterceptKey= 0x1B36 |<:7830-1-CLUSTER><:172.16.16.9><:1><:172.16.16.151><:A-U-CLTS-VI2>
04/04/2002 16:45:01.930 Cisco CallManager|Insert an entry into TransTable, now this table has 1 entries|<:7830-1-CLUSTER><:172.16.16.9><:1><:><:>
04/04/2002 16:45:01.930 Cisco CallManager|StationD: 70124d0 CallState callState=12 lineInstance=1 callReference=16777648|<:7830-1-CLUSTER><:172.16.16.9><:1><:172.16.16.151><:A-U-CLTS-VI2>
04/04/2002 16:45:01.930 Cisco CallManager|StationD: 70124d0 CallInfo callingPartyName='A-U-CLTS' callingParty=2001 cgpnVoiceMailbox= calledPartyName='' calledParty=8998 cdpnVoiceMailbox= originalCalledPartyName='' originalCalledParty=8998 originalCdpnVoiceMailbox= originalCdpnRedirectReason=0 lastRedirectingPartyName='' lastRedirectingParty= lastRedirectingVoiceMailbox= lastRedirectingReason=0 callType=2(OutBound) lineInstance=1 callReference=16777648. version: 0|<:7830-1-CLUSTER><:172.16.16.9><:1><:172.16.16.151><:A-U-CLTS-VI2>
04/04/2002 16:45:01.930 Cisco CallManager|StationD::star_StationOutputCallInfo(): callInfo: CI=16777648, CallingPartyName=A-U-CLTS, CallingParty=2001, CalledPartyName=, CalledParty=8998, OriginalCalledPartyName=, OriginalCalledParty=8998, lastRedirectingPartyName=, lastRedirectingParty=|<:7830-1-CLUSTER><:172.16.16.9><:1><:172.16.16.151><:A-U-CLTS-VI2>
04/04/2002 16:45:01.930 Cisco CallManager|StationD: 70124d0 DialedNumber dialedNumber=8998 lineInstance=1 callReference=16777648.|<:7830-1-CLUSTER><:172.16.16.9><:1><:172.16.16.151><:A-U-CLTS-VI2>
04/04/2002 16:45:01.930 Cisco CallManager|Delete entries from TransTable, now this table has 0 entries|<:7830-1-CLUSTER><:172.16.16.9><:1><:><:>
04/04/2002 16:45:01.940 Cisco CallManager|MessageWaiting - getting_call_info_SsCallInfoRes - MessageWaitingLamp for Dn= 8000 Turned ON|<:7830-1-CLUSTER><:172.16.16.9><:1><:><:>
04/04/2002 16:45:01.950 Cisco CallManager|<:7830-1-CLUSTER><:172.16.16.9><:1><:DIRECTORY number=""><:8000><:>
04/04/2002 16:45:01.950 Cisco CallManager|StationD: 70122dc SetLamp stimulus=15(VoiceMail) stimulusInstance=1 lampMode=2(LampOn).|<:7830-1-CLUSTER><:172.16.16.9><:1><:><:>
CallManager tells the phone (DN 8000) to turn on the lamp
04/04/2002 16:45:01.950 Cisco CallManager|StationD: 70122dc SetLamp stimulus=15(VoiceMail) stimulusInstance=0 lampMode=2(LampOn).|<:7830-1-CLUSTER><:172.16.16.9><:1><:><:>
CallManager tells the phone (DN 8000) to turn on the LCD
04/04/2002 16:45:01.950 Cisco CallManager|StationD: 70122dc DisplayPromptStatus timeOutValue=0 promptStatus='€$' content='You have a voice mail' lineInstance=0 callReference=0 ver=3.|<:7830-1-CLUSTER><:172.16.16.9><:1><:><:>
CallManager tells the phone (DN 8000) to display the message 'You have a voice mail'
04/04/2002 16:45:01.950 Cisco CallManager|<:7830-1-CLUSTER><:172.16.16.9><:1><:DIRECTORY number=""><:2001><:>
04/04/2002 16:45:01.950 Cisco CallManager|CTI: RoutePatternToCtiCommandData::findValue() : RP=2001:, bRc=0, T=, #entries=0|<:7830-1-CLUSTER><:172.16.16.9>
04/04/2002 16:45:01.950 Cisco CallManager|CTI: RoutePatternToCtiCommandData::findValue() : RP=2001:, bRc=0, T=, #entries=0|<:7830-1-CLUSTER><:172.16.16.9>
04/04/2002 16:45:01.970 Cisco CallManager|StationD: 70124d0 SetSpeakerMode speakermode=2(Off).|<:7830-1-CLUSTER><:172.16.16.9><:1><:><:>
04/04/2002 16:45:01.970 Cisco CallManager|StationD: 70124d0 ClearPromptStatus lineInstance=1 callReference=16777648.|<:7830-1-CLUSTER><:172.16.16.9><:1><:><:>
04/04/2002 16:45:01.970 Cisco CallManager|StationD: 70124d0 CallState callState=2 lineInstance=1 callReference=16777648|<:7830-1-CLUSTER><:172.16.16.9><:1><:><:>
04/04/2002 16:45:01.970 Cisco CallManager|StationD: 70124d0 SelectSoftKeys instance=0 reference=0 softKeySetIndex=0 validKeyMask=7.|<:7830-1-CLUSTER><:172.16.16.9><:1><:><:>
04/04/2002 16:45:01.970 Cisco CallManager|StationD: 70124d0 DisplayPromptStatus timeOutValue=0 promptStatus='Your current options' content='Your current options' lineInstance=0 callReference=0 ver=0.|<:7830-1-CLUSTER><:172.16.16.9><:1><:><:>
04/04/2002 16:45:01.970 Cisco CallManager|StationD: 70124d0 ActivateCallPlane lineInstance=0.|<:7830-1-CLUSTER><:172.16.16.9><:1><:><:>
04/04/2002 16:45:01.980 Cisco CallManager|StationD: 70124d0 SetLamp stimulus=9(Line) stimulusInstance=1 lampMode=1(LampOff).|<:7830-1-CLUSTER><:172.16.16.9><:1><:><:>
04/04/2002 16:45:01.980 Cisco CallManager|StationD: 70124d0 DefineTimeDate timeDateInfo=? systemTime=1017956701.|<:7830-1-CLUSTER><:172.16.16.9><:1><:><:>
04/04/2002 16:45:01.980 Cisco CallManager|StationD: 70124d0 StopTone.|<:7830-1-CLUSTER><:172.16.16.9><:1><:><:>

Does that explain it?

Keith Chambers
Unity Technical Lead
Unified Voice Team, San Jose
Cisco Systems

140
Views
0
Helpful
6
Replies