Peer Unreachable After IP Change

Home » Asterisk Users » Peer Unreachable After IP Change
Asterisk Users 5 Comments

Hi list!

Another day, another problem… I’m checking with Nagios my Asterisk at home, and since yesterday I noticed that, after my IP changes (Deutsche Telekom drop the DSL-line every 24 hours, so that I have a new IP every day), the peer of an VoIP-provider I use is UNREACHABLE. Yesterday I though it was a problem on the line, but today is the same, so I
think it is something other… Yesterday I solved changing the Port from 5061 to 5060, but I don’t want to change the port every day… 🙂

On the Asterisk CLI I see:

OpenWrt*CLI> sip show registry Host dnsmgr Username Refresh State Reg.Time
messagenet:5060 N 5406013068 105 Unregistered Mon, 08 Jun 2015 00:30:27

and every couple of seconds:

[Jun 8 07:17:52] WARNING[30003]: chan_sip.c:13784 transmit_register: Probably a DNS error for registration to 5406013068@messagenet, trying REGISTER again (after 20 seconds)
[Jun 8 07:17:52] NOTICE[30003]: chan_sip.c:13656 sip_reg_timeout: — Registration for ‘5406013068@messagenet’ timed out, trying again (Attempt
#1218)

Could someone help me to understand the problem?

Thanks Luca Bertoncello
(lucabert@lucabert.de)

5 thoughts on - Peer Unreachable After IP Change

  • Don’t use Port 5061, your SIP-port should be always even like 5060,
    5062, 5064 or 5066.

    Regards Guenther

    –

  • Guenther Boelter schrieb:

    Could you please explain why?
    I see in /etc/services, that 5060 is the port for SIP and 5061 for SIP-TLS, but I don’t find anything for the other ports…

    Thanks Luca Bertoncello
    (lucabert@lucabert.de)
    —–BEGIN PGP SIGNATURE—

  • Hi Luca,

    that’s what Deutsche Telekom has told me. I’m using it since a few month in Germany and it works well.

    It depends from which ports are supported by your provider. Sipgate for example is telling there customers to use 5060, 5160, 5260 etc.

    Regards Guenther

    –

  • Guenther Boelter schrieb:

    OK, thanks.. I’m using port 5060, so I think, it would not be a problem…

    OK, thanks!

    Another question: do you use Asterisk on the DSL of Deutsche Telekom? Could we compare our configuration?

    Thanks Luca Bertoncello
    (lucabert@lucabert.de)
    —–BEGIN PGP SIGNATURE—

  • Since your IP has changed you probably need to do a ‘sip reload’ so that Asterisk learns about the new IP and can build the SIP headers with the correct IP.