[asterisk-dev] [Code Review] SIP: transaction matching using top most Via header

[Klaus Darilion]

Am 13.07.2010 15:43, schrieb Kevin P. Fleming:
>> incoming request do not generate forked calls - only outgoing requests
>> >  may result in multiple responses from different UAS.
>> >
>> >  I wonder why not using the standard approach as defined in RFC:
>> >  branch-parameter -->  transaction matching.
>> >  callid + fromtag + totag -->  dialog matching
> Asterisk can be the*recipient*  of multiple forks of the same request,
> which is what this patch is trying to address. We are not talking about
> forked*responses*  (which is the outgoing request scenario), but forked
> *requests*.

Ah, I see.
Looks like too much SIP causes permanent damage to my brain :-)

Sorry for the noise,
Klaus