Vestalink Now "Supports Direct Integration With Google Voice"
gsmlnx:
2 cons to using Vestalink
1. You have to pay Vestalink to use their service in addition to paying Google
2. All your calls to and from Google are going through a 3rd party server (Vestalink) so if Vestalink have problems so do you. You are adding in a level of complexity that isn't needed. The more moving parts, the more to go wrong.
Vestalink:
Here are some benefits for users interested in Vestalink
1. Vestalink has 911 services natively
2. Google Voice will not port/transfer in landline numbers, Vestalink can.
3. Currently MWI (message waiting indicator) no longer works with the Obi and Google Voice directly, however it does when you use your OBi with Vestalink voicemail and Google Voice calling.
Vestalink is designed to be a simple drop in replacement for a landline. A complete package and integration with Google voice.
Quote
All your calls to and from Google are going through a 3rd party server (Vestalink) so if Vestalink have problems so do you. You are adding in a level of complexity that isn't needed. The more moving parts, the more to go wrong.
I believe if Obihai's provisioning servers went down your OBi would not be able to update its Oauth password to re-register to Google Voice. This password is updated every hour.
LTN1:
Quote from: Vestalink on March 23, 2015, 12:45:44 pm
I believe if Obihai's provisioning servers went down your OBi would not be able to update its Oauth password to re-register to Google Voice. This password is updated every hour.
Steve...is the above claim regarding Obihai provisioning servers supported by the facts?
billsimon:
The device could refresh its own token as needed, but this would require the firmware to contain Obihai's oauth2 client-id and secret with Google, which would be a questionable design decision. (Those credentials are disposable, and should be disposed of, when there's suspicion of compromise.)
In other words, it's likely that the devices rely on the provisioning server to provide updated access tokens either on a regular basis or as needed. A network capture would easily confirm or refute.
Vestalink:
That’s what I was thinking too. Seems questionable to put the oauth google credentials in the device firmware directly, those are best on the provisioning servers especially since if those credentials change it wont require another firmware upgrade. Maybe someone can confirm this theory by blocking the obitalk provisioning servers and trying to connect the OBi via oauth to GV?
Navigation
[0] Message Index
[#] Next page
[*] Previous page