Outbound Call Route Configuration
Outbound Call Routes are rules to tell the device 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 between the syntaxes 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.
The general format is:
OutboundCallRoute := 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 := callee-list : terminal
where
● callee-list := callee|callee|callee| …(vertical bar separated list of 0 or more callee
object)
● callee := number OR embedded-digit-map OR @ (@ = any number)
● terminal := PHx OR AAx OR LIx(arg) OR SPx(arg) OR PPx(arg) (arg object is
optional)
● arg := cid > target
● x := 1 OR 2 OR 3…(where applicable; can be omitted if it’s equal to 1)
● cid = spoofed-caller-number
● target = number-to-call OR $2
● embedded-digit-map = (Mlabel) OR digit-map
Notes
● A terminal can be a trunk or another endpoint.
● Abbreviated terminal names are case-insensitive.
● Number and number-to-call are literal strings, such as 14089991234.
● Digit-map is any digit map, such as (1xxx|xx.); make sure to include the enclosing
parentheses.
● Spoofed-caller-number is a literal string, such as 14081112233, to be used as the caller
number for making a new call on the specified trunk.
● (Mlabel) is a named digit map where label is the abbreviated name of any terminal that has a
digit map defined: SP1, SP2, PP, PH, or AA.
Outbound Call Route Configuration
61
To Next Page
Loading...
Need help?
General
