[SR-Users] MESSAGE forking bug(?)

Daniel-Constantin Mierla miconda at gmail.com
Wed Jul 23 12:41:28 CEST 2014


Hello,

can you get the sip traffic with ngrep on kamailio server? It can be 
taken with:

ngrep -d any -qt -W byline port 5060

Cheers,
Daniel

On 23/07/14 03:08, Allen Zhang wrote:
>
> 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
>
>
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20140723/4456c8bd/attachment.html>


More information about the sr-users mailing list