PlexView Element Management System

(EMS) Software Release Notice

255-400-402R9.6.3.3

Release 9.6.3.3
April 5, 2005
Lucent Technologies - Proprietary
This document contains proprietary information
of Lucent Technologies and is not to be disclosed or used
except in accordance with applicable agreements
Copyright 2005 Lucent Technologies
All Rights Reserved

Copyright 2005 by Lucent Technologies. All Rights Reserved.

This material is protected by the copyright laws of the United States and other countries. It may not be reproduced, distributed, or
altered in any fashion by any entity (either internal or external to Lucent Technologies), except in accordance with applicable
agreements, contracts, or licensing, without the express written consent of the Customer Training and Information Products
organization and the business management owner of the material.
For permission to reproduce or distribute, please contact the following:
Product Development Manager 1 888-LTINFO6 (domestic)
1-317-322-6848 (international)
Notice
Every effort was made to ensure that the information in this information product (IP) was complete and accurate at the time of
printing. However, information is subject to change.
Information Product Support Number
Lucent Technologies provides a referral telephone number for documentation support. Use this number to report errors or to ask
questions about the information in the IP. This is a non-technical number. The referral telephone number is:
1-508-804-8346
Developed by Lucent Technologies Information Products & Training Group.

HEADQUARTERS

508-480-0909

LUCENT WORLDWIDE SERVICE

support@telica.com

866-582-3688

RETURN MATERIAL REPAIR

888-440-8354

TRAINING DEPARTMENT

508-480-0909

ORDER ADMINISTRATION
sales@telica.com

508-480-0909

PlexView Element Management System

Software Release Notice

1. Software Release Notice Table of Contents

Release 9.6.3.3
1.
2.

Software Release Notice Table of Contents ............................................................... 3

Release Abstract.......................................................................................................... 4
Software .......................................................................................................................... 4
3. System Requirements.................................................................................................. 5
PlexView Client Requirements....................................................................................... 5
PlexView Server Requirements ...................................................................................... 5
Oracle Database Requirements..................................................................................... 5
Solaris Version/Patch Requirements............................................................................... 6
4. New Features .............................................................................................................. 7
Another CAS Call Model Added.................................................................................... 7
SCP-Based Termination Routing Now Supported ......................................................... 7
ABGN Added as a Route Digit Type ............................................................................. 7
ReferReplace functionality enhances SIP....................................................................... 7
AIN Trigger Escape List Now Configurable on 3.8.2.x Switches.................................. 7
Billing Server Alarm Change.......................................................................................... 7
Switch Performance Statistics Collection....................................................................... 7
Time Zones Now Configurable for Switches and Users ................................................ 8
Rate Center Provisioning Changes ................................................................................. 8
Notes and Labels Added ................................................................................................. 8
Order Entry Rollback...................................................................................................... 9
Alarm and Event Filtering Enhancements ...................................................................... 9
Alarm and Event Forwarding.......................................................................................... 9
Server Date and Time Displays in Backup/Upgrade/Restore Windows ........................ 9
N11 Route Node Moved ................................................................................................. 9
Progress Window Change............................................................................................. 10
5. Configurable Properties ............................................................................................ 11
Customizable Server Properties.................................................................................... 11
Bulk Download Security Level..................................................................................... 11
SSL Data Encryption Between Client and Server ........................................................ 12
BTS SNMP Traps Display on PlexView ...................................................................... 12
Forwarding Alarms and Events as SNMP Traps ...................................................... 12
6. Restrictions and Special Considerations................................................................... 14
Connecting PlexView Clients and the Server through Firewalls and with NATs........ 14
Deleting Switches Also Deletes All Related Database Entries .................................... 14
NAL (Node Access List) Changes During Upgrades ................................................... 14
7. Known and Fixed Anomalies.................................................................................... 16
8. Technical Support ..................................................................................................... 19

Lucent Technologies, Inc.

3 of 20

Software Release Notice

PlexView Element Management System

