Beware with firmware 2824 for OBi1xx
habibie:
I have an OBi-110 device and it was working fine with firmware 2774 to bridge VoIP/PSTN calls with and/or without the Obi Auto Attendant (aa). In other words, callers from PSTN or VoIP had no problem to reach callees on the VoIP or PSTN site, respectively, with and/or without the aa.
Recently, I made a wrong decision to upgrade the OBi-110 device with the latest firmware 2824. Upon the upgrade, I noticed the Obi110 device gives the following problems:
[*]Firmware downgrade is no longer possible as others have reported here. The process to downgrade the firmware ends up with this error message: Firmware downgrading is prohibited.
[*]Firmware upgrade (reflash) is also not possible and the process returns with this error message: Previous version identical to the update. Firmware not modified.
[*]When SP1 Service::X_InboundCallRoute (this also applies to SP2) is set to default (ph), incoming and outgoing calls work OK. When SP1 Service::X_InboundCallRoute is set to aa, incoming VoIP call has no problem to complete on the Phone port when option #1 is selected. However, when a VoIP callee selects option #2, aa accepts the option and the call goes dead after aa announces Please wait while your call is being connected. The Status Call shows Number of Active Calls: 2 and Call History indicates the call from VoIP to PSTN was placed after the call was terminated by the OBi110 device within 30 seconds of the # key pressed.
[*]When LINE Port::InboundCallRoute is set to default, the Phone port rings when there is an incoming call from PSTN port. Upon picking up the telephone handset, the call goes dead while the caller still hears the call is still in progress (ringing). When LINE Port::InboundCallRoute is set to aa and the caller selected option #2 when prompted by aa, the Phone port won't ring and the PSTN caller keeps hearing as if the call is still in progress (ringing). The Status Call shows Number of Active Calls: 0.
[/list]
At this point, I am clueless but thought perhaps reflash the same new firmware would fix the problem. A las, all I encounter is as shown on item #2 above. :( Without being able to downgrade and/or reflash with the same firmware, I am left with an unusable OBi110 device due to problems I encountered in firmware 2824. I am hoping OBiHai will come up with a better firmware to fix this issue.
drgeoff:
Quote from: habibie on January 15, 2014, 07:29:08 am
[*]When LINE Port::InboundCallRoute is set to default, the Phone port rings when there is an incoming call from PSTN port. Upon picking up the telephone handset, the call goes dead while the caller still hears the call is still in progress (ringing).
I cannot make reliable comments on the veracity of your other claims but I can say that the one I quote above does not apply to my OBi110 running firmware 2824. Admittedly it does not have the InboundCallRoute set to default but rather:
{(Mbl):},{ph}
where Mbl is a user digit map containing a short list of blocked phone numbers.
ianobi:
There have been a few complaints on this forum since the upgrade to 2824, but very few considering it's been around for at least four months now.
I tried to reproduce your problems, but all seems ok here. I am running two OBi110s with this setup:
HardwareVersion 2.8
SoftwareVersion 1.3.0 (Build: 2824)
I wonder if during your upgrade some data got corrupted. It may be worth trying a factory reset as detailed here:
http://www.obihai.com/faq/Troubleshooting-sec/How-to-Factory-Reset
Note any important configuration details before you start. You will have to re-add your device and input user details and passwords after the factory reset.
habibie:
Quote from: drgeoff on January 15, 2014, 07:48:52 am
Quote from: habibie on January 15, 2014, 07:29:08 am
[*]When LINE Port::InboundCallRoute is set to default, the Phone port rings when there is an incoming call from PSTN port. Upon picking up the telephone handset, the call goes dead while the caller still hears the call is still in progress (ringing).
I cannot make reliable comments on the veracity of your other claims but I can say that the one I quote above does not apply to my OBi110 running firmware 2824. Admittedly it does not have the InboundCallRoute set to default but rather:
{(Mbl):},{ph}
where Mbl is a user digit map containing a short list of blocked phone numbers.
Unfortunately, the PSTN doesn't have a CID capability. So, I believe adding {(Mbl):} will not do any good.
habibie:
Quote from: ianobi on January 15, 2014, 07:56:35 am
There have been a few complaints on this forum since the upgrade to 2824, but very few considering it's been around for at least four months now.
That's good to know. However, if the problems still linger, then OBiHai failed to address the issues.
Quote
I tried to reproduce your problems, but all seems ok here. I am running two OBi110s with this setup:
HardwareVersion 2.8
SoftwareVersion 1.3.0 (Build: 2824)
Same hardware and software.
Quote
I wonder if during your upgrade some data got corrupted. It may be worth trying a factory reset as detailed here:
http://www.obihai.com/faq/Troubleshooting-sec/How-to-Factory-Reset
Note any important configuration details before you start. You will have to re-add your device and input user details and passwords after the factory reset.
I had done two different factory resets with the same results: The problems still persist, unfortunately. After the resets, even manually reconfigured the device and the problems still exist. :(
[/quote]
Navigation
[0] Message Index
[#] Next page