RFC 3486:Compressing the Session Initiation Protoc...
RFC-Ref

Proxies


Click on the red underlined text to get to the source

... SIP entities exchanging compressed requests in one direction and uncompressed requests in the other direction) proxies need to rewrite their Record-Route entries in the responses. A proxy ...


... Although proxies usually add zero or one Record-Route entries to a particular request, some proxies ...
... proxies usually add zero or one Record-Route entries to a particular request, some proxies add two of them to avoid Record- Route rewriting. A typical example of double Record-Routing ...
... Record-Route header field on the response. Proxies that receive compressed messages from one side of the dialog (e.g., upstream) and uncompressed messages from the other side (e.g., ...


... handshake between a UAC and a UAS through two proxies. Proxy P1 does not Record-Route ...
... not Record-Route but proxy P2 does. Both proxies support compression, but they do not use it by default. ...
... Figure 1: INVITE transaction through two proxies Messages (1), (6) and (7) are compressed (c). ...



Google
Web
RFC-Ref