[Serusers] t_relay won't give up
Brett's Asterisk Account
brett-asterisk at mail.worldcall.net
Tue May 10 09:15:52 CEST 2005
Hey All,
I'm having a problem. I'm attempting a:
if (!t_relay()) {
route(2);
break
}
When the destination ignores the request (perhaps the domain portion of the RURI points to a server that is down?), I see the INVITE processed like 10 times. Here is the trace..
11.066729 192.168.20.10 -> 192.168.50.100 SIP/SDP Request: INVITE sip:2015551212;rn=2015550099;npdi=yes at 192.168.50.100;dtg=HSTNSIPORIG02;user=phone, with session description
4(24793) ******** INCOMMING CALL FROM TRUSTED IP ADDRESS
4(24793) INFO Checking ANI from Trusted IP
4(24793) INFO: ANI Verification successful for trusted IP
4(24793) ****** INCOMING CALL PASSED SECURITY CHECKS
4(24793) INFO: Begining attempt 1 DID route for trusted ip customer
4(24793) ****** FOUND DID TABLE ROUTE
11.318093 192.168.50.100 -> 192.168.20.10 SIP Status: 100 trying -- your call is important to us
11.318223 192.168.50.100 -> 10.1.2.3 SIP/SDP Request: INVITE sip:2015551212 at 10.1.2.3, with session description
11.425865 192.168.50.100 -> 10.1.2.3 SIP/SDP Request: INVITE sip:2015551212 at 10.1.2.3, with session description
13.429423 192.168.50.100 -> 10.1.2.3 SIP/SDP Request: INVITE sip:2015551212 at 10.1.2.3, with session description
17.436544 192.168.50.100 -> 10.1.2.3 SIP/SDP Request: INVITE sip:2015551212 at 10.1.2.3, with session description
21.443657 192.168.50.100 -> 10.1.2.3 SIP/SDP Request: INVITE sip:2015551212 at 10.1.2.3, with session description
23.328599 192.168.20.10 -> 192.168.50.100 SIP Request: CANCEL sip:2015551212;rn=2015550099;npdi=yes at 192.168.50.100;dtg=UTEXHSTNSIPORIG02;user=phone
3(24790) ******** INCOMMING CALL FROM TRUSTED IP ADDRESS
3(24790) INFO Checking ANI from Trusted IP
3(24790) INFO: ANI Verification successful for trusted IP
3(24790) ****** INCOMING CALL PASSED SECURITY CHECKS
3(24790) INFO: Begining attempt 1 DID route for trusted ip customer
3(24790) ****** FOUND DID TABLE ROUTE
23.581023 192.168.50.100 -> 192.168.20.10 SIP Status: 200 ok -- no more pending branches
25.451776 192.168.50.100 -> 10.1.2.3 SIP/SDP Request: INVITE sip:2015551212 at 10.1.2.3, with session description
29.458898 192.168.50.100 -> 10.1.2.3 SIP/SDP Request: INVITE sip:2015551212 at 10.1.2.3, with session description
33.466012 192.168.50.100 -> 10.1.2.3 SIP/SDP Request: INVITE sip:2015551212 at 10.1.2.3, with session description
37.473130 192.168.50.100 -> 10.1.2.3 SIP/SDP Request: INVITE sip:2015551212 at 10.1.2.3, with session description
40.479489 192.168.50.100 -> 192.168.20.10 SIP Status: 408 Request Timeout
40.487743 192.168.20.10 -> 192.168.50.100 SIP Request: ACK sip:2015551212;rn=2015550099;npdi=yes at 192.168.50.100;dtg=HSTNSIPORIG02;user=phone
10.1.2.3 is not a real node.. but it really does attempt to send a call there.. I'd like for it to attempt, die, and process the next route.
I've considered using t_on_failure, but it's not really what I want.. I want this failure to occur for any status >500 (ie: 5xx and 6xx) AND for dead SIP (ie, no SIP reply at all). t_on_failure will catch too much. Also, it takes too long to timeout.
I could have sworn I had this working with t_relay the other day. Am I doing something wrong? What is making it retry over and over?
Thanks,
Brett
More information about the sr-users
mailing list