kowsalya | 1 Dec 2003 06:11

RE: Query on PRACK

Gokul,
 
PRACK is just like any other non-INVITE transaction and hence does not require an ACK by UAC.
 
1. UAC sends an INVITE
2. UAS responds with a reliable provisional response
3. UAC sends a PRACK
4. UAS responds to PRACK with a 200 OK
5. UAS sends 200 OK for INVITE
6. UAC sends ACK for the original INVITE transaction
 
Thanks
Kowsalya
 
 
-----Original Message-----
From: Gokul Krishnan [mailto:gktvm2 <at> yahoo.com]
Sent: Saturday, November 29, 2003 5:44 PM
To: sip <at> ietf.org
Subject: [Sip] Query on PRACK

Hi All,
 
Does PRACK trigger another 2XX response ? If yes, does that mean UAC should send an ACK? Can any one please provide a message sequence flow?
 
  If a PRACK request is received by the UA core that does not
  match any unacknowledged reliable provisional response, the
  UAS MUST respond to the PRACK with a 481 response.  If the
  PRACK does match an unacknowledged reliable provisional
  response, it MUST be responded to with a 2xx response. 
  (RFC 3262, Page 5)
Thanks and Regards
Gokul

Do you Yahoo!?
Free Pop-Up Blocker - Get it now
Tolga Asveren | 1 Dec 2003 15:18
Favicon

remote terget update

(due to no response in sip-implementors list switching to sip list)
 
If a reINVITE with target refresh rejected, should remote target reverted back to its original value before that reINVITE is received?
 
  Tolga
Rosen, Brian | 1 Dec 2003 15:34

RE: Session timer question

You send 420  - Bad Extension, because you don't understand the
timer option in the Require.  See section 8.2.2.3 in RFC3261.

Brian
-----Original Message-----
From: vhegde <at> san.rr.com [mailto:vhegde <at> san.rr.com]
Sent: Friday, November 28, 2003 9:13 PM
To: sip <at> ietf.org
Subject: [Sip] Session timer question

Hi:
I have a question on session timer message flow.

 If a UA does not support session timer and if it receives 

Require: timer
Session Expires: 3600 

in the 200 OK to re-INVITE what is the correct way to process this response?

Should UAC Ack the 200 OK and then send a bye or ignore the Require and
session Expires: headers and continue with rest of the processing?

Veda

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors <at> cs.columbia.edu for questions on current sip
Use sipping <at> ietf.org for new developments on the application of sip

Paul Kyzivat | 1 Dec 2003 16:36
Picon
Favicon

Re: Session timer question

Brian,

The question was about a Require in a 200 response to an invite. The UAC 
clearly can't return a 420 in that case.

I don't think any valid usage of session timer will ever result in this 
case. The only cases where Require: timer is validly put into the 
response are when the request contained Supported: timer.

So this can only result from a broken proxy or UAS. In this case I think 
the UAC is justified in either sending an ACK and then BYE as you 
suggest, or else just ignoring the Required: timer.

	Paul

Rosen, Brian wrote:
> You send 420  - Bad Extension, because you don't understand the
> timer option in the Require.  See section 8.2.2.3 in RFC3261.
> 
> Brian
> -----Original Message-----
> From: vhegde <at> san.rr.com [mailto:vhegde <at> san.rr.com]
> Sent: Friday, November 28, 2003 9:13 PM
> To: sip <at> ietf.org
> Subject: [Sip] Session timer question
> 
> 
> Hi:
> I have a question on session timer message flow.
> 
>  If a UA does not support session timer and if it receives 
> 
> Require: timer
> Session Expires: 3600 
> 
> in the 200 OK to re-INVITE what is the correct way to process this response?
> 
> 
> Should UAC Ack the 200 OK and then send a bye or ignore the Require and
> session Expires: headers and continue with rest of the processing?
> 
> Veda
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors <at> cs.columbia.edu for questions on current sip
> Use sipping <at> ietf.org for new developments on the application of sip
> 

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors <at> cs.columbia.edu for questions on current sip
Use sipping <at> ietf.org for new developments on the application of sip

Paul Kyzivat | 1 Dec 2003 16:38
Picon
Favicon

Re: remote terget update


Tolga Asveren wrote:
> (due to no response in sip-implementors list switching to sip list)
>  
> If a reINVITE with target refresh rejected, should remote target 
> reverted back to its original value before that reINVITE is received?

Yes, 3261 seems pretty clear on this.

	Paul

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors <at> cs.columbia.edu for questions on current sip
Use sipping <at> ietf.org for new developments on the application of sip

