Hi Nils,
Very cool!
Looking forward to tst it!
Feedback before testing it would to maybe make it also print the "most"
logical request-uri changes.
(like, rewritehostport, lookup(".."))
-Atle
* Nils Ohlmeier <nils(a)iptel.org> [061026 18:22]:
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
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers