cSipCfgUserLocationServerAddr
CISCO-SIP-UA-MIB ·
.1.3.6.1.4.1.9.9.152.1.1.1.3
Object
This object specifies address of the User Location
Server (ULS) being used to resolve the location of end
points. This could be a Domain Name Server (DNS) or a
SIP proxy/redirect server.
The format of the address follows the IETF service location
protocol. The syntax is as follows:
mapping-type:type-specific-syntax
the mapping-type specifies a scheme for mapping the matching
dial string to a target server. The type-specific-syntax is
exactly that, something that the particular mapping scheme can
understand. For example,
Session target Meaning
ipv4:171.68.13.55:1006 The session target is the IP
version 4 address of 171.68.13.55
and port 1006.
dns:pots.cisco.com The session target is the IP host
with dns name pots.cisco.com.
The valid Mapping type definitions for the peer follow:
ipv4 - Syntax: ipv4:w.x.y.z:port or ipv4:w.x.y.z
dns - Syntax: dns:host.domain.
Context
- MIB
- CISCO-SIP-UA-MIB
- OID
.1.3.6.1.4.1.9.9.152.1.1.1.3- Type
- scalar
- Access
- readwrite
- Status
- current
- Parent
- cSipCfgBase
- Groups
- 4
Net-SNMP examples
How SNMP and these commands workScalars have one instance, identified by the .0 suffix.
Read the scalar instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'CISCO-SIP-UA-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-SIP-UA-MIB::cSipCfgUserLocationServerAddr.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-SIP-UA-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-SIP-UA-MIB::cSipCfgUserLocationServerAddr'
Syntax
- Source
- SNMP-FRAMEWORK-MIBSnmpAdminString
- Base type
OctetString
Values & Constraints
Type Constraints
range: 0..255
Conformance
Member of
Compliance refinements
ciscoSipCompliance
readonly
Write access is not required.
ciscoSipComplianceRev1
readonly
Write access is not required.
ciscoSipComplianceRev2
readonly
Write access is not required.
ciscoSipComplianceRev3
readonly
Write access is not required.
ciscoSipComplianceRev4
readonly
Write access is not required.
ciscoSipComplianceRev5
readonly
Write access is not required.
ciscoSipComplianceRev6
readonly
Write access is not required.