SIP POCKET GUIDE

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- - - - - - - - - - - - - - - - - - - - - - - -8
Generic Message Structure- - - - - - - - - - - - - - - - - - - - - -9
SIP Method Message Structure- - - - - - - - - - - - - - - - - - -9
SIP Methods- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 10
SIP Responses Class 1XX- - - - - - - - - - - - - - - - - - - - - 12
SIP Responses Class 2XX- - - - - - - - - - - - - - - - - - - - - 13
SIP Responses Class 3XX- - - - - - - - - - - - - - - - - - - - - 13
SIP Responses Class 4XX- - - - - - - - - - - - - - - - - - - - - 14
SIP Responses Class 5XX- - - - - - - - - - - - - - - - - - - - - 19
SIP Responses Class 6XX- - - - - - - - - - - - - - - - - - - - - 20
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 2

SIP Pocket Guide

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- - - - - - - - - - - - - - - - - - - - - - - - - - - - - 51
404 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

SIP Pocket Guide



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 4

SIP Pocket Guide

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 UA
must 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.

his pocket guide is provided bySIP

IMSWorkX,
Pocket GInc.
uide Visit us at www.imsworkx.com.



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 or
media converters depending on the type of
network being interfaced.

NOTES:
__________________________________________
__________________________________________
__________________________________________
__________________________________________
__________________________________________

5 6

SIP Pocket Guide

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:
__________________________________________
__________________________________________
__________________________________________
__________________________________________

SIP Pocket Guide



SIP Protocol Stack

NOTES:
__________________________________________
__________________________________________
__________________________________________
__________________________________________

7 8

SIP Pocket Guide



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:
__________________________________________
__________________________________________
__________________________________________
__________________________________________
__________________________________________
__________________________________________
___________________________________________

SIP Pocket Guide



Generic Message Structure

SIP Method Message Structure

9 10

SIP Pocket Guide



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 or
server 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

SIP Pocket Guide

11



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 the existing dialog.

NOTES:
__________________________________________
__________________________________________
__________________________________________
__________________________________________
__________________________________________
__________________________________________
___________________________________________

1112

SIP Pocket Guide



SIP Responses Class 1XX
Provisional Response Class (1XX)
Provisional responses, also known as informational
responses, indicate that the server contacted is performing
some further action and does not yet have a definitive
response. 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 been
received by the next-hop server and that some unspecified
action 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 call
is being forwarded to a different set of destinations.

182 Queued (RFC 3261) __________________

The called party is temporarily unavailable, but the server
has decided to queue the call rather than reject it. When
the callee becomes available, it will return the appropriate
final status response.

183 Session Progress (RFC 3261) ___________

The 183 (Session Progress) response is used to convey
information about the progress of the call that is not
otherwise classified.

NOTES:
__________________________________________
__________________________________________
__________________________________________
__________________________________________

12

SIP Pocket Guide

13



SIP Responses Class 2XX
Success Response Class (2XX)
Success responses indicate that the request was
successful.

200 OK (RFC 3261) ______________________

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

202 Accepted (RFC 3265) _________________

Indicates that the subscription request has been
understood, and that authorization may or may not have
been granted.

SIP Responses Class 3XX

Redirection Class (3XX)
3XX responses give information about the user's new
location, or about alternative services that might be able to
satisfy 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 and
redirect its request to that location.

301 Moved Permanently (RFC 3261) _________

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

302 Moved Temporarily (RFC 3261) _________

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

305 Use Proxy (RFC 3261) ________________

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

380 Alternative Service (RFC 3261) __________

The call was not successful, but alternative services are
possible. The alternative services are described in the
message body of the response.

13
1314

SIP Pocket Guide



SIP Responses Class 4XX
Client Error Class (4XX)
4XX responses are failure responses from a particular
server. The client SHOULD NOT retry the same request
without modification.

400 Bad Request (RFC 3261) ______________

The request could not be understood due to malformed
syntax. The Reason-Phrase SHOULD identify the syntax
problem in more detail, for example, "Missing Call-ID
header field."

401 Unauthorized (RFC 3261) ______________

