header
Click on the red underlined text to get to the source
... URI and servers send
responses to the host in the sent-by parameter of the Via header
field.
We define two parameters, one for SIP ...
... SIP URIs and the other for the Via
header field. The format of both parameters is the same, as shown in
the examples below:
...
... 2].
The presence of comp=sigcomp in a Via header field indicates that the
response has to be compressed using SigComp.
...
... SIP entity
identified by the URI or by the Via header field supports SigComp and
is willing to receive compressed messages. Having comp=sigcomp ...
... the parameter comp=sigcomp to the URI in the Contact header field if
it is a user agent client. If the client ...
... the parameter comp=sigcomp to its URI in the Record-Route header
field.
If a user agent client ...
... parameter comp=sigcomp to the URI in the Contact header field. If a
proxy that Record-Routes sends a compressed request, it SHOULD add
...
... client sends a compressed request, it SHOULD add the parameter
comp=sigcomp to the topmost entry of the Via header field.
If a client ...
... client SHOULD add the parameter
comp=sigcomp to the topmost entry of the Via header field. The
request, however, as stated above, will not be compressed.
...
... parameter is obtained from a Record-Route header field when the
dialog is established. A client sending a request outside a dialog
...
... SIP URIs with comp=sigcomp in a Contact header field
in a 3xx or 485 response to the request.
...
... SIP URI with the comp=sigcomp
parameter in a Contact header field in a 200 OK response to the
OPTIONS. The client can use this URI ...
... says:
Contact header fields MAY be present in a 200 (OK) response and
have the same semantics as in a 3xx response. That is, they may
...
... A response is sent to the host in the sent-by parameter of the Via
header field. If the topmost Via header field contains the parameter
comp=sigcomp ...
... host in the sent-by parameter of the Via
header field. If the topmost Via header field contains the parameter
comp=sigcomp, the response SHOULD be compressed. Otherwise, the
...
... proxy performing Record-
Route inspects the Record-Route header field in the response and the
Contact header field in the request that triggered this response (see
...
... Route inspects the Record-Route header field in the response and the
Contact header field in the request that triggered this response (see
example in Section 9). It looks for the URI of the next upstream ...
... proxy SHOULD add
comp=sigcomp to its entry in the Record-Route header field. If this
URI does not contain the parameter comp=sigcomp ...
... sigcomp (if it is present) from its entry in the Record-
Route header field.
The same way, a user agent server ...
... user agent server SHOULD add comp=sigcomp to the
Contact header field of the response if the URI of the next upstream
...
... interface.
This way, the proxy does not need to rewrite the Record-Route header
field on the response.
Proxies ...
... the error to the client. The message will be impossible to parse,
and there will be no Via header field indicating an address to send
an error response ...
... Record-Route and
Contact header fields. We have not used a correct format for these
header fields. We have rather focus on the contents of the header
fields ...
... Contact header fields. We have not used a correct format for these
header fields. We have rather focus on the contents of the header
fields and on the presence (or absence) of the "comp=sigcomp"
...
... header fields. We have not used a correct format for these
header fields. We have rather focus on the contents of the header
fields and on the presence (or absence) of the "comp=sigcomp"
parameter.
...
... INVITE), the next hop will
be the Contact header field of the INVITE, because P1 did not
Record-Route ...
... requests (Record-Route of the 200 OK). Therefore, P2 modifies its
entry in the Record-Route header field of the 200 OK (5). In the
INVITE (3), P2 did not used the comp=sigcomp ...
...
P1 sends the 200 OK (6) compressed to the UAC because the Via header
field contained the comp=sigcomp parameter.
...