Jump to content

Recommended Posts

I have never had a problem, however I have heard rumors of old versions of firmware having issues, or if you have 2+ devices registered to the same extension, and one is subscribing to the MWI, and the other is not.

Link to post
Share on other sites
Is there a trick to get MWI working? cisco blah

 

 

Lofile should look like this.

 

 

 

NOTIFY sip:42@192.168.0.34:2050;line=wci1bz2y SIP/2.0

Via: SIP/2.0/UDP 192.168.0.33:5060;branch=z9hG4bK-d6a8dd9eed186e03416b38e516dc8190;rport

From: <sip:42@pbx.company.com;user=phone>;tag=05f96e8ce6

To: <sip:42@pbx.company.com>;tag=al0f66n7nn

Call-ID: 3c2693c7c50a-1s5kcf653dy3

CSeq: 16431 NOTIFY

Max-Forwards: 70

Contact: <sip:192.168.0.33:5060;transport=udp>

Event: message-summary

Subscription-State: active;expires=355

Content-Type: application/simple-message-summary

Content-Length: 91

 

Messages-Waiting: yes

Message-Account: sip:842@pbx.company.com

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

[7] 2010/06/10 20:09:06: SIP Tx udp:192.168.0.34:2050:

NOTIFY sip:42@192.168.0.34:2050;line=wci1bz2y SIP/2.0

Via: SIP/2.0/UDP 192.168.0.33:5060;branch=z9hG4bK-39949aef1b7405665f896b6d148673bc;rport

From: <sip:42@pbx.company.com;user=phone>;tag=05f96e8ce6

To: <sip:42@pbx.company.com>;tag=al0f66n7nn

Call-ID: 3c2693c7c50a-1s5kcf653dy3

CSeq: 16432 NOTIFY

Max-Forwards: 70

Contact: <sip:192.168.0.33:5060;transport=udp>

Event: message-summary

Subscription-State: active;expires=355

Content-Type: application/simple-message-summary

Content-Length: 91

 

Messages-Waiting: yes

Message-Account: sip:842@pbx.company.com

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

Link to post
Share on other sites
Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...