Gokul Krishnan | 1 Dec 2003 17:43
Picon
Favicon

Query on Extensions

Hi All,
 
What is the difference between "Allow" and "Supported" header from a usage perspective?
 
As an example, for PRACK an UAC sends Supported:100rel (RFC 3262) and for UPDATE, the UAC is supposed to send Allow: UPDATE (RFC 3311).
 
What is the advantage/disadvantage of each approach?
 
Thanks and Regards
Gokul

Do you Yahoo!?
Free Pop-Up Blocker - Get it now
Paul Kyzivat | 1 Dec 2003 18:49
Picon
Favicon

Re: Query on Extensions


Gokul Krishnan wrote:
> Hi All,
>  
> What is the difference between "Allow" and "Supported" header *from a 
> usage perspective*?
>  
> As an example, for PRACK an UAC sends Supported:100rel (RFC 3262) and 
> for UPDATE, the UAC is supposed to send Allow: UPDATE (RFC 3311).

"Allow" identifies sip *methods* that the UA supports. "Supported" 
identifies named "packages" that the UA supports. The values are drawn 
from different namespaces.

> What is the advantage/disadvantage of each approach?

They aren't substitutes for one another. A package listed as Supported 
may require the use of certain methods. Those methods should also be 
listed in an Allow header.

An example of this is 100rel. You need to specify both Allow: UPDATE and 
Supported: 100rel to use reliable provisional responses.

	Paul

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors <at> cs.columbia.edu for questions on current sip
Use sipping <at> ietf.org for new developments on the application of sip

Veda Hegde | 1 Dec 2003 19:27
Picon

Re: Session timer question

Hi:
I don't think it says in the draft that a proxy/UAS can not put Require:
timer in 2xx, if UAC did not include Supported: timer in the request.
May be this should be specified in the draft.
Veda

----- Original Message -----
From: "Paul Kyzivat" <pkyzivat <at> cisco.com>
To: "Rosen, Brian" <Brian.Rosen <at> marconi.com>
Cc: <vhegde <at> san.rr.com>; <sip <at> ietf.org>
Sent: Monday, December 01, 2003 7:36 AM
Subject: Re: [Sip] Session timer question

> Brian,
>
> The question was about a Require in a 200 response to an invite. The UAC
> clearly can't return a 420 in that case.
>
> I don't think any valid usage of session timer will ever result in this
> case. The only cases where Require: timer is validly put into the
> response are when the request contained Supported: timer.
>
> So this can only result from a broken proxy or UAS. In this case I think
> the UAC is justified in either sending an ACK and then BYE as you
> suggest, or else just ignoring the Required: timer.
>
> Paul
>
> Rosen, Brian wrote:
> > You send 420  - Bad Extension, because you don't understand the
> > timer option in the Require.  See section 8.2.2.3 in RFC3261.
> >
> > Brian
> > -----Original Message-----
> > From: vhegde <at> san.rr.com [mailto:vhegde <at> san.rr.com]
> > Sent: Friday, November 28, 2003 9:13 PM
> > To: sip <at> ietf.org
> > Subject: [Sip] Session timer question
> >
> >
> > Hi:
> > I have a question on session timer message flow.
> >
> >  If a UA does not support session timer and if it receives
> >
> > Require: timer
> > Session Expires: 3600
> >
> > in the 200 OK to re-INVITE what is the correct way to process this
response?
> >
> >
> > Should UAC Ack the 200 OK and then send a bye or ignore the Require and
> > session Expires: headers and continue with rest of the processing?
> >
> > Veda
> >
> > _______________________________________________
> > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> > This list is for NEW development of the core SIP Protocol
> > Use sip-implementors <at> cs.columbia.edu for questions on current sip
> > Use sipping <at> ietf.org for new developments on the application of sip
> >
>
>
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors <at> cs.columbia.edu for questions on current sip
> Use sipping <at> ietf.org for new developments on the application of sip
>

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors <at> cs.columbia.edu for questions on current sip
Use sipping <at> ietf.org for new developments on the application of sip

