Hi! I tried to understand how chan_sip can be configured by means of a database. I found these 2 different approaches (please correct me if I am wrong): static configuration: the sip.conf file is mapped to a database table. The table contains one line for each line in sip.conf. realtime configuration: the peers/users are stored in the database using a single line for each peer/user. "Static" does not eases provisioning as configuring a SIP peer/user using this approach is really complicated - it is just a method to store .conf files in database. "realtime" really eases provisioning of SIP peers/users. You only have to insert/update/delete a single line. But functionality is different - there are limitations as these objects are not stored in memory (can be cached), for example device status information. What I am looking for is a method to provision peers/users with a single line in the database, but without limitations. Thus, the peers need not to be realtime but are loaded on "sip reload". So is there a possiblity to have static peer/users configuration using a nice and easy way? thanks klaus
On 10:56, Tue 24 Feb 09, Klaus Darilion wrote:> Hi! > > I tried to understand how chan_sip can be configured by means of a > database. I found these 2 different approaches (please correct me if I > am wrong): > > static configuration: the sip.conf file is mapped to a database table. > The table contains one line for each line in sip.conf. > > realtime configuration: the peers/users are stored in the database using > a single line for each peer/user. > > > "Static" does not eases provisioning as configuring a SIP peer/user > using this approach is really complicated - it is just a method to store > .conf files in database. > > "realtime" really eases provisioning of SIP peers/users. You only have > to insert/update/delete a single line. But functionality is different - > there are limitations as these objects are not stored in memory (can be > cached), for example device status information. > > > What I am looking for is a method to provision peers/users with a single > line in the database, but without limitations. Thus, the peers need not > to be realtime but are loaded on "sip reload". > > So is there a possiblity to have static peer/users configuration using a > nice and easy way?Store them in a database and use a combination of cron and some scripting to generate the configuration files. Some advice: keep track if an update has been done to the database since last reload and only regen files and issue a reload when this is true.> > thanks > klaus > > > _______________________________________________ > -- 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-- Michiel van Baak michiel at vanbaak.eu http://michiel.vanbaak.eu GnuPG key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x71C946BD "Why is it drug addicts and computer aficionados are both called users?"
24 feb 2009 kl. 11.31 skrev Michiel van Baak:> On 10:56, Tue 24 Feb 09, Klaus Darilion wrote: >> Hi! >> >> I tried to understand how chan_sip can be configured by means of a >> database. I found these 2 different approaches (please correct me >> if I >> am wrong): >> >> static configuration: the sip.conf file is mapped to a database >> table. >> The table contains one line for each line in sip.conf. >> >> realtime configuration: the peers/users are stored in the database >> using >> a single line for each peer/user. >> >> >> "Static" does not eases provisioning as configuring a SIP peer/user >> using this approach is really complicated - it is just a method to >> store >> .conf files in database. >> >> "realtime" really eases provisioning of SIP peers/users. You only >> have >> to insert/update/delete a single line. But functionality is >> different - >> there are limitations as these objects are not stored in memory >> (can be >> cached), for example device status information. >> >> >> What I am looking for is a method to provision peers/users with a >> single >> line in the database, but without limitations. Thus, the peers need >> not >> to be realtime but are loaded on "sip reload". >> >> So is there a possiblity to have static peer/users configuration >> using a >> nice and easy way? > > Store them in a database and use a combination of cron and some > scripting to generate the configuration files. > > Some advice: keep track if an update has been done to the database > since > last reload and only regen files and issue a reload when this is true.I think this is what FreePBX does. /O