SIP Pocket Guide.pdf

7/26/2019 SIP Pocket Guide.pdf

1/60

SIP POCKET GUIDE


2/60

This pocket guide is provided by IMSWorkX, Inc. Visit us at www.imsworkx.com.

" #$% %&'()* +,-.)

Table of Contents

SIP Definition- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -3

SIP Network Architecture- - - - - - - - - - - - - - - - - - - - - - - 3

SIP User Agents- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -4

Presence Agents- - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5

SIP Gateways- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5

SIP Proxy Servers- - - - - - - - - - - - - - - - - - - - - - - - - - - - 6

SIP Redirect Servers- - - - - - - - - - - - - - - - - - - - - - - - - - 6

SIP Registration Servers- - - - - - - - - - - - - - - - - - - - - - - -6

SIP Protocol Stack- - - - - - - - - - - - - - - - - - - - - - - - - - - -7

SIP Addressing- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 8

SIP Message Definitions- - - - - - - - - - - - - - - - - - - - - - - -8Generic Message Structure- - - - - - - - - - - - - - - - - - - - - -9

SIP Method Message Structure- - - - - - - - - - - - - - - - - - -9

SIP Methods- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 10

SIP Responses Class 1XX- - - - - - - - - - - - - - - - - - - - - 12






Legend for Header Table- - - - - - - - - - - - - - - - - - - - - - 21

Header Table- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -22

SIP Events- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -31

SIP Timers- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -32

SDP Description- - - - - - - - - - - - - - - - - - - - - - - - - - - - -33

SDP Fields- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -33

SDP Field Descriptions- - - - - - - - - - - - - - - - - - - - - - - - 34

SIP Responses to ISUP Release Cause Mapping- - - - - 35

SIP Call Flow Network- - - - - - - - - - - - - - - - - - - - - - - - -36

Call Flow Messages

Invite #1- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -37

Invite #2- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -38

100 Trying #3- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -39

1


3/60

/#$% %&'()* +,-.)

100 Trying #4- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -39

180 Ringing #5- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -40

180 Ringing #6- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -40

200 OK #7- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 41

200 OK #8- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 42

ACK #9- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 43

ACK #10- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 43

BYE #11- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 44

BYE #12- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 44

200 OK #13- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -45

200 OK #14- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -45

Registration Process- - - - - - - - - - - - - - - - - - - - - - - - - 46

Registration Messages

Register #1- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 47

402 Unauthorized #2- - - - - - - - - - - - - - - - - - - - - - - - - 47

Register #3- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 48

200 OK #4- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -49

Additional Sample Messages

Cancel- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 49

Subscribe- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 50

302 Moved Temporarily- - - - - - - - - - - - - - - - - - - - - - - 50

401 Unauthorized- - - - - - - - - - - - - - - - - - - - - - - - - - - 51

403 Forbidden- - - - - - - - - - - - - - - - - - - - - - - - - - - - - 51404 Unknown User Account- - - - - - - - - - - - - - - - - - - - 52

407 Proxy Authentication Required- - - - - - - - - - - - - - - 52

408 Request Timeout- - - - - - - - - - - - - - - - - - - - - - - - 53

481 Transaction Does Not Exist- - - - - - - - - - - - - - - - - 53

487 Request Terminated- - - - - - - - - - - - - - - - - - - - - - 53

Glossary of SIP Related Terms- - - - - - - - - - - - - - - - - 54

References- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 55

2


4/60

0 #$% %&'()* +,-.)

SIP DEFINITION

Session Initiation Protocol (SIP) is a signaling protocol

specified by the Internet Engineering Task Force (IETF) for

establishing, modifying, and terminating sessions in an IP

network. These sessions are independent of the SIP

protocol and can be voice, video, or any other type of

media. The current baseline specification for SIP is IETF

RFC 3261 with other RFCs further defining extensions to

the SIP Protocol.

SIP NETWORK ARCHITECTURE

NOTES:

__________________________________________

__________________________________________

3


5/60

his pocket guide is provided by IMSWorkX, Inc. Visit us at www.imsworkx.com.#$% %&'()* +,-.)

SIP User Agents

SIP User Agents are SIP-enabled devices that take input

from users and act on their behalf.

Rules for User Agents _____________________

UAs must be capable of establishing media

sessions with other UAs.

UAs must maintain call states of calls it initiates

or participates in.

Even after the call has been terminated the UAmust maintain the call state for 32 seconds in case

of lost messages.

UAs must support UDP transport.

UAs must support TCP transport if they send

messages greater than 1000 octets.

UAs must support Session Description Protocol

(SDP) for media description.

UAs must be understand extensions contained in

the Require header of received request from other

UAs.

UAs may ignore unknown header fields.

4


6/60

2 #$% %&'()* +,-.)

Presence Agents

Support the SIP Event Specification (RFC 3856).

Receives subscription request (SUBSCRIBE

Messages).

Validates the SUBSCRIBE Messages.

Can collect presence information from multiple

sources.

o User Agents publishing presence

information

o Registration servers

o Non SIP Sources

Sometimes acts as a presence agent collecting

presence information.

Sometimes acts as a proxy forwarding

subscription request to other Presence Agents.

Authenticates the Subscription Request.

SIP Gateways

Applications that allow a SIP network to interface

with a non-SIP network (PSTN, H323 etc.).

Can be thought of as protocol converters ormedia converters depending on the type of

network being interfaced.

NOTES:

__________________________________________

__________________________________________

__________________________________________

__________________________________________

__________________________________________

5


7/60

3#$% %&'()* +,-.)

SIP Proxy Servers

Accept session request from a SIP User Agent

and query the SIP Registration Server for the

address of the callED party.

It then forwards the session invitation to either

the SIP User Agent or another Proxy Server based

on whether the callED party is in the same domain

as the callING party.

Proxy Servers may be either Stateful or

Stateless.

SIP Redirect Servers

Receive SIP Request.

Respond to but do not forward SIP Request.

Uses databases or Location Servers to find user

location.

Respond to originator with 300 Class.

Response messages (redirection class).

SIP Registration Servers

Registration Servers are databases that contain the

location of User Agents within a domain. They retrieve and

send participants IP address and other information to the

SIP Proxy Server.

NOTES:

__________________________________________

__________________________________________

__________________________________________

__________________________________________

6


8/60

4 #$% %&'()* +,-.)

SIP Protocol Stack

NOTES:

__________________________________________

__________________________________________

__________________________________________

__________________________________________

7


9/60

5#$% %&'()* +,-.)

SIP Addressing

Is used to identify a user by its SIP Uniform

Resource Identifiers (URI) (RFC 2396).

A SIP URI consists of a user and a domain

delimited by one @, as is shown in the following

examples:

o user@domain

o user@machine

o user@ip_address

o telephone_number@gateway

SIP Message Definitions

SIP Methods____________________________

SIP Messages that request an action to take place in

another user agent or server.

SIP

Responses____________________________

SIP Messages generated by a UA or SIP server in

response to a SIP request or method.

NOTES:

__________________________________________

__________________________________________

__________________________________________

__________________________________________

__________________________________________

__________________________________________

___________________________________________

8


10/60

67 #$% %&'()* +,-.)

Generic Message Structure

SIP Method Message Structure

9


11/60

66#$% %&'()* +,-.)

SIP Methods

ACK (RFC 3261) ________________________

The ACK method is used to acknowledge the final

response to an INVITE method. Final responses are

response classes 2XX, 3XX, 4XX, and 5XX.

Bye (RFC 3261) _________________________

The Bye method is used to terminate an established media

session.

Cancel (RFC 3261) _______________________

The Cancel method is used to terminate a session before

the session is established.

Info (RFC 2976) _________________________

The INFO method is used to carry call signaling

information from a user agent to another user agent, with

which it has an established media session.

Invite (RFC 3261) ________________________

The Invite method is used by a user agent to request the

establishment of a session to another user agent.

Message (RFC 3428) _____________________The Message method is used to transfer Instant Message

information in SIP.

Notify (RFC 3265) _______________________________

The Notify method is used to provide the updated event

and status information requested in the Subscribe Method.

