Summary:ASTERISK-02114: When using Meetme(<conf #>), won't retry if you enter incorrect pin
Reporter:edgar (edgar)Labels:
Date Opened:2004-07-26 16:50:14Date Closed:2008-01-15 15:03:39.000-0600
Versions:Frequency of
Environment:Attachments:( 0) 20040726__meetme_bug2143.diff.txt
Description:I'm using Meetme(xxx|pM). If non-dynamic conference 'xxx'
has a pin and I enter an incorrect pin, I am not prompted
to retry. I just get the 'invalid pin' message and Meetme
exits and the dialplan continues on.

If I use MeetMe(|pM), if I enter an invalid conference OR
pin, I always get to retry.

So, from the code it looks like the allowretry variable
which defaults to 0 is either never getting set to 1, or
is being set to back to 0 somewhere in the code. I have
not had the time to learn how the code works, and I
can use the work-around of not letting users dial straight
into a conference, i.e. they must always answer the
conference number prompt.


Asterisk version CVS-HEAD-07/14/04-09:54:13
Fedora Core 1, stock kernel 2.4.22-1.2115.nptlsmp
Comments:By: Tilghman Lesher (tilghman) 2004-07-26 18:33:43

Try this patch on for size.  This will change the behavior slightly:

In the case of no arguments or no conference number and no pin, the conference app will prompt for a conference, allow up to 3 pin retries, then allow the conference number to be reentered up to 2 more times, each time, if there's a pin on that conference, allowing the pin to be retried 3 times.

By: Mark Spencer (markster) 2004-07-26 23:22:05

Added to CVS, thanks Tilghman for the patch, perfect first time.

By: Digium Subversion (svnbot) 2008-01-15 15:03:39.000-0600

Repository: asterisk
Revision: 3520

U   trunk/apps/app_meetme.c

r3520 | markster | 2008-01-15 15:03:38 -0600 (Tue, 15 Jan 2008) | 2 lines

Merge tilghman's meetme fix for reentering pin (bug ASTERISK-2114)