Call Forwarding [DRAFT]
Call Forwarding status update can be triggered by these interfaces:
- HTTP interface toward Feature Server
- T-Library interface toward T-Controller
Call Forwarding status is stored in the Cassandra database. The overall mechanism is similar to agent login monitoring and control procedures.
If requested through the T-Library interface, T-Controller sends the corresponding event, EventForwardSet or EventForwardCancel, to Feature Server which stores Call Forwarding status in the database.
If requested through the HTTP interface, Feature Server sends the corresponding request, TCallSetForward or TCallCancelForward, to T-Controller, which is in charge of the DN. Eventually, the confirmation event is sent to Feature Server and Call Forwarding status is stored in the database.
Comments or questions about this documentation? Contact us for support!