2. Release Abstract
This Software Release Notice (SRN) for version 9.6.3.3 of the PlexView Element
Management System (EMS) software describes the system architecture and features
provided by this product.
The PlexView EMS software allows you to perform element and network management
functions on your Lucent Compact Switches. It provides the functionality to configure,
monitor, and manage faults on multiple switches simultaneously.
This software release notice (SRN) contains important release-specific information that is
not available elsewhere. Section 6, Restrictions and Special Considerations and Section 7,
Known and Fixed Anomalies both describe issues discovered during the development
and testing of this software release that you need to be aware of.
Software
This release of the PlexView EMS software consists of the following software:
PlexView Client Release, Version 9.6.3.3
PlexView Server Release, Version 9.6.3.3
PlexView TL1 Gateway Release, Version 9.6.3.3
This release contains a version of the PlexView Client installation program that enables
you to install PlexView Client software on multiple Sun Solaris or Windows
platforms.
The Apache web server bundled with the PlexView server was upgraded from Release
1.3.26 to Release 1.3.29. If you are upgrading from 9.4.x.x or earlier to 9.6.x.x, contact
Lucent Technical Support for assistance.
Releases of switch software that this release of EMS software supports are listed in
Section 6, Restrictions and Special Considerations.

4 of 20

Lucent Technologies, Inc.

PlexView Element Management System

Software Release Notice

3. System Requirements
This version of PlexView software can manage a network of many Lucent Compact
Switches with many simultaneously connected clients. The switches and clients are both
connected to a single PlexView Server. The minimum recommended system
requirements for this version of PlexView software are given in the following sections.
PlexView Client Requirements
The PlexView Client software is written in Java and runs on Sun/Solaris, Windowsxp,
Windows NT or Windows 2000 platforms.
The minimum recommended configuration for a Windows-based PlexView Client is:
A 200MHz CPU
A minimum of 128 Mbytes of memory (256 Mbytes recommended)
A minimum of 100 Mbytes of free disk space is necessary to install the client
application
Executing other applications may require additional memory
To run the PlexView Client software on a Sun/Solaris platform:
An Ultra 10 or greater system is recommended
A minimum of 256 Mbytes of memory is recommended
The Common Desktop Environment (CDE) must be used when running the PlexView
Client in the Sun environment.
Lucent recommends that only one client run on each platform.
Lucent does not recommend using a configuration where a single server runs multiple
clients or the client applications are x-termed to user displays.
PlexView Server Requirements
PlexView Server software runs on a Sun Solaris platform. The minimum recommended
hardware configuration for PlexView is:
A Sun Solaris platform with a 550 MHz CPU
1 Gbyte of memory minimum
36 Gbytes of hard disk space minimum
A 100MB Ethernet connection
This release does not support the configuration of more than a single PlexView Server
instance.
Oracle Database Requirements
The PlexView Server employs an Oracle database for persistent storage of selected
configuration information as well as user account information. Oracle 8i Standard
Lucent Technologies, Inc.

5 of 20

Software Release Notice

PlexView Element Management System

Edition Release 3 (8.1.7.0) and the Oracle 8.1.7.4 patch set are bundled into this release
of PlexView EMS software. You are required to upgrade your existing Oracle software
to 8.1.7.4 to use this version of PlexView.
Solaris Version/Patch Requirements
PlexView EMS software (client or server) requires Solaris 9 or 8 (both are
recommended) or 7 with the corresponding Solaris patches. Patches can be downloaded
in .tar format from the Sun website, http://sunsolve.sun.com/.

6 of 20

Lucent Technologies, Inc.

PlexView Element Management System

Software Release Notice

