If the forking proxy knows the service that it is attempting to perform (i.e. group video only device with an audio device), it wouldn't send the immediate CANCEL even if rfc3261 or another RFC says it must or should. However there is little reason to discuss since the service is typically done with B2BUA for interoperability reasons.
> -----Original Message----- > From: Iñaki Baz Castillo [mailto:[email protected]] > Sent: Friday, March 19, 2010 8:12 AM > To: Brett Tate > Cc: Premalatha Kuppan; [email protected] > Subject: Re: [Sip-implementors] GRUU - SIP extension Basic questions > > 2010/3/19 Brett Tate <[email protected]>: > > It is standard service related forking. The issue is that the caller > likely won't keep both calls up after answer. > > The problem before it is the fact that when UAS-1 replies 200 the > forking proxy would inmediately cancel the second one, so just in the > exotic case both UAS-1 and UAS-2 reply at teh ***same*** time the 200, > both calls could be handled by the UAC. > > > -- > Iñaki Baz Castillo > <[email protected]> _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
