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

UC540 Message Waiting Indicator Not Working with Software Pack 8.2.0

I have a UC540 that I have recently upgraded to software pack 8.2.0.  I amhaving problems with the message waiting indicator not coming ON when a new message is received.  I seems to be happening with all the phones at this time.  I configured the system with CCA 3.1.1 and am not aware if it ever worked on this system.  The message is in the mailbox but I am not getting an indication of the new message.

The configuration is as follows:

ephone-dn  299

number A801... no-reg primary

mwi off

!

!

ephone-dn  300

number A800... no-reg primary

mwi on

In CUE:

ccn application ciscomwiapplication aa

description "ciscomwiapplication"

enabled

maxsessions 6

script "setmwi.aef"

parameter "CallControlGroupID" "0"

parameter "strMWI_OFF_DN" "A801"

parameter "strMWI_ON_DN" "A800"

end application

What else do I need to check?  How can I test this?

14 REPLIES
Cisco Employee

UC540 Message Waiting Indicator Not Working with Software Pack 8

Hi there,

Upload the show run from UC540 and from CUE and I'll look at it.

Thanks,

Luis Ramirez.

Community Member

Re: UC540 Message Waiting Indicator Not Working with Software Pa

Attached

Cisco Employee

Re: UC540 Message Waiting Indicator Not Working with Software Pa

Hi,

Configuration looks good.

I think the CUE is generating the call to turn MWI on but there is no dial-peer able to receive it and that is what is causing the issue.

The only way to confirm that would be getting debugs but lets try first to force the call to match the desired incoming dial-peer.

Try this.

dial-peer voice 2000 voip

incoming called number A80....

end

Please rate this post if it was helpful.

Thanks,

Luis Ramirez

Community Member

Re: UC540 Message Waiting Indicator Not Working with Software Pa

Sorry, that did not fix it.  Here is what I put in:

dial-peer voice 2001 voip

incoming called-number A80....

If I test the pattern:

rec_calgary#sh dialplan number A801601
Macro Exp.: A801601

VoiceEncapPeer20003
        peer type = voice, system default peer = FALSE, information type = voice,
        description = `',
        tag = 20003, destination-pattern = `A801...',
        voice reg type = 0, corresponding tag = 0,
        allow watch = FALSE
        answer-address = `', preference=0,
        CLID Restriction = None
        CLID Network Number = `'
        CLID Second Number sent
        CLID Override RDNIS = disabled,
        rtp-ssrc mux = system
        source carrier-id = `', target carrier-id = `',
        source trunk-group-label = `',  target trunk-group-label = `',
        numbering Type = `unknown'
        group = 20003, Admin state is up, Operation state is up,
        incoming called-number = `', connections/maximum = 0/unlimited,
        DTMF Relay = disabled,
        URI classes:
            Destination =
        huntstop = enabled,
        in bound application associated: 'DEFAULT'
        out bound application associated: ''
        dnis-map =
        permission :both
        incoming COR list:maximum capability
        outgoing COR list:minimum requirement
        Translation profile (Incoming):
        Translation profile (Outgoing):
        incoming call blocking:
        translation-profile = `'
        disconnect-cause = `no-service'
        advertise 0x40 capacity_update_timer 25 addrFamily 0 oldAddrFamily 0
        mailbox selection policy: none
        type = pots, prefix = `',
        forward-digits 0
        session-target = `', voice-port = `50/0/299',
        direct-inward-dial = disabled,
        digit_strip = enabled,
        register E.164 number with H323 GK and/or SIP Registrar = FALSE
        fax rate = system,   payload size =  20 bytes
        supported-language = ''
        preemption level = `routine'
        bandwidth:
            maximum = 64 KBits/sec, minimum = 64 KBits/sec
        voice class called-number:
            inbound = `', outbound = `'
        dial tone generation after remote onhook = enabled
        mobility=0, snr=, snr_noan=, snr_delay=0, snr_timeout=0
        Time elapsed since last clearing of voice call statistics never
        Connect Time = 0, Charged Units = 0,
        Successful Calls = 1, Failed Calls = 0, Incomplete Calls = 0
        Accepted Calls = 0, Refused Calls = 0,
        Last Disconnect Cause is "10  ",
        Last Disconnect Text is "normal call clearing (16)",
        Last Setup Time = 243754.
        Last Disconnect Time = 0.
