WEBPRO - PCPRO - Aspire System Data Communications Manual
WEBPRO - PCPRO - Aspire System Data Communications Manual
Introduction
2. Installing Telephone
This manual covers the installation of the serial and USB drivers, CTA and Adapters
CTU Adapter installation, as well as the setup and configuration for the
following applications:
5. Troubleshooting
System Data
Communications Manual
Nothing contained in this manual shall be deemed to be, and this manual does not constitute, a warranty of, or
representation with respect to, any of the equipment covered. This manual is subject to change without notice and
NEC Unified Solutions, Inc. has no obligation to provide any updates or corrections to this manual. Further, NEC
Unified Solutions, Inc. also reserves the right, without prior notice, to make changes in equipment design or
components as it deems appropriate. No representation is made that this manual is complete or accurate in all
respects and NEC Unified Solutions, Inc. shall not be liable for any errors or omissions. In no event shall NEC Unified
Solutions, Inc. be liable for any incidental or consequential damages in connection with the use of this manual. This
document contains proprietary information that is protected by copyright. All rights are reserved. No part of this
document may be photocopied or reproduced without prior written consent of NEC Unified Solutions, Inc.
Section 1:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Section 2:
Adapter Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Installing Telephone Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
APA and APR Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Installing the APA and APR Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
CTA Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Installing the CTA Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
CTA Driver Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
PC Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Telephony Service Provider (TSP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Completing the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
Uninstalling the CTA Driver/Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
CTU Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
Installing the CTU Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
CTU Driver Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
PC Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
Installing the CTU Driver Under Windows XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24
Telephony Service Provider (TSP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31
Uninstalling the CTU Driver/Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40
Section 3:
NTCPU Connection and Driver Installation. . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
NTCPU Connection and Driver Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Connecting to the Aspire S/Aspire System’s NTCPU . . . . . . . . . . . . . . . . . . . . . . . 3-1
Connection for Local Access:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Connection for Remote Access:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Connecting to the Serial Port - Locally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Connecting to the Serial Port - Remotely . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Modem Set Up for PCPro Only: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Modem Setup For SMDR and DIM History Only:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Connecting to the LAN Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Connecting to the USB Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Section 4:
Feature Setup / Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Feature Setup / Programming. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
PCPro/WebPro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45
Aspire Software and PCPro Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-47
Installing PCPro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-48
Creating a Dial Up Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-51
Direct Dial Up (USB cable from PC to Aspire cabinet - not available for Aspire S) . . . . . 4-51
Direct Dial Up (direct serial cable from PC to Aspire S/Aspire cabinet) . . . . . . . . . . . . . . 4-55
Direct Dial Up (modem connection via serial cable to Aspire S/Aspire cabinet) . . . . . . . 4-59
Completing the Dial Up Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64
PCPro/WebPro - Using PCPro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-71
Using PCPro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-71
Make the Connection with PCPro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-73
Using PCPro. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-75
PCPro/WebPro - Using WebPro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-77
Using WebPro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-77
PCPro/WebPro - Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-81
PCPro/WebPro Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-81
SMDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-101
SMDR - Installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-107
Installing SMDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-107
SMDR - Programming. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-110
Programming SMDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-110
Programming (Cont’d) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-117
Related Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-119
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-119
Section 5:
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Troubleshooting CTA/CTU/TAPI Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
General. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
CTA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
CTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
TAPI 1.x/CTI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
TAPI 2.x/CTI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Troubleshooting Your PCPro/WebPro Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Serial Connection - Direct . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Serial Connection - Remote . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Troubleshooting Ultra CallAnalyst Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
Section 1: 1
Introduction
Introduction
Introduction
The system provides the ability to connect data devices (such as modem, fax machines, PCs, etc.). Some
of these connections can also be used to send and retrieve system data (such as SMDR, PCPro, WebPro,
TAPI, etc.).
In addition to the NTCPU’s serial, USB, and ethernet connections, there are four types of data devices available:
APA, APR, CTA and CTU.
The Aspire system allows for direct connection to the system data using a serial, USB or LAN connection. In
addition, a network connection can also be made through a hub. This manual describes how to install the
required drivers and set up the data application which will be used.
In addition, the APA and APR adapters can be used to provide analog ports which allow for connection of
fax machines, modems or single line telephones. These adapters, however, can not be used to connect to the
system for system data exchanges.
Important!
• When installing or removing the adapters, the keyset should first be unplugged from
the system.
• Telephones with any adapters installed cannot be wall-mounted. The bracket will not
1 •
accommodate the adapter(s).
The APA, APR, CTA, and CTU adapters cannot be installed on an Aspire 2-button
phone or IPhone.
APA Adapter
The APA Adapter provides an analog interface for the keyset. The APA Adapter does not provide ringing, so
the connected device is used for outgoing calls only (for example, when using a modem). One keyset can
have either an APA or an APR Adapter. Both adapters cannot be installed on the same keyset as only one
voice path is provided by the keyset for the adapters. The maximum distance between the APA Adapter and
the analog terminal is 49’. The system provides up to 24 ports (Aspire S) or 192 ports (Aspire M/L/XL) for
connecting APA adapters.
The APA Adapter does not support reverse-polarity, message waiting lamping, or Caller ID.
No AC-R AC/DC Adapter is required for this unit.
APR Adapter
The APR Adapter provides an analog interface for the keyset. The APR Adapter provides ringing which
allows the connected device to be used for incoming and outgoing calls. This adapter also provides a sepa-
rate extension number for the analog device, which allows both devices to be used at the same time (this can
be removed in system programming if you wish). One keyset can have either an APA or an APR Adapter.
Both adapters cannot be installed on the same keyset as only one voice path is provided by the keyset for the
adapters. When installing the APR Adapter, an AC-R AC/DC adapter (P/N 780135) is required for
power. As this adapter requires the AC power adapter, it can not be installed on a phone with an CTU or
Speakerphone adapter, which also require power. The placement of the AC power adapter plug will not allow
the unit placed on the left of the phone to receive power. The maximum distance between the APR Adapter
and the analog terminal is 49’.
The APR Adapter does not support reverse-polarity, message waiting lamping, or Caller ID.
With the APA adapter installed, when the analog device attached to the adapter is in use, the keyset cannot be
used as there is only one physical port number assigned to the phone. If both the analog device and keyset
are picked up at the same time, the analog device takes priority. If the keyset is on a call and the single line
telephone is picked up, the single line telephone will take the call from the keyset.
When installing the APR adapter, there must be an extension port available for the adapter or it will function
like an APA adapter (only one physical port assigned to the phone so only one phone can be used at a time).
The system provides up to 24 B1 channel or 16 B2 channel ports (Aspire S) or 192 ports (Aspire M/L/XL)
for connecting APA adapters.
When used for SMDR or system reports, the CTA driver does not need to be installed. When used for TAPI,
the CTA driver (available on NEC’s Technical Support web site: ws1.necii.com) is required. The system pro-
vides up to 24 ports (Aspire S) or 128 ports (Aspire M/L/XL) for connecting CTA or CTU adapters.
1
No AC-R AC/DC Adapter is required for this unit.
CTU Adapter
The CTU Adapter provides a USB connector. This can be used for either SMDR, TAPI (1.4), or system
reporting. The CTU driver needs to be installed for any use. The CTU driver is available on NEC’s Technical
Support web site: ws1.necii.com. The system provides up to 24 ports (Aspire S) or 128 ports (Aspire M/L/
XL) for connecting CTA or CTU adapters.
An AC-R AC/DC adapter (P/N 780135) is required for power for each CTU Adapter installed. As this
adapter requires the AC power adapter, it can not be installed on a phone with an APR or Speakerphone
adapter, which also require power. The placement of the AC power adapter plug will not allow the unit
placed on the left of the phone to receive power.
Aspire S Hardware
Feature
CPU Built-In ENTU-S CTA CTU
1 PCPro
Serial Port
Yes
Ethernet Port
Yes
Adapter
No
Adapter
No
Drivers
Drivers are required for the following connections:
●
●
●
NTCPU USB (Aspire M/L/XL only)
CTU Adapter
CTA Adapter (when used for TAPI)
1
Applications
The following applications are available for interfacing with the Aspire S or M/L/XL system:
Section 2:
Adapter Installation 2
required position.
● The SW3 switch is used to 1 2 3 4 5 6 7 8
set the terminating imped-
ance. Setting to position
“1” is for a pure resistance
of 600 ohms; position “2”
is used for complex
impedance (factory setting
is set to “1”). - 73
100
3
14
0-
10
93
08
2
6. Hook the two plastic prongs into the bottom of the phone.
7. Push the connector into place. The top latch on the top of the adapter should lock into place when it
is properly positioned.
8. In order for the APA/APR adapter to recognized correctly, the extension number to be used for the
adapter should be undefined in Program 10-03-01 before plugging in the keyset.
9. Plug the line cord back into the keyset.
10. Wrap the line cord once through the ferrite bead (included) and
snap it shut.
11. Plug the end of the line cord for the analog device with the ferrite
bead closest to it into the jack on the adapter. The opposite end
should then be connected to the analog device.
To avoid any hardware problems, when removing the
adapter, first unplug the line cord, then the power cord, then any other adapter cables.
12. To determine the APR’s analog extension number . . .
10-03-04 : Optional Installed Unit 1
Displays the type of terminal installed. This can be used to verify that the system recognizes the
adapter.
When you wish to have the APR use the same extension number as the keyset to which it is
attached (like an APA), remove the terminal type in this option. With this setup, when the analog
device is in use, it busies out the keyset as there is no separate port number assigned for the adapter.
To reverse this, and allow the APR to have its own extension number, simply reassign the terminal
type (12) in this option.
ON
PC Connection Printer/SMDR Connection
ON
2
0893100-150
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
3
14
0-
10
93
08
5. Hook the two plastic prongs into the bottom of the phone.
6. Push the connector into place. The latch on the top of the adapter should lock into place when it is
properly positioned.
7. Connect an RS-232C straight-thru cable from the adapter to the printer or PC.
8. Change system programming (15-02-19) to match the CTA module dip switch settings. Enter 0 for
CTI (PC connection) or 1 for non-procedural (SMDR).
9. Change system programming (15-02-20) to the correct baud rate.
10. Change remaining system programming as required. Refer to the specific feature in the Program-
ming Features section in this manual.
11. In order for the CTA adapter to recognized correctly, before plugging in the keyset, make sure that
in Program 10-03-01, the extension number using the adapter is undefined.
12. Plug the line cord back into the keyset. This should only be done once the system has been pro-
grammed as indicated in steps 8-10 above.
To avoid any hardware problems, when removing the adapter, first unplug the line cord, then
any other adapter cables.
13. Wait approximately 1 minute for the adapter to be recognized by the system.
14. Check Program 10-03-04 or 10-03-06 to make sure the system recognizes the CTA adapter. If not,
unplug the phone, undefine the port in Program 10-03-01 and repeat the installation steps.
15. Connect the serial cable from the PC to the CTA Adapter.
16. When using the adapter for TAPI, install the CTA Adapter driver downloaded from the NEC Techni-
cal Support web site (http://ws1.necii.com). Refer to the following steps for the driver installation.
To uninstall the CTU Adapter, refer to Uninstalling the CTA Driver/Adapter on page 2-20.
If a CTU adapter has been used previously, the CTU driver must first be uninstalled before installing
the CTA driver. Correct operation will not be possible if the CTA driver is installed without first
removing the previous CTU driver.
PC Specifications
Recommended Hardware
Windows 98 Second Edition
● CPU : Intel Pentium 300MHz or higher compatible processor
● RAM : minimum 64MB
● HD : minimum 50MB
● An available RS-232C port
10. After the file installation has completed, the INITIALIZING dialog box appears. The setup must
now be performed in order for the CTI application to operate correctly.
2
11. The ASPIRE TELEPHONY SERVICE PROVIDER dialog box appears.
This window can be accessed after the installation process by clicking START - SETTINGS -
CONTROL PANEL - TELEPHONY or PHONE AND MODEM OPTIONS (depending on the ver-
sion of Windows software being used) then click the TELEPHONY DRIVERS or ADVANCED
(when using Windows 2000 or XP) tab to display the following screen.
The TSP Setup must match the Aspire system data to ensure that this product operates correctly.
12. Continue the installation process with TSP Basic Setup – Telephony System on page 2-12.
3. Select ASPIRE TELEPHONY SERVICE PROVIDER on the screen above and click CONFIGURE
to display the TSP setup screen.
There are three TSP setup dialog boxes - one for basic settings of the TSP, one for line configuration, and
one for port settings. The first and second dialog boxes are each associated with a setup screen (tab).
TSP setup consists of the following seven screens.
The TSP Basic Setup dialog box has the following tabs:
<1> Telephony System
<2> Power Management
The TSP setup dialog box (screen <1>) appears when the TSP setup screen is started. Click LINE CONFIG-
URATION on screen <1> to display the Line Configuration dialog box (screen <3>), or click PORT SET-
TING in screen <1> to display the Port Setting dialog box (screen <7>).
The fields on the screen are as described below. Read thoroughly and enter settings appropriate for the
system environment.
Operation Mode
Select to suit the application used.
● Select NORMAL if using a CTI application with the Aspire system.
● Select SINGLE LINE if using a CTI application with the i-Series system.
● Select ELITE/XEN if using a CTI application with the Elite / Xen system.
A PC is normally set up to ensure that it does not enter the Sleep or Hibernation mode during an active call.
These modes may be enabled by changing the relevant setting on this screen, and conversely, they may be
completely disabled while TAPI applications are running. Note that the power management function cannot
be used with Windows NT 4.0. Under Windows NT 4.0, the PC is unable to enter the sleep or hibernation
modes while a TAPI application is running.
The fields on the screen are as described below. Read thoroughly, and enter settings appropriate for the sys-
tem environment.
The fields on the screen are as described below. Read thoroughly, and enter settings appropriate for the sys-
tem environment.
Call Mode
● Select AUTO SPEAKER MODE to emit a tone from the phone speaker when a line is acquired.
● Select AUTO HEADSET MODE to emit a tone from the headset connected to the phone when a line is
acquired.
● PC cannot be selected.
Usage of other extensions may be monitored by adding extensions in THE EXTENSION POSSIBLE TO
MONITOR list to THE EXTENSION TO BE MONITORING list.
The fields on the screen are as described below. Read thoroughly and enter settings appropriate for the sys-
tem environment.
Line Name:
● Enter EXTENSION xxx KEYSET (‘xxx’ is the extension number of the phone connected to the PC).
Phone Number:
● Enter the extension number of the phone connected to the PC.
Different block call information may be set/not set depending upon the mode selected with NOTIFY CALL
INFORMATION (O : May be set, X : Cannot be set).
2
Block Call
Notify Call
Incoming
Outgoing Call Internal Call Trunk Number
Call
Mode 0 X O O O
Mode 1 O O O O
Mode 2 O O O O
Mode 3 X X X X
Port Setup
The port used by the CTA adapter is setup on the following screen. It is displayed by clicking PORT SET-
TING on the TSP Telephony System screen (screen <1>).
Enter the name of the COM port connected to the CTA adapter and click OK.
2 2.
3.
Select START - PROGRAMS - ASPIRE TELEPHONY DRIVER (RS) and click UNINSTALL
ASPIRE DRIVER.
The CONFIRM UNINSTALL screen appears. Click OK.
4. The UNINSTALL COMPLETE dialog box appears. Click FINISH to complete the uninstall process.
0893100-108
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
5. Program the system for the feature to be used with the adapter. Refer to the Programming Fea-
tures section in this manual for details on programming.
6. Install the CTU Adapter driver. Refer to CTU Driver Setup (page 2-23) for details.
The CTU Adapter driver can be downloaded from the NEC Technical Support web site:
http://ws1.necii.com.
7. Attach ferrite beads to the AC-R power cable and USB cables. These should be installed on the
ends of the cables closest to the adapter.
The USB cable is a USB Type B Male (to adapter) to Type A Male Cable (to USB device).
3
14
0-
10
93
08
2
9. Hook the two plastic prongs into the bottom of the phone.
10. Push the connector into place. The top latch on the top of the adapter should lock into place when it
is properly positioned.
11. Plug the AC-R AC/DC adapter into the AC jack on the side of the adapter and to an AC outlet.
12. Plug the line cord back into the keyset.
13. Connect the USB cable from the adapter to the USB device to be connected.
To avoid any hardware problems, when removing the adapter, first unplug the line cord, then
the power cord, then any other adapter cables.
To print from the CTU to a printer, you must connect the CTU to a PC, with the printer then
connected to the PC (you can not have a direct CTU-to-printer connection).
14. Confirm in Program 10-03-04 that the CTU adapter is recognized for the keyset's port.
15. You can now confirm the port assignment using the Windows Device Manager (click Start - Set-
tings - Control Panel - System - Hardware - Device Manager). Under the Ports (COM & LPT)
section should be displayed NEC-I CTU Communications Port (Com x). Use the port number
displayed here when connecting via your communications program (such as HyperTerminal). Note
that the baud rate in HyperTerminal does not matter when connecting via USB.
To uninstall the CTU Adapter, refer to Uninstalling the CTU Driver/Adapter on page 2-40.
! IMPORTANT !
• A driver is required for the CTU adapter. This driver can be downloaded from the NEC
Technical Support web site (ws1.necii.com).
• Check the USB port on the PC.
This product is connected to the PC via a USB interface. Check that the USB interface on
the PC is operating normally before installing the CTU driver. Despite the PC containing
•
a USB port, the driver cannot be used unless the BIOS has been setup appropriately.
Multiple CTU adapters cannot be used simultaneously.
Refer to Uninstalling the CTA Driver/Adapter on page 2-20 for the CTA driver uninstall
2
procedure.
If a CTA adapter has been used previously, the CTA driver must first be uninstalled before
installing the CTU driver. Correct operation will not be possible if the CTU driver is
installed without first removing the previous CTA driver.
• Do not connect the USB cable to the PC and CTU adapter until instructed to do so.
Preparations for installation (copying files) are required before connecting the USB cable
between the PC and the CTU adapter. Correct operation will not be possible if the CTU
adapter and the PC are connected before the necessary files are copied.
If the USB cable is connected before the CTU driver is installed, then refer to USB cable
has been connected before the CTU driver is installed. on page 5-3 to setup the CTU
driver again.
PC Specifications
Recommended Hardware
Windows 98 Second Edition
● CPU : Intel Pentium 300MHz or higher compatible processor
● RAM : minimum 64MB
● HD : minimum 50MB
● An available USB port
Windows 2000 / XP
● CPU : Intel Pentium 300MHz or higher compatible processor
● RAM : minimum 128MB
● HD : minimum 50MB
● An available USB port
5. The SERVICE SOFTWARE dialog box appears. When installing the driver for CTI (TAPI) select
the CTI CONNECTION option. If you install the driver for SMDR or other system reports, select
OTHER (non-control sequence) mode.
6. Click NEXT.
10. Connect the USB cable from the CTU adapter to the PC.
Insert the USB cable Series A connector (flat connector) in the socket on the PC.
The CTU adapter must be installed in order for all the TSP menu options to be recognized dur-
ing the installation process.
! Important !
Insert the USB cable firmly in the socket.
3. When the necessary driver has been installed, the PLEASE WAIT ... dialog box appears and the
setup required for the operation of the CTI application proceeds automatically.
5. Continue the installation process with TSP Basic Setup – Telephony System on page 2-33 when
installing the driver for TAPI applications.
6. After the TSP settings have made, the SYSTEM SETTING CHANGE dialog box appears. In order
to confirm a new setup, it is necessary to reboot a computer. Click OK.
Unless the computer reboots, any application which uses the CTU adapter may not operate
correctly.
3. Continue the installation process with TSP Basic Setup – Telephony System on page 2-33 when
installing the driver for TAPI applications.
3. Continue the installation process with TSP Basic Setup – Telephony System on page 2-33.
3. Select ASPIRE TELEPHONY SERVICE PROVIDER on the screen above and click CONFIGURE
to display the TSP setup screen.
There are three TSP setup dialog boxes - one for basic settings of the TSP, one for line configuration, and
one for port settings. The first and second dialog boxes are each associated with a setup screen (tab).
TSP setup consists of the following seven screens.
The TSP Basic Setup dialog box has the following tabs:
<1> Telephony System
<2> Power Management
The TSP setup dialog box (screen <1>) appears when the TSP setup screen is started. Click LINE CONFIG-
URATION on screen <1> to display the Line Configuration dialog box (screen <3>).
The fields on the screen are as described below. Read thoroughly, and enter settings appropriate for the
system environment.
Operation Mode
Select to suit the application used.
● Select NORMAL if using a CTI application compatible with the Aspire system.
● Select SINGLE LINE if using a CTI application compatible with the i-Series system.
● Select ELITE/XEN if using a CTI application compatible with the Elite / Xen system.
A PC is normally set up to ensure that it does not enter the Sleep or Hibernation mode during an active call.
These modes may be enabled by changing the relevant setting on this screen, and conversely, they may be
completely disabled while TAPI applications are running. Note that the power management function cannot
be used with Windows NT 4.0. Under Windows NT 4.0, the PC is unable to enter the sleep or hibernation
modes while a TAPI application is running.
The fields on the screen are as described below. Read thoroughly, and enter settings appropriate for the sys-
tem environment.
The fields on the screen are as described below. Read thoroughly, and enter settings appropriate for the sys-
tem environment.
Call Mode
● Select AUTO SPEAKER MODE to emit a tone from the phone speaker when a line is acquired.
● Select AUTO HEADSET MODE to emit a tone from the headset connected to the phone when a line is
acquired.
The headset button must be registered with a function key when Auto Headset Mode is used.
● Select PC to emit a tone from the PC speaker when a line is acquired.
Usage of other extensions may be monitored by adding extensions in THE EXTENSION POSSIBLE TO
MONITOR list to THE EXTENSION TO BE MONITORING list.
The fields on the screen are as described below. Read thoroughly, and enter settings appropriate for the sys-
tem environment.
Line Name:
● Enter EXTENSION xxx KEYSET (‘xxx’ is the extension number of the phone connected to the PC).
Phone Number:
● Enter the extension number of the phone connected to the PC.
2 Different block call information may be set/not set depending upon the mode selected with NOTIFY CALL
INFORMATION (O : May be set, X : Cannot be set).
Block Call
Notify Call
Incoming
Outgoing Call Internal Call Trunk Number
Call
Mode 0 X O O O
Mode 1 O O O O
Mode 2 O O O O
Mode 3 X X X X
Used to specify the audio device used for sound recording at the specified line and phone.
● Line Media
Input : Specifies the audio device to which the sound from the line (caller) is input as the recording
source.
Output : Specifies the audio device used for playback of sound to the line (caller).
● Phone Media
Input : Specifies the audio device to which the sound from the phone (self) is input as the recording
source.
Output : Specifies the audio device used for playback of sound to the phone (self).
● Line and Phone Mixed Media
Input : Specifies the audio device to which the mixed line (caller) and phone (self) sound is input as
the recording source.
Output : Specifies the audio device used for playback of sound to both the line (caller) and phone
(receiver).
1. Remove the USB cable from the PC. If not, the following error message will appear.
5. The UNINSTALL COMPLETE dialog box appears. Click FINISH to complete the uninstall process.
The PC must be restarted in order to complete the process.
Section 3:
NTCPU Connection and
Driver Installation
3
NTCPU Connection and Driver Installation
Connecting to the Aspire S/Aspire System’s NTCPU
ENTU PCB
9-Pin Female
Connector
LAN Cross Cable
(RJ-45)
Aspire S Connection
3
PC
9-Pin Female
Serial Cross Cable
Connector
Aspire Connection
USB Cable
9-Pin Female
Connector
PC
9-Pin Female
Connector
ISDN Network
Aspire S Connection
With BRI:
T-Point 9-Pin Female
Terminal Connector
Adapter LAN Cross Cable
(RJ-45)
CO Trunk 3
PC
9-Pin Female
Connector
Modem
ISDN Network
With BRI:
T-Point
Terminal
Adapter LAN Cross Cable
(RJ-45)
9-Pin Female
Connector
CO Trunk
Aspire Connection
Modem
PC
9-Pin Female
Connector
3
ENTU-S to Switching Hub Standard Ethernet Cable 328 (100 meters)
(straight-cable)
3
Aspire: Set the SW3 switch number 1 on
the Aspire NTCPU to OFF (down).
If it is set to ON, this is the debugging
mode and the serial connection will not
work.
2. Through telephone programming, use Program 10-21-02 to set the NTCPU serial communication
baud rate (default=19200).
It is recommended to increase the baud rate to 38400 (the maximum rate for a serial
connection).
3. Connect the PC to the serial port on the Aspire S/Aspire NTCPU using a null modem (cross-over)
cable (P/N 0892004).
The modem to be used should already be installed on the PC. Refer to the modem installation
instructions for details, if needed.
When creating a null modem cable, refer to the Null Modem Pin-Out table which follows.
Signal DB-25 Pin DB-9 Pin To DB-9 Pin DB-25 Pin Signal
FG (Frame Ground) 1 - - 1 FG
TD (Transmit Data) 2 3 2 3 RD
RD (Receive Data) 3 2 3 2 TD
RTS (Request to Send) 4 7 8 5 CTS
CTS (Clear to Send) 5 8 7 4 RTS
SG (Signal Ground) 7 5 5 7 SG
DSR (Data Set Ready) 6 6 4 20 DTR
CD (Carrier Detect) 8 1 4 20 DTR
DTR (Data Terminal Ready) 20 4 1 8 CD
DTR (Data Terminal Ready) 20 4 6 6 DSR
3 4. Using a communication software (such as HyperTerminal), connect to the Aspire S/Aspire serial
port which is connected to your PC’s serial COM port (usually COM 1). The baud rate setting in
the communication software must match the Aspire S/Aspire setting in Program 10-21-02. In addi-
tion, the following items should be set :
Data Bits=8, Parity=None, Stop Bit=1, Flow Control=Hardware.
5. Type AT and press Enter.
Either OK or AT should appear to tell you that your cable connection and communication
parameters are set correctly. If not, recheck your communication parameters set in Program 10-21-
02, recheck the communication software parameters and check that the null modem cable is using
the correct pin-out.
6. Disconnect the HyperTerminal session.
CN1
3
Serial Cable
Connector
(D-Sub 9-pin male)
3. Connect the PC to the serial port on the Aspire S/Aspire NTCPU using a null modem (cross-over)
cable (P/N 0892004).
The modem to be used should already be installed on the PC. Refer to the modem installation
instructions for details, if needed.
When creating a null modem cable, refer to the Null Modem Pin-Out table which follows.
Signal DB-25 Pin DB-9 Pin To DB-9 Pin DB-25 Pin Signal
FG (Frame Ground) 1 - - 1 FG
TD (Transmit Data) 2 3 2 3 RD
RD (Receive Data) 3 2 3 2 TD
RTS (Request to Send) 4 7 8 5 CTS
CTS (Clear to Send) 5 8 7 4 RTS
SG (Signal Ground) 7 5 5 7 SG
DSR (Data Set Ready) 6 6 4 20 DTR
CD (Carrier Detect) 8 1 4 20 DTR
DTR (Data Terminal Ready) 20 4 1 8 CD
DTR (Data Terminal Ready) 20 4 6 6 DSR
3 4. Use a communication software (such as HyperTerminal) to connect to the Aspire S/Aspire serial
port. Set the communication software to use the following settings:
- Baud Rate: 19200
(must match Aspire Program 10-21-02 setting)
It is recommended to increase the baud rate to 38400 (the maximum rate for a serial
connection).
- Data Bits: 8
- Parity: None
- Stop Bits: 1
- Flow Control: Hardware
If using HyperTerminal, start the program by clicking START - PROGRAMS - ACCESSORIES -
COMMUNICATIONS - HYPERTERMINAL. Create a name for the new connection, such as
MODEM SETUP and click OK.
Select the COM Port to be used and click OK, set the RS232 options with the above settings,
then click OK.
5. Type AT then press Enter.
Either OK or AT should appear to tell you that your cable connection and communication
parameters are set correctly. If not, recheck your communication parameters set in Program 10-21-
02, recheck the communication software parameters and check that the null modem cable is using
the correct pin-out.
6. Once the communication between the system and PC is established, the Aspire S/Aspire serial port
needs to be modified with the following entries. After each line, press the Enter key.
ATR1
AT&W
The screen should indicate a series of ATs. If not, repeat Step 6 until they appear.
To reset this serial port to its initial setting, enter:
ATR0
AT&W
7. Disconnect the HyperTerminal connection but do not close the HyperTerminal program. Discon-
nect the PC from the Aspire S/Aspire system.
8. Connect the NEC-recommended CNet modem model #CN5614XR (P/N 85862D) power supply to
the modem, connect the modem using a straight-through cable to the serial communication port of
your computer, and turn on the modem.
Check the manuals that came with your computer if you’re not sure how to set up and connect a
modem to your computer.
Though remote connection is possible for SMDR and DIM history, it is not recommended as
the change in the modem initialization string will prevent access with the PCPro application. In
addition, for SMDR, unless a device is constantly connected, records will be lost once the buffer
fills (500 calls - the oldest records are deleted and the new calls are stored).
3
connection will not work. Serial Cable
Connector
For DIM: Set the SW3 switch on the (D-Sub 9-pin male)
Aspire S CPU to the “3” position (down).
If it is set to “1” (up), this is the
SMDR/PCPro mode and the DIM
connection will not work.
Aspire:
For SMDR: Set the SW3 switch number
1 on the Aspire NTCPU to OFF (down).
If it is set to ON, this is the debugging
mode and the serial connection will not
work.
For DIM: Set the SW3 switch number 1
on the Aspire NTCPU to ON (up).
If it is set to “OFF” (down), this is
the SMDR/PCPro mode and the DIM
connection will not work.
3. Connect the PC to the serial port on the Aspire S/Aspire NTCPU using a null modem (cross-over)
cable (P/N 0892004).
The modem to be used should already be installed on the PC. Refer to the modem installation
instructions for details, if needed.
When creating a null modem cable, refer to the Null Modem Pin-Out table which follows.
Signal DB-25 Pin DB-9 Pin To DB-9 Pin DB-25 Pin Signal
FG (Frame Ground) 1 - - 1 FG
TD (Transmit Data) 2 3 2 3 RD
RD (Receive Data) 3 2 3 2 TD
RTS (Request to Send) 4 7 8 5 CTS
CTS (Clear to Send) 5 8 7 4 RTS
SG (Signal Ground) 7 5 5 7 SG
DSR (Data Set Ready) 6 6 4 20 DTR
CD (Carrier Detect) 8 1 4 20 DTR
DTR (Data Terminal Ready) 20 4 1 8 CD
DTR (Data Terminal Ready) 20 4 6 6 DSR
4. Use a communication software (such as HyperTerminal) to connect to the Aspire S/Aspire serial
3
port. Set the communication software to use the following settings:
- Baud Rate: 19200
(must match Aspire Program 10-21-02 setting)
It is recommended to increase the baud rate to 38400 (the maximum rate for a serial
connection).
- Data Bits: 8
- Parity: None
- Stop Bits: 1
- Flow Control: Hardware
If using HyperTerminal, start the program by clicking START - PROGRAMS - ACCESSORIES -
COMMUNICATIONS - HYPERTERMINAL. Create a name for the new connection, such as
MODEM SETUP and click OK.
Select the COM Port to be used and click OK, set the RS232 options with the above settings,
then click OK.
5. Type AT then press Enter.
Either OK or AT should appear to tell you that your cable connection and communication
parameters are set correctly. If not, recheck your communication parameters set in Program 10-21-
02, recheck the communication software parameters and check that the null modem cable is using
the correct pin-out.
6. Once the communication between the system and PC is established, the Aspire S/Aspire serial port
needs to be modified with the following entries. After each line, press the Enter key.
ATQ1
ATE0
S0=1
These commands will turn off local echo, provide no result codes, and enable auto answer.
To reset this serial port to its initial setting, enter:
ATQ0
ATE1
S0=0
7. Disconnect the HyperTerminal connection but do not close the HyperTerminal program. Discon-
nect the PC from the Aspire S/Aspire system.
Aspire S
Ethernet
Straight-Thru
Aspire S Cabinet
Cable
0893130-110A
LAN 3
CPU
Ethernet PC 4VOIPU
4VOIPDB
ENTU
AC Adaptor
(Not needed if power
supplied by LAN)
Aspire IPhone,
Aspire Keyset with IP Adapter or
H.323 Terminal
Aspire M/L/XL
Ethernet
Straight-Thru
Cable Aspire Cabinet voipA.eps
LAN
NTCPU
Ethernet PC 4VOIPU
4VOIPDB
16VOIPU
AC Adaptor
16VOIPDB
(Not needed if power
8SHUBU
supplied by LAN)
Aspire IPhone,
Aspire Keyset with IP Adapter or
H.323 Terminal
2. Connect the Aspire S/Aspire system to the PC using a LAN cable. When connecting to a LAN hub,
use a straight-through cable. If connecting directly to the telephone system, use a cross-connect
cable.
Connect the cable to the CN15 LAN connector on the Aspire M/L/XL NTCPU or the CN2 LAN
connector on the ENTU with the Aspire S.
If the connection is correct, the green and amber LEDs on the LAN connector in the Aspire S/
Aspire system will be lit.
5. In the list of items, INTERNET PROTOCOL (TCP/IP) should be checked. Click on the INTER-
NET PROTOCOL (TCP/IP) and then click on PROPERTIES.
With the Aspire S/Aspire set to use the built-in DHCP Server (Program 10-12-01 = IP Address
172.16.0.10 and Program 10-13-01 = 1 [DHCP Server enabled]):
The network settings on the PC connected to the Aspire S/Aspire system must be set to obtain an IP
address automatically.
1. Insert the disk containing the NEC USB driver into your PC.
2. Connect the Aspire system to the PC using a USB cable.
3. Windows notifies you of new hardware found. Open the Hardware Wizard window to begin the
setup.
4. The software locates the USB driver file on the disk and begins the installation.
Depending on your software, the next screen may ask you to check which drives should be
searched for the USB driver.
5. When the following window appears, click CONTINUE ANYWAY.
8. The PC must then be restarted in order for the USB port to work.
3
10. Click on the DEVICE MANAGER button. The following screen displays listing the installed
hardware.
11. Click on MODEM. If the installation was successful, the NECI USB MODEM will be listed.
If the NECI USB Modem is not listed, repeat the installation process.
Section 4:
Feature Setup / Programming
This section details any additional setup or programming required for the data features. After determining the system
connection, and installing the required adapter and driver, use this section to finalize the setup and programming.
●
●
Alarm Reports (page 4-3)
inDepth Lite/inDepth/inDepth+ (page 4-5)
4
● PCPro/WebPro:
❍ PCPro/WebPro - Setup (page 4-45)
❍ PCPro/WebPro - Using PCPro (page 4-71)
❍ PCPro/WebPro - Using WebPro (page 4-77)
❍ PCPro/WebPro - Features (page 4-81)
● SMDR (page 4-101)
● SMDR - Installing (page 4-107)
● SMDR - Programming (page 4-110)
● System Information Reports (page 4-121)
● TAPI 1.x / CTI (page 4-123)
● TAPI 2.1 / CTI (page 4-127)
● Traffic Reports (page 4-179)
● Ultra CallAnalyst (page 4-181)
● Ultra CallAnalyst Server (CES) (page 4-183)
Alarm Reports
Alarm Reports
The system logs various errors and information about the operation which can be used to determine the cause of a problem (up
to 100 individual alarms are stored, then oldest data is deleted to allow for new information to be stored). The system can indi-
cate the errors on a keyset’s display, send the information to a printer at a programmed time, or send the data via EMail. When
an alarm report is printed through PCPro, the system will not delete the report data after printing. If the system is set up to
EMail the report and the mail server is down, the report will not be sent.
Sample Report:
4
<< Alarm Report >> 06/16/2003 14:12 PAGE 001
Programming
Basic Programming
➻ 90-10-01 : System Alarm Setup - Alarm Type
Assign a status to system alarms (001-100). You can designate an alarm as Major or Minor (0=no notifi-
cation, 1=major alarms displayed, 2=minor alarms displayed).
➻ 90-10-02 : System Alarm Setup - Report
This program assigns whether or not the alarm is displayed to a key telephone and whether or not the
alarm information is reported to the pre-defined destination (0=no report, 1=report).
➻ 90-11-01 : System Alarm Report - System Alarm Display Telephone
Assign the display keyset’s extension number that should receive system alarms.
➻ 90-12-05 : System Alarm Output - Clear All Alarm Reports
Entering 1 will clear all alarm reports.
➻ 90-12-06 : System Alarm Output - Output Mode
Select either manual (0) or automatic (1) alarm reports.
➻ 90-24-01 - 90-24-04 : System Alarm Report Notification Time Setup
Set the month (00=disabled, 01-12), day (00-31), hour (00-23), and minute (00-59) that the alarm report
should print. Up to 12 time settings can be programmed (01-12). This report will indicate both major
and minor alarms.
inDepth Lite/inDepth/inDepth+
inDepth Lite/inDepth/inDepth+
Introduction
Welcome to inDepth MIS, a Call Center Management tool which provides real time status information, cumulative perfor-
mance statistics and a range of historical reports to help you manage the people in the Call Center and the level of service you
provide to your customers. The system uses the WindowsTM Graphical User Interface (GUI) giving it a look and feel which is
consistent with other WindowsTM products you may use. This manual is directed toward those familiar with WindowsTM and
NEC’s Aspire telephone systems and its programming.
The inDepth Management Information System (MIS) computer software enhances the ACD capabilities of the NEC’s Aspire
phone systems. Using the WindowsTM-based program, real time statistics and reports are available to a customer providing
ACD group traffic patterns and usage. The inDepth software is designed with a high degree of flexibility to suit the needs of a
wide range of call centers. To allow even more flexibility, there are three levels of the inDepth software - inDepth Lite, inDepth
and inDepth+.
The inDepth Lite software provides small or startup organizations the ability to choose from six different management reports
and four different status options to appear on-screen in the display window. Only a single screen template can be created and
4
saved.
The inDepth software offers many of the MIS capabilities of inDepth+ but is streamlined for more modest ACD applications.
The inDepth provides a single real time screen template that may include up to 14 different status windows, up to seven reports
and can track report data for up to one full month. Customized reports may be created, but the template for a report may not be
saved. Although loaded with ACD/MIS capabilities like Report View/Print and Audible/Visual Alarms, inDepth excludes the
ability to run certain reports as well as the ability to connect multiple inDepth computers. In addition, there are limits on the
number of real time screens available and wallboards are not supported.
The inDepth+ software is the most comprehensive and capable ACD/MIS package and offers 30 different reports, the ability
to create and save an unlimited number of customized report templates and it includes one (1) inView user license.
The type of license assigned to the PC dongle determines which inDepth software is available to the user.
Throughout this section, unless otherwise noted, references to the inDepth Lite, inDepth or inDepth+ will be made as
“inDepth”.
The inDepth software is made up of three main components; Real Time Displays, the Reporter, and the Configurator. Commu-
nicating through the Open Application Interface (OAI), inDepth provides an extensive set of user-configurable Real Time Win-
dows and Reports.
For details on using the Configurator, Real Time Displays, Reports, and Wallboards, refer to the inDepth Lite/inDepth/
inDepth + Manual, P/N 0893230.
The Reporter
The Reporter is the source for information about each agent’s activity. This allows ACD system administrators to cre-
ate fully-configurable reports for display and printing. The reports can include traffic reports, event/activity reports,
utilization reports, contention reports, agent-based reports, wait time profiles, etc. Each report format is saved as a
4
template and can be started or stopped at any date and time.
The Configurator
The Configurator is the place to create the settings for the software. In the Configurator, devices and groups of devices
are created, shifts are created, real call thresholds are set, and passwords are set. All the editing and programming for
the inDepth is done within the Configurator.
Common Configuration
The inDepth MIS and inDepth Reporter run over the top of a common configuration database that defines what lines,
DID numbers, extensions, agents and their corresponding groups the system is monitoring.
The inDepth Configurator manages this common configuration database. The inDepth Configurator can be password
protected to stop unauthorized access. Also, on networked systems, it is possible to setup the network of inDepth MIS
and Reporter applications to have just one common configuration database.
The displays may be configured to report on individual devices, device groups, or on a supergroup
(group of groups).
The only limit to the number of windows that can be displayed at any one time is the size of the
●
screen and the size of each window.
One real time template can be created and saved at any time using any number of windows.
4
● Six types of reports available.
Reports can be viewed on screen and printed, but may not be saved.
- Agent Traffic Report
- Agent Group Traffic Report
- Agent Group Traffic Profile Report
- Agent Utilization Report
- Line Group Traffic Report
- Line Group Traffic Profile Report
4
● Call-In Queue Graphs
The displays may be configured to report on individual devices, device groups, or on a supergroup (group of
groups).
The only limit to the number of windows that can be displayed at any one time is the size of the screen and the
size of each window.
● One real time template can be created and saved at any time using any number of windows.
4
●
The displays may be configured to report on individual devices, device groups, or on a supergroup (group of
groups).
The only limit to the number of windows that can be displayed at any one time is the size of the screen and the
size of each window.
● Any number of real time templates can be created and saved at any time using any number of windows.
If a window layout contains too many windows to be visible on the screen, then the windows are moved to
the top left-hand corner and a warning message box will be displayed.
● The maximum period of an individual report is 1 year, except event reports which have a maximum of 10,000
events.
● Reports may be exported in comma delimited format to spreadsheet packages like ExcelTM or Lotus 123TM, where
information may be displayed in graphical format.
● The inDepth database may be exported (in call record format) to a 16-bit ODBC compliant database for further
analysis.
Note: The ODBC is installed when the inDepth+ program is installed. However, the ODBC drivers are not
installed. Therefore, to use the ODBC option within the Reporter, the user must install the relevant ODBC driver
for their particular database.
inDepth products may operate up to 1000 agents, with 1000 extensions, 1000 DID’s, and 1000 lines but are lim-
ited to the capacity of the telephone system. Up to 500 groups and 500 supergroups are supported.
Aspire S:
- ACD: Not Supported
- Lines and Extensions: 8x50
Aspire M/L/XL:
4
- ACD Agents: 512
- ACD ID Codes: 512 [Program 41-18]
- Lines and Extensions: 200x512
● Remote Access
Remote access is supported by all inDepth products. To use this feature, an additional remote access package,
such as PC AnywhereTM is required by the user and the Technical Support center. This allows a technician to dial
in remotely to the system to make programming changes.
● Help File
There is a comprehensive context-sensitive help file with all inDepth products which provides users with imme-
diate on-line assistance on operation and programming.
● Alarms
Audible and visual alarms may be programmed at the individual device or group level. They enable the supervi-
sor to continue with their daily activities with the knowledge that any problems will be highlighted by means of
an audible or visual alarm.
● Password Protection
Password protection of the product configuration, exit of the product, real-time screen templates and reporting
templates is standard. Additional security has been added by the introduction of security groups.
● Flexible Reporting
Reports can be compiled using statistics relating to any shift pattern, as defined by the call center manager. When
compiling a report, the user defines the time period over which the report is compiled. This period may be
defined to the nearest minute and is not limited to any time boundaries. For example, a report can cover the
The resolution of event reports (inDepth+ only) is to the second. For profile reports, the user may set the resolu-
tion to any integral value of minutes, hours, days or weeks.
● Automatic Reporting
The Automatic Reporting feature of inDepth enables reports to be generated at user-defined times (and intervals).
There is a choice of outputs available; more than one output option can be selected at any one time.
4 ●
data.
Automatic Configuration
All individual devices will automatically be identified and added to the product configuration as they appear.
These devices then simply require grouping according to user requirements.
● Output Options
● Print - After the report has been generated, it will automatically be printed to the inDepth
default printer.
● Close on Completion – After the report has been generated or has completed any other output
options selected, the report will be removed from the inDepth Reporter screen.
● Save to file – The report will be saved after being generated to the file name specified. Every time
this report is generated, the name will be overwritten. (Only available on inDepth+)
● Export to file – This is similar to Save To File but it will create a text file which can be opened in
another application such as a spreadsheet package. (Only available on inDepth+)
The reports may be scheduled to output a report every hour, day or week at a specified time. There are advanced
scheduling options which include more control over interval, frequency, commencement date and period of the
report.
Version 2 Schematic
With a single license, all applications are installed on the same PC.
Version 3 Schematic
With a single license, each application (Real Time MIS or Reporter) can be installed on separate PCs.
LAN
Gateway Other applications across the LAN
● Aspire Cabinet with station and trunk cards (Loop Start, Ground Start, DID, T1, etc.)
● LAN connection from the inDepth PC to the Aspire cabinet
(Aspire S requires an ENTU PCB, P/N 0891053, for LAN connections.
Aspire provides a LAN connector (CN15) on the NTCPU or use an 8SHUBU PCB, P/N 0891021.)
The maximum length should not exceed 328 feet (100 meters).
● ACD group or groups set up and running (Aspire only)
● M.I.S. inDepth/inDepth+ software dongle
● inDepth software version 3.10.500.1 or higher
- With Windows 2000 or Windows XP using inDepth version 2.xx, a driver update is required. This driver update can
be obtained from the NEC web site (web address: www.necii.com) in the Software Library.
Information Flow
As the inDepth program and the telephone system work together, prior to installing the inDepth software, be sure to
have the following information available:
● Software level of the telephone system
● Telephone system configuration (trunk cards, station cards, and their types)
● Number of lines connected to the system and their types (loop, ground start, DID, T1 DNIS)
● Number of extensions connected to the telephone system
● Number of agents and their log-in PIN numbers
● The configuration for the PC which will be running the inDepth software
● The software level and type of the inDepth software
Installation
6.
is already connected to a network and you are connecting to the NTCPU through a hub or router, please check with
your network manager to determine the IP address that should be used.
The following information is based on a stand-alone PC using Windows XP connected to the Aspire, with the Aspire
4
using the default settings for the IP address and subnet mask (Program 10-12-01: IP Address 172.16.0.10 / Program
10-12-02: Subnet Mask 255.255.0.0).
a. To change the TCP/IP information, click START ☞ SETTINGS ☞ NETWORK CONNECTIONS.
The following window appears.
4 c. In the list of items, click on the INTERNET PROTOCOL (TCP/IP) and then click on PROPERTIES.
d. In the Internet Protocol (TCP/IP) Properties window that appears, click on USE THE FOLLOWING IP
ADDRESS button and enter the following:
IP Address: 172.16.0.100
Subnet Mask: 255.255.0.0
Note: After installing the inDepth software, any remaining COM ports will be disabled for all other func-
tions. (If inDepth is removed you can enable the COM ports by doing the following: From the START menu, high-
light PROGRAMS-INDEPTH MIS (US) and click on INDEPTH SETUP. Click on the EVENT SOURCE tab and
set the PORT NUMBER to <NONE>. If you wish to reinstall inDepth, reverse these steps.)
Note: The IP address for the NTCPU’s LAN connector must be entered in the inDepth Setup. This will be
requested during the installation process, but can be changed later by selecting INDEPTH SETUP from the
inDepth program group in the Windows Start Menu (START ☞ PROGRAM ☞ INDEPTH ☞ INDEPTH SETUP).
Select the Phone System Connection tab. This is available for the Server PC only. This indicates the network port
number and the IP address of the Aspire system. The Aspire default for this is set at port 0 and IP address
172.16.0.10, but it can be changed. Refer to Program 10-12-01 for the IP address and Program 10-20-01 for the
port number.
TCP/IP
TCP provides reliable byte stream communication between pairs of processes in hosts attached to interconnected net-
works. It is the portion of the TCP/IP protocol suite that governs the exchange of sequential data. IP provides the
addressing needed to allow routers to forward packets across a multiple LAN inter-network. If these protocols are not
installed, inDepth will not run and the PC may act erratically.
4 The inDepth software requires that the system has TCP/IP protocols installed. Install the TCP/IP protocols before
proceeding with the installation. If you already have TCP/IP installed, use the steps below to confirm that it is work-
ing correctly. If you need to install TCP/IP, the Windows installation disks will be required.
PC Power Management
Power Management must be disabled on the server PC. This is accessed through the Control Panel.
1. From the WindowsTM menu, click START. Highlight SETTINGS and click on CONTROL
PANEL.
2. Double-click on the POWER MANAGEMENT icon.
3. Make sure that SYSTEM STANDBY, TURN OFF MONITOR, and TURN OFF HARD
DRIVES are set to NEVER.
The computer name should be something that is easily recognizable on the network (i.e.,
INDEPTHPC). The name must contain at least one letter character and must not contain any char-
acters such as spaces or punctuation marks.
1. Shut down all open applications. This includes any PC’s that are networked by the inDepth
program.
2. Carefully remove the existing dongles from all the PC(s).
3. Connect the new dongle to the machine chosen as the inDepth Server.
4. Before performing any upgrade, back up the existing configuration and data (if possible) to a
temporary directory on the hard drive, or more preferably, a storage area on the network.
5. Continue with PRODUCT INSTALLATION.
1. Make sure the telephone system is connected to the inDepth PC using either a LAN cable.
2. Insert the dongle into the parallel port.
If a printer is to be attached to this PC, then the printer should be connected to the con-
nector at the back of the dongle.
3. Insert the inDepth MIS CD-ROM into the drive. If the PC is configured to auto play CD-
ROMs, a menu screen will appear and offer a choice of installing the live software, demo soft-
ware, or to view the explore the CD. If the auto play option is disabled on the PC, browse and
double click on the Autorun.exe file.
With software version 3.04, both the inDepth and inDepth+ software is included on the
installation CD. The type of dongle installed determines which version of the inDepth software
is installed. With software 3.11.100.0, the installation CD also provides inDepth Lite ability.
With software version 3.10 or higher, the inDepth+ software can be run in evaluation
mode without a dongle for 30 days from the point of installation. In this mode, inDepth+ will
run with 1 Supervisor, 1 Reporter, and 5 inView licenses.
4. After selecting the option to install the software an installation wizard will appear: Click NEXT.
Depending on your inDepth version, you may see a message advising you that the dongle
license needs to be upgraded. This would be required, for example, when upgrading to version
3.04 or higher. If you have the new license key, enter it and click OK. If you do not, contact
your dealer for details on obtaining a new license key.
5. The installation program will display the same Name and Company information with which
Microsoft Windows has been registered. Click on the boxes and change the information if
necessary.
4
7. The path box determines the installation path for the program files and should be a path on a
4 local drive of the PC. To change the path, type in a new path or press BROWSE to search for
the location. If the default location is acceptable, click NEXT.
If the installation is an upgrade of an existing inDepth program, the existing directory will
appear. This will allow the existing configuration to be used. To load the program using the
default configuration, enter a new directory for the program installation.
9. The installation wizard will take you to Windows Explorer showing the directories to be
shared. Sharing is enabled by selecting the directory, pressing the right-mouse button and
then selecting the “SHARING” option. Make sure that the directories are shared with FULL,
4
read and write access. Once the directories are shared, proceed by clicking NEXT on the
installation wizard.
11. Select the TCP port (defined in Program 10-20-01) and the IP address of the Aspire (defined in
Program 10-12-01). Click FINISH.
4 This information can be changed at any point after the installation by selecting INDEPTH
SETUP from the inDepth program group in the Windows Start Menu (START ☞ PROGRAM ☞
INDEPTH ☞ INDEPTH SETUP). Select the Phone System Connection tab. This is available
for the Server PC only.
14. Click FINISH to proceed with the installation of the program files. Once the installation pro-
gram has copied all the files to the hard drive, the installation will prompt you to click OK to
finish the installation.
On each screen, the installation process can be progressed by reading the instructions on-screen and press-
ing the Next button. Some of the following screens may be slightly different, depending on the version of inDepth
you are installing.
A client can only be installed when a server is already in place on the network.
1. Insert the inDepth MIS CD-ROM into the drive. If the PC is configured to auto play CD-ROMs, a
menu screen will appear and offer a choice of installing the live software, demo software, or to view the
explore the CD. If the auto play option is disabled on the PC, browse and double click on the Auto-
run.exe file.
With software version 3.04, both the inDepth and inDepth+ software is included on the
installation CD. The type of dongle installed determines which version of the inDepth software
is installed.
With software version 3.10 or higher, the inDepth software can be run in evaluation mode
without a dongle for 30 days from the point of installation. In this mode, inDepth will run with
1 Supervisor, 1 Reporter, and 5 inView licenses.
4
3. The installation program will display the same Name and Company information with which Microsoft
Windows has been registered. Click on the boxes and change the information if necessary.
6. The next step involves pointing the Client to the CONFIG folder present on the inDepth server. Use the
browse buttons to search the network for the inDepth server and the folders. Follow the instructions on
screen.
8. In the ADDITIONAL OPTIONS window, check the box if you want the inDepth to run automatically
whenever the computer is started. Uncheck the box if the inDepth is to be started manually by the user.
9. A review of installation options will be presented. Click FINISH to proceed with the installation of the
program files. Once the installation program has copied all the files to the hard drive, the installation
will prompt you to click OK to finish the installation.
10. When starting inDepth for the first time, there is some programming required. Refer to Starting
inDepth for the First Time (page 4-41) for further details.
In this window, five tabs will be available on the server PC; two tabs on the client PC.
Folders – This is available for the Server PC only. This contains the paths for the logging of data
and the shared configuration. These must be directories on the server PC.
Licensing – This is available for the Server and Client PC. This tab contains the name of the PC to
which the licensing dongle is attached. INSERT allows you to insert a new server name
or number - REMOVE lets you remove it. The PORT number should always be set to
7625. The VALIDATE LICENSE button displays the current licensing contained with
the dongle. This information is for viewing only - no changes can be made here except
in the DIAGNOSTICS tab.
Note: This can only be performed on the PC to which the dongle is physically
attached.
GENERAL tab: This area displays the type of inDepth software installed (inDepth Lite,
inDepth or inDepth+), whether wallboards are available, and the expiration date of the
inDepth program.
CAPACITY tab: This window displays the number of supervisors, agents, reporters, and
extensions for which the inDepth dongle is licensed.
LAN WALLBOARDS tab: This section shows the number of LAN wallboards available
with the current inDepth license.
4 Diagnostics – This is available for the Server PC only. This area allows you to select whether or not
inDepth will store diagnostic information on serial port data and other errors to a file for
troubleshooting inDepth (all serial communications errors are logged regardless of this
setting). You can also determine whether network connections made at the inDepth PC
server will be displayed. These options should only be selected when instructed to do
so.
With inDepth version 3.04 some changes have been made to the Diagnostics:
- diagnostics can be turned on/off without stopping the Gateway
- critical errors are always logged regardless of the diagnostic setting
- auto-configured devices are always logged
- all manual configuration changes are logged
- inDepth Setup only restarts the Gateway when the event source, data directory
or configuration directory is changed
Operational Mode – This indicates whether the product is installed as either a Server or a Client.
Phone System – This is available for the Server PC only. This indicates the network port number and the
Connection IP address of the Aspire system. The Aspire default IP address is set at 172.16.0.10, but
it can be changed (refer to Program 10-12-01). The TCP IP port is set to “0” by default,
but can be changed in Program 10-20-01 (External Device 2). This port number must
match the setting in the inDepth program (set to “4000” by default).
To Add A License:
1. Click TOOLS ☞ ADD LICENSE.
2. After adding a new license, the server PC must be rebooted. All the inDepth client PCs will then need
to re-started.
The following wallboards can be used in conjunction with the inDepth software:
● Shorekarn Messagemaker 2x16
● Shorekarn Messagemaker 4x16
● Shorekarn Messagemaker 2x21
● Shorekarn Messagemaker 4x21
● Spectrum 215C/1512 1x15
● Spectrum 320C/1023 1x20
● Spectrum 4120C/3214 2x20
The wallboards can be connected to the inDepth PC using a standard CAT5 UTP network cable. The connection is
made to the PC using a serial port adapter from the cable. This can either be a 9-way or 25-way D socket. Connection
to a PC will require a free serial COM port.
Once the physical connection has been made, it is necessary to point the inDepth software to the correct COM port
and wallboard type. This is achieved by selecting WALLBOARDS ☞ DRIVERS from the top of the real-time screen.
Up to six wallboards can be connected together on one COM port. Wallboards can only be connected to one COM
port on a PC and only wallboards by the same manufacturer can by connected together. To use wallboards from two
manufacturers will require two PC’s running the inDepth Client software.
4 inDepth Configuration
To ensure reliable and accurate statistics and real time displays, the inDepth must be correctly configured. The basic rule is as
follows:
The configuration of every Trunk (line), Extension, Extension Group, Agent, and Agent Pin on
the telephone system should be mirrored in the configuration of the inDepth MIS. This applies
even if the lines or extensions are not part of the ACD group!
After programming the inDepth with the above information, the other options within the Configurator should also be consid-
ered and programmed as required as they can affect the system’s ability to interpret the information gathered.
For more details on configuring the inDepth system, refer to THE CONFIGURATOR section in the inDepth Lite/inDepth/
inDepth+ Manual, P/N 0893230.
Each line, line group, extension, extension group, etc., uses the first digit to help differentiate between the different devices, in
4
addition to the preceding letter. For example, using the default settings shown above, “L9” is used to define a line, “E3”, ”E4”,
and “E5” define extensions, “A4” defines an ACD Agent, and “D1” is used for DID’s. The only one that must be kept is the line
setting. The first digit for lines must be “9” in order for the inDepth program to recognize it and consist of only 4 digits (this
does not include the ‘L’). For example, in the Configurator, the entry must be “9XX” (The X represents any other combina-
tion of numbers.). When the lines display in the Real Time Display, they will appear as “L9XXX”. If your numbering plan is
different for extensions, agents, or DID’s, you can change the digits inDepth uses to match your system settings. Refer to THE
CONFIGURATOR section in the inDepth Lite/inDepth/inDepth+ Manual, P/N 0893230.
If ACD Agents are using PIN codes to log in on their phones (Program 41-18-01), the inDepth ACD Agent numbers must
match the codes being used on the telephone system. For example, if the ACD Agents use PIN codes that range from 500-650,
the ACD Agent numbers in the inDepth must be changed to A500-A650.
To make changes in the inDepth programming easier, add all the ACD Agents available in the phone system. If the agents’
numbers are not used, the inDepth will ignore them. This will ensure that the data from any new agents added in the telephone
system will be reflected in the inDepth screens and reports. If a line, DID, agent, extension, or extension has not been previ-
ously configured and it is used, inDepth will automatically add the new item to its configuration so accurate call logging is
maintained. But these automatically added devices may not have the preferences you desire, so it’s best to add all the devices
when initially programming the inDepth.
4 12.
The AGENT GROUP AG1 CONFIGURATION window appears.
In the AGENTS AVAILABLE box, click on the first agent number. Use the down arrow to get to the
last available agent number. Hold down the shift key and click on the last agent number.
This will highlight all the agent numbers.
13. Click ADD.
The agent numbers will then be added to the group and will appear in the AGENTS IN
GROUP box.
14. Click OK.
15. In the AGENT GROUP CONFIGURATION window, click OK.
16. In the EXTENSIONS box, click EDIT GROUPS.
The EXTENSION GROUP CONFIGURATION window appears. The first extension group
EG1-ALL EXTENSIONS must be updated to be associated with the correct Agent Group cre-
ated in step 10.
17. With EG1-ALL EXTENSION GROUPS highlighted, click EDIT GROUP.
The EXTENSION GROUP EG1 CONFIGURATION window appears.
18. In the ASSOCIATED AGENT GROUP box, click the drop-down list and select the AG1 group. Click
OK.
19. In the EXTENSION GROUP CONFIGURATION window, click OK.
20. In the INDEPTH CONFIGURATOR window, click on the SAVE CHANGES button.
21. The program will then prompt you with “ARE YOU SURE YOU WISH TO SAVE THE CHANGES
YOU HAVE MADE?”. Click YES.
☞ Note: The inDepth computer must remain on in order to collect data. If the computer is turned off, all
information will be lost for that time period!
Powering down will also cause the following:
- In a network, when a client tries to start inDepth, they will receive an error message.
- In a network, if the server is shut down wile clients are running inDepth, then the clients will fail and
receive an error message.
☞ When audible alarms are selected, in order to receive the alarms, the Taskbar must be visible at all times.
Prior to any upgrading, you must first obtain a license number from NEC Unified Solutions. For this you will need to
provide the NEC representative with the number printed on the side of your dongle.
Sension Services
The inDepth includes two programs that run in the background on the Server PC: SLISVR.EXE and GATEWAY.EXE. In Win-
dows 2000/ME/XP, they can be found by pressing CTRL + ALT + DELETE once. With Windows XP, you will then need to
select the Task Manager and click on the PROCESSES tab. In Windows NT, they can be found in the Task Manager or the
4
Services folder within the Control Panel (the file names are SENSION GATEWAY and SENSION LICENSE SERVER).
If any network connection has been lost between inDepth PCs, then it is advisable to run Setup from each inDepth PC and
press OK. If any components of the inDepth are currently running when OK is pressed, Setup will display a warning message
advising you to close down the running components.
For details on using the Configurator, Real Time Displays, Reports, and Wallboards, refer to the inDepth Lite/inDepth/
inDepth + Manual, P/N 0893230.
PCPro/WebPro
PCPro/WebPro - Setup
Introduction
In addition to the keyset programming, the Aspire system provides the ability to use a PC to access system programming. The
Windows-based PCPro and the HTML-based WebPro allows you to:
● Edit the telephone system programming options from a remote location.
The PCPro application requires changes to be uploaded to the system before they take effect. The WebPro
application applies the changes as soon as the APPLY or OK icon is clicked.
● Access system maintenance functions (like reports and tests).
PCPro PC Requirements
● CPU: Pentium II 500 MHz equivalent or higher ● 128Mb of RAM
● 20Mb of Hard Drive Space ● Monitor Resolution: 800 x 600 pixels or higher
● Mouse ● Microsoft Windows 2000/XP
● Internet Browser: Internet Explorer 6.0 or higher or ● Network Interface Card (NIC)
Netscape 6.0 or higher (depending on connection type)
WebPro PC Requirements
● CPU: Pentium III 600 MHz equivalent or higher ● Monitor Resolution: 800 x 600 pixels or higher
● Mouse ● Microsoft Windows 2000/XP
● Internet Browser: Internet Explorer 6.0 or higher or ● Network Interface Card (NIC)
Netscape 6.0 or higher (depending on connection type)
● When updating the PCPro software, it is recommended that you first remove the existing software version.
● Only one person is allowed in programming mode at a time. An error message will be received if trying to log in
while another user is already in programming mode.
● When exiting the PCPro application, disconnect the session by pressing the F6 key or clicking on COMMUNI-
CATIONS ☞ DISCONNECT before closing the application. Exiting the application without disconnecting will
prevent any attempt to re-enter programming for 10-15 minutes until the session is closed automatically or unless
the system is reset.
● When connecting to the system with PCPro (either before or just after the connection is made), you must make
sure to open an Aspire S or Aspire database file (from within the PCPro application, click FILE ☞ NEW ☞
ASPIRE S or ASPIRE). If this step is not done, the program will not allow you to upload or download data to/
from the system.
● The Aspire S 2.50 software increases the port capacity for the system as well as adds the ability to use IntraMail
which is a plug-in “in-skin” full-featured, DSP-based integrated Voice Mail with Automated Attendant for the
Aspire S.
4 Due to the port capacity changes, it is recommended the system be cold started and the customer database
reprogrammed. However, using PCPro 3.00 or higher, you can choose to reload the majority of the customer
database. Follow the steps in the Aspire S Software Update to 2.50 or Higher Instructions, P/N 0893222.
● If using PCPro on a PC which has inDepth installed, note that a PC Pro database which takes a long time to
download will fail. It is recommended that the inDepth application be installed on its own PC.
● The CTA and CTU adapters cannot be used for system programming access.
● In the Aspire Software Manual (P/N 0893200), the item numbers for the programs indicated below are different
when using PCPro/WebPro due to the window layout of the applications. Refer to the program within the PCPro/
WebPro application to determine the correct item number when making:
- Program 10-03
- Program 15-01
- Program 22-11
- Program 44-03
- Program 47-12
!! IMPORTANT !!
With Aspire software 1.08 or prior, due to modem commands sent by the Aspire system after a
remote session is disconnected, you must wait 30 seconds before dialing back into the system.
For further details on upgrading the Aspire system software, refer to the Upgrade Instructions in the Aspire Software
Enhancements in P/N 0893209. For the Aspire S, when updating 2.0x, 2.1x, or 2.2x software to 2.50 or higher, refer to the
Aspire S Software Update to 2.50 or Higher instructions, P/N 0893222.
•
•
versions 0.29 - 1.10 and 1.14 - 4.0J except for 2.63.
It will also support PCPro 1.23, 2.04 - 4.01+ database files.
It is NOT compatible with Aspire system software 1.11 or PCPro 2.01 or 2.02 database files.
4
5.00D • This version is compatible with Aspire S software 2.50 - 4.0C except for 2.63 OR Aspire software
versions 0.29 - 1.10 and 1.14 - 4.0C except for 2.63.
• It will also support PCPro 1.23, 2.04 - 4.01+ database files.
• It is NOT compatible with Aspire system software 1.11 or PCPro 2.01 or 2.02 database files.
4.10 • This version is compatible with Aspire S software 2.50 - 3.00 except for 2.63 OR Aspire software
versions 0.29 - 1.10 and 1.14 - 3.00 except for 2.63.
• It will also support PCPro 1.23, 2.04 - 4.02 database files.
• It is NOT compatible with Aspire system software 1.11 or PCPro 2.01 or 2.02 database files.
4.02 • This version is compatible with Aspire S software 2.50 - 2.67 except for 2.63 and 2.64 OR Aspire
software versions 0.29 - 1.10 and 1.14 - 2.67 except for 2.63.
• It will also support PCPro 1.23, 2.04 - 4.01 database files.
• It is NOT compatible with Aspire system software 1.11 or PCPro 2.01 or 2.02 database files.
3.00 • This version is compatible with Aspire S software 2.50+ or Aspire software versions 0.29 - 1.10
and 1.14+.
• It will also support PCPro 1.23, 2.04+ database files.
• It is NOT compatible with Aspire system software 1.11 or 1.12 or with PCPro 2.01 or 2.02 data-
base files.
2.05 • This version supports PCPro 1.23 and 2.04 database files and is compatible with Aspire system
software 0.29-1.10 and 1.14-1.16.
• It is NOT compatible with Aspire system software 1.11 or 1.12 or with PCPro 2.01 or 2.02 data-
base files.
2.02 • This version of PCPro is backwards compatible with Aspire system software 0.29-1.12 and with
any PCPro file saved with 1.23 or higher.
• It is incompatible with system software 1.14.
2.01 • This software is not backwards compatible prior to system software 1.11.
1.23
Installing PCPro
To install the PC Program on your hard disk:
1. Insert the PC Program Installation disk into your PC.
2. From MY COMPUTER, double-click on the drive.
3. Double-click on the SETUP.EXE file. You see:
4. Click NEXT.
5. Click on the checkbox to accept the license terms. The following window displays:
10. Make sure the system is connected to the PC in one of the following ways:
● Remote Modem to Serial Port
- Connect to the system modem. Refer to Connecting to the Serial Port - Remotely (page 3-7).
- Continue with Direct Dial Up (modem connection via serial cable to Aspire S/Aspire cabinet)
on page 4-59.
4 - Make sure the system and PC are connected using an RS-232 cable. Refer to Connecting to
the Serial Port - Locally (page 3-5).
- Continue with Creating a Dial Up Setting on page 4-51.
Direct Dial Up (USB cable from PC to Aspire cabinet - not available for Aspire S)
1. Set the SW3 switch number 1 on the Aspire NTCPU to OFF (down).
If it is set to ON, this is the debugging mode and the serial connection will not work.
2. Make sure the PC is connected to the USB port on the Aspire NTCPU with a USB cable and that the USB driver has
been installed (Connecting to the USB Port (page 3-17)).
3. Windows XP: Click on START ☞ PROGRAMS ☞ ACCESSORIES ☞ COMMUNICATIONS ☞ NETWORK
CONNECTIONS.
Windows 2000: Click on START ☞ PROGRAMS ☞ ACCESSORIES ☞ COMMUNICATIONS ☞ NETWORK
AND DIAL-UP CONNECTIONS.
5. In the NETWORK CONNECTION TYPE window, select CONNECT TO THE NETWORK AT MY WORK-
PLACE and click NEXT.
7. Make sure only the box next to the USB Modem is checked and click NEXT.
8. Enter the name to be used for the dial-up connection and click NEXT.
9. Windows XP: In the NETWORK CONNECTION TYPE window, select SET UP AN ADVANCED CONNEC-
TION and click NEXT.
Windows 2000: In the NETWORK CONNECTION TYPE window, select CONNECT DIRECTLY TO
ANOTHER COMPUTER and click NEXT.
The Windows XP window is displayed below.
13. Select COMMUNICATIONS CABLE BETWEEN TWO COMPUTERS as the device type.
Direct Dial Up (modem connection via serial cable to Aspire S/Aspire cabinet)
When using a modem, the following steps are for use with an external modem with an RS-232 serial connec-
tion. If you wish to use an internal modem, your steps will vary slightly.
1. Aspire S: Set the SW3 switch on the Aspire S CPU to the “1” position (up).
If it is set to “3” (down), this is the debugging mode and the serial connection will not work.
Aspire: Set the SW3 switch number 1 on the Aspire NTCPU to OFF (down).
If it is set to ON, this is the debugging mode and the serial connection will not work.
2. Click on START ☞ CONTROL PANEL ☞ PHONE AND MODEM OPTIONS. Click on the MODEMS tab.
If there is not already a built-in modem or standard modem which matches the external modem to be used, one must
be added. Continue with Step 3. If the modem setup already exists, continue with Step 4.
3. Click on ADD and select the DON’T DETECT MY MODEM; I WILL SELECT IT FROM A LIST. Click
NEXT.
Double-click on the type of modem which matches the external modem to be used (STANDARD 33600 BPS
MODEM can be used if unknown) and click on the COM port to be used (usually COM1). Click NEXT and then
FINISH when it appears.
4. Double-click on the installed modem to be used (ex: STANDARD 33600 BPM MODEM) and then click the
MODEM tab.
5. Set the MAXIMUM PORT SPEED to the setting defined in Program 10-21-02 (default 19200).
6. Windows XP: Click on the ADVANCED tab and enter service code 830 in the EXTRA INITIALIZATION COM-
MANDS box. Click OK then click OK again to close the window.
Windows 2000: Enter service code 830 for the EXTRA INITIALIZATION COMMANDS prompt. Click OK until
the control panel screen appears then close that window.
*830).
If an ISDN terminal adapter is used, this entry should be entered with a * preceding the number (example: 4
The 830 dialed above is the Remote Maintenance service code number assigned in Program 11-15-01. By default,
this is set to 830. If this is changed in system software, then the entry made above should match the new code.
7. Windows XP: Click on START ☞ PROGRAMS ☞ ACCESSORIES ☞ COMMUNICATIONS ☞ NETWORK
CONNECTIONS.
Windows 2000: Click on START ☞ PROGRAMS ☞ ACCESSORIES ☞ COMMUNICATIONS ☞ NETWORK
AND DIAL-UP CONNECTIONS.
9. Windows XP: In the NETWORK CONNECTION TYPE window, select CONNECT TO THE NETWORK AT
MY WORKPLACE and click NEXT.
10. Windows XP: The DIAL-UP CONNECTION bullet should be selected. Click NEXT.
Windows 2000: Skip this step.
11. If a list of modems appears, select the modem you want to use for this Aspire dial-up connection by putting a check
mark in the box next to the desired modem and click NEXT. Otherwise, continue with the next skip.
4
15. Windows XP: Click NEXT then FINISH.
Windows 2000: Click NEXT, NEXT then FINISH.
16. Continue with Completing the Dial Up Settings on page 4-64.
These passwords can be changed or additional passwords added after accessing programming using
Program 90-02.
With WebPro, to change or add passwords once connected to the system, click PCPRO SETTINGS, then
clicking ACCOUNT SETUP.
The “Dial” number (if required) should already be filled in with the telephone number/service code to be dialed.
2. Click on PROPERTIES. In the window that appears, select the correct connection type (MODEM ☞ NECI USB
MODEM, MODEM ☞ STANDARD 33600 BPS MODEM, or COMMUNICATION CABLE BETWEEN TWO
COMPUTERS option if not already selected.
3. Click on CONFIGURE. Set the MAXIMUM PORT SPEED to the setting defined in Step 2 and in Program 10-21-
02 (default 19200). This is not required for a USB connection.
4 8.
9.
Click OK.
Select the NETWORKING tab. Only the INTERNET PROTOCOL (TCP/IP) option and QoS Packet Scheduler
option (if displayed) should be checked.
11. Click on the ADVANCED tab. Both the USE DEFAULT GATEWAY ON REMOTE NETWORK and USE IP
HEADER options should be selected.
13. Click on the WINS tab. Make sure the ENABLE LMHOSTS and ENABLE NETBIOS OVER TCP/IP options are
4 selected.
14. Click OK until the property windows are closed and the ASPIRE USER NAME AND PASSWORD screen appears.
15. Click CANCEL.
16. Some computers may not make the baud rate changes in the Device Manager. In order for the connection to be made,
the baud rate must be changed. To verify the correct baud rate has been accepted, right-click on MY COMPUTER,
click PROPERTIES then click HARDWARE.
18. Click once on + PORTS (COM & LPT1) to display the list of available ports.
4 21. Close the DEVICE MANAGER window, then click OK in the SYSTEM PROPERTIES window.
22. Continue with Using PCPro on page 4-71 to begin using PCPro or Using WebPro on page 4-77 to use WebPro.
Using PCPro
Important Points to Remember
● Set the SW3 to the proper position. Aspire S: Set the SW3 switch on the Aspire S CPU to the “1” position (up).
Aspire: Set the SW3 switch number 1 on the Aspire NTCPU to OFF (down). If it is set to the incorrect position
(debugging mode), the serial connection will not work.
● The Aspire system (Program 10-21-02) and the Dial Up setting must be set to use the same baud rate (19200 by
default).
● For local connections, make sure the PC is connected to the serial or USB port on the Aspire NTCPU with a null
modem (cross-over) cable. If connection is through a LAN, the PC should be connected to the Aspire NTCPU
with an ethernet cable.
● When updating the PCPro software, it is recommended that you first remove the existing software version.
● Only one person is allowed in programming mode at a time. An error message will be received if trying to log in
while another user is already in programming mode.
● When exiting the PCPro application, disconnect the session by pressing the F6 key or clicking on COMMUNI-
CATIONS ☞ DISCONNECT before closing the application. Exiting the application without disconnecting will
prevent any attempt to re-enter programming for 10-15 minutes until the session is closed automatically or unless
the system is reset.
4
● In order for users to connect through a firewall, the port used by PCPro must be opened in the router at the far
side. Due to changes in different Aspire system softwares, the port number used by PCPro may be 8 or 8000.
● When connecting to the system with PCPro (either before or just after the connection is made), you must make
sure to open an Aspire S or Aspire database file (from within the PCPro application, click FILE ☞ NEW ☞
ASPIRE S or ASPIRE). If this step is not done, the program will not allow you to upload or download data to/
from the system.
● The Aspire S 2.50 software increases the port capacity for the system as well as adds the ability to use IntraMail
which is a plug-in “in-skin” full-featured, DSP-based integrated Voice Mail with Automated Attendant for the
Aspire S.
Due to the port capacity changes, it is recommended the system be cold started and the customer database
reprogrammed. However, using PCPro 3.00 or higher, you can choose to reload the majority of the customer
database. Follow the steps in the Aspire S Software Update to 2.50 or Higher Instructions, P/N 0893222.
● If using PCPro on a PC which has inDepth installed, note that a PC Pro database which takes a long time to
download will fail. It is recommended that the inDepth application be installed on its own PC.
● The CTA and CTU adapters cannot be used for system programming access.
● The PCPro software provides a Help system if you experience difficulty in using the program. Simply press the
‘F1’ key.
In order for users to connect through a firewall, the port used by PCPro must be opened in the router at the far side.
Due to changes in different Aspire system softwares, the port number used by PCPro may be 8 or 8000.
10. Click CONNECT.
4 Selecting VIEW ☞ VIEW SEARCH TREE BAR will display the program listing on the right side of the
screen as shown in the graphic above.
Using PCPro
To create a new database:
1. Click FILE ☞ NEW. Select Aspire S, Aspire M (for a one-cabinet Aspire system) or Aspire L (for a two-cabinet
Aspire system).
2. Define the PCB layout for the system by dragging the PCB card name (from the list on the right) to the correct cabi-
net and slot number. Change other system programs as required.
After making changes in a window, click the APPLY or OK icon.
3. Click FILE ☞ SAVE AS and select the location where the file should be saved and the name for the file.
Refer to To edit a database and exit programming: below for details on uploading changes to the system.
4
2.
button then click YES to the ‘Are you sure?’ prompt. Click the OK button once the uninstall has completed.
3. Install the latest version of PCPro. Refer to Installing PCPro (page 4-48).
Using WebPro
The WebPro software is installed on the Aspire NTCPU PCB - there is no separate software installation. This means that when
the Aspire system software is updated, the WebPro software is updated as well.
● Make sure the SW3 switch on the Aspire NTCPU (switch just above the serial port connector) is set to OFF
(down).
● The Aspire system (Program 10-21-02) and the Dial Up setting must be set to use the same baud rate (19200 by
default).
● Make sure the PC is connected to the serial or USB port on the Aspire NTCPU with a null modem (cross-over)
cable. For LAN connections, use a straight-through cable if connected through a hub. If connected directly to the
Aspire S/Aspire LAN connector, use a cross-connect cable.
● In order for users to connect through a firewall, port 80 (the port used by WebPro) must be opened in the router at
the far side.
● Only one person is allowed in programming mode at a time. An error message will be received if trying to log in
●
while another user is already in programming mode.
When exiting the WebPro application, disconnect the session by clicking on the menu option LOGOUT before
4
closing the application. Exiting the application without disconnecting will prevent any attempt to re-enter pro-
gramming for 10-15 minutes until the session is closed automatically or unless the system is reset.
● The CTA and CTU adapters cannot be used for system programming access.
● In the Aspire Software Manual (P/N 0893200), the item numbers for the programs indicated below are different
when using PCPro/WebPro due to the window layout of the applications. Refer to the program within the PCPro/
WebPro application to determine the correct item number when making:
- Program 10-03
- Program 15-01
- Program 22-11
- Program 44-03
- Program 47-12
● The WebPro software provides a Help system if you experience difficulty in using the program. Simply click
HELP in the menu.
● Using the browser’s Refresh button will change the screen to either advance or decrease the page based on the
last action. For example, if a screen is displayed showing extensions 311-320, clicking Refresh will change the
page to display extensions 321-330. If the left arrow button in WebPro was used first, the window will show
extensions 301-310.
4 ISDN Connection
LAN (Ethernet)
192.78.0.3
172.16.0.10
Fixed - cannot be changed.
This setting is defined in Program 10-12-01
and can be changed.
4
9. After making changes in a window, click on either the APPLY or OK icon to accept the changes. The system is
immediately updated.
10. When you wish to exit WebPro, click LOGOUT from the Home page in order to log out of the system.
11. Close your internet browser application.
12. (Skip this step for LAN connections) Disconnect the connection between the computer the Aspire system. This is
usually done by double-clicking the Network Connections icon in the tool bar (usually indicated by a double com-
puter icon then clicking the DISCONNECT button).
PCPro/WebPro Features
The main window for WebPro provides a menu for accessing features, settings, and program options. Most of these
options are also available with PCPro, however, you access them using the toolbar at the top of the window.
WebPro PCPro
4
After selecting an option, each window will display options similar to the following:
As displayed in the above graphic, you can search for extensions and select particular keys to program. This area will
change based on the program you are in - this area can allow you to specify the trunk, group, access map, class of ser-
vice, console, etc. If the program option does not require any selection (such as a system-based program option
instead of an extension-based program), this area will not be displayed. However, the top row of icons used for sav-
ing, applying changes, cancel, etc. will always be displayed.
Open
Open a previously saved database using the OPEN command.
Save
After creating or changing a database, save the file for future use.
Save As
Use this option to save an existing file with a new name.
Export
With PCPro 4.00 or higher, the following data can be exported as a CSV or Excel file format (the
programming data can only be exported as an Excel file).
● Maintenance data
● Abbreviated Dial (Speed Dial) data
● Programming data
4
5. Click Export to start exporting.
Conditions
● This data can be saved only as CSV file format. The Excel file format is not supported.
● The data will be saved as each program group (Program 10-xx, Program 20-xx, etc.).
Example: If Program 10-02, 21-04, 30-01, and 30-03 were chosen, the data will be saved as
follows:
Program 10-02 data will be saved as "PRG10-xx.csv".
Program 21-04 data will be saved as "PRG21-xx.csv".
Program 30-01 and Program 30-03 data will be saved as "PRG30-xx.csv".
Function Keys
This option allows you to define the Programmable Function Keys (Program 15-07-01) for each
extension.
This screen also displays the Caller ID list (see below) and Microphone Status (indicates whether
This screen also displays the Caller ID list (see below) and Microphone Status (indicates whether
an extension’s MIC key is on or off) for the extension being viewed.
Copy
The Copy option allows you to copy the program settings from an existing item to another (Pro-
gram 92-01 and 92-03). The following items are available to be copied with this option:
- Telephone Settings- Trunk Settings- Trunk Group Settings
(Extension or Port-Based *)
- Extension Group Settings- DSS Console Settings
Select the category to be copied by clicking the bulleted item at the top of the screen, then select the
programs to be copied, the item from which the settings should be copied, and the item to which the
settings should be copied. Click the SAVE or APPLY icon to save the changes, or click the CAN-
CEL icon.
To select a sequential group of programs, hold down the SHIFT key, click the first program, then
click the last program. To select individual programs, hold down the CTRL key and click the pro-
grams to be selected.
1. Select Copy from the Menu (Programming ☞ Copy) or click the Copy icon in the Tool Bar. 4
2. Select Copy Telephone Settings (Port Base) and enter the "From" and "To" port numbers to
be copied.
The Swap option allows you to swap the program settings from one extension number to another
(Program 92-04).
1. Click Programming ☞ Swap from the Menu or click the Swap icon in the Tool Bar.
2. Enter the extension numbers to be swapped in the Telephone 1 and Telephone 2 fields.
3. Click the Save or Apply button.
Conditions
● Any user-defined programming stored in the SRAM will not be swapped (for example, Call
Forward set up, Selectable Display Messaging, etc.).
● The extensions to be swapped must be idle while the swap is performed, or an "Invalid" error
message will be received.
● Data for virtual extension’s cannot be swapped.
● When a swap is performed, the following actions are executed for the swapped extensions.
- Camp On Clear (Program 11-12-05)
- Common Cancel (Program 11-12-37)
- Last Number Redial Clear (Program 11-17-17)
4
- Saved Number Clear (Program 11-12-18)
- Incoming History data is deleted.
● Using Program 92-04-01 will also swap the order in which these extensions are displayed in
all extension-related programs. This means that the system will no longer display all the
extension numbers from low to high. For example, if port 2 and 6 were swapped, when view-
ing the extensions in 15-02-01, the extensions will display in the following order: 301, 306,
303, 304, 305, 302.
4 This area allows you to configure specific program settings for the administration and account setup
(user name/password) when accessing WebPro.
The Administration option lists currently active programming sessions, the user, how the program
mode is accessed (telephone programming, PCPro, or WebPro), and the program level. This option
also allows you to log out any other WebPro sessions that may be active.
The Account Setup option allows you to setup the user names, passwords and access levels used
when entering the program mode (Program 90-02).
Modification History
This screen displays the details of recent changes made to the system. The changes displayed will
be based on the programming mode being used. When using WebPro, any changes made with Web-
Pro are logged. When using PCPro, only changes made with PCPro are logged. Telephone pro-
gramming changes are not included in either log.
With PCPro software 4.00 or higher, the application can provide a history of the modifications
made in the system programming. This can be viewed using the System Data Programming,
Search Tree Bar and Modification History screens.
This data will be stored in the local PC, therefore, any other revisions made in WebPro or
phone programming will not be saved.
System data
changed
This history information can be saved to a file (refer to Saving and Loading the History File
(page 4-94)).
1. Select Advanced from the menu bar, then choose Modification History.
Conditions
● To clear modified data indication:
When you wish to clear the modified data indication, either select Clear list in the Modifica-
tion History screen or click the Clear Modification History icon in the Search Tree bar.
The modified data indication will remain after uploading any modified data to system.
● Modified data indication for System Configuration:
Uploading modified data indication for the System Configuration screen is not supported.
Therefore, when the system configuration is uploaded to the Aspire system, the configuration
will be revised.
4
Telephone Data
4
Trunk Data
When selecting the 2nd Initialization, the system will be reset, but all programming will remain
(like powering down the system and then powering back up). Any user in program mode will be
logged out (Program 90-08).
System Time
This screen allows you to set the time and date for the system (Program 10-01).
Also displayed at the bottom of this list is the password level with which you are currently logged
in. Not all programs are available with each access level. Refer to the programming section of the
Aspire Software Manual (P/N 0893200) to determine each programs access level.
In addition, the following option can also be accessed from this menu item:
4
● Quick Search
You can click on Quick Search to perform a quick program comparison between the Aspire
and i-Series telephone systems. This would be helpful if you knew a particular program in one
system and wanted the equivalent program in the other system.
● Language Setting
This option allows you to select the language the PCPro windows are displayed.
● Customize
Customize the what is displayed for the commands, toolbars, keyboard, menu, and options.
SMDR
SMDR
Station Message Detail Recording (SMDR) provides a record of the system’s trunk calls. Typically, the record outputs to a
customer-provided printer, terminal or SMDR data collection device. SMDR allows you to monitor the usage at each exten-
sion and trunk. This makes charge-back and traffic management easier.
Sample SMDR Report Through Software 3.07
4
BRD 10:56 01/01/03 002 00:00:00 324 0
ALB 10:56 01/01/03 02 00:00:09
BRD 10:56 01/01/03 002 00:00:00 324 120366541233 0
ALB 10:56 01/01/03 02 00:00:09
BRD 10:56 01/01/03 002 00:00:00 324 181477445236 0
ALB 10:56 01/01/03 02 00:00:08
● Digit Masking
Digit Masking lets you “X” out portions of the number dialed on the SMDR report. A digit mask of
seven, for example, masks out all exchange codes (NNXs) and local addresses. Digit Masking makes it
easier to keep track of calling patterns, without having to interpret each individual number. You can also
use Digit Masking to block out access and security codes.
● Duration Monitoring
SMDR can include calls of any duration, or only those that last longer than the interval you specify. If
you want to keep track of all trunk activity, use a short duration. To keep track of only significant usage,
use a longer duration.
● Extension Exclusion
You can selectively exclude extensions from the SMDR report. This ensures privacy for high-profile
callers. For example, the company attorney negotiating a merger may not want his calls to show up on
an in-house report.
4 ●
just calls that include the PBX trunk access code.
● Trunk Exclusion
Use Trunk Exclusion to exclude certain trunks not subject to per-call charges (like WATS lines) from the
SMDR report. This makes call accounting easier, since you review only those calls with variable costs.
● Usage Summaries
SMDR can automatically print daily, weekly and monthly call activity summaries. Each summary
includes the total number of regular trunk calls and ISDN trunk calls, and the costs for each type. The
daily report prints every day at midnight. The weekly report prints every Sunday night at midnight. The
monthly report prints at midnight on the last day of the month.
If the Caller ID name is not received, the area for Caller ID Name is left blank.
If Program 35-02-18 = 1 (Caller ID Name Output Method) is set to line feed, the SMDR will display as
follows:
CLASS TIME DATE LINE DURATION STATION DIALLED No./CLI ACCOUNT
POT 10:52 12/09 002 00:00:10 2001 2142623801 08754
PIN 10:52 12/09 001 00:00:20 2017 2142623802 NECinfrontia Cor
NEXT NECinfrontia Corp.
PIN 10:53 12/09 002 2142623801 NO ANSWER
Definitions
Call Record Number SMDR record number (consecutive)
CLASS
TIME
Type of call (see Class Definitions below)
Time call placed or answered. (For Transferred calls, shows time
user picked up Transfer.)
4
DATE Date the call was made
LINE Trunk number used for call
DURATION How long call lasted. (For Transferred calls, shows how long user
was on call after answering the Transfer.)
STATION Extension number of call “owner” (i.e., extension that first placed
or answered call) (For Transferred calls, there can be more than one
owner - depending on how many extensions shared the call.)
DIALLED No./CLI For outgoing calls, the number dialed or, for incoming calls, the
Caller ID information
COST For system with ARS, indicates the call cost
OR
ACCOUNT Account Code number entered by extension user
Class Definitions
POT Outgoing trunk call
POTA Outgoing trunk call placed using Toll Restriction Override
PIN Incoming trunk calls
ALB All lines in group are busy (group number follows TIME field)
BRD Call blocked due to Toll Restriction
PTRS Transferred call
IVIN BRI trunk call
4 33-39
40-44
STATION
Spaces
45-51 DIALLED
52 Space
53-59 No./CLI
60-63 Spaces
64-70 ACCOUNT
CR & LF Carriage return and line feed
LF Line feed
SMDR Record
1-4 Call type (e.g., POT for outgoing)
5 Space
6-10 Time in 24 hour clock (HH:MM)
11 Space
12-21 LINE
22 Space
23-30 Call Duration (HH:MM:SS)
31 Space
32-41 Station number or name
42 Space
43-62 Number dialed (20 digits maximum)
63 Space
64-79 Account number or NO ANSWER
OUTGOING CALL/COST
SUMMARY FOR WEEK ENDING nn/nn/nn
TOTAL NO. OF OUTGOING PSTN CALLS:49
TOTAL NO. OF OUTGOING ISDN CALLS:0
NO. OF OUTGOING PSTN CALLS COSTED:0 COST: 0
NO. OF OUTGOING ISDN CALLS COSTED:0 COST: 0
4 Conditions
(A.) The SMDR report does not include voice Intercom calls.
(B.) The SMDR call buffer stores 500 calls. The buffer stores calls when the SMDR device is unavail-
able. When the buffer fills, the oldest record is deleted to allow the new record to be saved.
(C.) When SMDR reports are enabled using the same port as the Traffic Reporting feature (exam-
ple: 147), the SMDR blocks the Traffic reports. Unplugging the cable and plugging it back in
again will allow Traffic reports to print.
(D.) SMDR requires a connection to the NTCPU via a COM port, USB (Aspire only) or LAN con-
nection. A USB connection from the Aspire NTCPU requires the USB driver which can be
downloaded from the NEC Technical Support web site - ws1.necii.com.
The system can also use a connection to the system via a CTA/CTU adapter (the CTU adapter
also requires a USB driver which is also available on the web site). Once you designate a CTA
or CTU for SMDR, you cannot use that extension for placing and answering other data calls.
SMDR and the Traffic Reports should not use the same CTA/CTU.
(E.) If no answer is received, “NO ANSWER” is displayed regardless of the system programing for
the Caller ID display option.
(F.) The setting in Program 35-02-18 works regardless of the entry in Program 35-02-15 or 35-02-
17.
(G.) When Program 35-02-18 is set to "1", the first and second lines are sometimes separated.
When the buffer is full, the overflowed data may not be shown.
(H.) The special characters used in the Aspire system cannot be output to the SMDR - they are con-
verted to “_”.
Default Setting
Disabled.
Installing SMDR
The following devices can be used to output SMDR from the system:
● CTA
● CTU
● NTCPU’s Serial Port
● NTCPU’s USB Port
● NTCPU’s Ethernet Port
The LAN port only provides information through LAN-capable programs, such as
HyperTerminal. Printing of the SMDR information must be done from within that program.)
1. Install the data device to be used (refer to the specific CTA/CTU information described previously).
If using a CTU or the Aspire M/L/XL NTCPU’s USB connector, drivers are required for each of these
devices. The drivers can be downloaded from NEC’s Technical Support web site (ws1.necii.com).
2. Install the SMDR recording device according to the manufacturer’s instructions.
3. Connect the SMDR recording device to the telephone system - through the CTA, CTU or one of the NTCPU ports.
Note: When using a CTA, a straight through RS-232C cable terminated with a 9-pin female connector
is required. Refer to the pin-out information below.
Note: When using a CTU or the NTCPU USB port, a standard USB cable (USB Type B Male-to-USB
Note:
Type A Male) is required.
When using the ethernet port, a standard ethernet cross-over cable is required.
4
Note: When using the NTCPU serial connector, a null modem cable is required. This cable is available from
NEC as part number 0892004 or refer to the pin-out information below to make your own cable.
Signal DB-25 Pin DB-9 Pin To DB-9 Pin DB-25 Pin Signal
FG (Frame Ground) 1 - - 1 FG
TD (Transmit Data) 2 3 2 3 RD
RD (Receive Data) 3 2 3 2 TD
RTS (Request to Send) 4 7 8 5 CTS
CTS (Clear to Send) 5 8 7 4 RTS
SG (Signal Ground) 7 5 5 7 SG
DSR (Data Set Ready) 6 6 4 20 DTR
CD (Carrier Detect) 8 1 4 20 DTR
DTR (Data Terminal Ready) 20 4 1 8 CD
DTR (Data Terminal Ready) 20 4 6 6 DSR
25-Pin RS-232-C
Connector One-Pair Cross-Connect
13 12 11 10 9 8 7 6 5 4 3 2 1
25 24 23 22 21 20 19 18 17 16 15 14
YEL BLK
BLU-WHT WHT-BLU
To digital
station circuit RED GRN
on ESIU PCB
Cross
Connect
Block
25-Pair 625
Installation
4
Modular
Cable Jack
RS-232-C
SMDR Printer Cable (with CTA)
0893130 - 126
OR
Aspire Keyset
with CTA or
CTU Adaptor
USB Cable
(with CTU)
PC
RS-232 Null
Modem Cable
Aspire S
IP Network
Cabinet
Ethernet Cable
0893100 - 126
Cable Jack
25 24 23 22 21 20 19 18 17 16 15 14
RS-232-C
Cable (with CTA
Aspire Keyset
with CTA or
4
or NTCPU Serial connection) CTU Adaptor
SMDR Printer
OR
USB Cable
(with CTU or
NTCPU USB connection)
PC
Aspire Cabinet
IP Network
Programming SMDR
SMDR With a CPU Connection
(Serial / USB / Ethernet)
Start
Connect an
ethernet cable Which connection type will Aspire Only
from the CPU to Ethernet be used to connect the CPU USB Connect a USB cable to
the PC to be used for SMDR? the CPU and PC.
for SMDR.
Serial
4
In 10-21-02, set the
In 35-01-01 set the
baud rate (0=4800, In 35-01-01 set the SMDR
SMDR output to "3"
1=9600, 2=19200, output to "2" for NTCPU USB.
for LAN.
3=38400).
Go to
"A".
Was the
Disconnect
In 15-02-20, set the baud extension on
the phone
rate to be used which the CTA
and undefine
for the CTA connection Adapter is to be
Yes (set to 0)
(0=4800, 1=9600, 2=19200). installed
the keyset's
previously
port in
connected to
10-03-01.
the system?
Yes
Go to
Remove the CTA Adapter.
"A".
Install the CTU USB driver (available from Set 15-02-19 to "0" for the extension
the NEC Technical Support web site - which will have the CTU installed.
www.necii.com). Select "non-procedure" (With PCPro/WebPro, select
service during the installation for SMDR. "Direct Print Mode".)
When connecting to the USB por t using a
communications program (such as
HyperTerminal), you can determine the
COMport used by checking the Ports listing
in the Device Manager (right-click on "My
Yes
Remove the CTU Adapter.
Connect the USB cable to the adapter and PC.
Go to
"A".
"A".
Japanese
In 80-05-01, enter 1.
In 35-03-01, for each trunk group, select the SMDR port (1-8)
to which the incoming SMDR information should be sent. 4
In 35-04-01, for each Department group, select the SMDR
port (1-8) to which the outgoing SMDR information should
be sent.
For example, you can use this feature to
block the printing of security codes.
In 35-01-04, enter the number
of digits you want to block. Do you want to block (i.e., "X"
If you enter 8, for example, Yes out) any of the digits on the No In 35-01-04, enter 0.
SMDR Xs out the last 8 SMDR report?
digits dialed.
Continued on
next page.
Continued
from
previous
page.
In 35-01-06, enter
minimum duration of call Should calls of any
that will print on the No duration print on the Yes In 35-01-06, enter 0.
SMDR report (1-65535 SMDR report?
seconds).
Continued on
next page.
Continued
from
previous
page.
4
Extension Extension
In 35-02-09, enter 0. name
include extension names number
In 35-02-09, enter 1.
or numbers?
Continued on
next page.
Continued
from
previous
page.
Is the system
software
No
version 4.0E
or higher?
Yes
Caller ID Name
4
Should the SMDR report
In 35-02-16, enter Received
Trunk include the trunk port names or In 35-02-16, enter
Number
0. Name received number dialed for ANI/ 1.
Dialed
DNIS and DID trunks?
In 35-02-18, enter
1.
Selecting this option
Should the Caller ID Name
In 35-02-18, enter inserts a line feed
Yes appear on the same line as the No
0. and up to 24
call record?
characters can be
displayed for the
Caller ID name.
Stop
Programming (Cont’d)
➻ 10-12-01 : NTCPU Network Setup - IP Address
When using an IP connection from the NTCPU’s ethernet port, set up the IP address used to connect
from the PC to the Aspire system (Default: 172.16.0.10).
➻ 10-20-01 : LAN Setup for External Equipment
Define the TCP port (0-65535) when communicating to the SMDR (type 5).
➻ 10-21-02 : NTCPU Hardware Setup - Baud Rate for COM Port
If the SMDR connection is made using the COM port on the NTCPU, define the baud rate (0=4800,
1=9600, 2=19200, 3=38400).
➻ 14-01-06 : Basic Trunk Data Setup - SMDR Print Out
For each trunk, enter 1 if trunk’s calls should appear on SMDR report. Enter 0 if trunk’s calls should
not appear on SMDR report. See Program 35-01 and 35-02 for SMDR printout options (0=No print out,
1=Prints out).
➻ 15-01-03 : Basic Extension Data Setup - SMDR Printout
For each extension, enter 1 if extension’s calls should appear on SMDR report. Enter 0 if extension’s
calls should not appear on SMDR report.
➻ 15-02-19 : Multi-Line Telephone Basic Data Setup - CTA/CTU Data Communication Mode
Select ‘1’ for a printer/SMDR connection to the CTA or CTU adapter.
➻ 15-02-20 : Multi-Line Telephone Basic Data Setup - Baud Rate for CTA Port
Set the baud rate to be used by the CTA (0=4800, 1=9600, 2=19200). For USB connections, this setting
should not matter.
➻ 35-01-01 : SMDR Options - Output Port Type
Specify the type of connection used for SMDR (0=No setting, 1=COM(NTCPU), 2=USB (NTCPU),
3=LAN (NTCPU), 4=CTA/CTU). The baud rate for the COM port should be set in Program 10-21-02
4
or 15-02-20.
➻ 35-01-02 : SMDR Options - Output Destination Number
Specify the SMDR printer output port (CTA/CTU port number).This is the extension number which has
the CTA/CTU installed.
➻ 35-01-03 : SMDR Options - Header Language
Specify the language in which the SMDR header should be printed (0=English, 1=German, 2=French,
3=Italian, 4=Spanish).
➻ 35-01-04 : SMDR Options - Omit (Mask) Digits
Enter the number of digits (1-24) you want SMDR to block (i.e., “X” out). Enter 0 not to block any
digits.
➻ 35-01-05 : SMDR Options - Minimum Number of SMDR Digits
Enter the minimum number of digits a user must dial (1-24) before the system includes a call on the
SMDR report. Enter 0 to include all outgoing calls, regardless of the number of digits dialed.
➻ 35-01-06 : SMDR Options - Minimum Call Duration
Enter the minimum duration of a call (1-65535) that will print on the SMDR report. Enter 0 to have
calls of any duration print.
➻ 35-01-07 : SMDR Options - Minimum Ringing Time
Enter how long an unanswered call must ring (1-65535) before SMDR logs it as “No Answer”. Enter 0
to allow all “No Answer” calls to print.
➻ 35-01-08 : SMDR Options - SMDR Format
Do not change:
This option is added to allow an increased account code field from 8 to 16 when used in the U.K. This
allows 16 characters of the Caller ID name to be displayed. For the U.S., this option is set to "0" and
should remain at this setting as 16 characters are already provided for the account code field.
4 ➻
group. Enter 0 if this information should not be included.
35-02-12 : SMDR Output Options - DID Table Name Output
Determine if the DID table name should be displayed for incoming DID calls (0=Not Displayed,
1=Displayed).
➻ 35-02-13 : SMDR Output Options - CLI Output When DID to Trunk
Determine if the Caller ID should be displayed when the incoming DID number is transferred to an out-
going trunk (0=Not Displayed, 1=Displayed).
➻ 35-02-14 : SMDR Output Options - Date
Determine whether the date should be displayed on SMDR reports (0=not displayed, 1=displayed). This
option must be set to “0” if the trunk name is set to be displayed in Program 35-02-03.
➻ 35-02-15 : SMDR Output Options - CLI/DID Number Switching
Enter 0 to display the Caller ID number. Currently, option “1” for the DID number is not available.
With software 4.0E+, determine if the Caller ID number (0), DID number (1) or Caller ID name (2)
should be displayed in the SMDR output.
➻ 35-02-16 : SMDR Output Options - Print Trunk Name or Received Dialed Number
Determine how the SMDR should print incoming calls on ANI/DNIS or DID trunks. If set to (1), ANI/
DNIS trunks can print DNIS digits. For DID trunks, if the received number is not defined in Program
22-11-01, then no number will be printed. If set to (0) trunk names are printed instead (as assigned in
Program 14-01-01).
➻ 35-02-17 : SMDR Output Options - Print Account Code or Caller ID Name
Determine whether the Account Code (0) or Caller ID name (1) should appear in the SMDR record. By
default, the Account Code will be displayed.
Note: Program 35-01-08 must be set to "0" for this entry to be followed.
Related Features
PBX Compatibility
To use the PBX Call Reporting option, program system for behind PBX operation.
4
Traffic Reports
Traffic Management Reports and SMDR should not use the same CTA port.
Operation
Once installed and programmed, SMDR operation is automatic.
The system can print a report of the PCBs installed, the port assignments, and the port types. This information is sent to the
port defined in Program 90-13. This report includes:
● The version of system software
● PCB names
● Slot condition (working, blocked)
● Port assignment
● Port classification
Sample Report:
<< System Information >> 06/16/2003 13:57
Programming
➻ 90-13-01 : System Information Output - Output Port Type
Define the output port to be used as the output for system information report (0=no setting,
1=NTCPU COM port, 2=NTCPU USB port, 4=CTA/CTU adapter). Set the baud rate for the
COM port in Program 10-21-02.
➻ 90-13-02 : System Information Output - Destination Extension Number
If the output port type (90-13-01) is a CTA or CTU, enter the extension number with the CTA/
CTU connection.
➻ 90-13-03 : System Information Output - Output
Entering 1 will print the system report to the connected device.
Related Features
Traffic Reports
Traffic Reports log system call data providing several reports which can be used to determine
adequate system resources (receivers, channels, trunks, etc.).
The system has Telephony Applications Programming Interface (TAPI) capability. TAPI allows the user personalized control
of the telephone system from a desktop or laptop PC when used in conjunction with a TAPI-compliant application. The tele-
phone system and PC are connected by installing a CTA or CTU adapter on the telephone keyset, allowing the PC user to
access sophisticated communications services via the telephone lines.
In addition to a compatible system software version (1.07 or higher), you must also have:
● Aspire keyset telephone containing an RS-232-C CTA Adapter (P/N 0890058) / CTU Adapter (P/N 0890059)
with TAPI compliant firmware.
Refer to CTA Adapters (page 2-5) and CTU Adapters (page 2-21) for details on installing the adapters
and drivers required for TAPI 1.4 applications (stand-alone).
● PC Driver for the CTA: PC running Windows 98 Second Edition or higher
● PC Driver for the CTU: PC running Windows 98 Second Edition, Windows 2000, or Windows XP
● TAPI 2 applications (server-based) are possible with the Aspire S cabinet. With the Aspire M/L/XL, the Aspire
64-port basic CPU (P/N 0891002) with the Feature Upgrade PAL chip (P/N 0891039) or the Enhanced CPU (P/
N 0891038) is required. The 64-port Basic CPU with the basic factory-installed PAL chip does not support
TAPI 2.
● A TAPI compatible Windows application
4 TSPI_LINEGETDEVCAPS
TSPI_LINEGETEXTENSIONID
TSPI_LINEUNHOLD
TSPI_LINEUNPARK
TSPI_LINEGETID TSPI_PROVIDERCONFIG
TSPI_LINEGETLINEDEVSTATUS TSPI_PROVIDERINIT
TSPI_LINEGETNUMADDRESSIDS TSPI_PROVIDERINSTALL
TSPI_LINEHOLD TSPI_PROVIDERREMOVE
TSPI_LINEMAKECALL TSPI_PROVIDERSHUTDOWN
TSPI_LINENEGOTIATEEXTVERSION
Caller ID Data
When a CTA keyset answers a call, it provides the following data to the connected device:
If the incoming call data contains the Caller ID number . . .
NMBR=XXX (XXX = Caller ID number data)
If the incoming call data does not contain the Caller ID number . . .
NUMBR=
UNAVAILABLE, OUT OF AREA, or PRIVATE
● To place a call on Hold, the CTA provides the following data to the connected device:
ATD!
● When the data keyset becomes busy, the CTA provides the following data to the connected
device:
4
BUSY
➻ Program 15-02-20 : Multi-Line Telephone Basic Data Setup - Baud Rate for CTA Port
When using a CTA for the connection, set the baud rate to be used (0=4800, 1=9600, 2=19200).
Related Features
Caller ID
An extension’s Class of Service setting determines if additional options (Caller ID display, Caller
ID for second incoming call, etc.).
Computer Telephony Integration (CTI) Applications and Caller ID
The system provides Database Lookup through Caller ID and TAPI compatible third-party software
(such as Interact Commerce Corporations ACT!).
Data Communications
For more information on setting up the CTA Module, turn to this feature.
Headset Operation
In order to use the headset for some TAPI features (such as dialing out from MS Outlook), use the
Automatic Answer feature and press the Headset programmable function key (PGM 15-07 or SC
851: 05) to redirect the call to the headset and disable the hookswitch detection.
Operation
TAPI operation is automatic once programmed in the phone system and enabled in the PC’s TAPI application, unless
a headset is used.
Introduction
General Description
The NEC Infrontia Aspire has capability to use Computer Telephony Integration (CTI). It uses the Tele-
phony Application Programming Interface (TAPI) 2.1 protocol. To allow CTI, an Ethernet interface is
present on the NTCPU.
TAPI 2.1-based CTI realizes third party call control features such as ACD, Predictive Dialing, and Call Routing.
Requirements
The following are the minimum specifications required to use the CTI (TAPI 2.1) interface feature.
Telephone System
● Aspire S System
● Aspire M/L/XL with Feature Upgrade PAL chip or Enhanced CPU
CTI Server
* If the TAPI server is using Windows Server 2003, then the clients have to
be updated to either Windows XP SP2 or Windows 2000 SP4 with Rollup 1.
4 Memory
Drives
256MB or more
CD-ROM Drive
Note: The above are the specifications for TAPI set-up only. They may differ depending on the applications to
be installed.
The setup requires you to be logged onto the PC Server as a Local Administrator.
The server should be connected to the network via the TCP/IP Protocol (including WINS, DNS services),
and should include the appropriate number of Client Access Licenses.
The backup procedure and virus defenseare not part of the Aspire functionality and is the responsibility of
the customer.
* If the TAPI server is using Windows Server 2003, then the clients have to
be updated to either Windows XP SP2 or Windows 2000 SP4 with Rollup 1.
The setup requires you to be logged onto the PC Server as a Local Administrator.
The server should be connected to the network via the TCP/IP Protocol (including WINS, DNS services),
and should include the appropriate number of Client Access Licenses.
Requirements
The ethernet interface is located on the Aspire M/L/XL NTCPU or the Aspire S ENTU. This is a 10/100MB
RJ45 ethernet connection.
0893100 - 83a
CN15
LAN Connector
(CTI Interface)
4
The following basic commands must be set in the Aspire.
External Device 1
Installation Procedure
1. Double-click on the Setup.exe file. Click NEXT when you see the following welcome screen.
4
2. At the Aspire Telephony Service Provider Setup screen, select SERVER and click NEXT.
4. The Setup Address screen appears. Enter the IP address of the computer, the IP address for the NTCPU in the Aspire
4 system, and the TCP port number. Use period (“.”) between numbers. The PBX IP and TCP port numbers must
match the entry within the Aspire programming (Programs 10-12 and 10-20). (e.g. TAPI: 192.168.1.76, PBX IP:
192.168.1.75, TCP Port: 8181) When you enter the information, click NEXT.
6. The Register for Service Provider Setup screen appears. Select REGISTER and click NEXT to begin the
installation.
4
4 8. Verify the installation settings before clicking NEXT to complete the installation.
10. The TSP Installation is now complete. You should now proceed to the section for your operating system:
● Windows NT Server - page 4-136
4
● Windows 2000 Server - page 4-148
● Windows Server 2003 - page 4-163
General Description
The following section assumes you have installed the Aspire TSP. This section contains further information on con-
figuring TAPI 2.1 on Windows NT Server. The following information is provided:
Configuration
1. To verify that the Aspire TSP installed correctly and is using the proper settings double-click the
TELEPHONY icon from within the Control Panel (START ☞ SETTINGS ☞ CONTROL PANEL).
2. Click on the TELEPHONY DRIVERS tab to see that the Aspire TSP is installed.
4 5. By selecting a device and clicking DETAIL, the Call Mode can be set.
Note: To allow the call mode configuration, the device should be not be in use by any TAPI applica-
tion (i.e Arc ScreenPop).
6. To exit, click CANCEL then click OK until you have exited to the Control Panel. Double-click in the
upper left hand corner of the Control Panel to close the window.
An example of this is where users wish to connect to the telephony devices handled by the Aspire system. By
enabling the Telephony Server, it allows Clients to connect to the Aspire telephony devices. TAPI-based requests are
sent from the Client PC to the Aspire system via the Telephony Server.
The following example installs the Server using the Administrator account within the CTI domain
using the Administrator’s password Passw0rd.
4 3.
4.
Click on OK or press ENTER.
Usage is:
/S - Server Setup
/n - No Password
Note: The logon account you specify MUST be a member of the Administrator’s group on the server.
It must also be in the same domain as the server.
Client computers will be allocated telephone extensions based on their Domain Logon account. The only
exception to this is where by a Client computer is logged on using a Domain Administrator account, which
has permission to access all telephone extension(s).
Access permissions are configured using a Windows program called TCMAPP. This program allows the
Telephony administrator to assign telephone extension(s) to domain users.
3. TAPI Administration Application screen appears. From the taskbar, select USER ☞ ADD A USER
TO THIS TELEPHONY SERVER.
4
5. Click OK. The TAPI Administration Application screen will then display the selected user(s).
7. The Administration application will then update the user account with the devices to which he/she has
access.
9. On completion, select FILE ☞ EXIT. When the following message appears, click YES and save the
changes.
4
2. Locate the AspireTspStart service, and select STOP.
4. Copy the file n2iptsp.tsp to C:\WINNT\SYSTEM32 (assuming C:\WINNT is the location of the OS).
You will be asked if you are sure you want to replace, click YES.
4. When the Telephony Service stops, double-click the ADD/REMOVE PROGRAMS icon from the
Control Panel. Select AspireTSP from the INSTALL/UNINSTALL tab, then click ADD/REMOVE.
6. Click the OK button at the end of the uninstall program. The uninstall of the Aspire TSP is complete.
General Description
The following section assumes you have installed the Aspire TSP. This section contains further information on con-
figuring TAPI2.1 on a Windows 2000 Server.
Configuration
1. To verify that the Aspire TSP is installed correctly and is using the proper settings, double-click the
PHONE AND MODEMS icon from within the Control Panel (START ☞ SETTINGS ☞ CONTROL
PANEL).
2. Click on the ADVANCED tab to see that the Aspire TSP is installed.
4
4. Click on the DEVICE tab to confirm the system extension ports’ status. You cannot change any data on
this screen.
Note: To allow the call mode configuration, the device should be not be in use by any TAPI applica-
tion (i.e Arc ScreenPop).
4 6. To exit, click CANCEL then click OK until you have exited to the Control Panel. Double-click in the
upper left hand corner of the Control Panel to close the window.
An example of this is where users wish to connect to the telephony devices handled by the Aspire system. By
enabling the Telephony Server, it allows Clients to connect to the Aspire telephony devices. TAPI-based requests are
sent from the Client PC to the Aspire system via the Telephony Server.
Note: Enabling the TAPI Server requires you to specify a Domain User account which exists in the same Domain to
which the TAPI Server is a member. This account must also be a member of the TAPI Server’s Local Administrator
group.
We strongly recommend using a Domain User account created specifically for use with the Telephony Service, which
contains a password which is unchangeable and does not expire.
3. Select ADD and specify the appropriate Domain in the LOOK IN drop-down list. 4
4. Specify the appropriate Domain User account and click ADD. Click OK to accept the account.
8. The SELECT USER window will appear. From this list, select the account used in Step 4.
4
9. Enter the password associated with the selected user account.
The following example installs the Server using the TAPI account within the necinfrontia domain.
11. The following message appears, confirming that the Telephony Service must be restarted. Click NO.
Note: Restarting the Telephony Service will drop any existing connection to the Aspire system.
12. The Server must now be shut down and restarted before proceeding.
User Administration
By default, the Client computers will not be able to access any extensions. By enabling the TAPI Server, you are able
to permit Domain users to access their telephone extension(s). Extensions available to the TAPI Server are authenti-
cated using Windows 2000 access permissions.
Client computers will be allocated telephone extensions based on their Domain Logon account. The only exception to
this is where by a Client computer is logged on using a Domain Administrator account, which has permission to
access all telephone extension(s).
Access permissions are configured using the Telephony snap-in within Windows Computer Management. This
allows the Telephony administrator to assign telephone extension(s) to domain users.
4. Click ADD - the Edit Users screen appears. Specify the appropriate domain user account and click OK
to accept.
5. The Edit Users screen reappears with confirmation of selected users. Click OK to accept.
4. Copy the file n2iptsp.tsp to C:\WINNT\SYSTEM32 (assuming C:\WINNT is the location of the OS).
You will be asked if you are sure you want to replace - click YES. Restart the computer.
4
3. Locate the Telephony service and select STOP.
4 5. The verification message follows, click the YES button to proceed with uninstall.
6. Click the OK button at the end of the uninstall program. The uninstall of the Aspire TSP is complete.
General Description
The following section assumes you have installed the Aspire TSP. This section contains further information on con-
figuring TAPI2.1 on Windows 2000 Server.
Configuration
1. To verify that the Aspire TSP installed correctly and is using the proper settings, double-click the
PHONE AND MODEMS icon from within the Control Panel (START ☞ SETTINGS ☞ CONTROL
PANEL).
2. Click on the ADVANCED tab to see that the Aspire TSP is installed.
4 4. Click on the DEVICE tab to confirm the system extension ports’ status. You cannot change any data on
this screen.
Note: To allow configuration of Call mode the device should be not be in use by any TAPI applica-
tion (i.e Arc ScreenPop)
6. To exit, click CANCEL then click OK until you have exited to the Control Panel. Double-click in the
upper left hand corner of the Control Panel to close the window.
4
An example of this is where users wish to connect to the telephony devices handled by the Aspire system. By
enabling the Telephony Server, it allows Clients to connect to the Aspire telephony devices. TAPI-based requests are
sent from the Client PC to the Aspire system via the Telephony Server.
Note: Enabling the TAPI Server requires you to specify a Domain User account which exists in the same Domain to
which the TAPI Server is a member. This account must also be a member of the TAPI Server’s Local Administrator
group.
We strongly recommend using a Domain User account created specifically for use with the Telephony Service, which
contains a password which is unchangeable and does not expire.
3. Select ADD and specify the appropriate location (i.e., Entire Directory).
4. Specify the appropriate User account and click CHECK NAMES to confirm. Click OK to accept the
4 account.
5. Click APPLY and then OK to accept the selected account into the TAPI Server Local Administrator
Group. You are returned to the Computer Management window.
7. In the Telephony properties, tick the box which says ENABLE TELEPHONY SERVER. Below in
the USER NAME field, click the CHOOSE USER button.
8. The Select User window will appear. From this list select the account used in Step 4.
The following example installs the Server using the TAPI account within the necinfrontia domain.
11. The following message appears confirming that the Telephony Service must be restarted. Click NO.
Note: Restarting the Telephony Service will drop any existing connection to the Aspire system.
12. The Server must now be shut down and restarted before proceeding.
Client computers will be allocated telephone extensions based on their Domain Logon account. The only exception to
this is where by a Client computer is logged on using a Domain Administrator account, which has permission to
access all telephone extension(s).
Access permissions are configured using the Telephony snap-in within Windows Computer Management. This
allows the Telephony administrator to assign telephone extension(s) to domain users.
4
2. Go to SERVICES AND APPLICATIONS ☞ TELEPHONY ☞ ASPIRE TELEPHONY SERVICE
PROVIDER. You should see a list of all connected Aspire telephone extensions.
4. Select ADD and specify the appropriate Location (i.e., Entire Directory).
5. Specify the appropriate User account and click CHECK NAMES to confirm. Click OK to accept the
account.
4
6. The Edit Users screen reappears with confirmation of selected users. Click OK to accept.
7. The selected user should now be associated with the extension you assigned.
4. Copy the file n2iptsp.tsp to C:\WINNT\SYSTEM32 (assuming C:\WINNT is the location of the OS).
You will be asked if you are sure you want to replace - click YES. Restart the computer.
4
3. Locate the Telephony service and select STOP.
4 5. The verification message follows, click the YES button to proceed with uninstall.
6. Click the OK button at the end of the uninstall program. The uninstall of the Aspire TSP is complete.
4
2. After executing the command, the following window should be received.
TCMSETUP /C /D
2. After executing the command, you will receive the following message. Click on OK.
Traffic Reports
Traffic Reports
The system provides the ability to send data to a PC connected to the Aspire. The telephone call traffic data for each extension
is captured for use with the SMDR feature (refer to SMDR (page 4-101) for more details). Traffic Reports require connection
to the serial or USB connector on the NTCPU or a CTA or CTU adapter. Additional programming and a customer-provided
printer is also required. Refer to NTCPU Connection and Driver Installation (page 3-1), Installing the CTA Adapter
(page 2-5) or Installing the CTU Adapter (page 2-21) for more on setting up and connecting to the Aspire system.
Call Traffic
The total of outgoing call frequency, outgoing call duration, call charge, incoming call frequency, answer frequency,
incoming call duration, ringing duration for each line and extension, and abandon call frequency for each line is
logged. The total of incoming calls, answer frequency, call duration for each line and extension, and abandon call fre-
quency of each line is logged and the data is outputted to the PC. The system totals the hour, day, week, and month for
each terminal and trunk number. This information is used by the SMDR feature. The extension which is totalled is
determined by system programming. The system outputs this data to the PC for the total period.
Traffic Total Report - Sample Report
Terminal OTG Duration Cost ICM Answer Duration Ringing Abandon
301 54 01:45:14 720 326 115 02:11:52 00:09:36
4
301 92 02:37:22 1855 84 84 01:58:31 00:04:19
LINE001 -- -- -- 79 71 01:05:26 -- 8
Definitions
Terminal Terminal Number/Called Party Number (maximum 24 digits)
OTG Outgoing Call Frequency/number of outgoing calls (maximum 65535 calls)
Duration Call Duration for an Outgoing Call
Cost Call Charge
ICM Incoming Call Frequency/number of incoming calls (maximum 65535 calls)
Answer Answer Frequency (maximum 65535 calls)
Duration Call Duration for an Incoming Call
Ringing Ringing Duration
Abandon Number of Abandoned Calls (maximum 65535 calls)
Conditions
● The SMDR call buffer stores 500 calls. The buffer stores calls when the SMDR device is unavailable. When
the buffer fills, the oldest record is deleted to allow the new record to be saved.
● If connected to the output device, the reports will print hourly. If not connected and the data is not out-
putted at the end of the hour, the traffic data will be overwritten by new incoming data.
● The traffic data is lost if a power failure occurs.
Default Setting
Disabled.
Programming
➻ 90-20-01 : Traffic Report Data Setup - Call Traffic Output
Determine whether or not the Call Traffic Output should be measured (0=no, 1=yes).
➻ 90-21-01 : Traffic Report Output
Define the output port to be used for the traffic reports (0=no setting, 1=NTCPU COM port, 2=NTCPU
USB port). The reports will print hourly when connected to the output device.
Ultra CallAnalyst
Ultra CallAnalyst
Ultra CallAnalyst is an easy to use, graphically oriented software package that allows you to monitor and analyze phone calls,
understand phone usage and cut costs. CallAnalyst tracks both incoming and outgoing calls accurately as well as the date and
time of each call. If you need to track the incoming phone call with name and/or telephone numbers, CallAnalyst requires
Caller ID services from the local phone company.
Ultra CallAnalyst increases productivity, facilitates billing and helps detect toll fraud and phone abuse. It also has powerful
tabular (text) and graphical report generating capabilities. Reports include extension/line summaries, date/time and department
summaries, longest/most expensive calls, most frequently called numbers, and other commonly used summaries.
These reports can be used to analyze your telephone as a critical business communication tool, thereby, improving its effec-
tiveness and helping you to reduce your telephone related costs. CallAnalyst keeps track of:
● The date and time calls were made or received.
● The duration of each call.
● Which extension made or received the call.
● The CID/ANI, DNIS of the caller.
● The trunk or line numbers which handled the call.
● Account codes and authorization codes used for the call.
For CallAnalyst to receive call information from your telephone system, you must connect a serial cable between the
SMDR port on your phone system and a serial port on your PC. Or, with CallAnalyst software 6.0 or higher, you can
also connect using an IP network connection. CallAnalyst uses the Call Data Manager (CDM) communications pro-
gram to read the call information from the PC.
The following steps must be taken in order for CDM to track your calls:
● Connect an RS-232C cable from the serial port on the PC to the phone system's SMDR port. Or, if
available, connect to the TCP/IP network port on the phone system to the PC or to the USB connector
on a CTU Adapter (The NTCPU’s USB connector cannot be used - for a USB connection, a CTU must
be used as the CallAnalyst does not allow the port selection.). The SMDR connection is made to the
For details on programming the SMDR options, refer to SMDR - Programming (page 4-110).
Programming Notes:
● If the system is programmed to display the date (Program 35-02-14=1), the date will be dis-
played regardless of the setting for display of trunk name (Program 35-02-03) and only the
trunk number is printed. For example, if trunk port “049” has a trunk name of “PRI Ch1”, if
Program 35-02-03 = 0 (name) and 35-02-14 = 1 (display date), then SMDR will show “8/19
049.” However, if Program 35-02-14 = 0 (date not displayed), the SMDR will show “PRI
Ch1”.
● For proper handling of DNIS calls, the name field (Program 22-11-03) must be the same as
the received DNIS digits (Program 22-11-01). If this is not set, CallAnalyst will not be able to
track transferred calls since the system displays the DNIS number when a call is received and
displays the DNIS name for transferred calls. This setting has no impact on outgoing calls,
4 ●
which display the trunk name instead of the DNIS name.
With Aspire software 4.0E+, Caller ID name can be displayed in SMDR records. Program 35-
02-17 must be set to “0” and Program 35-02-18 set to “1”.
CTA/CTU Adapter:
➻ 15-02-19 : Multi-Line Telephone Basic Data Setup - CTA/CTU Data Communication Mode
Change the system programming to match the CTA adapter's dip switch settings.
➻ 15-02-20 : Multi-Line Telephone Basic Data Setup - Baud Rate for CTA Port
Select the baud rate to be used by the CTA Adapter (0=4800, 1=9600, 2=19200).
LAN Connection:
➻ 10-12-01 : NTCPU Network Setup - IP Address
When using an IP connection, set up the IP address used to connect from the CallAnalyst PC to the
Aspire system (Default: 172.16.0.10).
➻ 10-20-01 : LAN Setup for External Equipment
When using an IP connection, define the TCP port used for communicating to the CallAnalyst
(External Device 5=SMDR, Entries: 0-65535). This entry must match the entry made in the CDM
setup with the CallAnalyst program.
Serial Connection:
➻ 10-21-02 : NTCPU Hardware Setup - Baud Rate for COM Port
If the SMDR connection is made using the COM port on the NTCPU, define the baud rate (0=4800,
1=9600, 2=19200, 3=38400).
CallAnalyst Enterprise Server is a network version of Ultra CallAnalyst used for collecting and generating telephone usage
reports for multiple telephone systems on a network. It is a scalable call accounting solution for the small to mid-size business.
CallAnalyst Enterprise Server is an easy to use, graphically oriented software package that allows you to monitor and analyze
phone calls, understand telephone usage and cut costs. Ultra CallAnalyst tracks both incoming and outgoing calls accurately.
The application supports connection of heterogenerous (different type) telephone systems as well as the connected interfaces
(serial or TCP/IP) and supports real time consolidation and reporting of call accounting data. If you need to track the incoming
telephone traffic with calling name and/or telephone numbers, Ultra CallAnalyst requires Caller ID services from the local
phone company.
Ultra CallAnalyst increases productivity, facilitates billing and helps detect toll fraud and phone abuse. It also has powerful
tabular (text) and graphical report generating capabilities. Reports include extension/line summaries, date/time and department
summaries, longest/most expensive calls, most frequently called numbers, and other commonly used summaries. Ultra Cal-
lAnalyst also has the ability to automatically generate and Email reports to managers on set schedules. These reports can be
used to analyze your telephone as a critical business communication tool, thereby, improving its effectiveness and helping you
to reduce your telephone related costs. Ultra CallAnalyst keeps track of:
• The date and time calls were made or received. • The CID/ANI, DNIS of the caller.
• The duration of each call. • The trunk or line numbers which handled the call.
• Which extension made or received the call. • Account codes and authorization codes used for the call.
Software
• Windows NT 4.0 (workstation or server) w/SP6, 2000 Professional w/SP3, XP Professional w/ SP1 or
2003 Server
• MS SQL Server 2000 or MSDE (Microsoft Database Engine) for the database (MSDE is included on
the application CD)
• Microsoft Internet Explorer 5.0 or higher (Internet Explorer is included on the application CD)
Software
• Windows NT 4.0 w/ SP6, or 2000 Professional w/ SP3, XP Professional w/ SP1 or 2003 Server
• Microsoft Internet Explorer 5.0 or higher (Internet Explorer is included on the application CD)
Prerequisites
The instructions to perform installation assume you have the following settings:
1. The location is set to United States. To set the location to United States:
a. Click Start and point to Settings.
b. Select Control Panel.
c. In the Control Panel window, double-click Regional Options.
d. In the General tab, select English (United States) from the Your locale (location)
drop down.
e. Click OK.
2. The currency symbol is set to Dollar ($). To set the currency to Dollar:
a. Click Start and point to Settings.
b. Select Control Panel.
c. In the Control Panel window, double click Regional Options.
d. In the Currency tab, select $ from the Currency symbol drop down.
e. Click OK.
3. The date format is set to MM/DD/YYYY format. To set the date format to MM/DD/YYYY
format:
a. Click Start and point to Settings.
b. Select Control Panel.
c. In the Control Panel window, double click Regional Options.
d. In the Date tab, select MM/dd/yyyy from the Short date format drop down.
e. Click OK.
4
Steps for Installing the Software
Due to the dependency of the programs with each other, they should be installed in the following sequence:
● On the Application Server for the CallAnalyst Enterprise Server:
1. Microsoft Internet Explorer 5.0 (or higher) must be installed first if not already installed.
2. A database server must be installed. If the CES database will be used on the Microsoft SQL
Server, then first verify that it is installed and running. The MS SQL Server can be on the CES
application server or on a server on the network that is accessible from the CES application
server. If using MSDE (Microsoft Database Engine), then it must be installed on the applica-
tion server. (MSDE is included on the application CD).
3. Install Ultra CallAnalyst.
● On the Remote Workstations for MSR (Multi Site Reporting) Thin Client Module:
1. Microsoft Internet Explorer 5.0 (or higher) must be installed first if not already installed.
2. MSR (Multi-Site Reporting) Thin Client should then be installed on any workstation that is
used to collect call data from a telephone system serial port and forward it on the IP network to
the central application server. The MSR Thin Client loaded on the workstation can also store
data locally on the PC when the IP connection is down. When connectivity is recovered it will
transmit the stored data to the central application server as normal.
After loading the NEC CallAnalyst Enterprise Server CD-ROM into your CD-ROM drive, choose from one of the
five available options from the Installation screen.
1. CES (CallAnalyst Enterprise Server) Installation - For installing components of CES (listed
below):
a. Ultra CallAnalyst - software for analyzing and generating reports from captured call data.
For installation details, see “Install CallAnalyst Enterprise Server” in the Installation and
Configuration Guide on the CES application CD.
b. Ultra CallAnalyst Network Client – Software is installed on a workstation for running Ultra
CallAnalyst from another network location. The number of Network Client Licenses
installed on CallAnalyst Server determines the number of workstations that can simulta-
neously access Ultra CallAnalyst. The Network Client software may be installed on as
many computers as you wish. For further details refer to “Install CallAnalyst Network Cli-
ent” in the Installation and Configuration Guide on the CES application CD.
c. CallAlert – Software installed on a workstation with TCP/IP access to the CallAnalyst
Enterprise Server so it can monitor call records and send alerts when telephone abuse is
detected. For installation details, see “Install CallAlert” in the Installation and Configuration
Guide on the CES application CD.
2. MSR (Multi-Site Reporting) Thin Client Installation - This software is installed on a computer at a
remote site to packetize the SMDR data and send it over an IP network. This software is only needed if
the telephone system is not able to send SMDR data to an IP network directly. Refer to “Install Multi-
4 Site Reporting Thin Client” on the CES application CD for installation details.
3. MSDE (Microsoft Database Engine) Installation - This is installed on the CallAnalyst Enterprise
Server if Microsoft SQL Server is NOT installed on the network. Microsoft Internet Explorer 5.0 (or
higher) must be installed before MSDE is installed. See the “Installation and Configuration Guide” on
the CES application CD for more details.
SQL Server's security mode is stored as the LoginMode value in the Windows NT Registry
as part of the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\
MSSQLServer. You should change the value of LoginMode to 2. After changing the value,
restart the MSSQLSERVER service.
Important Information: If you install the MSDE on a Windows NT machine, then the
machine restarts after successful completion of the installation. In case of any error, see
MSDEInstall.log stored in the temporary directory.
4. Internet Explorer 5.0 - MSDE and the CallAnalyst Help file require Microsoft Internet Explorer 5.0
or later to be installed.
5. Adobe Acrobat Reader 5.0 - Adobe Acrobat Reader must be available for viewing the Ultra CallAna-
lyst manuals.
For more information about installing each software package, refer to the following installation information or to the
installation documentation provided on the CES application CD.
6. Click Install. This takes you to the Ultra Call Analyst Enterprise Server Enterprise Server
Installation wizard.
4
9. In the Select Destination Directory, click the Browse button to select the destination folder
and click Next. The Backup Replaced Files window appears as shown below:
12. Click the Browse button to select the destination directory and click Next. The Ready to
Install window appears.
13. Click Next to begin installation.
The License agreement window appears. Click OK to accept the agreement and continue
4
with the installation.
Ultra Call Analyst Enterprise Server installation starts. All the Data Access Components are
installed along with the other required files. The Installing CallAnalyst Security window
appears.
14. Click OK to install the CrypKey Software Security Service for network. This helps you
generate license key and also helps you to protect the Ultra Call Analyst Enterprise Server
application and its data from harm or loss. This is implemented especially so that only the
authorized user can gain access to the Ultra Call Analyst Enterprise Server application and
nobody can tamper with the license key. The installer also provides you with an option to setup
Ultra Call Analyst Enterprise Server database.
Important Information:
● You cannot connect to the database, if you are not a valid user and have the authorized net-
work connection.
● The machine where you run the database installer should have the SQL Server 2000 client
installed.
Using Ultra Call Analyst Enterprise Server’s database wizard, you can either:
● Create a new database or
● Use an existing database
Installation of the database creates all Ultra Call Analyst Enterprise Server related database
objects and load the sample data or only the data necessary for bootstrapping, as specified by
you.
Important Information:
We recommend that you do not overwrite any database associated with the previous version of
Ultra Call Analyst Enterprise Server.
4 16. Enter the necessary login ID and the Password. Only SQL Server authentication is supported
currently. Please make sure that the database user has the ‘dbo’ role.
17. Click Next.
22. Click Next. Ultra Call Analyst Enterprise Server Database installation starts. The installer
installs the database accordingly:
● Creates the following schema objects of the SQL Server:
- Database Tables
- Database Views
- Database Triggers
● Executes some pre-data SQLs.
● Imports the Bootstrap data, required for starting the Ultra Call Analyst Enterprise Server.
● Executes post-data SQLs.
The status of the installation is displayed in the progress bar.
23. Once the Ultra Call Analyst Enterprise Server Database installation is completed, click Done
to continue with the Ultra Call Analyst Enterprise Server installation.
The installer also allows you to configure the directory for database archive and restore pro-
cess. Once configured, this directory is centrally located, thus available to the Ultra Call Ana-
lyst Enterprise Server as well as the SQL Server (ideally located on different machine).
25. Click Save to continue with the Ultra Call Analyst Enterprise Server installation.
If you do not want to configure the directory during installation, click Cancel. For details
on how to configure the directory at a later stage, see “Configure the Archive and Restore
Directory”. The Important Information window appears.
26. Go through the information and click OK. The Installation Completed window appears.
27. Click Finish to complete the installation.
Important Information:
4 1. In case the Ultra Call Analyst Enterprise Server database is not installed properly due to some
reason, you can re-install the database as follows:
a. Click the Windows Start button, point to Programs and then click the Ultra Call Analyst
Enterprise Server shortcut folder.
b. Point to Tools and click Install CA Database.
c. Once you have re-installed the Ultra Call Analyst Enterprise Server database, configure the
database as follows:
- Click the Windows Start button, point to Programs and then click the Ultra Call Ana-
lyst Enterprise Server shortcut folder.
- Point to Tools and select Configure CA Database.
2. In case you want to change the directory for database archive and restore process due to some
reason, you can re-configure the directory as follows:
a. Click the Windows Start button, point to Programs and then click the Ultra Call Analyst
Enterprise Server shortcut folder.
b. Point to Tools and select Configure Archive Restore Directory.
Install CallAlert
CallAlert installation allows you to install CallAlert on any PC on the (LAN) network with TCP/IP enabled. CallAlert
helps you monitor phone abuse. Call Data Manager (CDM) communicates with the CallAlert and generates alarms
when certain conditions are met. CallAlert can also be installed on the same PC as the CallAnalyst server.
You can install CallAlert on more than one machine for Ultra CallAnalyst Enterprise Server CES Version.
This takes you to the CallAlert Installation wizard, similar to the server installation. For
details see To install CallAnalyst Enterprise Server: (page 4-187).
The wizard also prompts you to load the CALL ALARM at the time of System boot. Call
Alarm is a CallAlert component, which monitors the phone system and triggers alarms as
defined by the CallAlert.
If you are installing the CallAlert on a machine (client machine) other than the server (where
the Ultra CallAnalyst Enterprise Server is installed), the installation prompts you to configure
the CallAlert Database.
6. Enter the Ultra CallAnalyst Enterprise Server database information to connect to the CallAlert
4 remotely. After you have entered the required information, click Test Configuration. On suc-
cessful test, click Save. The Data Source Network (DSN) is created automatically.
Important Information: You cannot install the Ultra CallAnalyst Enterprise Server Network Client on the same
machine, where the Ultra CallAnalyst Enterprise Server is installed. If you try to install the Ultra CallAnalyst Enter-
prise Server Network Client on the same machine, the Existing Installation window appears. Click Finish to exit
the installation.
4
To perform Ultra CallAnalyst Enterprise Server Network installation:
1. Close all applications running on your system.
2. Load the NEC CallAnalyst Enterprise Server CD-ROM into your CD-ROM drive.
3. The Setup program will start automatically. If it does not start, follow the next step, otherwise
skip the next step.
4. On the Windows Desktop, choose Start ☞ Run; enter F:\Install.exe (where F: is your CD-
ROM drive) and press Enter.
The Network Client connects to a Ultra CallAnalyst Enterprise Server installation via a
mapped network drive. The CallAnalyst Server installation synchronizes call records with the
4
Network Client allowing you to remotely administer the Server. The installation also prompts
you to configure the Ultra CallAnalyst Enterprise Server Network Client Database.
7. Enter the Ultra CallAnalyst Enterprise Server database information to connect to the Network
Client remotely. After you have entered the required information, click Test Configuration.
On successful test, click Save. The Data Source Network (DSN) is created automatically.
6. In the Select the Installer window, select the MSR Thin Client Installation.
7. Click Install. This takes you to the CES MSR Thin Client Installation wizard.
8. In the Welcome window, click Next.
4
The Backup Replaced Files window appears as shown below:
10. Select the Yes option (recommended) to backup all the files replaced during installation and
click Next. The Start Installation window appears.
11. Click Next to begin installation. The Installation Complete window appears.
12. Click Finish to complete the installation. Once MSR Thin Client is installed on your system,
the MSRCDM receives the call record data from the MSR Thin Client and dumps them into
the Data Manager.
Acquiring a License
After the software is installed, a License Site Key must be entered. Access to CallAnalyst Enterprise Server is con-
trolled by licenses. It is these licenses that determine the number of sites and extensions that a user is allowed to
access. The license of all applications are installed on the computer where CallAnalyst Enterprise Server is installed.
Network Client software will not be able to access Ultra CallAnalyst unless the proper license has been installed on
the PC running the CES.
The License and associated Site Key are valuable. This unlocks the software. Be very careful when working with
License and Site Keys. If procedures are not followed, the Site Key can be damaged or erased. There are procedures
for moving the software and license from one drive or computer to another. If it becomes necessary to re-issue a new
Site Key, you will be required to produce proof of purchase and you may be charged a processing fee.
4 5.
asked questions about the installation site and be given a Site Key. Write this number down for
future reference.
Enter the Site Key information in the space provided in the CallAnalyst License Configura-
tion dialog box.
6. Once entered click the Validate button.
A message will be displayed to indicate that the software is now ready to use.
7. After installation, start Ultra CallAnalyst by choosing Start ☞ Programs ☞ NEC CallAna-
lyst ☞ CallAnalyst.
Refer to the Installation and Configuration Guide for information about updating the software with additional site or
extension licenses or for additional network clients.
Transferring a License
If you move CallAnalyst Enterprise Server to a different directory or to a different computer, then you need to transfer
the license. The process for transferring a license must be followed as described or the license may be destroyed. Do
not uninstall Ultra CallAnalyst Enterprise Server on the licensed computer until after this transfer process is completed.
For more information about license transfer including handling of transfers for special cases, refer to the Installation
and Ultra CallAnalyst User Guides on the CES application CD or on-line help.
4
If the COM port is properly configured and the phone system is configured to generate call records then the following
tests will show some kind of ASCII output - recognizable call records (if the port settings are correct) or gibberish
(random ASCII characters, if the port settings are incorrect). If no output
appears during the testing, then refer to the Troubleshooting section.
Manual Testing
1. Click Configure Port to set the COM port settings as desired.
2. Click Apply and Test Configuration and follow the directions that appear in the Call Data
Output Screen. You would be instructed to make a test phone call on your phone system to see
if the COM port settings are correct. If they are, then you will see lines of alphanumeric char-
acters (gibberish characters *&%#@) that clearly represent call records.
If you do not have clear call records then try using the guided process.
When you are able to see the call records, you are done.
3. Click Save Current Configuration for use in CDM and click Exit.
● In the Call Data Source pane, select the call data source. External DB, Web (URL) and
Log files are used to store the call information after the call is over. Comm Port or TCP/IP
are used to store real time data (records the call, while it is in process).
To configure the serial port using the configuration tool, click Configure. For details
see Configure and Test the Serial Port (page 4-202).
● External DB settings:
❍ In the Data Source DSN box, type the data source name to connect to an existing
database.
❍ In the Data Request Interval (max. 7 day equivalent) box, type the time interval
(in minutes) after which the call data should be retrieved from this data source and
stored.
4 ❍ In the Data Request Interval (max. 7 day equivalent) box, type the time interval
(in minutes) after which the call data should be retrieved from this site and stored.
● TCP/IP settings:
❍ In the IP Address box, type the IP address of the MSR Thin Client.
❍ In the Port Number box, type the port number to which you want to connect the
MSR Thin Client.
You can also configure your local and toll free area codes as follows:
❍ Local Area Code: Enter your local area code (such as 503). This area code is tagged
with all the local calls and is useful in generating reports.
❍ Other Toll Free Area Codes: Enter your toll free area codes (such as 503). This
code is tagged with all toll free or long distance calls and useful in generating
reports.
● Route Numbers for Local Calls: Enter the route numbers that will be considered in the
local calls for billing purposes. You can add or delete the route numbers, if required.
● Route Numbers for Long Distance Calls: Enter the route numbers that will be consid-
ered in the long distance calls for billing purposes. You can add or delete codes, if
required.
● In the Common Parameters pane, select the following:
❍ Local DM IP Address: The IP address of the machine, where the Data Manager
(DM) is running. The DM and the MSRCDM must be running on the same machine.
The IP address should be 127.0.0.1.
❍ Receive UDP Port Number: Type the User Datagram Protocol (UDP) port number
of the DM, where it will receive the call data records from MSRCDM. You can use
port number between 2000 and 65536, except 15000, 15001 and 15002. The value 0
is invalid and values 15000, 15001 and 15002 are reserved port numbers.
This port is used mainly for receiving data from local computer. It cannot receive data
from remote locations.
4
❍ Receive TCP Port Number: Type the Transfer Control Protocol (TCP) port number
of the DM, where it will receive the call data records from MSRCDM. You can use
port number between 2000 and 65536, except 15000, 15001 and 15002. The value 0
is invalid and values 15000, 15001 and 15002 are reserved port numbers.
The port is mainly used for receiving data mainly from remote locations. The value
for this port number should not be same as UDP Port number.
❍ Send CDR to remote DM? : Select this option, if you want your local DM to trans-
mit the Call Data Records to the remote DM. Once you select this option, type the
remote DM IP address and the port number in the respective boxes.
The Configure Ultra CallAnalyst Enterprise Server Database appears as shown below:
Whenever the license limit (i.e., license for number of extensions) is violated, the process MSAdvPrs.exe sends an
email to this email address.
Important Information: The process MSAdvPrs.exe can send the mail only when the Administrator is logged into
the system. The mails cannot be sent if the system restarts automatically due to a power failure and the Administrator
is logged out.
3.
4.
In the Administrator Email box, type the mail address of the Administrator.
Click Save.
4
3. In the Archive/Restore directory box, type the directory name along with the machine name
4 4.
(that resides on the network) and the path. For example, \\M1\C$\Temp, where Temp is the
directory and M1 is the machine name.
Click Save.
The Temp directory created is accessible to the CallAnalyst Enterprise Server and the
SQL Server residing on the network.
4
● Comm Port Details: Allows you to configure the serial communications port.
❍ In the Port pane, select the serial port to which you want to connect the MSR Thin
Client.
❍ In the Communication Settings pane, do the following:
• From the Baud drop down, select the transmission rate in bits per second
• From the Parity drop down, select how the system should use the parity bit to select
the errors. The default value is Even. All computers do not support Mark and
Space.
• From the Data Bits drop down, select the number of data bits in a character. The
valid values for data bits are in the range 5 through 8.
• From the Stop Bits drop down, select the number of stop bits that define the end of
a character. The valid values for stop bits are 1, 1.5 and 2. If the baud rate is 110,
then the default value is 2; otherwise the default value is 1. All computers do not
support the value 1.5.
❍ TCP/IP Details: Allows you to set the TCP/IP Port.
• In the Port Number box, type the port number to which you want to connect the
MSR Thin Client.
3. After you have entered all the details, click Save.
Note: If you want to configure the serial port using the configuration tool of CallAnalyst
Enterprise Server, click Configure. For details see Configure and Test the Serial Port
(page 4-202).
4 3. In the Domain/Workgroup Name box, enter you domain or the workgroup name. These
names are stored under the Network Identification tab of “My Computer” properties.
4. In the User Name box, enter your Windows user name.
5. In the Password box, enter your password.
Note: Whenever you open the Configure Service Parameters window, the password
remains blank. You need to confirm your password.
6. Click Save.
After installing Ultra CallAnalyst Enterprise Server, you may or may not have a trial license for an introductory
period. You must obtain a permanent license from TriVium Systems.
To acquire a license
1. Start CallAnalyst.
2. Press the Enter key on your keyboard within 3 seconds.
If Ultra CallAnalyst Enterprise Server starts instead of the license configuration window, then
it means you did not press the Enter key quickly enough. You must close CallAnalyst and
restart from step 1 again.
3. Contact your Ultra CallAnalyst Enterprise Server vendor with your Site Code information to
receive your license. Enter the Site Key given by the vendor to license Ultra CallAnalyst
Enterprise Server.
4. If you re-install Ultra CallAnalyst Enterprise Server in a different directory or on a different
computer, then you need to transfer your license.
The Process Status pane appears and you can view the activity of each site. To view more detail
information on each site:
● Select the row that contains the site code and double click.
The log file opens and you can view all the activities performed on the site.
Uninstall CallAnalyst
When removing CallAnalyst from your system, it is important that you first close the application and
uninstall the scheduler and other services, if installed.
Remove CallAnalyst
This instruction completely remove all CallAnalyst Enterprise Server programs from your computer.
Remove CallAlert
This instruction completely remove the CallAlert programs from your computer.
Section 5:
Troubleshooting
Troubleshooting
General
● The product (CTA adapter, CTU adapter, or CD-ROM) is defective.
Cause Solution
5
• Problems during manufacture. • Contact your distributor/dealer.
• Damage during use. • Contact your distributor/dealer.
Cause Solution
• MS-DOS or another Windows • Close all MS-DOS and Windows applications (except
application is still running. the program manager), and run the setup program
again.
• Defective CD-ROM. • Contact your distributor/dealer.
Cause Solution
CTA
● Dial-up connection to the Internet is no longer possible after a CTI application has been installed.
Cause Solution
• The same COM port is used by the CTA • The same COM port cannot be used. Uninstall one of
driver and the dial-up connection. the two.
● The CTA driver does not operate correctly after the operating system is updated.
Cause Solution
• The CTA driver settings are lost when • Refer to CTA Driver Installation on page 2-6 and rein-
the operating system is updated. stall the CTA driver.
Cause Solution
• The COM port in the PC BIOS is set • Set the COM port in the PC BIOS to ENABLED
to DISABLED. (refer to the PC manual).
• The serial cable is not connected. • Connect the PC and CTA adapter with serial cable.
• The serial cable is cross cable. • Use a 9 pin-9 pin straight cable.
• The PC is in the power saving mode. • Clear the power saving mode on the PC (refer to the
5
PC manual).
• The remote access service is operating • Set the COM port used with the remote access service
with the COM port connected to the to a port other than the COM port connected to the
CTA adapter. CTA adapter.
CTU
● USB cable has been connected before the CTU driver is installed.
Cause Solution
Cause Solution
• The USB cable is not connected • Check that the PC and the CTU adapter are connected
correctly. correctly with the USB cable (to make sure, remove
the cable, wait five seconds, and insert it again firmly).
Cause Solution
• The audio input device is used by • Halt or disable the audio function of the other software.
other software.
• The audio device has not been • Open SYSTEM on the control panel, double-click the
installed correctly. DEVICE MANAGER tab, select VIEW DEVICES
BY TYPE, and check that 'DTR-8/16/32KH-1D' is
included under SOUND, VIDEO AND GAME CON-
TROLLERS and that it operates correctly.
• Another USB device is in use at the • Change the settings to reduce the usable band for
limits of the usable band. other USB device.
• Remove the other USB device.
• The TSP media setting is incorrect. • Refer to '<6> Detailed Settings by Line – Media Set-
ting' and specify the correct device.
Cause Solution
• The audio output device is used by • Halt or disable the audio function of the other software.
other software.
• The audio device has not been • Open SYSTEM on the control panel, double-click the
installed correctly. DEVICE MANAGER tab, select VIEW DEVICES
BY TYPE, and check that 'DTR-8/16/32KH-1D' is
included under SOUND, VIDEO AND GAME CON-
• The TSP media setting is incorrect. • Refer to '<6> Line Configuration – Media Setting' and
specify the correct device.
● Using the CTU adapter, sound is intermittent during recording playback of an audio in an
application.
Cause Solution
• Another application which uses con- • Do not use other applications during recording or
siderable processing power is running playback.
simultaneously. • Use a PC with enough processing power to allow
other applications to be run simultaneously.
Cause Solution
• The CTU adapter 'NEC-I CTU-R' has • Double-click MULTIMEDIA (SOUNDS AND MUL-
been selected as the preferred device TIMEDIA with Windows 2000) on the Control Panel,
for sound playback. set the preferred device for sound playback to a device
other than 'NEC-I CTU-R', and place a check in USE
ONLY PREFERRED DEVICES.
TAPI 1.x/CTI
● Dial-up connection to the Internet is no longer possible after a CTI application has been installed.
Cause Solution
• The same COM port is used by the CTA • The same COM port cannot be used. Uninstall one of
driver and the dial-up connection. the two.
● When the CTI application is used, it cannot be used again when a subsequent attempt is made to use it
after a short internal.
Cause Solution
• The PC power saving function dis- • Change the PC BIOS setting so that the power saving
ables the COM port, thus preventing function does not disable the COM port.
communication between the CTU
adapter and the PC.
● The Aspire Telephony Service Provider has been uninstalled with the required procedure, however the
‘AspireTelephonyDriver’ icon remains of the Windows ‘Start menu.’
Cause Solution
Cause Solution
• ASPIRE TELEPHONE SERVICE • Install the CTA or CTU driver if it has not been
PROVIDER not displayed in TELE- previously installed.
PHONY on the control panel (in • Reinstall the CTA or CTU driver if it has not been
PHONE AND MODEM OPTIONS correctly installed.
with Windows 2000 and Windows
XP). Due to the CTA or CTU driver
not having been installed, or not hav-
ing been installed correctly.
• CTA hardware is not connected • Check connections:
correctly. - Serial cable: Is the serial cable correctly connected
to the COM port on the PC?
- Phone
Is the phone operating? (Is the time displayed on the
LCD? Are outgoing calls possible?)
- Is it connected to ESI?
The CTA adapter does not operate when the phone is
connected to ESIC.
• CTU hardware is not connected • Check the connections:
correctly. - AC adapter: Is the AC adapter connected to the CTU
adapter?
- USB Cable: Is the USB cable connected correctly to
the PC and the CTU adapter?
- Keyset: Is the phone operating? (Is the time
displayed on the LCD? Are outgoing calls possible?
• The CTA’s serial cable is not a straight • Use a 9 pin-to-9 pin straight cable.
cable (e.g. cross or special cable).
•
•
A special communications driver is
installed.
With the CTA adapter:
•
•
Uninstall the special communications driver.
TAPI 2.x/CTI
The majority of problems encountered with CTI operation are related to general networking troubleshoot-
ing. In addition to networking, CTI relies on a working domain, due to the fact the operation is based on
Microsoft TAPI 2.1 setup.
Problems:
● Server unable to see Aspire devices within Aspire TSP
● Server unable to see Aspire devices under Phone.exe
● Server Phone and Modem Options fails to Open
● Server Telephony Service is not responding
These problems normally indicate that there is a communication problem between the Aspire and CTI
Server.
Please follow the steps below to check communication between the CTI Server and Aspire.
1. Use the Ping command line tool from the CTI Server to ensure you can ping the Aspire IP address.
The Aspire IP address is found in Program 10-12-01.
You should ensure that, as above, there is 0% Packet Loss displayed in the Ping statistics.
If you are unable to Ping the Aspire NTCPU, verify the Aspire NTCPU IP address (10-12-01).
Next, verify that the PC you are using is connected to the LAN, and attempt to Ping other Hosts on
the LAN (the Default Gateway for example). A useful way of eliminating the LAN is to Ping the
Aspire NTCPU using a cross-over cable from your PC to the Aspire.
Alternatively, consult the Local IT Administrator for any specific configuration requirements on the
LAN.
You should ensure that a Telnet session is established, and verify that the Keep Alive Timer symbol
appears within the Telnet session after 30 seconds (defined in 10-20-01).
Note: You should ensure that the following Services are disabled on the CTI Server before proceeding:
● AspireTSP
● Telephony
If you are unable to establish a Telnet session to the CTI port, verify the CTI port has been defined
in 10-20-01 (8181 recommended).
5
3. Verify the AspireTSP is installed and configured using the correct parameters. It is possible to ver-
ify the configuration using the Registry.
You should verify that the PBX IP address matches the IP address configured in the Aspire
(10-12-01). You should also verify that the PBX Port matches that used in the Aspire configuration
(10-20-01).
On Windows XP or Windows 2000 based computers, when you try and connect to a Telephony Server run-
ning Windows Server 2003, you cannot see or access any telephony devices.
This problem is specific to the Security level within Microsoft Windows Server 2003, in that the Client does
not support the Default Level.
If the TAPI server is using Windows Server 2003, then the clients have to be updated to either XP SP2 or
2000 SP4 with Rollup 1. Or, Microsoft has released a Hotfix which resolves the problem.
The Hotfix can be obtained by contacting Microsoft Support. Further information regarding this can be
found by going to the following Microsoft web page:
http://support.microsoft.com/default.aspx?scid=kb;en-us;824692
The above link also provides a link to the Windows XP service pack 2 update. To obtain the Windows 2000
SP4 Rollup 1 update, go to the following Microsoft web page:
http://support.microsoft.com/default.aspx?scid=kb;en-us;891861
A problem with TAPI 2.1 remote clients using Microsoft Windows XP Pro Service Pack 2 exists due to Fire-
wall settings in Windows.
The built-in firewall (added with Service Pack) is set to the most restrictive mode. This causes Microsoft's
TAPI Remote Service Provider connection to the Telephony Server to run slow. One client with the firewall
in the default mode connecting to a TAPI server will cause every TAPI user on site to run extremely slow.
The firewall settings should be changed for all potential TAPI users to allow a speedy connection. The rec-
ommended change is to enable file and printer sharing in the exception list of the firewall.
7. Click OK.
This is a Microsoft error - complete details can be found on Microsoft’s web site at:
http://support.microsoft.com/default.aspx?scid=kb;en-us;274298
5
The fault affects several manufacturers utilizing the Microsoft Windows Remote Service Provider as used in
the Microsoft TAPI distribution model.
A fix was provided by Microsoft for Outlook® 2000, however currently no fix is available for Outlook 2002,
2003 and XP.
Please check Microsoft's web site for further updates on this matter.
The error box does not affect the call being ended as required and the ability to make a new call.
Unfortunately, it does however mean an extra click on ending a call.
10. Right-click on the serial COM port (usually COM 1) and then click on UNINSTALL. Click
OK to confirm the removal.
11. Right-click on PORTS and click on SCAN FOR HARDWARE.
12. After the communications port has been reinstalled, right-click on the serial port (usually COM
1) and click on PROPERTIES.
13. Select the PORT SETTINGS tab, and make sure the following settings are selected then click
OK:
BITS PER SECOND = rate to set in Program 10-21-02 PARITY = None
(default setting: 19200) STOP BIT = 1
DATA BITS = 8 FLOW CONTROL = Hardware.
14. Close the DEVICE MANAGER window, click OK in the SYSTEM PROPERTIES window,
then close the Control Panel window.
15. Try to reconnect using the dial-up connection (refer to page 5-15).
Use the HyperTerm connected directly to the port that you have selected to determine if the SMDR is
sent. If you receive garbled data, then it is most likely that the Com Port settings are incorrect. You can
also use the Port Configuration tool in CallAnalyst to fine tune the settings.
● I do not see my phone system on your list of supported phone systems. How do I get Ultra
CallAnalyst Enterprise Server to recognize my phone system, which is not on the list.
The requirements to add a new phone system to Ultra CallAnalyst Enterprise Server are:
1. SMDR output from the phone system captured into a text file (use the Hyperterm instructions at
the end of this file). Capture approximately 10 to 15 inbound/outbound and transferred/confer-
ence calls.
2. The SMDR format information from the manual of the phone system.
5 Send the captured data and the information to TriVium Systems, who in turn will make the necessary
arrangements.
● No Inbound or Outbound calls are showing in the Call Data Manager Screen.
1. Make sure that the PC running the Ultra CallAnalyst Enterprise Server has a good serial cable con-
nection to the SMDR port of your phone system.
2. Verify that the correct COM port is selected with the right settings (Baud rate, Stop bits, Data bits,
Parity) in the CDM. If you do not have this information you can contact the phone vendor who
should have the default settings in the manual. If the default settings are not working please use the
configuration tool available on the CDM setup screen for a guided process to determine the settings.
3. Make sure that you have the green telephone icon from CDM in the system tray (right hand corner
of the computer screen).
● Why is Ultra CallAnalyst Enterprise Server not recording my calls correctly from my Com-
dial phone system? I am getting the wrong dates and time for my calls.
Most likely, you have selected the wrong phone system. You need to select either the SMDA or SMDR
based on the output format selected on your phone system.
● I am getting the call information in CDM/CallAnalyst, but the local calls have the format
(000)0nn-nnnn.
The CDM Setup may be incorrect. For details see “Configure the Call Data Manager”.
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\
Sub-Systems\Windows
The default data for this registry value is (all in one line):
5
%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSec-
tion=1024,3072,512,512 Windows=On SubSystemType=Windows ServerDll=basesrv,1 Server-
Dll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitializa-
tion,2ProfileControl=Off MaxRequestThreads=16
The desktop heap is allocated based on the numeric values (in Kilo Bytes) following the
Shared-Section.
Note: You should restart your system for the changes to take effect.
Sales: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203-926-5450
Customer Service: . . . . . . . . . . . . . . . . . . . . . . . . . . .203-926-5444
Customer Service FAX: . . . . . . . . . . . . . . . . . . . . . . .203-926-5454
Technical Service: . . . . . . . . . . . . . . . . . . . . . . . . . . .203-925-8801
Discontinued Product Service: . . . . . . . . . . . . . . . . . .900-990-2541
Technical Training: . . . . . . . . . . . . . . . . . . . . . . . . . . .203-926-5430
Emergency Technical Service (After Hours) . . . . . . . .203-929-7920
(Excludes discontinued products)
NEC Unified Solutions, Inc.
4 Forest Parkway, Shelton, CT 06484
*0893114* TEL: 203-926-5400 FAX: 203-929-0535 December 13, 2005
0893114 www.necunifiedsolutions.com Printed in U.S.A.