[prev in list] [next in list] [prev in thread] [next in thread] 

List:       asterisk-dev
Subject:    Re: [Asterisk-Dev] E option in meetme.conf
From:       Tilghman Lesher <tilghman () mail ! jeffandtilghman ! com>
Date:       2004-06-28 21:08:06
Message-ID: 200406281608.06029.tilghman () mail ! jeffandtilghman ! com
[Download RAW message or body]

On Monday 28 June 2004 09:19, Ryan Courtnage wrote:
> On Monday 28 June 2004 04:01, Tilghman Lesher wrote:
> > On Friday 11 June 2004 20:49, Ryan Courtnage wrote:
> > > Hi all,
> > >
> > > I'm toying with the 'E' option for MeetMe:
> > >
> > > 	 'E' — select an empty pinless conference (added after v0.7.2)
> > >
> > >
> > > [ext-meetme]
> > > exten => 80,1,MeetMe(|E)
> > > exten => _8[1-6],1,MeetMe(${EXTEN})	; 81-86 defined in meetme.conf
> > >
> > >
> > > Works great when a single extension dials into 80.
> > > However, if a second extension dials 80 (while the 1st extension is
> > > still in a conference), * will pin the CPU and require a restart.
> >
> > What kind of restart?  Asterisk soft restart, kill -9 restart, warm
> > reboot, or cold reboot?
>
> 'restart now' at the * CLI will correct it.

Okay, I've reproduced the problem, and found a fix.  Please go to
bugs.digium.com and apply the patch in bug#1934.  Let me know
if that works (by posting a bugnote).

-- 
Tilghman

[prev in list] [next in list] [prev in thread] [next in thread]