This page was last edited on November 6, 2018, at 03:57.
Comments or questions about this documentation? Contact us for support!
You can handle calls that are detected with an Answering Machine (AM) call result on a per-record basis.
OCS supports the ability to assign different types of AM-detection to each dialing request based on a custom-configured value of an arbitrary field in Calling List record.
To configure AM-detection on a per-record basis, OCS uses the Business Attributes configuration object. Use the following for guidelines when configuring it.
Note: | Any number of attribute values can be configured under this Business Attribute object. Each individual attribute value represents a field in the Calling List with a map of values for this field and the corresponding values for the desired AM-detection. You can specify only one map per calling list or OCS application. The name of the attribute value is arbitrary; however it should be meaningful so that it is easier to associate a calling list with this attribute value. |
The actual map for field values for AM-detection settings translation is configured in the Options tab of the attribute value as follows:
To specify which Calling List uses which attribute value, the am-detection-map option can be used.
OCS uses the following approach to determine which AM-detection value to apply to a dialing request.
If the attribute value is not found or disabled, then OCS uses the AM-detection method that is defined in the call_answer_type_recognition option.
Note: | When working with GVP, the ANSWER_TYPE_RECOGNITION attribute is added to the dialing attributes. This attribute holds the value for AM-detection for a given dialing request. |
Starting with release 8.1.517.04, OCS provides the ability to handle an outbound call (drop or connect) on a particular device when the call is placed in any auto-dialing mode and AM is detected. The am-drop-field configuration option controls the AM handling logic.