The beauty of the Internet is that you can read the same document I did, for free!

Yes, fax has a long history of changing its communications protocols and command set, just like dial-up modems did, to improve speed and reliability. This resulted in new ways to negotiate connections (including speed, error correction, CODEC, etc.). CED is just one of those methods, and since fax devices are backwards-compatible, and negotiate to the highest-mutually-supported standards, you can just enable the settings and fuggedaboudit. Perhaps they added this setting at the request of some large service provider, but otherwise, I don't ever see a consumer user needing to change it.

The beauty of the Internet is that you can read the same document I did, for free!

I appreciate the link, but I've been blessed with a short attention span, am conditioned to expect people to spoon-feed me answers, am slightly influenced by a few millennials, and have an extremely low I.Q. But, really, the only reason I was up that late and am now up again is due to surgical pain. Additionally, I was getting timeouts (but am not currently) when visiting different pages from the link you provided. Thanks.

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.

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.

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.

@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ż?

@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.

I checked for a firmware update today when my phones weren't ringing on incoming calls through my 202. Sure enough, firmware updated to 5757. However, unlike in the past, after the system rebooted, my phones are still not ringing. Outgoing calls work fine. Anyone else having this problem?

UPDATE: Problem solved. Not firmware issue. I'm using GV and unchecked "Forward Calls to Google Chat" a few days ago, forgetting that setting needs to be enabled.

All of my Obi200 (4) and my Obi110 stopped working all of a sudden with Google Voice where the Obi couldn't connect. Also I couldn't use the Obi-to-Obi **9- got the service unavailable too.

1. I don't use ObiExtra HOWEVER strangely I see that 2 of my Obi200 were automatically updated to 3.1.1 (Build: 5463EX) while I was trying to resend configs hoping that would help. How did this happen? I did notice a yellow triangle but I have never seen it before or used it so I wasn't sure what it was.

2. The following citation says that this problem were are all having all of a sudden is related to Google xmpp security certificates having expired and Google is updating their server, apparently haphazardly, and we hit or miss updated one.