Pocket Guide Sip

1 SIP Pocket Guide
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
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
100 Trying #4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
180 Ringing #5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
180 Ringing #6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
200 OK #7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Table of Contents _____________________________
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
Table of Contents (Continued) _____________________
2 SIP Pocket Guide
3 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 session 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:
4 SIP Pocket Guide
SIP USER AGENTS
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.
SIP User Agents are SIP-enabled devices that take input from users and act on
their behalf.
200 OK
NOTES:
5 SIP Pocket Guide
PRESENCE AGENTS
SIP GATEWAYS
NOTES:

Support the SIP Event Specification (RFC 3856).

Receives subscription request (SUBSCRIBE Messages).

Validates the SUBSCRIBE Messages.

Can collect presence information from multiple sources.
- User Agents publishing presence information
- Registration servers
- 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.

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.
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:
7 SIP Pocket Guide
SIP PROTOCOL STACK
M
e
d
i
a

C
o
d
i
n
g
S
D
P
R
T
S
P
T
C
P
S
C
T
P
U
D
P
I
P
S
I
P
R
T
P
D
N
S
D
H
C
P
V
.
9
0
E
t
h
e
r
n
e
t
P
P
P
S
I
G
N
A
L
I
N
G
M
E
D
I
A
U
T
I
L
I
T
Y
NOTES:
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:
user@domain
user@machine
user@ip_address
telephone_number@gateway
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.
SIP MESSAGE DEFINITIONS
NOTES:
9 SIP Pocket Guide
Item Description
Maximum
Length
Request Line /
Start Line
Identifies the message type, address of recipient
and the version of SIP
256 Bytes
Header #1
Transport specific information determined by the
header type
256 Bytes

