[asterisk-bugs] [Asterisk 0018182]: [patch] useropts not initialized

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18182 
====================================================================== 
Reported By:                dimas
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18182
Category:                   Applications/app_meetme
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
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-21 17:49 CDT
Last Modified:              2010-10-21 17:53 CDT
====================================================================== 
Summary:                    [patch] useropts not initialized
Description: 
The useropts variable is not initilized to empty string inside
find_conf_realtime so if there is not useropts column, it will receive
random garbage.
====================================================================== 

---------------------------------------------------------------------- 
 (0128304) dimas (reporter) - 2010-10-21 17:53
 https://issues.asterisk.org/view.php?id=18182#c128304 
---------------------------------------------------------------------- 
I'm attaching the trivial patch which fixes the issue.

However I would like to confirm one thing: how these realtime user options
relate to user options already passed to meetme by the dialplan? What was
the design? should they be merged or realtime options replace dialplan
options? (I see what the code does but I'm curious if this is intended
behavior or a bug) 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-10-21 17:53 dimas          Note Added: 0128304                          
======================================================================