[Sip-implementors] Early Dialog Termination

[Anurag Chaudhry]

Hi All,

I want to know from both UAC and UAS prospective how to terminate the early dialog.

The Scenario is :

UAC Send INVITE with 100 Rel required header and UAS respond back with 183( reliable provisional response) to establish early dialog

Query

1) Can UAS use BYE to Terminate the dialog instead of error response?

2) Can UAC use BYE to TERMINATE instead of CANCEL ?

3) In this scenario do I need to support both CANCEL and BYE coming from UAC when my device is acting as a UAS ?

Thanks in Advance
Anurag
"DISCLAIMER: This message is proprietary to Aricent 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. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."

[Vivek Talwar]

Hi Anurag,

Kindly refer RFC for response 199 which is used to terminate early
dialog. This is extention and client need to first indicate that it
supports 199 response.

Thanks and Regards,
Vivek Talwar


On Fri, May 30, 2014 at 12:13 PM, Anurag Chaudhry <

Post by Anurag Chaudhry
Hi All,
I want to know from both UAC and UAS prospective how to terminate the early dialog.
UAC Send INVITE with 100 Rel required header and UAS respond back with
183( reliable provisional response) to establish early dialog
Query
1) Can UAS use BYE to Terminate the dialog instead of error response?
2) Can UAC use BYE to TERMINATE instead of CANCEL ?
3) In this scenario do I need to support both CANCEL and BYE coming
from UAC when my device is acting as a UAS ?
Thanks in Advance
Anurag
"DISCLAIMER: This message is proprietary to Aricent 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. Aricent 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
Sip-implementors at lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

[ankur bansal]

Hi Anurag

Lets take forking scenario
A calls B and proxy forked the call to B1 ,B2 .
A has established 2 early dialogs D1 ,D2 with B1 ,B2 respectively
Now B1 is busy so sent 486 response but B2 still ringing.



*> Query > > 1) Can UAS use BYE to Terminate the dialog instead of
error response?*


Server acting as UAS can send 199 response on getting 486 from B1 to inform
UAC that no need to terminate D1
and UAC can stop media session also for D1 .
But please note UAS here will be proxy only and not endpoint UE.


*> > 2) Can UAC use BYE to TERMINATE instead of CANCEL ?*

In case 199 came from proxy for D1 then UAC dont need to send CANCEL or BYE.
If user pressed endcall manually then anyway UAC should send CANCEL(no
to-tag) to end all legs possible
If UAC wants to terminate D1 without user intervention then UAC should send
BYE(to-tag of D1) in early dialog .



*> > 3) In this scenario do I need to support both CANCEL and BYE
coming > from UAC when my device is acting as a UAS ?*

Mostly CANCEL will come in early dialog and BYE in confirmed to UAS
So in case UAS send BYE to terminate early D1 ,proxy can absorb it and send
CANCEL to B1 .
Otherwise if BYE is being sent to B1 then UAS will still have INVITE
transaction pending till times out.
So ideally CANCEL should come to UAS from proxy so that 487 can be sent and
apart from dialog ,invite transaction too can be cleaned.


Thanks & regards
Ankur Bansal


On Fri, May 30, 2014 at 12:16 PM, Vivek Talwar <vivek.talwar at globallogic.com

Post by Vivek Talwar
Hi Anurag,
Kindly refer RFC for response 199 which is used to terminate early
dialog. This is extention and client need to first indicate that it
supports 199 response.
Thanks and Regards,
Vivek Talwar
On Fri, May 30, 2014 at 12:13 PM, Anurag Chaudhry <

Post by Anurag Chaudhry
Hi All,
I want to know from both UAC and UAS prospective how to terminate the early dialog.
UAC Send INVITE with 100 Rel required header and UAS respond back with
183( reliable provisional response) to establish early dialog
Query
1) Can UAS use BYE to Terminate the dialog instead of error

response?

Post by Anurag Chaudhry
2) Can UAC use BYE to TERMINATE instead of CANCEL ?
3) In this scenario do I need to support both CANCEL and BYE coming
from UAC when my device is acting as a UAS ?
Thanks in Advance
Anurag
"DISCLAIMER: This message is proprietary to Aricent and is intended

solely

Post by Anurag Chaudhry
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

Post by Anurag Chaudhry
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

Post by Anurag Chaudhry
not the intended recipient, you are notified that you are strictly
prohibited from using, copying, altering, or disclosing the contents of
this message. Aricent accepts no responsibility for loss or damage

arising

Post by Anurag Chaudhry
from the use of the information transmitted by this email including

damage

Post by Anurag Chaudhry
from virus."
_______________________________________________
Sip-implementors mailing list
Sip-implementors at lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

--
Name | Title
GlobalLogic
P +x.xxx.xxx.xxxx M +x.xxx.xxx.xxxx S skype
www.globallogic.com
<http://www.globallogic.com/>
http://www.globallogic.com/email_disclaimer.txt
_______________________________________________
Sip-implementors mailing list
Sip-implementors at lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

[Tarun2 Gupta]

Hi Anurag

See RFC 3261 Section 15 Terminating a Session

"The caller's UA MAY send a BYE for either confirmed or early dialogs, and the callee's UA MAY send a BYE on confirmed dialogs, but MUST NOT send a BYE on early dialogs."

Regards
Tarun Gupta


-----Original Message-----
From: sip-implementors-bounces at lists.cs.columbia.edu [mailto:sip-implementors-bounces at lists.cs.columbia.edu] On Behalf Of Anurag Chaudhry
Sent: Friday, May 30, 2014 12:13 PM
To: sip-implementors at lists.cs.columbia.edu
Subject: [Sip-implementors] Early Dialog Termination

Hi All,

I want to know from both UAC and UAS prospective how to terminate the early dialog.

The Scenario is :

UAC Send INVITE with 100 Rel required header and UAS respond back with 183( reliable provisional response) to establish early dialog

Query

1) Can UAS use BYE to Terminate the dialog instead of error response?

2) Can UAC use BYE to TERMINATE instead of CANCEL ?

3) In this scenario do I need to support both CANCEL and BYE coming from UAC when my device is acting as a UAS ?

Thanks in Advance
Anurag
"DISCLAIMER: This message is proprietary to Aricent 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. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."