OBiTALK Community

Firmware, Software Updates => Firmware / Advisories / Notifications for OBi Products => Topic started by: IrwinFamily on February 27, 2014, 11:54:35 pm



Title: 3.0.1 (4303) Can No Longer Receive Calls
Post by: IrwinFamily on February 27, 2014, 11:54:35 pm
I just updated my OBi 202 to the latest 4303 firmware and now I can not receive calls.
Everything looks fin on the ObiTalk portal. SP1 and SP2 are both registered with different extensions on CallCentric. The CallCentric Dashboard shows all extensions registered. I can place calls At first I would get either a busy signal or ring when calling my numbers from other phones. Now they direct straight to Voice Mail. CallCentric shows all the calls received, even before they were directing to VM. It's like something in the device changed where CallCentric can no longer ring or deliver to the device. My OBi 110 is also registered with a CallCentric extension, and it still works fine.
I saw previous posts with Static/DHCP troubles after upgrading, so I changed from Static to DHCP. The IP address of the device changed, but still could not receive calls. I switched back to my static address. That part works fine, but still no receive. I use this for work obviously, and am scheduled to be on the phones in the morning. HELP!


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: QBZappy on February 28, 2014, 05:25:39 am
@IrwinFamily

Not a solution, but until you figure this out you might need to use a softphone on your computer registered directly to your voip service provider. At least you can keep working.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: DrJay on March 01, 2014, 12:00:06 pm
I had the same problem after the update today. Here's how I fixed it:

1. Deleted CallCentric from SP1 on ObiTalk.com
2. Added CallCentric account back to SP1 on ObiTalk.com
3. Cycled power on the ObiHAI 202.

Not sure if steps 1 & 2 alone, step 3 alone or a combination of all three steps did the trick but everything is back to normal.

1. Calls to my Google Voice number still forward to the OBiHAI via my CallCentric account's native number
2. Outbound calls on SP1 go through CallCentric with the outbound CID spoofed as my GV number.
3. Calls to my CallCentric number - which no one knows but me. Well and GoogleVoice  ;) - ring the phones connected to the OBiHAI.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: carl on March 01, 2014, 03:43:55 pm
will not work for me.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: Mango on March 01, 2014, 07:01:17 pm
RonR at DSLR suggests: Voice Services -> SPx Service -> X_EnforceRequestUserID : (unchecked)

Anyone who is having the problem, please test and report if this solves it.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: gderf on March 01, 2014, 07:22:50 pm
Anyone who is having the problem, please test and report if this solves it.

I can confirm that the suggestion fixes the problem.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: DrJay on March 01, 2014, 09:02:19 pm
OBiHAI Support confirms this: http://www.obitalk.com/forum/index.php?topic=7367.msg47103#msg47103


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: IrwinFamily on March 01, 2014, 09:06:10 pm
RonR at DSLR suggests: Voice Services -> SPx Service -> X_EnforceRequestUserID : (unchecked)

Anyone who is having the problem, please test and report if this solves it.

That did not work for me. I disconnected the 202 from the network, reset to default with a paperclip, removed the device from Obitalk and started fresh. After reconfiguring everything, I performed the suggested fix and still cannot receive calls. I purchased an OBI100 locally to get me through and it is working perfectly.
I like to idea of blocking the SIP Bots, but only if it WORKS. This has effectively bricked my 202. Amy other suggestions?


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: gderf on March 02, 2014, 08:17:30 am
@IrwinFamily

Have you tried downgrading to the previous firmware 3-0-1-4269?

That solved my problem.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: carl on March 02, 2014, 09:06:06 am
RonR at DSLR suggests: Voice Services -> SPx Service -> X_EnforceRequestUserID : (unchecked)

Anyone who is having the problem, please test and report if this solves it.

That did not work for me. I disconnected the 202 from the network, reset to default with a paperclip, removed the device from Obitalk and started fresh. After reconfiguring everything, I performed the suggested fix and still cannot receive calls. I purchased an OBI100 locally to get me through and it is working perfectly.
I like to idea of blocking the SIP Bots, but only if it WORKS. This has effectively bricked my 202. Amy other suggestions?

