On 29.02.2012, at 21:29, Juha Heinanen wrote:

> i noticed that when my proxy forks the same invite request twice to sems
> sbc, it responds to the second invite with '492 loop detected'.
> 
> wireshark shows that the two invites have different request uri
> host:port and different topmost via branch param.
> 
> this is with sems version 1.4.  has this been fixed in master branch?

Yes, it is. Here is the SHA 1e56183392f53c476ba592f44f3f7013c4f7b2ec.

> if so, could you backport the fix also to 1.4?
> 

Basically, it should be fairly easy if you need it. It is about cherry-picking 
following commits:
1e56183392f53c476ba592f44f3f7013c4f7b2ec
863fe68cbae0a151709a5b5de3162f2eb759dde3

Cheers
Raphael.

> -- juha
> _______________________________________________
> Semsdev mailing list
> [email protected]
> http://lists.iptel.org/mailman/listinfo/semsdev

_______________________________________________
Semsdev mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/semsdev

Reply via email to