Matched: A801601   Digits: 4
Target:

Here is a ccsip debug when I leave a message for x605

008018: Nov  8 18:20:10.330: //60/20BDD7D480B0/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:699@10.6.0.1:5060 SIP/2.0
Via: SIP/2.0/UDP 10.6.0.2:5060;branch=z9hG4bK222317
Remote-Party-ID: "Name" <604>;party=calling;screen=no;privacy=off
From: "Name" <604>;tag=1474CB54-25BA
To: <699>
Date: Tue, 08 Nov 2011 18:20:10 GMT
Call-ID: 20BE73FC-96D11E1-80B4B214-AEA71E37@10.6.0.2
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE:  1800
Cisco-Guid: 0549312468-0158142945-2159063572-2930187831
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Max-Forwards: 70
Timestamp: 1320776410
Contact: <604>
Diversion: <605>;privacy=off;reason=no-answer;counter=1;screen=no
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 235

v=0
o=CiscoSystemsSIP-GW-UserAgent 4068 1902 IN IP4 10.6.0.2
s=SIP Call
c=IN IP4 10.6.0.2
t=0 0
m=audio 18678 RTP/AVP 0 101
c=IN IP4 10.6.0.2
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20

008019: Nov  8 18:20:10.338: //60/20BDD7D480B0/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.6.0.2:5060;branch=z9hG4bK222317
To: <699>
From: "Name" <604>;tag=1474CB54-25BA
Call-ID: 20BE73FC-96D11E1-80B4B214-AEA71E37@10.6.0.2
CSeq: 101 INVITE
Content-Length: 0
Timestamp: 1320776410


008020: Nov  8 18:20:10.402: //60/20BDD7D480B0/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 10.6.0.2:5060;branch=z9hG4bK222317
To: <699>;tag=dsb5462a6d
From: "Name" <604>;tag=1474CB54-25BA
Call-ID: 20BE73FC-96D11E1-80B4B214-AEA71E37@10.6.0.2
CSeq: 101 INVITE
Content-Length: 0
Contact: <699>
Allow: INVITE, BYE, CANCEL, ACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO
Cisco-Gcid: 20BE73FC-96D11E1-80B4B214-AEA71E37@10.6.0.2


008021: Nov  8 18:20:10.474: //60/20BDD7D480B0/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 Ok
Via: SIP/2.0/UDP 10.6.0.2:5060;branch=z9hG4bK222317
To: <699>;tag=dsb5462a6d
From: "Name" <604>;tag=1474CB54-25BA
Call-ID: 20BE73FC-96D11E1-80B4B214-AEA71E37@10.6.0.2
CSeq: 101 INVITE
Content-Length: 181
Contact: <699>
Content-Type: application/sdp
Allow: INVITE, BYE, CANCEL, ACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO
Cisco-Gcid: 20BE73FC-96D11E1-80B4B214-AEA71E37@10.6.0.2

v=0
o=CUE 6857881 2 IN IP4 10.6.0.1
s=SIP Call
c=IN IP4 10.6.0.1
t=0 0
m=audio 21044 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15


008022: Nov  8 18:20:10.494: //60/20BDD7D480B0/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:699@10.6.0.1:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 10.6.0.2:5060;branch=z9hG4bK23491
From: "Name" <604>;tag=1474CB54-25BA
To: <699>;tag=dsb5462a6d
Date: Tue, 08 Nov 2011 18:20:10 GMT
Call-ID: 20BE73FC-96D11E1-80B4B214-AEA71E37@10.6.0.2
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Content-Length: 0