Having the same problem. Obihai is not supportive on this.  The solution they suggest will not work. Closing the thread does not help either.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: Mango on March 02, 2014, 09:09:39 am
They locked the other thread because it was a duplicate of this one.  We can still post here.

Give downgrading a try and let us know how it works.

http://www.obihai.com/firmware/OBi202-3-0-1-4269.fw


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: carl on March 02, 2014, 11:03:31 am
As reported elsewhere, the upgrade apparently messed up everything on the device, Obihai made changes in inbound call routing parameters so now i DO have incoming calls but for outbound calls the SIP providers are still dead.  The firmware downgrade was not able to change that. :(


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: DrJay on March 02, 2014, 12:39:01 pm
They locked the other thread because it was a duplicate of this one.  We can still post here.

Give downgrading a try and let us know how it works.

http://www.obihai.com/firmware/OBi202-3-0-1-4269.fw

I downgraded to .4269. All is well again.

Now if I can just ignore the yellow triangle "Firmware Update" indicator on the OBiTALK dashboard...  8)


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: chicobiker on March 02, 2014, 02:42:57 pm
(4318) update is out reverting the previous update.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: carl on March 02, 2014, 03:00:46 pm
(4318) update is out reverting the previous update.
Too late for me. My outbound calling is permanently dead.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: gderf on March 02, 2014, 03:14:53 pm
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.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: 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.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: gderf on March 02, 2014, 03:30:14 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!


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: gderf on March 02, 2014, 03:31:19 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.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: Ostracus on March 02, 2014, 03:47:54 pm
Works fine on this end, although the bulk of calls goes through the Obi110.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: MikeHObi on March 02, 2014, 03:54:11 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.

Just confirmed problem when using either Anveo or Call centric forwarding.  Note when I check the webpage to find the X_EnforceRequestUserID thing to disable, it is currently disabled, so that tells me the Obi is not obeying what it is being told regarding that flag.

sigh... obi, it's called quality control.   I wonder if they are jacking with this just to make providers scramble like GV has made Obi scramble.

Syslogs show:
Dial GV number, it fowards to CallCentric and the obi does:

SIP DLG reject: 486
RTP:Del Channel



Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: MikeHObi on March 02, 2014, 04:09:41 pm
This type of problem has me thinking Obi will be Dead to me.  Sorry folks, but your inability to follow any sort of even have standards of quality control has me wondering were the future is for the company.  Between the lack of response, and the faulty firmware seems to indicate a lack of ready for prime time behavior.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: IrwinFamily on March 02, 2014, 06:26:05 pm
They locked the other thread because it was a duplicate of this one.  We can still post here.

Give downgrading a try and let us know how it works.

http://www.obihai.com/firmware/OBi202-3-0-1-4269.fw

I see OBI released an updated firmware to resolve this issue. Sadly, it did not.  :(
HOWEVER... Downgrading the firmware DID WORK!  :D
THANK YOU Mango!!!!!


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: Mango on March 02, 2014, 06:41:18 pm
My pleasure; in fact I received the link from iamhere at the DSLR forum.  Thanks for testing the updated firmware.  I don't have an OBi202 so have just been sitting here watching the fun.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: giqcass on March 02, 2014, 09:17:47 pm
This is why I keep copies of old firmware.  I have quite a collection now.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: Obbi202 on March 02, 2014, 09:25:55 pm
I would really have appreciated an e-mail notification when you screw-up on firmware update like that....That's what I would call - taking care of your customers !!!! I did miss many important calls just because of you.....Thanks again for your good sens of business


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: giqcass on March 02, 2014, 10:10:58 pm
I would really have appreciated an e-mail notification when you screw-up on firmware update like that....That's what I would call - taking care of your customers !!!! I did miss many important calls just because of you.....Thanks again for your good sens of business
Welcome to the forum.  Please be aware most of us do not work for Obihai and Obihai rarely posts on this forum.  Most of us are customers like you that enjoy helping others.  If you have a serious issue that needs to be fixed you can open a support ticket.  I agree with you this was a pretty big error that caused a lot of grief but all companies make mistakes occasionally when it comes to software updates.  The feature they added to the last update was a highly requested feature.  It's unfortunate that it caused so many people problems.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: MikeHObi on March 03, 2014, 07:08:50 am
The feature they added to the last update was a highly requested feature.  It's unfortunate that it caused so many people problems.

#1 - and it was so highly requested that it didn't work when it was released?
#2 - Where is the roadmap for the obi products and where would this feature indicate high requests?
#3 - Where are the release notes for the firmware version where they might even indicate a possible problem with a default configuration setting they enabled.

Do they yet have a updated firmware that actually works?


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: Mango on March 03, 2014, 07:29:02 am
So far, we have seen anecdotal reports of:

1) People who had problems after updating the firmware, and had to reset/reconfigure their device to make it work.
2) People who had problems, but had to disable the new feature, even though they use a compatible service provider.
3) People who had problems, and had to downgrade, because both 1) and 2) didn't work.
4) People who reported the new feature works properly.

