One way audio on outgoing calls only / GV
drgeoff:
Quote from: A_Friend on July 06, 2018, 07:42:18 am
Quote from: drgeoff on July 05, 2018, 04:23:56 pm
Whether the problem is with OBi's firmware or GV's infrastructure is difficult to tell.
Don't discount the possibility that the ObiTalk portal is the culprit. I'm tempted to try the crowdsourced, third-party firmware from obifirmware.com and register directly with google.
That indicates you don't understand the function of the portal. The portal is used to configure your OBi device. The portal plays no part whatever (neither call set up, nor audio transmission nor cleardown) in the calls between your Obi and Google Voice (or other Service Providers). The only calls which use OBi servers are calls which use the Obitalk network.
A_Friend:
Quote from: drgeoff on July 06, 2018, 07:56:59 am
That indicates you don't understand the function of the portal. The portal is used to configure your OBi device. The portal plays no part whatever (neither call set up, nor audio transmission nor cleardown) in the calls between your Obi and Google Voice (or other Service Providers). The only calls which use OBi servers are calls which use the Obitalk network.
That's not what I meant. I meant the configuration script (or whatever) the portal is currently using is... wrong. Or at least that's a possibility in my mind, that it's out of sync with the current firmware or doing something else wrong. Why else would I, after a fresh GV setup on the portal, be seeing a Peer RTP Address of 74.125.39.26:19305(relay), which someone (possibly you?) told me was associated with the XMPP version of GV, when I initiate a phone call?
GPz1100:
Quote from: drgeoff on July 06, 2018, 07:56:59 am
That indicates you don't understand the function of the portal. The portal is used to configure your OBi device. The portal plays no part whatever (neither call set up, nor audio transmission nor cleardown) in the calls between your Obi and Google Voice (or other Service Providers). The only calls which use OBi servers are calls which use the Obitalk network.
The portal's job is to configure the device to connect to gv. For those who's accounts are still on the xmpp platform, conversion *should* occur the first time the obi (configured for gv sip) connects to the gv account. Based on comments in a number of these threads, it appears this is not happening. It's uncertain whether the issue is in the 5897 firmware, obitalk portal, or changes at google. Based on various success posts (here/dslr), it appears downgrading to the 5859 firmware and reattempting provisioning seems to convert the account properly and issue is resolved.
As cumbersome as it is it generate one's own oauth2 credentials, using the modded firmware (obifirmware.com) along with these credentials has generated successful gv sip accounts each and every time for me. Unfortunately, once one is on the official 5859 firmware, flashing the modded firmware is no longer possible (because of signature checks). So customers are SOL trying to get things worked. Not to mention, pushing a new buggy firmware on the day before a holiday (7/3) was brilliant planning!
WillSmith:
UPDATE: I tested my OBI200 today - appears to be working properly now (I can hear the other party whether I initiate or receive the call).
vbprof:
Mine still does not work.
Navigation
[0] Message Index
[*] Previous page