[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Linphone-developers] ACK construction not compliant to RFC 3261

From: Aymeric Moizard
Subject: Re: [Linphone-developers] ACK construction not compliant to RFC 3261
Date: Tue, 5 Jun 2012 15:02:15 +0200 (CEST)

On Tue, 5 Jun 2012, Rick van Rein wrote:



I ran into a problem with SIP that ended up being a flaw in LinPhone.

Version:        linphone 3.3.2
Variation:      console, linphonec (linphone-nox)
Platform:       Debian Squeeze
Transport:      UDP over IPv6

The ACK constructed in response to a "200 OK" contains a Request-URI that
seems to originate from the Contact: header.  This is incompatible with
RFC 3621 which states:

  The ACK request constructed by the client transaction MUST contain
  values for the Call-ID, From, and Request-URI that are equal to the
  values of those header fields in the request passed to the transport
  by the client transaction (call this the "original request").

This text relates to ACK for negative answer (between 300 and 699)! For ACK's 200ok, the construction is described in Section 13 and request-uri will -usually- comes from Contact header of previous 200ok.


amsip -
osip2 -
eXosip2 -

reply via email to

[Prev in Thread] Current Thread [Next in Thread]