[asterisk-bugs] [Asterisk 0017672]: Meetme PIN caching problem using realtime

Asterisk Bug Tracker noreply at bugs.digium.com
Mon Jul 19 14:59:22 CDT 2010


The following issue has been UPDATED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17672 
====================================================================== 
Reported By:                kenji
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17672
Category:                   Addons/res_config_mysql
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.2.9 
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-07-19 13:26 CDT
Last Modified:              2010-07-19 14:59 CDT
====================================================================== 
Summary:                    Meetme PIN caching problem using realtime
Description: 
If you delete or set a new PIN while you're in a conference a new caller
enter the new PIN, he get a "conf-invalidpin" message.

The PIN that is set at starting the conference is cached.

I tested with 2 ways:

1.) over asterisk: hostname*CLI> realtime update meetme confno 33 pin
1111
2.) directly: UPDATE `meetme` SET `pin` =  '1111' WHERE `confno` = '33'
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-07-19 14:59 pabelanger     Severity                 major => minor      
======================================================================




More information about the asterisk-bugs mailing list