Google Voice Message Waiting Indicator
SteveInWA:
Thanks, Taoman!
avinyc:
Quote from: SteveInWA on September 13, 2014, 07:54:36 pm
The MWI and VMWI options are there, on the Voice Service page. See my attached screenshots -- one for my 202, showing a SIP Service Provider slot and the other for my 1032, showing Google Voice as a SP.
However: Mark, the issue is that, even with these settings enabled, they have no effect on generating MWI/VMWI signals for Google Voice as a service provider.
The question to your engineers is: is this a bug that they're working on, or is it a limitation of the new access method for Google Voice?
Steve,
In your 2nd screenshot, you also have the parameter "MessageWaiting" but I see it is not checked as Mark had in his example. If you enable that setting on the 1032, it should get the MWI working on that device. Since that option is absent from the 202, it is looking like that may be part of the problem.
SteveInWA:
Quote from: avinyc on September 13, 2014, 09:24:16 pm
Quote from: SteveInWA on September 13, 2014, 07:54:36 pm
The MWI and VMWI options are there, on the Voice Service page. See my attached screenshots -- one for my 202, showing a SIP Service Provider slot and the other for my 1032, showing Google Voice as a SP.
However: Mark, the issue is that, even with these settings enabled, they have no effect on generating MWI/VMWI signals for Google Voice as a service provider.
The question to your engineers is: is this a bug that they're working on, or is it a limitation of the new access method for Google Voice?
Steve,
In your 2nd screenshot, you also have the parameter "MessageWaiting" but I see it is not checked as Mark had in his example. If you enable that setting on the 1032, it should get the MWI working on that device. Since that option is absent from the 202, it is looking like that may be part of the problem.
No, the unchecked options with the "2" after them are to turn on the indicators on phone port 2 vs. phone port 1 (this is on an OBi 202, which has two independent RJ11 phone ports).
The test I ran was on the 1032 IP phone, which has only one phone port (the phone, itself), and it doesn't work.
As Taoman replied, Obihai has already confirmed that MWI/VMWI is no longer supported for Google Voice.
avinyc:
Quote from: SteveInWA on September 13, 2014, 09:43:04 pm
No, the unchecked options with the "2" after them are to turn on the indicators on phone port 2 vs. phone port 1 (this is on an OBi 202, which has two independent RJ11 phone ports).
The test I ran was on the 1032 IP phone, which has only one phone port (the phone, itself), and it doesn't work.
As Taoman replied, Obihai has already confirmed that MWI/VMWI is no longer supported for Google Voice.
Hi Steve, I wasn't referring to the parameters marked with a 2. I just noticed on the 1032 screenshot you had the 3rd parameter labeled "MessageWaiting" and it was unchecked. The 3 of them are "MWIEnable", "X_VMWIEnable" and "MessageWaiting". No matter though, as I see that Mark edited his post to say this feature is currently unavailable. I just found that a little strange that certain devices still had the old parameter for MessageWaiting and other devices like the OBi202 do not.
In any event, it appears there is no manual workaround. It is a bit confusing as the capability does exist and has worked prior to the firmware upgrade. Ooma devices do not appear affected by this problem either, so perhaps it will be fixed for us in a future update.
SteveInWA:
The "MessageWaiting" parameter is a dynamic register that actually holds the status of, well, Message Waiting! It's not a static setting. I don't know why they included in the settings page, since it is useless and misleading.
You can't make a comparison at all to your Ooma device or to a SIP VoIP provider. This issue is unique to Google Voice, which does not use the standard SIP protocol, and thus, is not sending MWI/VMWI signals the same way.
Navigation
[0] Message Index
[#] Next page
[*] Previous page