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

Stefan Tichy (JIRA) noreply at issues.asterisk.org
Mon Sep 14 07:59:33 CDT 2015


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

Stefan Tichy commented on ASTERISK-25388:
-----------------------------------------

Sorry for the delay, but serveral attempts where necessary until I could reproduce the problem with a small configuration. There is at least one error in it. The peer that registers to another asterisk server has a mailbox configuration. It was a mistake in the original configuration and it seems to be neccessary to reproduce the problem.

The names for hosts, users and secrets just have dummy values. With incoming and outgoing registration and incoming option requests the problem should show up within a few hours (max 4 or 5 in my tests, sometimes only a few minutes).

> 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