proxy
Click on the red underlined text to get to the source
... Session Initiation Protocol (SIP) entities, which include User
Agents, and Proxy, Redirect and Registrar servers. The managed
objects defined in this document are intended to provide basic SIP
...
... RFC3261] - User Agents (UA), and Proxy, Redirect, and
Registrar servers. It is intended to provide management of the basic
...
... SIP-SERVER-MIB contains objects
specific to Proxy, Redirect, and Registrar servers. SIP-UA-MIB ...
... version, the type of SIP entity (UA, proxy, redirect, registrar
servers), the operational and administrative status, the SIP
...
... * sipServerProxyCfg: This object group defines configuration
objects for SIP Proxy Servers including the proxy mode of
operation (stateless ...
... group defines configuration
objects for SIP Proxy Servers including the proxy mode of
operation (stateless, stateful, call stateful), the proxy ...
... proxy mode of
operation (stateless, stateful, call stateful), the proxy
authentication method(s), realm, etc.
...
... * sipServerProxyStats: This object group defines a table
containing the statistics objects applicable to SIP Proxy
Servers. It includes the number of occurrences of unsupported
options being specified in received Proxy-Require headers ...
... containing the statistics objects applicable to SIP Proxy
Servers. It includes the number of occurrences of unsupported
options being specified in received Proxy-Require headers.
...
... UA uses to register,
proxy, or redirect calls.
To conform with this specification, an SNMP agent ...
... entity, the applName value SHOULD be equal to a
character string starting with "sip_proxy" followed by a unique
application instance identifier, for example, "sip_proxy1",
...
... "sip_ua2".
o for any combination of Proxy, Registrar, or Redirect Server being
managed as a single aggregate entity ...
... expectations, the following order of names is RECOMMENDED:
* if Proxy exists, list first.
* if Proxy and Redirect exists, list Redirect second.
...
... * if Proxy exists, list first.
* if Proxy and Redirect exists, list Redirect second.
* if Registrar exists, always list last.
...
... * if Registrar exists, always list last.
For example "sip_proxy1", "sip_proxy_registrar1",
"sip_proxy_redirect5", "sip_proxy ...
... For example "sip_proxy1", "sip_proxy_registrar1",
"sip_proxy_redirect5", "sip_proxy_redirect_registrar2", or
"sip_registrar1".
...
... proxy_registrar1",
"sip_proxy_redirect5", "sip_proxy_redirect_registrar2", or
"sip_registrar1".
...
... Example 1:
The tables below illustrate how a system acting as both Proxy and
Registrar server might be configured to maintain separate SIP-
...
... +-----------+-------------------+----------------------+
| 1 | "sip_proxy10" | "ACME SIP Proxy" |
| 2 | "sip_registrar17" | "ACME SIP Registrar" |
...
... SIP-COMMON-MIB sipCommonCfgTable would have two rows: one for the
proxy (applIndex=1) and one for the registrar (applIndex=2). The
SIP-SERVER-MIB tables ...
... row
indexed by applIndex=1 and applIndex=2, respectively, if the server
provides either proxy or registrar.
The SIP ...
...
This example illustrates how to represent a system acting as both
Proxy and Registrar server, where the two entities share a single
instance of SIP-COMMON-MIB ...
... | applIndex | applName | applDescription |
+-----------+------------------------+------------------------------+
| 1 | "sip_proxy_registrar1" | "ACME SIP Proxy and |
...
... | 1 | "sip_proxy_registrar1" | "ACME SIP Proxy and |
| | | Registrar" |
+-----------+------------------------+------------------------------+
...
... MIB sipCommonCfgTable would have only one row to cover
both the proxy and the registrar.
The SIP ...
... client for the purpose of making requests on
behalf of other clients. A proxy server primarily plays the
role of routing ...
... entity 'closer' to the targeted
user. Proxies are also useful for enforcing policy. A proxy
interprets and, if necessary, rewrites specific parts of a
request message ...
... 3261prop. These tags are used in
Require (Section 20.32), Proxy-Require (Section 20.29),
Supported (Section 20.37), and Unsupported (Section 20.40)
header fields ...
... require(0), -- Require header
proxyRequire(1), -- Proxy-Require header
supported(2), -- Supported header ...
... SIP User Agents (UAs), Proxy, Redirect, and Registrar servers.
Objects specific to each of these entities MAY be managed using
entity ...
... SIP entity. These option tags are
used in the Require, Proxy-Require, Supported, and
Unsupported header fields.
...
... a Require header to a UAS, or in a Proxy-Require to a Proxy
Server), the server returns a 420 Bad Extension listing the
feature in an Unsupported header ...
... header to a UAS, or in a Proxy-Require to a Proxy
Server), the server returns a 420 Bad Extension listing the
feature in an Unsupported header.
...
... header), unsupported (Unsupported header), or
required (Require or Proxy-Require header) by the SIP entity.
...
... STATUS current
DESCRIPTION
"This object reflects the maximum time a SIP Proxy Server will
wait to receive a provisional response to an INVITE. The Timer ...
... This table does not apply to transaction stateless Proxy
Servers."
::= { sipCommonStatsTrans 1 }
...
... address of a SIP server this user
agent will use to proxy/redirect calls. The type of this
address is determined by the value of the
...
... "This object reflects the function of the SIP server this user
agent should communicate with: registrar, proxy (outbound
proxy), etc."
::= { sipUACfgServerEntry 4 }
...
... SIP server this user
agent should communicate with: registrar, proxy (outbound
proxy), etc."
::= { sipUACfgServerEntry 4 }
...
... and Registrar Servers.
A Proxy Server acts as both a client and a server. It accepts
requests from other clients ...
... "This table contains configuration objects applicable to SIP
Redirect and Proxy Servers."
::= { sipServerCfg 1 }
...
... group contains MIB objects
-- related to SIP Proxy Servers.
--
sipServerProxyCfg OBJECT IDENTIFIER ...
...
--
-- Proxy Server Configuration
--
sipServerProxyCfgTable OBJECT-TYPE
...
... STATUS current
DESCRIPTION
"This table contains configuration objects applicable to SIP
Proxy Servers."
::= { sipServerProxyCfg 1 }
...
...
"This object reflects the default mode of operation for the
Proxy Server entity.
...
... state machines when it
processes requests. A stateless proxy forwards every request it
receives downstream and every response it receives upstream ...
... upstream. If
the value of this object is stateless(1), the proxy defaults to
stateless operations.
...
... A transaction stateful proxy, or simply a 'stateful proxy', is
a logical entity that maintains the client and server ...
... state machines during the processing of a request.
A (transaction) stateful proxy is not the same as a call
stateful proxy. If the value of this object is
...
... transaction) stateful proxy is not the same as a call
stateful proxy. If the value of this object is
transactionStateful(2), the proxy is stateful on a transaction ...
... stateful proxy. If the value of this object is
transactionStateful(2), the proxy is stateful on a transaction
basis.
...
... for a dialog from the initiating INVITE to the terminating BYE
request. A call stateful proxy is always transaction stateful,
but the converse is not necessarily true. If the value of this
...
... transaction stateful,
but the converse is not necessarily true. If the value of this
object is callStateful(3), the proxy is call stateful."
REFERENCE
...
... STATUS current
DESCRIPTION
"This object reflects whether or not the Proxy performs a
recursive search on the Contacts provided in 3xx redirects.
...
...
DESCRIPTION
"This object reflects whether or not the proxy adds itself to
the Record-Route header ...
... path for subsequent requests related to the call leg.
If the value of this object is 'true', the proxy adds itself to
the end of the Record-Route header ...
... header, creating the header if
required. If the value is 'false', the proxy does not add
itself to the Record-Route header ...
... DESCRIPTION
"This object reflects the default realm value used in
Proxy-Authenticate headers. Note that this MAY need to be
...
...
--
-- Proxy Server Statistics
--
sipServerProxyStatsTable OBJECT-TYPE
...
... DESCRIPTION
"This table contains the statistics objects applicable to all
SIP Proxy Servers in this system."
::= { sipServerProxyStats 1 }
...
... DESCRIPTION
"This object contains the number of occurrences of unsupported
options being specified in received Proxy-Require headers.
Such occurrences result in a 420 Bad Extension status code ...
... Redirect Server, or is used as the RequestURI in a SIP request
line for requests forwarded by a proxy."
::= { sipServerRegContactEntry 3 }
...
... "The compliance statement for SIP entities acting as Proxy
Servers."
MODULE -- this module
MANDATORY-GROUPS ...
... "A collection of objects providing configuration common to SIP
Proxy and Redirect servers."
::= { sipServerMIBGroups 1 }
...
... STATUS current
DESCRIPTION
"A collection of objects providing configuration for SIP Proxy
servers."
::= { sipServerMIBGroups 2 }
...
... STATUS current
DESCRIPTION
"A collection of objects providing statistics for SIP Proxy
servers."
::= { sipServerMIBGroups 3 }
...