This target represents the Routing Service. The Routing Service routes calls to Oracle Voicemail and Fax services. When the Telephony Server receives a call from the PBX, the Routing Service answers the call. There are two ways in which the Routing Service gets handed calls: direct and forwarded. A direct call is one made directly to the voice mail system. A forwarded call is a call that is diverted to the voice mail system because the call was not answered or there is a busy signal. The Routing Service retrieves call detail information from the PBX including the callers phone number, the destination phone number, and how the call arrived at the voice mail system (direct or forwarded). If call detail information is unavailable, then the Routing Service allows the caller to choose voice mail recording, retrieval, or transfer to an attendant. For forwarded calls, the Routing Service checks the PBX-Application Clusters call routing map. If the calls destination number is listed in the call routing map, the call is handed off to the IVR (Interactive Voice Response) Service. All other forwarded calls are handed off to the Recording Service.
This category includes a set of metrics that provides information on the type of requests being handled by this routing instance.
Host name of system where recording instance is running.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
Name of the metric.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
This metric is for internal use only.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
The recording requests is the number of requests to record voicemail messages that are being handled by this instance in the Routing Service.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 95-1 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
|
All Versions |
Every 5 Minutes |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
OVF Recording Requests overload |
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
No action is required. If there is evidence that the service cannot keep up with the incoming call demand, return to the Routing Service home page, click the Add One Instance button to increase the number of service instances that can handle the calls.
The retrieval requests is the number of requests to retrieve voicemail messages that are being handled by this instance in the Routing Service.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 95-2 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
|
All Versions |
Every 5 Minutes |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
OVF Retrieval Requests overload |
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
No action is requied. If there is evidence that the service cannot keep up with the incoming call demand, return to the Routing Service home page, click the Add One Instance button to increase the number of service instances that can handle the calls.
This category includes a set of related metrics that provides you with information about the CPU and memory being used by the Routing Service instance. It provides a snapshot of how the Routing Service instance is performing. If a particular metric is empty, it is likely that the service instance is down and unavailable. Check the Up/Down status metric of the Routing Service instance.
This metric represents the percentage of the host CPU recorded for this instance of the Routing Service. By default, a critical and warning threshold value is set for this metric. Alerts are generated when threshold values are reached. You can edit the value for a threshold as required.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 95-3 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
|
All Versions |
Every 5 Minutes |
After Every Sample |
> |
70 |
75 |
2 |
CPU utilization of Routing Instance, %target% (%Name%), is %value%%% |
For this metric you can set different warning and critical threshold values for each "Name" object.
If warning or critical threshold values are currently set for any "Name" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
You can use this metric to determine if the Routing Service instance is using the most CPU on your system, thereby leading to high end-user response times. If the service instance is consuming a large amount of CPU, consider changing the configuration settings to reduce the CPU consumption. To investigate the cause of the CPU consumption, check for alerts that may have been generated by the following: the Routing Service instance, the Voicemail and Fax Application that this Routing Service instance is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server), or the host computer.
This metric is for internal use only.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
This metric shows you the percentage of host memory being used by the Routing Service instance. By default, a critical and warning threshold value is set for this metric column. Alerts are generated when threshold values are reached. You can edit the value for a threshold as required.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 95-4 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
|
All Versions |
Every 5 Minutes |
After Every Sample |
> |
80 |
90 |
2 |
Memory utilization of Routing Instance, %target% (%Name%), is %value%%% |
For this metric you can set different warning and critical threshold values for each "Name" object.
If warning or critical threshold values are currently set for any "Name" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
You can use this metric to determine if this Routing Service instance is using the most memory on your system and leading to high end-user response times. If the service instance is consuming a large amount of memory, consider changing the configuration settings to reduce memory consumption. To investigate the cause of the memory consumption, check for alerts that may have been generated by the following: the Routing Service instance, the Voicemail and Fax Application that this Routing Service instance is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server), or the host computer.
This metric represents the memory usage (in megabytes) for the Routing Service instance.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
Compare this metric with Memory Usage (%), which measures the percentage of host memory being used by the Routing Service instance.
This metric is for internal use only.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
This metric is for internal use only.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
This metric provides information about the Up/Down status of the Routing Service instance and alerts you when the Routing Service instance is down. If the status is down, it could mean that the service instance is in the process of starting up, or it is not responding to process management heartbeat checks. By default, a critical threshold value is set for this metric. Alerts are generated when threshold values are reached. You can edit the value for a threshold as required.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 95-5 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
|
All Versions |
Every 5 Minutes |
After Every Sample |
= |
Not Defined |
0 |
1 |
Routing Instance, %target% (%Name%), is down |
For this metric you can set different warning and critical threshold values for each "Name" object.
If warning or critical threshold values are currently set for any "Name" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
You can restart the Routing Service by selecting the Routing Service target and clicking on the Restart button on the Oracle Voicemail and Fax home page. To investigate why the instance is down, check for alerts that may have been generated by the following: the Routing Service instance, the Voicemail and Fax Application that this Routing Service instance is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server), the central agent on the host computer, or the host computer.
This category includes a set of metrics that provides information on the type of requests being handled by all the instances in the Routing Service.
The total recording requests is the number of requests to record voicemail messages that are being handled by all the instances in the Routing Service.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 95-6 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
|
All Versions |
Every 5 Minutes |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
OVF Recording requests overload |
No action is required. If there is evidence that the service cannot keep up with the incoming call demand, return to the Routing Service home page, click the Add One Instance button to increase the number of service instances that can handle the calls.
The total retrieval requests is the number of requests to retrieve voicemail messages that are being handled by all instances in the Routing Service.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 95-7 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
|
All Versions |
Every 5 Minutes |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
OVF Retrieval requests overload |
No action is required. If there is evidence that the service cannot keep up with the incoming call demand, return to the Routing Service home page, click the Add One Instance button to increase the number of service instances that can handle the calls.
This category includes a set of related metrics that provides you with information about the CPU and memory being used by the Routing Service. It provides a snapshot of how the Routing Service instances are performing. If a particular metric is empty, it is likely that an Routing Service instance is down and unavailable. Check the Up/Down status metric for all the Routing Service instances.
This metric represents the percentage of the host CPU recorded for all the instances of the service. By default, a critical and warning threshold value is set for this metric. Alerts are generated when threshold values are reached. You can edit the value for a threshold as required.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 95-8 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
|
All Versions |
Every 5 Minutes |
After Every Sample |
> |
70 |
75 |
2 |
CPU utilization of Routing Service, %target%, is %value%%% |
You can use this metric to determine if the Routing Service is using the most CPU on your system, thereby leading to high end-user response times. If the Routing Service is consuming a large amount of CPU, consider changing the configuration settings to reduce the CPU consumption. To investigate the cause of the CPU consumption, check for alerts that may have been generated by the following: the specific instances of the Routing Service, the Voicemail and Fax Application that this Routing Service is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server), or the host computer.
This metric shows you the percentage of host memory being used by the service. By default, a critical and warning threshold value is set for this metric column. Alerts are generated when threshold values are reached. You can edit the value for a threshold as required.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 95-9 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
|
All Versions |
Every 5 Minutes |
After Every Sample |
> |
80 |
90 |
2 |
Memory utilization of Routing Service, %target%, is %value%%% |
You can use this metric to determine if the Routing Service is using the most memory on your system and leading to high end-user response times. If the Routing Service is consuming a large amount of memory, consider changing the configuration settings to reduce memory consumption. To investigate the cause of the memory consumption, check for alerts that may have been generated by the following: the Routing Service instances, the Voicemail and Fax Application that this Routing Service is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server), or the host computer.
This metric represents the memory usage (in megabytes) for the service.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
Compare this metric with Memory Usage (%), which measures the percentage of host memory being used by the Routing Service.
This metric is for internal use only.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
This metric provides information about the Up/Down status of the Routing Service. The Routing Service shows a status of Down when all configured instances for this service are down.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
You can restart the Routing Service by selecting the Routing Service target and clicking on the Restart button on the Oracle Voicemail and Fax home page. To investigate why the service is down, check for alerts that may have been generated by the following: the Routing Service, specific instances of the Routing Service, the Voicemail and Fax Application that this Routing Service is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server), the central agent on the host computer, or the host computer.
This category includes metrics that provide information about the Up/Down status of the Routing Service.
This metric provides information about the Up/Down status of the Routing Service and alerts you when the Routing Service is down. The Routing Service shows a status of Down when all configured instances for this service are down. By default, a critical threshold value is set for this metric. Alerts are generated when threshold values are reached. You can edit the value for a threshold as required.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 95-10 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
|
All Versions |
Every 5 Minutes |
After Every Sample |
= |
Not Defined |
0 |
1 |
Routing Service, %target%, is down |
You can restart the Routing Service by selecting the Routing Service target and clicking on the Restart button on the Oracle Voicemail and Fax home page. To investigate why the service is down, check for alerts that may have been generated by the following: the Routing Service, specific instances of the Routing Service, the Voicemail and Fax Application that this Routing Service is a member of (check status of dependent components - Oracle Internet Directory, Telephony Server), the central agent on the host computer, or the host computer.