asterisk users - Apr 2019 - PJSIP Delay in Dialing

As I understand it, delays like this are almost always caused by slow or
failing DNS lookups. Running a packet capture on all interfaces filtering
on port 53 shows no DNS traffic leaving the server. I have ensured that
there is a DNS record for the server & that it can resolve it. I've also
added records to my hosts file and checked using 'genet ahosts hostname'
but still the issue remains.

So how do I figure out what is going wrong please? This is preventing me
from moving from chan_sip to chan_pjsip.

Many thanks
Mark.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20190404/daed5546/attachment.html>

On Thu, Apr 4, 2019, at 10:53 AM, Mark Farmer wrote:
> As I understand it, delays like this are almost always caused by slow 
> or failing DNS lookups. Running a packet capture on all interfaces 
> filtering on port 53 shows no DNS traffic leaving the server. I have 
> ensured that there is a DNS record for the server & that it can resolve
> it. I've also added records to my hosts file and checked using
'genet
> ahosts hostname' but still the issue remains.
> 
> So how do I figure out what is going wrong please? This is preventing 
> me from moving from chan_sip to chan_pjsip.
What version of Asterisk? That will change the answer as 13 uses the built-in
PJSIP DNS resolver, while 16 uses our own implementation.

-- 
Joshua C. Colp
Digium - A Sangoma Company | Senior Software Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - US
Check us out at: www.digium.com & www.asterisk.org

Sorry, should have included that.

Asterisk 16.2.1

Mark.


On Thu, 4 Apr 2019 at 14:56, Joshua C. Colp <jcolp at digium.com> wrote:
> On Thu, Apr 4, 2019, at 10:53 AM, Mark Farmer wrote:
> > As I understand it, delays like this are almost always caused by slow
> > or failing DNS lookups. Running a packet capture on all interfaces
> > filtering on port 53 shows no DNS traffic leaving the server. I have
> > ensured that there is a DNS record for the server & that it can
resolve
> > it. I've also added records to my hosts file and checked using
'genet
> > ahosts hostname' but still the issue remains.
> >
> > So how do I figure out what is going wrong please? This is preventing
> > me from moving from chan_sip to chan_pjsip.
>
> What version of Asterisk? That will change the answer as 13 uses the
> built-in PJSIP DNS resolver, while 16 uses our own implementation.
>
> --
> Joshua C. Colp
> Digium - A Sangoma Company | Senior Software Developer
> 445 Jan Davis Drive NW - Huntsville, AL 35806 - US
> Check us out at: www.digium.com & www.asterisk.org
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> Check out the new Asterisk community forum at:
> https://community.asterisk.org/
>
> New to Asterisk? Start here:
>       https://wiki.asterisk.org/wiki/display/AST/Getting+Started
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users


-- 
Mark Farmer
farmorg at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20190404/f082bee0/attachment.html>