[asterisk-bugs] [JIRA] (ASTERISK-29692) Asterisk stops responding to SIP OPTIONS requests from other SIP servers or asterisk servers via LAN or WAN with PJSIP module

[Julio Guarniz (JIRA)]

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

Julio Guarniz commented on ASTERISK-29692:
------------------------------------------

I understand, thank you very much for your reply.
 Just for knowledge, you could hire a commercial support plan that can evaluate this case and support us with this review in order to solve or support us in locating the problem, if requested, what would be the process to acquire it and the conditions of this?

> Asterisk stops responding to SIP OPTIONS requests from other SIP servers or asterisk servers via LAN or WAN with PJSIP module
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-29692
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29692
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip
>    Affects Versions: 16.21.0
>         Environment: CentOS Linux release 7.9.2009 (Core)
> 16 vCPU with + 64GB RAM
>            Reporter: Julio Guarniz
>            Assignee: Unassigned
>         Attachments: core-asterisk-running-2021-10-15T09-24-08-0500-brief.txt, core-asterisk-running-2021-10-15T09-24-08-0500-full.txt, core-asterisk-running-2021-10-15T09-24-08-0500-info.txt, core-asterisk-running-2021-10-15T09-24-08-0500-locks.txt, core-asterisk-running-2021-10-15T09-24-08-0500-thread1.txt, options not response.PNG, pjsip.conf
>
>
> Good morning, I have this problem that has been happening more frequently recently.
> An Asterisk server after working normally, suddenly stops responding "sip options" messages from other Asterisk's SIP servers, so the other sip servers declare this asterisk server as down at the SIP level.
> I am using Asterisk 16.21.0 with the PJSIP channel, however the asterisk service continues to run and continues to send sip options to the other servers, therefore the trunks on this server's side are always active, but this asterisk for the other servers is UNREACHABLE.
> I have checked the system logs and I have no errors or warnings that could indicate that the problem is related to a particular action or configuration.
> I have also enabled the CORE SET DEBUG to see the events that occur when this happens and I only get these messages.
> #########################################
> [Oct 5 12:40:02] DEBUG[7979]: res_pjsip/pjsip_distributor.c:503 distributor: Searching for serializer associated with dialog dlg0x7f379823d348 for Response msg 481/ACK/cseq=15893 (rdata0x7f37852a0f38)
> [Oct 5 12:40:02] DEBUG[7979]: res_pjsip/pjsip_distributor.c:520 distributor: No dialog serializer for Response msg 481/ACK/cseq=15893 (rdata0x7f37852a0f38). Using request transaction as basis.
> [Oct 5 12:40:02] DEBUG[7979]: res_pjsip/pjsip_distributor.c:128 find_request_serializer: Found transaction tsx0x7f3798e68298 for Response msg 481/ACK/cseq=15893 (rdata0x7f37852a0f38).
> [Oct 5 12:40:02] DEBUG[7979]: res_pjsip/pjsip_distributor.c:138 find_request_serializer: Found serializer pjsip/distributor-000026e9 on transaction tsx0x7f3798e68298
> ############################################
> It should be noted that the problem is solved, every time I restart asterisk and everything returns to normal, happening again in some cases after 2 or 3 days or in some cases up to 1 week later, so it is very difficult to replicate it and know the exact moment when it will happen.
> Today I had this problem again, but previously, after a similar event previously, I had already recompiled asterisk using the DONT OPTIMIZE option, which is recommended to obtain a backtrace and be able to have a better vision of what may be happening.
> I attach the files that I obtained after the problem happened and asterisk was still active, I obtained this by executing the following:
> /var/lib/asterisk/scripts/ast_coredumper --running
> Likewise, I am attaching captures of the traces obtained by sngrep on the affected asterisk server (192.168.0.5), where it is seen that it receives requests from SIP OPTIONS, but is not able to respond to them, so the other servers declare it UNREACHABLE or UNAVAILABLE
> I really appreciate that you can help me to locate the problem and that the attachments are of help to solve this.
> Greetings and thanks.



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