Hi Paul,
looks like now you can add dynamic branches if you use AVPOPS module. Put all your SER farm addresses in AVP table with the same ID and do something like: avp_db_load("$ruri/domain","$dsts"); avp_write("$ruri", "$dsts"); avp_pushto("$ruri","$dsts/g"); t_replicate(fix_dst);
$dsts is an avp alias what what ever AVP name/ID you want to use. The AVPs can be kept per domain (like in this example) or you can use uuid (as you find more convenient).
The only disadvantage is you still need a fix destination to be used as parameter for t_replicate(). The avp which are loaded will be appended as branches.
Best regards, Marian Dumitru
Java Rockx wrote:
Hi All.
I came across this posting http://lists.iptel.org/pipermail/serusers/2004-August/010832.html where Bogdan suggested sending REGISTER messages to multiple ser proxies using something like this:
append_branch( dst1 ); append_branch( dst2 ); t_replicate( dst3 );
How would I best solve a problem where if I were to have say 10 ser proxies and wanted to avoid changing the ser.cfg everytime I added/removed a new sip proxy to the farm? I'm thinking it would be best to do this with a custom module which would look up rows in a MySQL table. Each row would be the location of a ser proxy which would be used in a call to append_branch(). This way I could add new ser proxies to the farm without modifying ser.cfg on every machine and in my ser.cfg file I could replace the above snippet with something like this:
append_proxy_locations();
Does anyone see pitfalls with this? Is there a better solution?
Regards, Paul
__________________________________ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers