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
2498
Views
10
Helpful
14
Replies

MWI issues with CME/CUE SIP integration

bkhanal1971
Level 3
Level 3

‎12-04-2015 07:03 AM - edited ‎03-19-2019 10:27 AM

I have CME 10.5 and CUC 10.5,newly installed. Everything seems to be working fine except that the MWI is not working. I have MWI turned on in each DNs as well as voicemail pilot number in the voice register global. I also created a dialpeer.

I have done the required work in telephony integration related in the CUC including ports, port groups etc. There are a few ports that are configured for MWIs. Everything looks ok but still MWI is not working. Voicemails are there in the test mailboxes.

Not knowing what went wrong, I decided to post here. If somebody could give me the checklist where I should be looking to resolve this issue,that would be great.

Thanks, Khanal

1 person had this problem
Labels:
0 Helpful
14 Replies 14

Vivek Batra
VIP Alumni
VIP Alumni

‎12-04-2015 07:09 AM

With debug ccsip messages, can you see notify message from cuc?

Did you configure mwi unsolicited command under sip-ua mode?

- Vivek

bkhanal1971
Level 3
Level 3
In response to Vivek Batra

‎12-04-2015 07:25 AM

I have mwi-server ipv4:........unsolicited command under sip-ua

I haven't done the ccsip messages debug yet but i will see if I can find something from the output.

Thank you Vivek.

0 Helpful

Vivek Batra
VIP Alumni
VIP Alumni
In response to bkhanal1971

‎12-07-2015 10:41 PM

Hi,

I can't see any issue with the configuration you've provided so far and it should simply work. Can you please share the ouput of show run to identify further?

- Vivek

0 Helpful

bkhanal1971
Level 3
Level 3
In response to Vivek Batra

‎12-08-2015 05:58 AM

Hi Vivek: Here is the relevant portion of show run command. I even tried sccp integration and when i fired "mwi relay" i got the error that says "Problem starting mwi application"

Preview file
2 KB
0 Helpful

Vivek Batra
VIP Alumni
VIP Alumni
In response to bkhanal1971

‎12-09-2015 01:30 AM

I can't figure out any issue with the configuration. I suggest you to check with TAC unless any of my friend here has to say on this.

- Vivek

0 Helpful

bkhanal1971
Level 3
Level 3
In response to Vivek Batra

‎12-09-2015 12:01 PM

I got it working finally. I had to eliminate long string of parameters for mwi-server command and just put mwi-server ipv4:ip unsolicited and mwi lights are on now. Thank for all your help Vivek.

Thanks

0 Helpful

Vivek Batra
VIP Alumni
VIP Alumni
In response to bkhanal1971

‎12-09-2015 08:09 PM

Thanks for updating the results Khanal.

- Vivek

0 Helpful

asotojimenezz
Level 1
Level 1
In response to bkhanal1971

‎07-26-2016 11:48 AM

Hello 

I have the same error

You can check that I wrong ??

I have days without success =(

Regards.

Preview file
22 KB
0 Helpful

bkhanal1971
Level 3
Level 3
In response to asotojimenezz

‎07-26-2016 12:41 PM

just put "mwi-server ipv4:address unsolicited" under sip-ua and see if that helps.

0 Helpful

asotojimenezz
Level 1
Level 1
In response to bkhanal1971

‎07-26-2016 09:18 PM

Hello

He removed the command

sip-ua

no mwi-server ipv4:172.16.1.2 expires 3600 port 5060 transport udp unsolicited or

no sip-ua

I place

mwi-server ipv4:172.16.1.2 unsolicited

but it still appeared in settings

sip-ua

mwi-server ipv4:172.16.1.2 expires 3600 port 5060 transport udp unsolicited

Because I still appears ??

As he put it correctly ??

Regards.

0 Helpful

bkhanal1971
Level 3
Level 3
In response to Vivek Batra

‎12-04-2015 07:40 AM

I have attached the output of debug ccsip pmessages. Looks like MWI is working but neither I see the light turned or or the voicemail icon. Any help would be a great help.

Thanks, Khanal

Preview file
5 KB
0 Helpful

Vivek Batra
VIP Alumni
VIP Alumni
In response to bkhanal1971

‎12-04-2015 07:47 AM

I can see notify coming from cuc but there is no 200 OK from CME.

Can you check cuc ip address is correct in mwi command? You can also verify the SIP bind interface is correct and that is where cuc should be sending notify.

- Vivek

bkhanal1971
Level 3
Level 3
In response to Vivek Batra

‎12-07-2015 09:49 AM

Hi Vivek,

Everything looks good in terms of configuration per your advise. I have used subinterface for sip bind

such as:

bind control source-int gig1/0/1.32

bind media source-int gig1/0/1.32

And the CUC ip address is correct in mwi command

and MWI config lines looks like this:

sip-ua

timers buffer-invite 800

mwi-server ipv4:x.x.x.x (CUC ip) expires 3600 port 5060 transport tcp unsolicited.

My problem still remains as it is.

0 Helpful

tyoungbauer
Level 1
Level 1
In response to bkhanal1971

‎10-04-2017 10:46 AM

Hi,

 

I know this is very old but I am having the same issue.  I wonder if anyone can help.  I have tried all three methods.  I can dial the MWI number and the ext and light and unlight the phone, but the trace doesn't show the sip number including the MWI prefix.

 

I am running CME and CUE n a UC500 with 8.6.5 code.

 

Sent:

INVITE sip:1000@10.200.11.251:5060 SIP/2.0

Via: SIP/2.0/UDP 10.200.11.250:5060;branch=z9hG4bK1A12614

Remote-Party-ID: <sip:1205@10.200.11.250>;party=calling;screen=no;privacy=off

From: <sip:1205@10.200.11.250>;tag=345B36C-50E

To: <sip:1000@10.200.11.251>

Date: Wed, 04 Oct 2017 17:37:16 GMT

Call-ID: 7FD859DF-A86111E7-8AFC940B-57223D2B@10.200.11.250

Supported: 100rel,timer,resource-priority,replaces,sdp-anat

Min-SE:  1800

Cisco-Guid: 2144845239-2824933863-2331546635-1461861675

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: 1507138636

Contact: <sip:1205@10.200.11.250:5060>

Diversion: <sip:1205@10.200.11.250>;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: 249

 

v=0

o=CiscoSystemsSIP-GW-UserAgent 414 5984 IN IP4 10.200.11.250

s=SIP Call

c=IN IP4 10.200.11.250

t=0 0

m=audio 18782 RTP/AVP 0 101

c=IN IP4 10.200.11.250

a=rtpmap:0 PCMU/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=ptime:20

 

000668: //950/7FD7BDB78AF8/SIP/Msg/ccsipDisplayMsg:

Sent:

INVITE sip:1000@10.200.11.251:5060 SIP/2.0

Via: SIP/2.0/UDP 10.200.11.250:5060;branch=z9hG4bK1A12614

Remote-Party-ID: <sip:1205@10.200.11.250>;party=calling;screen=no;privacy=off

From: <sip:1205@10.200.11.250>;tag=345B36C-50E

To: <sip:1000@10.200.11.251>

Date: Wed, 04 Oct 2017 17:37:17 GMT

Call-ID: 7FD859DF-A86111E7-8AFC940B-57223D2B@10.200.11.250

Supported: 100rel,timer,resource-priority,replaces,sdp-anat

Min-SE:  1800

Cisco-Guid: 2144845239-2824933863-2331546635-1461861675

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: 1507138637

Contact: <sip:1205@10.200.11.250:5060>

Diversion: <sip:1205@10.200.11.250>;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: 249

 

v=0

o=CiscoSystemsSIP-GW-UserAgent 414 5984 IN IP4 10.200.11.250

s=SIP Call

c=IN IP4 10.200.11.250

t=0 0

m=audio 18782 RTP/AVP 0 101

c=IN IP4 10.200.11.250

a=rtpmap:0 PCMU/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=ptime:20

 

000669: //950/7FD7BDB78AF8/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 10.200.11.250:5060;branch=z9hG4bK1A12614

To: <sip:1000@10.200.11.251>

From: <sip:1205@10.200.11.250>;tag=345B36C-50E

Call-ID: 7FD859DF-A86111E7-8AFC940B-57223D2B@10.200.11.250

CSeq: 101 INVITE

Content-Length: 0

Timestamp: 1507138637

 

 

000670: //950/7FD7BDB78AF8/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 180 Ringing

Via: SIP/2.0/UDP 10.200.11.250:5060;branch=z9hG4bK1A12614

To: <sip:1000@10.200.11.251>;tag=ds218b77f7

From: <sip:1205@10.200.11.250>;tag=345B36C-50E

Call-ID: 7FD859DF-A86111E7-8AFC940B-57223D2B@10.200.11.250

CSeq: 101 INVITE

Content-Length: 0

Contact: <sip:1000@10.200.11.251:5060;transport=udp>

Allow: INVITE, BYE, CANCEL, ACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO

Cisco-Gcid: 7FD859DF-A86111E7-8AFC940B-57223D2B@10.200.11.250

 

 

000671: //950/7FD7BDB78AF8/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 10.200.11.250:5060;branch=z9hG4bK1A12614

To: <sip:1000@10.200.11.251>;tag=ds218b77f7

From: <sip:1205@10.200.11.250>;tag=345B36C-50E

Call-ID: 7FD859DF-A86111E7-8AFC940B-57223D2B@10.200.11.250

CSeq: 101 INVITE

Content-Length: 133

Contact: <sip:1000@10.200.11.251:5060;transport=udp>

Content-Type: application/sdp

Call-Info: <sip:10.200.11.251:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"

Allow-Events: telephone-event

Allow: INVITE, BYE, CANCEL, ACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO

Cisco-Gcid: 7FD859DF-A86111E7-8AFC940B-57223D2B@10.200.11.250

 

v=0

o=CUE 7769615 2 IN IP4 10.200.11.251

s=SIP Call

c=IN IP4 10.200.11.251

t=0 0

m=audio 21116 RTP/AVP 0

a=rtpmap:0 PCMU/8000

 

000672: //950/7FD7BDB78AF8/SIP/Msg/ccsipDisplayMsg:

Sent:

ACK sip:1000@10.200.11.251:5060;transport=udp SIP/2.0

Via: SIP/2.0/UDP 10.200.11.250:5060;branch=z9hG4bK1A272E

From: <sip:1205@10.200.11.250>;tag=345B36C-50E

To: <sip:1000@10.200.11.251>;tag=ds218b77f7

Date: Wed, 04 Oct 2017 17:37:17 GMT

Call-ID: 7FD859DF-A86111E7-8AFC940B-57223D2B@10.200.11.250

Max-Forwards: 70

CSeq: 101 ACK

Allow-Events: telephone-event

Content-Length: 0

 

 

000673: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

SUBSCRIBE sip:1205@10.200.11.250:5060 SIP/2.0

Via: SIP/2.0/UDP 10.200.11.251:5060;branch=z9hG4bKGtM1eiuZu4D04FJQaYGdGw~~273

Max-Forwards: 70

To: <sip:1205@10.200.11.250>

From: <sip:1000@10.200.11.251>;tag=ds218b77f7

Call-ID: 7FD859DF-A86111E7-8AFC940B-57223D2B@10.200.11.250

CSeq: 1 SUBSCRIBE

Content-Length: 0

Contact: <sip:1000@10.200.11.251:5060;transport=udp>

Expires: 3600

Event: telephone-event

 

 

000674: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 10.200.11.251:5060;branch=z9hG4bKGtM1eiuZu4D04FJQaYGdGw~~273

From: <sip:1000@10.200.11.251>;tag=ds218b77f7

To: <sip:1205@10.200.11.250>;tag=345B36C-50E

Date: Wed, 04 Oct 2017 17:37:17 GMT

Call-ID: 7FD859DF-A86111E7-8AFC940B-57223D2B@10.200.11.250

CSeq: 1 SUBSCRIBE

Content-Length: 0

Contact: <sip:1205@10.200.11.250:5060>

Expires: 3600

 

 

000675: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

NOTIFY sip:1000@10.200.11.251:5060;transport=udp SIP/2.0

Via: SIP/2.0/UDP 10.200.11.250:5060;branch=z9hG4bK1A31A2

From: <sip:1205@10.200.11.250>;tag=345B36C-50E

To: <sip:1000@10.200.11.251>;tag=ds218b77f7

Call-ID: 7FD859DF-A86111E7-8AFC940B-57223D2B@10.200.11.250

CSeq: 102 NOTIFY

Max-Forwards: 70

Date: Wed, 04 Oct 2017 17:37:17 GMT

User-Agent: Cisco-SIPGateway/IOS-12.x

Event: telephone-event

Subscription-State: active

Contact: <sip:1205@10.200.11.250:5060>

Content-Length: 0

 

 

000676: //0/000000000000/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 10.200.11.250:5060;branch=z9hG4bK1A31A2

To: <sip:1000@10.200.11.251>;tag=ds218b77f7

From: <sip:1205@10.200.11.250>;tag=345B36C-50E

Call-ID: 7FD859DF-A86111E7-8AFC940B-57223D2B@10.200.11.250

CSeq: 102 NOTIFY

Content-Length: 0

Allow-Events: refer

Allow-Events: message-summary

Allow-Events: telephone-event

 

 

000677: //950/7FD7BDB78AF8/SIP/Msg/ccsipDisplayMsg:

Sent:

BYE sip:1000@10.200.11.251:5060;transport=udp SIP/2.0

Via: SIP/2.0/UDP 10.200.11.250:5060;branch=z9hG4bK1A41A90

From: <sip:1205@10.200.11.250>;tag=345B36C-50E

To: <sip:1000@10.200.11.251>;tag=ds218b77f7

Date: Wed, 04 Oct 2017 17:37:17 GMT

Call-ID: 7FD859DF-A86111E7-8AFC940B-57223D2B@10.200.11.250

User-Agent: Cisco-SIPGateway/IOS-12.x

Max-Forwards: 70

Timestamp: 1507138651

CSeq: 103 BYE

Reason: Q.850;cause=16

P-RTP-Stat: PS=715,OS=114400,PR=617,OR=98243,PL=0,JI=0,LA=0,DU=14

Content-Length: 0

 

 

000678: //950/7FD7BDB78AF8/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 10.200.11.250:5060;branch=z9hG4bK1A41A90

To: <sip:1000@10.200.11.251>;tag=ds218b77f7

From: <sip:1205@10.200.11.250>;tag=345B36C-50E

Call-ID: 7FD859DF-A86111E7-8AFC940B-57223D2B@10.200.11.250

CSeq: 103 BYE

Content-Length: 0

 

 

000679: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

NOTIFY sip:1000@10.200.11.251:5060;transport=udp SIP/2.0

Via: SIP/2.0/UDP 10.200.11.250:5060;branch=z9hG4bK1A5D2E

From: <sip:1205@10.200.11.250>;tag=345B36C-50E

To: <sip:1000@10.200.11.251>;tag=ds218b77f7

Call-ID: 7FD859DF-A86111E7-8AFC940B-57223D2B@10.200.11.250

CSeq: 104 NOTIFY

Max-Forwards: 70

Date: Wed, 04 Oct 2017 17:37:31 GMT

User-Agent: Cisco-SIPGateway/IOS-12.x

Event: telephone-event

Subscription-State: terminated

Contact: <sip:1205@10.200.11.250:5060>

Content-Length: 0

 

 

000680: //0/000000000000/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 10.200.11.250:5060;branch=z9hG4bK1A5D2E

To: <sip:1000@10.200.11.251>;tag=ds218b77f7

From: <sip:1205@10.200.11.250>;tag=345B36C-50E

Call-ID: 7FD859DF-A86111E7-8AFC940B-57223D2B@10.200.11.250

CSeq: 104 NOTIFY

Content-Length: 0

Allow-Events: refer

Allow-Events: message-summary

Allow-Events: telephone-event

 

Thanks

Todd

0 Helpful
Customers Also Viewed These Support Documents