ā07-10-2012 06:43 AM - edited ā03-16-2019 12:06 PM
MWI on phones not turning ON when leaving voice message on CUE. I have gone through ccsip messages and found below output, can someone please advise what its pointing to
009987: Jul 9 10:00:18.059: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:58505491@10.121.183.5:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 10.113.18.54:5060;branch=z9hG4bKGKFjxXd4Tsz1pGsqi4V0Cw~~142
Max-Forwards: 70
To: <sip:58505491@10.121.183.5:5060>
From: <sip:4000@10.113.18.54>;tag=ds72954331
Call-ID: 1341841987058118@10.113.18.54
CSeq: 100 INVITE
Content-Length: 130
Contact: <sip:4000@10.113.18.54:5060;transport=udp>
Content-Type: application/sdp
Call-Info: <sip:10.113.18.54:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"
Allow-Events: telephone-event
Allow: INVITE, BYE, CANCEL, ACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO
Cisco-Gcid: 6C03D5F2-0138-1000-6C82-5112931DF39B
v=0
o=CUE 251380 2 IN IP4 10.113.18.54
s=SIP Call
c=IN IP4 10.113.18.54
t=0 0
m=audio 32988 RTP/AVP 0
a=rtpmap:0 PCMU/8000
009988: Jul 9 10:00:18.063: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 488 Not Acceptable Media <<<<<<<<<<<<<<
Via: SIP/2.0/UDP 10.113.18.54:5060;branch=z9hG4bKGKFjxXd4Tsz1pGsqi4V0Cw~~142
From: <sip:4000@10.113.18.54>;tag=ds72954331
To: <sip:58505491@10.121.183.5:5060>;tag=799B30A8-2E7
Date: Mon, 09 Jul 2012 14:00:18 GMT
Call-ID: 1341841987058118@10.113.18.54
CSeq: 100 INVITE
Allow-Events: telephone-event
Warning: 304 10.113.18.53 "Media Type(s) Unavailable" <<<<<<<<<<<<<<
Reason: Q.850;cause=65
Server: Cisco-SIPGateway/IOS-12.x
Content-Length: 0
009989: Jul 9 10:00:18.063: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:58505491@10.121.183.5:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 10.113.18.54:5060;branch=z9hG4bKGKFjxXd4Tsz1pGsqi4V0Cw~~142
Max-Forwards: 70
To: <sip:58505491@10.121.183.5:5060>;tag=799B30A8-2E7
From: <sip:4000@10.113.18.54>;tag=ds72954331
Call-ID: 1341841987058118@10.113.18.54
CSeq: 100 ACK
Content-Length: 0
009990: Jul 9 10:00:20.367: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
BYE sip:5491@10.113.18.53:5060 SIP/2.0
Via: SIP/2.0/UDP 10.113.18.54:5060;branch=z9hG4bKGKFjxXd4Tsz1pGsqi4V0Cw~~143
Max-Forwards: 70
To: <sip:5491@10.113.18.53>;tag=799B0C14-24E8
From: <sip:4000@10.113.18.54>;tag=ds4ca61eac
Call-ID: 3A3D5813-C90511E1-B0A7BF5C-92935187@10.113.18.53
CSeq: 2 BYE
Content-Length: 0
Allow: INVITE, BYE, CANCEL, ACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO
Cisco-Gcid: 3A3D5813-C90511E1-B0A7BF5C-92935187@10.113.18.53
Solved! Go to Solution.
ā07-10-2012 06:52 AM
What is your topology? CME/CUE Integration. You are getting SIP/2.0 488 Not Acceptable Media which generally means a codec Mismatch...
This output indicates that Cisco CallManager Express rejected the call because the SIP
INVITE
message from Cisco Unity Express did not match a dial peer that G.711 configured. You can add a dial peer specifically for the MWI traffic in order to correct this call rejection.
Also take a look at this post.. Could help you in locating the problem..
ā07-10-2012 06:52 AM
What is your topology? CME/CUE Integration. You are getting SIP/2.0 488 Not Acceptable Media which generally means a codec Mismatch...
This output indicates that Cisco CallManager Express rejected the call because the SIP
INVITE
message from Cisco Unity Express did not match a dial peer that G.711 configured. You can add a dial peer specifically for the MWI traffic in order to correct this call rejection.
Also take a look at this post.. Could help you in locating the problem..
ā07-12-2012 10:25 AM
Thanks kelvin, its fixed by adding dialpeer.....
ā07-10-2012 07:45 PM
Try to logon to CUE Gui and under Voicemail, there is a message waiting indicator make sure that the unsollicited notify is check and on the cme make sure the sip ua looks like this X= CUE ip address
mwi-server ipv4:X.X.X.X expires 86400 port 5060 transport tcp unsolicited
ā07-12-2012 10:26 AM
thanks, we already have this in the config but issue was dialpeer for incoming call codec mismatch.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide