[asterisk-bugs] [JIRA] (ASTERISK-24456) SIP deadlock in transfer scenario between Asterisk Servers

[Rusty Newton (JIRA)]

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

Rusty Newton commented on ASTERISK-24456:
-----------------------------------------

I'm unable to reproduce the issue.

Peter can you provide simple SIP configuration and dialplan that would allow us to reproduce the issue?

If we can reproduce , that would make this much easier to track down.

Also, for your own reproduction, can you provide logs with the DEBUG channel enabled and turned up as I mentioned before? If possible, for both the crashing scenario and the locking scenario.

> SIP deadlock in transfer scenario between Asterisk Servers
> ----------------------------------------------------------
>
>                 Key: ASTERISK-24456
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24456
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_local, Channels/chan_sip/General
>    Affects Versions: 11.13.0
>         Environment: Ubuntu precise
>            Reporter: Peter Katzmann
>            Assignee: Peter Katzmann
>            Severity: Critical
>         Attachments: asterisk-sip-loc, backtrace.txt, serverchef.txt, serversek.txt, threads.txt
>
>
> We have 3 Asterisk server (a,b and c)
> we have also 3 different user (Caller, Chef, Sek) .
> User Caller on Server a
> User Chef on Server b
> User Sek on Server c
> Now Caller Dials to Chef
> Chef has a call rule via agi to only accept direct calls from Sek, all other calls are transferred to Sek.
> So the call from Caller on server a is tranfered to Sek on server c automatically
> Sek accepts the calls
> Now Sek will do a unattended transfer of caller to Chef
> Now the server b with Chef shows no action on the dialplan anymore and blocks
> Sometimes also crashes.



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