VOIP Stuck and Registration Failed - Asuswrt-Merlin 384.14.

[miazza]

Hello to everybody.

Since some time I have an issue where my Vodafone VOIP account fails to connect after few days of proper work (I use a Siemems VOIP Gigaset station).
The only way I have in order to get proper registartion is to switch off the router and power it back after a few seconds (simple reboot does not work).

Another way to unlock the situation, seems to disable Diversion from amtm; in this case a simple reboot seems to unlock the issue.

Is anyone affected by a similar issue ?

I guess Diversion might need to be configured with some exceptions for the VOIP registration.

 

[CaptnDanLKW]

Hello to everybody.

Since some time I have an issue where my Vodafone VOIP account fails to connect after few days of proper work (I use a Siemems VOIP Gigaset station).
The only way I have in order to get proper registartion is to switch off the router and power it back after a few seconds (simple reboot does not work).

Another way to unlock the situation, seems to disable Diversion from amtm; in this case a simple reboot seems to unlock the issue.

Is anyone affected by a similar issue ?

I guess Diversion might need to be configured with some exceptions for the VOIP registration.

As a Vonage user for > 10 years (with the same VDV21 V-Portal adapter) I had something similar happen.

Over the past few months I've switched from a RT-AC68U to the newer RT-AC86U, at that time i also updated from 384.12 to .13 (and subsequently .14) and had 4 instances of VOIP issues. I don't know if the cause was something introduced in version > .13 or the new hardware - or a combination. Or it could be completely unrelated. I don't run any additional scripts, have QOS turned off and the SIP setting is Helper + NAT as it's been since running merlin on my old N66U back from the .374 days.

The 4 times problems occurred happened time when my ISP offered a "free speed upgrade Weekend" to my DOCSIS 3.1 service - using an Arris 8200 modem-only device. When they sent down the new CM profile and the command that resulted in the "Resetting the cable modem due to docsDevResetNow" event, after the Cable Modem finished rebooting, Vonage stopped working. ONLY my VOIP Service - everything else was fine. The VDV21 adapter will play a message that says "Please check your Internet connection" message when you pick up the handset and it cannot connect to the Internet. In this case it says "Your adapter cannot register on the Vonage network" - clearly a different message which indicates to me there's something wrong with making the UDP SIP connection over port 10000.

(Screenshot when it working)

I did a lot of troubleshooting (wan down/up scripts, disable/enable nat, disable/enable SIP helper, etc) before I threw in the towel and just rebooted the router.

I did consider the fact that I got a new IP address from my ISP each time, but that alone was not the issue since I've powered off the CM many time, waited, and its come back with a a new IP address and the issue did not happen.

So, a lot of information here but no solution. Maybe this will help in someway.

 

[Vexira]

Try Mac cloning an isp unit, see if that works also reboot the router and the VoIP device.

 

[miazza]

Try Mac cloning an isp unit, see if that works also reboot the router and the VoIP device.

I have tried to clone the MAC of the Vodafone Station Revolution but this seems not to help.
The reboot of the only Gigaset VOIP Station is not solving the problem.

As said, the last time after some power off cycles I disabled Diversion and made a hot reboot. This solved and since that moment VOIP is OK (one week now).

When I use the ISP router (VSR) with built in VOIP routing on different VLAN provided by ISP , the VOIP connection is very much stable ...

 

[Vexira]

Sounds like diversion is blocking some domains use for authentication by Voda phone, if you have access to a virtual machine you could install linux and pi hole point the phone at the VM for DNS and see where it phones home to, if there is not already a list of domains being used by the device already.

 

[miazza]

Sounds like diversion is blocking some domains use for authentication by Voda phone, if you have access to a virtual machine you could install linux and pi hole point the phone at the VM for DNS and see where it phones home to, if there is not already a list of domains being used by the device already.

This is a good suggestion and I will try even if I'm not much Linux familiar.
The tricky point is that if I enable Diversion after that the registration is done, the VOIP connection remains up for few days.
After that registration fails and again I need to disable Diversion and reboot.

 

[Vexira]

I'd also give ago settings the reboot schedule and see if that helps.

 

[miazza]

I'd also give ago settings the reboot schedule and see if that helps.

This has been my first try. Reboot Schedule function is not very much reliable: sometimes it does not reboot, sometimes the router remains OFF with no reboot and need to be power cycle.

 

[Vexira]

Oh that sounds like the issue with the 86u I've been hearing about.

 

[dosborne]

I know people swear by it, but i found running diversion caused memory to eventually run out. Now i run as little as possible on the router itself to ensure stability and offload anything i can to other systems.

 

[dev_null]

I'm running VOIP from 5 providers, including SMS from AnveoDirect, without issues using Diversion. That being said, it is entirely possible that Vodaphone is different.

As stated above, first try disabling the SIP helper (or enabling if disabled).

If that doesn't help, you could wait for another non-registration occurrence and open Diversion and monitor the log entries to see what IP or domain is being blocked. Generally you are looking at port 5060-5080 so watch for these. Then whitelist them.

Alternatively (and this is what I need to do with AnveoDirect) you could port forward the ports that Vodaphone uses to your device. But don't forward from all IP addresses: ask for or find the specific service IPs that Vodaphone uses and forward only those (for example, AnveoDirect has 4-5 IPs that they use, so I have forwarded those to my PBX. Or you could first whitelist these IPs to see if that's enough.

(I've never had Diversion lead to a low-memory situation, except temporarily during stats generation. I edit the cron job to run stats every 6 hours rather than more frequently, and I have a 1GB swap which probably also helps.)