[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: Rick van Rein
Subject: Re: [Linphone-developers] ACK construction not compliant to RFC 3261
Date: Tue, 05 Jun 2012 15:15:57 +0200
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20120506 Icedove/3.0.11

Hi Ramon,
Beware: You are reading the rules for an ACK to a NON-200 response.
Indeed, I was reading in the wrong context.  Thanks for correcting me.
So you must follow the rules in Section 13 for the ACK.
Section 13 points back to section 12, where the applicable fragments seem to be:

   The UAC uses the remote target and route set to build the Request-URI
   and Route header field of the request.


   If the route set is not empty, and the first URI in the route set
   contains the lr parameter (see Section 19.1.1), the UAC MUST place
   the remote target URI into the Request-URI and MUST include a Route
   header field containing the route set values in order, including all

Furthermore, the remote target URI is updated by the Contact: header.  This
explains the behaviour of Linphone.  In other words, the fault lies with my
SIPproxy64 and/or the surrounding infra.


reply via email to

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