Fourth Quarter

2000

E-Mail Us at isi-mat@isi-info.com

Optivity Telephony Manager (OTM)

The Nortel Optivity Telephony Manager 1.0 software has been available and is replacing MAT (Meridian Administration
Tools). By the release of this bulletin Nortel will have released its FREE upgrade to version 1.01 for all OTM 1.0 users. This
Up-issue will correct a variety of 1.0 bugs and allow for the use of the Windows 2000 operating system. When ordering from
Nortel, use the special code of NTTL24AA for the 1.0 to 1.01 upgrade kit.
The final version of MAT, 6.67.07, has been available since mid-summer, and will remain as-is. It will be available through
2001 for those vendors/customers who would prefer it. However, there will be no further development on the MAT product.
Resources have been transferred over to the new OTM product line that includes all the functionality of MAT plus more.
OTM can be purchased from Nortel in one of three packages outlined below. It is also possible to upgrade from MAT versions 5.71 and greater to OTM. Which upgrade OTM package is ordered will depend on the MAT modules already in use.
For instance, if a customer has, or is only interested in the Station module, then the General OTM package will suffice. However, if they also require ESN, then the Premium package would be needed.
The MAT Call Accounting module has been re-worked and is being sold as an unbundled package entitled the OTM Telecom
Billing System. This can be purchased along with one of the other packages. TBS has expanded reporting capabilities, and
improved collection and costing methods.
OTM can reside as a stand-alone application or you can upgrade a stand-alone MAT client. However, you will not be able to
take advantage of the Client/Server architecture which allows for the new Web-enabled functions or the LDAP (Lightweight
Directory Access Protocol) synchronization. Here, an LDAP server provides common information such as first and last
names, department, division, and employee numbers and is the updating source for OTM. Clients no longer need a separate
dongle for operation. Now, there is only one dongle connected to the PC, which runs the NT Server and determines the
number of PBX and Client licenses.
ISI installation technicians are becoming Nortel Certified to install and train on the OTM product line. We predict this to be a
gradual change from MAT to the OTM software over the course of 2001. OTM upgrades may involve hardware upgrades to
meet server and client requirements. ISI will continue to support both MAT and OTM customers. Current MAT customers will
have the option to upgrade to an OTM system or continue with MAT. Contact ISI for additional information on OTM installation, training and support pricing at 800.359.6559 or e-mail us at isi-mat@isi-info.com.

General Package
Common Services
Scheduler; Version Control; Windows Navigator; Site Assignment; Import/Export; Watchdog; Database Compact and Repair;
Web Navigator
Fault Management
Alarm Capturing and Logging; PC Event Log and Viewer, Alarm
Viewer (Windows); Alarm Banner (Web)
Configuration Management
System Window; List Manager; Directory Editor; Station Administration; ITG Configuration; DBA Database Backup and Restore
(X11 Database)
Accounting Management
DBA CDR; DBA Traffic

Enhanced Package
Includes all General Package Functionality PLUS...
Common Services
Web Station Admin - End-user help
Fault Management
Web Alarm Viewer
Configuration Management
Maintenance Windows;
Web Maintenance Pages; Inventory
Management
Performance Management

Premium Package

Security Management
OTM User Admin (as in MAT Windows clients); Standard WinNT
Security

Includes all Enhanced Package Functionality PLUS...

System Access
Windows System Terminal; Web Virtual Terminal Server

Configuration Management
ESN Analysis

Applications
Corporate Directory, Optivity NMS integration (co-residency and
launch point)

Applications
LDAP Synchronization

Fault Management
Alarm Notification

MAT NEWSLETTER

DBA Script File

When using MAT version 6.67, make sure the correct script file is loaded
for the processing of the CDR records. ISI has standardized on NEW
Format CDR for all installations. The sl1new.scr file should be selected
for the processing of NEW Format CDR as in the screenshot below.
If you choose a different script file such as sl1newx.scr, you run the risk
of collecting duplicate data because the temporary file, detail1.img, does
not get renamed at the conclusion of a poll/parse. The result is that the
detail1.img file is continually appended to, and the same data is polled
many times. There was a typo in an earlier issue of Keeping Connected
with ISI which stated you should use the sl1newx.scr file.

