[asterisk-bugs] [Asterisk 0016393]: [patch] App MeeMe Set the channels' account code to the conference room number
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Dec 7 14:30:49 CST 2009
The following issue requires your FEEDBACK.
======================================================================
https://issues.asterisk.org/view.php?id=16393
======================================================================
Reported By: pta200
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 16393
Category: Applications/app_meetme
Reproducibility: N/A
Severity: feature
Priority: normal
Status: feedback
Asterisk Version: 1.4.27.1
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2009-12-04 10:37 CST
Last Modified: 2009-12-07 14:30 CST
======================================================================
Summary: [patch] App MeeMe Set the channels' account code to
the conference room number
Description:
This is a patch to the latest version of 1.4.27 such that the user can
specify option 'y' to have the meetme application set the channel's account
code to the conference room number. This is some functionality that our
client's conference server needed. I wrote this because we wanted to use
the meetme application's error handling to prompt for both conference room
and pin number. Not having the conference room number prior to calling
meetme and our customer needing the cdr to have an account code for billing
purposes I added the option. Also part of the motivation for adding this
was that as I was searching the web for ways of doing this in the dialplan
I found many people over the last few years wanting the same type of
functionality.
======================================================================
----------------------------------------------------------------------
(0114874) lmadsen (administrator) - 2009-12-07 14:30
https://issues.asterisk.org/view.php?id=16393#c114874
----------------------------------------------------------------------
Thanks for the contribution!
However, for this to be considered for future versions, you will need to
update your patch for the latest Asterisk trunk (not a released version) as
new features only go into future, and not current, versions.
This could potentially make it for Asterisk 1.8 which will eventually be
branched from trunk.
Thanks!
Issue History
Date Modified Username Field Change
======================================================================
2009-12-07 14:30 lmadsen Note Added: 0114874
2009-12-07 14:30 lmadsen Status new => feedback
======================================================================
More information about the asterisk-bugs
mailing list