Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
466
Views
0
Helpful
1
Replies

CUCM 7.0 & Unity Connection 7.0 - no MWI

stephan.steiner
Spotlight
Spotlight

‎12-04-2008 07:38 AM - edited ‎03-18-2019 10:06 PM

I set up a Unity Connection 7.0 the other day using a SIP trunk. The SIP security profile allows unsolicited notifications and MWI is defined for the user that I'm using to make my tests - yet the MWI lamp never turns on (it's a 7975 phone in SCCP mode) when somebody leaves a message.

I turned on traces to see what is going on, and sure enough, Unity Connection (10.145.206.104) does send the number of new voicemail messages to the CUCM (10.145.206.102). Here's an extract from the traces:

12/02/2008 01:12:53.534 CCM|//SIP/SIPTcp/wait_SdlReadRsp: Incoming SIP TCP message from 10.145.206.104 on port 53183 index 8589 with 529 bytes:

NOTIFY sip:2001@10.145.206.102 SIP/2.0

From: sip:8000@10.145.206.104:5060;tag=45ca40bf8533472fbdd13b2485c9f85d

To: sip:2001@10.145.206.102

Via: SIP/2.0/TCP 10.145.206.104:5060;branch=z9hG4bK21b87057e2e748c09291c235274a70cf

Max-Forwards: 70

Contact: sip:8000@10.145.206.104:5060

Call-ID: 6954e28c3b8c4a2fbe8c59b26326d48b@10.145.206.102

CSeq: 300 NOTIFY

Event: message-summary

Content-Length: 73

Content-Type: application/simple-message-summary

Messages-Waiting: yes

Voice-Message: 1/0 (0/0)

Fax-Message: 0/0 (0/0)

|<CLID::StandAloneCluster><NID::10.145.206.102><CT::1,100,43,1.312><IP::10.145.206.104><DEV::><LVL::State Transition><MASK::20000>

12/02/2008 01:12:53.534 CCM|//SIP/SIPTcp/wait_SdlReadRsp: SignalCounter = 310|<CLID::StandAloneCluster><NID::10.145.206.102><CT::1,100,43,1.312><IP::10.145.206.104><DEV::><LVL::Detailed><MASK::20000>

12/02/2008 01:12:53.535 CCM|//SIP/SIPHandler/ccbId=0/scbId=4294967295/ccsip_platform_init_scb: scb mgmt added 0xe6a54b0|<CLID::StandAloneCluster><NID::10.145.206.102><CT::1,100,43,1.312><IP::10.145.206.104><DEV::><LVL::Detailed><MASK::20000>

12/02/2008 01:12:53.535 CCM|//SIP/SIPHandler/ccbId=0/scbId=4294967295/findDevicePID: Routed to SIPD|<CLID::StandAloneCluster><NID::10.145.206.102><CT::1,100,43,1.312><IP::10.145.206.104><DEV::><LVL::Detailed><MASK::20000>

12/02/2008 01:12:53.536 CCM|MessageWaitingManager - hashChildProcess - entries in the messageWaiting table = 0x1 |<CLID::StandAloneCluster><NID::10.145.206.102><CT::1,100,43,1.312><IP::10.145.206.104><DEV::><LVL::Detailed><MASK::0800>

12/02/2008 01:12:53.537 CCM|MessageWaiting::sendDaReq dialingPattern= dialingPartition= voiceMailbox= orig digitString=2001|<CLID::StandAloneCluster><NID::10.145.206.102><CT::1,100,43,1.312><IP::10.145.206.104><DEV::><LVL::Detailed><MASK::0800>

12/02/2008 01:12:53.538 CCM|MessageWaitingManager - deleteEntryFromMwiTable - entries in the messageWaiting table = 0x0 |<CLID::StandAloneCluster><NID::10.145.206.102><CT::1,100,43,1.312><IP::10.145.206.104><DEV::><LVL::Detailed><MASK::0800>

12/02/2008 01:12:53.539 CCM|DB: SQL1[execute procedure dblSetMWI('', 2)]|<CLID::StandAloneCluster><NID::10.145.206.102><LVL::Detailed><MASK::ffffff>

12/02/2008 01:12:53.548 CCM|//SIP/SIPTcp/wait_SdlSPISignal: received a spi signal ...|<CLID::StandAloneCluster><NID::10.145.206.102><CT::1,100,43,1.312><IP::10.145.206.104><DEV::><LVL::Detailed><MASK::20000>

12/02/2008 01:12:53.548 CCM|//SIP/SIPTcp/wait_SdlSPISignal: Outgoing SIP TCP message to 10.145.206.104 on port 53183 index 8589

SIP/2.0 200 OK

Date: Tue, 02 Dec 2008 00:12:53 GMT

From: sip:8000@10.145.206.104:5060;tag=45ca40bf8533472fbdd13b2485c9f85d

