22 Jun
2009
22 Jun
'09
9:12 a.m.
Andrei Pelinescu-Onciul writes:
In your case the final reply is 408 (timeout) and the
new received one
is 403.
What might have happened is either the gw sent the 403 after the
fr_inv_timer did hit for the branch corresponding to your fifth call or
the gw sent the 403 for one of the previous branches, but it's hard to say
without more info.
andrei,
i set fr_timer_avp to 3000 (3 sec) before calling t_relay. i have
modparam("tm", "fr_inv_timer", 75000)
i have defined fr_inv_timer_avp, but it has not been given a value
during processing of this request. could the explanation be this:
k:
1.3.11. fr_timer_avp (string)
If you set the AVP to an empty string, the whole mechanism for
variable timeout will be disabled, falling back to the static
value.
sr:
1.3.29. fr_inv_timer_avp (string)
The value of fr_inv_timer timer can be overriden on per-transaction
basis. The administrator can provide a value to be used for a
particular transaction in an AVP. This parameter contains the name of
the AVP that will be checked. If the AVP exists then its value will be
used for the fr_inv_timer timer, effectively overriding the value
configured in fr_inv_timer parameter for the current transaction.
what does sr do if fr_inv_timer_avp exists, but is not set before
t_relay is called?
below is what comes to syslog.
-- juha
Jun 22 16:02:54 localhost /usr/sbin/sip-router[31499]: INFO: Routing initial INVITE to
<sip:0407058050@192.98.101.24:5060> and <<null>>
Jun 22 16:02:59 localhost /usr/sbin/sip-router[31514]: INFO: Routing next INVITE to
<sip:0407058050@192.98.101.21:5060>
Jun 22 16:03:04 localhost /usr/sbin/sip-router[31514]: INFO: Routing next INVITE to
<sip:0407058050@192.98.101.23:5060>
Jun 22 16:03:09 localhost /usr/sbin/sip-router[31514]: INFO: Routing next INVITE to
<sip:0407058050@192.98.101.22:5060>
Jun 22 16:03:14 localhost /usr/sbin/sip-router[31514]: INFO: Routing next INVITE to
<sip:0407058050@192.98.100.10:5060>
Jun 22 16:03:15 localhost /usr/sbin/sip-router[31499]: ERROR: tm [t_reply.c:1066]: ERROR:
t_should_relay_response: status rewrite by UAS: stored: 408, received: 403
Jun 22 16:03:15 localhost /usr/sbin/sip-router[31498]: ERROR: tm [t_reply.c:1066]: ERROR:
t_should_relay_response: status rewrite by UAS: stored: 408, received: 403
Jun 22 16:03:15 localhost /usr/sbin/sip-router[31500]: ERROR: tm [t_reply.c:1066]: ERROR:
t_should_relay_response: status rewrite by UAS: stored: 408, received: 403
Jun 22 16:03:18 localhost /usr/sbin/sip-router[31498]: ERROR: tm [t_reply.c:1066]: ERROR:
t_should_relay_response: status rewrite by UAS: stored: 408, received: 403
Jun 22 16:03:19 localhost /usr/sbin/sip-router[31514]: WARNING: No more gateways for
INVITE <sip:0407058050@192.98.101.24:5060>