Make Call Node

It is used to combine all call legs and Call Runtime Objects to make a call. For example, in an outbound process, when the call is picked up by the customer, then use this node to connect the call to the agent. It will be successful only when the agent is connected. It is also used during an existing call such as to make the conference or make the transfer.

Figure: "Make Call" Node

Following is the screenshot of its configuration.

Figure: Configuration of "Make Call" Node

Availability in Nodeflow Types

This node is available in the following Nodeflow types.

• Callback

• Customer-based Inbound

• Conference

• Dialing

• Inbound

• Manual Dial

Configuration

Perform the following steps to configure this node.

1. Rename The Node: Rename the node, if required.

   Provide an easy-to-recall name, which matches the default node name.

2. Allow Inactive Call Legs (Optional): If you want to allow the inactive call legs, then give the value of this attribute in "Boolean" format - "TRUE". If set to "FALSE", then the inactive call legs will not be allowed.

   

   Figure: Attributes of Make Call Node

3. Data Provider: This node contains the following data providers. Select any one of them.

   

   Figure: Data Provider of Make Call Node

   • voice.campaign.make.call.node.data.provider: It is used to bridge the live call leg originated by originate node.

   • make.call.with.virtual.entity.node.data.provider: It is used to bridge the virtual call leg (such as CRT call leg) in case of conference.

4. Postscript (Optional): Synthesizer allows to run a JavaScript code after the processing of the node.

   

   Figure: Script to run after processing "Make Call" Node

   Here, paste the JavaScript. Click icon to open the following JavaScript Editor.

   

   Figure: JavaScript Editor

   The Administrator can write its own code here and click "Save". It returns to node configuration, which will show the saved code.

5. PreScript (Optional): Specify to run a custom JavaScript code before processing the node. Like PostScript, add the code in Prescript.

6. Click "Save" to save the Node Configuration.

Events

Switch to "Events" tab to see the events of this node.

Figure: Events of Make Call Node

These events are listed hereinbelow.

• Event.Verification.Failed:

• Event.Call.Legs.Hungup: It is generated when "Allow Inactive Call Leg" Attribute flag is set to "FALSE" and the system is not able to fetch any call leg or a valid media call leg from the object. CallLegActionResponse is unsuccessful, that is, Call Runtime Objects are failed to enter in the already initiated call because of any of the following reasons.

  • If CallLegActionResponse is timed out.

  • It is generated when one of the calls gets disconnected while the other is about to be connected.

• Event.Failure: It is generated because of any of the following reasons.

  • "Make Call Runtime Objects" information are null.

  • Exception occurred while adding the call legs to call.

  • Nodeflow already stopped when received response of any async (asynchronization) request like adding call legs to call.

  • Call Runtime object hung-up when call was created

  • While obtaining the call manager service.

  • Call Manager Voice Resource is not Registered or available while creating the call.

  • Call Context is not enabled.

  • Invalid data provider

  • Nodeflow returns error event

• Event.Success: It is generated in any of the following cases.

  • If CallLegActionResponse is successful, that is, Call Runtime Objects are successfully entered in the already existing initiated call.

  • It is generated when the node is successfully processed and both calls are bridged.

  • If request has been placed and all call legs enter call.

  • Some call legs might exit from the call before other call legs have entered the call.

• Event.System.Error: It is generated in any of the following cases.

  • Invalid node model for MakeCall Node

  • Invalid Component State of Call Runtime object while obtaining the call manager service

  • While obtaining crt object node service

  • Invalid Call Runtime object found in make call data

  • When the system generate certain errors such as hardware, environmental, and others.