Jonathan K. Creasy wrote: I haven't used carrierroute module, but seems it doesn't add the new uri as branch. After the line prefix("+") add append_branch() and see if it work now. Regards, Ramona _______________________________________________ Users mailing list Users(a)lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users

Ovidiu Sas wrote: Smells like a high visiablity blog entry needs to be made on this topic then :) _______________________________________________ Users mailing list Users(a)lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users

Hi Ovidiu, I just had a look at http://voipembedded.com/resources/openser_cr.cfg and noticed that it uses cr_tree_rewrite_uri(tree, domain) which seems to have been superseded by cr_route(tree, domain, "$rU", "$rU", "call_id"). Is that correct? Are there other parts of the cfg file that need to be updated? Serge Ovidiu Sas-3 wrote: -- View this message in context: http://www.nabble.com/failure-route-configuration-tp19037695p19046933.html Sent from the OpenSER Users Mailing List mailing list archive at Nabble.com. _______________________________________________ Users mailing list Users(a)lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users

We're using OpenSER 1.3 so this should be fine. However, I'm looking at the failure routes and notice that what you are doing is selecting a new domain when the initial routing attempt returns an error. Assuming I have three gateways "G1" to "G3" in the same domain "D1" and the hash function causes the initial INVITE to be transmitted to "G1" which is saturated (503 returned), how can I sequentially try "G2" and "G3" in the failure routes? Am I going to need two failure routes with two additional domains "D2" and "D3", changing the hash_index of each gateway in the domains? E.g. if "G1" hash_index = 1 in "D1", then should I put "G2" hash_index = 1 in "D2" and "G3" hash_index = 1 in "D3"? The Dispatcher had an elegant way of dealing with post-failure re-routing by returning the destination set resulting from the first load balancing operation and allowing the script to then remove the last tried destination from the set and making another routing attempt on the reduced set. It seems that CarrierRoute doesn't support this, not even in its 1.4 incarnation. Ovidiu Sas-3 wrote: -- View this message in context: http://www.nabble.com/failure-route-configuration-tp19037695p19050540.html Sent from the OpenSER Users Mailing List mailing list archive at Nabble.com. _______________________________________________ Users mailing list Users(a)lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users

The issue is that upon hitting a routing failure to a specific gateway in a domain, we do not want to try the next domain but instead the next gateway in the current domain, and so on until no gateway remains and we return a 503 message. This is a common way of handling failure routes in the Dispatcher but it doesn't seem that the CarrierRoute supports it.