Firmware update for 20x series
SteveInWA:
Quote from: chilirock on November 02, 2017, 07:54:22 pm
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, CallCentric connected and showed Registered. But as soon as I went into Obi Expert to change the Ring Profile setting from B to A, 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 connect.
Something in the firmware update seems to have broken CallCentric for me.
No, the firmware update did not touch SIP provider support. It's user error. Delete SP2. On the OBiTALK portal web page, click SP2. On the next page, skip the offer to use Google Voice. Scroll down to the bottom of the page and click "OBiTALK Compatible Service Providers". On the next page, click "Callcentric", and then fill in your Callcentric 1777xxxxxxxxxx number and SIP password.
chilirock:
I have performed the same configuration many many times. The steps I used for the initial and subsequent configurations were exactly as you described. I just looked again and CC now shows as "Registered". The only thing I did differently this time was to change the settings locally vs. changing them via Obi Expert. I'll have to do more testing to see if I can replicate the issue.
Update: After further testing, I realized that the issue with CallCentric not registering was due to me changing the X_ServProvProfile from B to A on Voice Services>SP2 Service. I made the change accidentally when I was changing X_RingProfile and X_CodecProfile from B to A. After changing X_ServProvProfile (on SP2) back to B (from A), the service showed "Registered" as expected.
GPz1100:
@chilirock You could try comparing the settings between the two. Open several tabs to see the locally configured callcentric setting. Don't close or refresh these tabs. Allow obitalk (obiexpert) to push its settings to the device then compare with the already open tabs.
Could be obitalk (obiexpert) portal may need to be updated to work with the new firmwareż?
SteveInWA:
Quote from: GPz1100 on November 02, 2017, 09:19:47 pm
@chilirock You could try comparing the settings between the two. Open several tabs to see the locally configured callcentric setting. Don't close or refresh these tabs. Allow obitalk (obiexpert) to push its settings to the device then compare with the already open tabs.
Could be obitalk (obiexpert) portal may need to be updated to work with the new firmwareż?
No. There are no updates to the portal required. The firmware update has nothing to do with this at all. I have a total of seven OBi devices, including 200s, 202s, and several IP phones, all using Callcentric, configured via the portal. All were updated today, and none have any problem with Callcentric. The fact that it's working now proves this. This was some sort of human error caused after performing a factory reset on the device and re-configuring.
ProfTech:
Quote from: Taoman on November 02, 2017, 05:44:39 pm
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.
Is everyone comfortable with using EX firmware in non - GV ATA's? I would like to update to the latest but we don't ever plan to use Google Voice.
Navigation
[0] Message Index
[#] Next page
[*] Previous page