OBi202 keeps losing SIP registration with Anveo
Shplad:
After I finally got Anveo working with my OBi202, I keep losing
registration. I can't find any pattern to it.
This is after using Obitalk's own automated config routine for
Anveo.
I'm running a script on my router to check for packet loss, but I'm
not very Linux savvy at all and have zero understanding of scripts, so I
don't know how much/often it's sampling or what it will tell me.
I've recreated the Obitalk profile and contacted Anveo several times.
It isn't helping. Anveo keeps blaming Obihai. Any suggestions?
Can anyone suggest anything
Taoman:
You had problems with Voip.ms and now you're having problems with Anveo. Since you're an "ex-IT tech" have you considered looking at your own network/router config to see if that's where the problem is? Like temporarily putting your OBi in your router's DMZ to see if you still lose registration, for instance.
I would suggest downloading a free softphone and configure it for Anveo and let the softphone sit for awhile registered to Anveo and see if you lose registration or not.
What is the error message you see on the OBi status page when you lose registration to Anveo? It has to be saying something like "retrying" or a SIP error code or something.
Since you have a paid Anveo account you can use TCP as your transport protocol. Sometimes using TCP can make things more stable since it is a connection-oriented protocol. Change it here:
Service Providers-->ITSP Profile X-->SIP-->ProxyServerTransport
Shplad:
Quote from: Taoman on October 17, 2021, 07:04:14 pm
You had problems with Voip.ms and now you're having problems with Anveo. Since you're an "ex-IT tech" have you considered looking at your own network/router config to see if that's where the problem is? Like temporarily putting your OBi in your router's DMZ to see if you still lose registration, for instance.
I would suggest downloading a free softphone and configure it for Anveo and let the softphone sit for awhile registered to Anveo and see if you lose registration or not.
What is the error message you see on the OBi status page when you lose registration to Anveo? It has to be saying something like "retrying" or a SIP error code or something.
Since you have a paid Anveo account you can use TCP as your transport protocol. Sometimes using TCP can make things more stable since it is a connection-oriented protocol. Change it here:
Service Providers-->ITSP Profile X-->SIP-->ProxyServerTransport
I had call quality problems with Voip.ms, not connectivity/registration issues. The latter only happened recently because Voip.ms has been undergoing a DDoS attack. Those SIP registration issues with Voip.ms are now pretty much back to normal.
On the same network, I'm also using Anveo through my Bria Softlclient, and I don't seem to be having the same registration problems with that. That's why I'm leaning towards the OBi/OBi config. maybe being the problem.
I hadn't thought about putting it in the DMZ, but a while back, I had it hanging directly off the gateway and it still showed the same problems. I may try it, but it will be soem work and I'm down with a flu/virus right now.
Yes, I've looked at my network. The only thing that stands out is a few lost packets, but no one seems to be able to tell me what amount of lost packets might cause (or even if it will cause) this type of problem.
I have a script running on my router I grabbed to check for and log lost packets, but I'm not seeing a lot of them and I don't understand Bash scripts, so I don't know how often this script is "sampling" or checking or whatever the right term might be for that.
I supposed I could try using TCP. Wouldn't it be unusual though to have to use TCP just to maintain SIP registration?
Taoman:
Quote from: Shplad on October 18, 2021, 02:10:52 pm
Wouldn't it be unusual though to have to use TCP just to maintain SIP registration?
Yes.
Don't know what to tell ya. I've configured Anveo on multiple OBi devices without issue.
You can try enabling X_KeepAliveEnable under Voice Services.
You still haven't provided the error message seen on the status page when you lose registration.
So you have Voip.ms working on your OBi now?
Shplad:
The error message in Obitalk Dashboard is: Register Failed: No Response From Server
I tried putting the OBi in my router's DMZ. It didn't help.
Yes, Voip.ms is working on my OBI again minus intermittent
call quality issues, but no SIP registration problems.
I checked the Voice Services section and the X_KeepAlive setting
for Anveo was already enabled.
Should I try changing the value in the one of the following fields?
Would that help?
I got another DSL gateway, so I'll try that too, but during off-hours.
Navigation
[0] Message Index
[#] Next page