getting started Guide for ExecutiveAssistant

3Com ExecutiveAssistant Getting Started Guide 6
• Ensure that no other software is running on the server that can even temporarily
fully utilize the CPU, NIC, or hard-drive controller. It is highly recommended
that the Media Drivers and the ExecutiveAssistant are the only software
programs (besides the core Windows itself) running on the server.
• Windows must be logged in with a local or domain administrator account in order
to install the Media Drivers and the ExecutiveAssistant on the server. Client
computers must be logged in with a local or domain administrator account in
order to install the ExecutiveAssistant client software. It is not necessary or
advised to install the Media Drivers on client computers.
• Software requires access to a SMTP email in order to communicate with the
administrator and sending emails in conjunction with the AutoDialer such as the
automatic list dialing results.
• 3Com ExecutiveAssistant supports the NBX running in SIP; however, 3Com
phones are required and you must be talking TAPI between the 3Com phones and
the 3Com ExecutiveAssistant. SIP phones are not supported.
• The 3Com ExecutiveAssisant Call Recording feature requires two
(2) 3Com Media Driver Port licenses per call being recorded, or even be eligible
for on-demand recording, monitoring, whisper or barge-in – dynamically
allocated.
• Two (2) Media Driver Port licenses are required for each simultaneous call that is
eligible to be monitored/whispered/barged- into, plus one for each simultaneous
Supervisor who is using these features. If Automation or On-demand Recording is
being used, those would be the same two Media Drivers used for these features.
This includes calls that are sent to department path (such as an ACD or hunt
group) before it even reaches the final extension.