Tate" wrote:
> See RFC 3261 section 9.2.
>
> ** **
>
> ** **
>
> *From:* Arun Arora [mailto:arun.arora@gmail.com]
> *Sent:* Tuesday, September 17, 2013 7:51 AM
> *To:* Brett Tate
> *Cc:* sip-implementors
> *Subject:* RE: [Sip-implementors] About
See RFC 3261 section 9.2.
From: Arun Arora [mailto:arun.arora@gmail.com]
Sent: Tuesday, September 17, 2013 7:51 AM
To: Brett Tate
Cc: sip-implementors
Subject: RE: [Sip-implementors] About Cancel a Dialog
So what I understand is if there is a use-case where CANCEL can be sent for
other
So what I understand is if there is a use-case where CANCEL can be sent for
other than non-INVITE method, that case should be clearly outlined... may
be a sip extension rfc which specifically standardizes such scenario.
Otherwise if not explicitely mentioned CANCEL should be ignored in case of
non-
> Is it possible to send a CANCEL request for non-INVITE
> requests as well? In section 9 its written CANCEL is
> best suited for INVITE. However the standard does not
> restrict CANCEL only for INVITE. Moreover, In 9.1 its
> written cancel SHOULD NOT be sent for requests other
> than INVITE. B
17 sep 2013 kl. 09:59 skrev Arun Arora :
> Hi all,
>
> Is it possible to send a CANCEL request for non-INVITE requests as well? In
> section 9 its written CANCEL is best suited for INVITE. However the
> standard does not restrict CANCEL only for INVITE. Moreover, In 9.1 its
> written cancel SHOU
: Arun Arora [mailto:arun.arora@gmail.com]
Sent: Tuesday, September 17, 2013 1:29 PM
To: Guan Xsun
Cc: sip-implementors
Subject: Re: [Sip-implementors] About Cancel a Dialog
Hi all,
Is it possible to send a CANCEL request for non-INVITE requests as well? In
section 9 its written CANCEL is best
Hi all,
Is it possible to send a CANCEL request for non-INVITE requests as well? In
section 9 its written CANCEL is best suited for INVITE. However the
standard does not restrict CANCEL only for INVITE. Moreover, In 9.1 its
written cancel SHOULD NOT be sent for requests other than INVITE. But to
m
Thank you very much!!!
2013/9/13 ankur bansal
> Hi Casey ,
>
> Like Satish mentioned 487 comes immediately but assuming it lost in
> network or UAS is RFC2543-compliant(cant generate 487).
>
> Even then we cannot terminate dialog on getting 200ok(Cancel) due to these
> reasons :
>
> 1. Cancel
Hi Casey ,
Like Satish mentioned 487 comes immediately but assuming it lost in network
or UAS is RFC2543-compliant(cant generate 487).
Even then we cannot terminate dialog on getting 200ok(Cancel) due to these
reasons :
1. Cancel can be triggered before any provisional response (having to-tag)
Hello Casey,
As per RFC 3261 section 9.2
If the UAS did not find a matching transaction for the CANCEL
according to UAS first processes the CANCEL request, it SHOULD
respond to the CANCEL
with a 481 (Call Leg/Transaction Does Not Exist). If the transaction
for the original request st
heHi,
A SIP client create a dialog by sending INVITE and then will cancel it.
Whether the dialog can be finished when the dialog receive the 200 OK
from cancel or it needs receive the 487 message ?
Best Regards!
Casey
___
Sip-implementors maili
11 matches
Mail list logo
