Monitoring SBC AudioCodes

As mentioned earlier, eG Enterprise provides a specialized model for monitoring SBC AudioCodes (see Figure 1).

Figure 1 : Layer model of SBC AudioCodes

Each layer of Figure 1 above is mapped to tests that report a variety of metrics revealing the resource usage, port statistics, call and media statistics, and much more!

Using these metrics, administrators can find quick and accurate answers to the following persistent performance queries:

  • Is the appliance utilizing a very high percentage of CPU? If so, then what is the percentage of utilization?

  • Is the license utilization of the appliance on par with the licensing capacity?

  • Is the appliance utilizing a very high percentage of memory? If so, then what is the percentage of utilization?

  • Is the storage utilization of the appliance too high?

  • Is any port handling abnormal data traffic?

  • Are there any ports that handle too much packet traffic in terms of multicast, unicast, broadcast packets, etc.?

  • Is there any port that transmits or receives too many errors?

  • Are there too many failed calls or inbound calls closed due to routing failures in any IP index?

  • What is the number of active, attempted, and forwarded inbound and outbound calls on each IP index?

  • Is the SIP transaction rate on each SRD index too low? What is the count of registered users and inbound and outbound registrations on each SRD index?

  • Is the establishment rate for SIP-REC sessions on each SRD index optimum?

  • Is the SIP transaction rate for the global entity too low? What is the count of registered users and inbound and outbound registrations on the appliance?

  • Does the appliance successfully handle SBC-initiated outbound dialogs and user-initiated dialogs?

  • Are there too many failed calls or inbound calls closed due to routing failures in the appliance?

  • What is the number of active, attempted, and forwarded inbound and outbound calls on the appliance?

  • Is the DSP resource utilization percentage too high?

  • Are there too many failed transcoding resource allocations on the appliance?

  • Does the appliance experience high media traffic?

  • Are the media jitter and packet loss too high on the appliance?

  • Is the establishment rate for SIP-REC sessions on the appliance optimal?