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

Rusty Newton (JIRA) noreply at issues.asterisk.org
Fri Sep 11 08:34:32 CDT 2015


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

Rusty Newton updated ASTERISK-25388:
------------------------------------

    Assignee: Stefan Tichy
      Status: Waiting for Feedback  (was: Triage)

[~st] can you provide the configuration and describe how to set it up to reproduce the scenario where the locks occur?



> 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
>            Assignee: Stefan Tichy
>         Attachments: lock-one, lock-two
>
>
> 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