3.0.1 (4303) Can No Longer Receive Calls
MikeHObi:
Quote from: gderf on March 04, 2014, 02:10:15 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)
BigJim_McD:
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
Koby:
Quote from: 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?
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?
Quote from: gderf on March 04, 2014, 02:10:15 pm
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!
gderf:
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.
Koby:
Quote from: 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”
Thanks, good to know!
Navigation
[0] Message Index
[#] Next page
[*] Previous page