Polycom, Inc.
27
Call Routing
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 be originated from somewhere. From the device’s perspective, calls originated from the
trunk side are considered Inbound Calls, while calls originated from an endpoint Outbound Calls. The call
routing rule syntaxes for inbound calls and outbound calls are slightly different, and are explained in the
following section.
Inbound Call Route Configuration
Every trunk has a corresponding
InboundCallRoute
in the device configuration. It 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. These rules tell the device how to handle an inbound call, such as sending it to the Phone port (and
ringing the attached phone(s)), 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.
The general format is:
InboundCallRoute
:= rule
OR
{rule},{rule},….
Curly braces can be omitted if there is only one rule in the route. The OR operator is not part of the parameter
syntax; it is 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.
Rule Formats
Rule
Format
Notes
peering-list :
peering,peering,…
Comma-separated list of 0 or more peering
objects
terminal-list :
terminal,terminal,….
Comma-separated list of 0 or more
terminal objects
peering :
caller-list > callee-list
caller-list :
caller|caller|caller|…
Vertical bar-separated list of 0 or more
caller objects
