I now have the answer to all the issues I raised in this thread.

1. As previously mentioned, adding "seed" to the flags column for one node
in clusterer solved some issues.
2. Adding option "v" as an extra argument to the save function (in the
REGISTRAR module) has fixed the problem with the R-URI of the NAT pings.

My call to save() for recording registrations - and using the Path header -
now looks like this:

Thanks Liviu for your help.

John Quick
Smartvox Limited
Web: www.smartvox.co.uk

Users mailing list

Reply via email to