CAF: Working With Call Legs: Difference between revisions
(Created page with '= Creating Call Legs = == When Should Call Legs be Created == === When Doing a Standalone Outgoing Call === === When Bridging an Incoming Call === === When Creating a Media-only…') |
No edit summary |
||
| Line 1: | Line 1: | ||
= Creating Call Legs = | = Introduction = | ||
The main mechanism through which the customer application controls the Toolpack system, is via the management of call legs. The application creates a call leg (or more than one for conferencing and bridging) at the beginning of call, then control it through a simple, protocol-agnostic API. When a call is terminated, the call leg must | |||
== When Should Call Legs be Created == | == Creating Call Legs == | ||
=== When Doing a Standalone Outgoing Call === | === When Should Call Legs be Created === | ||
=== When Bridging an Incoming Call === | ==== When Doing a Standalone Outgoing Call ==== | ||
=== When Creating a Media-only Leg === | ==== When Bridging an Incoming Call ==== | ||
==== When Creating a Media-only Leg ==== | |||
Revision as of 17:23, 14 October 2009
Introduction
The main mechanism through which the customer application controls the Toolpack system, is via the management of call legs. The application creates a call leg (or more than one for conferencing and bridging) at the beginning of call, then control it through a simple, protocol-agnostic API. When a call is terminated, the call leg must