Copyright 2010-2017 Obihai Technology, Inc.
59
•
Ignore/reject the call if the trunk is not enabled, else
•
Forward the call if native per-line
Call Forward Unconditional
feature is enabled on the service, else
•
Apply
Busy Treatment
to the call if native per-line
Do Not Disturb
feature is enabled on the service, else
•
Apply
Busy Treatment
to the call if the number of existing calls on the trunk already reaches the limit set for
the service, else
•
Apply the rules in the
InboundCallRoute
parameter of the service to determine where to send the call to. A
common destination for an incoming call is
ph
(that is to ring the phone)
Notes:
•
Busy Treatment refers to whether to reject/ignore the call or apply native per-line Call Forward On Busy if the
feature is enabled on the service
•
When it comes to reject/ignore a call, the decision whether to reject or ignore is based on the service. For
OBiBluetooth, the call is ignored so it will continue to ring on the connected mobile phone. For other services,
the call is rejected
•
InboundCallRoute
can be configured to let the phone do complex call handling, for example:
o
Ring the phone, the AA, and one or more cell phone number(s) via SP
n
simultaneously; whoever
answers first takes the call
o
If the caller number ends in 4281234 or 3357, ring the AA and a cell phone number simultaneously;
otherwise ring the phone only
More information on this parameter can be found in the
Call Routing
section.
Basic Outgoing Call Handling
The mechanics of selecting a trunk for outgoing call is the subject of a later section. When the trunk receives a number
to call, it will make the call if the trunk is enabled and up and it has not yet reached full capacity. Otherwise, the trunk
will fail the outgoing call attempt.
It should be noted that although there is a
DigitMap
parameter available per service, it is however not used by the
trunk to validate the number to call (the validation is done at a higher level before the call attempt is routed to the
trunk for execution). The per-line
DigitMap
is used as a reference in other
DigitMap
parameters (usually in
Phone
Settings
::
DigitMap
) and in trunk selection from within a trunk group. The latter is more relevant to the trunk itself:
When a trunk group has been determined as the destination of an outgoing call, the phone selects the trunk from the
group by taking into account whether the number to call is valid against the rules in the
DigitMap
of the trunk.
Specification of Target Phone Numbers
There are places within the OBi configuration that specify a target phone number. For example, a speed dial number or
a call forward number. Here we define two formats to specify a target phone number: A
Short Numbe
r
where only the
number itself is specified, such as
3231234
or
14089993312
, and a
Full Number
where the number and the service
to use the number are both specified, such as
pp(ob222222222)
or
sp3(14089993312)
. The case-insensitive
service name to use for each service in full number specifications is:
•
sp
n
for SP
n
Service for
n
= 1
–
6
•
pp
for OBiTALK Service
•
bt
for OBiBluetooth Service
When only a short number is specified, the phone determines the service to use, where necessary, by going through
normal digit map and call routing processing, as explained later in this document. When a full number is specified, the
phone uses the number and service as specified without any modification.
