Douglas Garstang wrote:
Ok, I worked out that you need to use append_branch, like this:

append_branch (proxy1)
append_branch (proxy1)
t_replicate (proxy3)

That's what the devevelopers say anyway...

However, all the t_replicate's are going to exactly the same proxy.
Here's a post by two people that have reported _exactly_ the same problem.
Is there a solution?

If I remember right, there was a solution using t_relay_udp_non_ack (or similar) instead of t_replicate (not sure anymore). Look again in the archive.

klaus



http://www.archivum.info/[EMAIL PROTECTED]/2004-12/msg00268.html

Thanks,
Doug.

-----Original Message-----
From: Douglas Garstang Sent: Wednesday, November 30, 2005 4:11 PM
To: [email protected]
Subject: [Users] t_replicate after failure


In the scenario below, if the first t_replicate fails because 192.168.10.5 returns 
"Not Found", the second t_replicate command does not execute. Why? How can I 
make it execute? Call me crazy, but this doesn't seem at all intuitive to me. In a 
functional programming world, if the first fails, the next should still run.

 if (method=="REGISTER") {

                        # Uncomment this if you want to use digest 
authentication
                        if (!www_authorize("voip.com", "subscriber")) {
                                www_challenge("voip.com", "0");
                                exit;
                        };

                        save("location");
                        t_replicate("192.168.10.5","5060");
                        t_replicate("192.168.10.7","5060");
                        exit;
                };

Thanks,
Doug.


_______________________________________________
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users




_______________________________________________
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users

Reply via email to