Signaling models

The Blueworx Voice Response signaling model is based on the CallPath Services Architecture, as defined in the CallPath Services Programmer’s Reference manual (GC31-6824). The main difference is that Blueworx Voice Response does not implement the Routing state associated with automatic call distributors (ACDs).

Figure 1. CallPath signaling model
This signaling model begins and ends at Idle state. From Idle state the route passes in one direction through Pending state to Connected state, and in the other through Routing state to Alerting state and beyond. All states are shown returning directly to Idle state.
Figure 2. Blueworx Voice Response signaling model
This signaling model begins and ends at Idle state. From Idle state the route passes in one direction through Off-hook state to Connected state, and in the other through Ringing state to Connected state. All states are shown returning directly to Idle state.

There are differences in the responsibilities of the signaling process, depending on whether it is implementing a common channel signaling protocol or one of the exchange data link protocols: