Rayees Khan wrote:
>
> Hi Troy,
>
> Section 15 of RFC 3261 mentions that BYE terminates the whole dialog.
> Since, all the transactions (including re-INVITE) are aprt of the same
> dialog, BYE would terminate all of them.
I disagree. Terminating a dialog does not terminate *any* transactions.
If it did there would be no response to BYE.
Each transaction must be terminated. Now it may happen that upon
receiving a BYE, the UAS decides to abort an outstanding transaction
with a 487. When the UAC receives the 487 it can consider the
transaction terminated. In the absence of that it will need to cancel
the transaction or wait for it to timeout.
Paul
> regards
> Rayees
>
> [EMAIL PROTECTED] wrote: -----
>
> To: [email protected]
> From: Troy Cauble <[EMAIL PROTECTED]>
> Sent by: [EMAIL PROTECTED]
> Date: 03/07/2006 04:34PM
> Subject: [Sip-implementors] re-INVITE PROCEEDING state complications
>
> Hi all,
>
> I'm trying to understand the apparently timerless PROCEEDING
> state of the INVITE client transaction when sending re-INVITEs.
>
> Case 1)
> Assume that a UA has sent a re-INVITE within a dialog and
> received a 100 response, putting it in the PROCEEDING state.
> Then it sends a BYE.
>
> Should it send a CANCEL for the re-INVITE transaction as well,
> or is the BYE for the dialog sufficient?
>
> If not, it should receive 200(BYE) and 487(INVITE) anyway
> (according to 15.1.2).
>
> But if UA A never receives a final response to the re-INVITE,
> when can it discard the INVITE transaction state?
> This is answered (in 9.1) if CANCEL is sent. But I'm not
> sure if CANCEL should be sent.
>
>
> Case 2)
> Assume that a UA has sent a re-INVITE within a dialog and
> received a 100 response, putting it in the PROCEEDING state.
> Then it receives a BYE.
>
> Should it also receive a final response to the re-INVITE?
> If it doesn't, when can it discard the INVITE transaction state?
>
>
> Thanks,
> -troy
>
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
>
>
> *****FSS-Private *****" DISCLAIMER: This message is proprietary to
> Flextronics Software Systems Limited (FSS) and is intended solely for
> the use of the individual to whom it is addressed. It may contain
> privileged or confidential information and should not be circulated or
> used for any purpose other than for what it is intended. If you have
> received this message in error, please notify the originator
> immediately. If you are not the intended recipient, you are notified
> that you are strictly prohibited from using, copying, altering, or
> disclosing the contents of this message. FSS accepts no responsibility
> for loss or damage arising from the use of the information transmitted
> by this email including damage from virus."
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
