3.0.1 (4303) Can No Longer Receive Calls
gderf:
I doubt it is permanently dead. Try deleting your OBi from OBiTALK. Then reset it to the factory defaults. Then downgrade the firmware. Then reconfigure it from scratch.
MikeHObi:
upgraded my 202. Working fine for incoming and outgoing. Is currently using GV for both the incoming and outgoing due to the GV issues with fowarding through providers like Anveo and Callcentric.
gderf:
Quote from: chicobiker on March 02, 2014, 02:42:57 pm
(4318) update is out reverting the previous update.
There is more to this than reverting to the previous configuration of X_EnforceRequestUserID.
I was able to get my OBi working again by reverting from 3.0.1 (4303) back to 3.0.1 (4269).
But when I upgrade to the latest 3.0.1 (4318) my OBi is broken once again.
The only thing I did to fix it again was to downgrade back to 3.0.1 (4269).
Are the OBihai folks reading this post? If so please explain this to us!
gderf:
Quote from: MikeHObi on March 02, 2014, 03:29:55 pm
upgraded my 202. Working fine for incoming and outgoing. Is currently using GV for both the incoming and outgoing due to the GV issues with fowarding through providers like Anveo and Callcentric.
There was never a firmware problem with GV for outgoing or incoming.
Ostracus:
Works fine on this end, although the bulk of calls goes through the Obi110.
Navigation
[0] Message Index
[#] Next page
[*] Previous page