Options (RFC 3261) ______________________

The Options method is used to query a user agent orserver about its capabilities and discover its current

availability.

PRACK (RFC 3262) ______________________

The PRACK method is used to acknowledge reliability

transported provisional responses (1XX Class responses).

10


12/60

6" #$% %&'()* +,-.)

SIP Methods (Continued)

Publish (RFC 3903) ______________________

The Publish method is used by a user agent to

send/publish event state information to a SIP Server

known as an Event State Compositor (ESC).

Refer (RFC 3515) ________________________

The Refer method is used by a user agent to request

another user agent access to a particular SIP URI. This

method is also used to perform a call transfer.

Register (RFC 3261) ______________________

The Register method is used by a SIP User Agent to notify

the SIP network of its current Contact URI (IP Address)

and to provide the URI that should be used for the routing

of request to the User Agent.

Subscribe (RFC 3265) ____________________

The Subscribe method is used to request event and status

updates from a remote device.

Update (RFC 3311) ______________________

The Update method is used to modify the state of a

session without changing the state of theexisting dialog.

NOTES:

__________________________________________

__________________________________________

__________________________________________

__________________________________________

__________________________________________

__________________________________________

___________________________________________

11


13/60

6/#$% %&'()* +,-.)

SIP Responses Class 1XX

Provisional Response Class (1XX)

Provisional responses, also known as informationalresponses, indicate that the server contacted is performingsome further action and does not yet have a definitiveresponse. A server sends a 1XX response if it expects to

take more than 200 ms to obtain a final response.

100 Trying (RFC 3261) ____________________

This response indicates that the request has beenreceived by the next-hop server and that some unspecifiedaction is being taken on behalf of this call.

180 Ringing (RFC 3261) ___________________

The UA receiving the INVITE is trying to alert the user.This response MAY be used to initiate local ringback.

181 Call Is Being Forwarded (RFC 3261) ______

A server MAY use this status code to indicate that the callis being forwarded to a different set of destinations.

182 Queued (RFC 3261) __________________

The called party is temporarily unavailable, but the serverhas decided to queue the call rather than reject it. When

the callee becomes available, it will return the appropriatefinal status response.

183 Session Progress (RFC 3261) ___________

The 183 (Session Progress) response is used to conveyinformation about the progress of the call that is not

otherwise classified.

NOTES:

__________________________________________

__________________________________________

__________________________________________

__________________________________________

12


14/60

60 #$% %&'()* +,-.)


Success Response Class (2XX)Success responses indicate that the request wassuccessful.

200 OK (RFC 3261) ______________________

The request has succeeded. The information returned withthe response depends on the method used in the request.

202 Accepted (RFC 3265) _________________

Indicates that the subscription request has beenunderstood, and that authorization may or may not havebeen granted.

SIP Responses Class 3XXRedirection Class (3XX)

3XX responses give information about the user's newlocation, or about alternative services that might be able tosatisfy the call.

300 Multiple Choice (RFC 3261) ____________

The address in the request resolved to several choices,each with its own specific location, and the user (or UA)can select a preferred communication end point andredirect its request to that location.

301 Moved Permanently (RFC 3261) _________

The user can no longer be found at the address in theRequest-URI, and the requesting client SHOULD retry atthe new address given in the Contact header field.

302 Moved Temporarily (RFC 3261) _________

The requesting client SHOULD retry the request at thenew address(es) given in the Contact header field.

305 Use Proxy (RFC 3261) ________________

The requested resource MUST be accessed through theproxy listed in the Contact field. The Contact field gives theURI of the proxy.

380 Alternative Service (RFC 3261) __________The call was not successful, but alternative services arepossible. The alternative services are described in themessage body of the response.

13

13


15/60

61#$% %&'()* +,-.)


Client Error Class (4XX)4XX responses are failure responses from a particularserver. The client SHOULD NOT retry the same requestwithout modification.

400 Bad Request (RFC 3261) ______________

The request could not be understood due to malformedsyntax. The Reason-Phrase SHOULD identify the syntaxproblem in more detail, for example, "Missing Call-IDheader field."

401 Unauthorized (RFC 3261) ______________