This diverse array of behaviour is astonishing.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: carl on March 03, 2014, 08:45:37 am
So far, we have seen anecdotal reports of:

1) People who had problems after updating the firmware, and had to reset/reconfigure their device to make it work.
2) People who had problems, but had to disable the new feature, even though they use a compatible service provider.
3) People who had problems, and had to downgrade, because both 1) and 2) didn't work.
4) People who reported the new feature works properly.

This diverse array of behaviour is astonishing.

There is an additional one: 5.Where Obihai had to make some undisclosed adjustment to the standard incoming call routing in order to make it work for incoming calls.
and a possible 6. that the device was fried after the upgrade beyond fix - something we will find out in less than 48 hours.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: Mango on March 03, 2014, 09:20:49 am
I suspect you've accidentally configured something incorrectly that's preventing you from making outgoing calls.  I'm fairly certain your hardware is still functional, and when configured correctly, things will work properly again.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: carl on March 03, 2014, 09:56:37 am
I suspect you've accidentally configured something incorrectly that's preventing you from making outgoing calls.  I'm fairly certain your hardware is still functional, and when configured correctly, things will work properly again.


I doubt that, not because of my questionable abilities but because only my Localphone digitmap is custom and I copied it exactly but because my Callcentric settings are were basic , I double checked everything from their web site and used both the digitmap from the portal and alternatively the digitmap Callcentric recomends for Obi 202.
The only thing I can do if Obihai doess not get back to me- and they are not responding- is to do a complete factory reset again and then configure , as Ron advised, the device without registering on the portal. At the danger that whatever undisclosed changes they made to the incoming call routing in order to make it work on my device goes away and I will be stuck with no service at all.
As said, we will now soon. ::)


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: gderf on March 03, 2014, 10:03:04 am
Delete your OBi from the portal.
Download a copy of the 3.0.1 (4269) firmware.
Reset your OBi to factory defaults using a paper clip.
Install the 3.0.1 (4269) firmware.
If you want your OBi on the OBiTALK portal, add it.
Reconfigure your OBi from scratch. Don't use a backed up configuration, it may be corrupted.

Until you have done the above steps, it's likely that you will not get it working properly again.

If you'd rather wait for OBihai to suggest a similar approach, feel free to do so.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: carl on March 03, 2014, 10:08:11 am
Delete your OBi from the portal.
Download a copy of the 3.0.1 (4269) firmware.
Reset your OBi to factory defaults using a paper clip.
Install the 3.0.1 (4269) firmware.
If you want your OBi on the OBiTALK portal, add it.
Reconfigure your OBi from scratch. Don't use a backed up configuration, it may be corrupted.

Until you have done the above steps, it's likely that you will not get it working properly again.

If you'd rather wait for OBihai to suggest a similar approach, feel free to do so.


I did all of the above. And as I said, The Callcentric configuration was rock bottom basic.
I will have to repeat it without the portal though once I get some more time to do it.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: CLTGreg on March 03, 2014, 10:09:11 am
The lack of release notes is flabbergasting. It's the exact opposite of how cool and modern the product is. I think they should participate in the forum too because of the one to many benefit to owners.

But surely the changes for firmware are written down somewhere. Why not share it?

In the meantime, thanks to all the early adopters. I'm not one of them but someone needs to be willing to sacrifice.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: gderf on March 03, 2014, 10:09:44 am
If you have a bad configuration on the portal it will be pushed into you OBi rendering it inoperable all over again.

