Instruction manual

Page 1540 of 3156 Flexible Trunk to Trunk Connections
553-3001-306 Standard 10.00 January 2002
denies trunk to trunk connections for Transfer and Conference
allows trunk to trunk connections for Supervised Conference only, and
denies trunk to trunk connections for Transfer and unsupervised
Conference
The Conference feature allows additional parties to join an established call.
One internal Directory Number must always be involved in the Conference
call for a Supervised Conference. A Meridian 1 user can conference two or
more trunks and then drop out of the conference, leaving the other trunks
connected. This is an unsupervised Conference.
When Flexible Trunk to Trunk Connections is used in conjunction with the
Trunk Barring feature, one of the following options may be selected:
Additional set level restrictions can be added to the existing Customer
level Trunk Barring.
The restrictions placed by Trunk Barring, based upon the sets Flexible
Trunk to Trunk Connections Class of Service, can be lifted.
All set based trunk to trunk connections can be controlled for Conference
and Transfer, depending upon the sets Flexible Trunk to Trunk
Connections Class of Service, whether or not the route is barred by
TBAR.
The functionality of the Flexible Trunk to Trunk Connections feature is
activated by Flexible Trunk to Trunk Connections Options (FTOP prompt) in
the Customer Data Block and controlled by the Stations Class of Service.
The options that are available at a Customer level are dependent upon
whether or not Trunk Barring (package 132) is configured.
Functionality of Flexible Trunk to Trunk Connections without
Trunk Barring configured
When Flexible Trunk to Trunk Connections is used without Trunk Barring
configured, the following Classes of Service are provided at a set level:
When CLS = FTTU, Flexible Trunk to Trunk Connections Unrestricted,
trunk to trunk connections are allowed for both Conference and Transfer.
Flexible Trunk to Trunk Connections Unrestricted (FTTU) is the default
value.