[Kamailio-Users] Strange behaviour when RADIUS server is down

[Antonio Reale]

2009/3/10 Juha Heinanen <jh at tutpro.com>:

> radius accounting is different from other radius modules, because in acc
> module, accounting is triggered by tm module.
[CUT]

OK. So this can be the relationship between the accounting and the
delay relaying SIP messages. Is that so?

> if sending of radius accounting request fails, it should not fail the
> transaction.  i have not tested if it does.

I think that it doesn't fail the transaction but it affect the
signaling. Attached the short wireshark trace when reproduced the
issue in lab with RADIUS server down.
In the trace I see about 10 seconds between the reception and the
relay of the ACK by kamailio (maybe "radius_timeout  10" in
radiusclient.conf ?)
P.S.: in the trace you see only two IP addresses because both clients
are on 10.10.45.86...

> -- juha
>

Thank you for your help.
Regards.
Antonio.
-------------- next part --------------
266.595644  10.10.45.86 -> 10.10.45.227 SIP/SDP Request: INVITE sip:0001 at sipsvr, with session description
266.596349 10.10.45.227 -> 10.10.45.86  SIP Status: 100 Trying
266.596622 10.10.45.227 -> 10.10.45.86  SIP Status: 407 Proxy Authentication Required
266.742942  10.10.45.86 -> 10.10.45.227 SIP Request: ACK sip:0001 at sipsvr
266.743229  10.10.45.86 -> 10.10.45.227 SIP/SDP Request: INVITE sip:0001 at sipsvr, with session description
266.744062 10.10.45.227 -> 10.10.45.86  SIP Status: 100 Trying
266.765982 10.10.45.227 -> 10.10.45.86  SIP/SDP Request: INVITE sip:0001 at 10.10.45.86:6452;rinstance=b10d43f4f45e87b3, with session description
266.869216  10.10.45.86 -> 10.10.45.227 SIP Status: 180 Ringing
266.870041 10.10.45.227 -> 10.10.45.86  SIP Status: 180 Ringing
268.981853  10.10.45.86 -> 10.10.45.227 SIP/SDP Status: 200 OK, with session description
268.983385 10.10.45.227 -> 10.10.45.86  SIP/SDP Status: 200 OK, with session description
269.133645  10.10.45.86 -> 10.10.45.227 SIP Request: ACK sip:0001 at 10.10.45.86:6452;rinstance=b10d43f4f45e87b3
269.585376  10.10.45.86 -> 10.10.45.227 SIP/SDP Status: 200 OK, with session description
270.591198  10.10.45.86 -> 10.10.45.227 SIP/SDP Status: 200 OK, with session description
272.603137  10.10.45.86 -> 10.10.45.227 SIP/SDP Status: 200 OK, with session description
276.626450  10.10.45.86 -> 10.10.45.227 SIP/SDP Status: 200 OK, with session description
280.650183  10.10.45.86 -> 10.10.45.227 SIP/SDP Status: 200 OK, with session description
284.673821  10.10.45.86 -> 10.10.45.227 SIP/SDP Status: 200 OK, with session description
288.697243  10.10.45.86 -> 10.10.45.227 SIP/SDP Status: 200 OK, with session description
292.720868  10.10.45.86 -> 10.10.45.227 SIP/SDP Status: 200 OK, with session description
296.744437  10.10.45.86 -> 10.10.45.227 SIP/SDP Status: 200 OK, with session description
298.981982 10.10.45.227 -> 10.10.45.86  SIP Request: ACK sip:0001 at 10.10.45.86:6452;rinstance=b10d43f4f45e87b3
298.983158 10.10.45.227 -> 10.10.45.86  SIP/SDP Status: 200 OK, with session description
298.986003 10.10.45.227 -> 10.10.45.86  SIP/SDP Status: 200 OK, with session description
298.987503 10.10.45.227 -> 10.10.45.86  SIP/SDP Status: 200 OK, with session description
298.994592 10.10.45.227 -> 10.10.45.86  SIP/SDP Status: 200 OK, with session description
298.995771 10.10.45.227 -> 10.10.45.86  SIP/SDP Status: 200 OK, with session description
298.996967 10.10.45.227 -> 10.10.45.86  SIP/SDP Status: 200 OK, with session description
299.004465 10.10.45.227 -> 10.10.45.86  SIP/SDP Status: 200 OK, with session description
299.006001 10.10.45.227 -> 10.10.45.86  SIP/SDP Status: 200 OK, with session description
299.016219 10.10.45.227 -> 10.10.45.86  SIP/SDP Status: 200 OK, with session description
299.069145  10.10.45.86 -> 10.10.45.227 SIP Request: ACK sip:0001 at 10.10.45.86:6452;rinstance=b10d43f4f45e87b3
299.070903 10.10.45.227 -> 10.10.45.86  SIP Request: ACK sip:0001 at 10.10.45.86:6452;rinstance=b10d43f4f45e87b3