[asterisk-bugs] [Asterisk 0012488]: placing an outbound SLA call on hold crashes system
noreply at bugs.digium.com
noreply at bugs.digium.com
Tue Jun 3 11:02:36 CDT 2008
The following issue has been RESOLVED.
======================================================================
http://bugs.digium.com/view.php?id=12488
======================================================================
Reported By: mthomasslo
Assigned To: russell
======================================================================
Project: Asterisk
Issue ID: 12488
Category: Applications/SLA
Reproducibility: always
Severity: block
Priority: normal
Status: resolved
Asterisk Version: 1.4.19
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
Resolution: unable to reproduce
Fixed in Version:
======================================================================
Date Submitted: 04-21-2008 18:56 CDT
Last Modified: 06-03-2008 11:02 CDT
======================================================================
Summary: placing an outbound SLA call on hold crashes system
Description:
When an outbound SLA call is placed on hold prior to the user dialing any
digits, the call can not be retrieved from hold and then the application
stops responding to CLI commands. If the "barge" in SLA.conf is set to yes
for the SIP trunk (ie. Local/disa at line1_outbound) the meetme conference can
be rejoined, however hanging-up the station will still not release the
conference. The channel will remain busy forever and the CLI will not
accept keystrokes (it will continue to display verbose and debug
information) As a result control can only be returned by killing the PID,
and restarting.
======================================================================
----------------------------------------------------------------------
russell - 06-03-08 11:02
----------------------------------------------------------------------
I'm going to close this out since you are no longer experiencing the issue.
However, please let me know if you run into the problem again.
Issue History
Date Modified Username Field Change
======================================================================
06-03-08 11:02 russell Status assigned => resolved
06-03-08 11:02 russell Resolution open => unable to
reproduce
06-03-08 11:02 russell Note Added: 0087718
======================================================================
More information about the asterisk-bugs
mailing list