Event Notification Capabilities
Communications Server CallVisor ASAI Protocol Reference, 555-230-221.
Considerations
When monitoring is established for a VDN or ACD domain, ECS generates event reports as calls arrive at the domain. ECS does not generate event reports for calls that are already present (in progress) at ACD or VDN domains when the Request Notification is received. The ECS will generate the Call Offered to Domain Event Report only if the call is not already sending event reports over an Event Notification association related to the entered domain. (This is true for all cases, including the case of a call entering or reentering a VDN as a result of the Vector Return Destination feature.) Also refer to user scenario 11 in Appendix A, “Call Scenarios and Applications” for more information on VDN.
Starting with R5: if a call is already active at a trunk group when Notification is requested on the trunk groups, and the ECS then receives charging information for that call, then the ECS will generate a Charging Event Request. The Charging Event Report is the only report provided by an Event Notification trunk group association. The event notification for trunk groups with the ##### domain will provide a Charging Event Report for all trunk groups. Only one Event Notification association per system is allowed for the domain type trunk access code. Due to the volatility in traffic volume, it is recommended that customers reserve a separate ASAI link for any application that invokes the Advice of Charge (AOC) feature.
NOTE:
Event Notification capability has evolved over time. Prior to G3V3, only one Event Notification per ACD or VDN domain was allowed at any one time. G3V3 increased the number of associations that can be simultaneously active, to three per ACD or VDN domain. In R6r, the number of Event Notification Associations that can be active at a time, has been increased to six per ACD or VDN domain. In R6si, the number of Event Notification Associations per ACD or VDN domain, is still three.
