Vigor2820n 3.3.4 firmware upgrade also breaks SIP registrations

A few days after writing my last post about problems after upgrading my ADSL router’s firmware I also noticed that my VoIP connections were not working properly. I have several SIP providers and after a day or so of using the new firmware the SIP registrations to my providers started failing.  Initially I thought this was caused by my ISP as not all registrations seemed to be affected. I have not changed my Asterisk configuration in some time and did not associate the problem with the change in router firmware as everything else seemed to work fine.

The asterisk logging showed:

[Oct 15 02:12:04] NOTICE[3329] chan_sip.c:    -- Registration for '....@xxxxxxxxxx.com' timed out, trying again (Attempt #5)
[Oct 15 02:12:24] NOTICE[3329] chan_sip.c:    -- Registration for '....@xxxxxxxxxx.com' timed out, trying again (Attempt #6)
[Oct 15 02:12:44] NOTICE[3329] chan_sip.c:    -- Registration for '....@xxxxxxxxxx.com' timed out, trying again (Attempt #7)

A router reboot fixes the problem but it does come back again. Rebooting a router on a daily basis is not something I really want to do or think should be necessary.

I’ve reported the problem to Draytek support so will see what they say. In the meantime I see they’ve posted a 3.3.4.1 version of the firmware so perhaps this is one of a few known problems. Let’s see if this latest version solves my problem.

Update 25/10/2010

In spite of the upgrade to 3.3.4.1 I still notice the same problem:


[Oct 25 07:56:43] NOTICE[19553] chan_sip.c: -- Registration for 'myaccount@voip-provider2.com' timed out, trying again (Attempt #6898)
[Oct 25 07:56:56] NOTICE[19553] chan_sip.c: -- Registration for '123456789@voip-provider1.com' timed out, trying again (Attempt #5151)
[Oct 25 07:57:03] NOTICE[19553] chan_sip.c: -- Registration for 'myaccount@voip-provider2.com' timed out, trying again (Attempt #6899)
[Oct 25 07:57:16] NOTICE[19553] chan_sip.c: -- Registration for '123456789@voip-provider1.com' timed out, trying again (Attempt #5152)
[Oct 25 07:57:23] NOTICE[19553] chan_sip.c: -- Registration for 'myaccount@voip-provider2.com' timed out, trying again (Attempt #6900)
[Oct 25 07:57:36] NOTICE[19553] chan_sip.c: -- Registration for '123456789@voip-provider1.com' timed out, trying again (Attempt #5153)
[Oct 25 07:57:43] NOTICE[19553] chan_sip.c: -- Registration for 'myaccount@voip-provider2.com' timed out, trying again (Attempt #6901)
[Oct 25 07:57:56] NOTICE[19553] chan_sip.c: -- Registration for '123456789@voip-provider1.com' timed out, trying again (Attempt #5154)
[Oct 25 07:58:03] NOTICE[19553] chan_sip.c: -- Registration for 'myaccount@voip-provider2.com' timed out, trying again (Attempt #6902)
[Oct 25 07:58:16] NOTICE[19553] chan_sip.c: -- Registration for '123456789@voip-provider1.com' timed out, trying again (Attempt #5155)
[Oct 25 07:58:23] NOTICE[19553] chan_sip.c: -- Registration for 'myaccount@voip-provider2.com' timed out, trying again (Attempt #6903)
[Oct 25 07:58:36] NOTICE[19553] chan_sip.c: -- Registration for '123456789@voip-provider1.com' timed out, trying again (Attempt #5156)
[Oct 25 07:58:43] NOTICE[19553] chan_sip.c: -- Registration for 'myaccount@voip-provider2.com' timed out, trying again (Attempt #6904)
[Oct 25 07:58:56] NOTICE[19553] chan_sip.c: -- Registration for '123456789@voip-provider1.com' timed out, trying again (Attempt #5157)
[Oct 25 07:59:03] NOTICE[19553] chan_sip.c: -- Registration for 'myaccount@voip-provider2.com' timed out, trying again (Attempt #6905)

So looks like I’m going to have to revert back to 3.3.3.

Tags: , , , , ,

9 Responses to “Vigor2820n 3.3.4 firmware upgrade also breaks SIP registrations”

  1. Ryder Cowan says:

    I had this same problem with SIP registrations dropping after installing 3.3.4 firmware. I’ve since gone back to 3.3.3. Have you tried 3.3.4.1 and if so does it appear to solve the problem?

  2. [...] have been meaning to downgrade my Vigor software due to the issue I reported last month. It certainly hasn’t gone away, though I guess that’s not unexpected. So today I was [...]

  3. Ryder Cowan says:

    Having just tried the latest firmware, 3.3.5.2, which according to the release notes has ‘Resolved VoIP stability issues’, it would appear that the problem still has not been resolved. I’ve gone back to 3.3.3 again.

  4. Simon J Mudd says:

    I’ve just upgraded to 3.3.5.2 after using a rc1 version for some time and will see if it’s better. The pre-release version that Draytek offered me seems to help but I do still occasionally get problems. so hopefully I’ll be luckier with the full version.

  5. Andy says:

    Hi Simon

    Did the upgrade to 3.3.5.2 resolve the problem in the end or did you have to go back to the older version?

    No point me wasting time if you have already tried this.

    Thanks

    Andy

  6. kamel says:

    Hi,
    This blog is very helpful,

    I m in same situation as you : Asterisk internal server behind a draytek 2820Vn dsl-router which is blocking sip 5060 to voip module. I can’t get astersik trunks connected, and all my sip registrations fail.

    I downgraded the firmware to the 3.3.3 one, but with no success. Any other solution or fix ???

    Big Thank in advance

  7. Ryder Cowan says:

    Have you tried more recent versions of the firmware to see if any helped?

  8. Simon J Mudd says:

    I hadn’t noticed that there was a newer version but see there’s a 3.3.7.2 version versus 3.3.5.2 I’m currently using. The only thing I’m checking now with Draytek is the right firmware version to use. I bought this router from the UK and use ADSL with Annex M, and it’s not clear which firmware version is appropriate for me (Draytek’s web page is not very clear about this). Current firmware version is 211011_A Hardware: Annex A. This seems to vary a bit by country and I couldn’t find any 211011_A version of 3.3.7.2. Once that is clarified I’ll perform the upgrade to see if things improve. (3.3.5.2 hasn’t been too bad but I still do have occasional registration problems with an external SIP provider, which is resolved with a router reboot.)

Leave a Reply