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? if so, could you backport the fix also to 1.4? -- juha _______________________________________________ Semsdev mailing list [email protected] http://lists.iptel.org/mailman/listinfo/semsdev