The request requires user authentication. This response isissued by UASs and Registrars.

402 Payment Required (RFC 3261) __________

Reserved for future use.

403 Forbidden (RFC 3261) _________________

The server understood the request, but is refusing to fulfillit. Authorization will not help, and the request SHOULDNOT be repeated.

404 Not Found (RFC 3261) ________________

The server has definitive information that the user does not

exist at the domain specified in the Request-URI.

405 Method Not Allowed (RFC 3261) _________

The method specified in the Request-Line is understood,but not allowed for the address identified by the Request-URI. The response MUST include an Allow header fieldcontaining a list of valid methods for the indicated address.

406 Not Acceptable (RFC 3261) _____________

The resource identified by the request is only capable ofgenerating response entities that have contentcharacteristics not acceptable according to the Acceptheader field sent in the request.

407 Proxy Authentication Required (RFC 3261)

This response indicates that the client MUST firstauthenticate itself wit the proxy.

14


16/60

62 #$% %&'()* +,-.)

SIP Responses Class 4XX (Continued)

408 Request Timeout (RFC 3261) ___________The server could not produce a response within a suitableamount of time, for example, if it could not determine thelocation of the user in time.

410 Gone (RFC 3261) ____________________

The requested resource is no longer available at theserver and no forwarding address is known. This conditionis expected to be considered permanent.

412 Conditional Request Failed (RFC 3903) ___

Indicates that the precondition given for the request has

failed.

413 Request Entity Too Large (RFC 3261) ____

The server is refusing to process a request because therequest entity-body is larger than the server is willing orable to process.

414 Request-URI Too Long (RFC 3261) ______

The server is refusing to service the request because theRequest-URI is longer than the server is willing tointerpret.

415 Unsupported Media Type (RFC 3261) _____

The server is refusing to service the request because themessage body of the request is in a format not supportedby the server for the requested method. The server MUSTreturn a list of acceptable formats using the Accept,Accept- Encoding, or Accept-Language header field,depending on the specific problem with the content.

416 Unsupported URK Scheme (RFC 3261) ___

The server cannot process the request because thescheme of the URI in the Request-URI is unknown to theserver.

417 Unknown Resource-Priority (RFC 4412) ___

A request containing Require: resource-priority and anunknown value for Resource-Priority header field willreceive the 417 Unknown Resource Priority responses..

15


17/60

63#$% %&'()* +,-.)


420 Bad Extension (RFC 3261) _____________The server did not understand the protocol extensionspecified in a Proxy-Require or Require header field.

421 Extension Required (RFC 3261) _________

The UAS needs a particular extension to process therequest, but this extension is not listed in a Supportedheader field in the request. Responses with this statuscode MUST contain a Require header field listing therequired extensions.

422 Session Interval Too Small (RFC 4028) ___

Indicates that the session timer duration was too small.

423 Interval Too Brief (RFC 3261) ___________

The server is rejecting the request because the expirationtime of the resource refreshed by the request is too short.

429 Provide Referror Identify (RFC 3892) _____

Is used by the refer target to indicate that the referee mustprovide a valid Referred-BY token.

433 Anonymity Disallowed (RFC 4079) _______

Indicates that the server refused to fulfill the requestbecause the requestor was anonymous. Its default reason

phrase is "Anonymity Disallowed."

436 Bad Identity-Info (RFC 4474) ____________

This response code is used when the Identity-Info headercontains a URI that cannot be de-referenced by the verifier(either the URI scheme is unsupported by the verifier, orthe resource designated by the URI is otherwiseunavailable).

437 Unsupported Certificate (RFC 4474) ______

This response code is used when the verifier cannotvalidate the certificate referenced by the URI of theIdentity-Info header

16


18/60

64 #$% %&'()* +,-.)


438 Invalid Identity Header (RFC 4474) _______This response code is used when the verifier receives amessage with an Identity signature that does notcorrespond to the digest-string calculated by the verifier.

470 Consent Needed (RFC 5360) ___________

Indicates that the request that triggered the responsecontained a URI list with at least one URI for which therelay had no permissions.

480 Temporarily Unavailable (RFC 3261) _____

