com,"
domain= "sip:Verizon.com", qop="auth",
nonce= "a73dd646abc898763fbade98129e763547",
opaque= "", stale= FALSE, algorithm= MD5
Proxy-Authorization The PROXY-AUTHORIZATION header is used when a device is authenticating
itself with the challenging proxy in response to a 407 Proxy Authentication
Required. It is within this header that the user provides his or her credentials, known
only to the device and the network provider.
None of the data provided for authentication is human-consumable data. This is
data that is created using the various algorithms and keys that are provided by the
Session Initiation Protocol (SIP) 79
network provider at subscription time and embedded within the device (usually within
the UICC or SIM card).
This process is different than registration, where the network registrar performs the
authentication. This procedure and its associated headers provide the operator with
an added measure of security to prevent unauthorized access to network services, even
after registration.
The use of this header is implementation specific and is not required, but it does add
an additional level of security for the operator and an additional layer of protection to
select services housed on application servers.
PROXY-AUTHORIZATION:Digest username= "Travis", realm= "Verizon.com",
Nonce= "c60f3082ee1212b402a21831ae"
Response= "43536ff4355tcc45567"
Proxy-Require This is similar to the REQUIRE header, except that it is used by proxies
to communicate the extensions and capabilities that must be supported by the
device.
Pages:
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182