4. New Features
This section summarizes the new features provided in this release of PlexView EMS
software.
Another CAS Call Model Added
A new CAS call model has been added to the CAS Profile. Under the IMT>CAS
Profile>Call Model pulldown, EO_OPS_TRUNK_V2 is new and supports Trunk ModelOperator Services.
SCP-Based Termination Routing Now Supported
Termination routing based on SCP that supports keying on SCPTG has been added.
SCPTG can now be used as a key in Routing Administration>Add Route Digits,
IMT>Intelligent Network Services>SHLR SCP Services adds a new SCP Type
parameter, and SCPTG can be verified using Verify Translation Plan.
ABGN Added as a Route Digit Type
ABGN, (Anchor Bearer Group Number) has been added to the list of available keys for
digit screening for switches running a minimum release of 3.10.1.4. This routing key
expands SIP functionality.
ReferReplace functionality enhances SIP
A new trunk group parameter enhances SIP and SIP-T. The new ReferReplace parameter
provides Replace processing that supercedes Refer processing when the switch has the
call leg that the call comes into.
AIN Trigger Escape List Now Configurable on 3.8.2.x Switches
The trigger escape list can now be configured on switches running 3.8.2.x software.
Billing Server Alarm Change
The EMS will now post an alarm if a switchs primary billing server fails over. The EMS
will clear the alarm when it determines that the designated primary billing server has
resumed control of receiving and processing billing data from the switch.
Switch Performance Statistics Collection
Switch performance statistics are now monitored by PlexView and stored in the database.
These statistics are accessible only through the optional Advanced Reporting System.
The EMS periodically polls the active SP to retrieve this information. The available
information includes:
Free Memory
Used Memory
Non-volatile Free Memory
Non-volatile Used Memory
Average Busy time on the SP

Lucent Technologies, Inc.

7 of 20

Software Release Notice

PlexView Element Management System

The minimum, maximum and average of these parameters is calculated and stored every
five minutes along with EMS and switch timestamps.
Performance statistics collection can be enabled or disabled under the Modify
Switch>Stats Configuration tab.
Time Zones Now Configurable for Switches and Users
To facilitate alarm and event timestamp localization at the client for each user, all alarms
and events received by the server are now normalized to Greenwich Mean Time (GMT).
Modify each switch (Modify Switch->Time Zone) to allow the server to convert and log
all received alarms and events from the managed network to GMT. For example, if a
switch is on Pacific Time, set the Time Zone in the switch record to GMT-8:00.
Once the time zone settings are correct for each switch, the client display can be correctly
localized in all logs and the Fault Status panel.
Set the users time zone under the Actions>Users>Add/Modify> User Info tab for each
user. The default setting is GMT (Greenwich Mean Time). If you change the time zone,
all logs will display the change.
Rate Center Provisioning Changes
The character length for rate center names has been expanded from 16 to 32
alphanumeric characters. In previous version of PlexView, ambiguous rate center names
could lead to errors when local calling areas were being built out. The ability to enter the
maximum number of characters may be limited by the switch software release you are
using.
For example, Pinehurst could represent Pinehurst, NC or Pinehurst, TX. It was
impossible for the switch to distinguish between the rate centers. Now the EMS appends
both the state abbreviation and the LATA ID to the name. Consequently, Pinehurst, NC
will be provisioned as pinehurst_NC_960 and Pinehurst, TX as Pinehurst_TX_560,
eliminating any ambiguity when the provisioned rate centers are assigned to a local
calling area.
Notes and Labels Added
Notes and labels can now be added to any individual EMS node.
Enter a note by right-clicking a node, selecting Notes & Labels and typing in
the Notes field
A note can be displayed by right-clicking a node and selecting Notes & Labels
Enter a label by right-clicking a node, selecting Notes & Labels and typing in
the Label field
Labels are displayed in the navigator tree whenever you reveal the node in the
user display
In nodes with a Label field, both a label and notes can be entered. If there is no Label
field, only notes are available for that node.

8 of 20

Lucent Technologies, Inc.

PlexView Element Management System

Software Release Notice

Order Entry Rollback

