What exactly is the current status of CallCentric on an Obi device?
CoalMinerRetired:
There are so many permutations of combinations of configurations, software versions and devices that it’s a complicated question, with a moving target as an answer.
Tonight I was experimenting with the ObiTalk Portal and a new Obi110, and I noted that the CC wizard in the portal does not implement CC’s configuration per instructions on CC’s website, …. the difference is in multiple fields. I was hoping the cloud based approach would always implement the latest and greatest configuration tweaks, and would seamlessly keep things up to date.
Even more variation is out there from various combinations discussed here, discussed on DSLR, and on CC’s website, which previously (and ambiguously) said ‘if your current configuration works, don’t change it…’
To summarize the major categories of differences:
Software versions: Released, pre-release beta, and special request via Obi Support. Footnote: pre-release beta is for Obi202 only.
Configurations: From ObiTalk Portal wizard, CC’s webpage, discussions on DSLR, and various (multiple) discussions on here. That's five or six or more different variations by my count.
Until recently the DSLR discussions seemed to be the most current, while you could also argue they were a moving target. There’s a helpful CC guy on there, but he appears to be a non-official CC support person.
I wasn’t completely following the whole back and forth on using DnsSrvAutoPrefix. At first it did not stop the random reboots, then it did, now it’s no longer needed. I think.
This wasn’t intended to be a rant, unfortunately it’s almost coming off as one. And insightful comments or advice is appreciated.
VOIPisGreat:
Here is my experience:
When the DDoS first happened I changed to the SRV setting that callcentric suggested. It worked for roughly 20 days without issue. Then the storm knocked the service out completely, when the service came back, my obi started rebooting every few minutes with the exact same setting as I used before the outage. So I asked Obi support for the new firmware. With the new firmware, the obi would not reboot as frequently, but it still kept re-registering to callcentric every few minutes (to a different server ip address every time) The reboot cycle changed from every few minutes to roughly 48 hours.
Then callcentric seemed to have "fixed" their SRV record, and so far my obi has still rebooted once since that happened. This time it lasted a few more days.
I am still in search of a setting in which my obi would not reboot on its own.
CoalMinerRetired:
Quote from: jimates on November 16, 2012, 02:10:50 pm
I saw that earlier.
Anyone that is successfully using CC currently please post your configuration.
In response to Jimates post from another thread, I've got a CC free DID number running on a new Obi110. It's not my primary device, so I can afford to experiment.
It's loaded with sw version is 1.3.0 (Build: 2744). I used the Obitalk Portal to configure it, initially used the CC Wizard on the portal. At first registration was dropping frequently, several times over a ten minute period. I then looked at CC's configuration for an Obi202, and followed it exactly (no srv.callcentroic nor X_DnsSrvAutoPrefix). Had to get into expert mode to do this. I also have a GV service configured on SP2. So far the device has been up for 24 hours, and I received a few calls on it during the day today.
Twenty-four hours uptime is the best I've seen since the attacks, but I'm in 'I'll believe it when I see it mode' with this, so I'll reserve judgement until I see it up for a week or ten days.
Footnote: CC has configuration instructions for a 100 and a 202, but not a 110. Their configuration differs between a 100 and a 202 (four more fields changed in a 202 than in a 100). I chose to try the 202.
ProfTech:
I can't comment on the 202 but as far as the 100/110 go, the answer to your question may hinge on what DNS servers you are trying to use. Not sure. I use ATT dsl and I am using their standard system dns servers. My 110 also began rebooting after CC came back on line after Sandy. As VoipIsGreat reported, upgrading to 2755 helped the crashing & rebooting but it had serious problems staying registered. However, a week or so later CC made some major changes in their dns setup and now my 110 is working fine. I also administer a 100 that still has standard build 2744 and it also is working Ok. My final setup is only slightly different than pre-October settings. As long as ProxyServerRedundancy is checked, the Obi automatically uses the _sip._udp prefix and DnsSrvAutoPrefix does not need to be checked. Using ProxyServer srv.callcentric.com now produces different results than callcentric.com and srv.callcentric.com seems to work better. Use callcentric.com for UserAgentDomain. OutboundProxy and Registrar can be left blank as the Obi uses what ever is in the Proxy field. One more thing - set RegistrationPeriod to nothing less than 116. It can be greater but setting it greater will provide no benefit.
*edited* Make sure X_SecondaryRegistration is checked as well as ProxyServerRedundancy. My 110 no longer reboots unless I reboot it and registers exactly every 58 seconds [ 1/2 of 116 seconds] as Obi designed it.
jimates:
I saw the configuration settings at CC earlier today but wasn't sure how recent it was. I just configured CC using the 202 settings. Will see what happens.
Navigation
[0] Message Index
[#] Next page