Snom 4S manual Available OID, Oid

Page 62

6.

[ S N O M 4 S N A T F I L T E R ]

space etc.), the setup is a little bit more difficult that the setup of a stan- dard sensor.

A readable parameter is described by its object identifier (OID). The object identifies are described in the next paragraph. Please enter the OID in your tool and select appropriate names for them. Also make sure that the IP address of the host running the SNMP tool matches the setup that you gave the SBC in the “Trusted IP Addresses” setting.

The SBC does not support “snmpwalk” or other tools that auto- matically describe the abilities of the SBC. You must enter these settings manually.

6.3. Available OID

The following table describes the available OID. An absolute value describes the current state on the SBC, the value might go up and down. Relative values only go up and accumulate the values.

OID

Description

Absolute

Unit

1.3.6.1.2.1.7526.1.1

Open Calls

Yes

Calls

1.3.6.1.2.1.7526.1.2

Registrations

Yes

Registrations

1.3.6.1.2.1.7526.1.3

Minutes

No

Minutes

1.3.6.1.2.1.7526.1.4

Received Media

No

Bytes

1.3.6.1.2.1.7526.1.5

SIP Packets

No

Packets

1.3.6.1.2.1.7526.1.6

SIP Traffic

No

Bytes

1.3.6.1.2.1.7526.1.7

Successful Calls

No

Calls

1.3.6.1.2.1.7526.1.8

Unsuccessful Calls

No

Calls

The minutes are measured only for the codecs ulaw, alaw, G.726 (32 kbit/s), GSM 6.10, G.723.1 and G.729. The minute measurement is done by looking at the media type in the RTP packet. If the packet uses a non-standard mapping, the results may be inaccurate.

The SBC measures only the received traffic. Usually, this is equal to the sent traffic, because the SBC does not block traffic. However, when there is a problem with the media establishment, the number of transmit- ted bytes might differ from the number of received bytes. The information does not include IP header like the UDP header.

62 • SNMP

Image 62
Contents Snom 4S NAT Filter Admin Manual Snom 4S NAT Filter Version Table of Contents Snmp Overview Features ApplicationsSnom technology AG Overview Architecture NAT Filter and SIPNAT Symmetrical RTP Signalling SIPHow does NAT work? Media RTP Classification of User AgentsProbing Media Paths Role of the NAT FilterOptimizing the Media Path for Symmetrical NATSBC Behaviour RegisteringRTP Relay Snom technology AG Scaling and Redundancy NATDetecting the right NAT Filter STUN/ICE-Aware User Agents Requirements on User AgentsNon NAT-Aware User Agents Defining the Maximum Session Time Architecture Installation WindowsInstallation Snom technology AG Installation Snom technology AG Linux Rpm -ihv snomnatf-2.10.*.rpm Installation Logging Port BindingStandard Port Random Port System Settings LoggingPreparing Recovery General Outound ProxyMedia Relay Media PortsPort Budgets Controlling RoutingMultiple 2xx Handling Maximum Packet Size ChallengingTrusted Addresses Removing Headers Silence SuppressionConnection Oriented Media Clir Addresses Codec ControlWeb Server Integration Timeout Settings Register TimeoutsCall Timeouts Security Settings Snom technology AG Outbound Proxy List System Information Server LogTrace Call History Current Ports Currently Handled UA Memory StatisticsConfiguration Web Server Integration Authentication Interface to the Web ServerSnom technology AG Web Server Integration Registration Call Initiation Snom technology AG Call Termination Snom technology AG Web Server Integration Setup of the SBC Setup of the ToolsAvailable OID OIDSnom technology AG Snmp Checklist for Installation Checklist for Installation Reader‘s Feedback Snom technology AG All rights reserved