This Order Entry Rollback notice applies only for users that have purchased the Order
Entry package. Orders that have been entered can now be rolled back in PlexView. Some
conditions apply:
You must have the Order Entry License
Admin privilege is required to perform OE Rollbacks
One order at a time can be rolled back
The elapsed time between order commitment and rollback should be short.
The longer the time, the more likely that the order will have been referenced
elsewhere. Orders referenced in another location on the system cannot be
rolled back.
There are two new menu items under Order Entry:
Roll Back rolls back everything in the order until it encounters an error and
then the roll back stops.
Force Roll Back rolls back everything in the order, skipping the ones that
fail, ignoring errors, and does not stop until all orders that can be rolled back
have been rolled back.
Alarm and Event Filtering Enhancements
Alarm filtering now includes event filtering by Trouble Isolation ID. Accessing Filters by
User or by the Event tool in the toolbar on the Navigator now support filtering by Trouble
ID. There is also a Trouble (Isolation) ID column under the Fault Status tab in the
Navigator status pane. Filtering on TRID provides fine-grained control over fault and
event forwarding. Previously all alarms of a particular severity would be forwarded. Now
certain alarms of a particular severity can be excluded from forwarding.
Alarm and Event Forwarding
Alarms and events can be converted to SNMP traps and forwarded to northbound SNMP
managers. By default, generic traps can be forwarded, but the properties file can be
modified to forward specific traps using a procedure in chapter 5 Administration and
Maintenance in the EMS User Guide. Additionally, a users Alarm and Event filtering can
be used or not used to determine what alarms and events are forwarded.
Server Date and Time Displays in Backup/Upgrade/Restore Windows
The date and time as listed on the server are now displayed under all tabs when you
highlight a switch and select Backup/Upgrade/Restore. A Refresh Date /Time button
updates the display in real time. This information is posted to any function you perform
under these tabs. These timestamps are not affected by client time zone changes.
N11 Route Node Moved
The N11 Route node for 3.8x and earlier switch releases moves to the Routing
Administration portion of the tree from its previous location under the
Carrier Administration->Local portion of the navigator tree.

Lucent Technologies, Inc.

9 of 20

Software Release Notice

PlexView Element Management System

Progress Window Change

The display of the progress window, visible at the lower left of a navigator screen when
you call a function or execute a command, has been updated. The progress window
display is now a small vertical strip that bounces from left to right to left.

10 of 20

Lucent Technologies, Inc.

PlexView Element Management System

Software Release Notice

5. Configurable Properties
Customizable Server Properties
PlexView provides two editable properties files to customize PlexViews appearance and
operation. Both files are located in the
{ROOT}/opt/PlexView/Server/Properties
directory. The first file, plexview.properties, customizes client side behavior and
appearance. If you edit this file, restart your client session(s) for the change to take
effect. The second file, plexcore.properties, customizes server behavior. If you edit this
file, reboot the PlexView server for the changes to take effect.
Each new version of PlexView ships with template versions of these files. The template
versions are called plexview.properties.template and plexcore.properties.template
respectively. Examine the template files and merge the required changes into the
plexcore.properties and plexview.properties files.
This version of PlexView supports several new configurable properties. Specifically:
backupFileSystemPollInterval
backupFileSystemPollInitDelay
maxBackupFilesPerSwitch
These properties control the number of backup files that the EMS server will store per
managed switch and the rate (in seconds) at which the EMS server checks the number of
backup files present. These properties can be changed by modifying the
{ROOT}/opt/PlexView/Server/Properties/plexcore.properties
file.
trunkNumberScheme96 This property controls the numbering scheme used
when range provisioning SS7 trunks. When this property is set to true, trunks
will be numbered as followed: 1-96, 101-196, 201-296, etc. When this
property is set to false, trunks are numbered consecutively. This property is set
to false by default. This property can be changed by modifying the
{ROOT}/opt/PlexView/Server/Properties/plexview.prope
rties file.
Bulk Download Security Level
The security level required for issuing bulk download commands in now configurable.
Prior to 9.6.2.1, the SW (software) security level was required before you could issue a
bulk download command. PlexView can now be changed to allow users with SA (service
affecting) privileges to issue bulk downloads.

Lucent Technologies, Inc.

11 of 20

Software Release Notice

PlexView Element Management System

