Cisco Systems RFC 2543 and RFC 3261 manual

1
2
3
4
5
6
7
8

Go to page of

A good user manual

The rules should oblige the seller to give the purchaser an operating instrucion of Cisco Systems RFC 2543 and RFC 3261, along with an item. The lack of an instruction or false information given to customer shall constitute grounds to apply for a complaint because of nonconformity of goods with the contract. In accordance with the law, a customer can receive an instruction in non-paper form; lately graphic and electronic forms of the manuals, as well as instructional videos have been majorly used. A necessary precondition for this is the unmistakable, legible character of an instruction.

What is an instruction?

The term originates from the Latin word „instructio”, which means organizing. Therefore, in an instruction of Cisco Systems RFC 2543 and RFC 3261 one could find a process description. An instruction's purpose is to teach, to ease the start-up and an item's use or performance of certain activities. An instruction is a compilation of information about an item/a service, it is a clue.

Unfortunately, only a few customers devote their time to read an instruction of Cisco Systems RFC 2543 and RFC 3261. A good user manual introduces us to a number of additional functionalities of the purchased item, and also helps us to avoid the formation of most of the defects.

What should a perfect user manual contain?

First and foremost, an user manual of Cisco Systems RFC 2543 and RFC 3261 should contain:
- informations concerning technical data of Cisco Systems RFC 2543 and RFC 3261
- name of the manufacturer and a year of construction of the Cisco Systems RFC 2543 and RFC 3261 item
- rules of operation, control and maintenance of the Cisco Systems RFC 2543 and RFC 3261 item
- safety signs and mark certificates which confirm compatibility with appropriate standards

Why don't we read the manuals?

Usually it results from the lack of time and certainty about functionalities of purchased items. Unfortunately, networking and start-up of Cisco Systems RFC 2543 and RFC 3261 alone are not enough. An instruction contains a number of clues concerning respective functionalities, safety rules, maintenance methods (what means should be used), eventual defects of Cisco Systems RFC 2543 and RFC 3261, and methods of problem resolution. Eventually, when one still can't find the answer to his problems, he will be directed to the Cisco Systems service. Lately animated manuals and instructional videos are quite popular among customers. These kinds of user manuals are effective; they assure that a customer will familiarize himself with the whole material, and won't skip complicated, technical information of Cisco Systems RFC 2543 and RFC 3261.

Why one should read the manuals?

It is mostly in the manuals where we will find the details concerning construction and possibility of the Cisco Systems RFC 2543 and RFC 3261 item, and its use of respective accessory, as well as information concerning all the functions and facilities.

After a successful purchase of an item one should find a moment and get to know with every part of an instruction. Currently the manuals are carefully prearranged and translated, so they could be fully understood by its users. The manuals will serve as an informational aid.

Table of contents for the manual

  • Page 1

    A-1 Cisco SIP Proxy Server Administrato r Guide APPENDIX A SIP Compliance This appendix describes Cisco SIP proxy server (C isco SPS) compliance with the Internet Engineering T ask Force (IETF) def initi on of Session Initiation Prot ocol (SIP) as described in the follo win g RFCs. Contents • RFC 2543 and RFC 3261 – SIP Functions, page A-2 – [...]

  • Page 2

    A-2 Cisco SIP Proxy Server Administrator Guide Appendix A SIP Compliance RFC 2543 and RFC 3261 RFC 2543 and RFC 3261 SIP Functions SIP Methods Cisco SPS supports fi ve of the six methods used b y SIP . It handles un know n methods such as NEWMETHOD in the same manner as kno wn methods such as OPTIONS and REFER. SIP Responses Cisco SPS supports the [...]

  • Page 3

    A-3 Cisco SIP Proxy Server Administra tor Guide Appendix A SIP Compliance RFC 2543 and RFC 3261 • 5xx Response—Serv er Failure Respon ses • 6xx Response—Global Responses T abl e A-3 SIP Responses SIP Response Meaning Supported? Cisco SPS Action 1xx Response—Info rmation Responses 100 T rying Action is being take n on behalf of the caller [...]

  • Page 4

    A-4 Cisco SIP Proxy Server Administrator Guide Appendix A SIP Compliance RFC 2543 and RFC 3261 4xx Response—Request Failure Responses 400 Bad Request Request can not be u nderstood because of an illegal format. Y es Generates and forwards this response. 401 Unauthorized Request requires user authenticati on. Y es Forw ards this response. If it is[...]

  • Page 5

    A-5 Cisco SIP Proxy Server Administra tor Guide Appendix A SIP Compliance RFC 2543 and RFC 3261 415 Unsupported media Server ref uses to process the request because the format of t h e body is not supported b y the destination endp oint. Y es Forwards this response. 420 Bad extension Server cannot u nderstand the protocol extension indicated in the[...]

  • Page 6

    A-6 Cisco SIP Proxy Server Administrator Guide Appendix A SIP Compliance RFC 2543 and RFC 3261 SIP Header Fields Note All SIP header f ields that concern t he Cisco SPS are correct ly hand led and parsed except for the Hide and Encryption header f ields. Header fields that do no t directly af fect the Cisc o SPS or that are unknown to it are pa sse[...]

  • Page 7

    A-7 Cisco SIP Proxy Server Administra tor Guide Appendix A SIP Compliance RFC 2543 and RFC 3261 SIP Transport Layer Protocols T able A -4 SIP Header Fields Header Field Supported? Header Field Supported? Accept Y es O rganization Y es Accept-Encodi ng Y es M IME-V ersion Y es Accept-Language Y es Priority Y es Alert-Info Y es Proxy-Authenticate Y e[...]

  • Page 8

    A-8 Cisco SIP Proxy Server Administrator Guide Appendix A SIP Compliance RFC 3263 SIP Security RFC 3263 SIP DNS Records Usage T abl e A -6 SIP Secur ity Mode Supported? Encryption Mode End-to-end No Hop-by- Hop Y es Authentication Mode Basic 1 1. Due to its weak security, basic authen tic ation has been deprecated. This is a change from RFC 2543. I[...]