Kamailio sends the following when the first gateway times out. Failure route is never executed and next_gw specified in route block still results in the following.
Asterisk placed call to kamailio:
U kamailio:5060 -> asterisk:5060 SIP/2.0 408 Request Timeout. Via: SIP/2.0/UDP asterisk:5060;branch=z9hG4bK670647ee;rport=5060. From: "user" sip:asterisk;tag=as12708af4. To: sip:dialednumber@domain;tag=d7177f97ed67076dddc3163c85ab0656-a8a1. Call-ID: 35e9d8016fec2d9011d470a53224e923@asterisk:5060. CSeq: 102 INVITE. Server: SIP Proxy. Content-Length: 0.
-----Original Message----- From: sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Daniel W. Graham Sent: Friday, November 30, 2012 12:42 PM To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users Mailing List Subject: Re: [SR-Users] LCR Failover
Gave that a try still without success.
-----Original Message----- From: sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Juha Heinanen Sent: Friday, November 30, 2012 1:34 AM To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users Mailing List Subject: Re: [SR-Users] LCR Failover
Daniel W. Graham writes:
Makes sense, would LCR module permit this scenario to work in a different configuration? Or should I be looking at another module? I could use dispatcher but I'd like the ability to add additional routes based on prefix in the future.
if t_relay fails and failure route is not executed, you should call next_gw in route block.
-- juha
_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users