14 Jul
2004
14 Jul
'04
3:55 a.m.
On 13-07 14:45, Andres wrote:
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.
Is there any existing facilities of using metrics
based on Quality and
Cost, and also allowing for route failover? Also, if we have new (for
example) pstn gateways coming on to our network, how can we add these
routes without restarting ser?
There isn't anything designed yet but a module that reads routes (and
failure routes) from a DB would be a wonderful addition to SER. If we
can all chip in a little maybe someone can code it. The current ser.cfg
approach is completely impractical for a large network. Just imagine a
network with 20 Gateways...100 Gateways...