The VIA header is never stored as part of the registration but
is only used for by proxies for routing.
VIA: SIP/2.0/UDP pchome101@aol.com:5060; branch= z9hG4bK713a2
Session Initiation Protocol (SIP) 83
Warning Warnings indicate problems in processing the session description itself. They are
different than error responses, since the session itself is being processed. The WARNING
header contains a text description identifying the purpose of the header as defined here:
?– 300 Incompatible network protocol
?– 301 Incompatible network address formats
?– 302 Incompatible transport protocol
?– 303 Incompatible bandwidth units
?– 304 Media type not available
?– 305 Incompatible media format
?– 306 Attribute not understood
?– 307 Session description parameter not understood
?– 330 Multicast not available
?– 331 Unicast not available
?– 370 Insufficient bandwidth
?– 399 Miscellaneous warning
The definition of these warnings is outside the scope of this book. Their use is defined
in RFC 3261. The preceding text values are suggested and not mandatory. Operators
can define their own text values for these warnings for their own implementations.
WARNING: 307 tekelec.com "Session parameter 'foo' not understood"
WWW-Authenticate This header is used as a challenge to an entity sending a request.
The challenge is carried in the response to a request with this header.
Pages:
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190