Re: [asterisk-users] Meetme realtime table structure

[Dan Austin]

Sergey wrote:
 Sorry if I'll be very very stupid but really I write to
 this conference first. I have problems with configuration
 of app_meetme in realtime environment. I use last stable
 release of asterisk 1.6.0.3
 trimmed db table definition

The issue is not in the database, but a problem with how
the options are processed.  There is a patch for this, but
it was not applied to 1.6.0 or 1.6.1, only trunk.  The patch
is in Mantis under bug id 150384 and is named-
rt-meetme-flag-fixes-v2.txt


 Conference work fine but without possibility to manage
 OPTIONS.  Neither adminOpts nor UserOpts does not work.
 All other fields such as PINs, conference nomber, startime
 etc works fine. I think that the problem is in the database
 table format. I try to look to the source in C but really
 not competitive in programming. I chahged field type to
 varchar(28) etc, I tried reccord values in 'value' and in
 value but there was not result.
 I did not also find asterisk debug which could detect database
 errors.  No errors in logs file.  But is I configure static
 meetme conference over /etc/asterisk/*.conf file I get good result.


 Could any one explain database table structure should be and help in
 this issue?


___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

[asterisk-users] Meetme realtime table structure

[Sergey Voropaev]

Hi guys,

Sorry if I'll be very very stupid but really I write to this conference first.
I have problems with configuration of app_meetme in realtime environment.
I use last stable release of asterisk 1.6.0.3
Now situation is following. I create database and table in it. Th table is
CREATE TABLE IF NOT EXISTS `booking` (
  `bookId` int(10) unsigned NOT NULL auto_increment,
  `clientId` int(10) unsigned default '0',
  `confno` varchar(30) default '0',
  `pin` varchar(30) NOT NULL default '0',
  `adminpin` varchar(30) NOT NULL default '0',
  `starttime` datetime NOT NULL default '-00-00 00:00:00',
  `endtime` datetime NOT NULL default '-00-00 00:00:00',
  `dateReq` datetime NOT NULL default '-00-00 00:00:00',
  `dateMod` datetime NOT NULL default '-00-00 00:00:00',
  `maxusers` varchar(30) NOT NULL default '10',
  `status` varchar(30) NOT NULL default 'A',
  `confOwner` varchar(30) NOT NULL default '',
  `confDesc` varchar(100) NOT NULL default '',
  `adminopts` varchar(32) NOT NULL,
  `opts` varchar(32) NOT NULL,
  `sequenceNo` int(10) unsigned default '0',
  `recurInterval` int(10) unsigned default '0',
  `members` int(11) NOT NULL default '0',
  PRIMARY KEY  (`bookId`)
) ENGINE=MyISAM  DEFAULT CHARSET=latin1 AUTO_INCREMENT=145 ;


Conference work fine but without possibility to manage OPTIONS.
Neither adminOpts nor UserOpts does not work. All other fields such as
PINs, conference nomber, startime etc works fine. I think that the
problem is in the database table format. I try to look to the source
in C but really not competitive in programming. I chahged field type
to varchar(28) etc, I tried reccord values in 'value' and in value
but there was not result.
I did not also find asterisk debug which could detect database errors.
No errors in logs file.
But is I configure static meetme conference over /etc/asterisk/*.conf
file I get good result.


Could any one explain database table structure should be and help in this issue?

Thanks in advance.

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users