Header #N
Transport specific information determined by the
header type
256 Bytes
Message
Body
This portion of the message contains Session
Description Protocol (SDP) which defines the
media information
1000 Bytes
GENERIC MESSAGE STRUCTURE
Item Description
Request Line /
Start Line
Identifies the message type, address of recipient, and the
version of SIP
Method
Defines the method type: ACK, BYE, CANCEL, INFO,
INVITE, MESSAGE, NOTIFY OPTIONS, PRACK, PUBLISH,
REFER, REGISTER, SUBSCRIBE, and UPDATE
Request URI Remote target address
SIP Version "SIP/2.0" current version of SIP
Message Headers Transport specific information determined by the header type
Header #1 Information for 1st header
Header #N Information for Nth header
Message Body This portion of the message contains Session Description
Protocol (SDP) which defines the media information
SDP Fields
Defines parameters associated with required media.
SDP Fields: Protocol Version Number, Owner/Creator,
Session Name, Session Info., Uniform Resource Identifier,
E-Mail Address, Phone Number, Connection Information,
Bandwidth Info., Timer Sessions (Start/Stop, Repeat Times,
and Time Zone Corrections) Encryption Key, Attribute Lines,
Media Info., and Media Attributes
SIP METHOD MESSAGE STRUCTURE
NOTES:
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).
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).
11 SIP Pocket Guide
SIP METHODS (Continued)
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:
12 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:
13 SIP Pocket Guide
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.
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.
14 SIP Pocket Guide
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 Request-URI. 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 with the
proxy.
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.
15 SIP Pocket Guide
SIP RESPONSES CLASS 4XX (Continued)
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
response.
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.
16 SIP Pocket Guide
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
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.
17 SIP Pocket Guide
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 Max-Forwards 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.
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.
NOTES:
18 SIP Pocket Guide
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 "sec-agree" MUST respond to the client with
a 494 (Security Agreement Required) response.
19 SIP Pocket Guide
Server Failure (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 Version 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.
NOTES:
20 SIP Pocket Guide
Global Failures (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:
21 SIP Pocket Guide
LEGEND FOR HEADER TABLE
Legend
Where column:
R = Header field may only appear in request
r = Header field may only appear in responses
2XX, 4XX, etc. = Numerical value of the range of response codes
c = Header field copied from the request to the responses
Empty field = Header field may be present in all request and responses
Proxy column:
a = Proxy can add or concatenate the header field if not present
m = Proxy can modify an existing header field value
d = Proxy can delete a header field value
r = Proxy must be able to read the header field value, thus this header
field cannot be encrypted
"Named Request" column:
m = Header field is mandatory
m* = Header field SHOULD be sent, however clients/servers need to be
prepared to receive the message without the header field
o = Header field is Optional
t = Header field SHOULD be sent, however clients/servers need to be
prepared to receive the message without the header field
- = Header field is not applicable
NOTES:
22 SIP Pocket Guide
HEADER TABLE
H
e
a
d
e
r

F
i
e
l
d
R
F
C
N
o
.
W
h
e
r
e
P
r
o
x
y
A
C
K
B
Y
E
C
A
N
I
N
V
O
P
T
R
E
G
P
R
A
S
U
B
N
O
T
U
P
D
M
S
G
R
E
F
I
N
F
P
U
B
A
c
c
e
p
t
3
2
6
1
R
o
m
*
o
o
o
o
o
o
o
o
A
c
c
e
p
t
3
2
6
1
2
X
X
o
m
*
o
A
c
c
e
p
t
3
2
6
1
4
1
5
c
c
c
c
o
o
c
m
*
c
o
m
*
A
c
c
e
p
t
-
C
o
n
t
a
c
t
3
2
6
1
R
a
r
o
o
o
o
o
A
c
c
e
p
t
-
E
n
c
o
d
i
n
g
3
2
6
1
R
o
o
o
o
o
o
o
o
o
o
A
c
c
e
p
t
-
E
n
c
o
d
i
n
g
3
2
6
1
2
X
X
o
m
*
o
A
c
c
e
p
t
-
E
n
c
o
d
i
n
g
3
2
6
1
4
1
5
c
c
c
c
o
o
c
m
*
c
o
m
*
A
c
c
e
p
t
-
L
a
n
g
u
a
g
e
3
2
6
1
R
o
o
o
o
o
o
o
o
o
A
c
c
e
p
t
-
L
a
n
g
u
a
g
e
3
2
6
1
2
X
X
o
m
*
o
A
c
c
e
p
t
-
L
a
n
g
u
a
g
e
3
2
6
1
4
1
5
c
c
c
c
o
o
c
m
*
c
o
m
*
A
c
c
e
p
t
-
R
e
s
o
u
r
c
e
-
P
r
i
o
r
i
t
y
4
4
1
2
2
0
0
a
m
d
r
o
o
o
o
o
o
o
o
o
o
o
o
o
A
c
c
e
p
t
-
R
e
s
o
u
r
c
e
-
P
r
i
o
r
i
t
y
4
4
1
2
4
1
7
a
m
d
r
o
o
o
o
o
o
o
o
o
o
o
o
o
A
l
e
r
t
-
I
n
f
o
3
2
6
1
R
a
r
A
l
e
r
t
-
I
n
f
o
3
2
6
1
1
8
0
a
r
A
l
l
o
w
3
2
6
1
R
o
o
o
o
o
o
o
o
o
o
23 SIP Pocket Guide
HEADER TABLE (Continued)
H
e
a
d
e
r

F
i
e
l
d
R
F
C
N
o
.
W
h
e
r
e
P
r
o
x
y
A
C
K
B
Y
E
C
A
N
I
N
V
O
P
T
R
E
G
P
R
A
S
U
B
N
O
T
U
P
D
M
S
G
R
E
F
I
N
F
P
U
B
A
l
l
o
w
3
2
6
1
2
X
X
m
*
m
*
o
o
o
o
o
o
m
A
l
l
o
w
3
2
6
1
r
o
o
o
o
o
o
o
o
o
A
l
l
o
w
3
2
6
1
4
0
5
m
m
m
m
m
m
m
m
*
m
o
A
l
l
o
w
-
E
v
e
n
t
s
3
2
6
5
R
o
o
o
o
o
o
o
o
o
A
l
l
o
w
-
E
v
e
n
t
s
3
2
6
5
2
X
X
o
o
o
o
o
o
A
l
l
o
w
-
E
v
e
n
t
s
3
2
6
5
4
8
9
m
m
m
A
n
s
w
e
r
-
M
o
d
e
5
3
7
3
A
u
t
h
e
n
t
i
c
a
t
i
o
n
-
I
n
f
o
3
2
6
1
2
X
X
o
o
o
o
o
o
o
o
o
o
A
u
t
h
o
r
i
z
a
t
i
o
n
3
2
6
1
R
o
o
o
o
o
o
o
o
o
o
o
o
o
o
C
a
l
l
-
I
D
3
2
6
1
C
r
m
m
m
m
m
m
m
m
m
m
m
m
m
m
C
a
l
l
-
I
n
f
o
3
2
6
1
a
r
o
o
o
o
o
o
C
o
n
t
a
c
t
3
2
6
1
R
o
m
o
o
m
m
m
m
o
C
o
n
t
a
c
t
3
2
6
1
1
X
X
o
o
o
C
o
n
t
a
c
t
3
2
6
1
2
X
X
m
o
o
m
o
m
C
o
n
t
a
c
t
3
2
6
1
3
X
X
d
o
o
o
o
m
m
o
o
o
o
24 SIP Pocket Guide
H
e
a
d
e
r

F
i
e
l
d
R
F
C
N
o
.
W
h
e
r
e
P
r
o
x
y
A
C
K
B
Y
E
C
A
N
I
N
V
O
P
T
R
E
G
P
R
A
S
U
B
N
O
T
U
P
D
M
S
G
R
E
F
I
N
F
P
U
B
C
o
n
t
a
c
t
3
2
6
1
4
8
5
o
o
o
o
o
o
o
o
o
o
C
o
n
t
e
n
t
-
D
i
s
p
o
s
i
t
i
o
n
3
2
6
1
o
o
o
o
o
o
o
o
o
o
o
o
C
o
n
t
e
n
t
-
E
n
c
o
d
i
n
g
3
2
6
1
o
o
o
o
o
o
o
o
o
o
o
o
o
C
o
n
t
e
n
t
-
L
a
n
g
u
a
g
e
3
2
6
1
o
o
o
o
o
o
o
o
o
o
o
o
C
o
n
t
e
n
t
-
L
e
n
g
t
h
3
2
6
1
a
r
t
t
t
t
t
t
t
t
t
t
t
t
t
t
C
o
n
t
e
n
t
-
T
y
p
e
3
2
6
1
*
*
*
*
*
*
*
*
*
*
*
*
*
C
s
e
q
3
2
6
1
C
r
m
m
m
m
m
m
m
m
m
m
m
m
m
m
D
a
t
e
3
2
6
1
a
o
o
o
o
o
o
o
o
o
o
o
o
o
o
E
r
r
o
r
-
I
n
f
o
3
2
6
1
3
0
0
-
6
9
9
a
o
o
o
o
o
o
o
o
o
o
o
o
E
v
e
n
t
3
2
6
5
R
m
m
m
E
x
p
i
r
e
s
3
2
6
1
o
o
o
o
E
X
P
I
R
E
S
3
2
6
1
2
X
X
m
m
F
r
o
m
3
2
6
1
C
r
m
m
m
m
m
m
m
m
m
m
m
m
m
m
H
i
s
t
o
r
y
-
I
n
f
o
4
2
4
4
a
m
d
r
o
o
o
o
o
o
o
o
I
d
e
n
t
i
t
y
4
4
7
4
R
a
o
o
o
o
o
o
o
o
o
o
o
o
o
25 SIP Pocket Guide
H
e
a
d
e
r

F
i
e
l
d
R
F
C
N
o
.
W
h
e
r
e
P
r
o
x
y
A
C
K
B
Y
E
C
A
N
I
N
V
O
P
T
R
E
G
P
R
A
S
U
B
N
O
T
U
P
D
M
S
G
R
E
F
I
N
F
P
U
B
I
d
e
n
t
i
t
y
-
I
n
f
o
4
4
7
4
R
a
o
o
o
o
o
o
o
o
o
o
o
o
o
I
n
-
R
e
p
l
y
-
T
o
3
2
6
1
R
r
J
o
i
n
3
9
1
1
R
M
a
x
-
F
o
r
w
a
r
d
s
3
2
6
1
R
a
m
r
m
m
m
m
m
m
m
m
m
m
m
*
m
o
m
M
i
n
-
E
x
p
i
r
e
s
3
2
6
1
4
2
3
m
M
I
M
E
-
V
e
r
s
i
o
n
3
2
6
1
o
o
o
o
o
o
o
o
o
o
o
M
i
n
-
S
E
4
0
2
8
R
a
m
r
M
i
n
-
S
E
4
0
2
8
4
2
2
O
r
g
a
n
i
z
a
t
i
o
n
3
2
6
1
a
r
o
o
o
o
o
o
o
o
P
-
A
c
c
e
s
s
-
N
e
t
w
o
r
k
-
I
n
f
o
3
4
5
5
d
r
o
o
o
o
o
o
o
o
o
o
o
P
-
A
n
s
w
e
r
-
S
t
a
t
e
4
9
6
4
1
8
X
,
2
X
X
a
r
P
-
A
n
s
w
e
r
-
S
t
a
t
e
4
9
6
4
R
P
-
A
s
s
e
r
t
e
d
-
I
d
e
n
t
i
t
y
3
3
2
5
a
d
r
o
o
o
o
P
-
A
s
s
o
c
i
a
t
e
d
-
U
R
I
3
4
5
5
2
X
X
P
-
C
a
l
l
e
d
-
P
a
r
t
y
-
I
D
3
4
5
5
R
a
m
r
o
o
o
o

26 SIP Pocket Guide
H
e
a
d
e
r

F
i
e
l
d
R
F
C
N
o
.
W
h
e
r
e
P
r
o
x
y
A
C
K
B
Y
E
C
A
N
I
N
V
O
P
T
R
E
G
P
R
A
S
U
B
N
O
T
U
P
D
M
S
G
R
E
F
I
N
F
P
U
B
P
-
C
h
a
r
g
i
n
g
-
F
u
n
c
t
i
o
n
-
A
d
d
r
e
s
s
3
4
5
5
a
d
r
o
o
o
o
o
o
o
o
o
o
o
P
-
C
h
a
r
g
i
n
g
-
V
e
c
t
o
r
3
4
5
5
a
d
m
r
o
o
o
o
o
o
o
o
o
o
o
P
-
D
C
S
-
T
r
a
c
e
-
P
a
r
t
y
-
I
D
3
6
0
3
R
d
r
P
-
D
C
S
-
O
S
P
S
3
6
0
3
R
d
r
P
-
D
C
S
-
B
i
l
l
i
n
g
-
I
n
f
o
3
6
0
3
a
d
m
r
P
-
D
C
S
-
L
A
E
S
3
6
0
3
a
d
r
P
-
D
C
S
-
R
e
d
i
r
e
c
t
3
6
0
3
a
d
r
P
-
E
a
r
l
y
-
M
e
d
i
a
5
0
0
9
R
a
m
r
P
-
E
a
r
l
y
-
M
e
d
i
a
5
0
0
9
1
8
X
a
m
r
P
-
E
a
r
l
y
-
M
e
d
i
a
5
0
0
9
2
X
X
a
m
r
P
-
M
e
d
i
a
-
A
u
t
h
o
r
i
z
a
t
i
o
n
3
3
1
3
R
a
d
o
P
-
M
e
d
i
a
-
A
u
t
h
o
r
i
z
a
t
i
o
n
3
3
1
3
2
X
X
a
d
P
-
M
e
d
i
a
-
A
u
t
h
o
r
i
z
a
t
i
o
n
3
3
1
3
1
0
1
-
1
9
9
a
d
P
-
P
r
e
f
e
r
r
e
d
-
I
d
e
n
t
i
t
y
3
3
2
5
a
d
r
o
o
o
o
P
-
P
r
o
f
i
l
e
-
K
e
y
5
0
0
2
27 SIP Pocket Guide
H
e
a
d
e
r

F
i
e
l
d
R
F
C
N
o
.
W
h
e
r
e
P
r
o
x
y
A
C
K
B
Y
E
C
A
N
I
N
V
O
P
T
R
E
G
P
R
A
S
U
B
N
O
T
U
P
D
M
S
G
R
E
F
I
N
F
P
U
B
P
-
U
s
e
r
-
D
a
t
a
b
a
s
e
4
4
5
7
P
-
V
i
s
i
t
e
d
-
N
e
t
w
o
r
k
-
I
D
3
4
5
5
R
a
d
o
o
o
o
o
P
a
t
h
3
3
2
7
R
a
r
o
P
a
t
h
3
3
2
7
2
X
X
o
P
r
i
o
r
i
t
y
3
2
6
1
R
a
r
o
o
P
r
i
v
-
A
n
s
w
e
r
-
M
o
d
e
5
3
7
3
P
r
i
v
a
c
y
3
3
2
3
a
m
d
r
o
o
o
o
o
o
o
o
o
o
o
o
o
o
P
r
o
x
y
-
A
u
t
h
e
n
t
i
c
a
t
e
3
2
6
1
4
0
7
a
r
m
m
m
m
m
m
m
m
m
o
m
P
r
o
x
y
-
A
u
t
h
e
n
t
i
c
a
t
e
3
2
6
1
4
0
1
a
r
o
o
o
o
o
o
o
o
o
o
P
r
o
x
y
-
A
u
t
h
o
r
i
z
a
t
i
o
n
3
2
6
1
R
a
r
o
o
o
o
o
o
o
o
o
o
o
o
o
P
r
o
x
y
-
R
e
q
u
i
r
e
3
2
6
1
R
a
r
o
o
o
o
o
o
o
o
o
o
o
R
A
c
k
3
2
6
2
R
m
o
R
e
a
s
o
n
3
3
2
6
R
e
c
o
r
d
-
R
o
u
t
e
3
2
6
1
R
a
r
o
o
o
o
o
o
o
o
o
o
o
R
e
c
o
r
d
-
R
o
u
t
e
3
2
6
1
2
X
X
,
1
8
X
m
r
o
o
o
o
o
o
o
o
o
o

28 SIP Pocket Guide
H
e
a
d
e
r

F
i
e
l
d
R
F
C
N
o
.
W
h
e
r
e
P
r
o
x
y
A
C
K
B
Y
E
C
A
N
I
N
V
O
P
T
R
E
G
P
R
A
S
U
B
N
O
T
U
P
D
M
S
G
R
E
F
I
N
F
P
U
B
R
e
f
e
r
-
S
u
b
4
4
8
8
R
,

2
X
X
R
e
f
e
r
-
T
o
3
5
1
5
R
R
e
f
e
r
r
e
d
-
B
y
3
8
9
2
R
o
o
o
R
e
j
e
c
t
-
C
o
n
t
a
c
t
3
8
4
1
R
a
r
o
o
o
o
o
R
e
p
l
a
c
e
s
3
8
9
1
R
R
e
p
l
y
-
T
o
3
2
6
1
R
e
q
u
e
s
t
-
D
i
s
p
o
s
i
t
i
o
n
3
8
4
1
R
a
r
o
o
o
o
o
o
R
e
q
u
i
r
e
3
2
6
1
a
r
c
c
c
c
o
o
c
c
c
o
o
R
e
s
o
u
r
c
e
-
P
r
i
o
r
i
t
y
4
4
1
2
R
a
m
d
r
o
o
o
o
o
o
o
o
o
o
o
o
o
o
R
e
t
r
y
-
A
f
t
e
r
3
2
6
1
4
0
4
,
4
1
3
,
4
8
0
,
4
8
6
o
o
o
o
o
o
o
o
o
o
o
o
o
5
0
0
,

5
0
3
o
o
o
o
o
o
o
o
o
o
o
o
o
6
0
0
,

6
0
3

o
o
o
o
o
o
o
o
o
o
o
o
o
R
o
u
t
e
3
2
6
1
R
a
d
r
c
c
c
c
c
c
c
c
c
c
o
c
o
c
R
s
e
q
3
2
6
2
1
X
X
o
o
S
e
c
u
r
i
t
y
-
C
l
i
e
n
t
3
3
2
9
R
a
r
d
o
o
o
o
o
o
o
29 SIP Pocket Guide

H
e
a
d
e
r

F
i
e
l
d
R
F
C
N
o
.
W
h
e
r
e
P
r
o
x
y
A
C
K
B
Y
E
C
A
N
I
N
V
O
P
T
R
E
G
P
R
A
S
U
B
N
O
T
U
P
D
M
S
G
R
E
F
I
N
F
P
U
B
S
e
c
u
r
i
t
y
-
S
e
r
v
e
r
3
3
2
9
4
2
1
,
4
9
4
o
o
o
o
o
o
o
S
e
c
u
r
i
t
y
-
V
e
r
i
f
y
3
3
2
9
R
a
r
d
o
o
o
o
o
o
o
o
o
S
e
r
v
e
r
3
2
6
1
r
o
o
o
o
o
o
o
o
o
o
o
S
e
r
v
i
c
e
-
R
o
u
t
e
3
6
0
8
2
X
X
a
r
S
e
s
s
i
o
n

E
x
p
i
r
e
s
4
0
2
8
R
a
m
r
S
e
s
s
i
o
n

E
x
p
i
r
e
s
4
0
2
8
2
X
X
a
r
S
I
P
-
E
T
a
g
3
9
0
3
2
X
X
m
S
I
P
-
I
f
-
M
a
t
c
h
3
9
0
3
R
o
S
u
b
j
e
c
t
3
2
6
1
R
o
o
S
u
b
s
c
r
i
p
t
i
o
n
-
S
t
a
t
e
3
2
6
5
R
o
S
u
p
p
o
r
t
e
d
3
2
6
1
R
o
o
m
*
o
o
o
o
o
o
o
o
S
u
p
p
o
r
t
e
d
3
2
6
1
2
X
X
o
o
m
*
m
*
o
o
o
o
o
o
o
T
a
r
g
e
t
-
D
i
a
l
o
g
4
5
3
8
T
i
m
e
s
t
a
m
p
3
2
6
1
o
o
o
o
o
o
o
o
o
o
o
o
o
T
o
3
2
6
1
C
r
m
m
m
m
m
m
m
m
m
m
m
m
m
30 SIP Pocket Guide
H
e
a
d
e
r

F
i
e
l
d
R
F
C
N
o
.
W
h
e
r
e
P
r
o
x
y
A
C
K
B
Y
E
C
A
N
I
N
V
O
P
T
R
E
G
P
R
A
S
U
B
N
O
T
U
P
D
M
S
G
R
E
F
I
N
F
P
U
B
T
r
i
g
g
e
r
-
C
o
n
s
e
n
t
5
3
6
0
U
n
s
u
p
p
o
r
t
e
d
3
2
6
1
4
2
0
m
m
m
m
o
o
m
o
o
o
o
U
s
e
r
-
A
g
e
n
t
3
2
6
1
o
o
o
o
o
o
o
o
o
o
o
o
o
o
V
i
a
3
2
6
1
R
a
m
r
m
m
m
m
m
m
m
m
m
m
m
m
m
m
V
i
a
3
2
6
1
r
c
d
r
m
m
m
m
m
m
m
m
m
m
m
m
m
m
W
a
r
n
i
n
g
3
2
6
1
r
o
o
o
o
o
o
o
o
o
o
o
o
W
W
W
-
A
u
t
h
e
n
t
i
c
a
t
e
3
2
6
1
4
0
1
a
r
m
m
m
m
m
m
m
m
m
o
m
W
W
W
-
A
u
t
h
e
n
t
i
c
a
t
e
3
2
6
1
4
0
7
a
r
o
o
o
o
o
o
o
o
o
o
o
NOTES:
31 SIP Pocket Guide
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.
SIP EVENTS
Event Description RFC
Conference
Provides a list of URIs for participants of the
conference.
4575
Dialog
Allows the subscribed party to be notified if the
target changes state.
4235
KPML
Enables monitoring of Dual Tone Multi-Frequency
(DTMF) signals and uses Extensible Markup
Language (XML) documents referred to as Key
Press Markup Language (KPML).
4730
Message/
Summary/
Message Waiting
Carries message waiting status and message sum-
maries from a messaging system to an interested
User Agent.
3842
PoC-Settings
Supports publication, subscription, and notification of
additional capabilities required by the "Push to Talk
over Cellular" service.
4354
Presence
Presence, also known as presence information,
conveys the ability and willingness of a user to
communicate across a set of devices.
3856
Registrations
Allows the subscribed to be notified if the target has
a change in registration.
3680
Refer
Is used in a call transfer to indicate to the transferor
the states of the transfer.
3515
Winfo
Watcher information refers to the set of users
subscribed to a particular resource within a particular
event package.
3857
32 SIP Pocket Guide
SIP TIMERS
SIP TIMERS
Timer Value RFC 3261 Section Meaning
T1 500 ms Default
Section 17.1.1.1 RTT Estimate
T2 4S
Section 17.1.2.2
The maximum retransmit
interval for non-INVITE
requests and INVITE
responses
T4 5S
Section 17.1.2.2
Maximum duration a
message will remain in
the network
Timer A initially T1
Section 17.1.1.2
INVITE request retransmit
interval, for UDP only
Timer B 64*T1
Section 17.1.1.2
INVITE transaction
timeout timer
Timer C > 3min
Section 16.6 bullet 11
proxy INVITE transaction
timeout
Timer D
> 32s for UDP 0s
for TCP/SCTP
Section 17.1.1.2
Wait time for response
retransmits
Timer E initially T1
Section 17.1.2.2
non-INVITE request
retransmit interval,
UDP only
Timer F 64*T1
Section 17.1.2.2
non-INVITE transaction
timeout timer
Timer G initially T1
Section 17.2.1
INVITE response
retransmit interval
Timer H 64*T1
Section 17.2.1 Wait time for ACK receipt
Timer I
T4 for UDP 0s for
TCP/SCTP
Section 17.2.1
Wait time for ACK
retransmits
Timer J
64*T1 for UDP 0s
for TCP/SCTP
Section 17.2.2
Wait time for non-INVITE
request retransmits
Timer K
T4 for UDP 0s for
TCP/SCTP
Section 17.1.2.2
Wait time for response
retransmits
NOTES:
33 SIP Pocket Guide
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
Field Name
Mandatory/
Optional
v Protocol Version
m
o Origin
m
s Session Name
m
i Session Information
o
u Uniform Resource Identifier
o
e Email Address
o
p Phone Number
o
c Connection Data
m
b Bandwidth Information
m
t Time Sessions Starts and Stops
m
r Repeat Times
o
z Time Zone Corrections
o
k Encryption Key
o
a Attribute Lines
o
m Media Information
o
NOTES:
34 SIP Pocket Guide
SDP FIELD DESCRIPTIONS
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., daylight-savings 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, telephone-event, or control.
All underlined letters indicate the short version of the parameter names.
35 SIP Pocket Guide
SIP RESPONSES TO ISUP RELEASE CAUSE MAPPING
SIP to ISUP Mapping
# Received Response # ISUP Cause Value
400 Bad Request
41 Temporary Failure
401 Unauthorized
21 Call Rejected
402 Payment Required
21 Call Rejected
403 Forbidden
21 Call Rejected
404 Not Found
1 Unallocated Number
405 Method Not Allowed
63 Service or Option Unavailable
406 Not Acceptable
79 Service or Option Not Implemented
407 Proxy Authentication Required
21 Call Rejected
408 Request Timeout
102 Recovery on Timer Expiry
410 Gone
22 Number Changed w/o Diagnostics
413 Request Entity Too Long
127 Interworking
414 Request URI Too Long
127 Interworking
415 Unsupported Media Type
416 Unsupported URI Scheme
127 Interworking
420 Bad Extension
127 Interworking
421 Extension Required
127 Interworking
423 Interval Too Brief
127 Interworking
480 Temporarily Unavailable
18 No User Responding
481 Call/Transaction Does Not Exist
482 Loop Detected
25 Exchange Error Routing
483 Too Many Hops
25 Exchange Error Routing
484 Address Incomplete
28 Invalid Number Format
485 Ambiguous
486 Busy Here
17 User Busy
487 Request Terminated
(NOT MAPPED)
488 Not Accepted Here
(NOT MAPPED)
500 Server Internal Error
501 Not Implemented
502 Bad Gateway
38 Network Out of Order
503 Service Unavailable
504 Server Timeout
102 Recovery on Timer Expiry
505 Version Not Supported
127 Interworking
513 Message Too Large
127 Interworking
600 Busy Everywhere
17 User Busy
603 Decline
21 Call Rejected
604 Does Not Exist Anywhere
606 Not Acceptable
(NOT MAPPED)
36 SIP Pocket Guide
SIP CALL FLOW NETWORK
NOTES:
37 SIP Pocket Guide
Request
Line
INVITE sip:9103682854@192.168.16.140 SIP/2.0
Headers
Via: SIP/2.0/UDP 192.168.16.105:44646;branch=z9hG4bK-d8754z-
2651db598629a27e-1---d8754z-;rport
Max-Forwards: 70
Contact: <sip:9103683957@192.168.16.105:44646
To: "Jane Doe"<sip:9103682854@192.168.16.140
From: "John
Smith"<sip:9103683957@192.168.16.140>;tag=5c06d71d
Call-ID:
Yzk2ZjQ5YzJhOWVmNTJmNjk5MWMxYmMxMmJiNzQwOTg.
CSeq: 2 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY,
MESSAGE, SUBSCRIBE, INFO
Content-Type: application/sdp
Proxy-Authorization: Digest username="9103683957",realm
="192.168.16.140",nonce="2b028e9e929f845f097aa41196e511ac",ur
i="sip:9103682854@192.168.16.140",response="e714b87b94f9f5d4c
a3b288984963fb5",cnonce="dc58e9e10d0a63b19d65b1380324a101
",nc=
User-Agent: X-Lite release 1104o stamp 56125
Content-Length: 322
Empty Line
Message
Body
v=0
o=- 3 2 IN IP4 192.168.16.105
s=CounterPath X-Lite 3.0
c=IN IP4 192.168.16.105
t=0 0
m=audio 32854 RTP/AVP 107 0 8 101
a=alt:1 2 : oND7cBBb qhQukSDp 10.100.100.250 32854
a=alt:2 1 : napYhQOC H731+lWt 192.168.16.105 32854
a=fmtp:101 0-15
a=rtpmap:107 BV32/16000
a=rtpmap:101 telephone-event/8000
a=sendrecv
INVITE #1
NOTES:
38 SIP Pocket Guide
Request
Line
INVITE sip:9103682854@192.168.16.102:56912 SIP/2.0
Headers
Via: SIP/2.0/UDP 192.168.16.140:5060;branch=z9hG4bK-
85z25d58d7461b9
2651db598629a27e-1---d8754z-
;received=192.168.16.105;rport=44646
Max-Forwards: 69
Contact: <sip:9103683957@192.168.16.105:44646>
To: "Jane Doe"<sip:9103682854@192.168.16.140>
From: "John
Smith"<sip:9103683957@192.168.16.140>;tag=5c06d71d
Call-ID:
CSeq: 2 INVITE
Record-Route: <sip:192.168.16.140;lr>
Content-Length: 322
Empty Line
Message
Body
SDP
v=0
o=- 3 2 IN IP4 192.168.16.105
c=IN IP4 192.168.16.105
t=0 0
m=audio 32854 RTP/AVP 107 0 8 101
a=alt:1 2 : oND7cBBb qhQukSDp 10.100.100.250 32854
a=alt:2 1 : napYhQOC H731+lWt 192.168.16.105 32854
a=fmtp:101 0-15
a=rtpmap:107 BV32/16000
INVITE #2
NOTES:
39 SIP Pocket Guide
100 TRYING #3
Request
Line
SIP/2.0 100 Trying
Headers
85z25d58d7461b9
2651db598629a27e-1---d8754z-
;received=192.168.16.105;rport=44646
To: "Jane Doe"<sip:9103682854@192.168.16.140
From: "John
Smith"<sip:9103683957@192.168.16.140>;tag=5c06d71d
Call-ID:
CSeq: 2 INVITE
Content-Length: 0
100 TRYING #4
Request
Line
SIP/2.0 100 Trying
Headers
2651db598629a27e-1---d8754z-
;received=192.168.16.105;rport=44646
To: "Jane Doe"<sip:9103682854@192.168.16.140
From: "John
Smith"<sip:9103683957@192.168.16.140>;tag=5c06d71d
Call-ID:
CSeq: 2 INVITE
Max-Forwards: 70
Record-Route: <sip:192.168.16.140;lr>
Content-Length: 0
NOTES:
40 SIP Pocket Guide
180 RINGING #5
Request
Line
SIP/2.0 180 Ringing
Headers
85z25d58d7461b9
2651db598629a27e-1---d8754z-
;received=192.168.16.105;rport=44646
Record-Route: <sip:192.168.16.140;lr
Contact: <sip:9103682854@192.168.16.102:56912
To: "Jane Doe"<sip:9103682854@192.168.16.140>;tag=f63e876c
From: "John
Smith"<sip:9103683957@192.168.16.140>;tag=5c06d71d
Call-ID:
CSeq: 2 INVITE
Content-Length: 0
Request
Line
SIP/2.0 180 Ringing
Headers
2651db598629a27e-1---d8754z-
;received=192.168.16.105;rport=44646
Contact: <sip:9103682854@192.168.16.102:56912
From: "John
Smith"<sip:9103683957@192.168.16.140>;tag=5c06d71d
Call-ID:
CSeq: 2 INVITE
Max-Forwards: 70
Content-Length: 0
180 RINGING #6
NOTES:
41 SIP Pocket Guide
200 OK #7
Request
Line
SIP/2.0 200 OK
Headers
85z25d58d7461b9
2651db598629a27e-1---d8754z-
;received=192.168.16.105;rport=44646
Contact: <sip:9103682854@192.168.16.102:56912
From: "John
Smith"<sip:9103683957@192.168.16.140>;tag=5c06d71d
Call-ID:
CSeq: 2 INVITE
Content-Length: 270
Empty Line
Message
Body
SDP
v=0
o=- 8 2 IN IP4 192.168.16.102
c=IN IP4 192.168.16.102
t=0 0
m=audio 10574 RTP/AVP 107 0 8 101
a=alt:1 1 : EBcwd5ZA XQt5DSSm 192.168.16.102 10574
a=fmtp:101 0-15
a=rtpmap:107 BV32/16000
a=sendrecv
NOTES:
42 SIP Pocket Guide
200 OK #8
Request
Line
SIP/2.0 200 OK
Headers
2651db598629a27e-1---d8754z-
;received=192.168.16.105;rport=44646
Contact: <sip:9103682854@192.168.16.102:56912
From: "John
Smith"<sip:9103683957@192.168.16.140>;tag=5c06d71d
Call-ID:
CSeq: 2 INVITE
Max-Forwards: 70
Content-Length: 270
Empty Line
Message
Body
SDP
v=0
o=- 8 2 IN IP4 192.168.16.102
c=IN IP4 192.168.16.102
t=0 0
m=audio 10574 RTP/AVP 107 0 8 101
a=alt:1 1 : EBcwd5ZA XQt5DSSm 192.168.16.102 10574
a=fmtp:101 0-15
a=rtpmap:107 BV32/16000
a=sendrecv
NOTES:
43 SIP Pocket Guide
ACK #9
Request
Line
ACK sip:9103682854@192.168.16.102:56912 SIP/2.0
Headers
cd63ad64065fb73c-1---d8754z-;rport
Max-Forwards: 70
Route: <sip:192.168.16.140;lr
Contact: <sip:9103683957@192.168.16.105:44646
From: "John
Smith"<sip:9103683957@192.168.16.140>;tag=5c06d71d
Call-ID:
CSeq: 2 ACK
Proxy-Authorization: Digest user-
name="9103683957",realm="192.168.16.140",nonce="2b028e9e929f
845f097aa41196e511ac",uri="sip:9103682854@192.168.16.140",res
ponse="e714b87b94f9f5d4ca3b288984963fb5",cnonce="dc58e9e10
d0a63b19d65b1380324a101",nc=
Content-Length: 0
ACK #10
Request
Line
ACK sip:9103682854@192.168.16.102:56912 SIP/2.0
Headers
85zc6a60d74d3d4
cd63ad64065fb73c-1---d8754z-
;received=192.168.16.105;rport=44646
Max-Forwards: 69
Contact: <sip:9103683957@192.168.16.105:44646
From: "John
Smith"<sip:9103683957@192.168.16.140>;tag=5c06d71d
Call-ID:
CSeq: 2 ACK
Route: <sip:192.168.16.140;lr
Content-Length: 0
44 SIP Pocket Guide
BYE #11
Request
Line
BYE sip:9103682854@192.168.16.102:56912 SIP/2.0
Headers
f8728d218024a502-1---d8754z-;rport
Max-Forwards: 70
Route: <sip:192.168.16.140;lr>
Contact: <sip:9103683957@192.168.16.105:44646>
From: "John
Smith"<sip:9103683957@192.168.16.140>;tag=5c06d71d
Call-ID:
CSeq: 3 BYE
Proxy-Authorization: Digest user-
name="9103683957",realm="192.168.16.140",nonce="2b028e9e929f
845f097aa41196e511ac",uri="sip:9103682854@192.168.16.102:569
12",response="4fe9122045c410cf3b5c2b2f828142e3",cnonce="ffec2
900d9477f14248fcbb76b4d020
Reason: SIP;description="User Hung Up"
Content-Length: 0
BYE #12
Request
Line
BYE sip:9103682854@192.168.16.102:56912 SIP/2.0
Headers
85zf7828d7482d1
f8728d218024a502-1---d8754z-
;received=192.168.16.105;rport=44646
Max-Forwards: 69
Contact: <sip:9103683957@192.168.16.105:44646
From: "John
Smith"<sip:9103683957@192.168.16.140>;tag=5c06d71d
Call-ID:
CSeq: 3 BYE
Reason: SIP;description="User Hung Up"
Route: <sip:192.168.16.140;lr
Content-Length: 0
45 SIP Pocket Guide
200 OK #13
Request
Line
SIP/2.0 200 OK
Headers
85zf7828d7482d
f8728d218024a502-1---d8754z-
;received=192.168.16.105;rport=44646
Contact: <sip:9103682854@192.168.16.102:56912
To: "Jane Doe"<sip:9103682854@192.168.16.140>;tag=f63e876
From: "John
Smith"<sip:9103683957@192.168.16.140>;tag=5c06d71
Call-ID:
CSeq: 3 BYE
Content-Length: 0
Request
Line
SIP/2.0 200 OK
Headers
f8728d218024a502-1---d8754z-
;received=192.168.16.105;rport=44646
Contact: <sip:9103682854@192.168.16.102:56912
From: "John
Smith"<sip:9103683957@192.168.16.140>;tag=5c06d71d
Call-ID:
CSeq: 3 BYE
Max-Forwards: 70
Content-Length: 0
200 OK #14
NOTES:
46 SIP Pocket Guide
REGISTRATION PROCESS
NOTES:
47 SIP Pocket Guide
REGISTRATION MESSAGES
Register #1
Request
Line
REGISTER sip:192.168.16.140 SIP/2.0
Headers
f64d606d85428835-1---d8754z-;rport
Max-Forwards: 70
Contact: <sip:9103682854@192.168.16.102:10658;rin-
stance=c1bbc08e764e1a59>
To: Jane Doe"<sip:9103682854@192.168.16.140>
From: Jane
Doe"<sip:9103682854@192.168.16.140>;tag=74215226
Call-ID: MjNmYjBlZjhiODJiZmI4MjdhMzViNmIyMDFkNzk5MzQ.
CSeq: 1 REGISTER
Expires: 3600
Content-Length: 0
402 Unauthorized #2
Request
Line
SIP/2.0 401 Unauthorized
Headers
f64d606d85428835-1---d8754z-
;received=192.168.16.102;rport=10658
To: Jane Doe"<sip:9103682854@192.168.16.140>
From: Jane
Doe"<sip:9103682854@192.168.16.140>;tag=74215226
CSeq: 1 REGISTER
WWW-Authenticate: Digest realm="192.168.16.140",qop="auth",
nonce="b409d25d445aa41753167c2d96645524",opaque="",stale=F
ALSE
Server: TekSIP/v2.7
Content-Length: 0
NOTES:
48 SIP Pocket Guide
REGISTRATION MESSAGES (Continued)
Register #3
Request
Line
REGISTER sip:192.168.16.140 SIP/2.0
Headers
8c733834e54a867d-1---d8754z-;rport
Max-Forwards: 70
Contact: <sip:9103682854@192.168.16.102:10658;rin-
To: Jane Doe"<sip:9103682854@192.168.16.140>
From: Jane
Doe"<sip:9103682854@192.168.16.140>;tag=74215226
CSeq: 2 REGISTER
Expires: 3600
[truncated] Authorization: Digest user-
name="9103682854",realm="192.168.16.140",nonce="b409d25d445
aa41753167c2d96645524",
uri="sip:192.168.16.140",response="3017cba4e1a09d6deafdbb876cf
f13ca",cnonce=
"6def0392c6f264bc88216693693ec23a",nc=00000001,qo
Content-Length: 0
NOTES:
49 SIP Pocket Guide
200 OK #4
Status
Line
SIP/2.0 200 OK
Headers
8c733834e54a867d-1---d8754z-
;received=192.168.16.102;rport=10658
Max-Forwards: 69
Contact: <sip:9103682854@192.168.16.102:10658; rin-
To: Jane Doe"<sip:9103682854@192.168.16.140>;tag=43a8aa5e
From: Jane
Doe"<sip:9103682854@192.168.16.140>;tag=74215226
CSeq: 2 REGISTER
Allow: INVITE, BYE, CANCEL, OPTIONS, ACK, REGISTER, SUB-
SCRIBE, PUBLISH
Server: TekSIP/v2.7
Date: Fri, 30 Jul 2010 15:19:23 GMT
Allow-Events: presence, presence.winfo, message-summary
Expires: 3600
Content-Length: 0
REGISTRATION MESSAGES (Continued)
Cancel
ADDITIONAL SAMPLE MESSAGES
Request
Line
CANCEL sip:9103683957@192.168.16.140 SIP/2.0
Headers
From:sip:9193682854@192.168.16.124;tag=206c220a
To:"John Smith" <sip:9103683957@192.168.16.140>
Call-ID:89ba95c0a00025ac4c52f44c62f6a
CSeq:32042 CANCEL
Via:SIP/2.0/UDP 192.168.16.124;branch=z9hG4bK5vz9fc21
Contact:<sip:9193682854@192.168.16.124>
Max-Forwards:70
User-Agent:Whistle/iPhone 1.11 (VailSIP 20100330)
Content-Length:0
NOTES:
50 SIP Pocket Guide
Subscribe
ADDITIONAL SAMPLE MESSAGES (Continued)
Request
Line
SUBSCRIBE sip:9103683957@192.168.16.140 SIP/2.0
Headers
286c717328298f0b-1---d8754z-;rport
Max-Forwards: 70
Contact: <sip:9103683957@192.168.16.105:35948
To: "John Smith"<sip:9103683957@192.168.16.140>
From: "John
Smith"<sip:9103683957@192.168.16.140>;tag=c178351b
Call-ID:
MmM3OTdjY2EzYjhjM2M3NGNiMmFlYTlmMGM4NDNkYzQ.
CSeq: 1 SUBSCRIBE
Expires: 300
Event: message-summary
Content-Length: 0
302 Moved Temporarily
Status
Line
SIP/2.0 302 Moved Temporarily
Headers
7608a74aaf06f27b-1---d8754z-
;received=192.168.16.105;rport=44646
To: "Operator"<sip:0@192.168.16.140
From: "John
Smith"<sip:9103683957@192.168.16.140>;tag=ba2caa50
Call-ID:
MTZhOWZkMTNmMjMwODZiMzUwNzlhOTIzMDUyNjAwMGY.
CSeq: 1 INVITE
Contact: <sip:TekIVR@192.168.16.140
Server: TekSIP/v2.7
Content-Length: 0
NOTES:
51 SIP Pocket Guide
401 Unauthorized
Status
Line
SIP/2.0 401 Unauthorized
Headers
Via: SIP/2.0/UDP 192.168.16.105:44646;branch=z9hG4bK- d8754z-
57270431f4098616-1---d8754z-
;received=192.168.16.105;rport=44646
To: "John Smith"<sip:9103683957@192.168.16.140>
From: "John
Smith"<sip:9103683957@192.168.16.140>;tag=80131533
Call-ID:
NGU3ODEyMjZmMTA2NmVjMWNhMTgxYzJmODY2MTcyYTg.
CSeq: 1 SUBSCRIBE
WWW-Authenticate: Digest realm="192.168.16.140", qop="auth",
nonce="722568b6b454974a153a48f363aa21a8", opaque="",
stale=FALSE
Server: TekSIP/v2.7
Content-Length: 0
403 Forbidden
Status
Line
SIP/2.0 403 Forbidden
Headers
Via: SIP/2.0/UDP 192.168.16.105:44646;branch=z9hG4bK- d8754z-
8c2d83501a781052-1---d8754z-
;received=192.168.16.105;rport=44646
To: "John Smith"<sip:9103683957@192.168.16.140>
From: "John
Smith"<sip:9103683957@192.168.16.140>;tag=932b104c
Call-ID: ZWFlMjEzZTk2NGI0MGQzM2NmM2JjYTczYTQyYzE1Mzc.
CSeq: 2 SUBSCRIBE
Server: TekSIP/2.7
Content-Length: 0
NOTES:
52 SIP Pocket Guide
407 Proxy Authentication Required
Status
Line
SIP/2.0 407 Proxy Authentication Required
Headers
436c29051a613325-1---d8754z-
;received=192.168.16.105;rport=44646
To: "Jane Doe"<sip:9103682854@192.168.16.140>
From: "John
Smith"<sip:9103683957@192.168.16.140>;tag=f432004c
Call-ID:
MzZlNWZkMWQ3MmYyMTBkNGJmZTYyYzAzNDRjZGNjZTY.
CSeq: 1 INVITE
Proxy-Authenticate: Digest realm="192.168.16.140", qop="auth",
nonce="2809403cbd9d849c8193a3c1945100bb", opaque="",
stale=FALSE
Server: TekSIP/v2.7
Max-Forwards: 70
Content-Length: 0
NOTES:
404 Unknown User Account
Status
Line
SIP/2.0 404 Unknown user account
Headers
e937b55f7a01eb67-1---d8754z-
;received=192.168.16.105;rport=44646
To: "Operator"<sip:0@192.168.16.140>
From: "John
Smith"<sip:9103683957@192.168.16.140>;tag=ba2caa50
Call-ID:
MTZhOWZkMTNmMjMwODZiMzUwNzlhOTIzMDUyNjAwMGY.
CSeq: 2 INVITE
Server: TekSIP/v2.7
Content-Length: 0
53 SIP Pocket Guide
408 Request Timeout
Status Line SIP/2.0 408 Request Timeout
Headers
85zc6b38d7423a3;received=208.69.225.66
c263ba338c372e5b-1---d8754z-
;received=192.168.16.105;rport=44646
To: "15402042001"<sip:15402042001@sip.callwithus.com>;tag=
8e6t8arXaZr8m
From: "John
Smith"<sip:9103683957@sip.callwithus.com>;tag=61163c00
Call-ID:
OWY2N2QzODU5OGZhNjkzNmE4MmE3YjcyOTA3ZDM4YTQ.
CSeq: 3 BYE
Server: CWU SIP GW
Content-Length: 0
481 Transaction Does Not Exist
Status Line SIP/2.0 481 Call/Transaction Does Not Exist
Headers
Via: SIP/2.0/UDP 192.168.16.140:5060;branch=z9hG4bK-pOuOgO6t
Via: SIP/2.0/UDP 192.168.16.124;branch=z9hG4bKpgOOu6Ot;
received=192.168.16.124
To: "John Smith"<sip:9103683957@192.168.16.140>;tag=9317f75f
From: <sip:3333@192.168.16.140>;tag=2f488d9b
Call-ID: 9b5a99ed1f38aabb4c52f472c4872
CSeq: 26145 BYE
Accept-Language: en
Content-Length: 0
487 Request Terminated
Status Line SIP/2.0 487 Request Terminated
Headers
Via: SIP/2.0/UDP 192.168.16.140:5060;branch=z9hG4bK-5zf2v9c1
Via: SIP/2.0/UDP
192.168.16.124;branch=z9hG4bK5vz9fc21;received=192.168.16.124
To: "John Smith"<sip:9103683957@192.168.16.140>;tag=fe3ce576
From: <sip:3333@192.168.16.140>;tag=206c220a
Call-ID: 89ba95c0a00025ac4c52f44c62f6a
CSeq: 32044 INVITE
Content-Length: 0
54 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
55 SIP Pocket Guide
REFERENCES
RFC 2976
RFC 3261
RFC 3262
RFC 3265
RFC 3311
RFC 3312
RFC 3313
RFC 3323
RFC 3325
RFC 3326
RFC 3327
RFC 3329
RFC 3372
RFC 3398
RFC 3428
RFC 3455
RFC 3515
RFC 3578
RFC 3588
RFC 3603
RFC 3605
The SIP INFO Method
SIP: Session Initiation Protocol
Reliability of Provisional Responses in Session Initiation Protocol
(SIP)
Session Initiation Protocol (SIP) - Specific Event Notification
The Session Initiation Protocol (SIP) UPDATE Method
Integration of Resource Management and Session Initiation
Protocol (SIP)
Private Session Initiation Protocol (SIP) Extensions for Media
Authorization
A Privacy Mechanism for the Session Initiation Protocol (SIP)
Private Extensions to the Session Initiation Protocol (SIP) for
Asserted Identity within Trusted Networks
The Reason Header Field for the Session Initiation Protocol
(SIP)
Session Initiation Protocol (SIP) Extension Header Field for
Registering Non-Adjacent Contracts
Security Mechanism Agreement for the Session Initiation
Protocol (SIP)
Session Initiation Protocol for Telephones (SIP-T): Context and
Architectures
Integrated Services Digital Network (ISDN) User Part (ISUP) to
Session Initiation Protocol (SIP) Mapping
Session Initiation Protocol (SIP) Extension for Instant Messaging
Private Header (P-Header) Extensions to the Session Initiation
Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP)
The Session Initiation Protocol (SIP) Refer Method
Mapping of Integrated Services Digital Network (ISDN) User Part
(ISUP) Overlap Signaling to the Session Initiation Protocol (SIP)
Diameter Base Protocol
Private Session Initiation Protocol (SIP) Proxy-to-Proxy
Extensions for Supporting the PacketCable Distributed Call
Signaling Architecture
Real Time Control Protocol (RTCP) Attribute in Session
Description Protocol (SDP)
56 SIP Pocket Guide
REFERENCES (Continued)
RFC 3608
RFC 3841
RFC 3891
RFC 3892
RFC 3903
RFC 3911
RFC 4028
RFC 4244
RFC 4354
RFC 4412
RFC 4457
RFC 4474
RFC 4488
RFC 4538
RFC 4566
RFC 4964
RFC 5002
RFC 5009
RFC 5079
RFC 5360
Session Initiation Protocol (SIP) Extension Header Field for
Service Route Discovery During Registration
Caller Preferences for the Session Initiation Protocol (SIP)
The Session Initiation Protocol (SIP) Replaces Header
The Session Initiation Protocol (SIP) Referred-By Mechanism
Session Initiation Protocol (SIP)
Extension for Event State Publication
The Session Initiation Protocol (SIP) Join Header
Session Timers in the Session Initiation Protocol (SIP)
An Extension to the Session Initiation Protocol (SIP) for Request
History Information
A Session Initiation Protocol (SIP) Event Package and Data
Format for Various Settings in Support for the Push-to-Talk over
Cellular (PoC) Service
Communications Resource Priority for the Session Initiation
Protocol (SIP)
The Session Initiation Protocol (SIP) P-User-Database Private-
Header (P-Header)
Enhancements for Authenticated Identify Management in the
Suppression of Session Initiation Protocol (SIP) REFER Method
Implicit Subscription
Request Authorization through Dialog Identification in the
SDP: Session Description Protocol
The P-Answer-State Header Extension to the Session Initiation
Protocol for the Open Mobile Alliance Push-to-Talk over Cellular
The Session Intiation Protocol (SIP) P-Profile-Key Private
Header (P-Header)
Private Header (P-Header) Extension to the Session Initiation
Protocol (SIP) for Authorization of Early Media
Rejecting Anonymous Requests in the Session Initiation Protocol
(SIP)
A Framework for Consent-Based Communications in the Session
Initiation Protocol (SIP)
57 SIP Pocket Guide
REFERENCES (Continued)
RFC 5373
RFC 5503
RFC 5630
RFC 5876
Requesting Answering Modes for the Session Initiation Protocol
(SIP)
Private Session Initiation Protocol (SIP) Proxy-to-Proxy
Extensions for Supporting the PacketCable Distributed Call
Signaling Architecture
The Use of the SIPS URI Scheme in the Session Initiation
Protocol (SIP)
Updates to Asserted Identify in the Session Initiation Protocol
(SIP)
The Internet Engineering Task Force: www.ietf.org
Johnston, Alan B., SIP Understanding the Session Initiation
Protocol (2009, ARTECH HOUSE Norwood MA)
Camarillo, Gonzalo, SIP Demystified (2002, McGraw-Hill)
Sinnreich, Henry & Johnston, Alan B. Internet Communications
Using SIP (2006, Wiley Publishing, Indianapolis, IN)
Jenkins, Thomas W. SIP to ISUP Mapping course (2004,
Center Point Consulting, Inc., Swansboro, NC)
Jenkins, Thomas W. SIP Protocol course (2004, Center Point
Consulting, Inc., Swansboro, NC)
58 SIP Pocket Guide
NOTES: NOTES:

Pocket Guide Sip

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Pocket Guide Sip

Uploaded by

Copyright:

Available Formats

1 SIP Pocket Guide

HEADER TABLE (Continued)

HEADER TABLE (Continued)

29 SIP Pocket Guide

You might also like