[Asterisk-Dev] E option in meetme.conf

[Daniel Daley]

I had this happen earlier today as well with the 'e' option.
Glad to know it's not just my box though. Also, as well as the CPU 
spiking
about a minute after the event my zaptel interfaces all went red and 
starting giving
me more dread unknown error 500 messages.

Thanks,

--Dan--

On Jun 11, 2004, at 7:49 PM, 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.
>
> Can someone please try to duplicate this?
> (using CVS-HEAD)
>
> Thanks
> ...........................................
> Ryan Courtnage
> Coalescent Systems Inc
> 403.244.8089
> www.voxbox.ca
> _______________________________________________
> Asterisk-Dev mailing list
> Asterisk-Dev at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-dev
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-dev