Copyright 2010-2015 Obihai Technology, Inc.
155
-
The
cid
object inside an
arg
object is optional. If omitted, it implies no caller-ID spoofing when making the call
on the specified trunk. The succeeding ‘>’ can be omitted is
cid
is omitted
-
The
target
object inside an
arg
object is optional. If omitted, it implies the
target
$2, which means to call the
original called number after applying any necessary digit map transformation implied by the rule. The
preceding ‘>’ cannot be omitted if
target
is omitted but cid is not
-
arg
object is optional. If omitted, it implies the
arg
with the
target
$2 and no
cid
. If
arg
is omitted, the
succeeding parentheses ( ) can be omitted also.
An inbound call matches a rule if its caller-number/callee-number matches one of the
peering
objects of the rule.
Peering
objects are tested in the order left and right, and the first matched
peering
object will win. Rules are also
checked in the order left to right, and the first matched rule will win. Therefore it is important that you place the more
specific rules first in the
InboundCallRoute
if multiple rules can potentially match the same inbound call.
InboundCallRoute
Examples:
1)
ph
OR
{ph}
OR
{:ph}
OR
{@|?>@:ph}
(all equivalent)
It says: Ring the phone (only) for all incoming calls. This is the default
InboundCallRoute
for all trunks.
2)
{14081223330|15103313456:ph,aa},{(1800xx.|1888xx.)|?:},{ph}
It says: Ring the phone and AA for calls coming from 1 408 122 3330 or 1 510 331 3456, block all 800, 888, and
anonymous calls, and ring just the phone for all other calls
3)
{(x.4081113333|x.4152224444):aa},{ph}
It says: Ring the AA for calls coming from any number that ends with 408 111 3333 or 415 222 4444, and ring the phone
for all other calls. Be sure to include the enclosing parentheses in this example since “x.” is a digit map specific syntax.
4)
{200123456:aa},{sp1(14083335678)}
It says: Ring the AA for calls coming from 200123456. For all any other call, bridge it by calling 1 408 333 5678 using SP1
Service
Outbound Call Route Configuration
Every endpoint has an
OutboundCallRoute
parameter in the OBi device configuration. It tells the device where to
send the call when the endpoint attempts to make a call. Endpoints may 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 is not supported when routing outbound calls.
The general format is:
OutboundCallRoute
:=
rule
OR
{
rule
},{
rule
},….
Note that the curly braces may 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.
