[asterisk-users] SIP account registration fails after upgrade to 1.8

Asghar Mohammad asghar144 at gmail.com
Tue Mar 19 05:58:22 CDT 2013


hi,
try srvlookup=yes

On Tue, Mar 19, 2013 at 3:15 AM, Jaap Winius <jwinius at umrk.nl> wrote:

> Hi folks,
>
> Following an upgrade from Debian squeeze to wheezy, and Asterisk 1.6.2.9
> to 1.8.13, my server is no longer able to register a connection to a SIP
> account at my ISP (XS4ALL in the Netherlands). At the same time, it is
> still able to register a different account with another SIP provider, so
> it must be that they no longer have the same basic requirements.
>
> The relevant part of my sip.conf looks like this:
>
> [general]
> context=incoming-j
> canreinvite=no
> dtmfmode=inband
> qualify=yes
> srvlookup=no
> disallow=all
> allow=alaw
> allow=ulaw
> allow=g722
> allow=g726
> allow=g729
> insecure=port,invite
> register => <telno>:<password>@sip.xs4all.nl/<telno>
>
> Does anyone know of any new variables that have been introduced since
> Asterisk 1.6.2.9, that apply here and might be causing this problem?
>
> Thanks,
>
> Jaap
>
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> New to Asterisk? Join us for a live introductory webinar every Thurs:
>                http://www.asterisk.org/hello
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20130319/d659c71f/attachment.htm>


More information about the asterisk-users mailing list