Also disable automatic firmware upgrading capability.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: carl on March 03, 2014, 10:20:37 am
If you have a bad configuration on the portal it will be pushed into you OBi rendering it inoperable all over again.

Also disable automatic firmware upgrading capability.


That I was already advised to do and I changed that so it will hopefully not happen next time i do the reset. That's essentially the whole point of repeating it.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: gderf on March 03, 2014, 10:27:31 am
The factory default setting for automatic firmware updating is enabled. If you don't disable this after resetting it, the latest build will applied sooner or later. That one doesn't work for me either.

You shouldn't even expose the OBi to the internet until this is disabled.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: 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.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: carl on March 03, 2014, 10:31:33 am
The factory default setting for automatic firmware updating is enabled. If you don't disable this after resetting it, the latest build will applied sooner or later. That one doesn't work for me either.

You shouldn't even expose the OBi to the internet until this is disabled.

Thanks for the tip. I really have to check the default values on the things i disabled.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: carl on March 03, 2014, 10:34:39 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.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: obiliving on March 03, 2014, 02:00:30 pm
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



Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: Mango on March 03, 2014, 02:07:46 pm
Specifically what about the X_InboundCallRoute is incompatible?


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: gderf on March 03, 2014, 02:16:18 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 ;)


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: obi-support2 on March 03, 2014, 02:22:32 pm
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.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: chicobiker on March 03, 2014, 02:32:21 pm
Ok, I have the latest firmware update installed in my obi200 and just made a remote change to sp1 then changed it back to what I had before so my obi would recycle.  I am very remote from my obi right now and was hoping this would work vs power recycle.  Just called our obi and can report that it now rings correctly and goes to voice mail normally.  Hoping everyone's is fixed.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: gderf on March 03, 2014, 02:35:52 pm
It's fixed now.

What I am not sure about is that X_EnforceRequestUserID appears to be disabled by default, and X_InboundCallRoute is set to 'ph' only. Is this the intended configuration?


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: obi-support2 on March 03, 2014, 02:41:50 pm
X_EnforceRequestUserID is disabled by default (in 3.0.1.4318) but you can change it by yourself using the Expert Config on OBITALK if you need it.

Regarding ph or ph1,ph2, I believe this is the option you picked when used the setup wizard originally.



Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: gderf on March 03, 2014, 02:46:50 pm
Regarding ph or ph1,ph2, I believe this is the option you picked when used the setup wizard originally.

When I set my OBi up originally it was set to {>[Your Account User ID]:ph} all by itself. I never specified that.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: Mango on March 03, 2014, 03:06:31 pm
This rule {>[Your Account User ID]:ph} will no longer work

It seems like a pretty bad idea to have different versions of syntax that work with different firmware versions, especially since there was no inherent problem with the syntax before.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: gderf on March 03, 2014, 03:12:59 pm
So, if I am understanding this correctly, the protection that was available via X_InboundCallRoute -> {>[Your Account User ID]:ph} is no longer enabled by default and to get it back X_EnforceRequestUserID must be enabled?


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: QBZappy on March 03, 2014, 03:17:44 pm
This rule {>[Your Account User ID]:ph} will no longer work

It seems like a pretty bad idea to have different versions of syntax that work with different firmware versions, especially since there was no inherent problem with the syntax before.

Different not only between different firmware versions but also now different between the OBi1XX and the OBi2XX since the upgrade was only for the Obi2XX.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: gderf on March 03, 2014, 03:21:20 pm
I think it was a plot to push the Oleg method into obscurity :)


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: QBZappy on March 03, 2014, 03:38:20 pm
I think it was a plot to push the Oleg method into obscurity :)

I had exactly the same thought. This is a conspiracy to avoid any royalty payments to oleg for the one-upmanship he displayed by documenting his simple solution, when in all evidence obihai should have been providing this. The "oleg method" has been referenced so many times on this forum that he has reached mythical Guru status. His posts are few, however they have been significant.  :)


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: Tobi on March 03, 2014, 06:08:03 pm
No calls and can't use OBITALK to configure GoogleVoice this afternoon (as of 6 PM Pacific).  OBITALK reports "Service Not Configured".  The OBI 100 Admin screens for SP1 and 2 were all reset to default and the box rebooted.  Not a fix.