Create Extra PTY Ports

Normally for an Ethernet configuration you need to
define at least one PTY port in Load 17. However,
this limits you to running only one MAT or OTM
application at a time over the Ethernet, for example
Maintenance Windows. If you wanted to launch a
second application such as
System Terminal for direct
access to the
PBX, you
would have to
first terminate
the Maintenance Windows connection.
Instead, you
should create additional PTY ports in Load 17 for
simultaneous operation of different MAT or OTM
processes. You can configure up to four PTYs for
an Option 11C and up to eight for Options 51C
through 81C.

Happy Holidays
and
Good Selling in 2001!
Errors In The ESN Database Download
Occasionally, there will be a problem with the ESN database
download. This download pulls in the ESN information for NCOS
(Network Classes of Service), DMT (Digit Manipulation Indexes),
RLI (Route List Indexes) and all NPA/NXX listings. This
download can include PBX system messages which are output
during the retrieval process, or garbage characters which may be
generated by noise hits. Either case may cause errors when the
data is parsed which may hinder the ESN databases from being
created correctly in MAT.
While the ESN data is being collected, it is stored to a file named
esnretrieve0.dld which is located in the X:\Nortel\Common Data
\Site\System\Esn folder. X could be your local C: drive, or a
mapped network drive.
First, the data is printed from the PBX to this file, then the file is
parsed by the MAT software. If a problem is detected with the
parse, errors will be documented, and the line number which is
causing a possible problem will be shown as in Figure 1. Figure
1 shows some possible errors, but also that the Parse concluded
successfully. Had it not, there is an Edit button you can use to
open the file in Word Pad, locate the error(s), and delete them.
Figure 1
Then you could re-process the Parse successfully.

MAT NEWSLETTER

MAT/OTM Usernames, Templates and Passwords

Its important and worth noting again, with multi-user MAT installations as well as with the new Optivity Telephony Manager
systems, that only one User at any given time be logged in with Admin capabilities. If two people log into the system with full
Administrative access at the same time from two different clients, the software is liable to lock up.
The alternative is to create different user templates to minimize the above possibility. From the MAT or OTM Navigator menu,
click on the Security tab and go to MAT Users. There you should see the Administrative User entry. Never delete this or
youll lose the highest-level access to the system, and be forced to reload the software. What you want to do is add new Templates, and assign these templates to new Users.
Click on the Configuration tab and go to User Templates. Double-click on the Administration template and notice that there
is full read/write capability with this template, and that the Administrator box is checked as in Figure 2 below. To create a
new template, click on Configuration from the User Templates menu and designate a new entry as in Figure 3 below.

Figure 2

Figure 3
Do not click the Administrator box. You will now have a new template that has full
read/write capabilities, but does not have the Administrative designation. Additionally, you could assign read-only status to certain Sites/Systems or modules. You
could prohibit access to certain Site/Systems or modules as well.
Next, assign the new template to a
new User(s) by going back to the
MAT Navigator screen, click on the
Security tab, go to MAT Users,
then to the Configuration tab, and
then to Add User. Here, create a
new user and assign the new template as in Figure 4

Figure 4

MAT NEWSLETTER

6.67 PATCHES
6.67.07.p01

There are several patches available from Nortel for the latest MAT version 6.67. Listed below is information taken from the read-me files explaining the function of each. These patches are available from Nortel or
ISI.

Patch/Fix Name:

Patch/Fix Name: 6.67.07.p02

PRS#: MP08198

Module: (Station)

Description: Adding a NEW set already has information assigned to it.

Last Modified:
PRS#:

30/06/2000

MP09565

Description: DN number can't be assigned to DN field on Forms Interface.

Patch Contents:
File Name
Path
Station.exe
nortel\m1\meridian administration tools\
Matform.dll
nortel\m1\meridian administration tools\

Module: Station.
Last Modified: 09/13/2000

Platform: WinNT, Win95/98

