Hi,
I believe there is a bug on MESSAGE
forking.
Test scenario:
User A has two records in the location
table, with different instance ids: 111 and 222.
One of user A’s instance is killed, hence
222 is not reachable.
User B send a MESSAGE to user A.
Kamailio forked the MESSAGE.
Kamailio got a ‘200 Message delivered’
response from 111 and forwarded it to user B.
The MESSAGE forked to 222 timed out.
Kamailio send a ‘408 Time out’ to user B.
This violates RFC 3428 section 4. It states
that the forking UAS should only send ONE final response to
the sender UAC.
Forking is done by t_relay(), and the
registrar parameter ‘append_branches’ is set to default value
1.
Did I do something wrong, or there is a
bug?
Regards,
Allen