|
Connects two independent callers and links their voice paths together. |
Supported Script Types
|
| Phone |
Properties
- DestContactID
- The Contact IDA unique numerical identifier assigned to each contact. of the call with which to connect to.
- SourcePersistent
- This property is a True or False drop down list. The selection for this property determines whether the calling party will stay up after the callers disconnect. When True is selected, it prevents the destination legAn active piece of a call that connects between routers, gateways, or telephony devices. of the call (or called party) from dropping the source leg of the call when it hangs up. Use with caution. The default is False.
- DestPersistent
- This property is a True or False drop down list. The selection for this property determines whether the called party will stay up after the callers disconnect. When True is selected, it prevents the source leg of the call (or calling party) from dropping the destination leg of the call when it hangs up. Use with caution. The default is False.
Branches
- Default
- The Default branch condition will be used unless another specific branch condition is met.
- OnError
- If the Dest Contact IDA unique numerical identifier assigned to each contact. does not exist, or cannot be linked to, this branch condition is triggered.
Tips and Tricks
- In conjunction with SPAWN and PLACECALL, the LINK action facilitates the development of sophisticated two party scripts and advanced call solutions. The Source Persistent and Dest Persistent properties allow one leg of a call to remain connected even when the other leg disconnects.
- A script that uses a LINK action is similar to a script that uses the TRANSFER action. The differences between the TRANSFER and LINK actions are:
- a TRANSFER action allows a caller to hear a phone ring until the call is answered
- a LINK action allows you to play music, or to find 1 numbers, etc. while the calls are being linked
- an outbound call will have its own independent script when there is a LINK action
- A common example for the LINK action is when an inbound script executes a SPAWN action to initiate another script. Meanwhile, the script that spawned will play a voice prompt to the caller. The new script executes in parallel to the script that initiated it and can then execute a PLACECALL action. Once the destination party answers, the script may then connect the two parties using the LINK action.
- Some common applications for the LINK action include:
- Find-Me/Follow-Me functions
- Transferring calls that “hide” busy signals, or “no answer” or even ringbacks
- 1 Number Applications
- LINK is not restricted to outbound calls. Two inbound calls may also be linked. All that's required is the calling or called party's unique Contact IDA unique numerical identifier assigned to each contact.. Calls that are linked together using LINK may also be unlinked. See UNLINK for more information.