Ideas will be warmly received.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: gderf on March 03, 2014, 06:18:23 pm
Unsubscribe the OBi from OBiTALK,
Reset the unit to factory default with the paper clip,
Optionally downgrade the firmware to the previous working release if you can find it),
Add the OBi back into OBiTALK (if you choose to use the service),
Reconfigure the OBi.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: Tobi on March 03, 2014, 06:52:48 pm
gderf .... you've saved me from having no supper this evening, unless I make it myself.  GoogleVoice shows "connected" by OBITALK.

But, the experience has been a motivator to get handy with direct setup via the OBI 100 Admin screens.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: gderf on March 03, 2014, 06:57:40 pm
I'm glad I was able to help you. Many of us were really hosed by the recent firmware upgrade.

So, how much of what I suggested did you do?


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: carl on March 03, 2014, 08:47:16 pm
as reported elswhere, I finally got it going too. But it is interesting that somebody had problems with google voice, because that was the only thing which seemingly was not affected, at least in my case.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: SteveInWA on March 03, 2014, 08:57:14 pm
as reported elswhere, I finally got it going too. But it is interesting that somebody had problems with google voice, because that was the only thing which seemingly was not affected, at least in my case.

The Google Voice issue, whatever it might have been, was a "red herring".  Google Voice doesn't use SIP, and so it would have been unaffected by this change.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: SteveInWA on March 03, 2014, 09:05:24 pm
Guys, remember that OBiTALK can update your firmware automatically, even if Automatic Firmware Update is disabled.
...I may have to use my spare credit card and order a IP phone system and say farewell to this hassle.

SIP telephony is simply complex.  I have had an equivalent level of "hassle" trying to get ATAs from brand "C", Brand "L", and brand "G" to work.  Firmware releases sometimes fix one thing and break another thing.  Documentation ranges from incredibly obtuse to downright absent.  The target market is to telephone service providers and resellers who specialize in installing the equipment, not to average end users.  Obihai has at least done what very few other equipment providers have tried:  made a (relatively!) user-friendly web portal to try to shield the end user from the ugly complexity underneath.

I do also have a Gigaset C610A IP phone system, and its setup menus are pretty clear and easy to use.  It works great with Callcentric.  It's easy to set up an OBi box, for example, with separate CC extension numbers from the Gigaset, and thus have them all place or receive calls using the same account.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: Tobi on March 03, 2014, 09:15:45 pm
gderf, all your steps used here.  A nice little class for me.  Next, I'm trying to set up VestaLink for a test.  Something about my data input is glitchy.  VestaLink isn't registering. 

I have a feeling that it was using the VestaLink automatic OBI setup tool that killed GoogleVoice.  But, the issue was confused by the firmware update issue at the same time.  Then, someone here wrote of the unlikeliness of the firmware change messing with GoogleVoice.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: MikeHObi on March 04, 2014, 05:44:18 am
I am disappointed in Obi in that they are stating "some providers" but giving no indication to which ones that might be.  When setting up and obi SP port you get a list of providers that the wizard will then setup all the various parameters for that provider.  I would hope that a list of providers this does or does not work with from that provider list would be available.  Since that provider list is one that Obi maintains.

My experience over the weekend was that neither Callcentric or Anveo supported this.  Has that changed?


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: gderf on March 04, 2014, 06:10:19 am
You may have missed the post, but the providers that were broken weren't explicitly named. However, the difference between those that were broken and those that weren't was explained.

