Instruction manual

CTI Trunk Monitoring and Control Page 1211 of 3156
Features and Services
• The trunk must be an Associated trunk (AST = YES in Overlay 14).
• The call must be a 2-party call, and the call state must be established.
Warning Tone
With the Warning Tone functionality, the Connection Request (CON)
message is enhanced so that a short tone is provided to the originating party
of a call. The Warning Tone functionality is not limited to trunk calls. This
functionality also applies when the originating party is internal to the
Meridian 1 system. The warning tone is provided if either the originating TN
(in packed format) or the trunk route and member number is known. All of
the following conditions must be met to receive this tone:
• Either the Calling Party TN or the trunk route and member number in the
Calling Party DN field must be valid. If the value of the Calling Party TN
field is zero, the trunk route and member number is obtained from the
Calling Party DN field.
• The specified call must belong to the Customer group, as indicated by the
Customer number in the CON message.
• The trunk must be an Associated trunk (AST = YES in Overlay 14).
• The call must be a 2-party call, and the call state must be established.
Route Member Number Information Element (IE)
The Route and Member Number Information Element (IE) contains the trunk
route and member number on which a call arrives. The Route and Member
Number IE is added to the following two AML messages:
• Present Call Indication (PCI) message: for incoming trunk calls that
terminate to ACD sets
• USM (Ringing) message: for incoming trunk calls that terminate to non-
ACD sets
The Trunk Call Disconnect and Warning Tone functionalities require either
the packed TN or the CTI application to identify the trunk by route and
member number. The new Route and Member Number IE ensures that the
route and member number of the trunk involved in a trunk call is passed to
the CTI application.