Re: [Sip-implementors] change in tag field in To header

Ramesh, See inline. > -Original Message- > From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip- > implementors-boun...@lists.cs.columbia.edu] On Behalf Of Ramesh Babu > Kuppili > Sent: Wednesday, February 27, 2013 12:42 AM > To: Paul Kyzivat; sip-implementors@lists.cs.columbi

Re: [Sip-implementors] Race between re-registration and registration expiration

Please check RFC 3261 section 10.2.4 Refreshing Bindings Typically the endpoint should allow a full round trip delay before the REGISTER expires on the Registrar. It is implementation choice, and most of the clients re-register either half the interval in expiration, or 32 seconds prior to the

Re: [Sip-implementors] Should a proxy relay a second 200 for a SUBSCRIBE?

See inline. -Original Message- From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Iñaki Baz Castillo Sent: Thursday, August 16, 2012 7:05 AM To: sip-implementors@lists.cs.columbia.edu Subject: [Sip-implementors] Shoul

Re: [Sip-implementors] [RFC 3261] Priority header value

Reading RFC 3261 and RFC 2076, which references to RFC 1327. As there are no semantics defined, it is up to the endpoint to process the way it wants. >From RFC 3261: Section 20.26 The header field can have the values "non-urgent", "normal", "urgent", and "emergency", but additional val

Re: [Sip-implementors] Regarding SDP attributes

See inline. Thanks, Neel. > -Original Message- > From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip- > implementors-boun...@lists.cs.columbia.edu] On Behalf Of Abhishek Lal > Sent: Tuesday, March 06, 2012 6:54 PM > To: sip-implementors@lists.cs.columbia.edu > Subject: [Sip-i

Re: [Sip-implementors] Significance of ACK in SIP

Please read RFC 3261. You should read section 4 Overview of Operation and other places where ACK usage is discussed. For example, Offer/Answer exchanges can happen in 200 OK and ACK. Thanks, Neel. > -Original Message- > From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip-

Re: [Sip-implementors] Security issue in SIPconnect 1.1?

See Inline. Thanks, Neel. > -Original Message- > From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip- > implementors-boun...@lists.cs.columbia.edu] On Behalf Of Olle E. > Johansson > Sent: Friday, December 16, 2011 6:35 AM > To: sip-implementors@lists.cs.columbia.edu sip- > i

Re: [Sip-implementors] Query regarding Session timer

> -Original Message- > From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip- > implementors-boun...@lists.cs.columbia.edu] On Behalf Of Chandan Kumar > Sent: Monday, March 28, 2011 1:12 PM > To: sip-implementors@lists.cs.columbia.edu > Subject: [Sip-implementors] Query regardi

Re: [Sip-implementors] sip request-uri

Read the parts of RFC 3261 that describe the maddr. A client that sends a request to a multicast address MUST add the "maddr" parameter to its Via header field value containing the destination multicast address, and for IPv4, SHOULD add the "ttl" parameter with a value of 1. Usage o

Re: [Sip-implementors] How to convert String to SIPMessage

Probably you should try posting this to JainSIP mailing list? Thanks, neel -Original Message- From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Prem chandiran Sent: Saturday, March 12, 2011 8:29 AM To: sip-implement

Re: [Sip-implementors] SIP message size

It is given in the section 18.1.1 If a request is within 200 bytes of the path MTU, or if it is larger than 1300 bytes and the path MTU is unknown, the request MUST be sent using an RFC 2914 [43] congestion controlled transport protocol, such as TCP. If this causes a change in the trans

Re: [Sip-implementors] Direction attributes in SDP

You may want to see RFC 4566. The direction is both Session and Media level. So, it can be passed for multiple media descriptions. Thanks, Neel. > -Original Message- > From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip- > implementors-boun...@lists.cs.columbia.edu] On B

Re: [Sip-implementors] ACK cannot stop the flood of 200 OK from sipgate.com

Maybe the port number in contact has which might not be populated in the ACK. Is the call record routed? Are you populating the Route header? Is it possible to provide the packet capture? It is hard to diagnose without those. Please provide packet capture and it will help us to help you. Th

Re: [Sip-implementors] Offer-answer question

See below. > -Original Message- > From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip- > implementors-boun...@lists.cs.columbia.edu] On Behalf Of Michael > Hirschbichler > Sent: Friday, March 12, 2010 8:52 AM > Cc: sip-implementors@lists.cs.columbia.edu > Subject: Re: [Sip-imp

Re: [Sip-implementors] Mid call supported/require option tags modification

> -Original Message- > From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip- > implementors-boun...@lists.cs.columbia.edu] On Behalf Of Balu > Meenakshi-a24053 > Sent: Friday, March 12, 2010 12:22 AM > To: sip-implementors@lists.cs.columbia.edu > Subject: [Sip-implementors] Mi

Re: [Sip-implementors] Is anonymous user allowed in sip-uri with user=phone?

See below. -Original Message- From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Iñaki Baz Castillo Sent: Wednesday, January 13, 2010 2:54 PM To: sip-implementors@lists.cs.columbia.edu Subject: Re: [Sip-implementors]

Re: [Sip-implementors] What do you do with a REFER that arrives before an ACK.

See below. -Original Message- From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of M. Ranganathan Sent: Wednesday, January 13, 2010 1:37 PM To: sip-implementors Subject: [Sip-implementors] What do you do with a REFER th

Re: [Sip-implementors] Reg: session refresh

See below -Original Message- From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Sharanabasavaraj Mathapati Sent: Tuesday, December 29, 2009 8:00 AM To: sip-implementors@lists.cs.columbia.edu Subject: [Sip-implementor