UC520 MWI Failure

Answered Question
Apr 30th, 2010

Hi Netpro,

Voice messages can be correctly left in the voice mailbox, but MWI cannot reach phones. I have tried all three ways of delivering MWI with no success.

CME is SIP trunking to a SIP proxy server for PSTN calls. This part is working fine.

From CUE debugs, I can see the CUE is sending the MWI SIP messages to the CME; but no debug messages appear in CME (with 'debug ccsip all' and 'debug voice dialpeer all'). So the WMI does not reach CME.

Is this a bug? Any ideas?


=====================================cme config
IOS=====uc500-advipservicesk9-mz.124-11.XW6


interface Loopback0
ip address 10.1.10.2 255.255.255.252
ip virtual-reassembly
!
interface Integrated-Service-Engine0/0
ip unnumbered Loopback0
ip virtual-reassembly
service-module ip address 10.1.10.1 255.255.255.252
service-module ip default-gateway 10.1.10.2
!
dial-peer voice 2000 voip
description ** cue voicemail pilot number **
answer-address 1099
destination-pattern 1099
b2bua
session protocol sipv2
session target ipv4:10.1.10.1
incoming called-number 88[89]....
dtmf-relay sip-notify
codec g711ulaw
no vad
!
ephone-dn  159
number 888....
mwi off
!
!
ephone-dn  160
number 889....
mwi on
!

=======================================================================cue config

UC500-CUE# sh software ver

Installed Packages:

Software Version: 3.0.3


UC500-CUE# sh ccn su sip
SIP Gateway:                            10.1.10.2
SIP Port Number:                        5060
DTMF Relay:                             sip-notify,sub-notify
MWI Notification:                       outcall
Transfer Mode:                          bye-also
SIP RFC Compliance:                     Pre-RFC3261

---------------------------------------------

UC500-CUE# sh ccn  app

Name:                                   ciscomwiapplication
Description:                            ciscomwiapplication
Application type:                       aa
Script:                                 setmwi.aef
ID number:                              0
Enabled:                                yes
Maximum number of sessions:             6
CallControlGroupID:                     0
strMWI_OFF_DN:                          888
strMWI_ON_DN:                           889

---------------------------------------------------
UC500-CUE# no trace all
UC500-CUE# trace ccn StackSip DBUG
UC500-CUE# clear tra
UC500-CUE# mwi refresh telephonenumber 1400
UC500-CUE# sh trace buff lo
Press <CTRL-C> to exit...
3395 05/01 15:47:11.309 ACCN SIPL 0 sip-ltp7: 1099, State=CONTACTINGenter connect
3395 05/01 15:47:11.309 ACCN SIPL 0 sip-ltp7: 1099, State=CONTACTINGenter createInvitation
3395 05/01 15:47:11.309 ACCN SIPL 0 SDPBody : v=0
o=CiscoSystemsSIP-Workflow-App-UserAgent 2253 2253 IN IP4 10.1.10.1
s=SIP Call
c=IN IP4 10.1.10.1
t=0 0
m=audio 16908 RTP/AVP 0
a=rtpmap:0 pcmu/8000
a=ptime:20