008023: Nov  8 18:20:16.242: //60/20BDD7D480B0/SIP/Msg/ccsipDisplayMsg:
Sent:
BYE sip:699@10.6.0.1:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 10.6.0.2:5060;branch=z9hG4bK241F08
From: "Name" <604>;tag=1474CB54-25BA
To: <699>;tag=dsb5462a6d
Date: Tue, 08 Nov 2011 18:20:10 GMT
Call-ID: 20BE73FC-96D11E1-80B4B214-AEA71E37@10.6.0.2
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1320776416
CSeq: 102 BYE
Reason: Q.850;cause=16
Content-Length: 0


008024: Nov  8 18:20:16.254: //60/20BDD7D480B0/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 Ok
Via: SIP/2.0/UDP 10.6.0.2:5060;branch=z9hG4bK241F08
To: <699>;tag=dsb5462a6d
From: "Name" <604>;tag=1474CB54-25BA
Call-ID: 20BE73FC-96D11E1-80B4B214-AEA71E37@10.6.0.2
CSeq: 102 BYE
Content-Length: 0

Cisco Employee

Re: UC540 Message Waiting Indicator Not Working with Software Pa

Is that all you got from debug CCSIP messages?

I don't see the CUE sending the call for MWI.

try this on CUE.

ccn subsystem sip

mwi sip outcall

exit

Try getting the debugs ccsip again but don't leave the voice mail.

Do a "mwi refresh all" on CUE so it sends the calls for MWI to CME foe the voicemails that are already in CUE.

Thanks,

Luis Ramirez.

Community Member

Re: UC540 Message Waiting Indicator Not Working with Software Pa

"mwi refresh all" did not make any difference.

Can't do a "ccn subsystem sip"

se-10-6-0-1# ccn ?

  call              Active call related information

  copy              Copy data from one location to another

  delete            Remove data

  rename            Rename a local data file

  reporting         historical Reporting

  trace             Trace

se-10-6-0-1# ccn

Here is debug when I do NOT leave a message.  I let it go to VM, but disconnected when I heard the prompt.

rec_calgary#
008084: Nov  8 18:55:57.742: //71/20B2FDCD80D3/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:699@10.6.0.1:5060 SIP/2.0
Via: SIP/2.0/UDP 10.6.0.2:5060;branch=z9hG4bK2B24F1
Remote-Party-ID: "Name" <604>;party=calling;screen=no;privacy=off
From: "Name" <604>;tag=14958F64-22E8
To: <699>
Date: Tue, 08 Nov 2011 18:55:57 GMT
Call-ID: 20B399F5-97211E1-80D7B214-AEA71E37@10.6.0.2
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE:  1800
Cisco-Guid: 0548601293-0158470625-2161357332-2930187831
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Max-Forwards: 70
Timestamp: 1320778557
Contact: <604>
Diversion: <605>;privacy=off;reason=no-answer;counter=1;screen=no
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 233

v=0
o=CiscoSystemsSIP-GW-UserAgent 880 334 IN IP4 10.6.0.2
s=SIP Call
c=IN IP4 10.6.0.2
t=0 0
m=audio 17872 RTP/AVP 0 101
c=IN IP4 10.6.0.2
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20

008085: Nov  8 18:55:58.242: //71/20B2FDCD80D3/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:699@10.6.0.1:5060 SIP/2.0
Via: SIP/2.0/UDP 10.6.0.2:5060;branch=z9hG4bK2B24F1
Remote-Party-ID: "Name" <604>;party=calling;screen=no;privacy=off
From: "Name" <604>;tag=14958F64-22E8
To: <699>
Date: Tue, 08 Nov 2011 18:55:58 GMT
Call-ID: 20B399F5-97211E1-80D7B214-AEA71E37@10.6.0.2
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE:  1800
Cisco-Guid: 0548601293-0158470625-2161357332-2930187831
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Max-Forwards: 70
Timestamp: 1320778558
Contact: <604>
Diversion: <605>;privacy=off;reason=no-answer;counter=1;screen=no
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 233

v=0
o=CiscoSystemsSIP-GW-UserAgent 880 334 IN IP4 10.6.0.2
s=SIP Call
c=IN IP4 10.6.0.2
t=0 0
m=audio 17872 RTP/AVP 0 101
c=IN IP4 10.6.0.2
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20

