OBi110 Syslog messages: Report status of Message-Waiting-Indicator (MWI)?
jeffml:
Quote
I set X_SipDebugOption to "Log All Except REGISTER Messages" and that generated several lengthy SIP-related messages but nothing about MWI status so I put the option back to its default state (disabled).
I think I had this set to watch for lost registrations and send me an email when it dropped.
Quote
The only unwanted side-effect is that the following message is being generated every ten seconds:
++++ mwi subs failed
Are you also receiving this failure message? Anything I can do to help 'subs' succeed rather than fail?
I don't get that currently but looking back at my logs I have received it (not continuously) but it was preceded by a "SIP/2.0 404 Not found (no mailbox)" message from my provider. Maybe put X_SipDebugOption back in place for a bit and see if that helps explain it.
Telex:
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:
NOTIFYmwi notify state 0sendtoSIP/2.0 200 OKmwi subs failedRxFrom
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?
jeffml:
A couple things: I'm using voip.ms same as you but I'm using the london server and also using a sub-account. May or may not make a difference.
X_MWISubscribeExpires = 360
X_MWISubscribeURI is blank (default setting)
I'm also using the Expert Config on the website but verifying on both.
Telex:
Quote from: jeffml on December 11, 2011, 07:59:09 am
X_MWISubscribeExpires = 360
X_MWISubscribeURI is blank (default setting)
I'm also using the Expert Config on the website but verifying on both.
My X_MWISubscribeExpires option is set to 3600 (default). I also use Expert Config (and verify the changes took place locally).
Reaching at straws here but maybe voip.ms's London server is configured to respond differently than their Montreal server; I see 'subs failed' whereas you don't. Now it seems like the 'subs failed' message may appear for some folks but not others ... and I win the 'prize'. :(
Maybe some of the other forum gurus can chime in and shed more light on this issue; I'm stumped.
jeffml:
Do you by any chance have something configured as your second provider? The failed message doesn't specify which SP it comes from. *crosses fingers*
It will probably be one of those things you will end up having to ignore but you are probably like me and it will drive you insane. Good luck.
Navigation
[0] Message Index
[#] Next page
[*] Previous page