User Agent
Click on the red underlined text to get to the source
... manage 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 ...
... group defines timer
configuration objects applicable to SIP user agent and stateful
SIP proxy ...
... registrations, such as the maximum
registration expiry that may be requested by user agents, the
maximum number of users the registrar can support, the number
of currently registered users, per contact registration
information ...
... group specifies SIP server
configuration objects applicable to SIP user agents including
the Internet address of the SIP ...
... "sip_registrar1", "sip_registrar2".
o for a SIP User Agent entity, the applName value SHOULD be equal to
a character string starting ...
... SIP entities are proxies, user agents, redirect servers,
registrars, or combinations of the above.
...
... registrars, or combinations of the above.
User Agent (UA): A logical entity that can act as both a user
agent client ...
... User Agent (UA): A logical entity that can act as both a user
agent client and user agent server.
...
... UA): A logical entity that can act as both a user
agent client and user agent server.
User Agent Client ...
... transaction. If it receives a request later, it assumes the
role of a user agent server for the processing of that
transaction.
...
... transaction. If it generates a request
later, it assumes the role of a user agent client for the
processing of that transaction.
...
... Redirect Server: A redirect server is a user agent server that
generates 3xx responses to requests it receives, directing the
client ...
... This MIB is defined for managing objects that are common to
SIP User Agents (UAs), Proxy, Redirect, and Registrar servers.
...
... header fields.
Example: If a user agent client supports, and requires the
server to support, reliability of provisional responses
...
... "This table contains timer configuration objects applicable to
SIP user agent and SIP stateful Proxy Server entities."
...
... SIP User Agent MIB Module ...
... 3261prop (June 2002).
A User Agent is an application that contains both a User Agent
Client (UAC) and a User Agent Server ...
...
A User Agent is an application that contains both a User Agent
Client (UAC) and a User Agent Server (UAS ...
... User Agent is an application that contains both a User Agent
Client (UAC) and a User Agent Server (UAS). A UAC is an
...
... --
-- This MIB contains objects related to SIP User Agents.
--
sipUACfgServer OBJECT IDENTIFIER ...
... "This table contains SIP server configuration objects applicable
to each SIP user agent in this system."
::= { sipUACfgServer 1 }
...
...
Each row represents those objects for a particular SIP user
agent present in this system. applIndex is used to uniquely
identify these instances of SIP user agents and correlate
...
... row represents those objects for a particular SIP user
agent present in this system. applIndex is used to uniquely
identify these instances of SIP user agents and correlate
them through the common framework of the NETWORK ...
... "This object reflects the address of a SIP server this user
agent will use to proxy/redirect calls. The type of this
address ...
... DESCRIPTION
"This object reflects the function of the SIP server this user
agent should communicate with: registrar, proxy (outbound
proxy), etc."
...
... DESCRIPTION
"A collection of objects providing information about the
configuration of SIP User Agents."
::= { sipUAMIBGroups 1 }
...
... zero or more addresses to that client. Unlike a User Agent
Server, it does not accept calls.
A Registrar is a server that accepts REGISTER ...
... DESCRIPTION
"This object reflects the maximum expiry that may be requested
by a User Agent for a particular Contact. User Agents can
specify expiry using either an Expiry header ...
... "This object reflects the maximum expiry that may be requested
by a User Agent for a particular Contact. User Agents can
specify expiry using either an Expiry header in a REGISTER ...
... is greater than the value of this object, then the contact
information is given the duration specified by this object, and
that duration is indicated to the User Agent in the response."
::= { sipServerRegCfgEntry 1 }
...
... compute the Expires header in the REGISTER response. If a user
agent requests a time interval shorter than specified by this
object, the Registrar SHOULD honor that request. If a Contact
entry does not have an 'expires' parameter, the value of the
...