Obi firmware bug
asimmons:
Ok... I have to give a shout out to the Obi support team! Once I wised up and followed the process by submitting a support request, they made it happen! They updated my Obi100 with a newer firmware and viola, it works!!!
Because CallCentric has not setup the proper infrastructure to protect themselves from a DDoS attack, they made some major changes. Once they made some of their "proxy" modifications it crippled the Obi. Again, props to Obi! As a side note, if you expect other SIP gateways (Cisco SPA112) to perform the same as Obi, learn from me, they don't. The Cisco SPA112 does NOT allow you to provision two SIP providers on one line. Major drawback. They do already have the functions to deal with CallCentrics' multiple proxy and DNS environment, (Wow, an Arbor deployment would've been simpler) but there are some trade off's!
Thanks Obi for making your product even stronger and making me a believer!
IrwinFamily:
I'll throw my hat in the ring for a fix as well. Unfortunately, as I used CC for my business, I had to drop them and go back to Cox. I feel like I went back to 1970's Ma Bell technology. The reliability is there, but the quality is no better, and none of the features. I miss CC :(
ProfTech:
I don't have any comment on the Obi 202 but since Callcentric made their last set of changes, my 110 is working fine and I also have a 100 that is stable even with the standard Build 2744 firmware. I still believe that Obi putting in the TCP code for DNS is probably the correct thing for them to do for future compatibility but it doesn't seem to be required now for use with Callcentric.
Navigation
[0] Message Index
[*] Previous page