What exactly is the current status of CallCentric on an Obi device?
VOIPisGreat:
Quote from: VOIPisGreat on November 17, 2012, 01:36:37 pm
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.
My Obi finally has been running for over 7 days for the first time since the CC outage. Thanks for all your help!
CoalMinerRetired:
Quote from: ProfTech on November 16, 2012, 07:50:31 pm
.....
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.
I'm guessing you are seeing the effect of this rule/algorithm, from pps. 87 & 88 of the DeviceAdmin manual:
Quote
DNS Lookup of SIP Servers
When sending out SIP requests to the server, the device looks up the IP address of the server using standard DNS query if the server is specified as a domain name instead of an IP address. If Outbound Proxy Server is configured, it is used instead of the SIP Proxy Server or SIP Registration Server. The resolution of the server domain name into IP address is performed in the following manner:
- Try looking up the name as DNS A Record. If not found.
- Try looking up the name as DNS SRV Record. If not found.
- Try looking up the name as DNS SRV Record with "_sip._udp." prepended to the hostname. If not found, fail the request.
If the result from the DNS query is a SRV record, the server port is taken from that record also (the server port value configured on the device is ignored). Otherwise, the server port is taken from the configured value or use 5060 if none specified.
A verification would be to change your local configured value for server port and see if the rule in the second to last sentence is being invoked. Or watch things in ethereal/wireshark.
VOIPisGreat:
Quote from: VOIPisGreat on November 24, 2012, 06:22:08 pm
Quote from: VOIPisGreat on November 17, 2012, 01:36:37 pm
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.
My Obi finally has been running for over 7 days for the first time since the CC outage. Thanks for all your help!
My Obi finally rebooted itself last night after a call made from a voice gateway. Not sure if it's related to that gateway or it's just a coincidence. Does anyone have a theory about why it could have happened? Could it be a compatibility issue between the sp (callcentric) and the gateway (voip.ms)? The call was made successfully tho.
MikeHObi:
My obi 202 has been up for 19 days which is when the CallCentric Free NY DID's came back on line and I re-enabled CallCentric.
The only non Default setting I currently have configured for Call Centric is x_DnsSrvAutoPrefix which is checked on.
I stopped touching stuff when it started working. I assume at some point the Obi Defaults will get reset to what will work reliably with Call Centric and I'll revert to the defaults again.
My obi is hardware version 1.3 and software version 3.0.0 (Build 3460)
Navigation
[0] Message Index
[*] Previous page