Hi Atle, On Thursday 26 October 2006 18:31, Atle Samuelsen wrote: Thanks You are right. That would make sense for sure. But the problem with that is that the script then somehow would need to know "statically" which functions might change the RURI. But I do not like such "static" approaches very much, because someone has to maintain them. But if someone comes up with such a solution that would be a big step in the direction to an SER GDB :-)

BTW before solving the RURI problem, the first problem for route_graph is, that module functions might call a route. This is not solved yet.

Nils

looks promising, so I wanted to give it try.... and hey, what is that pyhton? Is it your preferred misspell, so did you create symbolic link to python? :-D

Michal Nils Ohlmeier wrote: > Hello, > > in case you are not following the CVS commit log messages: I just checked > in a small python script which should be able to print a dependency graph > in ASCII of the route blocks of a SER config file. > > When you try to understand more complex configuration files this tool > might be helpfull. But be warned: this is still alpha code! > It will not eat your config file, but the output might not meet your > expectations :-) > > If you run it with the default configuration file the output will look > like this: > > ./route_graph.py ../../etc/ser.cfg > > Main > > \- 1 > > \- 1 > > \- 1 > > \- 1 > > A more complex scenario (from a config with named routes) could look like > this: > > ./route_graph.py ./ser.cfg > > Main > > \- ROUTE_RPC > > | \- ROUTE_ERROR_REPLY > > \- ROUTE_PROXYINIT > > | \- ROUTE_ERROR_REPLY > > \- ROUTE_INDIALOG > > | \- ROUTE_ERROR_REPLY > | > | \- ROUTE_ST > | > | \- ROUTE_FORWARD > | > | | \- ROUTE_LI > | | > | | \- ROUTE_RTPPROXY > | | > | | \- ROUTE_RR > > \- ROUTE_DOMAINPOLICY > > | \- ROUTE_ERROR_REPLY > > \- ROUTE_REGISTRAR > > | \- ROUTE_ERROR_REPLY > > \- ROUTE_AUTHENTICATION > > > [... omitted bigger parts...] > > Send routes > ----------- > > onsend > > Failure routes > -------------- > > FAILURE_ROUTE > > \- ROUTE_RTPPROXY > > \- ROUTE_VOICEMAIL > > | \- ROUTE_SEMS > | > | | \- ROUTE_LI > | | > | | \- ROUTE_RR > | > | \- ROUTE_ERROR_REPLY > > [... omitted bigger parts...] > > Onreply routes > -------------- > > REPLY_ROUTE > > > Feedback is welcome. Patches even more! :-) > > Greetings > Nils > _______________________________________________ > Serdev mailing list > Serdev(a)lists.iptel.org > http://lists.iptel.org/mailman/listinfo/serdev