4 Nov
2011
4 Nov
'11
9:42 a.m.
This behavior is standard conform. The proxy must not forward the CANCEL
as it has not received a response to the INVITE yet. Further, the INVITE
transaction will be terminated only after the outgoing INVITE is
terminated, e.g. by the 408 timeout.
Usually you do not want to wait 30 seconds for the timeout to happen. I
for example limit it to 5 seconds using fr_timer:
http://kamailio.org/docs/modules/3.2.x/modules/tm.html#fr_timer
There are lots of other paramters to tweak tm module, e.g.:
http://kamailio.org/docs/modules/3.2.x/modules/tm.html#cancel_b_method
But the default settings are usually fine.
regards
Klaus
On 04.11.2011 14:06, Mino Haluz wrote:
Hi,
the scenario is like this:
- user1 makes a call to user2
- proxy sends receives INVITE and sends it to user2
- user2 does not respond at all (firewall for example)
- user1 after 5 seconds hangs up the call with CANCEL
- proxy sends to user1 200 canceling
CANCEL is not forwarded to user2. Ok this behaviour is maybe ok, but
after 30 seconds Request timed out is sent to user1 (fr_inv_timer
possibly hit). So if I am thinking well, first CANCEL did not match the
transaction ? Why ? It this behaviour ok or do I have to search for
something wrong in the config?
Thanks,
Mino
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users