Started by markosjal, November 01, 2021, 01:22:00 PM
Quote from: markosjal on November 01, 2021, 01:22:00 PMStep 2 (symptom of bug)Now immediately hang up and dial any number you know to be VALID. What do you hear? I get "(SIT Tone) The number you dialed did not receive a response from the service provider..." . When in fact you should have dialed a VALID number that rings through but in order to connect to a Valid number now you will need to give the Obi200 a refractory period of a few minutes.
Quote from: markosjal on November 02, 2021, 02:05:00 PMTaoman is that with Google Voice?
Quote from: markosjal on November 02, 2021, 02:05:00 PMThis is a test with GOOGLE VOICE, not with another provide. SteveInWA trying with a different provider invalidates it. Your opinion of what I "should" or "should not" use is irrelevant to the test or reproducing the bug.Taoman is that with Google Voice?
Quote from: Lavarock7 on December 27, 2021, 01:33:56 PMAlso remember that these suggestions come from community members not from OBI, Polycom nor Google. True many of the members here have very solid backgrounds with the products and services.I have told people to look at the issues people have in the forums and see that many have to do with interfacing to Google Voice.I personally tell people that the free GV service is great to play with but I do not rely upon it for things which are important.I tell them to remember the old joke "Doctor, it hurts when I do this" to which the reply is "Well, don't do that!"Your mileage *may* differ.
Quote from: rob613 on January 10, 2022, 08:23:17 PMI have been getting this bad behavior on an Obi202 as well.I discovered today that when the GV line on my SP1 gets into this behavior, even calls going out an actual SIP connection to a VoIP provider other than GV also gets only the intercept recording with numeric error codes after a bunch of babble.The only thing I can do to clear it is to reboot the Obi device, and then after a while, try calling again.I was trying to reach someone this evening who had a bunch of phone numbers listed.Several of them are old numbers that have been disconnected, and calling through to them had a strong probability of putting the Obi into this bad mode, in need of a reboot.