Quiescing a trunk

This section describes the sequence of events involved in quiescing a trunk

Figure 1 shows the following events:

Figure 1. Quiescing a trunk
The graphic is a simplified representation of the following text.
  1. Somebody requested a trunk to be quiesced, for example, by using the Blueworx Voice Response System Monitor window (or via SNMP).
  2. The Blueworx Voice Response system manager sends an SL_TRUNK_QUIESCE_REQ primitive to the signaling process.
  3. The signaling process prevents any new calls from being established on the trunk.
  4. The signaling process waits until any active calls on the trunk are cleared.
  5. The signaling process disables the trunk.
  6. The signaling process then sends an SL_TRUNK_QUIESCE_CNF primitive to Blueworx Voice Response.
  7. The trunk is now disabled.
Parent topic: Example signaling flows