The number you dialed, has not received a response from the service provider?
buddywiser:
Quote from: Summest on March 19, 2020, 12:45:55 am
This post was largely a waste of time, but I think whoever said to reset the password could have been onto something.
Instead of doing that I added GV to SP3 and updated the configuration to match. Voila.
I can call in and out once again and I am hardwired and have been the whole time. Let us see how long this lasts.
Curious if this was a permanent fix
buddywiser:
I think I am getting this message because of something I'm doing. I am a Obi newbie only using it for a few days. Everything worked fine with my GV number until this morning when I tried my first conference call using this setup. Out of habit, first thing I do it dial *70. This disabled call waiting on my previous provider. So now I do this and get the error sound with a different message. Hang up and try to call the number without *70 and get the message in the subject. Try to make a few more calls with same error message. Then after reconnecting to GV in the Obi settings, all is well. I can replicate this scenario and as soon as I hit *70, I can no longer make calls.
drgeoff:
Quote from: buddywiser on May 26, 2020, 09:37:44 am
I think I am getting this message because of something I'm doing. I am a Obi newbie only using it for a few days. Everything worked fine with my GV number until this morning when I tried my first conference call using this setup. Out of habit, first thing I do it dial *70. This disabled call waiting on my previous provider. So now I do this and get the error sound with a different message. Hang up and try to call the number without *70 and get the message in the subject. Try to make a few more calls with same error message. Then after reconnecting to GV in the Obi settings, all is well. I can replicate this scenario and as soon as I hit *70, I can no longer make calls.
See page 24 of the Admin Guide (download from the Documents section of this site) for full list of Star Codes. *56 and *57 are Call Waiting Enable and Disable respectively.
Jbyrne:
I just got obitalk setup and I was getting this same error. My provider is Spectrum.
I noticed if I used a pptp tunnel to purevpn I don't get this error. If i connect to my cable modem using regular dhcp I get this SIP error a lot.
My router has dd-wrt installed on it so connecting a pptp VPN to purevpn was an easy test. If you have access to a vpn try setting up obitalk through it and see what happens.
I am think there is some filtering going on with spectrum screwing up my voice traffic. If encapsulate the voice traffic in a vpn it is hidden and Spectrum leaves it alone.
Just throwing this out there as a possible solution. My calls are good now when I go through a vpn. It is kind of crazy because vpn tunnels (PPTP) are usually slow and don't work as well as a direct connection to your internet (dhcp). I was expecting the direct connection to work better.
dsm1212:
I find my obi 202 in this state from time to time and I reboot it to fix. I have no hotspot in use. Everything is hardwired and my internet connection is 100Gbps. The obi is on it's own segment of a ubiquiti router. Really everything is very clean and it still happens. Is hard to know cause and effect for sure but I have set RegistrationPeriod to 600 (5 mins) and that does seem to help. I had been seeing this weekly and now I only see this happen every month or two. Any other advice would be appreciated.
Navigation
[0] Message Index
[#] Next page
[*] Previous page