In my system I have exec that check database for aliases, check my GW for availability and return to SER right URI to send the call. It is pretty easy script on perl so far (it connect mssql server for LCR and working together with nagios to check if GW up/down/full (I know.. it is slow but so far ok for me))
I can not give u my script because it is meaningless without whole infrastructure, but can answer your questions
-----Original Message----- From: serusers-bounces@iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Andres Sent: Wednesday, July 14, 2004 4:43 PM To: Jan Janak Cc: serusers@lists.iptel.org Subject: Re: [Serusers] route managment
approach is completely impractical for a large network. Just imagine
a
network with 20 Gateways...100 Gateways...
You can use m4 (or any other) preprocessor to generate the configuration file. It is not the best solution but it certainly helps. A sample file for m4 can be found in sip_router/etc/rules.m4, sample config file using this approach is in sip_router/etc/ser.cfg.m4 (in unstable cvs branch).
Jan.
Hi Jan,
Maybe I am missing something here but I thought ser.cfg had a limit of 20 route blocks. Even if we use m4 wouldn't we have this limit? If so then how can we implement 100 gateway routes elegantly in their own route block? Must we stuff 5 per route block or all in one huge PSTN route block?
Thanks,
-
Vitaly Nikolaev