Your statement is essentially correct, however the last sentence is a little vague. More precisely, the different dialogs are created by the UA core as a result of multiple provisional responses passed to it by the client transaction created by the INVITE request.

Note that even after this transaction is terminated with a 2XX final response, it is still possible for additional dialogs to be created through receipt of additional 2XX responses from different UAs. This is due to the transport processing described in section 18.1.2 that will forward "stray" responses (i.e. responses for which there is no client transaction) to the UA core.

Regards,
Steve


Franz Edler wrote:


Hi all again,

just when I digged deeper into the protocol behavior I found the root of a
possible misunderstanding on my side, causing my previous question.

The principal question is now:

An INVITE request at a UAC creates exactly one transaction (one branch Id in
Via header). If several provisional responses from different UAS (different
To-tag) are received by the UAC each response creates a different dialog.
But these different dialogs are handled by exactly one transaction at the
UAC.

Please confirm my assumption.

Franz

_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors




_______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

Reply via email to