48
Call Routing
Call routing is the process your system uses to set up a call bridge or an endpoint call based on information
like the trunk on which the call originates, the caller’s number, and the called number.
From your system’s perspective, calls originated from the trunk side are considered inbound calls, while
calls originated from an endpoint are outbound calls.
Call routing rule configuration relies heavily on digit maps. If you aren’t familiar with how digit maps work,
see the
VVX D230 DECT IP Phone Technical Reference Guide
Inbound Call Route Configuration
Every trunk has a corresponding
InboundCallRoute
parameter in your system configuration. It’s a
comma-separated list of rules where each rule is also surrounded by a pair of curly braces
{}
. No extra
white space is allowed. These rules tell your D230 how to handle an inbound call, such as sending it to a
handset and ringing any attached phones.
By default, the
X_InboundCallRoute
parameter specifies the handset on which an incoming call rings.
Edit the Inbound Call Route Configuration
You can edit the inbound call route configuration to specify a different service (trunk) for each handset.
To edit the incoming call route configuration:
1
Go to
Voice Services > SPn Service
.
2
In the
Default
column for the
X_InboundCallRoute
parameter, clear the check box.
3
In the
Value
column for the
X_InboundCallRoute
column, enter the device that uses this call
route. Recommended values are
dt1
(handset 1) for SP1,
dt2
(handset 2) for SP2, and so forth.
If you enter the same
dt
n
value for more than one handset, then all handsets with that number ring
when an incoming call occurs.
Outbound Call Route Configuration
Every endpoint has an
OutboundCallRoute
parameter in its system configuration. It tells your system
where to send the call when the endpoint attempts to make a call. Endpoints can call each other or an
outside number using one of the trunks. The
OutboundCallRoute
syntaxes are almost identical to those
of the
InboundCallRoute
. The differences are mainly in the implied value when an optional field is
omitted, no caller objects, and one and only one terminal object per terminal-list in an
OutboundCallRoute
. Forking isn’t supported when routing outbound calls.