Loading...
A P P E N D I X A
SIP Compliance
This appendix describes Cisco SIP proxy server (Cisco SPS) compliance with the Internet Engineering Task Force (IETF) definition of Session Initiation Protocol (SIP) as described in the following RFCs.
RFC1 |
Title |
2543 |
SIP: Session Initiation Protocol (March 1999) |
|
|
3261 |
SIP: Session Initiation Protocol (June 2002) |
|
|
3263 |
SIP: Locating SIP Servers (June 2002) |
|
|
1. Not all supported RFCs are listed.
Contents
•RFC 2543 and RFC 3261
–SIP Functions, page A-2
–SIP Methods, page A-2
–SIP Responses, page A-2
–SIP Header Fields, page A-6
–SIP Transport Layer Protocols, page A-7
–SIP Security, page A-8
•RFC 3263
–SIP DNS Records Usage, page A-8
Cisco SIP Proxy Server Administrator Guide
A-1
Appendix A SIP Compliance
RFC 2543 and RFC 3261
RFC 2543 and RFC 3261
SIP Functions
Table A-1 |
SIP Functions |
|
|
|
|
Function |
|
Supported? |
|
|
|
Proxy server |
|
Yes (transaction stateful, parallel forking, and |
|
|
recursive) |
|
|
|
Redirect server |
|
Yes |
|
|
|
Registrar server |
|
Yes |
|
|
|
SIP Methods
Cisco SPS supports five of the six methods used by SIP. It handles unknown methods such as
NEWMETHOD in the same manner as known methods such as OPTIONS and REFER.
Table A-2 |
SIP Methods |
|
|
|
|
|
|
Method |
|
Supported? |
Cisco SPS Action |
|
|
|
|
ACK |
|
Yes |
Forwards ACK requests.1 |
BYE |
|
Yes |
Forwards BYE requests. |
|
|
|
|
CANCEL |
|
Yes |
Forwards CANCEL requests.2 |
INFO |
|
Yes |
Forwards INFO requests. |
|
|
|
|
INVITE |
|
Yes |
Forwards INVITE requests. |
|
|
|
|
NOTIFY |
|
Yes |
Forwards NOTIFY requests. |
|
|
|
|
OPTIONS |
|
Yes |
Responds to OPTIONS requests. |
|
|
|
|
REFER |
|
Yes |
Forwards REFER requests. |
|
|
|
|
REGISTER |
|
Yes |
Supports both user and device registration. |
|
|
|
|
SUBSCRIBE |
|
Yes |
Forwards SUBSCRIBE requests. |
|
|
|
|
UPDATE |
|
Yes |
Forwards UPDATE requests. |
|
|
|
|
1.The SPS can generate a local ACK for a non-200 OK final response to an INVITE request.
2.The SPS can generate a local CANCEL for a pending branch when it receives a 200 OK or 6xx response from the branch.
SIP Responses
Cisco SPS supports the following SIP responses:
•1xx Response—Information Responses
•2xx Response—Successful Responses
•3xx Response—Redirection Responses
•4xx Response—Request Failure Responses
Cisco SIP Proxy Server Administrator Guide
A-2
Appendix A SIP Compliance
RFC 2543 and RFC 3261
•5xx Response—Server Failure Responses
•6xx Response—Global Responses
Table A-3 SIP Responses
SIP Response |
Meaning |
Supported? |
Cisco SPS Action |
|
|
|
|
|
|
1xx Response—Information Responses |
|
|
||
|
|
|
|
|
100 |
Trying |
Action is being taken on behalf of the |
Yes |
Generates and forwards this |
|
|
caller, but the called party is not yet |
|
response for an incoming |
|
|
located. |
|
INVITE. Upon receiving this |
|
|
|
|
response, waits for a 180 |
|
|
|
|
Ringing, 183 Session progress, |
|
|
|
|
or 200 OK response. |
|
|
|
|
|
180 |
Ringing |
Called party is located and is being |
Yes |
Forwards this response. |
|
|
notified of the call. |
|
|
|
|
|
|
|
181 |
Call is being forwarded |
Call is being rerouted to another |
Yes |
|
|
|
destination. |
|
|
|
|
|
|
|
182 |
Queued |
Called party is not currently available or |
Yes |
|
|
|
elects to queue the call rather than reject |
|
|
|
|
it. |
|
|
|
|
|
|
|
183 |
Session progress |
System performs inband alerting for the |
Yes |
|
|
|
caller. |
|
|
|
|
|
|
|
2xx Response—Successful Responses
200 OK |
Request has been successfully |
Yes |
|
processed. The action taken depends on |
|
|
the request made. |
|
|
|
|
Generates this response to a REGISTER or CANCEL request. Otherwise forwards this response.
3xx Response—Redirection Responses |
|
|
|||
|
|
|
|
|
|
300 |
Multiple choices |
Address resolves to more than one |
Yes |
Does not generate this response. |
|
|
|
location. All locations are provided and |
|
If recursive is enabled, recurses |
|
|
|
the user or UA can select which location |
|
on all contacts; otherwise |
|
|
|
to use. |
|
forwards this response. |
|
|
|
|
|
|
|
301 |
Moved permanently |
User is no longer available at the |
Yes |
|
|
|
|
specified location. An alternate location |
|
|
|
|
|
is included in the header. |
|
|
|
|
|
|
|
|
|
302 |
Moved temporarily |
User is temporarily unavailable at the |
Yes |
In redirect mode, generates this |
|
|
|
specified location. An alternate location |
|
response when it locates one or |
|
|
|
is included in the header. |
|
more contacts. In proxy mode, if |
|
|
|
|
|
recursive is enabled, recurses on |
|
|
|
|
|
all contacts; otherwise forwards |
|
|
|
|
|
this response. |
|
|
|
|
|
|
|
305 |
Use proxy |
Caller must use a proxy to contact the |
Yes |
Does not generate this response. |
|
|
|
called party. |
|
If recursive is enabled, recurses |
|
|
|
|
|
on all contacts; otherwise |
|
380 |
Alternative service |
Call is unsuccessful, but alternative |
Yes |
||
forwards this response. |
|||||
|
|
services are available. |
|
||
|
|
|
|
||
|
|
|
|
|
|
Cisco SIP Proxy Server Administrator Guide
A-3
Loading...