| Summary: | ASTERISK-16392: Meetme PIN caching problem using realtime | ||
| Reporter: | Daniel Knoll (kenji) | Labels: | |
| Date Opened: | 2010-07-19 13:26:13 | Date Closed: | 2011-06-07 14:00:59 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Addons/res_config_mysql |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| 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' ****** ADDITIONAL INFORMATION ****** Is it possible to disable the caching, because we had many users on our conference system and they can change the PIN over a Webfrontend. We play a voicepromt into the Conference if the room is looked or muted, and a Orginate Call (to play voicepromts into a conference) failed, if the PIN is changed while a conf. is active. I do not know in which category it can be sorted. tested with: asterisk 1.6.2.6 asterisk 1.6.2.7 asterisk 1.6.2.8 asterisk 1.6.2.9 and asterisk-addons 1.6.2.1 | ||
| Comments: | By: Paul Belanger (pabelanger) 2010-07-19 14:59:33 I suspect this is a feature request. By: Tilghman Lesher (tilghman) 2010-07-19 15:10:40 It is, indeed, a feature request. Once a conference is created, it cannot be modified. | ||