008086: Nov  8 18:55:58.686: //71/20B2FDCD80D3/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.6.0.2:5060;branch=z9hG4bK2B24F1
To: <699>
From: "Marlene Rodriguez" <604>;tag=14958F64-22E8
Call-ID: 20B399F5-97211E1-80D7B214-AEA71E37@10.6.0.2
CSeq: 101 INVITE
Content-Length: 0
Timestamp: 1320778557


008087: Nov  8 18:55:58.710: //71/20B2FDCD80D3/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.6.0.2:5060;branch=z9hG4bK2B24F1
To: <699>
From: "Name" <604>;tag=14958F64-22E8
Call-ID: 20B399F5-97211E1-80D7B214-AEA71E37@10.6.0.2
CSeq: 101 INVITE
Content-Length: 0
Timestamp: 1320778557


008088: Nov  8 18:55:58.742: //71/20B2FDCD80D3/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 10.6.0.2:5060;branch=z9hG4bK2B24F1
To: <699>;tag=ds2cb4f267
From: "Name" <604>;tag=14958F64-22E8
Call-ID: 20B399F5-97211E1-80D7B214-AEA71E37@10.6.0.2
CSeq: 101 INVITE
Content-Length: 0
Contact: <699>
Allow: INVITE, BYE, CANCEL, ACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO
Cisco-Gcid: 20B399F5-97211E1-80D7B214-AEA71E37@10.6.0.2


008089: Nov  8 18:55:58.814: //71/20B2FDCD80D3/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 Ok
Via: SIP/2.0/UDP 10.6.0.2:5060;branch=z9hG4bK2B24F1
To: <699>;tag=ds2cb4f267
From: "Name" <604>;tag=14958F64-22E8
Call-ID: 20B399F5-97211E1-80D7B214-AEA71E37@10.6.0.2
CSeq: 101 INVITE
Content-Length: 181
Contact: <699>
Content-Type: application/sdp
Allow: INVITE, BYE, CANCEL, ACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO
Cisco-Gcid: 20B399F5-97211E1-80D7B214-AEA71E37@10.6.0.2

v=0
o=CUE 9006201 2 IN IP4 10.6.0.1
s=SIP Call
c=IN IP4 10.6.0.1
t=0 0
m=audio 20894 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15


008090: Nov  8 18:55:58.834: //71/20B2FDCD80D3/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:699@10.6.0.1:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 10.6.0.2:5060;branch=z9hG4bK2C7D8
From: "Name" <604>;tag=14958F64-22E8
To: <699>;tag=ds2cb4f267
Date: Tue, 08 Nov 2011 18:55:58 GMT
Call-ID: 20B399F5-97211E1-80D7B214-AEA71E37@10.6.0.2
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Content-Length: 0


008091: Nov  8 18:56:02.971: //71/20B2FDCD80D3/SIP/Msg/ccsipDisplayMsg:
Sent:
BYE sip:699@10.6.0.1:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 10.6.0.2:5060;branch=z9hG4bK2D1812
From: "Name" <604>;tag=14958F64-22E8
To: <699>;tag=ds2cb4f267
Date: Tue, 08 Nov 2011 18:55:58 GMT
Call-ID: 20B399F5-97211E1-80D7B214-AEA71E37@10.6.0.2
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1320778562
CSeq: 102 BYE
Reason: Q.850;cause=16
Content-Length: 0


008092: Nov  8 18:56:02.979: //71/20B2FDCD80D3/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 Ok
Via: SIP/2.0/UDP 10.6.0.2:5060;branch=z9hG4bK2D1812
To: <699>;tag=ds2cb4f267
From: "Name" <604>;tag=14958F64-22E8
Call-ID: 20B399F5-97211E1-80D7B214-AEA71E37@10.6.0.2
CSeq: 102 BYE
Content-Length: 0

Cisco Employee

Re: UC540 Message Waiting Indicator Not Working with Software Pa

The CCn subsystem Sip is in config mode.

don't call voicemail, just enable the debugs and run the command "MWI refresh all" in CUE.

