Summary:ASTERISK-15040: Meetme - Quitting time issue
Reporter:Andrea Sannucci (asannucci)Labels:
Date Opened:2009-10-26 17:12:05Date Closed:2011-06-07 14:08:18
Versions:Frequency of
Environment:Attachments:( 0) meetme-issue
Description:When one o more users enter in a conference, after about 60 seconds the conference dropped the users and in the asterisk console appear: "Quitting time..."

The conference is configured in the meetme.conf

This happen only if

If I change to

the issue disappear


Centos 5.3
32 bit
Comments:By: Leif Madsen (lmadsen) 2009-10-28 09:12:37

Are you using realtime?

Can you provide the console output with 'core set debug 10' enabled, along with 'meetme-issue => notice,warning,error,verbose,debug' in logger.conf then reproduce the issue, and attach the /var/log/asterisk/meetme-issue file to this issue?

If using realtime, please provide your database schema and which database you're using.

By: Andrea Sannucci (asannucci) 2009-10-28 13:27:39

I'm not using realtime just now.
En the meetme-issue there is this line (repeated hundred times) before the conference is dropped:

DEBUG[5100] channel.c: Internal timing is disabled (option_internal_timing=0 chan->timingfd=42)

My Linux server is a XEN VPS wiht DAHDI and DAHDI tools instalated.

Thank you

By: Leif Madsen (lmadsen) 2009-11-02 10:51:03.000-0600

That's a DEBUG message. You don't need to see those unless you're debugging. DEBUG messages can be very chatty. That is not an issue.

In asterisk.conf try enabling internal_timing.

By: Andrea Sannucci (asannucci) 2009-11-02 15:19:28.000-0600

With internal_timing=yes the behavior it's the same...

After one minute the users are dropped from conference.
quitting time....

By: Bereterbide Marcelo (marhbere) 2009-11-02 16:10:39.000-0600

If you have set schedule=yes, then must be create the a table similar to:
CREATE TABLE `meetme` (
 `confno` char(80) NOT NULL DEFAULT '0',
 `starttime` datetime DEFAULT NULL,
 `endtime` datetime DEFAULT NULL,
 `pin` char(20) DEFAULT NULL,
 `adminpin` char(20) DEFAULT NULL,
 `members` int(11) NOT NULL DEFAULT '0',
 `maxusers` int(11) NOT NULL DEFAULT '0',
 PRIMARY KEY (`id`),
 KEY `idx_confno` (`confno`,`starttime`)

By: Andrea Sannucci (asannucci) 2009-11-02 16:35:08.000-0600

So if I use schedule=yes I can only use conferences in realtime and if I use schedule=no i can only use conferences created in the meetme.conf.

Is this true?

Thank you

By: Bereterbide Marcelo (marhbere) 2009-11-02 16:42:40.000-0600

I think yes, that must be this way.


By: Andrea Sannucci (asannucci) 2009-11-02 17:42:03.000-0600

Maybe this can help other users:

-- Table structure for Realtime meetme

       confno char(80) DEFAULT '0' NOT NULL,
       -- Must set schedule=yes in meetme.conf to use starttime and endtime
       starttime datetime NULL,
       endtime datetime NULL,
       -- PIN to enter the conference, if any
       pin char(20) NULL,
       -- Options to associate with normal users of the conference
       opts char(100) NULL,
       -- PIN to enter the conference as an administrator, if any
       adminpin char(20) NULL,
       -- Options to associate with administrator users of the conference
       adminopts char(100) NULL,
       -- Current count of conference participants
       members integer DEFAULT 0 NOT NULL,
       -- Maximum conference participants allowed concurrently
       maxusers integer DEFAULT 0 NOT NULL,
       PRIMARY KEY (confno, starttime)

By: Leif Madsen (lmadsen) 2009-11-03 09:00:25.000-0600

Based on what I can see in the meetme.conf.sample file, scheduled conferences can only be handled from realtime.

; Conferences may be scheduled from realtime?

Closing this issue.