Callcentric issues
A_Friend:
Quote from: Johnny on October 28, 2012, 09:23:35 am
So, if OBI doesn't come up with a fix for this bug I will probably port my CC number to Voip.ms.
There's no need to port out, or at least yet. So far, DID Forwarding from CC has been working pretty well. (Preferences/DID Forwarding, that is. Use that over Call Treatments, which has been a little flaky, on and off.) I use and like voip.ms, so I'm not going to say anything against it, but for a temporary solution, you might also want to check out CallWithUs (others recommended it, I haven't used them), which has a much lower initial prefunding level. For a more permanent residential solution, at least voip.ms can sell you e911 service, whereas CallWithUs doesn't even offer it.
You could forward your Callcentric DID right now to your GoogleVoice account, but you'll have to pay for every incoming minute as an outgoing call by Callcentric. If you use a voip.ms or CallWithUs (or many other) SIP URI as a forwarding address, it's free (on both ends) and you don't need a DID from them. CallWithUs is more straightforward to set up, if I read their FAQ right. With voip.ms, if you want a free URI to forward to, you have to configure a subaccount, choose an internal extension number, use the credentials for that on your OBi110, and use your main account number plus the user-added part of the extension as part of your URI. So, it's a little more complicated and potentially confusing. Read up on subaccounts on their site for more info.
I'm currently paying voip.ms for a "virtual DID" to use with a Ring Group because they don't treat the subaccount-URI as a DID for that purpose and I don't trust Callcentric's Call Treatments right now, but as long as you don't need simultaneous ring or other special handling, a simple SIP URI forward is free (although with voip.ms you might have to pony up the $25 initial deposit to make things work).
I'm of the opinion that OBihai will eventually patch up the firmware to stop the rebooting problem, and also that Callcentric will stabilize their SIP SBCs and stop the attacks from working. Actually porting your number out will take a few weeks, anyway, so if you can find a passable workaround in the meantime, you might want to save the cost of porting out and just leave the DID with Callcentric until things either get fixed or get officially certified as hopeless.
Johnny:
Quote from: A_Friend on October 28, 2012, 10:28:39 pm
Quote from: Johnny on October 28, 2012, 09:23:35 am
So, if OBI doesn't come up with a fix for this bug I will probably port my CC number to Voip.ms.
There's no need to port out, or at least yet. So far, DID Forwarding from CC has been working pretty well. (Preferences/DID Forwarding, that is. Use that over Call Treatments, which has been a little flaky, on and off.) I use and like voip.ms, so I'm not going to say anything against it, but for a temporary solution, you might also want to check out CallWithUs (others recommended it, I haven't used them), which has a much lower initial prefunding level. For a more permanent residential solution, at least voip.ms can sell you e911 service, whereas CallWithUs doesn't even offer it.
You could forward your Callcentric DID right now to your GoogleVoice account, but you'll have to pay for every incoming minute as an outgoing call by Callcentric. If you use a voip.ms or CallWithUs (or many other) SIP URI as a forwarding address, it's free (on both ends) and you don't need a DID from them. CallWithUs is more straightforward to set up, if I read their FAQ right. With voip.ms, if you want a free URI to forward to, you have to configure a subaccount, choose an internal extension number, use the credentials for that on your OBi110, and use your main account number plus the user-added part of the extension as part of your URI. So, it's a little more complicated and potentially confusing. Read up on subaccounts on their site for more info.
I'm currently paying voip.ms for a "virtual DID" to use with a Ring Group because they don't treat the subaccount-URI as a DID for that purpose and I don't trust Callcentric's Call Treatments right now, but as long as you don't need simultaneous ring or other special handling, a simple SIP URI forward is free (although with voip.ms you might have to pony up the $25 initial deposit to make things work).
I'm of the opinion that OBihai will eventually patch up the firmware to stop the rebooting problem, and also that Callcentric will stabilize their SIP SBCs and stop the attacks from working. Actually porting your number out will take a few weeks, anyway, so if you can find a passable workaround in the meantime, you might want to save the cost of porting out and just leave the DID with Callcentric until things either get fixed or get officially certified as hopeless.
A_Friend,
Thanks so much for taking the time to post that helpful information.
I really like the OBI 110 and want to stick with it, so I may do as you advised and wait a little longer before porting out.
I just wish someone from OBIhai would let us know what's going on.
Thanks
Judgeless:
I am having more issues with Callcentric. I had everything working for 2 days and now it is broke again. I went to their website. http://www.callcentric.com/ and the domain no longer works.
Did they go out of business? If not how can they stay around without redundancy and power backup?
Billt928:
Quote from: Judgeless on October 30, 2012, 06:43:30 am
I am having more issues with Callcentric. I had everything working for 2 days and now it is broke again. I went to their website. http://www.callcentric.com/ and the domain no longer works.
Did they go out of business? If not how can they stay around without redundancy and power backup?
I'm in the web hosting business for 12 years now. I'm the owner and have about 50 servers that I own and have a backup plan. I'm in Florida and have planned for these instances. I even use multiple data centers for redundant core services in a fail-over situation. Not only do the data centers I use have redundant power grids, they have redundant generators with 14 days of fuel. and the APC system is rated to carry the entire Data center for 24 at full load.
I used callcentric as a primary provider and VOIP.MS as a fail over, but that does not even work now because callcentric could net even keep up the core services that other providers in the same area seem to have done.
I do think that if Callcentric manages to get back on line and maybe still have a customer base to explain why they had no backup plan for a extended power outage. its inexcusable that they said they only had 1 hour of APC backup.
I for one think some heads may need to roll if they plan on staying in business to show customers and any possible future customers that they are serious about being a VOIP provider and will not allow this to happen again, because the head engineer they have now failed to plan for the biggest threat to a data center or VOIP provider. A POWER OUTTAGE. They also failed to notify the customers of this planned shutdown. and I do not accept the tweet as notice or post on dslreports. They knew the storm was coming for days and failed across the board other than shut it all down and go home. This screw the customer attitude will most likely put them down for the long term. We have been hearing excuse after excuse on why its taken so long to mitigate the DDoS attack that been an issue for 26 days now. there mitigation steps have rendered most ISP's dns servers useless and required countless hours and days constantly changing there recommended setups
The billing system has been working well for them though. I got billed for full months of service and no credits as they stated over a week ago that they would be doing.
Judgeless:
There customers are not happy on the twitter feed.
http://twitter.com/Callcentric/status/263106841368752128
I am done with is company. What is the best company to port my number to? Cheap and relaible.
Navigation
[0] Message Index
[#] Next page
[*] Previous page