Using Other Subscription Events

BroadWorks virtual subscribers (Routing Points and ACD Queues) have not been included in the BroadWorks failover design, however, behavior for those subscribers after AS failover is similar to the agent subscribers. The main difference is that BroadWorks has no ability to report unsolicited RoutePointSubscriptionEvent and ACDSubcriptionEvent events.

BroadWorks reports those events when the UpdateSubscriptionRequest request is sent for those subscribers. CSTA Connector client may request call synchronization for Routing Points and ACD Queues by issuing a CSTA Snapshot Device request. CSTA Connector processes it as an UpdateSubscriptionRequest request. The call information received in the associated RoutePointSubscriptionEvent event (or ACDSubcriptionEvent event) are reported back to the client-requestor in the CSTA Snapshot Device response. If any unsynchronized calls are discovered, then the other CSTA Connector clients are informed using CSTA Event Connection Cleared.

CSTA Connector clients may request call synchronization for Routing Points and ACD Queues by issuing an CSTA Snapshot Device request. T-Server for CSTA Connector uses this request to validate the calls on the Routing Point and ACD Queues where the call party remains queued longer than the average queuing time. T-Server for CSTA Connector calcullates the average time between the EventQueued and EventDiverted events for each monitored ACD Queue and Routing Point and requests call synchronization, if this time is exceeded.

Note: The periodic check call feature configured in T-Server may delete established calls on the agent end-points after AS Failover.