[asterisk-bugs] [JIRA] (ASTERISK-22384) modifying transport configuration names results in non-functional transport after 'core reload'
Kevin Harwell (JIRA)
noreply at issues.asterisk.org
Fri Aug 30 14:53:03 CDT 2013
[ https://issues.asterisk.org/jira/browse/ASTERISK-22384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Harwell closed ASTERISK-22384.
------------------------------------
Resolution: Fixed
> modifying transport configuration names results in non-functional transport after 'core reload'
> -----------------------------------------------------------------------------------------------
>
> Key: ASTERISK-22384
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-22384
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Resources/res_pjsip
> Affects Versions: 12
> Environment: SVN-branch-12-r397614
> Reporter: Rusty Newton
> Assignee: Kevin Harwell
> Attachments: backtrace-threads9.txt
>
>
> This is another failure mode for ASTERISK-22382 and is likely related.
> If it doesn't crash, then Asterisk just ignores all incoming SIP traffic.
> Something bad happened to the transports!
> Shutting down asterisk and restarting it results in the transport functioning fine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list