[asterisk-bugs] [Asterisk 0017585]: MeetMe time limited conference sound files not played
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Jul 5 07:18:27 CDT 2010
The following issue has been CLOSED
======================================================================
https://issues.asterisk.org/view.php?id=17585
======================================================================
Reported By: var
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 17585
Category: Applications/app_meetme
Reproducibility: always
Severity: minor
Priority: normal
Status: closed
Asterisk Version: 1.6.1 - SECURITY ONLY! Test 1.6.2
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
Resolution: open
Fixed in Version:
======================================================================
Date Submitted: 2010-07-04 21:14 CDT
Last Modified: 2010-07-05 07:18 CDT
======================================================================
Summary: MeetMe time limited conference sound files not
played
Description:
When limiting a MeetMe conference with the 'L([x[:y[:z]]])' option, the
sound files are not played for warning time limit or end of conference.
These sound files can be set via:
CONF_LIMIT_WARNING_FILE
and
CONF_LIMIT_TIMEOUT_FILE
If these file locations are not set, default sound files are supposed to
be played - this does not happen either.
The L() limit option does limit the conference to a certain length of
time, which is helpful - but its other functionality does not work.
======================================================================
----------------------------------------------------------------------
(0124213) pabelanger (manager) - 2010-07-05 07:18
https://issues.asterisk.org/view.php?id=17585#c124213
----------------------------------------------------------------------
Please use the support resources before posting a bug report.
---
Thanks for your comments. This does not appear to be a bug report and we
are closing it. We appreciate the difficulties you are facing, but it would
make more sense to raise your question in the support tracker,
http://www.asterisk.org/support
Issue History
Date Modified Username Field Change
======================================================================
2010-07-05 07:18 pabelanger Note Added: 0124213
2010-07-05 07:18 pabelanger Status new => closed
======================================================================
More information about the asterisk-bugs
mailing list