iPECS UCP
Feature Description and Operation Manual Issue 1.3
231
upon return of the WAN connection.
5. iPECS can be installed behind a NAPT however, Fixed Nat with port forwarding is
required for the host to be reachable by remote devices.
6. Up to 100 local UCP modules can operate in local mode as part of a T-NET.
7. You must install a license and enable T-NET for all iPECS UCP modules that are
part of the T-NET.
8. Local VSF( UVMU/UVM) should be used when “RTP Relay Device Utilization” is
set to “Separated (SRC to DEST).
Programming
T-NET DATA T-NET Basic Attributes
T-NET CM Attributes
T-NET LM Attributes
Related Features
Remote Devices
Hardware
Remote UCP to support Local Survivability
2.80.2 Distributed Control Network
Description
In the Distributed Control Network, each iPECS system maintains control over the devices
registered to it. The networked systems communicate employing QSig over ISDN Lines or
H.450 over IP Lines for basic networking capabilities and the proprietary iPECS protocol for
the advanced networking features. QSIG employs ISDN PRI channels only with support for
ESTI standards ETS 300-237/238/256/257/260/261/361/362/363/364.
As a member of the network, you will have access to resources of other systems in the
network such as outside Lines, Stations and Paging. A Network Numbering Plan determines
the system call routing; your dialed digits are compared with the Numbering Plan Table for
routing.
An array of features is supported over the network employing the same operational
procedures as the local operating procedure. Common features supported include:
Call Transfer
Conference
Camp-on
Call Back
Message Wait
Call Forward
To Next Page
Loading...
