Home/Catalog/ZHONE-COM-VOIP-MIB

ZHONE-COM-VOIP-MIB

AI MIB Summary

The ZHONE-COM-VOIP-MIB enables SNMP-based configuration and monitoring of Voice over IP parameters on Zhone Systems hardware, specifically managing call session states, codec negotiations, and QoS metrics for VoIP traffic.

Voice over IP configuration for Zhone products
Main OID:
zhoneVoip.1.3.6.1.4.1.5504.4.3.4
81
Objects
Active
Status
9
Dependencies

Imported Objects

Objects

81 total
Object Name
zhoneVoipVoice over IP configuration for Zhone products
MODULE-IDENTITY
.1.3.6.1.4.1.5504.4.3.4
zhoneVoipSystemOnly SIP-PLAR is using this profile. The regular SIP and MGCP setting is moving to Voip-Server-Entry profile.deprecated
OBJECT IDENTIFIER
.1.3.6.1.4.1.5504.4.3.4.1
zhoneVoipSystemProtocolThe signalling protocol used for VOIP. Choicees are SIP (Session Initiation Protocol) and MGCP (Media Gateway Control Protocol. Currently, the device only supports SIP.rodeprecated
Enumeration
.1.3.6.1.4.1.5504.4.3.4.1.1
zhoneVoipSystemSendCallProceedingToneIndicates whether, on call originations destined to the PSTN, the device should play a call proceeding tone while waiting for ring-back tone from the switch.rwdeprecated
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.5504.4.3.4.1.2
zhoneVoipSystemRtcpEnabledIndicates whether the Real-Time Control Protocol is enabled for the device.rwdeprecated
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.5504.4.3.4.1.3
zhoneVoipSystemRtcpPacketIntervalRTCP packet interval, in milleseconds. Range is 2500 to 10000 ms. This object's value is only pertinent if RTCP has been enabled.rwdeprecated
Integer32
.1.3.6.1.4.1.5504.4.3.4.1.4
zhoneVoipSystemInterdigitTimeoutThis parameter indicates the duration, in seconds, that the device will wait after each digit is entered before assuming the user has finished entering digits.rwdeprecated
Integer32
.1.3.6.1.4.1.5504.4.3.4.1.5
zhoneVoipSystemIpTosThis parameter indicates the tos value that is set in the ip header for voice of ip traffic.rwdeprecated
Integer32
.1.3.6.1.4.1.5504.4.3.4.1.6
zhoneVoipSystemDomainNameThis parameter is ignored.rodeprecated
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.5504.4.3.4.1.7
zhoneVoipObjectsZhone VOIP objects.
Unknown
.1.3.6.1.4.1.5504.4.3.4.2
zhoneVoipSipDialPlan
OBJECT IDENTIFIER
.1.3.6.1.4.1.5504.4.3.4.3
nextVoipSipDialPlanIdReturns the next unused dial plan entry id.ro
Integer32
.1.3.6.1.4.1.5504.4.3.4.3.1
zhoneVoipSipDialPlanTableThis table defines a dialing plan for POTS to SIP originations. A dialing plan consists of a series of acceptable dial strings and the corresponding IP addresses to which SIP control messages (e.g., Invite) are sent to initiate the call. Each dial string is represented as digits, wildcards, and regular-expression-like patterns as the following rules show: 1. A leading '*' or '#' are allowed. 2. Digits 0-9 are allowed. 3. A wildcard 'x' represents any digit 0-9 4. A digit range can be specified using brackets [ ], as follows: [135] means a single digit with acceptable values 1,3, or 5. [1-4] means a single digit with acceptable values 1,2,3, or 4. Examples of valid dial strings: 911 - literal digit string 911 #87 - literal digit string #87 *6x - *6 followed by any single digit 35xxx - 35 followed by any 3 digits 77xxx - 77 followed by any 3 digits 3[35]xxx - 33 or 35 followed by any 3 digits 31[1-3]xxxx - 311, 312, 313, followed by any 4 digits Notes: (1) The length of the dial string is limited 1o 128 characters (2) Though the dialplan supports the '#' and '*' keys, the device may not support any features that use them (e.g., *69). (3) In the case where a collected digit set matches more than one dial string, the device will pick the dial string with the most leading literal digits that match. For example, given two dial strings: 35xxx 3[35]xxx and a collected digit set of 35123, the first dial plan string is selected because it contains two leading literal digits that match, as opposed to the second, which has only one leading literal digit. (4) Variable length dial strings, e.g. 353 followed by any number of digits, are not supported. (5) In the future, a dial string may be configurable such that it only applies to a subset of the supported ports (e.g., ports with international calling capabilities might be restricted). This is currently not supported; a dial string applies to all subscriberers. Support will be added for per-port control, most likely by adding port masks to the dial plan entry.
SEQUENCE OF ZhoneVoipSipDialPlanEntry
.1.3.6.1.4.1.5504.4.3.4.3.2
zhoneVoipSipDialPlanEntryAn entry in the SIP dial plan table.
ZhoneVoipSipDialPlanEntry
.1.3.6.1.4.1.5504.4.3.4.3.2.1
zhoneVoipSipDialPlanIdThe unique identifier of the dial plan entry.
INTEGER
.1.3.6.1.4.1.5504.4.3.4.3.2.1.1
zhoneVoipSipDialStringA dial string against which collected digits are matched.rw
SnmpAdminString
.1.3.6.1.4.1.5504.4.3.4.3.2.1.2
zhoneVoipSipDialIpAddrUpon detecting a match between the collected digits and the dial string for this table entry, this IP address is used for SIP negotiations to initiate the call.rw
IpAddress
.1.3.6.1.4.1.5504.4.3.4.3.2.1.3
zhoneVoipSipDialPlanRowStatusThe row status is used to create or delete an entry in this table.rw
ZhoneRowStatus (Zhone-TC)
.1.3.6.1.4.1.5504.4.3.4.3.2.1.4
zhoneVoipSipDialDestNameName of the destination for the dial stringrw
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.5504.4.3.4.3.2.1.5
zhoneVoipSipDialNumOfDigitsNumber of digits to wait for before initiating the callrw
INTEGER
.1.3.6.1.4.1.5504.4.3.4.3.2.1.6
zhoneVoipSipDialPrefixStripNumber of prefix digits to strip from dialled digitsrw
INTEGER
.1.3.6.1.4.1.5504.4.3.4.3.2.1.7
zhoneVoipSipDialPrefixAddString to be added to the beginning of the dialled digits before call initiationrw
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.5504.4.3.4.3.2.1.8
zhoneVoipSipDialPlanTypeDialPlanType indicates the type of the dial plan. UA has to differenciate between normal dialing and dialing when call features like call park is initiated. The different kinds of dial plan types are: Normal Call Park ESA (Emergency stand alone) isdnsig (ISDN-PRI) Intercomrw
Enumeration
.1.3.6.1.4.1.5504.4.3.4.3.2.1.9
zhoneVoipServerEntryIndexAn index to associated voip-server-entry for this sip-dialplan.rw
INTEGER
.1.3.6.1.4.1.5504.4.3.4.3.2.1.10
zhoneVoipOverrideInterdigitTimeoutThis parameter overrides the interdigit timeout in voip-system profile. It indicates the duration, in seconds, that the device will wait after each digit is entered before assuming the user has finished entering digits.rw
Integer32
.1.3.6.1.4.1.5504.4.3.4.3.2.1.11
zhoneVoipSipDialPlanClassThis parameter is used to configured the dial plan specific features.rw
Bits
.1.3.6.1.4.1.5504.4.3.4.3.2.1.12
zhoneVoipSipDialPlanDescriptionThis field gives details about the sip-dialplanrw
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.5504.4.3.4.3.2.1.13
zhoneVoipHuntGroup
OBJECT IDENTIFIER
.1.3.6.1.4.1.5504.4.3.4.4
nextZhoneVoipHuntGroupIdReturns the next unused hunt group entry id.ro
Integer32
.1.3.6.1.4.1.5504.4.3.4.4.2
zhoneVoipHuntGroupTableA hunt groups is defined to map a SIP uniform resource identifier (URI) or dirctory number (DN) to multiple DS0s, to allow a greater number of incoming calls to that URI/DN. A hunt group consists of the following information: - the target DN/URI - the default codec to be used for the call, and - the DS0 ports in the hunt-group. Notes: A URI defined in a subscriber-voice-sip profile cannot also be defined as part of a hunt group. This is enforced by the device. A DS0 must be provisioned in the subVoiceSipTable before that DS0 can be used in a hunt group. This is enforced by the device. A DS0 may be part of more than one hunt group.
SEQUENCE OF ZhoneVoipHuntGroupEntry
.1.3.6.1.4.1.5504.4.3.4.4.3
zhoneVoipHuntGroupEntryAn entry in the hunt group table.
ZhoneVoipHuntGroupEntry
.1.3.6.1.4.1.5504.4.3.4.4.3.1
zhoneVoipHuntGroupIdThe unique identifier of the hunt group entry.
INTEGER
.1.3.6.1.4.1.5504.4.3.4.4.3.1.1
zhoneVoipHuntGroupDestUriThe DN (directory number) or SIP URI (uniform resource identifier) being called. This is the called party from the incoming SIP Invite message.rw
SnmpAdminString
.1.3.6.1.4.1.5504.4.3.4.4.3.1.2
zhoneVoipHuntGroupDefaultCodecThe default codec to use for a call to a member of this hunt group.rw
ZhoneCodecType (ZHONE-GEN-SUBSCRIBER)
.1.3.6.1.4.1.5504.4.3.4.4.3.1.3
zhoneVoipHuntGroupPortMembersIndicates which ports are contained in the hunt group.rw
Bits
.1.3.6.1.4.1.5504.4.3.4.4.3.1.4
zhoneVoipHuntGroupRowStatusThe row status is used to create or delete an entry in this table.rw
ZhoneRowStatus (Zhone-TC)
.1.3.6.1.4.1.5504.4.3.4.4.3.1.5
zhoneVoipMaliciousCaller
OBJECT IDENTIFIER
.1.3.6.1.4.1.5504.4.3.4.5
nextVoipMaliciousCallerIdeturns the next unused malicious caller entry indexro
Integer32
.1.3.6.1.4.1.5504.4.3.4.5.1
zhoneVoipMaliciousCallerTableThis table defines a malicious caller whose call will be rejected if enabled. SIP terminal administrator needs to provision URI of this table exactly as it appears in the incoming session notification's(SIP INVITE) calling user's address-of-record(AOR) formatted as a SIP URI. The SIP URI can contain either a telephone number(RFC 2806) or an alphanumeric identification(RFC 2806) Entries in the table are case sensitive, shall not contain visual separations and have the exact length as it appears in the SIP INVITE message
SEQUENCE OF ZhoneVoipMaliciousCallerEntry
.1.3.6.1.4.1.5504.4.3.4.5.2
zhoneVoipMaliciousCallerEntryAn entry in the malicious caller table
ZhoneVoipMaliciousCallerEntry
.1.3.6.1.4.1.5504.4.3.4.5.2.1
zhoneVoipMaliciousCallerIdThe unique identifier of the malicious call reject entry.
INTEGER
.1.3.6.1.4.1.5504.4.3.4.5.2.1.1
zhoneVoipMaliciousCallerUriIncoming call from this URI will be rejected. The network operator is responsible for provisioning exactly as per appearance in the incoming session notification (SIP INVITE) the calling user's address-of-record (AOR) formatted as a SIP URIrw
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.5504.4.3.4.5.2.1.2
zhoneVoipMaliciousCallerEnableIndicates whether the incoming call reject is enabledrw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.5504.4.3.4.5.2.1.3
zhoneVoipMaliciousCallerRowStatusThe row status is used to create or delete an entry in this table.rw
ZhoneRowStatus (Zhone-TC)
.1.3.6.1.4.1.5504.4.3.4.5.2.1.4
zhoneVoipServerCfg
OBJECT IDENTIFIER
.1.3.6.1.4.1.5504.4.3.4.6
zhoneVoipServerTableTable of VOIP Server addresses applicable to each VOIP user agent within the system.
SEQUENCE OF ZhoneVoipServerEntry
.1.3.6.1.4.1.5504.4.3.4.6.1
zhoneVoipServerEntryAn entry within the table. Indexed by applIndex, which is the slot number, and a user specified unique number.
ZhoneVoipServerEntry
.1.3.6.1.4.1.5504.4.3.4.6.1.1
zhoneVoipServerAddressIndexA unique identifier of a server address when multiple addresses are configured by the MGCP entity. If one address isn't reachable, then another can be tried.
Unsigned32
.1.3.6.1.4.1.5504.4.3.4.6.1.1.1
zhoneVoipServerRowStatusRow Status is used to create, modify or delete an entry.rw
ZhoneRowStatus (Zhone-TC)
.1.3.6.1.4.1.5504.4.3.4.6.1.1.2
zhoneVoipServerAddrTypeThis object specifies the type of address contained in the associated instance of sipVoipServerAddr.rw
InetAddressType (INET-ADDRESS-MIB)
.1.3.6.1.4.1.5504.4.3.4.6.1.1.3
zhoneVoipServerAddrThis object specifies the address of a VOIP server this user agent will use to proxy/redirect calls.rw
InetAddress (INET-ADDRESS-MIB)
.1.3.6.1.4.1.5504.4.3.4.6.1.1.4
zhoneVoipServerUdpPortNumberSpecifies the UDP Port number for the MGCP Gateway. 2427 is the IANA Registered MGCP Gateway port.rw
Integer32
.1.3.6.1.4.1.5504.4.3.4.6.1.1.5
zhoneVoipServerIdIdentifies the voip server type.rw
Enumeration
.1.3.6.1.4.1.5504.4.3.4.6.1.1.6
zhoneVoipServerProtocolThe signalling protocol used for VOIP. Choicees are SIP (Session Initiation Protocol) and MGCP (Media Gateway Control Protocol).rw
Enumeration
.1.3.6.1.4.1.5504.4.3.4.6.1.1.7
zhoneVoipServerSendCallProceedingTonendicates whether, on call originations destined to the PSTN, the device should play a call proceeding tone while waiting for ring-back tone from the switch.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.5504.4.3.4.6.1.1.8
zhoneVoipServerRtcpEnabledIndicates whether the Real-Time Control Protocol is enabled for the device.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.5504.4.3.4.6.1.1.9
zhoneVoipServerRtcpPacketIntervalRTCP packet interval, in milleseconds. Range is 2500 to 10000 ms. This object's value is only pertinent if RTCP has been enabled.rw
Integer32
.1.3.6.1.4.1.5504.4.3.4.6.1.1.10
zhoneVoipServerInterDigitTimeoutThis parameter indicates the duration, in seconds, that the device will wait after each digit is entered before assuming the user has finished entering digits.rw
Integer32
.1.3.6.1.4.1.5504.4.3.4.6.1.1.11
zhoneVoipServerIpTosThis parameter indicates the tos value that is set in the ip header for voice of ip traffic.rw
Integer32
.1.3.6.1.4.1.5504.4.3.4.6.1.1.12
zhoneVoipServerDomainNameThis parameter indicates the Universal Resource Identifier (URI) of the system.rw
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.5504.4.3.4.6.1.1.13
zhoneVoipServerExpiresInviteFor user agent clients, this value is inserted into the Expires header. For proxy servers, if a received request contained an Expires header, then the value in the header takes precedence.rw
Unsigned32 UNITS "seconds"
.1.3.6.1.4.1.5504.4.3.4.6.1.1.14
zhoneVoipServerExpiresRegisterFor user agent clients, this value is inserted into the Expires header. For registrar servers, if a received request contained an Expires header, then the value in the header takes precedence.rw
Unsigned32 UNITS "seconds"
.1.3.6.1.4.1.5504.4.3.4.6.1.1.15
zhoneVoipServerHeaderMethodThis convention is a bit map. Each bit represents a SIP method where the Expires header should be included. If a bit has value 1, then the requests corresponding to that SIP method must include an Expires header line. If a bit has value 0, then the Expires header line will not be added. Combinations of bits can be set when the Expires header line is required in multiple SIP methods. bit 0 : INVITE method. bit 1 : REGISTER Method.rw
Bits
.1.3.6.1.4.1.5504.4.3.4.6.1.1.16
zhoneVoipServerSessionTimerSupport session timers on : Session timers are supported, and SIP messages will have a 'Supported: timer' header off: Session timers are NOT supported, and SIP messages will NOT have a 'Supported: timer' headerrw
Enumeration
.1.3.6.1.4.1.5504.4.3.4.6.1.1.17
zhoneVoipServerSessionExpirationThe time at which an element (proxy, UAC, UAS) will consider the SIP session timed out, if no successful session refresh transaction occurs beforehand.rw
Unsigned32
.1.3.6.1.4.1.5504.4.3.4.6.1.1.18
zhoneVoipServerSessionMinSEBecause of the processing load of mid-dialog requests, all elements (proxy, UAC, UAS) can have configured minimum value for the session interval that they are willing to accept.rw
Unsigned32
.1.3.6.1.4.1.5504.4.3.4.6.1.1.19
zhoneVoipServerSessionCallerReqTimerThis field specifies the caller's action yes: Caller (UAC) will request for timer when making outbound calls no : Caller (UAC) will NOT request for timer when making outbound callsrw
Enumeration
.1.3.6.1.4.1.5504.4.3.4.6.1.1.20
zhoneVoipServerSessionCalleeReqTimerWhen caller supports timer but did not request one this field specifies the callee's action yes: Callee (UAS) will request for timer no : Callee (UAS) will NOT request for timerrw
Enumeration
.1.3.6.1.4.1.5504.4.3.4.6.1.1.21
zhoneVoipServerSessionCallerSpecifyRefresherCaller specifies the refresher: UAC : Caller specifies itself (UAC) as the refresher UAS : Caller specifies the callee (UAS) as the refresher Omit: Caller does NOT explicitly specify the refresherrw
Enumeration
.1.3.6.1.4.1.5504.4.3.4.6.1.1.22
zhoneVoipServerSessionCalleeSpecifyRefresherWhen UAC did not specify refresher tag, callee specifies the refresher: UAC : Callee specifies the caller (UAC) as the refresher UAS : Callee specifies itself (UAS) as the refresherrw
Enumeration
.1.3.6.1.4.1.5504.4.3.4.6.1.1.23
zhoneVoipServerDtmfModeIndicates whether dtmf digits are to be passed as codec voice packets or special separate packets (rfc2833).rw
Enumeration
.1.3.6.1.4.1.5504.4.3.4.6.1.1.24
zhoneVoipServerBehaviorStringOneThis field is used to control any switch specific behavior of the VOIP Gateway.ro
OCTET STRING
.1.3.6.1.4.1.5504.4.3.4.6.1.1.25
zhoneVoipServerRtpTermIdSyntaxThis field describes the Ephemeral term ID syntax for the switch. The RTP syntax varies from switch to switch.But the string should contain atleast one %eid format, eg <string>%eid<string> . This field is supported only for the Megaco protocol for all other protocols this field will be initialized to NULL. If the protocol is megaco and the field is NULL, Ephemeral term id will be updated to default syntax of the server Id given. If the server Id is not provisioned with the default id then field will be updated to NULL.rw
OCTET STRING
.1.3.6.1.4.1.5504.4.3.4.6.1.1.26
zhoneVoipServerRtpDSCPThis parameter indicates DSCP value for voip's rtp traffic. NOTE:zhoneVoipServerIpTos field must be zero before entering a new value into this field. Valid code values: <0-63> Differentiated services codepoint value af11 Mark packets with AF11 dscp (001010) af12 Mark packets with AF12 dscp (001100) af13 Mark packets with AF13 dscp (001110) af21 Mark packets with AF21 dscp (010010) af22 Mark packets with AF22 dscp (010100) af23 Mark packets with AF23 dscp (010110) af31 Mark packets with AF31 dscp (011010) af32 Mark packets with AF32 dscp (011100) af33 Mark packets with AF33 dscp (011110) af41 Mark packets with AF41 dscp (100010) af42 Mark packets with AF42 dscp (100100) af43 Mark packets with AF43 dscp (100110) cs1 Mark packets with CS1(precedence 1) dscp (001000) cs2 Mark packets with CS2(precedence 2) dscp (010000) cs3 Mark packets with CS3(precedence 3) dscp (011000) cs4 Mark packets with CS4(precedence 4) dscp (100000) cs5 Mark packets with CS5(precedence 5) dscp (101000) cs6 Mark packets with CS6(precedence 6) dscp (110000) cs7 Mark packets with CS7(precedence 7) dscp (111000) default Mark packets with default dscp (000000) ef Mark packets with EF dscp (101110)rw
OCTET STRING
.1.3.6.1.4.1.5504.4.3.4.6.1.1.27
zhoneVoipServerSignalingDSCPThis parameter indicates DSCP value for voip's signaling traffic. Valid code values: <0-63> Differentiated services codepoint value af11 Mark packets with AF11 dscp (001010) af12 Mark packets with AF12 dscp (001100) af13 Mark packets with AF13 dscp (001110) af21 Mark packets with AF21 dscp (010010) af22 Mark packets with AF22 dscp (010100) af23 Mark packets with AF23 dscp (010110) af31 Mark packets with AF31 dscp (011010) af32 Mark packets with AF32 dscp (011100) af33 Mark packets with AF33 dscp (011110) af41 Mark packets with AF41 dscp (100010) af42 Mark packets with AF42 dscp (100100) af43 Mark packets with AF43 dscp (100110) cs1 Mark packets with CS1(precedence 1) dscp (001000) cs2 Mark packets with CS2(precedence 2) dscp (010000) cs3 Mark packets with CS3(precedence 3) dscp (011000) cs4 Mark packets with CS4(precedence 4) dscp (100000) cs5 Mark packets with CS5(precedence 5) dscp (101000) cs6 Mark packets with CS6(precedence 6) dscp (110000) cs7 Mark packets with CS7(precedence 7) dscp (111000) default Mark packets with default dscp (000000) ef Mark packets with EF dscp (101110)rw
OCTET STRING
.1.3.6.1.4.1.5504.4.3.4.6.1.1.28
zhoneVoipServerDtmfPayloadIdDescription.rw
Integer32
.1.3.6.1.4.1.5504.4.3.4.6.1.1.29
zhoneVoipServerRegisterReadyTimeoutFor Megaco Service change Messages this value will be used in service-change-delay.rw
Unsigned32 UNITS "seconds"
.1.3.6.1.4.1.5504.4.3.4.6.1.1.30
zhoneVoipServerMessageRetryCountThis field specifies the number of retries of SIP message to every DNS resolved server IP addresses. The default behaviour means that the SIP message will be retransmitted to the first DNS resolved IP address once and the remaining retransmissions will be to the second DNS resolved IP address. The default value of zero or DNS resolved to a single IP address means that the default behaviour will take effectrw
Integer32
.1.3.6.1.4.1.5504.4.3.4.6.1.1.31
zhoneVoipServerFeaturesSet of features can be enabled for voip server Bit Feature --- -------- 1 sip outbound 2 gruurw
Bits
.1.3.6.1.4.1.5504.4.3.4.6.1.1.32
zhoneVoipServerTransportProtocolThis field specifies type of transport protocol configured. Possible values are udp and tcp.rw
Enumeration
.1.3.6.1.4.1.5504.4.3.4.6.1.1.33
zhoneVoipSigLocalPortNumberThis field specifies signalling local port number, used when tcp is configured as tranport protocol.rw
Integer32
.1.3.6.1.4.1.5504.4.3.4.6.1.1.34
ZHONE-COM-VOIP-MIB - SNMP MIB Reference | MIBs Explorer