I followed your suggestion and my OBi110 is configured with:
X_SipDebugOption set to "
Log All Except REGISTER Messages"
X_MWISubscribe is enabled
The following pattern of syslog messages repeats itself:
- NOTIFY
- mwi notify state 0
- sendto
- SIP/2.0 200 OK
- mwi subs failed
- RxFrom
Here is the exact pattern except I've anonymized the SIP and IP addresses and put in line-breaks (hopefully in the right places) to make it more readable:
Quote
- [NOTIFY
sip:999999@11.11.11.11:5060 SIP/2.0
Via: SIP/2.0/UDP 22.22.22.22:5060;branch=z9hG4bK7fd93dab;rport
From: "Unknown" <sip:Unknown@montreal.voip.ms>;tag=as694a18b1
To: <sip:sip:999999@11.11.11.11:5060>;tag=SP158723cae4c602f7c
Contact: <sip:Unknown@22.22.22.22>
Call-ID: 22471cf8@10.1.1.1
CSeq: 127 NOTIFY
User-Agent: VoIPMS/SERAST
Max-Forwards: 70
Event: message-summary
Content-Type: application/simple-message-summary
Subscription-State: active
Content-Length: 96
Messages-Waiting: no
Message-Account: sip:asterisk@montreal.voip.ms
Voice-Message: 0/0 (0/0)] - [<7> +++ mwi notify state 0]
- [<7> sendto 43cd4aa4:5060(342)]
- [SIP/2.0 200 OK
Call-ID: 22471cf8@10.1.1.1
CSeq: 127 NOTIFY
Content-Length: 0
From: "Unknown"<sip:Unknown@montreal.voip.ms>;tag=as694a18b1
To:<sip:sip:999999@11.11.11.11:5060>;tag=SP158723cae4c602f7c
Via: SIP/2.0/UDP 22.22.22.22:5060;branch=z9hG4bK7fd93dab;received=22.22.22.22;rport=5060
Server: OBIHAI/OBi110-1.3.0.2651] - [<7> ++++ mwi subs failed]
- [<7> ++++ mwi subs failed]
- [<7> ++++ mwi subs failed]
- [<7> RxFrom:43cd4aa4:5060]
The NOTIFY message clearly shows that I have no waiting voicemail messages. When I left a message, NOTIFY indicated one voicemail was waiting and the log displayed 'mwi state 1'. This part seems to be working properly.
I'm not sure what the next log entry, SIP/2.0 200 OK, means buts it seems to suggest everything is fine. Nevertheless, the next entries are 'mwi subs failed'.
I have a feeble grasp of the true purpose of
X_MWISubscribe. From what I've read, it is a request, from a SIP-based device to the server, to be informed of (subscribe to) the status of voicemail messages. Apparently, one device can even subscribe to another device's status. My house phone's MWI light works just fine if X_MWISubscribe is
disabled and MWIEnable and X_VMWIEnable are enabled. Clearly, X_MWISubscribe must serve some higher purpose than the menial task of lighting up my phone's MWI light ... and I don't know what that may be.
In my OBI110's configuration,
X_MWISubscribeURI is blank. Is this option blank for you as well do you have it populated with the URI of your SIP account?