[asterisk-users] Update peer IP address

Sebastian Kemper sebastian_ml at gmx.net
Tue Apr 14 14:56:17 CDT 2015


On Tue, Apr 14, 2015 at 09:38:22AM +0200, Daniel Heckl wrote:
> Sebastian,
> 
> Your code sounds good, I'm curious how it goes on.
> 
> First the linux machine had the Google Public DNS 8.8.8.8 as DNS
> server. After I changed it to the via PPPoE assigned DNS servers, i
> had no changes any more. But we should be prepared for changes.
> 
> You must enable the dnsmgr. If DNS resolves a new ip, the peer is
> updated.

Hello Daniel,

Thanks for the tip. I've enabled the DNS manager. Let's see how it goes.

Kind regards,
Sebastian

> 
> > Am 14.04.2015 um 08:26 schrieb Sebastian Kemper <sebastian_ml at gmx.net>:
> > 
> >> On Thu, Apr 02, 2015 at 11:33:38PM +0200, Daniel Heckl wrote:
> >> I do not want set allowguest=yes. The problem is, there is no official
> >> list with ip addresses of Telekom Germany. But I think all ip
> >> addresses comes from the ip range 217.0.0.0/13.
> > 
> > Hello Daniel,
> > 
> > Judging by the lists I found I think it's more like this subnet:
> > 217.0.16.0/255.255.248.0
> > 
> >> I have now the following addition to sip.conf. I think it is the only
> >> safe option. Or what would you say?
> >> 
> >> [telekom](!)
> > 
> > <snip>
> > 
> >> [DTAG-IP_IN18_016](telekom)
> >> host=217.0.18.16
> >> 
> >> [DTAG-IP_IN18_036](telekom)
> >> host=217.0.18.36
> >> 
> >> etc.
> > 
> > This configuration is now running here:
> > 
> > [general]
> >    context=unauthenticated
> >    allowguest=no
> >    srvlookup=no
> >    udpbindaddr=0.0.0.0
> >    tcpenable=no
> >    localnet=172.16.28.0/24
> >    alwaysauthreject=yes
> >    directmedia=no
> >    sdpsession=MyNewSessionString
> >    useragent=MyNewUserAgent
> >    language=de
> >    tonezone=de
> >    defaultexpiry=480
> > 
> > register => 0NUMBER2:PASS:USER at t-online.de@tel.t-online.de/NUMBER2
> > register => 0NUMBER3:PASS:USER at t-online.de@tel.t-online.de/NUMBER3
> > register => 0NUMBER4:PASS:USER at t-online.de@tel.t-online.de/NUMBER4
> > 
> > [my-codecs](!)
> >    allow=!all,alaw
> > 
> > [home-phone](!,my-codecs)
> >    acl=voice_vlan
> >    type=friend
> >    host=dynamic
> >    context=LocalSets
> > 
> > [XXXXXXXXXXX](home-phone)
> >    secret=XXXXXXXXXXXXX
> > 
> > [dtag_inbound](my-codecs)
> >    acl=acl_dtag_inbound
> >    type=peer
> >    context=from_dtag
> >    host=tel.t-online.de
> > 
> > [dtag_outbound](my-codecs)
> >    acl=acl_dtag_outbound
> >    type=peer
> >    defaultuser=USER at t-online.de
> >    remotesecret=PASS
> >    host=tel.t-online.de
> >    fromdomain=tel.t-online.de
> > 
> > The thing is, the provider's SIP server hasn't changed the IP yet. This
> > morning it's still the same as yesterday. And yesterday it was the same
> > the whole day.
> > 
> > Don't know why I didn't run into the "load balancer" issue (yet). I'm
> > starting to think it's because I'm "hiding" that I'm using Asterisk
> > (sdpsession, useragent, also custom systemname in asterisk.conf). But
> > probably that's not the reason. Anyway, I'm just going to wait until it
> > doesn't work and then worry about it.
> > 
> > Regards,
> > Sebastian



More information about the asterisk-users mailing list