Types Of Sip Response Classes Supported In Screenos Devices - Juniper NETWORK AND SECURITY MANAGER 2010.4 - CONFIGURING SCREENOS DEVICES GUIDE REV 01 Manual

Configuring ScreenOS Devices Guide
Related
Documentation

Types of SIP Response Classes Supported in ScreenOS Devices

284
Table 70: SIP Request Methods (continued)
Method
Types/Response
Codes Description
Notify Sent to inform subscribers of changes
in state to which the subscriber has
a subscription. In NAT mode, the IP
address in the Request-URL header
field is changed to a private IP
address if the message is coming
from the external network into the
internal network.
Refer Used to refer the recipient (identified
by the Request-URI) to a third party
by the contact information provided
in the request.
Update Used to open pinhole for new or
updated SDP information
1xx, 202, 2xx, 3xx, Used to indicate the status of a
4xx, 5xx, 6xx transaction.
Response Codes
SCCP Support in ScreenOS Devices Overview on page 279
ALG Overview on page 286
Types of SIP Response Classes Supported in ScreenOS Devices on page 284
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:
Modified Fields
The IP address in the Via, From, To,
Call-ID, Contact, Route, and
Record-Route header fields are
modified.
In NAT mode, the IP address in the
Request-URI is changed to a private
IP address if the message is coming
from the external network into the
internal network. The IP addresses
in the Via, From, To, Call-ID,
Contact, Route, and Record-Route
header fields are modified.
For example, if user A in a private
network refers user B in a public
network to user C, who is also in the
private network, the SIP ALG
allocates a new IP address and port
number for user C so that user C can
be contacted by user B. If user C is
registered with a registrar, however,
its port mapping is stored in the ALG
NAT table and is reused to perform
the translation.
The Via, From, To, Call-ID, Contact,
Route, and Record-Route header
fields are modified.
Copyright © 2010, Juniper Networks, Inc.