[asterisk-bugs] [Asterisk 0016393]: [patch] App MeeMe Set the channels' account code to the conference room number

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
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 15:04 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. 
====================================================================== 

---------------------------------------------------------------------- 
 (0114879) lmadsen (administrator) - 2009-12-07 15:04
 https://issues.asterisk.org/view.php?id=16393#c114879 
---------------------------------------------------------------------- 
I think this link would be useful to answer your question about 1.7: 
http://blogs.asterisk.org/2009/11/10/asterisk-project-update-astricon-2009/
 -- 1.8 was not a typo.

However, we have never used odd numbers in our releases (1.0, 1.2, 1.4,
1.6.x, 1.8, etc...) (please ignore the use of odd numbers prior to the
release of 1.0 :))

Odd numbers (1.3, 1.5, 1.7, 1.9) would typically mean development
snapshots for future releases, but we don't do that.

New features are not permitted in branches outside of trunk -- as soon as
a branch is created, that is a feature frozen set of code, and only bug
fixes are then permitted at that point -- no matter how small the feature.
1.6.2 was feature frozen the moment it was branched from trunk. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-12-07 15:04 lmadsen        Note Added: 0114879                          
======================================================================