What exactly is the current status of CallCentric on an Obi device?
lacibaci:
This is the configuration I've been using for a couple of weeks (OBi100)
ProxyServer callcentric.com
RegistrarServer callcentric.com
UserAgentDomain callcentric.com
OutboundProxy callcentric.com
X_ProxyServerRedundancy yes
X_SecondaryRegistration yes
X_DnsSrvAutoPrefix yes
X_KeepAliveEnable yes
X_KeepAliveExpires 120
VOIPisGreat:
Quote from: ProfTech on November 16, 2012, 07:50:31 pm
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.
Thank you! I have tried many different settings and I still haven't quite get it to my satisfaction. I'll try your setting. If you have any further changes or fine tuning please let us know.
ProfTech:
Please note. If you are using DHCP to get an IP address from your router and the IP address for the Obi changes [which it can do], the Obi is designed to reboot. This is one reason to use a static IP address in the OBi. I think these types of devices are supposed to perform more reliably with a static IP anyway. Unfortunately, the procedure for setting a static IP varies from router to router.
CoalMinerRetired:
Quote from: ProfTech on November 17, 2012, 02:17:12 pm
Please note. If you are using DHCP to get an IP address from your router and the IP address for the Obi changes [which it can do], the Obi is designed to reboot. This is one reason to use a static IP address in the OBi. I think these types of devices are supposed to perform more reliably with a static IP anyway. Unfortunately, the procedure for setting a static IP varies from router to router.
I'm curious about that bolded statement. For the record, that is not anywhere in the device admin guide, so I'm wondering why you say it is designed to behave this way? It is regularly mentioned in the admin guide that using a dynamic IP address is routine -- for example the first if the four LED lights flashes green when it is searching for an IP address from a DHCP source. So I would have expected they'd warn you about this.
On another topic, with the config I mentioned above my Obi110 has now been up for three full days with a CC configuration.
ProfTech:
This has been mentioned "off the cuff" in the forum. I'm sure the default is DHCP because that is simplest for most people. Just plug it in. I'm not sure why Obi would have designed it to reboot if the IP changes unless it has something to do with routing. Anyway, check reboot reason codes 12 and 13 in the admin guide. 12 is "Reboot after DHCP server offers IP, GW-IP and/or Netmask different from what the OBi device is currently using" and 13 [related] "Reboot on Data Networking Link Re-establishment". I have tested and if you unplug the ethernet cable from the Obi and plug it back in the Obi reboots also. This seems to be why some people with certain routers have had issues. The Obi comes from the factory set for 10 mb / half duplex and some routers don't like it so their ethernet port goes crazy and the Obi reboots or in some cases the router seems to go nuts. Changing the port setting on the Obi to 100 / full duplex usually corrects that issue. 100 / full is the "modern" standard.
Navigation
[0] Message Index
[#] Next page
[*] Previous page