I use a view as the extensions table allowing you to add flags to
your source table which can be filtered out in the view.
The view also allows me to store users in an easier to handle way for
our web app (eg, a users/extension numbers table, device table, phone
models table for default sip settings) which are then joined together
in various ways to produce views for the extensions and a sipdevices.
Simon
On 22 Aug 2006, at 15:20, Douglas Garstang wrote:
The unofficial docs on the voip wiki for the realtime extensions
table structure is:
CREATE TABLE `extensions_table` (
`id` int(11) NOT NULL auto_increment,
`context` varchar(20) NOT NULL default '',
`exten` varchar(20) NOT NULL default '',
`priority` tinyint(4) NOT NULL default '0',
`app` varchar(20) NOT NULL default '',
`appdata` varchar(128) NOT NULL default '',
PRIMARY KEY (`context`,`exten`,`priority`),
KEY `id` (`id`)
) TYPE=MyISAM;
Uhm... what abouts comments? What if I wanted to temporarily
deactivate a couple of extensions? Without a comment flag, I'd have
to completely remove those entries from the extensions table!
That's not very friendly is it... Is there a better way?
Doug.
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