The callee's end system was contacted successfully but

the callee is currently unavailable (for example, is notlogged in, logged in but in a state that precludescommunication with the callee, or has activated the "do notdisturb" feature.

481 Call/Transaction Does Not Exist (RFC 3261)

This status indicates that the UAS received a request thatdoes not match any existing dialog or transaction.

482 Loop Detected (RFC 3261) _____________

The server has detected a loop.

483 Too Many Hops (RFC 3261) ____________

The server received a request that contains a Max-Forwards header field with the value zero.

484 Address Incomplete (RFC 3261) _________

The server received a request with a Request-URI thatwas incomplete. Additional information SHOULD beprovided in the reason phrase.

485 Ambiguous (RFC 3261) ________________

The Request-URI was ambiguous. The response MAYcontain a listing of possible unambiguous addresses inContact header fields.

17


19/60

65#$% %&'()* +,-.)


486 Busy Here (RFC 3261) ________________The callee's end system was contacted successfully, butthe callee is currently not willing or able to take additionalcalls at this end system.

487 Request Terminated (RFC 3261) ________

The request was terminated by a BYE or CANCELrequest. This response is never returned for a CANCELrequest itself.

488 Not Acceptable Here (RFC 3261) ________

The response has the same meaning as 606 (Not

Acceptable), but only applies to the specific resourceaddressed by the Request-URI and the request maysucceed elsewhere.

489 Bad Event (RFC 5360) ________________

Indicates that the specified event/event class is notunderstood.

491 Request Pending (RFC 3261) ___________

The request was received by a UAS that had a pendingrequest within the same dialog.

493 Undecipherable (RFC 3261) ____________

The request was received by a UAS that contained anencrypted MIME body for which the recipient does notpossess or will not provide an appropriate decryption key.

494 Security Agreement Required (RFC 3329) _

A server receiving an unprotected request that contains aRequire or Proxy-Require header field with the value "sec-agree" MUST respond to the client with a 494 (SecurityAgreement Required) response.

NOTES:

__________________________________________

__________________________________________

__________________________________________

18


20/60

"7 #$% %&'()* +,-.)


Server Failure Class (5XX)5XX responses are failure responses given when a serveritself has erred.

500 Server Internal Error (RFC 3261) ________

The server encountered an unexpected condition thatprevented it from fulfilling the request. The client MAYdisplay the specific error condition and MAY retry therequest after several seconds.

501 Not Implemented (RFC 3261) ___________

The server does not support the functionality required to

fulfill the request.

502 Bad Gateway (RFC 3261) ______________

The server, while acting as a gateway or proxy, receivedan invalid response from the downstream server itaccessed in attempting to fulfill the request.

503 Service Unavailable (RFC 3261) _________

The server is temporarily unable to process the requestdue to a temporary overloading or maintenance of theserver.

504 Server Time-Out (RFC 3261) ___________

The server did not receive a timely response from anexternal server it accessed in attempting to process therequest.

505 Versions Not Supported (RFC 3261) ______

The server does not support, or refuses to support, the SIPprotocol version that was used in the request.

513 Message Too Large (RFC 3261) _________

The server was unable to process the request since themessage length exceeded its capabilities.

580 Precondition Failure (RFC 3312) _________

When a UAS, acting as an answerer, cannot or is notwilling to meet the preconditions in the offer, it SHOULDreject the offer by returning a 580 Precondition-Failure)response.

19


21/60

"6#$% %&'()* +,-.)


Global Failure class (6XX)6XX responses indicate that a server has definitiveinformation about a particular user, not just the particularinstance indicated in the Request-URI.

600 Busy Everywhere (RFC 3261) ___________

The callee's end system was contacted successfully butthe callee is busy and does not wish to take the call at thistime.

603 Decline (RFC 3261) ___________________

The callee's machine was successfully contacted but the

user explicitly does not wish to or cannot participate.

604 Does Not Exist Anywhere (RFC 3261) ____

The server has authoritative information that the userindicated in the Request URI does not exist anywhere.

606 Not Acceptable (RFC 3261) _____________

