Hi experts, I need some clarification or confirmation on the UAC behavior in case of forking.
A UAC receives provisional responses (e.g. 180 Ringing) from different UAS and creates an early dialog for each of these responses. This is typical in case of forking. When the UAC receives a 200 OK response for one of the early dialogs this early dialog transitions to confirmed state. The question is now: What happens to the remaining early dialogs? In my picture these other early dialogs are canceled by the forking proxy according to RFC 3261 para 16.7 step 10. Within the UAC no other activity is necessary: the early dialogs are terminated by timeout. Is timer B responsible for this silent termination within the UAC? This is not clear documented in Figure 5 (proceeding state). Please help me clarify the behavior. Franz _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