If you used  a rule like this X_InboundCallRoute -> {>[Your Account User ID]:ph} (AKA as the "Oleg method" to stop SIP scanners) then the contents of [Your Account User ID] was the potential culprit. This was exasperated by the fact that the OBiTALK service, if used, pushed this syntax to your OBi. If you had configured your SPs manually (didn't use OBiTALK), and didn't use the Oleg method, you were fine.

If your provider used your phone number for the contents of [Your Account User ID] then it continued to work. If your provider used anything other than your phone number there, such as 1777xxxxxxx for Callcentric, then it was broken in some circumstances.

For me, calls dialed to Callcentric DIDs failed to connect. But for calls to an IPKall DID that forwarded to the OBi provisioned Callcentric SIP URI worked. I do not understand why calling a DID failed and calling a SIP URI worked though. I'd like to have that explained.

The current status now is that OBiTalk no longer pushes {>[Your Account User ID] to your X_InboundCallRoute. Only the bare 'ph' is used. If want protection from SIP scanners, and you actually need this protection, then you have to manually enable the new X_EnforceRequestUserID feature.

I hope this clears it up for you. And if anything I said is not correct, I welcome corrections.



Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: meerkat on March 04, 2014, 10:01:50 am
A changelog post from OBI, along with firmware release will certainly help some of those who get stuck and try to trouble shooting.



Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: QBZappy on March 04, 2014, 10:41:05 am
A changelog post from OBI, along with firmware release will certainly help some of those who get stuck and try to trouble shooting.

This is the most vexing problem for consumers of the OBi product since day one. Over the course of time people have begged on bended knees, demanded forcefully, politely asked to no avail. There was a breakthrough at one time when it seems there was a genuine effort to inform of firmware changes. This was greeted with much enthusiasm. Obihai dropped it faster than a new years resolution to loose lose weight.

Everyone without exception buying an OBi product wants obihai to succeed. Why do they go out of their way to keep their customers in the dark. The client base would be more forgiving when the occasional screw up happens as evidenced by the recent firmware fiasco. What trade secrets do they think they are protecting? From my point of view it is quite the opposite that they are doing. In fact they should be shouting from the rooftops extolling the different features of their products instead of sitting at their desk reading this rant about their disconnect with their retail base.

Just today I received an email notification from Grandstream notifying of the availability of a new firmware of one of their products. These notifications come on a regular basis. If you go on their support site you will see the proper way to document and support firmware changes. FWIW these notices are comforting and a constant reminder of my Grandstream products. The marketing people at obihai should be learning from this exercise as I think a simple email notification with a change log builds brand loyalty. This effort helps the product since it will have an effect of push and pull on product interest.

Enough for one day. Now back to your previously scheduled programming!

Edited: Pardon my French


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: BigJim_McD on March 04, 2014, 01:53:43 pm
I totally agree with the comments by Meerkat and QBZappy.  At times I wonder just why many of us remain loyal customers of OBi. 

I would enjoy being able to recommend OBi devices to my friends but I can't except to the most tech savvy friends that have time to dig into this forum when they have an issue.  As for me either I'm a glutton for punishment or maybe it's because I'm a retired Wireless Telephony Integration Engineer with too much time on hand with a need to keeping finding puzzles to solve.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: Koby on March 04, 2014, 01:59:51 pm
Fortunately, I did not upgrade my firmware in the last few days and did not encounter this issue, but my question is this.  I do currently use the "Oleg method" to thwart sip scanners, and I'd like to be able to keep my firmware up-to-date.  So, what is the recommendation now?

Do I:
  • Continue to use the Oleg method because the problem has now been corrected?
  • Stop using the Oleg method and enable X_EnforceRequestUserID instead?
  • Both use the Oleg method and enable X_EnforceRequestUserID
  • Don't use either of these for the time being?
  • Avoid ever updating the firmware again? ;)

I just don't understand what actually happened and how it was fixed well enough to know what is the right thing to do now.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: MikeHObi on March 04, 2014, 02:07:35 pm
If want protection from SIP scanners, and you actually need this protection, then you have to manually enable the new X_EnforceRequestUserID feature.


One correction perhaps.  If I want protection from SIP scanners I have to not only manually enable the new X_EnforceRequestUserID  but I have to make sure the company I am working with for my SIP can work with that.

Note that OBi is the ones that threw the OLEG method on my settings as I never did it, it was just there.  The benefit to that method is that the provider of the SIP service didn't need to do anything.  From what i understand now is that if you use X_EnforceRequestUserID then the provider has to support that.

I've yet to see any updates from providers or Obi with the list of providers that support this flag they added.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: gderf on March 04, 2014, 02:10:15 pm
With the current firware, the Oleg method may either work like it used to or cause your incoming calls to fail. The problem is that what the Oleg method introduces into your  X_InboundCallRoute is no longer fully compatible with all VoIP service providers. A question for you is do you really need to use the Oleg method? Are you really vulnerable to SIP scanners?

You can stop using the Oleg method and use X_EnforceRequestUserID instead if you are vulnerable to SIP scanners. It won't hurt anything to enable it even if you are not vulnerable.

There is nothing to be gained by combining both methods.

Unless you are vulnerable to SIP scanners, there is no need to use either method. Are you vulnerable?

I would say the better thing to do now is disable automatic firmware updates, keeping in mind that it may still be possible for Obihai to push new firmware to you even if you disable that function, and only update to new firmware if it solves a specific problem you are having. The problem with this advice is that exactly what is fixed or new in any particular firmware update is either undocumented or vaguely described.

You can safely update to the latest firmware if you are subscribed to OBiTALK. OBiTALK will remove the Oleg method from your X_InboundCallRoute to prevent breakage, but you will have to manually enable X_EnforceRequestUserID if you need protection against SIP scanning.




Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: MikeHObi on March 04, 2014, 02:17:31 pm
You can safely update to the latest firmware if you are subscribed to OBiTALK. OBiTALK will remove the Oleg method from your X_InboundCallRoute to prevent breakage, but you will have to manually enable X_EnforceRequestUserID if you need protection against SIP scanning.


I highlighted above as that seems to be something that some keep saying but they leave out the fact that manually enabling X_EnforceRequestUserID is not that simple.  Because enabling that can break your ability to receive and make calls unless you make sure you are using a provider with which that flag works.  (and I'm unaware of any provider that supports this)


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: BigJim_McD on March 04, 2014, 02:21:22 pm
Koby,

I have updated my OBi202 to the new firmware version Build: 4318.  I also have X_EnforceRequestUserID enabled without any issues with either Vestalink or with voip.ms.  I use OBiTALK to manage my Obi202, Obi100 and Obi110.  I no longer use the “Oleg method”.

The OBiTALK “Generic Service Provider” option was used to configure the OBi202 for Vestalink on SP1.  Next, OBiTALK was used to configure SP3 and SP4 for “voip.ms.  OBiTALK “OBi Expert Configuration” was used to modify the configuration to enable X_EnforceRequestUserID.

The voip.ms service is used for “Failover Call Forwarding” and for “Extensions” on my old OBi100 and OBi110.  I use the older OBi devices as Lab or Test devices to check out various VoIP services.


OBiTALK - OBi Dashboard
SP1  Home Ph1 sp1 Vestalink      Registered
SP2 
SP3  Home Ph2 sp3 voip.ms Main      Registered
SP4  vOFc Ph2 sp4 voip.ms x1024   Registered


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: Koby on March 04, 2014, 02:24:26 pm
With the current firware, the Oleg method may either work like it used to or cause your incoming calls to fail. The problem is that what the Oleg method introduces into your  X_InboundCallRoute is no longer fully compatible with all VoIP service providers. A question for you is do you really need to use the Oleg method? Are you really vulnerable to SIP scanners?

You can stop using the Oleg method and use X_EnforceRequestUserID instead if you are vulnerable to SIP scanners. It won't hurt anything to enable it even if you are not vulnerable.

There is nothing to be gained by combining both methods.

Unless you are vulnerable to SIP scanners, there is no need to use either method. Are you vulnerable?

Actually I shouldn't be, since although UDP port 5060 is open in the router it is directed to an Asterisk server, not to an Obihai device.  It was mainly just a bit of extra security.

But, I know a couple of guys that have Obihai devices, more or less on my recommendation, that were having this issue, so I helped them set up the Oleg method (easier than trying to get them to change their firewalls).  But they are both running OBi110's which I understand were not affected by this?

I would say the better thing to do now is disable automatic firmware updates, keeping in mind that it may still be possible for Obihai to push new firmware to you even if you disable that function, and only update to new firmware if it solves a specific problem you are having. The problem with this advice is that exactly what is fixed or new in any particular firmware update is either undocumented or vaguely described.

You can safely update to the latest firmware if you are subscribed to OBiTALK. OBiTALK will remove the Oleg method from your X_InboundCallRoute to prevent breakage, but you will have to manually enable X_EnforceRequestUserID if you need protection against SIP scanning.

Great, that's what I wanted to know.  Thanks!


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: gderf on March 04, 2014, 02:25:42 pm
Well, the only way to find out whether your provider supports enabling X_EnforceRequestUserID is to test it yourself.

Frankly, your not being aware of any provider that supports enabling X_EnforceRequestUserID doesn't mean it that there aren't any that do support it.

Callcentric does, I've tested it, and not having any others to try that's all I can do.

Don't you think we would be seeing this forum flooded again with problem reports if enabling X_EnforceRequestUserID caused new mass breakage?

Just enable it, call your number from another phone, and see what does or does not happen.

And do you really need protection from SIP scanners in the first place? I don't, so I leave it disabled. I didn't have a choice with the Oleg method, OBiTALK pushed that into me.


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: Koby on March 04, 2014, 02:27:32 pm
Koby,

I have updated my OBi202 to the new firmware version Build: 4318.  I also have X_EnforceRequestUserID enabled without any issues with either Vestalink or with voip.ms.  I use OBiTALK to manage my Obi202, Obi100 and Obi110.  I no longer use the “Oleg method”

Thanks, good to know!


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: QBZappy on March 04, 2014, 02:52:58 pm
Koby,

I have updated my OBi202 to the new firmware version Build: 4318.  I also have X_EnforceRequestUserID enabled without any issues with either Vestalink or with voip.ms.  I use OBiTALK to manage my Obi202, Obi100 and Obi110.  I no longer use the “Oleg method”

I believe the recent changes of the firmware are to the OBi2XX models. The OBi1XX did not inherit the X_EnforceRequestUserID feature. If that is correct the "oleg method" is still relavant!


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: Ostracus on March 04, 2014, 04:16:31 pm
This is the most vexing problem for consumers of the OBi product since day one. Over the course of time people have begged on bended knees, demanded forcefully, politely asked to no avail. There was a breakthrough at one time when it seems there was a genuine effort to inform of firmware changes. This was greeted with much enthusiasm. Obihai dropped it faster than a new years resolution to loose weight.

Hey that stuff is loose enough. Don't want it to fly free and put an eye out. ;D


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: MikeHObi on March 04, 2014, 04:29:04 pm
Took the firmware on my Obi202.  Configured Google Voice to forward via Anveo.  Flipped the X_EnforceRequestUserID  to true for SP1 (GV), SP2(Callcentric) and SP3(Anveo).  Note the default appeared to be on for Callcentric and Anveo though I can't be sure if that only flipped because I forced it for SP1 (GV).  In all cases I'm using the ObiTalk expert configuration pages.

First configure GV to forward through Anveo.   Able to receive call, able to make call.
Second, configure GV to forward through Callcentric.  Able to receive call, able to make call.
Third, configure to foward via google chat.  Able to receive call, able to make call.

So I think I can say that Anveo, and Callcentric support this.



Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: QBZappy on March 04, 2014, 04:48:05 pm
Hey that stuff is loose enough. Don't want it to fly free and put an eye out. ;D

Good one!


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: Mango on March 06, 2014, 06:27:57 am
3.0.1 (4330) for OBi2 & OBi3 Series: http://fw.obihai.com/OBi202-3-0-1-4330.fw
Restored the X_InboundCallRoute behavior as in 3.0.1.4269 and prior releases.
Specifically, the problem where the rule {>[Your Account UserID]:ph} is not working with
some service providers in 3.0.1.4303 and 3.0.1.4318 has been corrected.

Excellent!


Title: Re: 3.0.1 (4303) Can No Longer Receive Calls
Post by: giqcass on March 07, 2014, 01:09:32 am
3.0.1 (4330) for OBi2 & OBi3 Series: http://fw.obihai.com/OBi202-3-0-1-4330.fw
Restored the X_InboundCallRoute behavior as in 3.0.1.4269 and prior releases.
Specifically, the problem where the rule {>[Your Account UserID]:ph} is not working with
some service providers in 3.0.1.4303 and 3.0.1.4318 has been corrected.

Excellent!

Glad they restored {>[Your Account UserID]:ph} behavior.  All upgrades were a no go for me because of that change.  I'm still going to wait for something useful before I upgrade. 3.0.1 (Build: 4142) has been nice to me.