By default, only users with SW privileges and above can issue bulk download
commands. To allow users with SA privileges and above to issue these commands,
modify the plexview.properties file as follows:
# Properties for bulk download - recommend SW privilege
level
#
bulkDownloadPrivLevel=SA
execFtpPutPrivLevel=VIEW
For further information on that file, see Appendix D in the PlexView EMS User Guide.
SSL Data Encryption Between Client and Server
SSL Encryption of data between client and server is now available with PlexView. By
default, encryption is disabled.
To enable encryption, create or edit the file using the following path:
/opt/PlexView/Server/CurrRel/lumos/ext/auto-service.cfg
Edit it to add:
sslCommunicationOn=true
The data encryption level is preset and cannot be adjusted. On servers or clients residing
on older computers, performance may be slower than before you enabled encryption.
BTS SNMP Traps Display on PlexView
The SNMP agent in PlexView accepts, receives and displays/logs SNMPv1 traps from
the Billing and Traffic Server. SNMP traps retrieved from the BTS are converted to TL1
alarms and displayed by PlexView.
To enable the receipt and recognition of SNMPv1 traps from the BTS, edit the file using
the following path.
/opt/PlexView/Server/CurrRel/lumos/ext/auto-service.cfg
Edit it to add three lines as shown in the following example:
btsSnmpTrapRcvrOn=true
btsSnmpTrapRcvrPort=14002
btsSnmpTrapRcvrAgentList=10.2.2.18,10.2.2.13,10.2.2.15 (three
example IP addresses)
For the btsSnmpTrapRcvrAgentList, use the list of unique IP addresses with comma
delimiters that work for your network.
Once the trap receiver is on, the port is set, and the agent list is created, you should be
able to receive and forward SNMP traps from the Billing and Traffic Server. Configure
the SNMP agent in the BTS to send traps to the EMSs btsSnmpTrapRcvrAgentList.
Forwarding Alarms and Events as SNMP Traps
Alarms and events can be forwarded to northbound SNMP management systems as
SNMP traps. Alarms and events are converted to traps and forwarded by PlexViews

12 of 20

Lucent Technologies, Inc.

PlexView Element Management System

Software Release Notice

built-in SNMP proxy agent. For switches running <3.8 software, only generic traps can
be sent. For switches running >3.8 software, generic or specific traps can be sent.
Perform the following steps to enable trap forwarding.
1. Go to the server from a UNIX command line and change to the following
directory:
cd /opt/PlexView/Server/CurrRel/lumos/ext
2. Auto-snmptraps.jar is a hidden file. Copy it and change its attributes by the
copy so the file is not hidden as follows:
cp .auto-snmptraps.jar

auto-snmptraps.jar

3. Change your directory to:

/opt/PlexView/Server/Properties
4. Open plexcore.properties and uncomment the following
properties or copy the following lines to append the file:
enableTrapForward=true
trapDestinationHost=plexview1
trapDestinationPort=162
trapCommunityString=public
By default, the SNMP proxy sends generic traps when you enable forwarding. To send
specific SNMP traps from switches running >3.8 software, set the following property by
adding this line to the file:
trapMode=specific
You can filter traps that will get forwarded. The trapFilterAccountName parameter is
only valid starting with EMS 9.6. It uses the user accounts fault session filter and event
notification filter and forwards faults and events accordingly. Add the following property
to enable this feature:
trapFilterAccountName=(the user account name)
5. Save the file.
6. Shut down and restart the server. Northbound SNMP managers should now
see traps forwarded by the proxy agent.

Lucent Technologies, Inc.

13 of 20

Software Release Notice

PlexView Element Management System

6. Restrictions and Special Considerations