The request requires user authentication. This response is
issued 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 fulfill
it. Authorization will not help, and the request SHOULD
NOT 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 RequestURI. The response MUST include an Allow header field
containing a list of valid methods for the indicated address.

406 Not Acceptable (RFC 3261) _____________

The resource identified by the request is only capable of
generating response entities that have content
characteristics not acceptable according to the Accept
header field sent in the request.

407 Proxy Authentication Required (RFC 3261)

This response indicates that the client MUST first
authenticate itself wit the proxy.

14

SIP Pocket Guide

15



SIP Responses Class 4XX (Continued)
408 Request Timeout (RFC 3261) ___________
The server could not produce a response within a suitable
amount of time, for example, if it could not determine the
location of the user in time.

410 Gone (RFC 3261) ____________________

The requested resource is no longer available at the
server and no forwarding address is known. This condition
is 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 the
request entity-body is larger than the server is willing or
able to process.

414 Request-URI Too Long (RFC 3261) ______

The server is refusing to service the request because the
Request-URI is longer than the server is willing to
interpret.

415 Unsupported Media Type (RFC 3261) _____

The server is refusing to service the request because the
message body of the request is in a format not supported
by the server for the requested method. The server MUST
return 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 the
scheme of the URI in the Request-URI is unknown to the
server.

417 Unknown Resource-Priority (RFC 4412) ___

A request containing Require: resource-priority and an
unknown value for Resource-Priority header field will
receive the 417 Unknown Resource Priority responses..

1516

SIP Pocket Guide



SIP Responses Class 4XX (Continued)
420 Bad Extension (RFC 3261) _____________
The server did not understand the protocol extension
specified in a Proxy-Require or Require header field.

421 Extension Required (RFC 3261) _________

The UAS needs a particular extension to process the
request, but this extension is not listed in a Supported
header field in the request. Responses with this status
code MUST contain a Require header field listing the
required 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 expiration
time 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 must
provide a valid Referred-BY token.

433 Anonymity Disallowed (RFC 4079) _______

Indicates that the server refused to fulfill the request
because 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 header
contains a URI that cannot be de-referenced by the verifier
(either the URI scheme is unsupported by the verifier, or
the resource designated by the URI is otherwise
unavailable).

437 Unsupported Certificate (RFC 4474) ______

This response code is used when the verifier cannot
validate the certificate referenced by the URI of the
Identity-Info header

16

SIP Pocket Guide

17



SIP Responses Class 4XX (Continued)
438 Invalid Identity Header (RFC 4474) _______
This response code is used when the verifier receives a
message with an Identity signature that does not
correspond to the digest-string calculated by the verifier.

470 Consent Needed (RFC 5360) ___________

Indicates that the request that triggered the response
contained a URI list with at least one URI for which the
relay 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 not
logged in, logged in but in a state that precludes
communication with the callee, or has activated the "do not
disturb" feature.

481 Call/Transaction Does Not Exist (RFC 3261)

This status indicates that the UAS received a request that
does 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 MaxForwards header field with the value zero.

484 Address Incomplete (RFC 3261) _________

The server received a request with a Request-URI that
was incomplete. Additional information SHOULD be
provided in the reason phrase.

485 Ambiguous (RFC 3261) ________________

The Request-URI was ambiguous. The response MAY
contain a listing of possible unambiguous addresses in
Contact header fields.

1718

SIP Pocket Guide



SIP Responses Class 4XX (Continued)
486 Busy Here (RFC 3261) ________________
The callee's end system was contacted successfully, but
the callee is currently not willing or able to take additional
calls at this end system.

487 Request Terminated (RFC 3261) ________

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

488 Not Acceptable Here (RFC 3261) ________

The response has the same meaning as 606 (Not
Acceptable), but only applies to the specific resource
addressed by the Request-URI and the request may
succeed elsewhere.

489 Bad Event (RFC 5360) ________________

Indicates that the specified event/event class is not
understood.

491 Request Pending (RFC 3261) ___________

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

493 Undecipherable (RFC 3261) ____________

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

494 Security Agreement Required (RFC 3329) _

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

NOTES:
__________________________________________
__________________________________________

