This target represents the PBX-Application Cluster. Oracle Voicemail and Fax supports multiple locations in one voice mail system. Because there may be different types of PBXes in the same system, Oracle provides a way to define integrations through the concept of a PBX-Application Cluster. A PBX-Application Cluster defines a relationship between a PBX and one or more Voicemail and Fax Applications, called an application cluster, that support the PBX. For example, there may be two sites, San Francisco and Denver, served by two PBXes. The PBX that serves San Francisco is integrated with the Voicemail and Fax Application using analog and SMDI. The PBX that serves Denver is integrated using Voice Over IP (VOIP) and Host Media Processing (HMP). Each site is supported by a separate PBX-Application Cluster. San Francisco is supported by SF_Nortel and Denver is supported by Denver_VOIP.You set parameters in the PBX-Application Cluster for the specific Voicemail and Fax Applications that are servicing a specific PBX. The parameters define how the application integrates with the PBX. These parameters include the PBX integration type, PBX dialing rules, telephony number translation rules, Message Waiting Indicator (MWI) phone number conversion rules, Interactive Voice Response (IVR) mapping, and phone numbers belonging to the PBX. This configuration applies to any Voicemail and Fax Application that is associated with the PBX-Application Cluster. Therefore, once you configure a PBX-Application Cluster, you can change which application is associated with the PBX without having to reconfigure the application.
This category contains metrics that provide information about the Up/Down status of the PBX-Application Cluster.
This metric provides information about the Up/Down status of the PBX-Application Cluster. It alerts you when the PBX-Application Cluster is down. The PBX-Application Cluster is considered down when any of its member targets, that is, when any one of its Voicemail and Fax Application targets, is down. The evaluation of this metric is triggered whenever there is a change in the Up/Down status of any of its member targets. The alert message for the status of the PBX-Application Cluster lists the members followed by their state. The possible states are: Up, Down, Unreachable, Blackout, Agent Down, Metric Error, and Status Pending.
The following table shows how this metric is evaluated and the alerts that get generated.
| Target Version | Evaluation and Collection Frequency | Alert Text | Alert Example |
|---|---|---|---|
| All Versions | Every time there is a change in the Response Status of its member targets | Members status --> %Non-zero count of members% Up; %Non-zero count of members% Down; %Non-zero count of members% Unreachable; %Non-zero count of members% Blackout; %Non-zero count of members% Agent Down; %Non-zero count of members% Metric Error; %Non-zero count of members% Status Pending; | Members status --> 1 Up; 3 Status Pending; |
The status of the PBX-Application Cluster is dependent on the status of its members. To investigate why the PBX-Application Cluster is down, check for alerts that may have been generated by its member targets, that is, the Voicemail and Fax Applications, or by their corresponding host and agent targets.