This version of PlexView software has been validated against and only supports Lucent
Compact Switches running switch releases:
3.10.1.6
3.10.1.5
3.10.1.4
3.10.1.3
3.10.1.2
3.10.1.1
3.10.1.0
of switch software. This release of EMS software may not manage switches running other
versions of switch software correctly. For switches running software revisions from
earlier than 3.10, contact Lucent Worldwide Services for further support information.
This version of PlexView software does not support running multiple instances of the
PlexView Server. Only one instance of the PlexView Server should be running.
9.6.3.1 was the last EMS software release to be regression tested against switches running
software at a release lower than release 3.10. To migrate to later versions of EMS
(10.0.0.0 or later), you will need to fully migrate your switches to release 3.10 or later
first.
Connecting PlexView Clients and the Server through Firewalls and with NATs
The PlexView EMS uses Java Remote Method Invocation (RMI) to establish
communications paths between the EMS clients and the EMS server. To configure RMI
for Release 9.5.0.0 and later to work with all clients, including clients outside a firewall,
you must use the hostname of the EMS server and not localhost or the IP address in the
Server Name field of the install/upgrade setup dialog, update the DNS to resolve the
hostname, and use the EMS servers hostname in client setups. This is fully documented
in the PlexView EMS Server Software Installation Guide.
Deleting Switches Also Deletes All Related Database Entries
Deleting a switch requires enough time for the EMS to eliminate every trace of the
deleted switch from its databases.
To delete a switch, unmanage it, and then delete it. Lucent recommends that you delete a
switch from the navigators Lucent pane and not from the status pane. The Lucent pane is
the bottom window in the navigator that shows the configurable nodes. Right-click on the
switch name and select Delete. When you use the Lucent pane, the delete monitor
displays deletion progress. After you initiate a switch delete, allow the EMS enough time
to complete deletion before performing any other operations. Check the status bar at the
bottom of the delete monitor for completion.
NAL (Node Access List) Changes During Upgrades
A Node Access List (NAL) provides fine-grained access control allowing the PlexView
system administrator to limit individual operator account provisioning capabilities to a

14 of 20

Lucent Technologies, Inc.

PlexView Element Management System

Software Release Notice

specific functional area. A NAL list requires the system administrator to assign a
privilege level (RW or RO) for each node in the PlexView navigator tree and to save the
NAL list to the PlexView database. The NAL(s) can then be assigned to any operator
level account. The operator accounts NAL list determines the node-by-node
provisioning capabilities granted to the account.
Because new releases of PlexView introduce new navigator nodes, the system
administrator must review and modify the NALs each time a PlexView software upgrade
is performed. New nodes in the NAL default to RO, so operators cannot provision new
nodes after an upgrade, even if the node is within their functional provisioning area.
Modifications to the NALs required for each upgrade depend on the previous version of
PlexView software, the new version of PlexView software, and the versions of switch
software being managed.
The list below summarizes the PlexView navigator node changes that have occurred
between the release of PlexView 9.4.0.0 and this version and are applicable to the
management of 3.10.x.x and later switch software.
There were no new NALs added for >9.6.3.3 EMS software managing 3.9.x.x switches.
For >9.6.3.3 EMS software managing >3.10.1.x or >3.8.2.x switches, these are the new
nodes:
IMT>SIP-T
SS7>Intelligent Network Services>AIN Trigger Escape List

Lucent Technologies, Inc.

15 of 20

Software Release Notice

PlexView Element Management System

7. Known and Fixed Anomalies

The following table provides a list of known anomalies within the PlexView EMS
software.
ID
Priority Summary
Number
You must refresh the screen for rolled back ports or any object that
changes state to display its updated state. Workaround: None.
Do not update or delete trunks if you have sorted them.
If you alter the sort order of trunks in the Configure Trunking
dialogues and then send down a ranged update/delete, you may see
undesirable results.
As an example, If you have trunk 1 and trunk 10 IS and trunk 2-9
OOS, you sort by status, and then do a ranged update while
highlighting 1 and 10, you actually send a ranged update command to
the switch for 1 through 10, regardless of the sort order. So 2-9 also
get updated. Workaround: Only delete unsorted multiple trunks.
Roll Back of ISUP trunks
If you range delete ISUP trunks in an ISUP trunk group in Order
Entry mode, then commit the order, and then attempt to roll back the
committed order, PlexView will not be able to restore the committed
order to its previous state for the range deleted ISUP trunks. All range
deleted trunks will have the same configuration instead of the unique
configurations they had prior to being range deleted. Workaround:
None.
22844

