No, the UAC should not send a BYE on the remaining early dialogs. If the request was forked, the proxy that forked the request would have sent CANCEL to the remaining branches upon receiving the 200-OK. Normally, those branches would return 487 which the proxy would not pass back to the UAC. The UAC has no way to know the state of those early dialogs, and it is safe assume that they were properly cancelled. If a particular early dialog was not cancelled, the only thing the UAC could possibly see would be a 200-OK (which the UAC ACKs) confirming the additional dialog. At that point, the UAC is free to continue that dialog or terminate by sending a BYE.
The UAS does not send BYE on early dialog. The case you site is were the UAS has sent a 200-OK (confirming the dialog), but has not received the ACK from the UAC. Thus the BYE is on a confirmed dialog (from the point of view of the UAS). cheers, (-:bob Robert F. Penfield Chief Software Architect Acme Packet, Inc. 71 Third Avenue Burlington, MA 01803 [EMAIL PROTECTED] ----- Original Message ----- From: "Jeroen van Bemmel" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Wednesday, August 31, 2005 3:52 PM Subject: [Sip-implementors] clarification of RFC3261 text 13.2.2.4 2xx Responses: [...] "The UAC core considers the INVITE transaction completed 64*T1 seconds after the reception of the first 2xx response. At this point all the early dialogs that have not transitioned to established dialogs are terminated." Should the UAC send a BYE to terminate these early dialogs? In section 13.3.1.4 a UAS does, when it does not receive an ACK for 64*T1 Regards, Jeroen _______________________________________________ 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
