Table Of Contents
Cisco SIP Proxy Server (CSPS) Compliance Information
SIP Compliance with RFC 2543
SIP Functions
SIP Methods
SIP Responses
1xx Response—Information Responses
2xx Response—Successful Responses
3xx Response—Redirection Responses
4xx Response—Request Failure Responses
5xx Response—Server Failure Responses
6xx Response—Global Responses
SIP Header Fields
Transport Layer Protocols
SIP Security
Authentication
SIP DNS Records Usage
Cisco SIP Proxy Server (CSPS) Compliance Information
This appendix describes how the CSPS complies with the IETF definition of SIP (Internet Draft draft-ietf-sip-rfc2543bis-04.txt, based on RFC 2543). It also provides an overview of SIP services.
SIP Compliance with RFC 2543
This section contains compliance information on the following:
•
SIP Functions
•SIP Methods
•SIP Responses
•SIP Header Fields
•Transport Layer Protocols
•SIP Security
SIP Functions
Function
|
Supported?
|
Proxy Server
|
Yes (Transaction stateful, parallel forking, and recursive)
|
Redirect Server
|
Yes
|
Registrar Server
|
Yes
|
SIP Methods
Five of the six methods used by the SIP are supported:
Method
|
Supported?
|
Comments
|
INVITE
|
Yes
|
The CSPS proxies SIP INVITE requests.
|
ACK
|
Yes
|
The CSPS proxies the SIP ACK method.1
|
OPTIONS
|
See comments
|
The CSPS proxies the OPTIONS and BYE methods.
|
BYE
|
CANCEL
|
Yes
|
The CSPS proxies the SIP CANCEL method.2
|
REGISTER
|
Yes
|
The CSPS supports both user and device registration.
|
SIP Responses
The CSPS supports the following SIP responses:
•1xx Response—Information Responses
•2xx Response—Successful Responses
•3xx Response—Redirection Responses
•4xx Response—Request Failure Responses
•5xx Response—Server Failure Responses
•6xx Response—Global Responses
1xx Response—Information Responses
1xx Response
|
Supported?
|
Comments
|
100 Trying
|
Yes
|
The CSPS generates and proxies this response for an incoming INVITE. Upon receiving this response, the server waits for a 180 Ringing, 183 Session progress, or 200 OK response.
|
180 Ringing
|
Yes
|
None
|
181 Call is being forwarded
|
See comments
|
The CSPS proxies these responses.
|
182 Queued
|
183 Session Progress
|
The CSPS does not generate this message. Upon receiving this message, the proxy server forwards the message upstream.
|
2xx Response—Successful Responses
2xx Response
|
Supported?
|
Comments
|
200 OK
|
Yes
|
The CSPS can generate a 200 OK response to a REGISTER or CANCEL request. The CSPS proxy 200 OK responses to other requests.
|
3xx Response—Redirection Responses
3xx Response
|
Supported
|
Comments
|
300 Multiple Choices
|
Yes
|
When in Redirect mode, the CSPS can only generate the 300 Multiple Choices response. When in Proxy mode, the CSPS can generate or proxy this response.
|
301 Moved Permanently
|
Yes
|
The CSPS can proxy this response.
|
302 Moved Temporarily
|
Yes
|
When in Redirect mode, the CSPS can only generate the 302 Moved Temporarily response when a matching registration is located. When in Proxy mode, the CSPS can generate or proxy this response.
|
305 Use Proxy
|
Yes
|
None.
|
380 Alternate Service
|
No
|
None.
|
4xx Response—Request Failure Responses
4xx Response
|
Supported?
|
Comments
|
400 Bad Request
|
Yes
|
The proxy server can generate and proxy a 400 Bad Request response.
|
401 Unauthorized
|
Yes
|
This response is proxied by the CSPS. If the CSPS is configured as a registrar and authentication is turned on, the proxy server generates this response.
|
402 Payment Required
|
See comments
|
These responses are generated if the CSPS is in registrar mode and is proxied by the proxy server.
|
403 Forbidden
|
404 Not Found
|
Yes
|
These responses are generated and proxied by the CSPS.
|
405 Method Not Allowed
|
See comments
|
These responses are proxied in this release.
|
406 Not Acceptable
|
See comments
|
407 Proxy Authentication Required
|
Yes
|
This response is proxied by the CSPS. If authentication is turned on, the CSPS generates this response.
|
408 Request Timeout
|
See comments
|
These responses are generated and proxied by the CSPS.
|
409 Conflict
|
410 Gone
|
See comments
|
This response is only proxied by the CSPS in this release.
The 410 Gone response indicates that a resource is no longer available at the server and no forwarding address is known.
|
411 Length Required
|
Yes
|
This response is proxied in this release.
This response indicates that the user refuses to accept the request without a defined content length.
|
413 Request Entity Too Large
|
See comments
|
This response is only proxied by the CSPS in this release.
If a retry after header field is contained in this response, then the user can attempt the call once again in the retry time provided.
|
414 Request—URL Too Long
|
Yes
|
This response is generated and proxied by the CSPS.
|
415 Unsupported Media
|
Yes
|
This response is proxied in this release.
|
420 Bad Extension
|
Yes
|
This response is generated and proxied by the CSPS.
|
480 Temporarily Unavailable
|
Yes
|
This response is proxied by the CSPS in this release.
It is generated if pre-authentication is enabled and fails.
|
481 Call Leg/Transaction Does Not Exist
|
Yes
|
These responses are generated and proxied by the CSPS.
|
482 Loop Detected
|
483 Too Many Hops
|
484 Address Incomplete
|
See comments
|
This response is proxied by the CSPS.
|
485 Ambiguous
|
See comments
|
This response is only proxied by the CSPS in this release.
|
486 Busy Here
|
487" ; Request Terminated
|
No
|
|
488" ; Not Acceptable Here
|
See comments
|
This response is proxied by the CSPS.
|
5xx Response—Server Failure Responses
5xx Response
|
Supported?
|
Comments
|
500 Internal Server Error
|
Yes
|
These responses are generated and proxied by the CSPS.
|
501 Not Implemented
|
502 Bad Gateway
|
See comments
|
This response is only proxied by the CSPS in this release.
|
503 Service Unavailable
|
504 Gateway Timeout
|
505 Version Not Supported
|
Yes
|
6xx Response—Global Responses
6xx Response
|
Supported?
|
Comments
|
600 Busy Everywhere
|
See comments
|
These responses are only proxied by the CSPS in this release.
|
603 Decline
|
604 Does Not Exist Anywhere
|
606 Not Acceptable
|
SIP Header Fields
Note All SIP header fields that concern the CSPS are correctly handled and parsed except for the Hide and Encryption header fields. Header fields that do not directly affect the CSPS or are unknown to the CSPS are passed unaltered in the SIP request.
Header Field
|
Supported?
|
Accept
|
Yes
|
Accept-Encoding
|
Yes
|
Accept-Language
|
Yes
|
Alert-Info
|
Yes
|
Allow
|
Yes
|
Also
|
Yes
|
Authorization
|
Yes
|
Call-ID
|
Yes
|
Call-Info
|
Yes
|
Contact
|
Yes
|
Content-Encoding
|
Yes
|
Content-Disposition
|
Yes
|
Content-Length
|
Yes
|
Content-Type
|
Yes
|
Cseq
|
Yes
|
Date
|
Yes
|
Encryption1
|
No
|
Error-Info
|
Yes
|
Expires
|
Yes
|
From
|
Yes
|
In-Reply-To
|
Yes
|
Max-Forwards
|
Yes
|
Organization
|
Yes
|
MIME-Version
|
Yes
|
Priority
|
Yes
|
Proxy-Authenticate
|
Yes
|
Proxy-Authorization
|
Yes
|
Proxy-Require
|
Yes
|
Record-Route
|
Yes
|
Require
|
Yes
|
Response-Key
|
Yes
|
Retry-After
|
Yes
|
Route
|
Yes
|
Server
|
Yes
|
Subject
|
Yes
|
Supported
|
Yes
|
Timestamp
|
Yes
|
To
|
Yes
|
Unsupported
|
Yes
|
User-Agent
|
Yes
|
Via
|
Yes
|
Warning
|
Yes
|
WWW-Authenticate
|
Yes
|
Transport Layer Protocols
Protocol
|
Supported?
|
Unicast UDP
|
Yes
|
Multicast UDP
|
No
|
TCP
|
Yes
|
SIP Security
Authentication
Basic Authentication
|
Yes
|
Digest Authentication
|
Yes
|
Proxy Authentication
|
Yes
|
PGP
|
No
|
SIP DNS Records Usage
DNS Resource Record Type
|
Supported?
|
Type A
|
Yes
|
Type SRV
|
Yes.
|
Feedback
