Firmware update for 20x series
Taoman:
Just got pushed out to my 200 (yellow triangle) which is years out of warranty.
http://fw.obihai.com/OBi202-3-2-1-5757EX.fw
for OBiEXTRAS support.
GPz1100:
Toaman, did this fix the gv issue for you without resorting to different dns servers?
Taoman:
Quote from: GPz1100 on November 02, 2017, 06:21:15 pm
Toaman, did this fix the gv issue for you without resorting to different dns servers?
I never had the issue. I use Comcast for my DNS on a 200 and 110.
I switched to using Google's DNS servers and I got the error message for a few seconds but then it connected and was just fine.
SteveInWA:
Please read: http://www.obitalk.com/forum/index.php?topic=13113.msg84139
chilirock:
I updated the firmware to 5757EX. I performed a factory reset after the upgrade. I setup everything from scratch, GV on SP1 and CC on SP2. Google Voice is now connecting fine and calls are working.
However, I'm now having an issue with CallCentric. After the initial configuration from the ObiTalk.com portal, CallCentric connected and showed Registered. But as soon as I went into the local web portal to change settings then reboot (e.g. Ring Profile from B to A, disable T.38 codec, etc.), it will no longer connect.
I don't get a "backing off" error message like I did when GV wasn't working. It just says "Service Not Configured" next to SP2. I tried deleting the service and re-adding it. It still won't register. The only way I can get it to re-register is to remove the device from the portal and start over. Very frustrating.
Something in the firmware update seems to have broken CallCentric for me.
Update: Issue with CallCentric registration resolved by reversing setting made accidentally to X_ServProvProfile (see below) http://www.obitalk.com/forum/index.php?topic=9983.msg84157#msg84157
Navigation
[0] Message Index
[#] Next page
[*] Previous page