[asterisk-bugs] [Asterisk 0018086]: differences between meetme error handling

[Asterisk Bug Tracker]

The following issue requires your FEEDBACK. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18086 
====================================================================== 
Reported By:                kenji
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18086
Category:                   Applications/app_meetme
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.2.13 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-10-03 11:00 CDT
Last Modified:              2010-10-05 15:15 CDT
====================================================================== 
Summary:                    differences between meetme error handling
Description: 
I found some differences in error handling if a meetme room doesn't exist.

- using  "MeetMe(,Ms)"   and a room doesn't exist asterisk play 
conf-invalid.slin and you can re-enter the pin
- using  "MeetMe(${room},Ms)" an read DTMF with
"Read(roomid,conf-getconfno,6,1)" an the room doesn't  exist, asterisk
hangup the call

is it possible to have the same error handling like the first case (if
room not exist, play conf-invalid and re-enter the PIN. 
For me this function is important, because i need the room number, to for
some choices based on a mysql column.
====================================================================== 

---------------------------------------------------------------------- 
 (0127713) lmadsen (administrator) - 2010-10-05 15:15
 https://issues.asterisk.org/view.php?id=18086#c127713 
---------------------------------------------------------------------- 
This isn't really a bug so much, as it is perhaps an unexpected behaviour.
I'm going to import this into our triage system to have someone else look
at this, but my personal opinion is this is a feature request. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-10-05 15:15 lmadsen        Note Added: 0127713                          
2010-10-05 15:15 lmadsen        Status                   new => feedback     
======================================================================