The user's agent was contacted successfully but someaspects of the session description such as the requestedmedia, bandwidth, or addressing style were notacceptable.

NOTES:

___________________________________________

___________________________________________

___________________________________________

___________________________________________

___________________________________________

___________________________________________

___________________________________________

___________________________________________

20


22/60

"" #$% %&'()* +,-.)

Legend For Header Table

NOTES:

___________________________________________

___________________________________________

___________________________________________

___________________________________________

___________________________________________

___________________________________________

___________________________________________

__________________________________________

21


23/60

"/#$% %&'()* +,-.)

Header Table

22


24/60

"0 #$% %&'()* +,-.)

Header Table (Continued)

23


25/60

"1#$% %&'()* +,-.)


24


26/60

"2 #$% %&'()* +,-.)


25


27/60

"3#$% %&'()* +,-.)


26


28/60

"4 #$% %&'()* +,-.)


27


29/60

"5#$% %&'()* +,-.)


28


30/60

/7 #$% %&'()* +,-.)


29


31/60

/6#$% %&'()* +,-.)


30


32/60

/" #$% %&'()* +,-.)

SIP Events

SIP events provide a mechanism whereby aninterested UA can be notified of the state ofanother UA. The SIP events are primarily used inthe Subscribe and Notify methods.

NOTES:

___________________________________________

___________________________________________

___________________________________________

___________________________________________

31


33/60

//#$% %&'()* +,-.)

SIP Timers

NOTES:

___________________________________________

___________________________________________

___________________________________________

___________________________________________

32


34/60

/0 #$% %&'()* +,-.)

SDP Description

SDP is used to convey information about mediastreams in multimedia sessions. It allows therecipients of a session description to participatein the session. SDP is primarily intended for usein an internetwork, although it is sufficientlygeneral that it can describe conferences in othernetwork environments. Media streams can bemany-to-many. Sessions need not be continuallyactive.

SDP Fields

NOTES:

___________________________________________

___________________________________________

33


35/60

/1#$% %&'()* +,-.)

SDP Field Description

Protocol VersionIs 0 for SDP version 0.

Origin

Contains information about the originator of the sessionand session identifiers.

Session Name

Contains the name of the session.

Session Information

Contains information about the session.

Uniform Resource Identifier

Contains a uniform resource identifier with moreinformation about the session.

Email Address

Contains the email address of the host of the session.

Phone Number

Contains the phone number of the Originator. Should be inthe format of + country code, city code and number.

Connection Data

Contains IN for Internet, the address type IP4 or IP6 forIPv4 or IPv6, and address sending packets.

Bandwidth Information

Contains information about the bandwidth required.

Time Session Starts and Stops

Contains the start and stop time of the session.

Repeat Times

Contains information about the repeat times in NTP ordays, hour, and minutes.

Time Zone Corrections

Gives the time zone offset to be used, i.e., daylight-savings to standard time.

Encryption Key

Contains the encryption key for the session where theencryption key equals clear, base64, URI, or prompt.

Attribute Lines

Contains information about the described media session.Media Information

Contains information about the type of media sessionrequired, i.e., audio, video, application data, telephone-event, or control. All underlined letters indicate the shortversion of the parameter names.

34


36/60

/2 #$% %&'()* +,-.)

All underlined letters indicate the short version of the parameter.

SIP Responses To ISUP Release CauseMapping

35


37/60

/3#$% %&'()* +,-.)

SIP Call Flow Network

NOTES:

___________________________________________

___________________________________________

___________________________________________

___________________________________________

___________________________________________

___________________________________________

___________________________________________

___________________________________________

___________________________________________

36

36


38/60

/4 #$% %&'()* +,-.)

Invite #1

NOTES:

___________________________________________

___________________________________________

___________________________________________

37


39/60

/5#$% %&'()* +,-.)

Invite #2

NOTES:

___________________________________________

___________________________________________

___________________________________________

___________________________________________

38


40/60

07 #$% %&'()* +,-.)

100 Trying #3

100 Trying #4

NOTES:

___________________________________________

___________________________________________

___________________________________________

___________________________________________

39


41/60

06#$% %&'()* +,-.)

