Firmware update for 20x series
RFC3261:
Quote from: LTN1 on May 07, 2018, 09:34:49 am
I'm not in any GV beta program.
In many ways, if you are using any (especially free) cloud services, you *are* in their beta program. It is called CI/CD. They control the transmission. They control the horizontal. They control the vertical.
Taoman:
Is it my imagination or has call quality improved when using SIP with Google Voice?
SteveInWA:
Quote from: Taoman on May 07, 2018, 12:55:23 pm
Is it my imagination or has call quality improved when using SIP with Google Voice?
It is not your imagination. There are fewer hops back and forth between the legacy PSTN and the pure VoIP networks.
Also note: if both ends of the call are pure VoIP, not going through the PSTN, and both endpoints support it, then the calls will be in wideband audio (Opus CODEC), with superb call quality. OBiTALK IP phones support Opus; OBiTALK ATAs do not, as of this posting date.
Examples, assuming both endpoints have OBiTALK IP phones:
You both have Google Voice numbers. The call will be in HD.
You both have Callcentric accounts, and you call using their 1777xxxxxxx on-network numbers. The call will be in HD.
You and your called party both have SIP ITSPs that support Opus, and they have some sort of peering relationship. The call will be in HD.
The long-term, blue sky scenario: a mobile carrier peers with Google Voice, and there is some way to transcode or otherwise magically support the different CODECs used by the mobile carriers, then the call will be in HD. One hurdle at this time, is that fixed VoIP devices typically support Opus, whereas the mobile carriers are using G.722.2 AMR-WB CODEC.
chilirock:
What if anything needs to be done to trigger the firmware update? I had previously disabled firmware updates on my Obi200 after manually updating to v5804. After reading the changes here that GV is making to VOIP, I re-enabled "Auto Firmware Update" and "ObiTalk Provisioning" and set method to "Periodic" for both. Note, I still have ITSP Provisioning set to "Disabled". Not sure if that needs to be enabled.
After applying the setting changes, the device rebooted and the firmware was updated, but it went backwards from v5804 to v5757EX. Can someone help me understand why it would have gone backwards? Also, in the GV migration, which comes first, the firmware update or the GV change to Legacy Chat setting?
Thanks in advance for your help
billsimon:
Quote from: SteveInWA on May 07, 2018, 02:58:32 pm
Also note: if both ends of the call are pure VoIP, not going through the PSTN, and both endpoints support it, then the calls will be in wideband audio (Opus CODEC), with superb call quality.
Examples, assuming both endpoints have OBiTALK IP phones: ...
Since this thread is about the Obi 2xx and not the IP phones, I am curious whether the Obi 2xx are getting the Opus codec or will continue to have the limited list in the data sheet (http://www.obihai.com/docs/OBi202DS.pdf) - G.711u/a, G.726, G.729a, and iLBC (which was basically obsolete right out of the gate and is superseded by Opus).
Navigation
[0] Message Index
[#] Next page
[*] Previous page