Technical Documentation

Types of SIP Response Classes Supported in ScreenOS Devices

SIP responses provide status information about SIP transactions and include a response code and a reason phrase. SIP responses are grouped into the following classes:

  • Informational (100 to 199)—Request received, continuing to process the request.
  • Success (200 to 299)—Action successfully received, understood, and accepted.
  • Redirection (300 to 399)—Further action required to complete the request.
  • Client Error (400 to 499)—Request contains bad syntax or cannot be fulfilled at this server.
  • Server Error (500 to 599)—Server failed to fulfill an apparently valid request.
  • Global Failure (600 to 699)—Request cannot be fulfilled at any server.

Table 1 provides a complete list of current SIP responses, all of which are supported on Juniper Networks security devices.

Table 1: SIP Responses

Class

Response Code-Reason Phrase

Response Code-Reason Phrase

Response Code-Reason Phrase

Informational

100 Trying

180 Ringing

181 Call is being forwarded

182 Queued

183 Session progress

 

Success

200 OK

202 Accepted

 

Redirection

300 Multiple choices

301 Moved permanently

302 Moved temporarily

305 Use proxy

380 Alternative service

 

Client Error

400 Bad request

401 Unauthorized

402 Payment required

403 Forbidden

404 Not found

405 Method not allowed

406 Not acceptable

407 Proxy authentication required

408 Request time-out

409 Conflict

410 Gone

411 Length required

413 Request entity too large

414 Request-URL too large

415 Unsupported media type

420 Bad extension

480 Temporarily not available

481 Call leg/transaction does not exist

482 Loop detected

483 Too many hops

484 Address incomplete

485 Ambiguous

486 Busy here

487 Request canceled

488 Not acceptable here

 

 

Server Error

500 Server internal error

501 Not implemented

502 Bad gateway

502 Service unavailable

504 Gateway time-out

505 SIP version not supported

Global Failure

600 Busy everywhere

603 Decline

604 Does not exist anywhere

606 Not acceptable

 

 


Published: 2009-08-23