Call Routing
Polycom, Inc.
31
Each supported service is also referred to as a trunk. Each trunk is represented with a two-letter abbreviation
and a numeral-based instance identifier:
●
SP1 = the SP1 voice service (with ITSP A, B, C, or D)
●
SP2 = the SP2 voice service (with ITSP A, B, C, or D)
●
SP3 = the SP3 voice service (with ITSP A, B, C, or D)
●
SP4 = the SP4 voice service (with ITSP A, B, C, or D)
●
PP1 = the OBiTALK service
The instance identifier can be omitted when it equals 1. Thus, LI is equivalent to LI1. These short-hand
notations are used heavily in configuring the device, as found in call routes, call forward numbers, and speed
dials parameters. Unless stated otherwise, the abbreviated trunk names are case-insensitive.
In addition to all the call bridging functionalities, each device has a built-in physical Phone port for hooking
up analog telephones or FAX machines. The device includes a set of features to support its Phone port to
make it work as a full-featured Analog Telephone Adapter (ATA) device. Users can place and receive calls
on the Phone port or USB port (using a USB headset) over any of the trunks.
The device also comes with an Auto Attendant (AA) for helping callers to direct their calls landed on the
device. When an inbound call is received on the device, it can be routed to the AA, which then offers a menu
of options to the caller to direct it further. It could be directed to ring an available Phone port, or bridged with
another call on a trunk (which the AA “dials” or sets up on behalf of the caller).
The Phone port, headset port, and the AA entities in the device where calls can terminate, as opposed to
the trunks, which rely on the corresponding service provider or local system administrator to terminate the
call. In this document, the Phone port and the AA are endpoints. Like the trunks, each endpoint is
represented by a 2-letter abbreviation and a numeral-based instance identifier:
●
PH1 = the Phone port
●
HS = Headset
●
AA1 = the Auto Attendant
Unless stated otherwise, abbreviated endpoint names are case-insensitive. A trunk or an endpoint is also
referred to as a terminal in this document.
The following matrix shows the possible call connections between the endpoints and the trunks.
SP3 Service
yes
yes
yes
yes
yes
SP4 Service
yes
yes
yes
yes
yes
OBiTALKService
yes
yes
yes
yes
yes
Supported 2-way Call Bridges
SP1 Service
SP2 Service
SP3 Service
SP4 Service
OBiTALK
Service