__________________________________________

18

SIP Pocket Guide

19



SIP Responses Class 5XX
Server Failure Class (5XX)
5XX responses are failure responses given when a server
itself has erred.

500 Server Internal Error (RFC 3261) ________

The server encountered an unexpected condition that
prevented it from fulfilling the request. The client MAY
display the specific error condition and MAY retry the
request 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, received
an invalid response from the downstream server it
accessed in attempting to fulfill the request.

503 Service Unavailable (RFC 3261) _________

The server is temporarily unable to process the request
due to a temporary overloading or maintenance of the
server.

504 Server Time-Out (RFC 3261) ___________

The server did not receive a timely response from an
external server it accessed in attempting to process the
request.

505 Versions Not Supported (RFC 3261) ______

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

513 Message Too Large (RFC 3261) _________

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

580 Precondition Failure (RFC 3312) _________

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

1920

SIP Pocket Guide



SIP Responses Class 6XX
Global Failure class (6XX)
6XX responses indicate that a server has definitive
information about a particular user, not just the particular
instance indicated in the Request-URI.

600 Busy Everywhere (RFC 3261) ___________

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

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 user
indicated in the Request URI does not exist anywhere.

606 Not Acceptable (RFC 3261) _____________

The user's agent was contacted successfully but some
aspects of the session description such as the requested
media, bandwidth, or addressing style were not
acceptable.

NOTES:
___________________________________________
___________________________________________
___________________________________________
___________________________________________
___________________________________________
___________________________________________
___________________________________________
___________________________________________

20

SIP Pocket Guide

21



Legend For Header Table

NOTES:
___________________________________________
___________________________________________
___________________________________________
___________________________________________
___________________________________________
___________________________________________
___________________________________________
__________________________________________

2122

SIP Pocket Guide



Header Table

22
3

SIP Pocket Guide

23



Header Table (Continued)

2324
3

SIP Pocket Guide



Header Table (Continued)

24
3

SIP Pocket Guide

25



Header Table (Continued)

2526
3

SIP Pocket Guide



Header Table (Continued)

26
3

SIP Pocket Guide

27



Header Table (Continued)

2728

SIP Pocket Guide



Header Table (Continued)

28

SIP Pocket Guide

29



Header Table (Continued)

2930

SIP Pocket Guide



Header Table (Continued)

30

SIP Pocket Guide

31



SIP Events
SIP events provide a mechanism whereby an
interested UA can be notified of the state of
another UA. The SIP events are primarily used in
the Subscribe and Notify methods.

NOTES:
___________________________________________
___________________________________________
___________________________________________
___________________________________________

3132

SIP Pocket Guide



SIP Timers

NOTES:
___________________________________________
___________________________________________
___________________________________________
___________________________________________

32

SIP Pocket Guide

33



SDP Description
SDP is used to convey information about media
streams in multimedia sessions. It allows the
recipients of a session description to participate
in the session. SDP is primarily intended for use
in an internetwork, although it is sufficiently
general that it can describe conferences in other
network environments. Media streams can be
many-to-many. Sessions need not be continually
active.

SDP Fields

NOTES:
___________________________________________
___________________________________________

3334

SIP Pocket Guide



SDP Field Description
Protocol Version
Is 0 for SDP version 0.

Origin
Contains information about the originator of the session
and 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 more
information 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 in
the format of + country code, city code and number.

Connection Data
Contains IN for Internet, the address type IP4 or IP6 for
IPv4 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 or
days, hour, and minutes.

Time Zone Corrections

Gives the time zone offset to be used, i.e., daylightsavings to standard time.

Encryption Key
Contains the encryption key for the session where the
encryption 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 session
required, i.e., audio, video, application data, telephoneevent, or control. All underlined letters indicate the short
version of the parameter names.

34

SIP Pocket Guide

35



All underlined letters indicate the short version of the parameter.

SIP Responses To ISUP Release Cause

Mapping

3536

SIP Pocket Guide



SIP Call Flow Network

NOTES:
___________________________________________
___________________________________________
___________________________________________
___________________________________________
___________________________________________
___________________________________________
___________________________________________
___________________________________________
___________________________________________

