Send to a trunk
Sends the call out through a carrier. The destination is passed to the carrier exactly as written, which makes it the field to fill in with the most care.
At a glance
| Outputs | none, this module ends the journey |
| Fields | Trunk and Destination |
| Destination | free text, accepts a {{variable}} |
How it works
The module hands the call off to the carrier you chose from the Trunk list, asking it to reach the Destination.
If you leave the destination blank, the call goes to the trunk with no number: this is what you want for a trunk that already points to a fixed extension at the other end. In every other case, fill it in.
The destination accepts a variable, which lets you dial a number obtained earlier in the plan: an entry from the caller through the DTMF entry module, or data read from your management software with API request.
What to fill in
| Field | What's expected | If it's wrong |
|---|---|---|
| Trunk | a trunk from your installation, to choose from the list | the call is hung up immediately |
| Destination | the number in the format your carrier expects | the carrier refuses the call, or routes it elsewhere |
Step by step
- Place the Send to a trunk module and connect the previous node to its input.
- Open it and choose the Trunk from the list. If it's empty, no trunk is set up in your installation: contact us, this can't be fixed from this screen.
- Write the Destination in the format expected by this carrier.
- Click Apply changes.
- Call the number that enters this plan, and check in the call list that the outgoing call actually goes out, and with what end cause if it fails.
If it doesn't work
The call is hung up immediately, with no tone. The chosen trunk no longer exists or wasn't resolved. Reopen the module and reselect it from the list.
The carrier refuses the call. The destination's format doesn't match what it expects. Test the same number from an extension to compare, and check the disconnect cause in the call list.
The variable isn't substituted, the call goes to a number that contains curly braces. The variable's name doesn't exactly match the one from the module that sets it, or that module wasn't traversed on this path. Add a Debugging module just before it to display the actual value, then check the debug log.
The call goes through, but the called party sees an unexpected number. This isn't caused by this module. Check the Caller ID module if there is one, then the advanced presented-number rules in Settings.
How the call flow is built, explained in pictures
See the Dial plans page