Drage, Keith (Keith | 1 Dec 2003 19:41
Picon
Favicon

RE: Session timer question

I think this is answered by subclause 8.2.4 of RFC 3261, viz:

8.2.4 Applying Extensions

   A UAS that wishes to apply some extension when generating the
   response MUST NOT do so unless support for that extension is
   indicated in the Supported header field in the request.  If the
   desired extension is not supported, the server SHOULD rely only on
   baseline SIP and any other extensions supported by the client.  In
   rare circumstances, where the server cannot process the request
   without the extension, the server MAY send a 421 (Extension Required)
   response.  This response indicates that the proper response cannot be
   generated without support of a specific extension.  The needed
   extension(s) MUST be included in a Require header field in the
   response.  This behavior is NOT RECOMMENDED, as it will generally
   break interoperability.

   Any extensions applied to a non-421 response MUST be listed in a
   Require header field included in the response.  Of course, the server
   MUST NOT apply extensions not listed in the Supported header field in
   the request.  As a result of this, the Require header field in a
   response will only ever contain option tags defined in standards-
   track RFCs.

regards

Keith

> -----Original Message-----
> From: Veda Hegde [mailto:vhegde <at> san.rr.com]
> Sent: 01 December 2003 18:27
> To: Paul Kyzivat; Rosen Brian
> Cc: sip <at> ietf.org
> Subject: Re: [Sip] Session timer question
> 
> 
> Hi:
> I don't think it says in the draft that a proxy/UAS can not 
> put Require:
> timer in 2xx, if UAC did not include Supported: timer in the request.
> May be this should be specified in the draft.
> Veda
> 
> 
> ----- Original Message -----
> From: "Paul Kyzivat" <pkyzivat <at> cisco.com>
> To: "Rosen, Brian" <Brian.Rosen <at> marconi.com>
> Cc: <vhegde <at> san.rr.com>; <sip <at> ietf.org>
> Sent: Monday, December 01, 2003 7:36 AM
> Subject: Re: [Sip] Session timer question
> 
> 
> > Brian,
> >
> > The question was about a Require in a 200 response to an 
> invite. The UAC
> > clearly can't return a 420 in that case.
> >
> > I don't think any valid usage of session timer will ever 
> result in this
> > case. The only cases where Require: timer is validly put into the
> > response are when the request contained Supported: timer.
> >
> > So this can only result from a broken proxy or UAS. In this 
> case I think
> > the UAC is justified in either sending an ACK and then BYE as you
> > suggest, or else just ignoring the Required: timer.
> >
> > Paul
> >
> > Rosen, Brian wrote:
> > > You send 420  - Bad Extension, because you don't understand the
> > > timer option in the Require.  See section 8.2.2.3 in RFC3261.
> > >
> > > Brian
> > > -----Original Message-----
> > > From: vhegde <at> san.rr.com [mailto:vhegde <at> san.rr.com]
> > > Sent: Friday, November 28, 2003 9:13 PM
> > > To: sip <at> ietf.org
> > > Subject: [Sip] Session timer question
> > >
> > >
> > > Hi:
> > > I have a question on session timer message flow.
> > >
> > >  If a UA does not support session timer and if it receives
> > >
> > > Require: timer
> > > Session Expires: 3600
> > >
> > > in the 200 OK to re-INVITE what is the correct way to process this
> response?
> > >
> > >
> > > Should UAC Ack the 200 OK and then send a bye or ignore 
> the Require and
> > > session Expires: headers and continue with rest of the processing?
> > >
> > > Veda
> > >
> > > _______________________________________________
> > > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> > > This list is for NEW development of the core SIP Protocol
> > > Use sip-implementors <at> cs.columbia.edu for questions on current sip
> > > Use sipping <at> ietf.org for new developments on the 
> application of sip
> > >
> >
> >
> > _______________________________________________
> > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> > This list is for NEW development of the core SIP Protocol
> > Use sip-implementors <at> cs.columbia.edu for questions on current sip
> > Use sipping <at> ietf.org for new developments on the application of sip
> >
> 
> 
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors <at> cs.columbia.edu for questions on current sip
> Use sipping <at> ietf.org for new developments on the application of sip
> 

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors <at> cs.columbia.edu for questions on current sip
Use sipping <at> ietf.org for new developments on the application of sip

Peterson, Jon | 1 Dec 2003 20:19
Favicon

RE: ENUM-support in SIP-protocol?


See:

http://www.ietf.org/internet-drafts/draft-ietf-sipping-e164-04.txt

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: Rene Bartsch [mailto:ml <at> bartschnet.de]
> Sent: Saturday, November 29, 2003 11:26 AM
> To: sip <at> ietf.org
> Subject: [Sip] ENUM-support in SIP-protocol?
> 
> 
> Hi,
> 
> first I'm new to the list, so hello to all! :-)
> 
> My question is if there is any draft of plan to implement ENUM-lookups 
> into the SIP-protocol?
> 
> Rene Bartsch
> 
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors <at> cs.columbia.edu for questions on current sip
> Use sipping <at> ietf.org for new developments on the application of sip
> 

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors <at> cs.columbia.edu for questions on current sip
Use sipping <at> ietf.org for new developments on the application of sip


Gmane