[Spce-user] SIP ACK with changed Contact Header

[Daniel Grotti]

12.1.1 UAS behavior

   When a UAS responds to a request with a response that establishes a
   dialog (such as a 2xx to INVITE), the UAS MUST copy all Record-Route
   header field values from the request into the response (including the
   URIs, URI parameters, and any Record-Route header field parameters,
   whether they are known or unknown to the UAS) and MUST maintain the
   order of those values.  The UAS MUST add a Contact header field to
   the response.  The Contact header field contains an address where the
   UAS would like to be contacted for subsequent requests in the dialog
   (which includes the ACK for a 2xx response in the case of an INVITE).



Please note:

"The UAS MUST add a Contact header field to
   the response.The Contact header field contains an address where the
   UAS would like to be contacted for subsequent requests in the dialog
   (which includes the ACK for a 2xx response in the case of an INVITE)."


Daniel


On 02/04/2015 03:36 PM, Marc Storck wrote:
> Hello,
> 
> can anybody point me to the RFC that requires the SIP ACK to contain the identical Contact Header from the SIP 200 OK.
> 
> (SPCE ignores the SIP ACK and drops the call after 32 seconds, if contact header in SIP ACK differs from the one in SIP 200 OK).
> 
> Thanks for the help.
> 
> Regards,
> 
> Marc
> 
> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>