Call Routing11
Call Routing is the process by which the device sets up a call bridge or an endpoint call based on
such information as the trunk on which the call originates, the caller's number, the called number, etc.
Call Routing Rules are parameters used to instruct the device how to route calls. A call can transform
into a call bridge or an endpoint call after being routed by the device according to the given routing
rules.
Every call has to originate from somewhere. From the device's perspective, calls originated from the
trunk side are considered Inbound Calls, while calls originated from an endpoint are Outbound Calls.
The call routing rule syntaxes for inbound calls and outbound calls are slightly different, and are
explained in the following section.
Call Routing Rule configuration relies heavily on digit maps. If you aren’t familiar with how digit maps
work, see the Digit Map Configuration on page 63 section in this document first.
Inbound and Outbound Call Routing
Understand the call routing rules used by the device for handling inbound and outbound calls.
Inbound Call Route Configuration
Inbound Call Routes are rules to tell the device how to handle an inbound call. The options are
sending it to the Phone port, and ringing the attached phone, sending it to the Auto Attendant for
further routing interactively with the caller, or making another call on a specific trunk to bridge with this
call.
An inbound call route is a comma-separated list of rules where each rule is also surrounded by a pair
of curly braces {}. No extra white spaces are allowed.
The general format is:
InboundCallRoute := rule OR {rule},{rule},….
You can omit the curly braces if there’s only one rule in the route. The OR operator is NOT part of the
parameter syntax; it’s used here to separate alternative values only.
A rule has the following format:
rule := peering-list : terminal-list
The following table shows the rule formats.
58
Chapter 11Call Routing
To Next Page
Loading...
Need help?
General
