hi tanmay,
when the UAC recevies a 2xx, it initiates a new transaction for
ack, it moves to a confirmed state as it dosent have to wait for any
response form UAS( if it has to, to move to a conformed state it leads to
a well known Two army problem ). The UAS on the other had when it sends a
2xx, it waits for a ack in retrun to move to a confirmed state.
u r question was on the UAS not on the UAC( the UAC move to confirmed
state when it receives 2xx).
yes it is not clearly mentioned in the rfc in dialog chapter, but reading
the chapter on transactions (UAS behavior on INVITE) will give u a better
picture, usually in the rfc the flow is not continous.
regards
Naveen Pinto
Flextronics Software Systems
off: 91-080-51069025
mobile: 91-9448481804
Tanmay Paul/BLR/HSS
03/27/2006 12:54 PM
FSS-Unclassified
To
Jude Naveen Pinto/BLR/[EMAIL PROTECTED]
cc
[email protected], [EMAIL PROTECTED]
Subject
Re: [Sip-implementors] What is confirmed dialog for UAS.. is it after
sending final response or after receiving ACK for final response?
Hi Naveen,
Thank you for responding.
RFC 3261 says in chapter 12....
"A dialog can also be in the "early"
state, which occurs when it is created with a provisional response,
and then transition to the "confirmed" state when a 2xx final
response arrives. For other responses, or if no response arrives at
all on that dialog, the early dialog terminates."
So according to RFC when UAC receives final response for INVITE then
itself we can consider it as confirmed state for the the dialog.
RFC does not talk about ACK in this context. Please put some comment on
it.
Regards,
--Tanmay
Jude Naveen Pinto/BLR/HSS
03/27/2006 12:13 PM
FSS-Private
To
Tanmay Paul/BLR/[EMAIL PROTECTED]
cc
[email protected], [EMAIL PROTECTED]
Subject
Re: [Sip-implementors] What is confirmed dialog for UAS.. is it after
sending final response or after receiving ACK for final response?
hi tanmay,
these are some lines from chapter 12 of rfc 3261.
A dialog can also be in the "early"
state, which occurs when it is created with a provisional response,
and then transition to the "confirmed" state when a 2xx final
response arrives. For other responses, or if no response arrives at
all on that dialog, the early dialog terminates.
The UAC moves to a confirmed state only when it receives a 200 ok.
the UAS moves to a confirmed state only when it receives an ack from the
UAC , till then it retransmits 200 ok for unreliable transport for a time
out period. only when an ack is received a dialog is move a confirmed
state. to understand better u can go through transactions UAS behavior for
invite (17 chap) and UAS behavior in chapter 12.
regards
Naveen Pinto
Flextronics Software Systems
off: 91-080-51069025
mobile: 91-9448481804
Tanmay Paul/BLR/[EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
03/27/2006 11:21 AM
To
[email protected]
cc
Subject
[Sip-implementors] What is confirmed dialog for UAS.. is it after sending
final response or after receiving ACK for final response?
Hi All,
I have one doubt on the following issue. Could anyone please put
some light on it.
The scenario is as follows:
1] UAC initiates an INVITE towards UAS.
2] UAS respond with "100 Trying", "180 ringing" and "200 OK"
respectively.
3] Now before receiving ACK from UAC, UAS initiates a BYE.
Now according to RFC-3261 UAS can initiate BYE being only in confirmed
dialog. My doubt is should UAS consider it as confirmed dialog before
receiving ACK for 200 OK ?
Regards,
--Tanmay
*********************** FSS-Unclassified ***********************
"DISCLAIMER: This message is proprietary to Flextronics Software Systems
(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
*********************** FSS-Unclassified ***********************
"DISCLAIMER: This message is proprietary to Flextronics Software Systems (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
