[asterisk-bugs] [JIRA] (ASTERISK-25388) chan_sip partial unresponsive, one permanent lock

Asterisk Team (JIRA) noreply at issues.asterisk.org
Thu Sep 10 09:36:33 CDT 2015


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

Asterisk Team commented on ASTERISK-25388:
------------------------------------------

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.

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].

> chan_sip partial unresponsive, one permanent lock
> -------------------------------------------------
>
>                 Key: ASTERISK-25388
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25388
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/Registration, Resources/res_config_odbc
>    Affects Versions: 13.5.0
>         Environment: Debian Wheezy amd64;
> PostgreSQL 9.1;
> ODBC used for database connection;
> chan_sip loaded, pjsip not loaded
>            Reporter: Stefan Tichy
>
> Nagios/sipsak is sending SIP option requests to UDP 5060;
> Another Asterisk Instance (11.18.0) registers using transport tls (realtime config);
> Local Asterisk (13.5.0) registers to another Asterisk 13.5.0 using UDP;
> no other SIP traffic and no phone calls.
> Scenario A: Static configuration for second peer (outgoing registration): works fine
> Scenario B: realtime configuration (rtcachefriends=yes) for second peer: after some time asterisk stops responding to the monitoring requests, outgoing registration stops, Recv-Q for UDP 5060 fills up, but incoming registration still works.
> "core show locks" constantly shows one lock (see attachement).
> Phone calls from the first peer do work. "sip reload" will never finish. "core show locks" output in the second attachement.



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



More information about the asterisk-bugs mailing list