HP-UX Java SIP Stack Programmer's Guide (February 2008)

SIP/2.0 200 OK
Via: SIP/2.0/UDP local.hp.com;received=16.1.55.40
From: <sip:[e-mail]>
To: TPU <sip:[e-mail]>
Call-ID: [e-mail]
Content-Type: application/sdp
CSeq: 1 INVITE
Contact: <sip:tpu@16.188.155.20>
Content-Length: 187
v=0
o=user1 51633745 1348648134 IN IP4 16.188.155.20
s=Interactive Conference
c=IN IP4 224.2.4.4/127
t=0 0
m=audio 3456 RTP/AVP 0 22
a=rtpmap:22 application/g723.1
The status line at the beginning of the response message differentiates this message
from a request message. This line consists of the protocol version followed by a numeric
status-code and its associated textual phrase, with each element separated by a single
space (SP) character.
The status line contains the following information: SIP version, SIP status code, and
the SIP reason phrase. The first digit of the status code defines the class of response.
The last two digits do not carry any specific meaning, but the range of the status code
defines the type of response code. For example, if the response code is within the range
100 and 199, it is a 1xx response and this response is called a provisional response.
Table 1-1 discusses the response types.
Table 1-1 Response Types
DescriptionReason PhraseResponse Code
Specifies that the request is received and the server is
processing the request.
Provisional
1xx
Specifies that the action was successfully received,
understood, and accepted by the server.
Success
2xx
Specifies that further action needs to be taken in order
to complete the request.
Redirection
3xx
Specifies that the request contains a bad syntax or that
the request cannot be fulfilled at the server.
Client error
4xx
Specifies that the server failed to fulfill a valid request.Server error
5xx
Specifies that the request cannot be fulfilled at any
server.
Global failure
6xx
Table 1-2 discusses the response codes for each response type.
SIP Messages 25