The proxy sends this header in response to requests to communicate what it
requires of the user device when supporting a session.
It is different from the REQUIRE header, which is used between a client and a server
(non-proxies). The client and the server could be resident on two devices, or they could
be resident on application servers.
PROXY-REQUIRE:foo
Record-Route The RECORD-ROUTE header is used for strict routing within the IMS.
As a request is routed through the network, each proxy (CSCF or other entities such as
MGCFs) inserts this header along with its address into the request. When the request
is received by the destination, it uses the RECORD-ROUTE to send a response.
Think of RECORD-ROUTE as the header used to create a routing list for a subscriber
device. One use for this in the IMS prevents hijacking of sessions when routing is enforced.
When a device registers with the network, RECORD-ROUTE is used as the REGISTER
is routed through the network, and the various entities used to route the REGISTER to
the S-CSCF enter their addresses prior to forwarding to the next entity.
When the S-CSCF receives the REGISTER, it then uses the RECORD-ROUTE headers
to create a route list for the user. All responses are then sent using the same route
as recorded. This route is stored as part of the registration, so that all subsequent requests
and responses use the same route.
Pages:
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183