Special Instructions:
Caution:
1. Please make backup of mcdll.dll before overwriting/deleting.
2. Please follow the instructions carefully while installing the patch.
Patch Contents: This patch consists of the following files:
File Name
Path
Mcdll.dll
<OTM Root>\M1\Meridian Administration Tools\

Instructions to manually install the patch:

Instructions to manually install the patch:
1) If MAT is running, close all MAT applications and terminate MAT.
1) If MAT is running, close all MAT applications and terminate MAT.
2) Using Windows Explorer, locate the directory "<OTM Root>\M1
2) Using Windows Explorer, locate the directory "nortel\m1\meridian
\Meridian Administration Tools\" and keep a backup of "Mcdll.dll" so
adthat you can restore the files if the patch needs to be removed.
ministration tools\"
3) Copy Mcdll.dll provided in the patch to <OTM Root>\M1\Meridian
3) Copy matform.dll and station.exe provided in the patch to nortel\m1
Administration Tools\
\meridian administration tools\
Patch/Fix Name: 6.67.07.p03
ESN retrieve parsing error
Last Modified:

07/19/99

Patch/Fix Name: 6.67.07.p04

Update country-specific code parameters in loss.ini file.
Last Modified:
PRS#:

PRS#: MP09974
Description: Fixes ESN Retreival problem due to NXX problem.
Instructions to manually install the patch:
1) If MAT is running, close all MAT applications and terminate MAT.
2) Using Windows Explorer, locate the directory Program File (path
Nortel
\M1\ESN Analysis & Reporting\) and rename it such that it can be
eas
ily identified and renamed back if the patch needs to be removed. For
example, append the directory name with "old."
3) Copy Esndll.dll to <OTM root>\M1\ESN Analysis & Reporting\
directory Program\Program Files\Esndll.dll
Copy EsnENG.dll to <OTM root>\M1\ESN Analysis & Reporting\
directoryProgram\Program Files\EsnENG.dll
4) Re-launch MAT and test the application to see if the patch is working
correctly.
Patch/Fix Name: 6.67.07.p06
ITG_ISDN_TRUNK_D-channel_Fix

2000/08/01 11:49 (AM/PM) PST

N/A

Description:
Lost ini file contains the updated information on country-specific codec
parameters.
Special Instructions:
If the ITGIPPhone application is up, close it.
Note:
After the patch is installed, if the user goes to the DSP Property page, an
error dialog box may pop up saying that "USA is not in the combox list.
Please click OK to ignore this error dialog box, and select the country
dropdown list to "North America". Then click OK or APPLY button on the
property page. This will save the current setting. Next time when the DSP
Property page is visited, the error will not appear. This situation is corrected in newer versions of the software.
Platform: NTclient, NTWorkstation, NTserver, Win95/98
Instructions to manually install the patch:
Copy the file loss.ini to <OTM Root>\Common Data\ITGIPPhone Data\

Last Modified: 9/6/00

Patch/Fix Name: 6.67.07.p07

ITG IP PHONE fix

PRS#: MP09796

Last Modified: 9/11/2000

Description: Fixes the fact that "Sl1 ESN5" does not show up as an
available D-channel protocol for Option 11 systems. Also fixes the problem w/ Opt11C Compact and Opt11c Mini not being related like option
11C systems. This was causing a problem w/ the TN field showing up as
a
3-segment field for mini and compact, when this is only supposed to
happen for larger systems. Also, fixes the problem with the TN field being limited to integers between 0 and 159 for Opt 11 systems. Now the
TN field can be any integer between 0 and 256.

PRS#: MP09999

Special Instructions:

Close the ITG ISDN Trunk Application

Instructions to manually install the patch:

Copy and overwrite ITGISDNTrunkApp.exe to
<OTM Root>\M1\ItgIsdnTrunk\Program Files

Description: For an Option 11 system, the TN field should appear as a

single field (rather than a 3-part field). However, Option 11 Mini and Option 11 Compact were not being recognized as Option 11 systems.
Special Instructions:
Platform:

Shut off MAT first

ALL

Instructions to manually install the patch:

Copy and overwrite ITGIPPhoneApp.exe to
<OTM Root>\M1\ITGIPPhone\Program Files\