3.0.1 (4303) Can No Longer Receive Calls
QBZappy:
Quote from: 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.
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
BigJim_McD:
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.
Koby:
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_EnforceRequestUserIDDon'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.
MikeHObi:
Quote from: gderf on March 04, 2014, 06:10:19 am
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.
gderf:
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.
Navigation
[0] Message Index
[#] Next page
[*] Previous page