36
36

SIP Pocket Guide

37



Invite #1

NOTES:
___________________________________________
___________________________________________
___________________________________________

3738

SIP Pocket Guide



Invite #2

NOTES:
___________________________________________
___________________________________________
___________________________________________
___________________________________________

38

SIP Pocket Guide

39



100 Trying #3

100 Trying #4

NOTES:
___________________________________________
___________________________________________
___________________________________________
___________________________________________

3940

SIP Pocket Guide



180 Ringing #5

180 Ringing #6

NOTES:
___________________________________________
___________________________________________
___________________________________________

40

SIP Pocket Guide

41



200 OK #7

NOTES:
___________________________________________
___________________________________________
___________________________________________
___________________________________________

4142

SIP Pocket Guide



200 OK #8

NOTES:
___________________________________________
___________________________________________
___________________________________________
___________________________________________
___________________________________________

42

SIP Pocket Guide

43



ACK #9

ACK #9

4344

SIP Pocket Guide



Bye #11

Bye #12

44

SIP Pocket Guide

45



200 OK #13

200 OK #14

NOTES:
___________________________________________
___________________________________________

4546

SIP Pocket Guide



Registration Process

NOTES:
___________________________________________
___________________________________________
___________________________________________
___________________________________________
___________________________________________
___________________________________________
___________________________________________
___________________________________________
___________________________________________
___________________________________________

46

SIP Pocket Guide

47



Registration Messages

Register #1

402 Unauthorized #2

NOTES:
___________________________________________
___________________________________________

4748

SIP Pocket Guide



Registration Messages (Continued)
Register #3

NOTES:
___________________________________________
___________________________________________
___________________________________________
___________________________________________
___________________________________________
___________________________________________
___________________________________________
___________________________________________
___________________________________________

48

SIP Pocket Guide

49



Registration Messages (Continued)
200 OK #4

Additional Sample Messages
Cancel

NOTES:
___________________________________________
___________________________________________

4950

SIP Pocket Guide



Additional Sample Messages (Continued)
Subscribe

302 Moved Temporarily

NOTES:
___________________________________________
___________________________________________

50

SIP Pocket Guide

51



Additional Sample Messages (Continued)
401 Unauthorized

403 Forbidden

NOTES:
___________________________________________
___________________________________________
___________________________________________

5152

SIP Pocket Guide



Additional Sample Messages (Continued)
404 Unknown User Account

407 Proxy Authentication Required

NOTES:
___________________________________________
___________________________________________
___________________________________________

52

SIP Pocket Guide

53



Additional Sample Messages (Continued)
408 Request Timeout

481 Transaction Does Not Exist

487 Request Terminated

5354

SIP Pocket Guide



Glossary Of SIP Related Terms
DHCP _________________________________
Dynamic Host Configuration Protocol
DNS __________________________________
Domain Name System
IETF __________________________________
Internet Engineering Task Force
IP ____________________________________
Internet Protocol
PPP __________________________________
Point-to-Point Protocol
PSTN _________________________________
Public Switched Telephone Network
RFC __________________________________
Request for Comments
RTP___________________________________
Real-time Transport Protocol
RTSP _________________________________
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

SIP Pocket Guide

55



References

5556

SIP Pocket Guide



References (Continued)

56

SIP Pocket Guide

57



References (Continued)

5758

SIP Pocket Guide


















Although information contained in this document
resembles specifications by national or
international standards bodies, nothing
contained within this document is either
warranted or endorsed by said standards bodies.
While every effort has been taken to ensure the
accuracy of this material, errors may exist and
materials may become obsolete by more recent
additions of specifications. No development of
actual product should be undertaken without
referring to the ANSI, ITU, ETSI, IETC or IETF
specifications.

2014 Center Point Consulting, Inc.

58

SIP Pocket Guide

59


SIP Pocket
Guide

Center Point Consulting, Inc.

229 Wild 60
Oak
Drive

Swansboro, NC 28584
Tel: +1.252.422.1007
E-mail: tj.cpci@gmail.com
2014 Center Point Consulting, Inc.

SIP Pocket Guide