P2

EMS shows incorrect secondary state (RAI) on an IS T3 until

refreshed. Workaround: Refresh the screen.

26378

P2

The EMS search tool needs to allow multi-key searches.

29932

P2

Audio Announcements: When you issue a DBCHG for ENT/EDAUDIO-ANNC commands in TL1 that includes spaces, the EMS
cannot read it. Workaround: When issuing TL1 command, Use
underscore_ character for spaces. Spaces when issuing the equivalent
command in the EMS are accepted by both systems.

30561

P2

Backups of large switch databases will occasionally time out.

Workaround: Modify BackupRestoreTimeOut= in
plexcore.properties and reboot the EMS server

16 of 20

Lucent Technologies, Inc.

PlexView Element Management System

Software Release Notice

The following table provides a list of fixed anomalies within the PlexView EMS
software.
ID
Priority Summary
Number
27435

P3

EMS Loss of Comm alarm if client is set to Local time instead of

GMT

28249

P3

IOM-13 thru IOM-17 on 2688 Channel Voice Server Rear Card

shows Configuration Incorrect on EMS.

28266/
27300

P2

EMS schedule exercise count doesn't decrement when exercise runs

on the switch.

28640/
28827

P2

EMS route digits bulk download times out.

29011

P2

Unable to change TGSERVICE parameter on non-SS7 trunk group.

29406

P3

SS7 Link configure brings up the wrong window.

29594

P1

Add Switch/Delete Switch errors

29686

P3

EMS converts IP address on MGC.

31089

P2

System Service --> test port monitor is not working properly.

31552

P2

When adding a Trunk Group the EMS should strip leading zeros

31563

P2

EMS should do a ranged retrieval of CRVs rather then getting them

all.

31788

P2

EMS 9.6.1.0: max limit of backup files (parameters in

plexcore.properties) sporadically not working.

31790

P1

Order Entry's shuffle process has problems

31840

P1

SIP trunk groups lost their IP address in EMS during upgrade. Cannot
change info for these trunk groups since EMS is requiring valid IP
address.

32637

P2

Unable to change number of rings for subscibers with VM

33327

P1

The Parameter Suppression Profile doesn't accept DEFAULT for

GAP or GENDGTS

33691

P3

Next Digit Screen shows wrong value

33710

P3

Remarks are not displayed for both ISDN Interface and ISDN link.

33749

P2

Entering an MGCP-LINE command fails w/ Error Code 6

Lucent Technologies, Inc.

17 of 20

Software Release Notice

PlexView Element Management System

33964

P2

Cannot remove TransPlan from a Trunk Group without trying to add

one first

33971

P1

Test trans on GR303 IF does not work from EMS

33990

P2

EMS allows user to enter incomplete information in ParamDefaults;

sending down null values to the switch.

34021

P2

EMS doesn't allow "rings before forwarding" to be set.

34853

P2

EMS won't assign GAP-DEFAULT/NOTPRESENT Digit Screen.

34915

P2

ABGN missing DEFAULT and NOTPRSNT primKeyValues

34937

P2

Search filter for Called Party Routes under Routing Administration

throws exception of invalid column name.

35705

P2

For an SS7 trunkgroup, when using a generic digit mod, after a

synchronize, it reverts back to no digit mod.

34692

P2

Element Manager allows only 26 DS1 on GR303 instead of 28.

36012

P1

ISUP trunk groups that are configured as IXC/FGD are listed as INC
on the EMS

36813

P2

EMS client has problems with newly upgraded SP-3 from SP-2.

18 of 20

Lucent Technologies, Inc.

PlexView Element Management System

Software Release Notice

8. Technical Support
Lucent Worldwide Service Is available to assist you with any problems that you
encounter with this release of PlexView software. To contact Lucent Worldwide Service,
please call 866-582-3688.

Lucent Technologies, Inc.

19 of 20

Software Release Notice

PlexView Element Management System

Notes:

20 of 20

Lucent Technologies, Inc.