![Perimeter Technology VU-ACD /100 Скачать руководство пользователя страница 168](http://html.mh-extra.com/html/perimeter-technology/vu-acd-100/vu-acd-100_maintenance-manual_1529976168.webp)
5-16
Configuration Changes
VU-ACD™/100 Maintenance Guide – Host/DOS
To preserve time synchronization in an InterLink configuration the following rules should be observed:
1. If available, always reference to a DMS-100 on Node 0 or Node 1 of the primary host.
2. Timing synchronization is carried over InterLink Outputs – RS-232 or LAN – to secondary
VU-ACD/100 hosts.
3. In a 5ESS-only configuration, the internal clock of the primary host PC will
synchronize the internal clocks of all secondary hosts via Node 0 or 1.
4. Time references at Node 0 or 1 should be carefully observed across secondary
VU-ACD/100 hosts to assure the accuracy of all data displays and historical reporting. For
a MultiLink secondary host be sure to configure the InterLink Input from the primary host
as Node 1. Centrex ACD switch or Net-VU server data streams should be configured as
other nodes.
?
All of the example configurations in this section accurately indicate the Node
connections required to synchronize to a DMS-100 at Node 0 or 1 of the primary
host.
5.4.3
User Group Configuration
Each InterLink Output is associated with a User Group. The ACD Groups associated with the User
Group determine the extent of the data available for viewing on the primary and secondary hosts in the
configuration.
InterLink configurations retain the complete independence of each VU-ACD/100 host. User Group
configuration follows the guidelines explored in Section 3 of the VU-ACD/100 System Planning Guide.
This configurability gives Service Bureau operators a great deal of flexibility for meeting specific
customer requirements in InterLink VU-ACD/100 environments. User Groups can be set up with only
the ACD Groups/Teams of interest for assignment to a particular InterLink output via VU-ACD/100
User Group Administration.
Each InterLink Output can be associated with one User Group and one Primary Directory Number
(PDN). The PDN can service multiple ACD Groups/Teams. System descriptions (including ACD
Group/Team and Subgroup names, agent information, CKW/LOB codes), alarm values, Monitor Groups,
shifts, time values for archive data, archive schedule, agent trace configuration, adherence schedules and
configuration, Report Groups, Load Management macros, external display messages and assignments,
dialed destinations, MIS users, User Groups and devices are separate entities among the different
VU-ACD/100 hosts. The only common link is that Load Management and Recent Change/Verify
parameters (other than limits, macros, audio group names, and route names) changed on one host are
propagated to other hosts.
5.4.4
Database Replication
Descriptive and user configured parameters contained in the VU-ACD/100 host database are not passed
on through an InterLink output to another host. An InterLink input provides an initialized data stream
that mimics the contents of a Centrex ACD or Net-VU data stream. Sufficient ACD entity information is
provided to parse call event messages.
Each secondary host must manually recreate the descriptive information that defines the Centrex ACD or
Net-VU entities being tracked via the InterLink input. System descriptions, alarm values, Monitor
Groups, shifts, adherence schedules and configuration, Load Management macros, and external display
messages must be entered into the receiving host’s database. This usually requires obtaining descriptive
printouts from the sending host.