[OpenSIPS-Users] treply in failure route causes retransmissions

[Brett Nemeroff]

Hello all,
I'm pretty sure I'm missing something obvious here..

After hitting a failure route, I'm seeing retransmissions with a
t_reply. If I clear out the failure_route, opensips generates a 500,
which is sent out and it's happy with. Almost like the 500 (which is
internally generated) is sent statelessly, from a failure route?
Opensips sits on a server with a private IP and is NATed. I've set the
outside IP address in the advertised_address config param.


failure_route[1] {
        xlog("L_INFO","In failure route");
}


(opensips at 10.249.126.19)
0.052840 10.249.126.19 -> 1.2.3.4 SIP/SDP Request: INVITE
sip:74211234 at 1.2.3.4, with session description
  0.061683 1.2.3.4 -> 10.249.126.19 SIP Status: 100 Trying
  0.062550 1.2.3.4 -> 10.249.126.19 SIP Status: 503 Service Unavailable
  0.062637 10.249.126.19 -> 1.2.3.4 SIP Request: ACK sip:74211234 at 1.2.3.4
  0.062724 10.249.126.19 -> 5.6.7.8  SIP Status: 500 Service Unavailable
  0.100239  5.6.7.8 -> 10.249.126.19 SIP Request: ACK sip:1234 at sip.mydomain.com
(No retransmissions.. everyone happy)


---------------

Now if I put a t_reply in there..
failure_route[1] {
        xlog("L_INFO","In failure route");
        t_reply("503","Cannot route");
        exit;
}


  0.042059 10.249.126.19 -> 1.2.3.4 SIP/SDP Request: INVITE
sip:74211234 at 1.2.3.4, with session description
  0.051466 1.2.3.4 -> 10.249.126.19 SIP Status: 100 Trying
  0.051919 1.2.3.4 -> 10.249.126.19 SIP Status: 503 Service Unavailable
  0.052222 10.249.126.19 -> 1.2.3.4 SIP Request: ACK sip:742112324 at 1.2.3.4
  0.052436 10.249.126.19 -> 5.6.7.8  SIP Status: 503 Cannot route
  0.089601 5.6.7.8 -> 10.249.126.19 SIP Request: ACK sip:1234 at sip.mydomain.com
  1.030506 10.249.126.19 -> 5.6.7.8  SIP Status: 503 Cannot route
  2.030507 10.249.126.19 -> 5.6.7.8  SIP Status: 503 Cannot route
  4.030615 10.249.126.19 -> 5.6.7.8  SIP Status: 503 Cannot route
(not happy)


Any ideas??
Thanks!
-Brett