Filter
Top Products
NDA-24282 (E) CHAPTER 5
Page 181
Revision 1.0
OFFICE DATA DESIGN
2.2 ACD IN A FUSION NETWORK DATA ASSIGNMENT
This section provides general information about ACD in an Fusion Network and also, network establishment
conditions, data programming. For the function differences, this information is classified into the following two
functions.
Function 1 - ACD agents in a node providing ACDP can answer the ACD incoming calls via access to
ACD trunks in the remote node. This is called “ACD Trunk for Fusion” in this manual.
Function 2 - ACD agents in multiple nodes can answer ACD incoming calls since multiple ACDPs can be
provided in a Fusion Network (PBX software Series 7400 feature). This is called “Multiple
ACDPs in an Fusion Network” in this manual.
Note:
Feature [A-133] AGENT ANYWHERE allows ACD calls to be terminated to agents in remote nodes since
Series 7300 software. See Section 3, “ACD Service Feature” in this chapter for details.
Conditions for Network Establishment
1. Telephone Number (maximum 5 digits) is used for the station number type (both PBX line and ACD line)
to activate ACD system through Fusion Network.
Note 1
2. Logical Route (1-254: route numbers more than 254 are not available) is used for the route type to activate
ACD system through
Fusion Network
. The tables below show which data programming is changed in ac-
cordance with these conditions in terms of data and commands.
Basic Office Data
Data Description Notice
Monitor number 1. AMNON is used in place of AMNO
2. Telephone number for Monitor number (pilot number) is assigned in ALGNN com-
mand before the monitor number data assignment.
3. ACNON is used in place of ACNO
Announcement data AADTN is used in place of AADT
Back up-UCD data ASHUN is used in place of ASHU. See “Uniform Call Distribution (UCD) [U-1]” in Fea-
ture Programming Manual.
Other data Logical route number (1-254) and telephone number (max. 5 digits) are used.
1