3.0.1 (4303) Can No Longer Receive Calls
carl:
Quote from: Mango on March 03, 2014, 10:30:50 am
Guys, remember that OBiTALK can update your firmware automatically, even if Automatic Firmware Update is disabled.
You are right. But if they do it this time forcibly with the garbage they created I may have to use my spare credit card and order a IP phone system and say farewell to this hassle.
obiliving:
Dear Customers,
We apologize for the recent problems with respect to the latest f/w release.
There are multiple problems. One is related to the new option X_EnforceRequestUserID which turns out to be benign in most cases. The other one is due to the OBiTALK setup wizard that has generated an old X_InboundCallRoute that is incompatible with the new f/w behavior. We have just fixed the OBiTALK setup wizard.
If your device is still under OBiTALK management, you can simply power-cycle your device once so that our setup wizard can re-generate the proper X_InboundCallRoute to install on your device momentarily.
If you need further assistance, please email us at support@obihai.com.
We appreciate your support of the OBi products.
Obihai Support
Mango:
Specifically what about the X_InboundCallRoute is incompatible?
gderf:
Quote from: Mango on March 03, 2014, 02:07:46 pm
Specifically what about the X_InboundCallRoute is incompatible?
It looked OK to me. It was the very first thing I checked when I got upgraped ;)
obi-support2:
This rule {>[Your Account User ID]:ph} will no longer work (with some service providers) with the new f/w.
If you have this and you experience incoming call problems after f/w update, try replacing that with just {ph}, {ph2}, or {ph,ph2} yourself if you are managing the device yourself. Otherwise, our device management server will take care of that fix.
Navigation
[0] Message Index
[#] Next page
[*] Previous page