client
Click on the red underlined text to get to the source
... SRV [5] records are available for the server, the client can specify
the type of service it wants. The service ...
... next-hop URI contains the parameter comp=sigcomp, the client
SHOULD compress the request using SigComp as defined in [2 ...
... layer.
A client MUST NOT send a compressed request to a server if it does
not know whether or not the server supports SigComp.
...
...
Regardless of whether the request is sent compressed or not, if a
client would like to receive subsequent requests within the same
dialog in the UAS->UAC ...
... dialog in the UAS->UAC direction compressed, this client SHOULD add
the parameter comp=sigcomp to the URI ...
... URI in the Contact header field if
it is a user agent client. If the client is a proxy, it SHOULD add
...
... header field if
it is a user agent client. If the client is a proxy, it SHOULD add
the parameter comp=sigcomp ...
... Record-Route header
field.
If a user agent client sends a compressed request, it SHOULD add the
parameter comp=sigcomp to the URI ...
... Record-Route header field.
If a client sends a compressed request, it SHOULD add the parameter
comp=sigcomp to the topmost entry of the Via header field ...
... header field.
If a client does not know whether or not the server supports SigComp,
but in case the server supported it, it would like to receive
...
... SigComp,
but in case the server supported it, it would like to receive
compressed responses, this client SHOULD add the parameter
comp=sigcomp to the topmost entry of the Via header field ...
... Route header field when the
dialog is established. A client sending a request outside a dialog
can also obtain SIP URIs ...
... in a 3xx or 485 response to the request.
However, clients establishing a session will not typically be willing
to wait until the dialog is established in order to begin compressing
...
... INVITE of a dialog, when the user
is waiting for the session to be established. Therefore, clients
need a means to obtain a comp=sigcomp URI ...
... One solution to this problem is manual configuration. However,
sometimes it is necessary to have clients configured in an automatic
fashion. Unfortunately, current mechanisms for SIP client ...
... clients configured in an automatic
fashion. Unfortunately, current mechanisms for SIP client
configuration (e.g., using DHCP [6 ...
... 6]) do not allow to provide the
client with URI parameters. In this case, the client SHOULD send an
...
... client with URI parameters. In this case, the client SHOULD send an
uncompressed OPTIONS request to its outbound proxy. The outbound
proxy ...
... parameter in a Contact header field in a 200 OK response to the
OPTIONS. The client can use this URI for subsequent requests that
are sent through the same outbound proxy ...
... Sending a Response to a Client ...
... URI of the next upstream
(closer to the user agent client) hop in the route set. If this URI
...
... understand SigComp, the server will not have any means to indicate
the error to the client. The message will be impossible to parse,
and there will be no Via header field indicating an address ...
... If a SIP client sends a compressed request and the client transaction
times out without having received any response, the client ...
... client transaction
times out without having received any response, the client SHOULD
retry the same request without using compression. If the compressed
...
... compression. If the compressed
request was sent over a TCP connection, the client SHOULD close that
connection and open a new one to send the uncompressed request.
...