MessageWaiting is on, but not getting stutter tone
SteveInWA:
I am not equating Fongo's locked-down home phone service with byod freephoneline.ca, only linking to their support forum.
You're correct that the ITSP is responsible for toggling the MWI status on or off, and that the ATA is responsible for playing the stutter tone. And, of course, the telephone itself needs to have the feature enabled. Panny phones have a setting to optionally turn it off. I realize you said you tried another phone, but I am just mentioning this for completeness.
Note that the OBi "MessageWaiting" parameter is just a register holding the current state of whether or not there is a message waiting; it's not a setting.
The OBi should play whatever stutter tone you have set in Tone Settings--Tone Profile A (or B)-->Stutter Tone.
The default values are:
A: 350-18,440-18;20;2(.1+.1);()
B: 400-18,425-18,450-18;20;2(.1+.04);()
These two profiles are selected under Physical Interfaces-->PHONE 1 (or PHONE 2)-->ToneProfile
I suspect that your various configuration customizations and repeated firmware changes have messed this up somehow. There is nothing wrong with the current firmware in this regard. At least in my case, running firmware build 5285, both MWI and VMWI work as designed, using Callcentric, with no tweaks needed.
In theory, you should be able to delete SP1 and then re-add SP1 with the basic ITSP settings, and it should work. The OBiTALK portal has a pre-defined configuration for freephoneline.ca
Webslinger:
Quote from: SteveInWA on September 25, 2016, 01:50:48 am
You're correct that the ITSP is responsible for toggling the MWI status on or off, and that the ATA is responsible for playing the stutter tone. And, of course, the telephone itself needs to have the feature enabled. Panny phones have a setting to optionally turn it off. I realize you said you tried another phone, but I am just mentioning this for completeness.
Yeah, VM tone detect is enabled. Even if it weren't, the stutter tone should still be heard, and it's not.
Quote
Note that the OBi "MessageWaiting" parameter is just a register holding the current state of whether or not there is a message waiting; it's not a setting.
Yes, I appreciate the distinction you're making.
Quote
The OBi should play whatever stutter tone you have set in Tone Settings--Tone Profile A (or B)-->Stutter Tone.
The default values are:
A: 350-18,440-18;20;2(.1+.1);()
B: 400-18,425-18,450-18;20;2(.1+.04);()
These two profiles are selected under Physical Interfaces-->PHONE 1 (or PHONE 2)-->ToneProfile
Thanks, those are the values listed in the ATA.
Quote
In theory, you should be able to delete SP1 and then re-add SP1 with the basic ITSP settings, and it should work.
Unfortunately, it doesn't. At least, not with 3.1.0 (Build:5285)
I guess I'll try resetting the device back to defaults and re-doing everything.
Very strange issue
Webslinger:
Quote from: Webslinger on September 25, 2016, 07:44:03 am
I guess I'll try resetting the device back to defaults and re-doing everything.
And, of course, that fixed the problem. Well, it's fixed until all four SPs are configured again. What a pain... ::)
I really wish I knew for sure what caused this issue.
SteveInWA:
I had some time to experiment just now. I have an older Panasonic DECT 6.0 cordless phone connected to my OBi 202. I can confirm that, using the local web page interface, toggling the "MessageWaiting" register on or off and clicking "Submit" will immediately cause the stutter tone to turn on or off on the handset. Rebooting the OBi isn't necessary, since you aren't actually changing a setting, so if you want to futz with this further, that will save you some time.
Webslinger:
The issue is remaining ObiPlus settings after a subscription expires. I had no option to disable or remove these settings in the ATA.
Navigation
[0] Message Index
[*] Previous page