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

UAS


Click on the red underlined text to get to the source

... client would like to receive subsequent requests within the same dialog in the UAS->UAC direction compressed, this client SHOULD add ...


... handshake between a UAC and a UAS through two proxies. Proxy P1 does ...
... UAC P1 P2 UAS |(1)INVITE ...
... (1) INVITE UAS Via: UAC;comp=sigcomp ...
... (2) INVITE UAS Via: P1 Via: UAC ...
... (3) INVITE UAS Via: P2 Via: P1 ...
... P2 forwards the INVITE (3) to the UAS. P2 supports compression, but it does not use it by default. Therefore, it sends the INVITE ...
... Record-Route: P2 Contact: UAS The UAS ...
... UAS The UAS generates a 200 OK response and sends it to the host in the topmost Via, which is P2. ...
... Record-Route: P2;comp=sigcomp Contact: UAS P2 receives the 200 OK response. P2 Record-Routed, so it inspects ...
... P2 receives the 200 OK response. P2 Record-Routed, so it inspects the Route set for this dialog. For requests from the UAS towards the UAC (the opposite direction than the first INVITE ...
... Record-Route: P2;comp=sigcomp Contact: UAS P1 sends the 200 OK (6) compressed to the UAC ...
... (7) ACK UAS Via: UAC;comp=sigcomp ...
... (8) ACK UAS Via: P2 Via: UAC ...
... P2 sends the ACK (8) uncompressed to the UAS. ...



Google
Web
RFC-Ref