OBi110 Syslog messages: Report status of Message-Waiting-Indicator (MWI)?

(1/3) > >>

Telex:
Does anyone know what, if any, syslog messages can be used to indicate the presence or absence of new voicemail?

Does the Obi110 report the status of the Message-Waiting-Indicator (MWI) in its syslog messages?  In other words, when it detects there is new voicemail, does it report this via a syslog message?

I'm looking for the ability to detect when MWI is enabled/disabled by monitoring the Obi110's syslog messages.  Here's what I tried:

While monitoring the syslog, I called my home phone, left a message, then hung up.The moment the MWI indicator light lit up on my house phone, a syslog message appeared indicated  a "howling" tone. This may correlate with MWI being enabled.Using my house phone I called my voicemailbox, erased the new voicemail message, and hung up.At the moment the MWI indicator turned off on my house phone, I could not find a correlating syslog message.

I know I can detect MWI status whenever the phone goes off-hook because syslog indicates a "stutter" tone. However, this tone is generated only when the phone is off-hook and I want to detect MWI while the phone is on-hook.


BTW, based on what I've read, the 'howler tone' is supposed to indicate a phone left off-hook for too long. Odd that it was reported in syslog even though my phone was onhook at the time.

jeffml:
From my obi syslog output:

+++ mwi notify state 0

Telex:
Thanks for the quick reply.

What is your Obi110's syslog level? Seven? Mine is set at seven and yet I don't see that message.

I'm using a perl script to monitor the syslog traffic and I'm fairly confident that it is displaying all received messages. Maybe I'll try a syslog monitoring program and compare the results.

UPDATE
I installed Syslog Watcher and it confirms the perl script I use works fine. I do not get the "+++ mwi notify state 0" message.

Do you have some other option enabled that causes the OBi110 to generate this message?

jeffml:
Quote

Do you have some other option enabled that causes the OBi110 to generate this message?

Syslog Level 7 with:

X_MWISubscribe enabled in ITSP Profile A/SIP
X_SipDebugOption set to "Log All Except REGISTER Messages" in Voice Services/SP1 Service
MWIEnable and X_VMWIEnable enabled in Voice Services/SP1 Service/Calling Features

Not sure if these all need to be set but everything works as expected at this moment.

Telex:
OK, I already had MWIEnable and X_VMWIEnable enabled.

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).

Finally, I enabled X_MWISubscribe and that produced the desired results:
+++ mwi notify state 1
and
+++ mwi notify state 0

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?


PS
If there's no way to suppress the generation of the "mwi subs failed" message, then I suppose I could use it as a 'heartbeat' for monitoring the OBi110's operation. As long as those 'subs failed' message are received regularly, it means the OBi110 is alive and well.

Navigation

[0] Message Index

[#] Next page