180 Ringing #5

180 Ringing #6

NOTES:

___________________________________________

___________________________________________

___________________________________________

40


42/60

0" #$% %&'()* +,-.)

200 OK #7

NOTES:

___________________________________________

___________________________________________

___________________________________________

___________________________________________

41


43/60

0/#$% %&'()* +,-.)

200 OK #8

NOTES:

___________________________________________

___________________________________________

___________________________________________

___________________________________________

___________________________________________

42


44/60

00 #$% %&'()* +,-.)

ACK #9

ACK #9

43


45/60

01#$% %&'()* +,-.)

Bye #11

Bye #12

44


46/60

02 #$% %&'()* +,-.)

200 OK #13

200 OK #14

NOTES:

___________________________________________

___________________________________________

45


47/60

03#$% %&'()* +,-.)

Registration Process

NOTES:

___________________________________________

___________________________________________

___________________________________________

___________________________________________

___________________________________________

___________________________________________

___________________________________________

___________________________________________

___________________________________________

___________________________________________

46


48/60

04 #$% %&'()* +,-.)

Registration Messages

Register #1

402 Unauthorized #2

NOTES:

___________________________________________

___________________________________________

47


49/60

05#$% %&'()* +,-.)

Registration Messages (Continued)

Register #3

NOTES:

___________________________________________

___________________________________________

___________________________________________

___________________________________________

___________________________________________

___________________________________________

___________________________________________

___________________________________________

___________________________________________

48


50/60

17 #$% %&'()* +,-.)

Registration Messages (Continued)

200 OK #4

Additional Sample Messages

Cancel

NOTES:

___________________________________________

___________________________________________

49


51/60

16#$% %&'()* +,-.)

Additional Sample Messages (Continued)

Subscribe

302 Moved Temporarily

NOTES:

___________________________________________

___________________________________________

50


52/60

1" #$% %&'()* +,-.)


401 Unauthorized

403 Forbidden

NOTES:

___________________________________________

___________________________________________

___________________________________________

51


53/60

1/#$% %&'()* +,-.)


404 Unknown User Account

407 Proxy Authentication Required

NOTES:

___________________________________________

___________________________________________

___________________________________________

52


54/60

10 #$% %&'()* +,-.)


408 Request Timeout

481 Transaction Does Not Exist

487 Request Terminated

53


55/60

11#$% %&'()* +,-.)

Glossary Of SIP Related Terms

DHCP _________________________________Dynamic Host Configuration Protocol

DNS __________________________________

Domain Name SystemIETF __________________________________

Internet Engineering Task Force

IP ____________________________________

Internet ProtocolPPP __________________________________

Point-to-Point ProtocolPSTN _________________________________

Public Switched Telephone NetworkRFC __________________________________

Request for CommentsRTP___________________________________

Real-time Transport ProtocolRTSP _________________________________Real-time Streaming Protocol

SCTP _________________________________

Stream Control Transmission Protocol

SDP __________________________________Session Description Protocol

SIP ___________________________________Session Initiation Protocol

TCP __________________________________Transmission Control Protocol

UA___________________________________

User Agent

UAC __________________________________User Agent Client

UAS __________________________________

User Agent Server

UDP __________________________________User Datagram Protocol

URI ___________________________________Uniform Resource Identifier

54


56/60

12 #$% %&'()* +,-.)

References

55


57/60

13#$% %&'()* +,-.)

References (Continued)

56


58/60

14 #$% %&'()* +,-.)

References (Continued)

57


59/60

15#$% %&'()* +,-.)

Although information contained in this documentresembles specifications by national or

international standards bodies, nothingcontained within this document is eitherwarranted or endorsed by said standards bodies.While every effort has been taken to ensure theaccuracy of this material, errors may exist andmaterials may become obsolete by more recentadditions of specifications. No development ofactual product should be undertaken withoutreferring to the ANSI, ITU, ETSI, IETC or IETFspecifications.

2014 Center Point Consulting, Inc.

58


60/60

#$% %&'()* +,-.)

SIP Pocket Guide.pdf

Documents

Transcript of SIP Pocket Guide.pdf