Google Voice Message Waiting Indicator
ramjet73:
Quote from: SteveInWA on September 14, 2014, 06:12:35 pm
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.
Does XMPP even support MWI/VMWI signaling?
I did some Google searches to try to find out and the closest I could come was this post from August of 2008 which discussed it as a feature request. If XMPP doesn't support communicating those items Obihai must have been accessing that information by using the credentials (Google userid and password) that they no longer require, perhaps via a web service of some sort that requires those credentials.
That's just a guess but something other than XMPP must have been used to get message waiting status since there would be no reason to stop supporting it if it is available as part of the XMPP protocol. Or maybe Obihai is just positioning for the replacement of XMPP by Google?
CLTGreg:
I miss this feature but usually disabled it. I was looking at turning it back on though. The 202 would get SMS sent to the caller ID which was really cool unless you didn't turn it off at night.
SteveInWA:
Quote from: ramjet73 on September 14, 2014, 06:47:54 pm
Quote from: SteveInWA on September 14, 2014, 06:12:35 pm
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.
Does XMPP even support MWI/VMWI signaling?
I did some Google searches to try to find out and the closest I could come was this post from August of 2008 which discussed it as a feature request. If XMPP doesn't support communicating those items Obihai must have been accessing that information by using the credentials (Google userid and password) that they no longer require, perhaps via a web service of some sort that requires those credentials.
That's just a guess but something other than XMPP must have been used to get message waiting status since there would be no reason to stop supporting it if it is available as part of the XMPP protocol. Or maybe Obihai is just positioning for the replacement of XMPP by Google?
I really don't know how Obihai did it, and based on the number of times it broke and had to be modified over the years, it likely wasn't using something officially-supported. We'll just have to wait and see if this feature reappears over time as the two companies evolve their services.
Newbie:
Short version:
GV MWI (stutter tone and visual indication) is working fine on an OBI 200 SW 3.0.1 (Build: 4367) configured manually using the OBI 200 web interface and never configured in the OBITALK portal.
Long version:
I just got an OBI 200 that came with SW 3.0.1 (Build: 4367). I was an early adopter of the OBI 110 and after just updating the 110's firmware and getting forced into using the OBITALK gateway and the new Google authorization, I made sure to stay away from OBITALK and disabled firmware updates and OBITALK before letting the OBI 200 have internet access.
(Updated my OBI 110 fw from this thread Build 2872 http://www.obitalk.com/forum/index.php?topic=8482.0)
After manually setting up voip.ms, 2 GV lines and a free Callcentric DID using only the OBI200 web interface, GV voice mail indication, both stutter tone and visual indication, is working fine. I'll definitely avoid any firmware upgrades and will be one pissed off customer if they manage to force one. They shouldn't be able to unless they've left a hidden backdoor access mechanism.
I've been away from these forums since the first few months after the OBI 100/110 release and was appalled to find OBIHAI no longer allows firmware downgrades. On top of that they don't even seem to be providing release notes for many firmware versions. I can't find any info on the changes to the OBI 110 firmware I upgraded to or the firmware that came on my new OBI200.
As an early adopter of OBIHAI's products, I'm disappointed to see their focus has shifted so much. Even with their new business focus, I don't understand companies who prohibit firmware downgrades and avoid doing business with them whenever possible. No one is perfect and I won't accept downtime when a firmware release breaks something critical to me when a simple downgrade to a previous version could get me back up quickly.
ramjet73:
Quote from: Newbie on September 15, 2014, 11:23:14 pm
After manually setting up voip.ms, 2 GV lines and a free Callcentric DID using only the OBI200 web interface, GV voice mail indication, both stutter tone and visual indication, is working fine. I'll definitely avoid any firmware upgrades and will be one pissed off customer if they manage to force one. They shouldn't be able to unless they've left a hidden backdoor access mechanism.
My understanding is that you will have to upgrade the firmware at some point or GV will just stop working since Google is now requiring the authorization method that is only supported by the new firmware.
You've essentially figured out a way to "stop the clock", and work around the new security requirements and firmware, but that is only a temporary solution. The changes in GV were initiated by Google, not Obihai, and IMO having GV support without MWI/VMWI indicators is still better than not having it at all.
Navigation
[0] Message Index
[#] Next page
[*] Previous page