3395 05/01 15:47:11.311 ACCN SIPL 0 sip-ltp7: 1099, State=CONTACTINGbefore invitationmanager.createInvitation. body : v=0
o=CiscoSystemsSIP-Workflow-App-UserAgent 2253 2253 IN IP4 10.1.10.1
s=SIP Call
c=IN IP4 10.1.10.1
t=0 0
m=audio 16908 RTP/AVP 0
a=rtpmap:0 pcmu/8000
a=ptime:20
body type : application/sdp toNA : <sip:[email protected]:5060;user=phone> fromNA : <sip:[email protected]:5060> from tag : cuef594fbb8
3395 05/01 15:47:11.311 ACCN SIPL 0 sip-ltp7: 1099, State=CONTACTINGafter invitationmanager.createInvitation
3395 05/01 15:47:11.312 ACCN SIPL 0 sip-ltp7: 1099, State=CONTACTING added ciscogcid
3395 05/01 15:47:11.312 ACCN SIPL 0 sip-ltp7: 1099, State=CONTACTING getDTMFHeader: Enter
3395 05/01 15:47:11.312 ACCN SIPL 0 sip-ltp7: 1099, State=CONTACTING getDTMFHeader: getting the headers
3395 05/01 15:47:11.312 ACCN SIPL 0 sip-ltp7: 1099, State=CONTACTING getDTMFHeader: before adding headers to message
3395 05/01 15:47:11.313 ACCN SIPL 0 sip-ltp7: 1099, State=CONTACTING getDTMFHeader: after adding headers to message :
INVITE sip:[email protected]:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP 10.1.10.1:5060;branch=z9hG4bKooUjPgeVHhJTOspwHd2EGA~~8
Max-Forwards: 70
To: <sip:[email protected]:5060;user=phone>
From: <sip:[email protected]:5060>;tag=cuef594fbb8
Call-ID: [email protected]
CSeq: 1 INVITE
Content-Length: 172
Contact: <sip:[email protected]:5060>
Content-Type: application/sdp
Cisco-Gcid: 51C2A8CB-0128-1000-4000-001125CUCE68
Call-Info: <sip:10.1.10.1:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"
Allow-Events: telephone-event

v=0
o=CiscoSystemsSIP-Workflow-App-UserAgent 2253 2253 IN IP4 10.1.10.1
s=SIP Call
c=IN IP4 10.1.10.1
t=0 0
m=audio 16908 RTP/AVP 0
a=rtpmap:0 pcmu/8000
a=ptime:20

3395 05/01 15:47:11.314 ACCN SIPL 0 sip-ltp7: 1099, State=CONTACTINGinvite message : INVITE sip:[email protected]:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP 10.1.10.1:5060;branch=z9hG4bKooUjPgeVHhJTOspwHd2EGA~~8
Max-Forwards: 70
To: <sip:[email protected]:5060;user=phone>
From: <sip:[email protected]:5060>;tag=cuef594fbb8
Call-ID: [email protected]
CSeq: 1 INVITE
Content-Length: 172
Contact: <sip:[email protected]:5060>
Content-Type: application/sdp
Cisco-Gcid: 51C2A8CB-0128-1000-4000-001125CUCE68
Call-Info: <sip:10.1.10.1:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"
Allow-Events: telephone-event

v=0
o=CiscoSystemsSIP-Workflow-App-UserAgent 2253 2253 IN IP4 10.1.10.1
s=SIP Call
c=IN IP4 10.1.10.1
t=0 0
m=audio 16908 RTP/AVP 0
a=rtpmap:0 pcmu/8000
a=ptime:20

3395 05/01 15:47:11.315 ACCN SIPL 0 sip-ltp7: 1099, State=CONTACTINGreturning invitation
3395 05/01 15:47:11.315 ACCN SIPL 0 sip-ltp7: 1099, State=CONTACTINGgot Invitation
3395 05/01 15:47:11.315 ACCN SIPL 0 sip-ltp7: 1099, State=CONTACTINGbefore Invitation start
3395 05/01 15:47:11.320 ACCN SIPL 0 sip-ltp7: 1099, State=CONTACTINGafter Invitation start
3395 05/01 15:47:16.310 ACCN SIPL 0 sip-ltp7: 1099, State=CONTACTING terminating dialog in contacting state 20
3395 05/01 15:47:16.310 ACCN SIPL 0 sip-ltp7: 1099, State=CONTACTINGcontacting state hangup
3395 05/01 15:47:16.310 ACCN SIPL 0 sip-ltp7: 1099, State=CONTACTINGAfter contacting state hangup

Thanks in advance.

I have this problem too.
0 votes
Correct Answer by Paolo Bevilacqua about 6 years 7 months ago

Do not use on/off method. Unse unsolicited notify, that is much simpler and robust.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
Paolo Bevilacqua Sat, 05/01/2010 - 03:23

Do not use on/off method. Unse unsolicited notify, that is much simpler and robust.

Actions

This Discussion