Also get this show command fom CUE.

show voicemail maboxes

Thanks,

Luis Ramirez,

Community Member

Re: UC540 Message Waiting Indicator Not Working with Software Pa

Sorry.  Here it is.

No difference with the:

ccn subsystem sip

mwi sip outcall

exit

rec_calgary#sh debug
CCSIP SPI: SIP Call Message tracing is enabled  (filter is OFF)

rec_calgary#ser int 0/0 sess
Trying 10.6.0.2, 2002 ... Open
banner login ^Cisco Configuration Assistant. Version: 3.1 (1). Fri Nov 04 13:23:02 MDT 2011^

se-10-6-0-1#
se-10-6-0-1#
se-10-6-0-1#
se-10-6-0-1# mwi ref
se-10-6-0-1# mwi refresh all
se-10-6-0-1# sh voicem ma
se-10-6-0-1# sh voicem mailboxes
OWNER               MSGS NEW SAVE DEL BCST FUTR FAX MSGTIME   MBXSIZE  USED
"TPhone"            5    5   0    0   0    0    0   18        720      3 %
"xmmm"              0    0   0    0   0    0    0   0         720      0 %
"xm.1"              0    0   0    0   0    0    0   0         720      0 %
"xm.a"              0    0   0    0   0    0    0   0         720      0 %
"xm.d"              0    0   0    0   0    0    0   0         720      0 %
"xm.g"              0    0   0    0   0    0    0   0         720      0 %
se-10-6-0-1#

Cisco Employee

Re: UC540 Message Waiting Indicator Not Working with Software Pa

That confirms that the CUE is not generating the MWI call.

Configuration on CUE looks fine since the application and the trigger are enabled and and have max sessions.

You might try doing this on CUE.

conf t

ccn trigger http urlname mwiapp

maxsessions 6

exit

Then reload the CUE to see if that makes any difference.

If that does not work, you'll need to capture some CUE traces by doing this in CUE.

no trace all

clear trace

trace voicemail all

After that, try leaving a call and then in order to get the traces do this.

show trace buffer tail.

Hope this helps.

Thanks,

Luis Ramirez,

Community Member

Re: UC540 Message Waiting Indicator Not Working with Software Pa

Did this:


ccn trigger http urlname mwiapp
application "ciscomwiapplication"
enabled
maxsessions 6
end trigger

I then reloaded.  No difference.  Here is the trace.

se-10-6-0-1# no trace all

se-10-6-0-1#

se-10-6-0-1# clear trace

se-10-6-0-1# show trace buff tail

Press to exit...

se-10-6-0-1#

se-10-6-0-1#

se-10-6-0-1#

se-10-6-0-1#

se-10-6-0-1#

se-10-6-0-1#

se-10-6-0-1#

se-10-6-0-1# trace voicemail all

se-10-6-0-1# show trace buff tail

Press to exit...

3443 11/08 14:12:20.347 voicemail debug "dbg" com.cisco.aesop.voicemail.Mailbox : No session 8000000015 to logout

se-10-6-0-1#

Cisco Employee

Re: UC540 Message Waiting Indicator Not Working with Software Pa

try again with the show trace buffer tail.

It takes a while come up.

Thanks,

Luis Ramirez.

Community Member

Re: UC540 Message Waiting Indicator Not Working with Software Pa

Trace uploaded.

Cisco Employee

Re: UC540 Message Waiting Indicator Not Working with Software Pa

Seems like it is actually trying it but you have your ccn subsystem sip pointing to 10.1.10.2.

Change that to the real gateway.

conf t

ccnsubsystem sip

gateway address 10.6.0.2

exit

After that, try again that should help.

Please rate this post if it was helpful.

Thanks,

Luis Ramirez

Community Member

Re: UC540 Message Waiting Indicator Not Working with Software Pa

Sorry for the delay.  I have entered:

ccn subsystem sip

gateway address "10.6.0.2"

dtmf-relay rtp-nte

end subsystem

Still having the same problem though.

1313
Views
0
Helpful
14
Replies
CreatePlease to create content