Content-Length: 0

To: sip:2001@10.145.206.102;tag=1555829057

Call-ID: 6954e28c3b8c4a2fbe8c59b26326d48b@10.145.206.102

Via: SIP/2.0/TCP 10.145.206.104:5060;branch=z9hG4bK21b87057e2e748c09291c235274a70cf

CSeq: 300 NOTIFY

As you can see, UCx reports one new message, yet the MWI lamp doesn't turn on. Even a phone reboot doesn't change that. Also in the Unity Connection interface (Users - Edit - Message Waiting Indication) it shows that MWI is on.

Labels:
0 Helpful
1 Reply 1

stephan.steiner
Spotlight
Spotlight

‎12-04-2008 07:39 AM

If the user calls the voicemail, he's told there's a new message. Upon having listened to the message, the MWI status changes to off in the Unity Connection interface, and I see the following in the traces (I know.. the traces are older than the MWI on... but this is simply from an earlier attempt)

12/02/2008 01:10:21.809 CCM|//SIP/SIPTcp/wait_SdlReadRsp: Incoming SIP TCP message from 10.145.206.104 on port 53183 index 8589 with 528 bytes:

NOTIFY sip:2001@10.145.206.102 SIP/2.0

From: sip:8000@10.145.206.104:5060;tag=6b1681bfb31942eaa5d80c3f6c93634b

To: sip:2001@10.145.206.102

Via: SIP/2.0/TCP 10.145.206.104:5060;branch=z9hG4bK091c0fcb9f984368986c7da620a9c2f6

Max-Forwards: 70

Contact: sip:8000@10.145.206.104:5060

Call-ID: ce9a1280aecd40569deab65cdac26e93@10.145.206.102

CSeq: 300 NOTIFY

Event: message-summary

Content-Length: 72

Content-Type: application/simple-message-summary

Messages-Waiting: no

Voice-Message: 0/0 (0/0)

Fax-Message: 0/0 (0/0)

|<:STANDALONECLUSTER><:10.145.206.102><:1><:10.145.206.104><:><:STATE transition=""><:20000>

12/02/2008 01:10:21.809 CCM|//SIP/SIPTcp/wait_SdlReadRsp: SignalCounter = 300|<:STANDALONECLUSTER><:10.145.206.102><:1><:10.145.206.104><:><:DETAILED><:20000>

12/02/2008 01:10:21.810 CCM|//SIP/SIPHandler/ccbId=0/scbId=4294967295/ccsip_platform_init_scb: scb mgmt added 0xe6a2b90|<:STANDALONECLUSTER><:10.145.206.102><:1><:10.145.206.104><:><:DETAILED><:20000>

12/02/2008 01:10:21.810 CCM|//SIP/SIPHandler/ccbId=0/scbId=4294967295/findDevicePID: Routed to SIPD|<:STANDALONECLUSTER><:10.145.206.102><:1><:10.145.206.104><:><:DETAILED><:20000>

12/02/2008 01:10:21.811 CCM|MessageWaitingManager - hashChildProcess - entries in the messageWaiting table = 0x1 |<:STANDALONECLUSTER><:10.145.206.102><:1><:10.145.206.104><:><:DETAILED><:0800>

12/02/2008 01:10:21.811 CCM|MessageWaiting::sendDaReq dialingPattern= dialingPartition= voiceMailbox= orig digitString=2001|<:STANDALONECLUSTER><:10.145.206.102><:1><:10.145.206.104><:><:DETAILED><:0800>

12/02/2008 01:10:21.811 CCM|MessageWaitingManager - deleteEntryFromMwiTable - entries in the messageWaiting table = 0x0 |<:STANDALONECLUSTER><:10.145.206.102><:1><:10.145.206.104><:><:DETAILED><:0800>

12/02/2008 01:10:21.811 CCM|DB: SQL1[execute procedure dblSetMWI('', 1)]|<:STANDALONECLUSTER><:10.145.206.102><:DETAILED><:FFFFFF>

12/02/2008 01:10:21.812 CCM|//SIP/SIPTcp/wait_SdlSPISignal: received a spi signal ...|<:STANDALONECLUSTER><:10.145.206.102><:1><:10.145.206.104><:><:DETAILED><:20000>

12/02/2008 01:10:21.813 CCM|//SIP/SIPHandler/ccbId=0/scbId=0/wait_SIPSubTerminated: inDialogSubReferCounter=0 scbid=8761|<:STANDALONECLUSTER><:10.145.206.102><:1><:10.145.206.104><:><:DETA>

As far as the SIP messages are concerned I think we're good and there are no errors to be seen so I don't understand why MWI isn't being turned on.

Does anybody have an idea about what is going wrong here?

P.S. The extension of the user is 2001. 2002 is the extension of the user leaving the voicemail message.

0 Helpful
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Customers Also Viewed These Support Documents