From: Markus Hofmann <[EMAIL PROTECTED]> It stamps the via branch in the via header and creats an INVITE client transaction. All UAS will copy the Via header and when the provisional responses come back the transaction layer will not have any information if the INVITE was forked.
Provisional responses from different UASs will have different to-tags. Though it's not stated clearly in RFC 3261, each different to-tag creates a different early dialog, and each early dialog gets a clone of the state machine for processing its messages. And its messages are passed to the application code separately. Dale _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
