On Jun 22, 2009 at 11:38, Juha Heinanen jh@tutpro.com wrote:
while testing new version of lcr module, i got this kind of tm errors:
Jun 22 11:27:36 localhost /usr/sbin/sip-router[16330]: ERROR: tm [t_reply.c:1066]: ERROR: t_should_relay_response: status rewrite by UAS: stored: 408, received: 403 Jun 22 11:27:36 localhost /usr/sbin/sip-router[16329]: ERROR: tm [t_reply.c:1066]: ERROR: t_should_relay_response: status rewrite by UAS: stored: 408, received: 403 Jun 22 11:27:37 localhost /usr/sbin/sip-router[16331]: ERROR: tm [t_reply.c:1066]: ERROR: t_should_relay_response: status rewrite by UAS: stored: 408, received: 403 Jun 22 11:27:39 localhost /usr/sbin/sip-router[16331]: ERROR: tm [t_reply.c:1066]: ERROR: t_should_relay_response: status rewrite by UAS: stored: 408, received: 403
they came when i first called t_relay 4 times. first call was in route block and the rest in failure route block. there was no reply to any of these four calls and each time fr_timer hit. on fifth call, gw responded with 403.
i don't get these kind of errors in k. what do they mean and how to get rid of them?
They mean that after a final reply was received or "faked" (automatically generated locally) on a branch, a new different reply for the same branch was received. In all this cases the new reply is discarded. The error messages is printed for everything except the following 2 cases: initial final reply on branch was 487 or the final reply was 408 followed by a 487 (these are very common and happen in normal operation).
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.
You do not get this messages in k, because there the error message is enclosed by #ifdef EXTRA_DEBUG.
Andrei