[asterisk-bugs] [JIRA] (ASTERISK-25411) PJSIP functionality becomes unresponsive after some time

[Rafik Djabrailov (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-25411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rafik Djabrailov updated ASTERISK-25411:
----------------------------------------

    Status: Triage  (was: Waiting for Feedback)

> PJSIP functionality becomes unresponsive after some time
> --------------------------------------------------------
>
>                 Key: ASTERISK-25411
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25411
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip
>    Affects Versions: 13.5.0
>         Environment: CentOS 6.7 minimal x86
> Linux 2.6.32-504.el6.i686 #1 SMP Wed Oct 15 03:02:07 UTC 2014 i686 i686 i386 GNU/Linux
>            Reporter: Rafik Djabrailov
>            Assignee: Rafik Djabrailov
>         Attachments: 23-10-2015_debug.txt, acl.conf, backtrace-threads.txt, bad_pjsip_call.txt, bad_pjsip_options_request.txt, core-show-locks.txt, core-show-taskprocessors.txt, core-show-threads.txt, dialplan_excerpt.ael, good_pjsip_call.txt, good_pjsip_options_request.txt, modules.conf, new_info.txt, pjsip.conf
>
>
> After some time since Asterisk start (may be several hours or days), calls to PJSIP trunks are hanging with no actions or errors. 'pjsip set logger on' command executes, but SIP messages are not appearing in the console completely. 'pjsip show registrations' shows trunks as 'Registered' and 'pjsip show contacts' can display 'Avail' or sometimes 'Unavail' on contacts. It seems that res_pjsip completely hangs in it's last successfull state. 'module reload' executes, but does not help. Only full Asterisk restart brings PJSIP functionality to normal state.
> Maybe this problem can be linked to Internet downtimes, but when Internet brings up, all is functioning on OS level automatically (DHCP, DNS resolutions, default gateway routing, etc).
> I think maybe this problem is somehow related to sip_resolver.c and resolver.c not being executed by PJSIP for some reason.
> As I've noted before, there is no single SIP message in the console, only DEBUG messages (files bad_pjsip_call.txt and good_pjsip_call.txt).
> Also there are some additional debug logs with OPTIONS requests (qualify) to trunk (bad_pjsip_options_request and good_pjsip_options_request).
> Some IPs and numbers are "XXXed" for security reasons.
> PJSIP configure string "./configure --prefix=/usr/local --disable-sound --disable-resample --disable-video --disable-opencore-amr --enable-shared CFLAGS='-O2 -DNDEBUG'"



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