[reSIProcate] Request with non unique tid
Jason Fischl
jason at sipedge.com
Wed Sep 7 11:13:17 CDT 2005
On 9/7/05, Alexander Altshuler <alt at kaluga.ru> wrote:
> Hi All
>
> I have SIP client which generate (sometimes) non unique transaction id
> (branch parameter within Via header).
> I know it is wrong behavior.
> My resip based proxy respond for this request with previously sent response
> of first transaction.
> Nothing extremely bad, but I think if stack will respond with 400 Bad
> Request it will better.
>
> What do you think?
It is doing this because the second request is viewed as a
retransmission. I don't see a way to avoid this without looking at the
full contents of the message. Any ideas?
More information about the resiprocate-devel
mailing list