[asterisk-bugs] [JIRA] (ASTERISK-26136) pjsip deadlock after a while when a transport config is wrong

[Joshua Colp (JIRA)]

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

Joshua Colp commented on ASTERISK-26136:
----------------------------------------

Thank you for taking the time to report this bug and helping to make Asterisk better. Unfortunately, we cannot work on this bug because your description did not include enough information. Please read over the Asterisk Issue Guidelines [1] which discusses the information necessary for your issue to be resolved and the format that information needs to be in. We would be grateful if you would then provide a more complete description of the problem. At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the problem.
2. The behavior you expected and the location of documentation that led you to that expectation.
3. The behavior you actually encountered.

To demonstrate the issue in detail, please include Asterisk log files generated per the instructions on the wiki [2]. If applicable, please ensure that protocol-level trace debugging is enabled, e.g., 'sip set debug on' if the issue involves chan_sip, and configuration information such as dialplan and channel configuration.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

[2] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information

In this case the log files and output would be useful. You can also use the instructions at https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace#GettingaBacktrace-GettingInformationForADeadlock to get the deadlock info needed.

> pjsip deadlock after a while when a transport config is wrong
> -------------------------------------------------------------
>
>                 Key: ASTERISK-26136
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26136
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip
>    Affects Versions: 13.9.1
>         Environment: Debian 8.5 64bits
>            Reporter: Ludovic Gasc (Eyepea)
>
> To reproduce the bug:
> # You must have several transports. Create a wrong transport section. For example, add *send_pai=yes* in transport.
> # Configure an endpoint that uses this wrong transport
> # Configure another endpoint that use a good transport
> # Restart asterisk
> # In logs, you'll have: in aco_process_var: Could not find option suitable for category 'XXXX' named 'send_pai' 
> # Now, with the endpoint you have, try to call several times and reload several times configuration with *pjsip reload* during 15 minutes
> # After a moment, it will be impossible to call and *pjsip reload* won't work anymore
> # You must use kill -9 to stop asterisk
> It gives you an idea for the issue, or need to recompile Asterisk to have more debug details ?
> Have a nice day.



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