On an Obi202, I am seeing a lot of unwanted behavior when CallCentric is up and down:
- Random reboots, including but not always when on a call.
- Odd delays in getting dial tone when I first pick up a a handset. It can take from 0 to several, five or six, seconds to hear a dial tone.
- Opening the web portal and seeing the icon Reboot Required, when I nothing was changed since last access.
I have two GV and CC numbers configured, CC for inbound calls only (GV > CC with CMAM and e911). Of course the Obi doesn't know the CC #s are used for inbound only.
When CC registration drops in and out, it affects the entire device making it unusable at times. I would have thought an unreachable voice service, any one, not just CC, would be handled gracefully by the device. The workaround to make the device usable for me is to disable and remove the two CC configurations. But that is getting old.
Any tips or insights appreciated.
Have you tried the X_NoRegNoCall setting?
No. And I cannot find that parameter in my device, or in the Admin Manual. Am I missing something?
X_NoRegNoCall setting can only be found on the OBi202 under "Voice Services=>SPX Service". This is one of the features which differentiates itself from the previous models.
Quote from: Ostracus on October 19, 2012, 12:04:47 PM
Have you tried the X_NoRegNoCall setting?
Just curious, but what does this setting do?
Thanks,
Ian
Quote from: QBZappy on October 19, 2012, 01:07:40 PM
X_NoRegNoCall setting can only be found on the OBi202 under "Voice Services=>SPX Service". This is one of the features which differentiates itself from the previous models.
Well I see it now. I tried searching for it in a browser window and didn't get a match.
I'll echo the previous poster, do we know exactly what it does?
EDIT: What does it do? Per here (http://www.obitalk.com/forum/index.php?topic=9.msg27848#msg27848), "X_NoRegNoCall, if enabled, do not allow incoming or outgoing calls on that SP service."
"X_NoRegNoCall, if enabled, do not allow incoming or outgoing calls on that SP service."
If the service is not registered, it is implied that there is no ability to make or receive a call. There must be a specific use case with which this ability would be useful, but it really is not too obvious.
I'm thinking it might be related to the recently introduced field ToneOnPrimaryServiceDown. Haven't read any documentation to indicate this, just a hunch.
I'm not a 202 owner but on the 110 if you are using CallCentric [and probably any other provider who requires registration] you still get a dial tone and are completely able to dial a number even though you are not registered. But if you dial there is a very long delay before you hear " There is no response from the service provider". I would guess on the 202 you either will not hear dial tone when you pick up the hand set, or would get a message immediately after dialing. The SPA3102 simply will not give you a dial tone if you are not registered.
CallCentric had problems over past 2 weeks due to hacking. My obi100 device was down for 2 weeks and got it working over the weekend with the help from forum:
http://www.dslreports.com/forum/r27591360-CallCentric-tech-issues-today-~start=1100
See hmishra's posting on his Obi setting for CC.
Until Callcentric officially declare success on this, I think callcentric is going to be unstable due to the ongoing hacking.
Quote from: jxzz on October 22, 2012, 01:17:36 PM
CallCentric had problems over past 2 weeks due to hacking. My obi100 device was down for 2 weeks and got it working over the weekend with the help from forum:
http://www.dslreports.com/forum/r27591360-CallCentric-tech-issues-today-~start=1100
See hmishra's posting on his Obi setting for CC.
Until Callcentric officially declare success on this, I think callcentric is going to be unstable due to the ongoing hacking.
I am aware of all this. Since posting this I've learned other people are seeing instability and random reboots also.
The issue that is worrisome for me is my 202 was unstable even when the two CC SPs were disabled. I got past that by following some of the results posted on that very thread. What I learned is successful obi configurations are a combination of 'does your DNS server return a correct UDP packet?', in combination with 'does your router re-format or otherwise handle the UDO packet gracefully?'
My Obi202 finds some combinations of the bad or truncated packets to be cause enough to reboot. At least that's mu conclusion, I now have got a working combination of of DNS servers and callcentric.com servers configured. So far my device has been up for almost three days. That is a new record over the past two weeks.
After a solid three and a half days of uninterrupted uptime, my device did a random reboot again. So I'm back to disabling the CC voice services until things stabilize or a firmware update addresses the reboot issue.
My Obi110 has gotten so bad it's rebooting every 2-3 minutes tonight. Completely unacceptable in my opinion. I have since disabled CC on my Obi110 and the device returned to 100% stable operation. WTH! ???
I have deleted CC from my devices due to reboots every few minutes.
Quote from: jimates on October 23, 2012, 09:47:27 PM
I have deleted CC from my devices due to reboots every few minutes.
And I just received my $1.50 USD billing notice.
Are you going to keep CC or look for an alternative?
I only used the free DID to get CNAM. I didn't set up 911 so I am not paying anything. They haven't posted anything new on their site. I will try it again in a few days to see if it stabilizes any.
As much as I wish CallCentric survive the ongoing DDoS attack and continue to be successful as a provider of excellent VOIP service, I was forced to submit a DID port out request just last evening to a competitor.
After all, with the intermittent outage having lasted more than 2 weeks now, I need a working phone! Oh well. So for now, I have setup SIP forwarding on my CC account to the new provider and deleted CC service from my Obi.
Well looks like I get to join the crowd. Apparently it affects my VoIP.ms account with "484 Address Incomplete" and when I look at call status during a call I get the "no resource" error. Not to mention phantom disconnects.
I tried this out from the CC website and so far it has seemed to help
OBIHAI
***OBITALK Users need to enter OBI EXPERT CONFIGURATION FOR THESE SETTINGS***
Service Providers > ITSP Profile > SIP
ProxyServer = callcentric.com
RegistrarServer = callcentric.com
UserAgentDomain = callcentric.com
OutboundProxy = callcentric.com OR srv.callcentric.com (You can use either server, please test and configure this setting accordingly)
X_ProxyServerRedundancy = Checked
That was my settings (so I can fax T.38) but still a problem.
Temporarily disable faxing through callcentric until this DoS resolves
Quote from: mick44 on October 24, 2012, 05:35:48 PM
I tried this out from the CC website and so far it has seemed to help
OBIHAI
***OBITALK Users need to enter OBI EXPERT CONFIGURATION FOR THESE SETTINGS***
Service Providers > ITSP Profile > SIP
ProxyServer = callcentric.com
RegistrarServer = callcentric.com
UserAgentDomain = callcentric.com
OutboundProxy = callcentric.com OR srv.callcentric.com (You can use either server, please test and configure this setting accordingly)
X_ProxyServerRedundancy = Checked
I changed to that configuration yesterday from the one they gave previously. I removed CC last night after seeing a reboot approximately every 3 minutes (on 2 devices)
I have put in a post about "dropped calls" on this forum. Maybe it is callcentric that is making my obi service, including my google voice service drop calls. This has been happening since yesterday afternoon and I have been using my cellphone, but I cannot do this for long. I really liked callcentric service, but I too may have to switch out of it if I cannot conduct business on the phone, which appears to be the case as of now. I reconfigured my obi as per callcentric's instruction last week. I still dont know if callcentric instability is causing this, but if that is the case, I may have to switch to another provider.
See my post at http://www.obitalk.com/forum/index.php?topic=4430.0
Turning off ProxyServerRedundancy stopped my Obi from crashing immediately.
Be sure both X_ProxyServerRedundancy and X_SecondaryRegistration have Default checked.
My tests showed that it didn't matter if I used callcentric.com or srv.callcentric.com for the Proxy as long as whatever servers you are using send the "abbreviated" list of servers. Just be sure X_DnsSrvAutoPrefix is checked to get the benefit of their new server setup. Until [and If] Obi decides to make the DNS change for TCP that has been requested, it seems redundant Servers won't work.
*EDITED* I just remembered there was a note from Obi about the 2744 firmware for the 110 - Proxy redundancy fail-over then resume improvement.. Something may have broke (or been made worse) with this Build. Haven't tried reverting to the previous build. I opened a ticket with Obi.
Random reboots may be related to the firmware bug mentioned here:
http://www.obitalk.com/forum/index.php?topic=4399.0
i too had these random reboots, and i deleted CC from my phone and now have SIP URI forwarding calls to my obi100 directly and things are great since last evening.. oh, btw i had to open up the RTP port range in my router besides the SP1 port to be able to hear the voice...
guess it's time to port out of CC as obi is not going to address this 'issue' anytime soon as i bet they'd think it's not an issue with their devices at all (the serverredundancy 'bug' that is addressed to earlier in this thread).
Is this issue also affecting people just using CallCentric as a secondary SP for E911 services?
Quote from: crackie on October 27, 2012, 07:48:51 PM
Is this issue also affecting people just using CallCentric as a secondary SP for E911 services?
Most people are having trouble just by having CC configured on their device. It is configured the same no matter what you use it for.
Quote from: crackie on October 27, 2012, 07:48:51 PM
Is this issue also affecting people just using CallCentric as a secondary SP for E911 services?
I had a CC acct which was made inactive for lack of use. It would still register to CC. The OBI202 had to be hard reset because of it. Any active registration to CC should be viewed with suspicion.
I did not have ob100 reboot. But I got quite unstable GV calling (line 1) and calls would stopped within a few minutes of talking. I suspect this was due to unstable callcentric on line 2.
For completeness, this was posted in the dslreports forum regarding this same post:
"Well, that's not an instability of Callcentric, but rather inability of Obi to properly resolve DNS queries related to Callcentric SRV records; Obi reboots itself due to [my wild guess] some memory leaks or corrupted memory buffers when it attempts to accommodate a large number of returned [by DN server] records. This thread discussed some possible workarounds a number of pages back."
Unfortunately, since (as usual) Obi is basically incommunicado when it comes to discussing bugs we won't know if they know about this, if they give a crap, and if they are doing anything about it.
Tom
FYI: I opened a support ticket last Friday morning and I got reply from support in less than 12 hours. They pushed me a beta firmware into my box (I use obitalk) and my box was stable since then. I suggested people have this problem file a support ticket (indeed, my box warranty have already expired but the response was pretty prompt) I guess their staff may not monitor the forum request.
Callcentric Users:
Please contact Obihai support to request a special version of software that provides a work-around to issues that have come-about due to recent changes in the way Callcentric operates their VoIP services.
If you would like your OBi device(s) updated with this special software, please send e-mail to Obihai tech support indicating this wish along with your OBi device's 9-digit OBi Number.
Email Address: support@obihai.com
Subject: Callcentric <OBi No.>
Thank you,
Obihai Technology, Inc.
Why is the fix not applied across the board?
I use callcentric and it seems to be working so far, is there any harm to apply the new software?
(Out of curiosity, why is my unit seems to work as is while a large number of users are having problem?)
Quote from: OBiSupport on October 29, 2012, 02:16:51 PM
Callcentric Users:
Please contact Obihai support to request a special version of software that provides a work-around to issues that have come-about due to recent changes in the way Callcentric operates their VoIP services.
If you would like your OBi device(s) updated with this special software, please send e-mail to Obihai tech support indicating this wish along with your OBi device's 9-digit OBi Number.
Email Address: support@obihai.com
Subject: Callcentric <OBi No.>
Thank you,
Obihai Technology, Inc.
OBi responded to my trouble ticket filed earlier today and told me they applied the firmware to my box minutes ago.
I'm a newbie and I'd like to report my experience with obi110 / callcentric problem. I use the CC free N.Y. number to obtain caller Id and get 911 capability per "pc44" instructions (many thanks pc44!).
Started dropping active calls randomly last Thursday. Had to go to L.A. for two days so I figured Obihai would come out with a fix since others had the same problem( thanks, forum users). Sure enough....Today, I followed the instructions to email Obihai support and ask for the work-around software. They fixed my Obi110 within an hour of my email to them...That is service!!
fred11,
Welcome.
You're such a freeloader. :D
Quote from: fred11 on October 29, 2012, 05:19:43 PM
I'm a newbie and I'd like to report my experience with obi110 / callcentric problem. I use the CC free N.Y. number to obtain caller Id and get 911 capability per "pc44" instructions (many thanks pc44!).
Started dropping active calls randomly last Thursday. Had to go to L.A. for two days so I figured Obihai would come out with a fix since others had the same problem( thanks, forum users). Sure enough....Today, I followed the instructions to email Obihai support and ask for the work-around software. They fixed my Obi110 within an hour of my email to them...That is service!!
So Fred,
is calcentric working ok on your device, if so what settings are you using.
can't even access Callcentric right now in either IE or chrome
WEBSITE AVAILABILITY CHECK FOR CALLCENTRIC.COM:
callcentric.com is down
Last updated @ 10/29/2012 18:47:01Test finished in 20.723 seconds
They posted a message on the dslreport forum that they are completely down due to power loss in NYC due to the storm. They have only short run (1 hr) UPS backup.
Tom
oh yea, I didn't think about that. We are getting pretty hard here in East Central Pa.
Quote from: fred11 on October 29, 2012, 05:19:43 PM
......That is service!!
The other view here is this is also a beta version. Based on all the issues I've seen in the past few weeks, I think I'm going to wait until all the beta testers on here put it through it's paces and a formal new release version is available.
Quote from: tome on October 29, 2012, 07:07:56 PM
They posted a message on the dslreport forum that they are completely down due to power loss in NYC due to the storm. They have only short run (1 hr) UPS backup.
Tom
They're getting 'beat up on' pretty hard on dslr for that also. A lot of people on dslr sing CC's praises, it'll be interesting to observe if that continues in light of the no power backup/no redundant infrastructure locations.
Quote from: CoalMinerRetired on October 29, 2012, 08:53:23 PM
Quote from: tome on October 29, 2012, 07:07:56 PM
They posted a message on the dslreport forum that they are completely down due to power loss in NYC due to the storm. They have only short run (1 hr) UPS backup.
Tom
They're getting 'beat up on' pretty hard on dslr for that also. A lot of people on dslr sing CC's praises, it'll be interesting to observe if that continues in light of the no power backup/no redundant infrastructure locations.
VoIP in all it's incarnations has a ways to go before it gets the 9's telecom has gotten us use to. Even cellular can't do it.
Quote from: tome on October 29, 2012, 07:07:56 PM
They posted a message on the dslreport forum that they are completely down due to power loss in NYC due to the storm. They have only short run (1 hr) UPS backup.
Tom
This and the issues over the past few weeks show that they are not reliable.