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

Asterisk Team (JIRA) noreply at issues.asterisk.org
Wed Jun 22 01:26:57 CDT 2016


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

Asterisk Team updated ASTERISK-26136:
-------------------------------------

    Assignee: Asterisk Team  (was: Ludovic Gasc (Eyepea))
      Status: Triage  (was: Waiting for Feedback)

> 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)
>            Assignee: Asterisk Team
>
> 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)



More information about the asterisk-bugs mailing list