[asterisk-bugs] [JIRA] (ASTERISK-30025) PJSIP affected by delays in DNS resolution

[Asterisk Team (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-30025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258871#comment-258871 ] 

Asterisk Team commented on ASTERISK-30025:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].

> PJSIP affected by delays in DNS resolution
> ------------------------------------------
>
>                 Key: ASTERISK-30025
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30025
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: pjproject/pjsip
>    Affects Versions: 16.15.0, 16.22.0
>         Environment: Hosted - Microsoft Azure (DS2 v2 - 2vCPU, 8GB, STD SSD) 
> CentOS 7.9
>            Reporter: Nicholas Carr
>
> Issue causing multiple pjsip trunks to go unreachable at random times. Trunk would return after a random period of time. 
> Whilst the issue first appeared on 16.22.0, we have been able to recreate the issue on 16.15.0 as well. 
> Tested IP based and outbound auth based trunks, both are affected. 
> Tested multiple carriers, all seemed to be affected. 
> PJSIP logger showed registrations and SIP OPTIONS all seem to be sending and receiving just fine. After a debug, we found that the issue would appear when qualifying the aor, the SIP OPTIONS would get sent AFTER the qualify had expired. The SIP OPTIONS would receive its valid response almost instantly but still several seconds too late. 
> As per the community discussion - https://community.asterisk.org/t/pjsip-is-now-unreachable-realtime/92392/5, it was recommended to raise the bug for further investigation. 
> Current work around is simply to increase the qualify_timeout default from 3 to 5 or greater pending the delay. 
> Whether the issue/delay is due to the asterisk -> DNS server query or the DNS server -> remote domain DNS query, we are unsure... happy to help



--
This message was sent by Atlassian JIRA
(v6.2#6252)