-Original Message-
From: Jaap Winius jwin...@umrk.nl
Reply-to: Asterisk Users Mailing List - Non-Commercial Discussion
asterisk-users@lists.digium.com
To: asterisk-users@lists.digium.com
Subject: Re: [asterisk-users] SIP account registration fails after
upgrade to 1.8
Date: Fri, 22 Mar
On Thu, 21 Mar 2013 16:35:16 +, Jaap Winius wrote:
... For example, if my server sends it a SIP packet with a
register request and a Call-ID that looks like this:
Call-ID: 4991f57656d159925b296e5b3b06496b@[2001:888:abcd:1::a]
... somewhere along they line they end up changing it to
On Fri, 22 Mar 2013 02:46:43 +, Jaap Winius wrote:
Of course, an even better solution would be if Asterisk had a variable
with which to alter the Call-ID string format so that I could omit the
IP address. :-)
It turns out that there in a variable that can do exactly that, and is
On Tue, 19 Mar 2013 02:15:10 +, Jaap Winius wrote:
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
On Thu, 21 Mar 2013 16:35:16 +, Jaap Winius wrote:
Hopefully, my ISP will see fit to squash this bug ASAP.
Well, I got my answer from them quickly enough: Nope.
Luckily, somebody was kind enough to suggest a workaround. Unfortunately,
it involves, downloading the source code and making a
hi,
try srvlookup=yes
On Tue, Mar 19, 2013 at 3:15 AM, Jaap Winius jwin...@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
On Tue, 19 Mar 2013 11:58:22 +0100, Asghar Mohammad wrote:
try srvlookup=yes
Already tried that, but enabling DNS lookups makes no difference when
establishing the SIP connection. The error message that I keep seeing at
the console looks like this:
[Mar 19 12:47:21] NOTICE[7494]:
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
