Simple Network Monitoring Protocol (SNMP)
SNMP can be used to monitor the PBX through a lightweight protocol that is supported by many network management tools. The SNMP settings are located within the Admin > Network > Ports page.
|22.214.171.124.4.1.25060.1.2||Registrations and subscriptions||Yes||Registrations|
|126.96.36.199.4.1.25060.1.6||Media CPU load||Yes||Value 0..100|
|188.8.131.52.4.1.25060.1.9||Email alert flag||Yes||Value 0..1|
|184.108.40.206.4.1.25060.1.10||SIP received packets||No||Packets|
|220.127.116.11.4.1.25060.1.11||SIP sent packets||No||Packets|
|18.104.22.168.4.1.25060.1.15.x||Trunk status||Yes||SIP response code|
|22.214.171.124.4.1.25060.1.17||Disconnects (no media)||Yes||Calls|
|126.96.36.199.4.1.25060.1.18||Disconnects (media timeout)||Yes||Calls|
The Calls in OID .1 is the number of primary calls. When the license limits the number of calls, it checks this number. This OID is what an end-user would consider a call on the PBX.
The Call Legs in OID .13 shows the number of call objects that have been allocated inside the PBX. Note that usually there are at least two call objects for a regular call (see OID .1 above), and during call forking you might have even more. This object will give you a good overview on the internal resource usage of the PBX.
The Registrations and subscriptions and Registrations object shows how many extensions are actively registered with the PBX. This object gives you a good overview on how many active users the system has. The first OID shows how many total registration and subscriptions are active on the system. This number is important to determine how much load for keeping devices registered on the system, as both registrations and subscriptions are creating load. The Registrations OID counts only registrations, and omits the subscriptions. This shows how many devices are registered to the system.
The Messages object shows you how many voicemail messages the system currently has stored. Note that when you do Email-forwarding, the messages are not stored on the PBX.
The Call Attempts object is useful to measure the Busy Hour Call Attempts (BHCA) number. This number is useful when you want to see where the limits of your system are. The BHCA number is an important performance number of traditional PBX. Feel free to compare the BHCA value of your modern CPU to the value of an old-style hardware PBX.
The Successful Calls object is similar to the Call Attempts object, but is measure the number of successful calls. The number is increased when the call terminates. The number can be used to determine the busy hour call performance of the system. Please note that on this software PBX, not only the call establishment takes resources. The call traffic itself also causes significant traffic, especially when the CPU has to do codec translation.
The Media CPU Load object show (in percent) how much time the media CPU threads spend in processing. This information is very important, because as this number approaches 100 % the jitter gets worse and the CPU eventually will not be able to process all media streams.
The Successful Emails contains the number of Emails that the PBX has sent out successfully. That means it has received the acknowledgement of the SMTP server that the email has been accepted.
The Unsuccessful Emails contains the number of messages that failed. A failed message may be re-tried later; therefore the sum of the successful and the unsuccessful messages not have to be the number of attempted emails.
The Email Alert Flag is set to one, if the last email failed. This flag is useful to find out when there is a situation where the administrator needs to do some action.
The SIP Received Packets and SIP Send Packets number says how many SIP messages have been received and sent on the PBX. Messages shorter than 5 bytes are not counted.
The Allocated Memory shows how many bytes the PBX has allocated in managed objects on the heap. This OID can help you finding out how much memory the service needs to run properly.
The Trunk Calls OID returns the number of calls on a specific trunk. The unit is call legs; however because usually there is only one call leg on a trunk that number represents the number of primary calls that use the trunk. The trunk number can be retrieved from the web interface by going to the trunk list; the links for editing the trunk contain the trunk number. This OID was introduced in version 3.2.
The Trunk Status OID returns the last SIP registration status of the trunk. Like with the Trunk Calls, this OID must include the trunk index. Successfully registered trunks will show a registration status value between 200 and 299. Trunks that do not register will return no value. This OID was introduced in version 3.2.
The Uptime OID returns the number of seconds since the service was started. This OID was introduced in version 3.2.
The Registration Duration OID keeps track on how long an extension had an active registration. The number x is the index into the account table; the account must be an extension. If there were multiple registrations for the extension, then all those registrations are taken into account. The duration is accumulated, so that relative numbers should be processed with this OID. The SNMP request makes the PBX write the data to the file system. After a reboot of the system, the system will continue counting with that number. The registration duration OID is available since version 5.1.2.
If you use snmpget, you can get the status of the PBX with a command like like this:
# snmpget -v 1 -c public 192.168.1.103 .188.8.131.52.4.1.25060.1.3 SNMPv2-SMI::enterprises.25060.1.3 = INTEGER: 4