634
Alcatel-Lucent OmniVista 4760 Network Management System Administrator manual Alcatel-Lucent OmniVista 4760 Network Management System All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent OmniVista 4760Network Management System
Administrator manual
Alcatel-Lucent OmniVista 4760 Network Management SystemAll Rights Reserved © Alcatel-Lucent 2008
Legal notice:
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks ofAlcatel-Lucent. All other trademarks are the property of their respectiveowners.
The information presented is subject to change without notice.
Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.
Copyright © 2008 Alcatel-Lucent. All rights reserved.
The CE mark indicates that this product conforms to the following CouncilDirectives:- 89/336/CEE (concerning electro-magnetic compatibility)- 73/23/CEE (concerning electrical safety)- 1999/5/CE (R&TTE)
Chapter 1Section 1 Interface
Overview .................................................................................................... 1.1
Overview ....................................................................................................... 1.1
Client-server architecture ........................................................................... 1.2
Compatibility ................................................................................................ 1.4
Internal applications .................................................................................... 1.5
External applications .................................................................................1.11
Startup and Shutdown .........................................................................1.11
Starting Alcatel-Lucent OmniVista 4760 Network Management System ..1.11
Logging off ..................................................................................................1.13
Exiting Alcatel-Lucent OmniVista 4760 Network Management System 1.13
Main window ...........................................................................................1.13
Main window, overview ..............................................................................1.13
Starting applications ..................................................................................1.14
Using menus ...............................................................................................1.15
Sizing panels ...............................................................................................1.16
Application-specific icons .........................................................................1.17
Viewing data ............................................................................................1.17
Browsing the tree structure .......................................................................1.17
Displaying data ...........................................................................................1.18
Configuring columns .................................................................................1.20
Printing \ Exporting ....................................................................................1.21
Data search ..............................................................................................1.21
0-1
Using the search area ................................................................................1.21
Example searches ......................................................................................1.24
Searching from the tree .............................................................................1.27
Modifying data ........................................................................................1.27
Overview ......................................................................................................1.27
Updating attributes .....................................................................................1.27
Adding/Deleting an object .........................................................................1.28
Copy/Paste attributes .................................................................................1.29
Moving entries ............................................................................................1.30
Applying or canceling updates .................................................................1.30
Customizing dictionaries ...................................................................1.31
Overview ......................................................................................................1.31
Dictionary location in the Alcatel-Lucent OmniVista 4760 NetworkManagement System ..................................................................................1.31
Managing customized dictionary versions ..............................................1.32
The CustomDict.exe tool ...........................................................................1.32
Deployment .................................................................................................1.35
4760 Diagnostic Tools .........................................................................1.35
Overview ......................................................................................................1.35
Operation .....................................................................................................1.36
Chapter 2Section 2 Directory
Overview .................................................................................................... 2.1
Inter-Directory Relationships ..................................................................... 2.1
The Four Tabs of the Administration Directory ........................................ 2.2
Web Directory Client ................................................................................... 2.3
Cost Center Management Rules ................................................................ 2.3
Specific Management of an OmniPCX Office ........................................... 2.6
Customization of Parameter Names .......................................................... 2.6
Company tab ............................................................................................ 2.6
Description of the Company Tab ............................................................... 2.6
0-2
Creating Entries Automatically .................................................................. 2.7
Inherited Automatic Update of the Attributes ..........................................2.10
Managing Entries ........................................................................................2.10
Confidential List .........................................................................................2.17
Groups .........................................................................................................2.17
RSC tab .....................................................................................................2.17
Overview ......................................................................................................2.17
Address Books tab ...............................................................................2.17
Description of the Address Books Tab ....................................................2.17
Accessing the Personal Address Book Using the Web Directory Client ...2.18
Administration Client .................................................................................2.18
Managing links between the Directory and the PCX ................2.19
Configuring Links .......................................................................................2.19
Creating Links .............................................................................................2.20
Synchronizing Attributes in Real Time .....................................................2.24
Replacing Links ..........................................................................................2.27
Deleting Links .............................................................................................2.28
Following a Link between the Company and System Directories .........2.28
Interaction between the Directory and the Configuration ......................2.28
Interaction between the Directory and Accounting ................................2.32
System tab ...............................................................................................2.33
Overview ......................................................................................................2.33
Description of the System Tab ..................................................................2.33
Declaring a PCX Network ...........................................................................2.33
Registering an Eye Box .............................................................................2.49
Synchronizing PCX data .....................................................................2.51
Overview ......................................................................................................2.51
PCX to System Directory Synchronization ..............................................2.52
Synchronization Optimization ...................................................................2.56
Web Directory Client - Operation .....................................................2.57
Web Directory Client Overview .................................................................2.57
Connecting with a Browser .......................................................................2.57
The Web Directory Client Window ............................................................2.58
Logging in — Authentication ....................................................................2.59
Associating your Phone Set ......................................................................2.59
0-3
Browsing the Directory Tree .....................................................................2.60
Searching for a Directory Entry ................................................................2.60
Viewing Directory Entries ..........................................................................2.61
Printing Directory Entries ..........................................................................2.61
Viewing Detailed Information for an Entry ...............................................2.62
Making an Automatic Call ..........................................................................2.62
Sending an e-mail .......................................................................................2.63
Viewing your Personal Address Book ......................................................2.63
Creating a Personal Address Book Entry ................................................2.63
Deleting a Personal Address Book Entry .................................................2.64
Adding a Company Directory Entry ..........................................................2.64
Deleting a Company Directory Entry ........................................................2.64
Modifying a Directory Entry .......................................................................2.65
Modifying Attributes of a Company Directory Level ...............................2.66
Customizing the Search Filters .................................................................2.66
Customizing the Results Display and Print Parameters .........................2.67
Customizing the Detail and Edit Parameters ...........................................2.68
Selecting a Theme ......................................................................................2.68
Modifying a Theme .....................................................................................2.69
Web Directory Client - Configuration .............................................2.69
Configuring Sets for an Automatic Call ...................................................2.69
Fields for Automatic Dialing. .....................................................................2.70
Global Parameters ......................................................................................2.70
Managing prefixes ................................................................................2.71
Overview ......................................................................................................2.71
Management Rules .....................................................................................2.72
Detailed Examples ......................................................................................2.73
Appendix A: Using LDIF files ............................................................2.77
Overview ......................................................................................................2.77
Entries, Description ....................................................................................2.77
LDIF File Structure .....................................................................................2.80
Appendix B: Detailed structure of the LDAP directory ...........2.81
Overview ......................................................................................................2.81
List of Classes ............................................................................................2.82
List of SET Classes and Corresponding 4400 Objects ...........................2.82
Types of Attributes .....................................................................................2.83
0-4
Country Class (Country) ............................................................................2.83
City Class (City) ..........................................................................................2.83
Organization Class (Company) .................................................................2.84
OrganizationalUnit (Department) Class ....................................................2.85
InetOrgPerson Class (Person) ..................................................................2.86
GroupOfUniqueNames Class (Group) ......................................................2.88
Room Class (Room) ...................................................................................2.90
A4400User Class ........................................................................................2.91
Appendix C: LDIF Management Tools ...........................................2.92
Overview ......................................................................................................2.92
ConvertLdif .................................................................................................2.93
ExportLdap ..................................................................................................2.98
ImportLdap ..................................................................................................2.98
LinkDn .........................................................................................................2.99
PurgeLdap ...................................................................................................2.99
Ldif2Csv, Csv2Ldif ................................................................................... 2.100
ReplaceLdif ............................................................................................... 2.101
PurifyLdif ................................................................................................... 2.101
EncodeLdif ................................................................................................ 2.101
Examples ................................................................................................... 2.102
Chapter 3Section 3 Configuration
Overview .................................................................................................... 3.1
Overview ....................................................................................................... 3.1
Network tab .............................................................................................. 3.2
Preliminary steps ......................................................................................... 3.2
Network tab, description ............................................................................. 3.2
Connecting to a PCX ................................................................................... 3.3
Administering the Eye Box ......................................................................... 3.8
PCX tab ...................................................................................................... 3.9
0-5
Preliminary steps ......................................................................................... 3.9
Handling instances ...............................................................................3.14
Management commands ............................................................................3.14
Creating instances .....................................................................................3.15
Deleting/Moving instances ........................................................................3.17
Import/Export ..............................................................................................3.19
Troubleshooting .........................................................................................3.21
Saving/Restoring and Downloading with OmniPCX Office ....3.22
Preliminary steps ........................................................................................3.22
OmniPCX Office configuration preferences ............................................3.23
OmniPCX Office scheduled save ..............................................................3.26
Scheduled save of network/subnetwork OmniPCX Offices ...................3.26
OmniPCX Office scheduled restore ..........................................................3.27
Scheduled download of releases to a OmniPCX Office ..........................3.29
Scheduled download of releases for OmniPCX Offices in anetwork/subnetwork ...................................................................................3.30
Chapter 4Section 4 Accounting, VOIP and Performance Analysis
Overview .................................................................................................... 4.1
Overview ....................................................................................................... 4.1
Accounting ................................................................................................... 4.1
Traffic Analysis ............................................................................................ 4.1
Performance Analysis for Voice over IP ................................................... 4.2
Specific Menu .............................................................................................. 4.2
Terminology ................................................................................................. 4.2
Operating Principle ..................................................................................... 4.3
Pre-Configuration ........................................................................................ 4.3
Basic operation ....................................................................................... 4.5
Accounting Data Processing on the Alcatel-Lucent OmniVista 4760Network Management System Server ....................................................... 4.5
Different Uses .............................................................................................. 4.6
0-6
Accounting Processing Modes .................................................................. 4.6
Processing Accounting for Undeclared PCXs .......................................... 4.8
Different Call Costs ..................................................................................... 4.8
Specific Features of Multi-Carriers ...........................................................4.11
Accounting with the OmniPCX Office ......................................................4.13
Organization tab ....................................................................................4.14
Overview ......................................................................................................4.15
Tree Structure .............................................................................................4.17
Restricting Access to Organization Data .................................................4.22
Managing Organization Items ...................................................................4.22
History Criteria ............................................................................................4.25
Entry Properties ..........................................................................................4.26
Profiles ........................................................................................................4.28
Managing Mask Profiles .............................................................................4.29
Managing Cost Profiles ..............................................................................4.33
Managing Tracking Profiles .......................................................................4.37
Updating Costs in the Database ...............................................................4.44
Parameters tab .......................................................................................4.45
Overview ......................................................................................................4.45
Configuring Record Loading .....................................................................4.46
Configuring Total Accounting, Traffic Analysis, and VoIP PerformanceAnalysis Counter Calculation. ...................................................................4.51
Configuring Parameters Common to All Carriers ...................................4.53
Activating Calculation of Comparison Carrier Costs ..............................4.54
Viewing the Accounting Organization ......................................................4.54
Carriers tab ..............................................................................................4.55
Overview ......................................................................................................4.55
Removing a Carrier ....................................................................................4.72
Example of a Carrier Configuration ..........................................................4.73
Carrier Data Import and Export Commands ............................................4.73
Creating a Pulse Type Carrier. ..................................................................4.74
Database maintenance ........................................................................4.76
Overview ......................................................................................................4.76
Deleting Old Data Automatically ...............................................................4.76
Recommendations .....................................................................................4.77
Deleting Data Manually ..............................................................................4.77
0-7
Archiving/Restoring Records ....................................................................4.77
Scheduling Maintenance Tasks ................................................................4.79
Updating Accounting organization ...........................................................4.79
Managing carrier data files - EXPERT MODE ..............................4.80
Overview ......................................................................................................4.80
Accessing the Import and Export Commands .........................................4.81
File Description ...........................................................................................4.81
Carrier Description .....................................................................................4.93
Carrier Data Dependency ...........................................................................4.98
General Restrictions ..................................................................................4.98
Compatibility with Version 4715/4740 4.x ................................................4.98
Import Processing Duration ......................................................................4.99
Chapter 5Section 5 Reports
Use ............................................................................................................... 5.1
Overview ....................................................................................................... 5.1
Description ................................................................................................... 5.4
Data Access Restrictions ........................................................................... 5.7
Copying a Report Definition ....................................................................... 5.7
Modifying a Report Definition .................................................................... 5.8
Exporting/Importing a Report Definition ................................................... 5.8
Generating a Report .................................................................................... 5.8
Generating an Unmasked Report. .............................................................. 5.9
Interrupting Report Generation .................................................................. 5.9
Scheduling Report Generation ................................................................... 5.9
Scheduling Report Generation for a Customer List ................................5.10
Displaying a Report on the Screen ...........................................................5.11
Report Export Options ...............................................................................5.13
Creating a Customized Definition .............................................................5.14
Using Templates .........................................................................................5.36
Configuring the Server for Network Export Scheduling .........................5.38
0-8
Using Multi-Language Reports .................................................................5.39
Predefined accounting reports ........................................................5.40
Types of Reports ........................................................................................5.40
List of Predefined Reports .........................................................................5.40
Database Fields (Headers) .........................................................................5.42
Report Presentation (Examples) ...............................................................5.52
Predefined traffic analysis reports .................................................5.75
Report Contents .........................................................................................5.75
List of Predefined Reports .........................................................................5.80
Database Fields (Headers) .........................................................................5.83
Report Presentation ................................................................................. 5.104
Predefined threshold exceeded reports ..................................... 5.160
Overview .................................................................................................... 5.160
List of predefined reports ........................................................................ 5.160
Database fields (headers) ........................................................................ 5.160
Report presentation ................................................................................. 5.162
Predefined Audit Reports ................................................................. 5.166
Predefined Detailed Report ..................................................................... 5.166
Predefined Total Reports ......................................................................... 5.166
Predefined VoIP reports .................................................................... 5.168
Overview .................................................................................................... 5.168
Definitions ................................................................................................. 5.169
List of predefined reports ........................................................................ 5.170
Database Fields (headers) ....................................................................... 5.171
Report presentation ................................................................................. 5.173
Predefined reports on alarms and events .................................. 5.188
List of predefined reports ........................................................................ 5.188
Database fields (headers) ........................................................................ 5.188
Report presentation ................................................................................. 5.190
Chapter 6Section 6 Alarms
0-9
Overview .................................................................................................... 6.1
Alarm Management: General ...................................................................... 6.1
Specific Menu .............................................................................................. 6.2
Terms Used .................................................................................................. 6.2
Setting reception parameters ............................................................ 6.4
Licenses ....................................................................................................... 6.4
Setting PCX Alarm and Event Reception Parameters .............................. 6.4
Configuring Centralized Alarms for a Network Node ............................... 6.5
Configuring Alarms (Incidents) Filtering on a PCX .................................. 6.6
Viewing alarms ........................................................................................ 6.7
Overview ....................................................................................................... 6.7
Alarm counters ............................................................................................ 6.8
Browsing from trees .................................................................................... 6.9
Browsing from the data field .....................................................................6.10
Filtering .......................................................................................................6.14
Managing alarms ...................................................................................6.15
Requirements ..............................................................................................6.15
Acknowledging an alarm ...........................................................................6.15
Signing an alarm .........................................................................................6.16
Clearing an alarm .......................................................................................6.17
Deleting a branch .......................................................................................6.18
Configuring Alarm Application ........................................................6.19
Configuring Alarm Cleaning ......................................................................6.19
Setting List Size ..........................................................................................6.20
Requesting an Audio Signal for an Alarm or Event ................................6.20
Adding a Predefined Signature or a Predefined Action ..........................6.20
Modifying a Predefined Signature or a Predefined Action .....................6.21
Deleting a Predefined Signature or a Predefined Action ........................6.21
Defining Action Taken on Alarm Reception .............................................6.21
Filtering Alarms to Send SNMP Traps ......................................................6.29
0-10
Chapter 7Section 7 Topology
Overview .................................................................................................... 7.1
Overview ....................................................................................................... 7.1
Description of the interface ........................................................................ 7.1
The two display views ................................................................................. 7.4
Network component symbols .................................................................... 7.6
Managing custom views ............................................................................. 7.8
Graphic coding of alarms ..........................................................................7.12
Chapter 8Section 8 Scheduler
Overview .................................................................................................... 8.1
Overview ....................................................................................................... 8.1
Description of the interface ........................................................................ 8.1
Predefined and current jobs ....................................................................... 8.3
Jobs to schedule after installing the Server ............................................. 8.4
Execution process ....................................................................................... 8.4
Execution reports ........................................................................................ 8.5
Managing scheduled operations ................................................................ 8.6
Scheduling parameters ............................................................................... 8.8
Copy a task in order to customize it .........................................................8.10
Customizing the scheduler ........................................................................8.10
Chapter 9Section 9 Maintenance
0-11
Maintenance ............................................................................................. 9.1
Overview ....................................................................................................... 9.1
Alcatel-Lucent OmniVista 4760 Network Management SystemMaintenance ................................................................................................. 9.3
OmniPCX 4400/Alcatel-Lucent OmniPCX Enterprise CommunicationServer Maintenance ..................................................................................... 9.5
Purging Operations ....................................................................................9.10
Software Update .........................................................................................9.11
Software Update Status .............................................................................9.19
Configuring Settings ..................................................................................9.20
Chapter 10Section 10 Audit
Overview ...................................................................................................10.1
Overview ......................................................................................................10.1
Configuration procedure ....................................................................10.1
License ........................................................................................................10.1
Audit Application Configuration ...............................................................10.2
Audit Alcatel-Lucent OmniPCX Enterprise CS Configuration ................10.4
Audit Manager Access Rights ...................................................................10.5
Retrieving Audit Information .............................................................10.6
Overview ......................................................................................................10.6
Alcatel-Lucent OmniPCX Enterprise CS Audit Files ...............................10.6
Retrieving Audit Data .................................................................................10.7
Displaying Audit Information ............................................................10.9
Audit Graphical User Interface Access ....................................................10.9
PCX Tree .................................................................................................... 10.10
Mao Grid .................................................................................................... 10.10
Mao Detail Information ............................................................................. 10.11
Filtering ..................................................................................................... 10.12
0-12
Audit Information from the Configuration Application ......................... 10.14
Maintenance .......................................................................................... 10.15
Purging Audit Records from Database .................................................. 10.15
Exporting Log Information ...................................................................... 10.15
Save and Restore of Audit Database ...................................................... 10.16
Chapter 11Section 11 SIP Manager
Overview ...................................................................................................11.1
Overview ......................................................................................................11.1
Preliminary Operations ..............................................................................11.1
Accessing the SIP Manager Application ..................................................11.4
SIP Manager Application Main Window ...................................................11.4
Additional SIP Features in the Alcatel-Lucent OmniVista 4760 NetworkManagement System Main Window ..........................................................11.9
Interaction with the Configuration Application ..................................... 11.10
Operations ................................................................................................. 11.10
Chapter 12Section 12 Security
Overview ...................................................................................................12.1
Overview ......................................................................................................12.1
Administrator Accounts .............................................................................12.1
Access Groups ...........................................................................................12.1
Manager Accounts .....................................................................................12.7
Application Access Rights ........................................................................12.8
Managing User Accounts ........................................................................ 12.11
RADIUS Server .......................................................................................... 12.15
Special Operations ................................................................................... 12.22
0-13
Securing Access to the OmniPCX 4400 / OmniPCX Enterprise ........... 12.25
Securing Access to the Alcatel-Lucent OmniVista 4760 NetworkManagement System ................................................................................ 12.30
0-14
1.1 Overview
1.1.1 Overview
Alcatel-Lucent OmniVista 4760 Network Management System (called Alcatel-LucentOmniVista 4760 Network Management System in this document) is a set of managementapplications for a PCX network based on a client-server architecture and an LDAP directory(based on Sun ONE Directory Server). :
- Alcatel-Lucent OmniPCX Enterprise Communication Server
- Alcatel OmniPCX 4400
- Alcatel-Lucent OmniPCX Office Communication Server
Note 1:
As of Alcatel-Lucent OmniVista 4760 Network Management System R5.0, Alcatel Office is not supported.
Note 2:
See § Compatibility .
Alcatel-Lucent OmniVista 4760 Network Management System is modular and may include allor some of the following internal applications depending on the licenses installed:
See § Internal applications .
Internal applications requiring a license:
- Company directory (Web directory client, company directory entry, etc.). See § Webdirectory clients .
- Configuration – § Configuration .
- Accounting and Tracking * – § Accounting .
- Traffic analysis and VoIP traffic analysis*– § Traffic analysis/VOIP .
- Accounting, Traffic analysis, VoIP traffic analysis and alarm reports – § Reports .
- Alarms and Topology * – § Alarms and § Topology .
- Audit - § Audit
- SIP Management - § SIP Manager
Notes:
Tracking is an option of the Accounting application.
Topology is an option of the Alarms application.
Internal applications available with any license:
- System directory – § Directory administration .
- Scheduler – § Scheduler .
- Maintenance – § Maintenance .
- Security – § Security .
1
1-1
Alcatel-Lucent OmniVista 4760 Network Management System can also be used to launchexternal applications:
- Remote applications via a Web browser (for example: the URL for OmniTouch UCadministration).
- Executable files (for example: a word processor program).
See § External applications .
Highlights:
- User manager:Access rights can be customized for each administrator and user. According to their rights,users can access applications directly from their workstation:• Via the corporate LAN/WAN network• Via an Web browser (Intranet only)
- An LDAP standard directory:Alcatel-Lucent OmniVista 4760 Network Management System includes an LDAP directory,based on Sun ONE Directory Server. Directory data is automatically synchronized withnetworked OmniPCX 4400 and Alcatel-Lucent OmniPCX Enterprise CS data.Corporate users can view the Web directory client via a browser.
- Data broadcast:Reports and alarms can be sent to an e-mail address.Reports can be printed on a network printer.
1.1.2 Client-server architecture
The Alcatel-Lucent OmniVista 4760 Network Management System server runs on a Windowsplatform. See § Compatibility .
Chapter 1
1-2
Figure 1.1: Alcatel-Lucent OmniVista 4760 Network Management System Client — serverarchitecture
Configuration 1 - ServerThe Alcatel-Lucent OmniVista 4760 Network Management System server application installedon a server provides client PCs with database access. The server establishes connections tothe PCX network and contains the database required for PCX administration.To guarantee uninterrupted access, the server must remain permanently in service.Although the Omnivista 4760 client application is installed on the server, the application doesnot have to remain open on the server to provide clients with access.
If the Alcatel-Lucent OmniVista 4760 Network Management System server is of release 4.1and higher, the 4760 clients connecting to that server must be of release 4.1 or higher.
Configuration 2 - ClientsClient PCs access server resources via the LAN or WAN network. The Alcatel-LucentOmniVista 4760 Network Management System application installed on the client PC providesaccess to the database installed on the server. Network administration can be performed on allclient PCs, depending on user rights. If the 4760 client is of release 4.1, it can only beconnected to a server of release 4.1 or higher.
Configuration 3 - Clients via IntranetAdministrators can access server resources from any PC using a browser. By entering theserver address (URL) in the browser, you can access the Alcatel-Lucent OmniVista 4760Network Management System home page. Network administration can be accessed from thispage. The first time the administrator connects, server name and release are noted. A Javaplug-in must also be installed during the initial connection. This is the only software required tobe installed on the PC.
Configuration 4 - Clients - Web directory client (available subject to license)Corporate users can access the Alcatel-Lucent OmniVista 4760 Network Management Systemserver home page via a browser from any PC. The Web directory client can be viewed from
1-3
this page.Enter the server address (URL) in the browser.
1.1.3 Compatibility
table 1.1: Alcatel-Lucent OmniPCX Enterprise CS CompatibilityRelease 4760 Release PCX Software version equal
to or higher thanIP or IP/X25connection
PPPconnection
1.5 3.0 C1.532.5.w (exceptSTAP)
Yes No
1.5 3.2M C1.712.5.c, C1.714.3.a Yes Yes
1.5 1 3.2 C2 C1.762.2 Yes Yes
1.5 4.1 D1.305.4.f Yes Yes
1.5 4.1.1 D1.311.7.d Yes Yes
1.5 4.2.1 D2.304.4.s Yes Yes
2.0 5.0Ux D2.313.7.f Yes Yes
2.0 5.0.1 Ux D2.314.7.p Yes Yes
2.0 5.0 Lx E1.604.9.t Yes No
2.1 5.1 E2.404.u Yes No
2.1 5.1.1 E2.502.2.p Yes No
2. 5.1.2 E2.504.1.ai Yes Yes
3.0 6.0 F1.602.3.i Yes No
3.0 6.0.1 F1.603.1.l Yes Yes
3.1 6.1 F2.500.6.g Yes No
3.1 6.1.1 F2.502.12 Yes Yes
3.2 6.2 F3.301.36 Yes Yes
4.0 7.0 F4.401.13 Yes Yes
4.1 7.1 F5.401.7 Yes Yes
4.2 8.0 G1.302.5 Yes Yes
5.0 9.0 h1.3xx Yes Yes
table 1.2: OmniPCX Office CompatibilityReleases Software version equal to
or higher thanIP connection PPP connection
1.0 Not supported No No
1.1 1.0.19.06 Yes Yes
2.0 2.0.32.013 Yes Yes
2.1 210.083.001 Yes Yes
3.0 300/19.1 Yes Yes
3.1 310/038.001 Yes Yes
4.0 400/022.001 Yes Yes
Chapter 1
1-4
Releases Software version equal toor higher than
IP connection PPP connection
4.1 410/015.005 Yes Yes
5.0 500/030.004 Yes Yes
5.1 510/017 Yes Yes
6.0 600/014.001 Yes Yes
X: supported
table 1.3: Operating system compatibilityOmnivista 4760 Release
R4.1 - R4.2 - R5.0
Operating Systems Server Client
Windows 2003 ServerSP1/SP2 standard edition X X
Windows 2003 R2 X X
Windows Vista X X
Note:
64 bits Windows operating systems are not compatible with Alcatel-Lucent OmniVista 4760 Network
Management System server and Alcatel-Lucent OmniVista 4760 Network Management System client.
1.1.4 Internal applications
1.1.4.1 Directory administration
– module Directory - Overview
Directory administration is only accessible to users with the appropriate access rights.
Depending on your rights, this application allows you to:
- Access the company directory.
- Perform searches.
- Modify data.
- Import/export directory files.
Main features:
- Tree structure corresponding to company organization:• Branch (1st sublevel): country, city, company, department.• Leaf (2nd sublevel): person, group, room.
- Create persons in the directory from PCX telephone extensions.
- Create links between several extensions and one person (wired lines, DECT/PWT, fax,etc.):• Link created automatically if name and first name are identical.• Manual creation in other cases.
1-5
- Cost center update for all the extensions of a person from the individual's directory record.
- Direct access to extension Configuration.
- Import/Export in LDIF format:• Import/Export scheduling.• Download new and modified entries (import).• Export selected entries from the tree.
- Export in .txt format.
- Apply cost center changes made on the PCX.
1.1.4.2 Web directory clients
– module Directory - Web Directory Client - Operation
Corporate users can access the Web directory Client with an Internet browser.
This application allows access to the company directory.
Main features:
- Access with a browser.
- There are two types of connection:• Anonymous (rights limited to view and search in the green list).• Login and password (access to certain features dependent on rights: record
modification, green list, orange list, red list).
- Predefined groups for access rights.
- Multi-criteria search.
- Two display modes (list and record).
- Automatic dialing.
- Personal address book.
- Customizable interface.
1.1.4.3 Configuration
– module Configuration - Overview
The Configuration application is used to configure and manage PCXs declared in the SystemDirectory. For example, authorized users can set the items (users, for example) containedwithin PCX objects.
Main features:
- Networks, subnets and PCXs shown in tree form.
- One or more PCXs can be simultaneously configured.
- Automatic management of the MIB.
- Management of access rights.
Chapter 1
1-6
- Specify advanced search criteria to filter items.
- List of free equipment addresses for the Z and UA interfaces.
- List of available directory numbers.
- Object model local save.
- Access the OmniPCX 4400/Alcatel-Lucent OmniPCX Enterprise CS via Telnet or SSH.
- Direct access to other applications: Directory, Alarms, Accounting.
1.1.4.4 Accounting
– module Accounting - Overview
The Accounting and Traffic analysis applications are grouped within the same interface andaccessed by the icon in the application toolbar.
The Accounting application collects accounting records ("tickets") from PCXs to:
- Ensure calculation and correct distribution of call costs to the chargeable entries in theOrganization.
- Monitor costs, durations, carrier use, etc.
The Organization appears as a tree structure organized by cost centers. It shows acompany's Accounting and groups all its chargeable entries (extensions, attendants,projects, etc.).
The main features of the Accounting application are:
- Generation of reports from Accounting records and Traffic analysis counters.
- Managing the Organization
- Ensuring costs are correctly assigned
- Tracking, to check use of chargeable entries (number of calls, cost, duration)
- Managing the Carrier (tariffs used, regions, directions i.e. destinations, tariffs i.e. rates)
- Managing extension subscriptions
- Managing billing rules for calls and associated services (ISDN, subscriptions)
- Managing data masking rules to guarantee the confidentiality of information.
Tools for editing, formatting and generating accounting reports are grouped in the Reportsapplication.
1.1.4.5 Traffic analysis/VOIP
– module Accounting - Overview
The Accounting and Traffic analysis applications are grouped within the same interface,represented by the icon.
The Traffic analysis application uses traffic analysis counters, accounting records, and VoIP
1-7
records provided by PCXs for traffic monitoring and tracking:
- Trunk groups
- Extensions
- Attendants
- DECT/PWT sets
- IP devices
- etc.
For performance reasons, extension tracking is not enabled by default.
The main features of the Traffic analysis application are:
- Generation of reports from Traffic analysis counters and Accounting records to allowtraffic data to be correctly assigned.
- Management of the Organization (tree structure shared with that of Accounting).
- Configuration of Analysis (days, time periods and cost centers tracked).
The Report application contains tools to generate, format, and print Traffic analysis reports.
1.1.4.6 Reports
– module Reports - Use
The Reports application is dedicated to management of Accounting, Traffic analysis, andVoIP traffic analysis reports and Alarm statistics:
- Design
- Generation
- Print reports
Reports are generated from records in the database.
The Reports application includes:
- A tree structure with default report templates and definitions that meet most requirements.
- A Query tool, a graphical interface to select, sort and calculate the data used for reports.
- A Designer with graphical tools to format and aid presentation of reports.
Masking rules ensure call data confidentiality.
Report generation can be scheduled. Printing and forwarding by E-mail can also be scheduled.Data contained in accounting reports has no legal value.
1.1.4.7 Alarms
– module Alarms - Overview
The Alarm application allows authorized persons to manage:
- PCX alarms and events.
- Alarms generated by the different Alcatel-Lucent OmniVista 4760 Network ManagementSystem applications.
Chapter 1
1-8
The Alarm application runs as a background task. You can schedule actions to be performedwhen specific alarms are received (for example: major severity):
- Emit audio signal.
- Send E-mail.
- Run a script.Main display features:
- Detailed display of alarms and events received.
- Color code indicating alarm severity level.
- Counters of active alarms according to their severity.
- Real-time update of alarm status changes (for all connected clients).
- Alarm and event list size can be configured.
- Display of alarms and events for a specific object.
- Access object configuration from a generated alarm.
- Multi-criteria search.
- Indication of alarm type and probable cause.
- Diagnosis help.
- Alarms and events in the same language as the source PCX.
- Application alarms in the language selected at installation.Main management features:
- Programmed actions triggered on alarm reception (send E-mail, run script).
- Access rights configured according to the user profile. Action rights that can be heldconcurrently and configured for each user profile (acknowledge, delete and/or clear).
- Automatic correction of correlated alarms.
- Record the name of the operator in charge, the status and the date of the alarm along withthe action taken and remarks (if any).
- Broadcast of updated alarms to all Alcatel-Lucent OmniVista 4760 Network ManagementSystem server clients.
- Printout, formatting and presentation of reports on alarm statistics grouped in the Reportsapplication.
1.1.4.8 Topology
– module Topology - Overview
The Topology application, an option for the Alarms application, is used to:
- Locate alarms in the network topology.
- View shelves and boards referred to by an alarm.
- Filter alarms associated with the selected item (PCX, boards, Alcatel-Lucent OmniVista4760 Network Management System applications).
- Target PCX correlated alarms.
1-9
- Configure a topology customized to your requirements (create network items, reroute andfilter alarms).
1.1.4.9 Scheduler
– module Scheduler - Overview
This application runs scheduled tasks, including:
- Alcatel-Lucent OmniVista 4760 Network Management System operation and maintenance,for example,• Synchronization of information between PCXs and the server database.• Generate Accounting and Traffic analysis reports.• Recalculate accounting costs.• Delete obsolete data from the database.
- Run tasks external to Alcatel-Lucent OmniVista 4760 Network Management System (forexample, anti-virus or archiving programs).
Tasks can be grouped as a job. Task and job layout determines whether execution issimultaneous or sequential (performed one by one).
1.1.4.10 Maintenance
– module Maintenance - Maintenance
This application contains all predefined maintenance tasks required for Alcatel-LucentOmniVista 4760 Network Management System and networked PCX operation:
- Save/Restore the Alcatel-Lucent OmniVista 4760 Network Management System database.
- Download and save Alcatel-Lucent OmniPCX Enterprise CS and OmniPCX 4400 data.
- Restore Alcatel-Lucent OmniPCX Enterprise CS and OmniPCX 4400 data.
- Database defragmentation.
- Restart the Alcatel-Lucent OmniVista 4760 Network Management System application(NMC service).
- Launch OmniPCX 4400 \ Alcatel-Lucent OmniPCX Enterprise CS software updates.
Maintenance operations can be programmed with the Scheduler.
1.1.4.11 Audit
- module Audit - Overview
As of R5.0, the Audit application allows to display management operations performed on anAlcatel-Lucent OmniPCX Enterprise CS, supervised by the Alcatel-Lucent OmniVista 4760Network Management System.
With the Audit application, the security manager has a complete view of all configuration andmaintenance operations performed on the Alcatel-Lucent OmniVista 4760 NetworkManagement System network.
Chapter 1
1-10
1.1.4.12 SIP Manager
- module SIP Manager - Overview
As of R5.0, the SIP Manager application, provides a user graphical interface enabling SIPdevices commissioning and daily maintenance. This application allows to deploy quickly alarge quantity of SIP devices from the same application.
The SIP Manager application enables:
- To configure SIP devices
- To configure SIP users
- To assign one or several SIP devices to a SIP user (i.e. SIP device attachment list)
1.1.4.13 Security
– module Security - Overview
This application, exclusively reserved to administrators, allows user access rights forapplications to be managed. As a result, when a session is opened, User A may have accessto the Accounting and Reports applications and User B may have access to all applications.
1.1.5 External applications
– module Directory - System tab § Creating Applications Groups and External
Applications
External applications may be launched from the Alcatel-Lucent OmniVista 4760 NetworkManagement System.
External applications can be specified in the form of:
- URLs (in this case, the default Web browser is launched).
- Executable files.
The ability to launch external applications is a feature of the Alcatel-Lucent OmniVista 4760Network Management System.A security policy may be implemented to restrict access to this feature (see module Security -Overview ).These applications do not require a license.
1.2 Startup and Shutdown
1.2.1 Starting Alcatel-Lucent OmniVista 4760 Network Management System
1. Start Alcatel-Lucent OmniVista 4760 Network Management System using one of thefollowing two methods:• From the operating system Start menu: Start > Programs > OmniVista 4760 >
OmniVista 4760 Client. The Client module must already be installed on theworkstation to use this method.
1-11
• From a browser: In the address bar, type http://OmniVista 4760 server name. Thehome page offers access to the Web Directory Client and Network Management. Clickthe Network Management icon.
2. Open a session by completing the fields in the OmniVista 4760 access window:• User name: provided by the Alcatel-Lucent OmniVista 4760 Network Management
System administrator.• Password: provided by the network administrator.• Language: select the interface language.
Note 1:Last used language is the language selected for the previous session.
Note 2:Languages that appear in italics in the Language list are used only in generating reports. The in-terface language will be the language selected when the server was installed.
• Server name: modify the name if you want to access a different server.• Remember password: Check this box to save your login information including your
password, on the local personal computer. Your login information is saved and usedduring your next connection to the Alcatel-Lucent OmniVista 4760 NetworkManagement System client.Click OK. The application bar is displayed. The access and usage restrictions for thevarious applications, depend on the rights assigned to your account.
3. If this procedure fails, a dialog box is displayed:a. Unable to locate the servers:
• Click OK to close the dialog box.• Check Alcatel-Lucent OmniVista 4760 Network Management System server
access or contact your Alcatel-Lucent OmniVista 4760 Network ManagementSystem administrator.
b. Incorrect password or account:• Click OK to close the dialog box.• Enter your name and password again.• Click OK. If the problem persists, contact your Alcatel-Lucent OmniVista 4760
Network Management System administrator.c. Warning dialog box with problem description:
• Note the faulty application.• Click OK and contact the Alcatel-Lucent OmniVista 4760 Network Management
System administrator.• If the situation that caused the warning message is expected to continue, you can
check the box to mask the message in the future.d. Error dialog box with problem description:
• Note the faulty application.• Click OK and contact the Alcatel-Lucent OmniVista 4760 Network Management
System administrator.• The client works in restricted mode: Only the Directory application is available in
order to fix the problem.e. Expired license:
• Click Cancel and contact the Alcatel-Lucent OmniVista 4760 NetworkManagement System administrator.
Chapter 1
1-12
• The Alcatel-Lucent OmniVista 4760 Network Management System works inrestricted mode. The Directory application is the only application available andmust be used to fix the problem.0
f. Maximum number of clients exceeded dialog box:• The list of the connected clients is displayed.• Click OK.• Contact one of the managers to get a token and retry later.
1.2.2 Logging off
For security reasons, when you leave your workstation, it is advisable to log off to remove therights assigned. Logging on under a different name or with a different language closes allrunning applications.
To log off:
1. Click the icon in the application toolbar. The Omnivista 4760 access window is
displayed.You can now:• Either, close the current session and open another one by entering a different user
name.• Or, close the session by leaving the fields empty and clicking OK.
2. Click OK.
1.2.3 Exiting Alcatel-Lucent OmniVista 4760 Network Management System
- In the Client application, select the command, Files > Exit.
- In a browser, close the browser window.
Note:Operations programmed in the Alcatel-Lucent OmniVista 4760 Network Management System sched-uler are centralized on the server. To ensure their execution, the server PC must remain in service.
If a client performs a local import from his PC to the server, the Alcatel-Lucent OmniVista 4760 Net-work Management System application must be running on the client PC.
1.3 Main window
1.3.1 Main window, overview
Alcatel-Lucent OmniVista 4760 Network Management System makes full use of themulti-windowing concept to make the simultaneous use of several applications easier.
1-13
Figure 1.2: Alcatel-Lucent OmniVista 4760 Network Management System main window
Applications are divided into groups: Internal applications (4760 App. button) and externalapplications (Other App. button).
Note:
If no external application has been created, the 4760 App. and Other App. group buttons are not dis-
played in the graphical interface.
For more information about creating application groups and external applications, see moduleDirectory - System tab § Creating Applications Groups and External Applications .
1.3.2 Starting applications
You can start an application by using any one of three different methods:
- In the Applications menu, select the group of applications, then the application you wantto launch. This launch method allows the same application to be launched several times.
- In the application launch panel:1. Click the group of applications.
The applications in the group are immediately displayed below the application groupbutton.
2. Click the corresponding icon in the application launch panel.
Chapter 1
1-14
This launch method does not allow the same application to be launched several times.
- In the application toolbar, position the cursor on the icon and select the Start commandfrom the shortcut menu (right-click). Note that the application security manager can also beaccessed from this same shortcut menu.This launch method allows the same application to be launched several times.
To switch from one application to another, use one of the following two methods:
- In the application bar at the bottom of the screen, click the application's icon.
- In the Window menu list, click the application's name. The selected applicationautomatically switches to the foreground.
Note:
External applications are launched in separate windows as they are not linked to the Alcatel-Lucent Om-
niVista 4760 Network Management System client application.
1.3.3 Using menus
The menu bar of the main window includes the following commands.
table 1.4: Main window menuMenu Function
File Exit closes the Alcatel-Lucent OmniVista 4760 NetworkManagement System application
Applications Starts an application
Security Defines access rights for applications
Preferences - Framework• Saves application layout settings• Configures status bar
- Change Password• Allows you to change the currently used password
Preferences > Scheduler - User• Show only my jobs when enabled displays only your
own jobs.- Configuration sets task and schedule related preferences.For more information refer to:module Scheduler - Overview § Customizing the scheduler .
Preferences >Maintenance
Configuration defines file location, thresholds and record life for4760 and PCX backup/restore operations, temporary files andsoftware update.
Preferences > Alarms - Configuration sets default display mode for alarms byconfiguring parameters such as review history, audio signalfor notification, alarm list size and event list size.
- SNMP Filter filters alarms retransmitted as SNMP traps.- Alarm Filter configures sending of an E-mail or running of a
script when an alarm is detected.
1-15
Menu Function
Preferences >Configuration
- Access profile enables you to define the access level to thePCX, when connected to the OmniPCX 4400/ Alcatel-LucentOmniPCX Enterprise CS. The modified access level isapplicable for all the PCXs accessed by the Alcatel-LucentOmniVista 4760 Network Management System client.
- Object model save manages the list of PCX object modelfiles that are used to increase the access speed to the PCX.
- OXO Preferences manages the parameters for the OXOscheduled tasks, shared directory, backup/ restore directoryand software update directory.
Preferences > Audit Audit List Size enables you to define the size of audit list.
Accounting/Traffic/VoIPSpecific toAccounting/Traffic/VoIP
- Archive records archives records from the date of previousarchiving operation.
- Restoring records restores the records specified usingSearch command.
- Purging deletes the specified records.- Compute cost recalculates costs or subscriptions for
exceptional processing.- Total calculation updates total counters.- Detecting Exceeded Thresholds configures tracking
thresholds and applies them to Organization entries.
Window - Manages all running application windows:• Minimize all• Tile horizontally• Tile vertically• Cascade
- Enables to access one of the running applications.
Help - General help provides help for all the available applications.- Help - application name provides help for the current
application.- Help - Omni PCX provides help for Alcatel-Lucent OmniPCX
Enterprise CS management.- About lists the available applications along with the number
of users currently using the application and the licensednumber of users and the current releases of the server andclient.
- Connected client(s), lists the details such as host name, IPaddress, user name and login of the clients connected to the4760 server.
Action (specific to theDirectory)
Find locates the entry displayed in the grid, in the directory tree.
1.3.4 Sizing panels
Panels can be sized by:
- Dragging the border with the mouse.
- Using the sizing selector handles. These are two triangles located on the border:
Chapter 1
1-16
table 1.5: Main window sizing selectorsSelector Function
- If the panel is reduced: clicking displays the panel with the last sizeselected.
- If the panel is open: clicking displays the panel over the entire widthof the window.
- If the panel occupies the entire window: clicking returns it to the lastsize selected.
- If the field is open with the last size selected: clicking minimizes thepanel.
- Using the size icons in the icon bar:
table 1.6: Main window sizing selectors in the icon barSelector Function
Display/Minimize the application bar.
Display/Minimize data and search panels to show the tree.
Display/Minimize the tree panel.
Display/Minimize the search panel to show the data panel.
Display/Minimize the data panel to show the search panel.
1.3.5 Application-specific icons
Each Alcatel-Lucent OmniVista 4760 Network Management System application has specificicons. The function of each of these icons is described in the section on the relevantapplication.
1.4 Viewing data
1.4.1 Browsing the tree structure
1.4.1.1 The tree structure
The data area on the right side of the Alcatel-Lucent OmniVista 4760 Network ManagementSystem window displays detailed information on the items(s) selected in the tree on the leftside of the window.
Example tree structure:
1-17
Figure 1.3: Tree structure
The numbers in brackets are the number of items located directly below.In the above example, the Alcatel company has three direct sub-items (S1, Service (dept.) Aand Soher Larry).
1.4.1.2 Expanding/Collapsing the tree
Click to expand branches. If there are too many entries (list of a PCX's cost centers, forexample), you can reduce the number displayed by using a filter. The filter feature can beaccessed (in some applications) using the shortcut menu of the branch to be expanded.
Click to collapse branches.
1.4.1.3 Browsing in the data field
Use the arrow to select the previous entry.
Use the arrow to select the following entry.
Use the PgUp and PgDn keys to reach the top and bottom of the list.
1.4.1.4 Refreshing
When data has been edited, the display may need to be refreshed. There are several ways todo this:
- Select the Refresh command from the shortcut menu of any entry in the tree.
- Collapse, then expand the root,
- Click the refresh icon (depending on the application).
1.4.1.5 Progress icons
: Progress bar showing the number of items downloaded. To stop downloading,
click the cross located to the right of the progress bar. Data already downloaded is displayedon-screen.
1.4.2 Displaying data
1.4.2.1 Selecting items in the tree and displaying data
Click an item in the tree to select an entry in the tree. Its record is displayed in the data area.
Chapter 1
1-18
To select several adjacent entries
1. Select an entry (start selection).
2. Press the Shift key and keep it pressed down.
3. Select another entry (end selection). A table containing all the selected entries is displayedin the data area.
To select several non-adjacent entries
1. Select an entry.
2. Press the Ctrl key and keep it pressed down.
3. Select the other entry/entries. Each new entry selected is added to the selection table.
1.4.2.2 Locating an entry in the tree
You can locate an entry displayed in the data area in the tree. This feature can be useful tolocate an item found by searching (search result) in the tree.
1. To obtain a clearer view of the selected entry, fully collapse the tree.
2. Select an entry in the data area (table or record).
3. Click the icon. The upper level branches are expanded and the desired entry is
displayed in the tree.The Configuration also offers this command via the Action menu.
1.4.2.3 Records and tables
The data area has two display modes:
- Records: attributes are in lines.
- Tables: attributes are grouped in columns, entries in lines. The first column shows thenumber of lines.
Click the icon to switch between modes.
1.4.2.4 Attribute tab
To simplify the editing of some values, attributes are grouped by tabs.
In the Company directory, an Individual (person) type entry contains the groups:
- Individual
- Organization
- Personal
- Miscellaneous
- OmniPCX resources
In Configuration, in online (connected) mode, the All tab groups all attributes also displayedin other tabs.
1.4.2.5 Filtering attribute display
Some applications offer filtering in the tree that enables the number of attributes displayed tobe limited. By applying a filter, you can significantly reduce loading time and optimize datahandling operations. Filters can be applied in table and record modes and be used to:
1-19
- Expand a directory branch containing several hundred entries.
- Modify a limited number of Directory entries.
- Display PCX cost centers in Configuration.
- ...
1.4.3 Configuring columns
1.4.3.1 Sizing the columns of a table
You can adjust column width using the mouse at any time:
1. Place the cursor on the column border. The shape of the cursor changes.
2. Move the border by dragging with the mouse.
3. Release at the desired location. The column is resized.
1.4.3.2 Sorting in a table column
You can sort the data contained in each column in ascending or descending order. Open theshortcut menu by right-clicking the column header, then:
- Select the Sort > ascending command to sort in ascending order.
- Select the Sort > descending command to sort in descending order.
1.4.3.3 Freezing/Unfreezing
To view data while continuing to scroll through the contents of a record, you can use theFreeze feature. Frozen data does not scroll and remains displayed while you scroll through therest of the record.The Freeze command keeps part of the display on the screen while you read other data. In atable, the Freeze and Unfreeze commands are applied to specific columns of the data area.In records, these commands apply to specific lines of the data area.To freeze part of a table:
1. Select a column.
2. Place the cursor on the column header.
3. Select the Freeze command from the shortcut menu.
The column is moved to the left, following the identification attributes column.
You can now scroll through other (unfrozen) columns using the horizontal scroll bar.To freeze in a record:
1. Select a line.
2. Place the cursor on the first cell in the line.
3. Select the Freeze command from the shortcut menu.
The line is moved up, following the identification attributes line.
You can now scroll through other (unfrozen) lines using the vertical scroll bar.
The values displayed in a frozen line or column can be modified.To unfreeze:
Chapter 1
1-20
1. Select the frozen line(s) or column(s).
2. Place the cursor on the first cell in the line or on the column header.
3. Select the Unfreeze command from the shortcut menu.
1.4.4 Printing \ Exporting
1.4.4.1 Printing
1. Click the icon to open the printing window.
2. Configure and start printing.
1.4.4.2 Exporting in a text file
1. Click the icon to open the printing window.
2. Configure and Click the "Text Export" button to export in a text file.
1.5 Data search
1.5.1 Using the search area
Figure 1.4: Data search area
To perform a search, you must:
1. Complete the search area, specifying:• What you are looking for (Search).• In which domain you want to perform the search (In).• Any search criteria desired (Where).
2. Launch the search with one of the following icons:• launches a search and displays the results in the data area.
• launches the search and adds the results to that of the previous search.
1-21
1.5.1.1 Searching
The Search field contains a list of the types of entries on which a search can be performed.
Select a type of entry in the list.
Example:
- For the Accounting application (Organization tab): User, cost center, record entity, etc.
- For the Directory application (Company tab): Person, group, room, city, country,department, company.
- For the Configuration application• in offline (disconnected) mode (Network tab): Alcatel-Lucent OmniPCX Enterprise CS,
OmniPCX Office, OmniPCX 4400.• in online (connected) mode (PCX tab): Users, interface board, etc.
"Configuration" is a special case, because, in online (connected) mode, you canalso:• Click to select the type of entry by category from the following window:
Figure 1.5: Class selection window
• Click to select the type of entry from the following window, with various results
in tabs:
Chapter 1
1-22
Figure 1.6: Class search and select window
• Right click and Select Search, or use CTRL+F to search for a value or an attributename, inside the grid. The result will be highlighted in the grid.
1.5.1.2 Search domain (In)
The term In allows searching within a specific branch. The branches available depend on thetype of item selected:
- By default, the branch that is displayed corresponds to the selection made in the treestructure.
- Other available domains correspond to branches of a higher level than that of theselection.
Example:
- In the directory, for a first level location selected in the tree, search domains are:• The location.• The root.
- In Configuration, in offline (disconnected) mode (network tab), for a PCX selected in thetree, search domains are:• The PCX node.• The subnet.• The network.• The root.
1.5.1.3 Search criteria (Where)
1-23
The Where box allows search criteria to be specified.
It consists of:
- The list of attributes of the entry searched for (for example: type of extension).
- A list of comparison operators allowing search criteria to be combined (for example:Equals).
- An entry field for attribute data corresponding to search criteria (for example: Analog).
- Icons allowing additional search criteria to be managed.
1.5.1.3.1 Operators for comparison
Select an operator from the list of presets.
Operators for character string attributes:For example: Equal to, Does not equal, Empty, Not empty, etc.
Operators for integer or listed attributes:For example: Equal to, Not equal to, etc.
1.5.1.3.2 Entry box
Depending on the search to be performed, enter either a string of characters or an integer. Theentry must respect the search criteria.
1.5.1.3.3 Multicriteria filter icons
table 1.7: Multicriteria filter iconsIcons Functions
And to search for entries matching all criteria.
Or to search for entries matching at least one of the criteria.
To add a search criterion.
To remove a search criterion.
1.5.1.4 Search icons
table 1.8: Search iconsIcons Functions
Search and replace:Search results are displayed in the data area and replace the datapreviously displayed.
Search and add:Search results are displayed following the data already present inthe data area.
1.5.2 Example searches
1.5.2.1 Example using the company directory
Chapter 1
1-24
You are looking for all people from the DEP1 department of company XYZ whose name startswith a P:
1. Select Individual(s) in the Search drop-down list.
2. Select XYZ in the In drop-down list or select company XYZ in the tree.
3. Specify the search criteria:a. Select the Department attribute, the Equals operator and enter DEP1 in the text box
of the Where item.b. Click + to add a criterion.c. Select And.d. Select the Name attribute, the operator Begins with and enter P in the text box.
4. Run the search.
1.5.2.2 In the Configuration application
A search on User name is case sensitive.
1.5.2.2.1 Search for PCX in offine (disconnected) mode (Network tab)
You want to search for all c1.705 release PCXs on network netw1 whose name starts with a b:
1. Select netw1 in the In drop-down list or select network netw1 in the tree.
2. Specify the search criteria:a. Select the Release attribute, the Equals operator, and enter c1.705 in the text box of
the With item.b. Click + to add a filter line to attribute.c. Select And.d. Select the Name attribute, the Begins with operator, and enter b in the text box.
3. Run the search.
1.5.2.2.2 Examples of filters in online (connected) mode (PCX tab)
You want to search for users with a 4035T type extension/set:
Figure 1.7: User search area
Click the magnifying glass icon to launch the search and display the results.
1-25
Figure 1.8: Search results
Here is an example of a more refined search using a combination of two search criteria: allanalog extensions with the STAP feature unrestricted
Reminder:
The STAP feature is required for automatic calling via the Web Directory Client.
Figure 1.9: Searching with two search criteria _ — example 1
Here is a second example of a refined search combining two search levels: all No. 1 and 2directory keys of all users whose set is not an analog set.
Note:
This type of multi-level search is specific to the Configuration application.
Figure 1.10: Searching with two search criteria _ — example 2
1.5.2.3 In the Accounting application
You want to search for the user Alexis in the organization:
1. Select User in the Search field.
2. Select the Name attribute, the Contains or Equals operator, then enter Alexis in the textbox of the With item.
Chapter 1
1-26
3. Run the search. After a few moments, the result is displayed.
1.5.3 Searching from the tree
The shortcut menu Filter... command allows a search to be run and the results of this searchto be displayed in the tree (to view, move, delete, or modify them):
1. Select an item in the tree.
2. Select the Filter... command from the shortcut menu. A search window is displayed. Youcan use it in the same way as you use the search area.
3. Complete the items and run the search.
1.6 Modifying data
1.6.1 Overview
Each entry contains attributes with values that can be modified. The table below shows anexample.
table 1.9: Examples of modifiable attributesEntry type Name of attributes Value
Person (Individual)
NameFirst namePhone No.
…
BridgesJean3333
…
1.6.2 Updating attributes
The attributes displayed in bold in the record or table must be completed.
Remark:
For the Configuration application, a record only displays relevant attributes. All attributes are displayed
in a table. For example, for a User, a record only displays attributes corresponding to his own type of ex-
tension while a table displays all attributes available for all types of extensions.
During attribute update (creation, modification, deletion), you can either apply or cancel youroperations. See § Applying or canceling updates .
1.6.2.1 Performing input (entering data)
1. Double-click the box to be completed.
2. Complete the box. The symbol is displayed to show modified boxes.
3. Click Apply to accept changes.
1.6.2.2 Selecting a box
1. Double-click to change state. The symbol is displayed.
2. Click Apply to accept changes.
1-27
1.6.2.3 Entering a password
1. Double-click the box to be completed. The box is divided into two sections.
2. Enter the password in the first section.
3. Move the cursor into the second section (TAB key or click).
4. Enter the password again in the second section. The symbol is displayed.
5. Click Apply to accept changes.
1.6.2.4 Selecting a value from a predefined list
1. Double-click the box. An arrow is displayed to the right of the box.
2. Click the arrow to scroll down the list of possible values.
3. Select a value. The symbol is displayed.
4. Click Apply to accept changes.
1.6.2.5 Entering multiple values
1. Double-click the box.
2. Select a command from the shortcut menu:Standard method:• Add a value: to add a value.• Delete a value: to delete a value.Method when the order of values is important:• Add before: to add a value before the selection.• Add after: to add a value after the selection.• Delete: to delete the selection.
3. Complete the boxes added.
4. Confirm by pressing Enter or by clicking another field. The symbol is displayed.
5. Click Apply to accept changes.
1.6.2.6 Adding attributes
This feature (disabled by default) must only be used by a manager familiar with the Systemdirectory. It consists in displaying attributes that are naturally masked when empty/blank. Theprocedure is as follows:
- In the System directory, select (for example) the branch NMCConfiguration >GlobalPreferences > DirectoryClient.
- In the data box, click one of the attributes listed in record mode.
- Select the Add attributes command. New attributes are displayed in the record.
1.6.3 Adding/Deleting an object
The Create icon can only be used when:
Chapter 1
1-28
- Creation can be used for the position currently selected in the tree.
- Only one type of item can be created at this position.
If different items can be created at the same position, use the shortcut menu to select an item.
The creation procedure may vary according to the application. Here are some examples ofitem creation:
SchedulerA new job or new task is created in the shortcut menu at the highest level of the tree.
Accounting (carrier tab)To create a carrier, an area or a tariff, for example, click the item in the tree to which you wantto add the new item, then select the Create command from the shortcut menu.
ReportsTo create a file or a report definition, select one of your personal directories, then select theAdd > Folder or Add > Definition command from the shortcut menu.
Company directoryTo create a department, a person or a group, for example, click at the appropriate place in thetree structure, and, from the shortcut menu, select the appropriate command, Create > X,where X is Country, City, Company, Department, Person, etc. .Once a detail grid is displayed to be filled in, the create a new record icon allows you tocreate multiple entries of the same type. To create each new entry click the create a newrecord icon.
SIP Manager
Create and assign a SIP device to a SIP user
1.6.4 Copy/Paste attributes
1. Select the cells to be copied.
2. Use the Ctrl C keys or select the Edit > Copy command from the shortcut menu.
3. Select the destination cells.
4. Use the Ctrl V keys or select the Edit > Copy command from the shortcut menu. Thevalues of the attributes are copied.
To avoid entering the same data several times, you can copy cells using the same procedure.The following example shows how to copy directory entry data on several lines:
Figure 1.11: A line of data is copied
1-29
Figure 1.12: The copied data is pasted on several lines
When a cell is copied, and the paste function (using the Ctrl + V keys) is applied on the columnheader or the row header, the paste will be processed for the whole column or the whole row.
1.6.5 Moving entries
Moving the selection (Directory only):
1. Select one or more entries in the tree.
2. Drag the selection to the appropriate place in the tree. A dialog box is displayed.
3. Confirm the move operation. The entry is displayed at its new place in the tree.
Cut/Paste the selection:
1. Select one or more entries in the tree.
2. Select the Cut command from the shortcut menu. The selection appears shaded.
3. Select the destination.
4. Select the Paste command from the shortcut menu. The selection is displayed in its newposition.
1.6.6 Applying or canceling updates
The Apply, Cancel, and Cancel all commands can be used to apply or cancel operationsperformed on selected data. Three operations may be performed on the selected data, eachtype of operation is symbolized by an icon:
- modify.
- create.
- delete.
The selected data concerned is:
- either the current record (record mode),
- or entry(ies) selected (table mode).
1.6.6.1 Applying modifications to selected data currently being edited
To apply the modifications performed on the line being edited select Apply from the shortcutmenu. If modifications are accepted, the icon symbolizing the modification disappears and thedata is updated in the database.
Chapter 1
1-30
1.6.6.2 Apply all
Apply all is used to apply operations performed to all entries in a table, unlike the Applycommand whose field of application is limited to the entry currently being edited.
There are two methods of applying this command:
- Select Apply all from the shortcut menu to apply current operations.
- Click .
1.6.6.3 Canceling current edit operations
To delete the operations performed on the line being edited, select Cancel from the shortcutmenu. The data returns to its initial value.
1.6.6.4 Cancel all
Cancel all is used to restore operations performed on a set of entries in a table, unlike theCancel command that is limited to the entry currently being edited.
There are two methods of applying this command:
- Select Cancel all from the shortcut menu to cancel all current operations.
- Click . The data returns to its initial value.
1.7 Customizing dictionaries
1.7.1 Overview
Customizing dictionaries allows the translation of certain expressions used in theAlcatel-Lucent OmniVista 4760 Network Management System to be changed, for example, thetranslation of LDAP attribute names (names in the Company directory).Customization consists of creating a second dictionary file containing the new translations. Aspecific application, called “CustomDict.exe”, allows this second dictionary file to bemanaged.
1.7.2 Dictionary location in the Alcatel-Lucent OmniVista 4760 NetworkManagement System
Alcatel-Lucent OmniVista 4760 Network Management System applications use “.properties”and “.php” dictionary files that only contain one language and are not easily modifiable.
The CustomDict tool uses a “.dict” file as input. This file, in Unicode format, contains alllanguages and generates the corresponding “.properties” and “.php” files as output.
Two dictionary files are embedded on the Alcatel-Lucent OmniVista 4760 NetworkManagement System:
- LdapAttributes_User.dict containing Company directory LDAP attributes.
- AlarmReporting.dict containing header for free fields in the Alarms application (seemodule Alarms - Overview )
1-31
The file user/xxx_user.dict contains the modified fields.
The Java client uses the dict_user.zip archive containing theLdapAttributes_user.properties file generated by the CustomDict tool.
Break-down of files in the Alcatel-Lucent OmniVista 4760 Network Management System treestructure:
- 4760\Locales\dict\xxx.properties
- 4760\Locales\dict\user\xxx_user.properties
- 4760\Client\dict\xxx.php
- 4760\Client\dict\user\xxx_user.php
- 4760\Client\bin\dict_user.zip
- 4760\dict\xxx.dict
- 4760\dict\xxx_user.dict
Note:
When Alcatel-Lucent OmniVista 4760 Network Management System backup, restore, and upgrade oper-
ations are performed, the “4760\dict\xxx_user.dict” files are conserved, but as uninstalling the Alcatel-Lu-
cent OmniVista 4760 Network Management System deletes all files, a backup copy of these files must, in
this case, be made in another directory.
1.7.3 Managing customized dictionary versions
Version number must be managed to allow remote clients to know when they must downloadnew dictionaries.Version number is shown in two places:
- In the xxx_user.dict file
- In LDAP: dictVersion parameter
Version number is managed with the CustomDict tool which, at backup, increments versionnumber and updates the “xxx_user.dict” file and LDAP.
1.7.4 The CustomDict.exe tool
This application is used to edit a xxx.dict dictionary and generate xxx_User.dict containingthe new translations. It is also used to automatically generate xxx_User.properties andxxx_User.php files and add these to the dict_User.zip archive.The application is run on the Alcatel-Lucent OmniVista 4760 Network Management Systemserver by clicking Start > Programs > Omnivista 4760 > Tools > Customize Dictionary
Chapter 1
1-32
Figure 1.13: Customizing dictionaries — Main window
The following window is displayed when the xxx.dict file is opened:
1-33
Figure 1.14: [D:\4760\dict\LdapAttributes.dict] — CustomDict window
The left column contains a list of dictionary items. List display language can be selected via thedrop-down Languages list. The Find dialog box allows a search to be run on the list of items.The table (grid) on the right contains the translations of each dictionary item and allows a newtranslation to be entered in each language.
Figure 1.15: Default translation for misc1 attribute
Save is used to:
- Save new translations in the xxx_user.dict file.
- Automatically generate xxx_User.properties files in the directory “4760\Locales\dict\user”,and automatically generate xxx_User.php files in the directory “4760\Client\dict\user”.
- Update the archive “4760\Client\bin\dict_user.zip”.
- Increment version number in LDAP.
Note:If the Alcatel-Lucent OmniVista 4760 Network Management System client application is already run-ning on the server, changes cannot be saved since the “dict_user.zip” file is currently being used.Close the application to enable save.
Chapter 1
1-34
Figure 1.16: Customized translation for misc1 attribute
Set All to Default restores the default translation for all items.A xxx_user.dict file from another machine can be used on the Alcatel-Lucent OmniVista 4760Network Management System, but, for this file to be locally applied, you must launch theCustomDict.exe application, open the file, and then save it to generate the localxxx_User.properties and xxx_User.php files and update version number.
1.7.5 Deployment
When the client application is run, local (internal) dictionary version number (if installed) andserver version number are checked. If the dictionary on the server is more recent (higherversion number), the user is asked if he wants to download it.
1.8 4760 Diagnostic Tools
1.8.1 Overview
The tool allows to collect maintenance information.This information is required to diagnostic the behaviour of the Alcatel-Lucent OmniVista 4760Network Management System server.
The maintenance information is:
- Alcatel-Lucent OmniVista 4760 Network Management System server and client log files
- SunOne and Apache log files
- Installation paths
- Service status
- The license file
1-35
- The host characteristics
- Scheduled task information
1.8.2 Operation
To start the tool:
- Open a session on Alcatel-Lucent OmniVista 4760 Network Management System server
- Click:___change-begin___
___change-end___
Figure 1.17: 4760 Diagnostic Tool Home Window
- Follow the instructions...
The user is prompted to enter the . This password has been definedduring server installation.
The collected information is saved in the directory.
At the end of data collection, a web browser is opened to display the main collectedinformation (file: ).
In addition, a compressed file ( ), including all collectedinformation is generated. This file can be transmitted to Alcatel-Lucent support for diagnostic.
Chapter 1
1-36
2.1 Overview
2.1.1 Inter-Directory Relationships
The Directory application is part of the Alcatel-Lucent OmniVista 4760 CommunicationManagement System (called Alcatel-Lucent OmniVista 4760 Network Management System inthis document).
The following figure shows the relationships between the Directory, Accounting, and the PCXs.
Figure 2.1: Inter-Directory Relationships
A: Company directoryB: System directoryC: AccountingD: Web Directory Client
Note:
The Company Directory and Accounting are installed according to the license installed on the server.
If Accounting (C) is installed, you must be familiar with the main rules that apply to cost centermanagement (see § Cost Center Management Rules ).
2
2-1
2.1.2 The Four Tabs of the Administration Directory
The Administration directory consists of four tabs:
- The Company tab.
- The System tab.
- The Remote Service Center, or RSC tab.
- The Address Books tab.
For general viewing principles, see module Interface - Overview
2.1.2.1 Company Tab
The Company directory is subject to license.It contains the organization of persons, services, rooms, etc. through a detailed tree structurein relation with the System directory. This relationship is set via Setting links management,which ensures automatic update of Sets to Individuals.The Web Directory Client uses the content of the Company directory.
See module Directory - Company tab .
2.1.2.2 System Tab
The System directory is present regardless of the licenses installed. It contains essentialconfiguration and customization attributes for the Alcatel-Lucent OmniVista 4760 NetworkManagement System server (reserved for the administrator):
- PCX configurations.
- The command for data synchronization with the PCXs.
- Data from PCXs (Extensions and their associated physical characteristics) used by thevarious applications. This data cannot be modified manually except attributesserialnumber for board and user in particular cases (see note).
Note 1:Attributes that can be manually updated Two attributes available from Alcatel-Lucent OmniPCXEnterprise CS 6.1, can be manually updated from the system directory in some cases:
• +serialnumber in A4400Board class: if the PCX is running a release previous to 6.1.
• serialnumber in user class: For others sets than Alcatel series 8 and 9.
Note 2:Attributes that can be manually added: extra user.
According to some PCX topology, it is possible to have tickets associated with users undetected bysynchronization. Such tickets are affected to undefined organization branch. If you need to addnames to such users, create manually extra users under the PCX branch:
1. create one single extra container under PCX OmniPCX Enterprise/4400
2. create extra users under this extra container
- Internal application customization settings and options.
- External application configuration.
See module Directory - System tab .
2.1.2.3 RSC Tab
Chapter 2
2-2
The Remote Service Center (RSC) is subject to license. It allows for the remote managementof a PCX network according to customer.
In the Company directory, it is possible to create RSC customer entries, associate one or morePCXs with a customer, and manage customer attributes.
The RSC tab is used to create lists of customers to facilitate the generation of reports.
See module Directory - RSC tab
2.1.2.4 Address Books Tab
The Address Books tab, is used to manage the Personal Address Book (this is anindependent branch of the Company directory). Each person can use this feature to store theirpersonal contacts.
The Personal Address Book is available for all users connected with their own login/password.Users connected with the Anonymous login do not have access to Personnal Address Book.
In additionaly, there is a global parameter to allow address book usage (see module Directory- Address Books tab ).
2.1.3 Web Directory Client
The Web Directory Client allows the Company directory to be accessed via a Web browser. Ina variety of languages you can use the Web Directory Client to:
- view and print directory entries,
- make an automatic call or send an e-mail,
- modify the information in your directory entry (subject to authentication),
- create or modify other records, depending on your access rights (subject toauthentication),
- maintain a Personal Address Book (subject to authentication).
See module Directory - Web Directory Client - Operation .
Some settings are reserved for the administrator. See module Directory - Web Directory Client- Configuration
2.1.4 Cost Center Management Rules
Cost center names are displayed:
- In the Individual records of the Company directory.
- In chargeable entities in the Accounting organization.
In the internal configuration of the OmniPCX 4400 and Alcatel-Lucent OmniPCX EnterpriseCS, the name of a cost center is restricted to 10 characters maximum. On the other hand, theAlcatel-Lucent OmniVista 4760 Network Management System Accounting internally acceptsnames with up to 60 characters (which may be restricted to 20 characters depending on thelanguage). This prevents cost centers from being synchronized (PCX/Server), allowing you tomanage cost center names with more than 10 characters in the Accounting or Directoryapplications.
The choice between the two types of management is made (and cannot subsequently be
2-3
modified) at installation:
1. Management of cost centers on Alcatel-Lucent OmniVista 4760 Network ManagementSystem, independent of the PCX network.
2. Synchronized management between the Alcatel-Lucent OmniVista 4760 NetworkManagement System and the network.
Note:These types of management concern only the OmniPCX 4400 and Alcatel-Lucent OmniPCX Enter-prise CS.
Figure 2.2: Cost Center Synchronization
A: Company directoryB: System directoryC: PCX networkD: Accounting
Concerning relationships with the OmniPCX Office, there cannot be any synchronizationbetween the internal directory and the Alcatel-Lucent OmniVista 4760 Network ManagementSystem sever.
2.1.4.1 Synchronized Management
After cost center data is retrieved from the PCXs (C) via full or partial synchronization, it islinked to the System directory records (B). Then, when a primary, secondary, or miscellaneouslink is established between System directory (A) and company directory (B) records (see note),any cost center change will be automatically noted in all related entries, including those inaccounting (D).This two-way dynamic update will occur after modification of the following:
Chapter 2
2-4
- An individual record in the company directory (A).
- The cost center in a PCX (C) user's data.
- The cost center, directly on the PCX (C).
Manual management and update rules (on the PCX or the server) must be established jointlyby the different company network managers to avoid inconsistencies.
Restrictions: The same person cannot be linked to sets declared in different cost centers.
Update conflict: A conflict may arise when a primary link is established and a different costcenter name is defined for two entries to be linked to both the company directory (A) and theSystem directory (B). A System directory option allows you to select the master:Nmc > NmcConfiguration > 4760 master for cost center management.
- Option selected: This is the default value — the company directory updates the Systemdirectory that, in turn, updates the Accounting organization.
- Option deselected: The System directory that retrieves data from PCXs updates thecompany directory and the Accounting organization.
A change of status to this option is immediately applied when the next link is set up withoutchanging current cost center links.
Inconsistent update: If you record cost center data that does not exist in the PCX (OmniPCX4400 or Alcatel-Lucent OmniPCX Enterprise CS) in the company directory, the followingevents will occur:
Figure 2.3: Inconsistent Update of Cost Center
table 2.1: Inconsistent Update of Cost CenterItems in thefigure
Events
A
1 – Initially, there is a directory entry in cost center cc1 linked to a phone setin cc1.2 – In the company directory, transfer the entry for cost center cc1 to costcenter cc2 (that does not exist on the PCX).
2-5
B
3 – The System directory is updated for application in the Accountingorganization and in Accounting. Chargeable entry cc1 is stored in thehistory. A new chargeable entry (cc2) is created.4 – If reverse synchronization is enabled, the Alcatel-Lucent OmniVista 4760Network Management System attempts to place the set in cc2. As cost centercc2 does not exist, the PCX generates an alarm.5 – When the alarm is received, you may manually create cost center cc2 onthe PCX and assign the set to cc2.
C
6 – If the operation is not performed, at the following synchronization costcenter cc1 of the set on the PCX will overwrite the System directory costcenter.7 – The System directory updates the company directory and Accounting,which generates a second storing operation (history) in the organization.The chargeable entry in cc2 is stored in the history and a new chargeableentry is created in cc1.
Note:
See module Directory - Company tab § Creating Entries Automatically .
2.1.4.2 Independent Management
With Independent management (unlike Synchronized management), no cost center names areretrieved from the PCXs. Cost center management is performed manually in the companydirectory, where the administrator can define names with more than 10 characters. The limit inthe Alcatel-Lucent OmniVista 4760 Network Management System Accounting is 60characters,or as few as 20 UTF8 characters, depending on the language.The System directory is automatically updated by synchronization operations for transfer toAccounting.If you do not have a company directory license, cost centers can be managed directly in theAccounting organization by moving sets to cost centers. This also involves the exclusiveentry management process for OmniPCX Office set entries. See § Specific Management ofan OmniPCX Office .
2.1.5 Specific Management of an OmniPCX Office
The cost center concept does not exist on this type of PCX. The Cost center parameterincluded in the PCX declaration defines the cost center that chargeable entities must be linkedto.
2.1.6 Customization of Parameter Names
Some parameters names of dictionaries can be customized with the customization tool. Formore information, see: module Interface - Customizing dictionaries .
2.2 Company tab
2.2.1 Description of the Company Tab
To access the company:
Chapter 2
2-6
- Click the Company tab in the tree.
This has dedicated features to facilitate management: automatic creation, manual creation viaa wizard, inter-directory (System/Company) link management, LDAP file import and export.The Company tab is the LDAP server branch: o=”company tab root”, o=DirectoryRoot.Some operations can only be performed by the directory administrator.
The tree structure may contain the following types of entries:
table 2.2: Directory Tree SymbolsEntry type Symbol
Company
Organization Department
RSC Customer
Country
City
Termination Group
Room
Person
The tree structure root contains first level entries that may contain second level entries and soon. The Company, Department, RSC Customer, Country, and City fields are Organizationtype entries. They are only managed manually.
The Person, Group, and Room entries occur at the last level in the hierarchy and are thus thedifferent terminations of the tree.
Note 1:
The Administration branch appears first in the tree and contains a list of Alcatel-Lucent OmniVista 4760
Network Management System administrators classified by group. You can customize the remainder of
the tree layout using organization type entries.
The RSC Customer type is similar to the Company type with some additional attributes used tomanage scheduled report generation and exports. See § Managing RSC Customer Entries
Note 2:
The name of the RSC Customer is copied in Accounting. In order for the name to be readable on the re-
ports, use a name no longer than 30 characters (20 UTF8 characters, depending on language).
2.2.2 Creating Entries Automatically
2-7
1 This second search mode is available only if the attribute "Automatic links with Wildcards"(Directory>System>nmc>NmcConfiguration) is checked.
2.2.2.1 Overview
After adding or modifying a System directory entry by synchronization, two consecutivesearches are run in the Company Directory to find the directory record for the set.The first search is an exact search on telephone set name and first name fields.If this search fails, a second search is run using a wildcard character. This wildcard canreplace one or more characters of the name and first name fields. 1
In addition, this second search ignores characters defined in Nmc > NmcConfiguration >Strings to ignore. By default, the list contains the blank space " " and the period “.”
Example:
The Automatic links with Wildcards option allows to link J Smith and John Smith or John S and
John Smith
The string to ignore option allows to link JohnPeter Smith and John Peter Smith.
If reverse synchronization (Alcatel-Lucent OmniVista 4760 Network Management System toPCX) is not disabled, the set is updated with the data of the Company Directory.
Caution:
When the Automatic links with Wildcards option is enabled, a set named Office11 and a set
named Office1 are linked to the same entry (Office1*). If you are not sure that this should apply to
your system configuration, disable the Automatic links with Wildcards option.
When the double search is complete, if no result is available to establish a link, a directoryrecord is created (if the "Dial by name" attribute is set to "True/Yes" in set management).
As of R5.0, the automatic creation takes into account the cost center.
The following tables detail the behavior of the automatic creation process when the name isalready in the Company Directory or when an equivalent name (search with wild card) isalready in the Company Directory.
table 2.3: Automatic Link without Wild Card: When the Search Results in the Same Surnameand Same First Name
Extension Cost Center Action performs by thesystem
Same extension (in differentAlcatel-Lucent OmniPCXEnterprise CS)
Same cost center Update of the existingperson's data in the CompanyDirectory
Same or different extensions Different cost centers Alarm number 19003 isgenerated: the administrator isprompted to solve the situationmanually.
table 2.4: Automatic Link with Wild Card Set to True: When the Search Results in anEquivalent Surname and/or Equivalent First Name
Chapter 2
2-8
Extension Cost Center Action performs by thesystem
Same extension (in differentAlcatel-Lucent OmniPCXEnterprise CS)
Same cost center Update of the existingperson's date in the CompanyDirectory
Different extensions Same cost center Update of the existing personin the Company Directory.The new extension is added.
Same or different extensions Different cost centers Alarm number 19003 isgenerated: the administrator isprompted to solve the situationmanually.
If the RSC license is present, the automatic link creation feature will search matchingCompany directory entries under the directory level defined by the RSC Customer attribute ofthe PCX entry.
2.2.2.2 Creation Criterion
The table below represents the type of item automatically created in the Company directoryaccording to the System directory initiating the item.
table 2.5: Entry Types Created in Company DirectorySystem Directory Options Company Directory
User Person
User alias Person
Speed dial No. alias Person
Remote user Person
Hunt groups Group
Note 1: Automatic creation will only be effective for PCXs with the "Automatic creation"attribute enabled.
Note 2: By default, none of the options are enabled and therefore no automatic creation isperformed. To enable automatic creation, you must select the options corresponding to thedesired types of items.Open the System directory and select Nmc > NmcConfiguration > GlobalPreferences >DirectoryAdmin > Automatic Creation.
2.2.2.3 Location of the Items Automatically Created in the Company Directory
You can specify for each network, subnetwork, or PCX (OmniPCX 4400 and Alcatel-LucentOmniPCX Enterprise CS only), the location where you want the entries to be createdautomatically. You can specify this in the System directory via the Location for automaticcreation attribute for networks, subnetworks, and PCXs.To ensure consistency, select an organization type container (company, department, city, orcountry).Lower level containers prevail over upper level containers. In the figure below, container Bapplies to the Subnet except for container C, applied to the company, that takes precedenceover B.
2-9
Figure 2.4: Precedence of Containers
If no container is specified or if it is incorrectly specified, automatic creation will be performedat the directory root level. If the RSC license is present and no container is specified, the entrywill be created under the directory level defined by the RSC Customer attribute of the PCXentry. As for any other entries, the administrator may move the automatically created entrieswithin the tree structure.
2.2.3 Inherited Automatic Update of the Attributes
When creating certain types of entries, the organization attributes automatically inherit thevalues from entries located higher in the hierarchy of the directory tree. This inheritance isapplied regardless of how the entry was created: automatically, manually, or imported. Noautomatic update occurs when an entry is moved or modified. Fields that are alreadycompleted are not automatically updated. This means if you use report on user group basedon department field, you should check consistency of such department field before any reportand apply this check after moving directory entries.
Inheritance applies to these types of entries:
- Company
- Department
- Person
- Room
The attributes that inherit values are:
- Company
- Department
- Country
- City
You can enable or disable this feature in the System directory via the Nmc > NmcConfiguration> Automatic inheritance attribute. A change of status to this option has no impact on theentries included in the Company directory.
2.2.4 Managing Entries
2.2.4.1 Creating Entries Manually
2.2.4.1.1 Creating One or More Entries in the Tree
The Create command allows entries to be created.
Chapter 2
2-10
Figure 2.5: Company Directory: Creating EntriesTo create a single entry:
1. Select an entry in the tree.
2. Select the Create command from the shortcut menu and select the type of entry.A blank record is displayed in the data area.
3. Complete the attributes.
4. Click Apply to accept changes.A new branch is displayed in the tree.
To create several entries in one step:
1. Select an entry in the tree.
2. Select the Create command from the shortcut menu and select the type of entry.A blank record is displayed in the data area.
3.
2-11
.
The data area switches to table mode.
4. Place the cursor on the table and select the Create command from the shortcut menu.
5. Complete the attributes.
6. Click Apply to accept changes.New branches are displayed in the tree.
Another way to create several entries in one step:
1. Select an entry in the tree.
2. Select the Create command from the shortcut menu and select the type of entry.A blank record is displayed in the data area.
3. Click the icon.
The data area switches to table mode. A new blank line is created with each click.
4. Complete the attributes
5. Click Apply to accept changes.The new entry branches are displayed in the tree.
2.2.4.1.2 Creating New Individuals with Set Assignments.
This feature allows:
- Individuals to be added to the Company directory.
- Extensions to be assigned to these individuals.
Chapter 2
2-12
Figure 2.6: Company Directory: Creating Entries from Sets
To create individuals with extension assignment:
1. Select a level in the tree (for example: country, city, company, department).
2. Select the Sets to Individuals command from the shortcut menu.The "Create person from sets" window is displayed.
3. Search for and select the extension(s) to be assigned to the individuals.See module Interface - Data search § Using the search area .
4. Click Create.A record (one per extension) or a table (several extensions) is displayed in the data area.
2-13
5. Complete the attributes.
6. Click Apply to accept changes.New individuals are displayed in the tree.
Remark:
In this procedure, links are created between individuals and extensions.
See module Directory - Managing links between the Directory and the PCX .
2.2.4.2 Converting Person Type Entries to Organization Type Entries
Person type entries can be converted to Organization type entries (company, department,group, or room). This operation is equivalent to deleting the selected entry and recreating it asa new type. It can be simultaneously performed for multiple entries by making a multipleselection.The conversion deletes the individual's specific attributes: password, photo, mobile, etc. aswell as any links to other records (assistant, manager, etc.). Other attributes are eitherautomatically updated (if they match) or kept.Directory records associated with a converted entry are not updated and will have dead endlinks (pointing to no valid entry).To convert an individual:
1. Select the individual to be converted in the company directory.
2. Search for and delete any links pointing to this individual.
3. Scroll down the Conversion > company / department / Group / Room shortcut menu.
4. Click on the new type desired. The entry is converted.
2.2.4.3 Managing RSC Customer Entries
With the appropriate license, you can create RSC Customer entries. These entries are similarto Company entries, with additional attributes for generating reports in an RSC context.
The aim of RSC Customer entries is to gather and report information about PCXs owned by aparticular customer.
Link every PCX to at most one customer. Do this by filling in the RSC Customer attribute inthe Organization tab of the System directory. This will associate the accounting tickets,counters, PTP or TOIP data, and alarms for a PCX with a customer. The RSC Customerattribute is available for all types of PCXs.
You may also link a customer to one or more PCXs in the Company directory by filling in theCustomer's PCX attribute in the OmniPCX resources tab.
The update of either attribute will automatically update the other. Update and delete operationsto RSC customer entries in the Company directory will be reported in the accounting databaseto be used during report generation.
To export a customer's reports by e-mail, enter the Customer contact's email addressattribute in the Customer contact tab.
To export a customer's reports in a format different from the default format specified atgeneration time, enter the File format (export or mail) attribute in the Report preferencestab.
For more information about generating reports using customer lists, see . module Reports -Use § Scheduling Report Generation for a Customer List
Chapter 2
2-14
2.2.4.4 Converting Company Type Entries to RSC Customer Entries
With the appropriate license, RSC customer entries can be created manually as describedabove, or existing company entries can be converted to RSC customer entries. To convert acompany entry:
1. Select the company in the Company directory.
2. Using the shortcut menu, select Conversion > To Rsc customer.
2.2.4.5 Importing/Exporting Entries
These commands allow all or part of the database to be imported or exported in the form ofLDAP Data Interchange Format (LDIF) files.
An exported file can be modified then re-imported to apply the changes to the database (seemodule Directory - Appendix A: Using LDIF files ).
Remarks:
LDIF (RFC2849, LDAPV3 RFC2251 to 2256) is the exchange format for LDAP server text files. LDAP is
the client-server protocol used to access directory services.
2.2.4.5.1 Exporting from the Tree
The Export command allows an LDIF file containing all or part of the database to be created:
To export a directory, directory branch, or selected directory entries:
1. Select the directory root, branch, or entry to be exported.
2. Using the shortcut menu, select Export, then Local or Server. Lastly, select:• Entries... to export the selected entries only.• Sub level... to export the entries located immediately below the selected entry only.• Branch... to export the selected entry and all the entries below it.If you selected Local, the Save window is displayed. If you selected Server, the Export toserver window is displayed.
3. If desired, click to select the destination directory.
Note:If you selected Server, the destination directory must be \4760\Client\Data\Import.
4. In the File name field, enter the name of the LDIF file.
Remark:Make sure File type is set to LDAP Data Interchange Format (.ldif).
5. Click Save to generate the LDIF file.When the export operation is complete, a message is displayed in the status field notifyingthe user that the export was successful.
2.2.4.5.2 Importing from the Tree
The Import command allows a file in LDIF format to be loaded.
To import a directory, directory branch, or directory entry:
1. Select any entry in the tree.
2. Using the shortcut menu, select Import, then Local or Server. Lastly, select:
2-15
• Add and modify: to import new and modified entries.• Add only: to import new entries only.• Modify only: to import modified entries only.
These three operations allow you to control the update according to your needs.If you selected Local, the Open window is displayed. If you selected Server, the Import toserver window is displayed.
3. If necessary, click to search for the directory containing the LDIF file.
Note:If you selected Server, the source directory must be \4760\Client\Data\Import.
4. Select the LDIF file.
Remark:If the file is not displayed in the window, make sure File type is set to LDAP Data InterchangeFormat (.ldif).
5. Select Open to import the LDIF file.When import is complete, a message is displayed in the status window notifying the userthat the import was successful and new entries are automatically positioned in the tree.
2.2.4.5.3 Exporting from the Table
1. Select all or some of the instances in the data area.
2. Using the shortcut menu, select Export in text format, then To file, or To clipboardIf you selected To file, the Save window is displayed.
3. If desired, click to select the destination directory.
4. Enter the name of the text file in the File name field.
5. Click Save to generate the text file.
2.2.4.6 Deleting Entries
You can delete entries from the data area or from the tree.
Caution:
From the data area, you can change your mind as long as you have not applied all modifications.
From the tree, entries are immediately deleted (after confirmation).
2.2.4.6.1 Deleting Entries from the Data Area
The Delete command allows several entries to be deleted from the data area in one step. Thiscommand is specific to table mode.
1. Switch to table mode.
2. Select the lines to be deleted.
3. Select the Delete command from the shortcut menu.The symbol (delete) is displayed in front of each entry to be deleted.
4. Click Apply to accept changes.
2.2.4.6.2 Deleting Entries from the Tree
Chapter 2
2-16
The Delete command allows an entry and its sub-levels to be deleted.
To delete an entry:
1. Select the entry in the tree.
2. Select the Delete command from the shortcut menu.A dialog box is displayed.
3. Confirm deletion.The entry and any sub-levels it contains are deleted.
2.2.4.7 Moving Entries in the Tree
To move an entry:
1. Select the entry in the tree.
2. Drag-and-drop the entry or select Cut, then Paste from the shortcut menu.
2.2.4.8 Renaming Directory Entries
Reminder:
After a name or first name has been changed, do not forget to modify the full name (name + first name).
2.2.5 Confidential List
You can put a person on the green, orange, red, or Administrator list (to restrict access tohis/her record) using the Confidentiality attribute.
2.2.6 Groups
The different authentication levels and access rights for the Web Directory Client (see moduleDirectory - Web Directory Client - Operation ) are configured in the "Groups" branch (seemodule Security - Overview ).
2.3 RSC tab
2.3.1 Overview
To facilitate the generation of reports by customer, RSC customers are gathered into lists.These lists are maintained in the RSC tab of the Directory application. This tab is onlyavailable when the RSC license is present.
For more information about generating reports using customer lists, see module Reports - Use§ Scheduling Report Generation for a Customer List
2.4 Address Books tab
2.4.1 Description of the Address Books Tab
To access the Personal address book:
2-17
- Click the Address Books tab to access the Personal Address Book.Each user's entire set of personal contacts are grouped in this tab.
Figure 2.7: Address Books Tab
The Address Books tab is the LDAP server branch: o=AddressBook, o=DirectoryRoot.Every user has an entry in the Personal Address Book allowing him to store all his personalcontacts.
As the Personal Address Book is integrated in the Company branch of the directory, LDAPusers can perform simultaneous searches on both branches.
The Directory records of the Personal Address Book may be imported or exported in Localor Server mode.
Figure 2.8: Importing Personal Address Book Records
2.4.2 Accessing the Personal Address Book Using the Web Directory Client
You can access your Personal Address Book using the Web Directory Client. You must beprovide a login and password. You can search Personal Address Book entries, create, delete,modify and print entries, and customize the entry attributes.
For more information on using the Personal Address Book from the Web Directory Client, seemodule Directory - Web Directory Client - Operation § Viewing your Personal Address Book
Note:
To configure the number of entries allowed in the Personal Address Book, see module Directory - Web
Directory Client - Configuration § Global Parameters
2.4.3 Administration Client
The administrator can access Personal Address Books to perform cleaning and import/export
Chapter 2
2-18
operations, but cannot view the contents of Personal Address Book entries.When a user is deleted, his Personal Address Book is deleted automatically. Similarly, if a useris renamed, his personal address book is also renamed accordingly.Converting a "person" type entry into another type of entry results in the Personal AddressBook being deleted.
2.5 Managing links between the Directory and the PCX
2.5.1 Configuring Links
The links managed are those established between the Company directory and the Systemdirectory.Creating a link consists of associating a System directory telephone extension with a companydirectory entry (person, room, company, department, or group).PCX set groups may be linked to Company directory service, groups, and company.
Links are used for real-time synchronization of attributes. Each type of link behaves in aspecific way (see § Synchronizing Attributes in Real Time ).
Figure 2.9: Types of Links
See § Changing Set Assignment .
table 2.6: Types of LinksID Type of Link
A Primary link
B Secondary link
C FAX link
D Miscellaneous link
Note:
By convention and to facilitate comprehension, the following terms have been replaced in the rest of the
section:
2-19
- The Company directory is referred to as the Directory.
- A Company directory entry is referred to as an entry.
- The System directory is referred to as the PCX (the System directory is automatically updated withPCX data).
- A System directory extension is referred to as an extension (or set).
2.5.1.1 The Primary Link
The primary link allows an entry to be associated with a telephone extension. This extensionwill then have the same name and first name in the directory and in the PCX.
An entry may have several primary links.
During the installation process, primary links are automatically created between the Directoryname and the first name and the extension with the same name and first name (see §Updating Links in Real Time ).
2.5.1.2 Other Links
- The secondary link:The secondary link allows an entry to be associated with a telephone extension with adifferent name.This link can be used for a DECT (PWT) set, the advantage being that you candifferentiate the DECT set from the primary set (extension) by name.
- The FAX link:The FAX link allows a fax set to be associated with one or several entries.
- The miscellaneous link:The miscellaneous link allows an entry to be associated with another type of set/extension(for example: a data terminal).
2.5.2 Creating Links
Link can be created in the data area (the right area) or the tree (the left area). Creation in thetree offers the advantage of a graphic representation allowing you to combine (or separate):
- Creation of a PCX resource.
- Selective deletion of previously assigned links.
2.5.2.1 Creating a Llink from the Tree
2.5.2.1.1 Creating/Adding a Link with an Existing Resource
1. In the Company tab, select the desired entry.
2. Select the Setting links... command from the shortcut menu. The Setting links window isdisplayed.
Chapter 2
2-20
Figure 2.10: Edit Links Window — Setting Links with an Existing Resource
3. Click the tab corresponding to the type of link to be created (primary, secondary, fax, ormiscellaneous), then click Edit. A new window is displayed.
4. In the Create/Replace section, select the A link with an existing resource option.
5. In the Delete section, do not select an option. Click OK. A dialog box is displayed.
6. Use the search criteria and magnifying glass to search for the item(s) to be associated withthe directory entry. Click OK. The dialog box closes.
Note:Use the CTRL or CAPS keys to make a multiple selection.
7. Click Apply to view the associated item in the descriptive table of links.• If you have finished adding links, click OK to close the "Setting links" window.• To create another link, repeat the procedure from step 3.
2.5.2.1.2 Creating a Link and a Resource Simultaneously
1. In the Company tab, select the desired entry.
2. Select the Setting links... command from the shortcut menu. The Setting links window isdisplayed.
3. Click the tab corresponding to the type of link to be created (primary, secondary, fax, ormiscellaneous), then click Edit. A new window is displayed.
4. In the Create/replace section, select the Link with new resource and Add options.
5. In the Delete section, do not select an option. Click OK. A class selection window isdisplayed.
2-21
Figure 2.11: Edit Links Window — Creating a Link and a Resource
6. Specify the class of the new resource (users, user aliases, etc.), then click Next. Thebrowse and configure attribute dialog boxes are successively displayed. Use the Next andPrevious buttons to switch between the windows.
7. Specify the OmniPCX 4400 on which the resource is to be created and confirm.
8. Click the Attribute tab and complete the required attributes, then confirm. The resource isconfigured on the OmniPCX 4400. The initial Setting links window is displayed again.
2.5.2.2 Creating a Link from the Data Field
1. From the Company tab, select an entry in record mode.
2. Click the bottom OmniPCX resources tab.
3. Double-click the field corresponding to the link to be created (primary link, secondary link,etc.). The field is shaded.
4. Double-click the field, then click the icon displayed to its right. A selection window is
displayed.
5. Search for and select the extension(s) and speed dial number aliases to be assigned.Example: Search: Users In: NMC.
Note:Use the CTRL or CAPS keys to make a multiple selection.
6. Click OK. The dialog box closes. The directory entry link is updated and displayed in therecord.
7. Click Apply to accept changes.
Chapter 2
2-22
2.5.2.3 Creating an Additional Link
Follow the procedure presented below to add an additional link, such as the assignment of aDECT (PWT) set (secondary link) to an individual.
1. From the Company tab, select an entry in record mode.
2. Click the bottom OmniPCX resources tab.
3. Double-click the field of the link to be assigned to the individual. The field is shaded.
4. Select the Add a value command from the shortcut menu. A new blank line is displayedwith an icon to its right.
5. Click the edit icon. A search window is displayed.
6. Search for and select the extension(s), aliases, and speed dial numbers to be assigned inthe search window.
7. Click OK. The link is updated.
8. Click Apply to accept changes.
2.5.2.4 Updating Links in Real Time
If you create a directory record with property fields identical to those of an extension (set)present in the configuration, a primary link is automatically created. The conditions forautomatic creation are listed in the following table:
table 2.7: Conditions for Automatic Creation of a Primary LinkOn the Directory Side On the PCX Side
[Name] and [First name] of an individual(person)
must correspond to the combination of directory[Name] and [First name] configured on theOmniPCX 4400.
Room name
Company name
Department name
Group name
If the configuration of the OmniPCX 4400 includes a user with the first name: John and thename Bridges and you declare a person with the same first name and name in the companydirectory, a primary link is created automatically.Make sure entries are spelled correctly, otherwise links will not be automatically updated.
If the RSC license is present, the automatic link creation feature will search entries under thelist of PCXs defined in the Customer's PCX attribute for the customer in the Companydirectory.
Note:
- Modifying a directory record may set up a link with an existing extension and update the correspond-ing attributes via automatic synchronization.
- Deleting a linked entry also deletes the link but does not delete the extension.
The directory also has an Automatic creation disabled by default feature. See moduleDirectory - Company tab § Creating Entries Automatically .
2-23
2.5.3 Synchronizing Attributes in Real Time
If data in the directory or on the PCX is modified, links guarantee that some attributes will beupdated on both sides. Consequently, modifying some attributes of directory records results inthe attributes of the associated extensions being updated.When there is a link, the Phone number, ISDN number, Fax number attributes areautomatically computed from the corresponding telephone set data. These attributes cannotbe manually modified and an additional set number cannot be manually added. If the link isdeleted (set deleted or renamed), the computed data is automatically deleted and the setnumber is lost.Similarly, modifying some attributes of telephone sets affects the associated directory records.The classes concerned are:
- For telephone extensions/sets (viewed via Configuration in online mode):
• User• User alias• Abbreviated (Speed dial) No.• Abbreviated (Speed dial) No. alias• User type on remote network directory• Directory of directory service No. type• Station group
The attributes concerned for this class are:• Phone number• ISDN number• Cost center number• Entity number• Person name or first name• Directory name and first name
- For directory entries (company directory):
• Person• Room• Company• Department• Group
The attributes concerned for this class are:• Phone number• ISDN number• Cost center name• Entity name• Directory name and first nameNote 1: Real-time updating is operational if event reception is enabled on thecorresponding PCXs (see module Directory - Synchronizing PCX data § Real-TimeSynchronization ).
Chapter 2
2-24
Note 2: Directory to PCX synchronization is only effective if the reverse synchronizationoption is selected when the PCXs are declared.Note 3: PCX cost centers are only updated if the cost centers are enabled (option at 4760installation). As from release 2.1 of the Alcatel-Lucent OmniVista 4760 NetworkManagement System, cost centers are updated in both directions.Note 4: When a link is set up, if the cost center values on the Alcatel-Lucent OmniVista4760 Network Management System directory entry and the PCX directory entry aredifferent, the Alcatel-Lucent OmniVista 4760 Network Management System directory isused (by default) to set cost center. To modify this mechanism, consult your installationtechnician.Note 5: If a person has several sets, there is one common cost center for all the sets andthe Directory entry. If the cost center for a set or for the Directory entry is modified, all theother sets are modified to match this new cost center.Note 6: The attributes Name and First name in extended format (UTF8 format) areincluded in the PCX to manage the names of the sets and trunk groups. They aresynchronized from the PCX or manually entered in the System directory and are notified tothe Accounting application for report generation. These attributes are available in theAlcatel-Lucent OmniPCX Enterprise CS of release 7.0 and higher, and will be directlymanaged on the PCX and will be correspondingly updated in the System directory. If theseattributes are empty in the PCX, the values in the System directory will be maintained.
2.5.3.1 Primary Link
Configuration (PCX) to Directory.
Modification of the following attributes results in a real-time update of the associated directoryentries:
table 2.8: Primary Link: Automatic Updates in Directory after PCX Modifications
Configuration Directory
Phone number(set deletion followed by the creation ofanother set with the same name)
Phone number
ISDN number ISDN number
Cost center number (Note 3 in §Synchronizing Attributes in Real Time )
Cost center name
Entity No. Entity name
Person name or first name Primary link broken, phone number and ISDNnumber deleted from the entry! If automaticcreation is enabled, a new directory entry iscreated. The obsolete directory entry musttherefore be deleted manually.
Directory to Configuration (PCX).
Modification of the following attributes results in a real-time update of the associated sets:
table 2.9: Primary Link: Automatic Updates in PCX after Directory Modifications
2-25
Directory Configuration
Person name Directory Name
Person first name Directory first name
Room name - Directory Name- Directory first name
Company name - Directory Name- Directory first name
Department name - Directory Name- Directory first name
Group name - Directory Name- Directory first name
Cost center name (Note 5 in § SynchronizingAttributes in Real Time )
Caution:
The name of the cost center must exist in the
PCX.
- Cost center No.- Cost Center Name
2.5.3.2 Secondary Link
Configuration (PCX) to Directory.
Modification of the following attributes results in a real-time update of the associated directoryrecords:
table 2.10: Secondary Link: Automatic Updates in Directory after PCX Modifications
Configuration Directory
Phone number(set deletion followed by the creation ofanother set with the same name).
Phone number
ISDN number ISDN number
Cost center number (Note 5 in §Synchronizing Attributes in Real Time )
Cost center name
Entity No. Entity name
Directory to Configuration (PCX).
Modification of the following attribute results in a real-time update of the associated sets:
table 2.11: Secondary link: Automatic Updates in PCX after Directory Modifications
Chapter 2
2-26
Directory Configuration
Cost center name (Note 5 in § SynchronizingAttributes in Real Time )
Caution:
The name of the cost center must exist in the
PCX.
- Cost center No.- Cost Center Name
2.5.3.3 Fax Link
When a fax link is created in the directory, the set number is automatically entered in the Faxattribute of the entry. The Fax attribute only exists in the company directory. It does not appearin the PCX configuration.
2.5.3.4 Miscellaneous Link
Directory to Configuration (PCX)
Modification of the following attribute results in a real-time update of the associated sets:
table 2.12: Cost Center Name: Automatic Update in PCX after Directory ModificationOn the Directory Side On the PCX Side
Cost center name (Note 5 in § SynchronizingAttributes in Real Time )
- Cost center No.- Cost Center Name
2.5.4 Replacing Links
This feature allows you to delete and replace all links of the same type. For example, you candelete the secondary links of an individual to several fixed sets and replace them with asecondary link to a DECT (PWT) set.
1. In the company tree, select the entry for which you want to modify the links.
2. Select the Setting links... command from the shortcut menu. The Setting links windows isdisplayed.
3. Click to select the link(s) to be replaced, then click Edit. A window is displayed.
Note:Use the CTRL or CAPS keys to make a multiple selection.
4. In the Create/Replace item, select the desired option:• Replace selection: to replace the links selected in the previous window.• Replace all: to replace all links listed in the previous window.Specify the origin of the resource of the new link by clicking one of the two options:• A link with an existing resource: to attach a link to a resource configured on the
OmniPCX 4400. Follow the procedure § Creating/Adding a Link with an ExistingResource
• A link with a new resource: to attach a link to a new resource (to be configured at thesame time). Follow the procedure § Creating a Link and a Resource Simultaneously .
2-27
2.5.5 Deleting Links
2.5.5.1 Deleting a Link (and its Associated Resource) from the Tree
This command deletes links between directory entries and PCX resources. These resourcescan also be deleted if desired. Different types of links can be deleted simultaneously:
1. Select the entry in the Company directory tree.
2. Select the Setting links... command from the shortcut menu. The Setting links window isdisplayed.
3. Select the link(s) to be deleted from the different tabs. Use the CTRL or SHIFT keys tomake a multiple selection. Click Edit.... A window is displayed.
4. In the Delete section, select the desired option:• Selected links: deletes links (previously shaded).• Selected links and associated resources: deletes links (previously shaded) and also
the associated resources present on the OmniPCX 4400. This option must be usedwith precaution.
5. Click OK, then Apply to accept your changes.
2.5.5.2 Deleting a Link from the Data Field
1. Select an entry in record mode.
2. Click the OmniPCX resources tab.
3. Click the field of an attribute to edit it. It is shaded.
4. Select the Delete a value command from the shortcut menu. The link is deleted from theattribute.
5. Click Apply to accept changes.
Note:
If the link is deleted, the attribute is also deleted
2.5.6 Following a Link between the Company and System Directories
The directory has a feature allowing the attributes of a set (extension) linked to a directoryentry to be accessed. This feature avoids having to start the Configuration application andsearch for the set (extension) associated with the link.
1. Select an entry and switch to record mode.
2. Select the OmniPCX resources tab.
3. Position the cursor on the field describing the link and select Follow this link from theshortcut menu. The record of the associated set (from the System directory) is displayed inthe edit field. If the set has several links, the shortcut menu has a sub-menu offeringaccess to each resource.
4. From the set record, you can return to the Company directory record by clicking theDirectory link attribute and selecting Follow link from the shortcut menu.
2.5.7 Interaction between the Directory and the Configuration
Chapter 2
2-28
To better understand the multiple relationships between the directory and the configuration,several examples of typical management operations are presented.
2.5.7.1 Changing Set Assignment
Figure 2.12: Changing Set Assignment — Initial State
Initial state: James Bridges, unlike Michael Buxtor, has no assigned set (extension). Aprimary link A2 is added between Bridges and the set linked with Buxtor.
Figure 2.13: Changing Set Assignment — Final State
Final state: Michael Buxtor loses his link A1 and a new primary link A2 is added betweenBridges and set 3700. Both directory records are updated. The reassigned set has the nameBridges assigned to it and his initial cost center (if the Alcatel-Lucent OmniVista 4760 NetworkManagement System is master for cost center).
2.5.7.2 Adding a Secondary Link
2-29
Figure 2.14: Adding a Secondary Link — Initial State
Initial state: Bridges has a primary link A1 with a set with the same name declared on thePCX. A secondary link B is added to assign the Dect Roaming set to him.
Figure 2.15: Adding a Secondary Link — Final State
Final state: Creating the secondary link does not affect set attributes, initial name, and firstname are kept. However, the cost center is modified.
2.5.7.3 Other Examples
table 2.13: Synchronization — Example
Chapter 2
2-30
OmniPCX 4400/Alcatel-Lucent OmniPCXEnterprise CS
Creation of a Set in Configuration
Alcatel-Lucent OmniVista 4760 NetworkManagement System
Consequences in the Set Record in theDirectory
Creation of a set with name and first namecorresponding to a directory record.
Automatic creation of a primary link.
Creation of a set with the name and first nameof a person who already has a primary link.
Creation of a second primary link between theperson and the new set.
Creation of a set with name and first namethat do not exist in the directory.
When there is no automatic creation- No automatic link creation.When there is automatic creation- Creation of the directory record and the
link.
table 2.14: Synchronization — Example
OmniPCX 4400/Alcatel-Lucent OmniPCXEnterprise CS
Modification of a Set in ConfigurationLinked with a Person in the Directory
Alcatel-Lucent OmniVista 4760 NetworkManagement System
Consequences in the Set Record in theDirectory
Modification of set type Update after synchronization.
Modification or deletion of name/first name Loss of the primary link (record saved).Loss of phone No.
Modification of Cost center name or No. See notes 1 to 5 in § Synchronizing Attributesin Real Time
Deletion of the set Deletion of the link. The record is updated andsaved.
Move (cut and paste in the configurationwithout changing name and first name)
The link is automatically recreated.The results are the same as when the set isdeleted and recreated.
table 2.15: Synchronization — Example
Alcatel-Lucent OmniVista 4760 NetworkManagement System
Operations on a Linked Directory Record
OmniPCX 4400/Alcatel-Lucent OmniPCXEnterprise CS
Consequences on the Set Record inConfiguration
Modification of the name.User ID. is saved.
Modification of the name.
Deletion of Set No., ISDN No.(No effect: values reset)
No consequence. The current values arereturned to the directory record
2-31
Alcatel-Lucent OmniVista 4760 NetworkManagement System
Operations on a Linked Directory Record
OmniPCX 4400/Alcatel-Lucent OmniPCXEnterprise CS
Consequences on the Set Record inConfiguration
Record moved in the tree structure No consequence.
2.5.8 Interaction between the Directory and Accounting
Also see module Directory - Overview § Cost Center Management Rules .To gain a better understanding of any of the relationships between these two applications,refer to the examples provided in section § Interaction between the Directory and theConfiguration .
Figure 2.16: Changing Set Assignments — Accounting Initial State
Initial state: Only Michael Buxtor is shown in Accounting, with set 3700. On date T1,James Bridges is linked to the same set and the existing link is broken.
Figure 2.17: Changing Set Assignments — Accounting Final State
Final state: After T1, James Bridges is shown in Accounting and, as of this date, theaccounting records for set 3700 are assigned to him. The entry, Michael Buxtor, is inactiveand shown shaded in the Accounting Organization as accounting records for set 3700transmitted before date T1 are still assigned to him. A detailed accounting report that includesthis date will include both Bridges and Buxtor.
Chapter 2
2-32
2.6 System tab
2.6.1 Overview
Click the System tab of the tree to access the System directory. This directory allows you to:
- Declare PCX networks.
- Synchronize PCX/Alcatel-Lucent OmniVista 4760 Network Management System data.
- Configure application groups and external applications.
- Configure some internal applications (the settings are described in the relevant internalapplications, when appropriate).Contact your installer before making any major modifications to internal applicationsettings (NmcConfiguration entry) or to server settings Alcatel-Lucent OmniVista 4760Network Management System (4760 server name entry).
- Configure RADIUS server. For more details refer to the section module Security -Overview § RADIUS Server .
2.6.2 Description of the System Tab
The System directory is the LDAP server root: o=nmc.
The tree has:
- Four system branches:• Server: server and service parameters (for the system only).• Applications: configuration parameters for application groups and external
applications (reserved to the administrator).• NMCApplications: application security parameters (reserved to the system), managed
via the Security menu.• NmcConfiguration: application display parameters, saved user preferences (reserved
to expert users only):
- PCX networks declared by the administrator, each containing:• Subnetworks• PCXs and Passive Communication Servers (PCSs)The results of the last synchronization are listed in the tree structure:• Telephone extensions and attendant groups• Trunk groups and links between PCXs• The management parameters required for Alcatel-Lucent OmniVista 4760 Network
Management System applications (Entities, DID No., etc.) to operate correctlyFor these latter objects (generated by synchronization), all changes MUST be madevia the Configuration application.
2.6.3 Declaring a PCX Network
To declare a PCX network:
1. Create the network.
2-33
2. Create subnetworks.
3. Create PCXs.
All these branches will be displayed in the Alarm/Topology tree.
2.6.3.1 Creating a Network
To create a network:
1. Select the root.
2. Select the Create > Network command from the shortcut menu. A blank network record isdisplayed in the data area.
3. Complete the attributes via the different tabs.• Network tab
table 2.16: Network Entry — Network Tab AttributesName Mandatory entry
Network Number Mandatory entry
Description
Optional entry.Owner
See also
• Organization tab: This tab gives additional information on network organization.Updating this tab is optional.
• Data Collection tab – reserved for the installation technician. This tab providesinformation on data collection. Updating this tab is optional.
table 2.17: Network Entry — Data Collection Tab Attributes
ISDN Prefix
This parameter concerns the Directory. The ISDN number of theset/extension provided by the PCX (for example, 155667000), canbe completed with this prefix (for example, 0) to obtain 01 55 66 7000.
Location for automaticcreation
If automatic entry creation is enabled, new directory entries will becreated under the Company directory root. This parameter allowsa directory sub-branch to be selected for placement of new entriesfor the same PCX network. See module Directory - Company tab §Location of the Items Automatically Created in the CompanyDirectory .
4. Click Apply. The created network is displayed in the tree under the root.
2.6.3.2 Creating a Subnetwork
To create a subnetwork:
1. Select a network.
2. Select the Create > Subnetwork command from the shortcut menu. A blank subnetworkrecord is displayed in the data area.
3. Complete the attributes on the different tabs:• Subnetwork tab:
Chapter 2
2-34
table 2.18: Subnetwork Entry — Subnetwork Tab AttributesName Mandatory entry
Subnetwork Number Mandatory entry There is a specific section on identifyingsubnetworks and PCXs. See § Identifying PCXs .
Description
Optional entry.Owner
See also
• Organization tab: This tab gives additional information on subnetwork organization.Updating this tab is optional.
• Data Collection tab – reserved for the installation technician. Updating this tab isoptional:
table 2.19: Subnetwork Entry — Data Collection Tab Attributes
ISDN Prefix
This parameter concerns the Directory. The ISDN number of theset/extension provided by the PCX (for example, 155667000), canbe completed with this prefix (for example, 0) to obtain 01 55 66 7000.
Location for automaticcreation
If automatic entry creation is enabled, new directory entries will becreated under the Company directory root. This parameter allowsa directory sub-branch to be selected for placement of new entriesfor the same PCX subnetwork. See module Directory - Companytab § Location of the Items Automatically Created in the CompanyDirectory .
• Synchronization tab: Slice number for general synchronization.• OmniPCX Office Connectivity tab: DN for OmniPCX Office urgent alarms modem
pool - receiving (PPP).• OXE Software Download tab: These are parameters used during the OmniPCX 4400
\ Alcatel-Lucent OmniPCX Enterprise CS software update operation:
table 2.20: Subnetwork Entry — OXE Software Download Tab AttributesSwitchover time A time scheduled indicating when the switchover to the updated
software version will occur on the PCX. Possible values are:• No switchover (default)• Immediate switchover• A number representing a time in 24-hour format by half-hour
increments, for example: 00:00, 00:30, 01:00, ..., 23:30.
Delay for switch onduplicated CPUs
Possible values same as for Switchover time.
Switchback Activates the switchback of a CPU to the old version in case ofsystem reboot.
Delay for switchback(days)
Determines the number of days during which the switchback isactivated. Possible values:• 0 (corresponds to no switchback)• an integer from 1 to 7.
4. Click Apply. The created subnetwork is displayed in the tree under the network.
2.6.3.3 Declaring a PCX
2-35
This section describes how to declare PCXs with a single type of connection (IP for theOmniPCX 4400, Alcatel-Lucent OmniPCX Enterprise CS and OmniPCX Office).The particular case of an OmniPCX Enterprise supporting spatial redundancy (6.1 or higher)and using consequently two IP addresses, is also described.If other different types of connection are used, consult your installation technician to completethe declaration.
2.6.3.3.1 Declaring an OmniPCX 4400
To declare an OmniPCX 4400:
1. Select a subnetwork.
2. Select the Create > OmniPCX4400/Entreprise command from the shortcut menu. A blankPCX record is displayed in the data area.
3. Complete the attributes via the different tabs.• PCX tab:
table 2.21: OmniPCX 4400 / Alcatel-Lucent OmniPCX Enterprise CS Entry — PCX TabAttributes
Name Enter PCX name
Node Number Mandatory entry There is a specific section on identifying PCXs. See§ Identifying PCXs .
Network Value inherited automatically during network creation.
Subnetwork Value inherited automatically during network creation.
Description Optional entry.
IP Address PCX address.
FTP username andpassword
Complete the information for the account authorized to perform FTPtransfer to the PCX. Account ID (adfexc by default) and passwordmust be the same here and on the PCX side.
Process configuration Select this box to enable configuration of this PCX.
Alarm reception mode Possible values:• None (default)• Permanent IP connectivity• via supervision node• RMA calls
Directory Process Select the box to enable loading of the OmniPCX 4400 directory(phone book).
Disable PCX DirectorySynchronization
To prevent PCX telephone configuration updating followingmodification to the directory of the Alcatel-Lucent OmniVista 4760Network Management System: select this option.
Accounting Process Select processing type from the drop-down menu: No, OrganizationUpdate, Detailed accounting, Global accounting with or withoutOmniPCX 4400 record download to Alcatel-Lucent OmniVista 4760Network Management System.
PTP Process Select the box to enable traffic analysis data download.
VoIP performanceprocess
Select the box for VoIP record processing.
Chapter 2
2-36
Declaration node(License Control)
If the license file hardware key is physically present on the PCX,select this option in order to connect to this node in priority.
Note 1:If none of the declared nodes has this option selected, the Alcatel-LucentOmniVista 4760 Network Management System searches, during initial syn-chronization with PCXs, for the holder of the license file and automaticallyenables this attribute on the PCX.
• Organization tab: This tab gives information on the organization associated with thisPCX. To link this PCX to a customer, enter the RCS Customer attribute . Updating thistab is optional.
• Customer Data tab: The parameters are filled in with the values read from the PCXduring the synchronisation phase.
• Connectivity tab: This tab contains connection parameters reserved for expert users(installer, administrator).To declare secure connection to the PCX via SSH/FTP protocol:
table 2.22: OmniPCX 4400 / Alcatel-Lucent OmniPCX Enterprise CS Entry — Connectivity TabAttributes
SSH connection Select the box to allow SSH/FTP connection.
Host Name Enter PCX name.
Note 2:If the “SSH connection” box is not selected, connection is made with TELNET protocol.
• Data Collection tab:
table 2.23: OmniPCX 4400 / Alcatel-Lucent OmniPCX Enterprise CS Entry — Data CollectionTab Attributes
Automatic creationThis parameter is used to enable or disable automatic entry creationin the Company directory when synchronization operations areperformed.
Location for automaticcreation
This parameter allows a directory sub-branch to be selected forplacement of new entries for the same PCX. See module Directory -Company tab § Location of the Items Automatically Created in theCompany Directory .
Record/Ticket Collection
Select processing type from the drop-down menu:• None• Accounting: to enable record collection for accounting
processing by an external application.• VOIP: to enable record collection for VOIP processing by an
external application.• Accounting and VOIP: to enable record collection for accounting
and VOIP processing by an external application.
2-37
UID Construction
As of R5.0, this parameter selects processing type to buid the UID(User IDentificator):• None: the UID is built with the first name and the last name of
the user. In this case, the UID is built as before R5.0.• Extension: the UID is built with the first name, the last name and
the set number of the user (recommended)• Cost Center: the UID is built with the first name, the last name
and the cost center of the user• PCX: the UID is built with the first name, the last name and the
PCX number of the user
• Version tab: This is automatically completed during initial PCX to directorysynchronization.See . module Directory - Synchronizing PCX data § PCX to System DirectorySynchronization .
• Miscellaneous tab: This tab contains parameters for Alcatel-Lucent OmniVista 4760Network Management System administrators to store administrative information oftheir choice. Values remain unchanged after synchronization.
• Software download tab: This tab contains parameters used in the OmniPCX 4400 \Alcatel-Lucent OmniPCX Enterprise CS software update operation.
table 2.24: OmniPCX 4400 / Alcatel-Lucent OmniPCX Enterprise CS Entry — SoftwareDownload Attributes
Username maintenance Login name used to connect to the PCX and perform maintenanceoperations.
Password maintenance Password associated with Username maintenance.
Master node Enter the DN of the PCX master node that receives softwarepackages from the 4760 server and broadcasts them to this client. Ifthis entry is left blank, this node is considered a master.
Notes:A master PCX must be accessible by the 4760 server with Ethernet con-nectivity or via an IRAD board. IP tunnelling is not advised.
If the client PCX is connected to the master by a trunk without IP tunnel, thesoftware update will fail on the client.
Apply in local accountparameters
If checked, the values of the next four parameters will be used asdefined for this PCX. Otherwise, the values defined for thesubnetwork will be used.
Switchover time A time scheduled indicating when the switchover to the updatedsoftware version will occur on the PCX. Possible values are:• No switchover (default)• Immediate switchover• A number representing a time in 24-hour format by half-hour
increments, for example: 00:00, 00:30, 01:00, ..., 23:30.
Delay for switchover onduplicated CPUs
Possible values same as for Switchover Time.
Switchback Activates the switchback of a CPU to the old version in case ofsystem reboot.
Chapter 2
2-38
Delay for switchback(days)
Determines the number of days during which the switchback isactivated. Possible values:• 0 (corresponds to no switchback)• an integer from 1 to 7.
The remaining attributes on the Software download tab are updated duringsynchronization. See module Directory - Synchronizing PCX data § PCX to SystemDirectory Synchronization .
4. Click Apply.The PCX created is displayed in the tree under the subnetwork. If this is not the case,check all attributes by repeating the procedure.
2.6.3.3.2 Declaring an OmniPCX Office
To declare an OmniPCX Office:
1. Select a subnetwork.
2. Select the Create > OmniPCX Office command from the shortcut menu. A blank PCXrecord is displayed in the data area.
3. Complete the attributes in the different tabs.PCX tab:
table 2.25: OmniPCX Office Entry — PCX Tab AttributesName Enter PCX name
Node Number Mandatory entry There is a specific section on identifying PCXs. See§ Identifying PCXs .
Network Value inherited automatically during network creation
Subnetwork Value inherited automatically during network creation
Description Optional entry.
IP Address PCX address
FTP password Complete the information on the account authorized to perform FTPtransfers to the PCX. Account ID (tuxalize by default) and passwordmust be the same here and on the PCX side.
Process configuration Select this box to enable the configuration of this PCX.
Alarm reception mode Possible values:• None (default)• HTTP notification• Permanent IP connectivity• PPP urgent alarm call
Accounting Process Select processing type from the drop-down menu: No, OrganizationUpdate, Detailed accounting, Global accounting with or withoutOmniPCX Office record download to Alcatel-Lucent OmniVista 4760Network Management System.
Default Cost center Complete this field if you want chargeable entries to be grouped inthe same PCX cost center (phone book). For more information, see §module Accounting - Basic operation § Managing OmniPCX Officeand Alcatel Office Cost Centers .
2-39
VoIP performanceprocess
Select the box for VoIP record processing.
Internet Access hostname
Enter name.
Organization tab: This tab gives information on the organization associated with this PCX.To link this PCX to a customer, enter the RCS Customer attribute. Updating this tab isoptional.Connectivity tab: This tab contains connection parameters reserved for expert users(installer, administrator).Data Collection tab:
table 2.26: OmniPCX Office Entry — Data Collection Tab Attributes
Record/Ticket Collection
Select processing type from the drop-down menu:• None• Accounting: enables record collection for accounting processing
by an external application.• VOIP: to enable record collection for VOIP processing by an
external application.• Accounting and VOIP: to enable record collection for accounting
and VOIP processing by an external application.
Alarm Management tab:Version tab: This tab is automatically completed during initial PCX to directorysynchronization.Miscellaneous tab: This tab contains parameters for Alcatel-Lucent OmniVista 4760Network Management System administrators to store administrative information of theirchoice. Values remain unchanged after synchronization.
4. Click Apply.The PCX created is displayed in the tree under the subnetwork. If this is not the case,check all attributes by repeating the procedure.
2.6.3.3.3 Declaring an Alcatel-Lucent OmniPCX Enterprise CS
Declare an Alcatel-Lucent OmniPCX Enterprise CS as you would an OmniPCX 4400 (see §Declaring an OmniPCX 4400 ).
However, in the particular case of an OmniPCX Enterprise supporting the spatial redundancy(6.1 or higher) you must enter a second IP address for the IP address attribute.
table 2.27: Alcatel-Lucent OmniPCX Enterprise CS Entry — CPU Redundancy AttributesIP Address Enter the first CPU IP Address
Note:
The two IP addresses can be given in any order, the system will put them
automatically in the correct order in function of the CPU role.
IP Address Enter the second CPU IP Address
2.6.3.3.4 Declaring a Pseudo PCX
Pseudo PCXs are useful on certain high-traffic sites that generate a large number ofaccounting records. Selective record loading and filtering may use considerable systemresources and result in lengthy processing times.
Chapter 2
2-40
These important functions can be performed by a device other than the Alcatel-LucentOmniVista 4760 Network Management System server: a PC referred to as a Pseudo PCX,fully dedicated to these tasks.In this case, the Alcatel-Lucent OmniVista 4760 Network Management System server merelydownloads the data files already filtered from the pseudo PCX.To manage accounting records only, a pseudo PCX is sufficient. If the configuration must alsobe managed, a PCX must be declared. The PCX and the pseudo PCX must be declared onthe same subnetwork.
To declare a pseudo PCX:
1. Select a subnetwork.
2. Select the Create > Pseudo PCX command from the shortcut menu. A blank PCX recordis displayed in the data area.
3. Complete the attributes via the different tabs.
table 2.28: Pseudo—PCX Entry — General TabsName Enter PCX name
Node Number Mandatory entry There is a specific section on identifying PCXs. See§ Identifying PCXs .
Network Value inherited automatically during network creation.
Subnetwork Value inherited automatically during network creation.
IP Address PCX address.
FTP username andpassword
Complete the information on the account authorized to perform FTPtransfers to the PCX.
Organization tab:This tab gives additional information on network organization. Updatingthis tab is optional.ConnectivityThis tab contains connection parameters reserved for expert users (installer,administrator).Data Collection tab: This tab displays information on the last downloads carried out fromthis PCX
table 2.29: Pseudo—PCX Entry — Data Collection Tab Attributes
Record/Ticket Collection
Select processing type from the drop-down menu:• None• Accounting: to enable record collection for accounting
processing by an external application.• VOIP: to enable record collection for VOIP processing by an
external application.• Accounting and VOIP: to enable record collection for accounting
and VOIP processing by an external application.
MiscellaneousThis tab contains information parameters free for use for Alcatel-LucentOmniVista 4760 Network Management System administrators. They can be used to storeadministrative information and remain inchanged after synchronization.
4. Click Apply.The PCX created is displayed in the tree under the subnetwork. If this is not the case,check all attributes by repeating the procedure.
2.6.3.4 Discovery and Synchronization of a Passive Communication Server
2-41
The main function of a Passive Communication Server (PCS) is to provide continuity of servicefor a customer area in case of network trouble between the Alcatel-Lucent OmniPCXEnterprise CS media gateway and the Alcatel-Lucent OmniPCX Enterprise CS call server.When there are no network problems, the PCS is in passive mode. In case of network trouble,the PCS switches to active mode and acts as the Alcatel-Lucent OmniPCX Enterprise CS callserver for its associated media gateways and IP phones. When in active mode, the PCSmaintains in its own database the accountingand Voice over IP tickets. The Alcatel-LucentOmniVista 4760 Network Management System must synchronize the PCS to get thisinformation.
The Alcatel-Lucent OmniVista 4760 Network Management System discovers a PCSautomatically during synchronization with its associated PCX. In order to discover a PCS andcreate it in the System Directory, you must have:
- a LAN type connection between the Alcatel-Lucent OmniPCX Enterprise CS and theAlcatel-Lucent OmniVista 4760 Network Management System
- at least one valid license among: Accounting, Traffic Performance, Voice over IP, orConfiguration
A PCS appears in the hierarchy under its associated PCX. A PCX can be associated with 0 toseveral PCSs. The PCS name is read from the Alcatel-Lucent OmniPCX Enterprise CSconfiguration data. If no name exists, the Alcatel-Lucent OmniVista 4760 NetworkManagement System creates the name with the following format: "PCS_" + the physical IPaddress of the PCS. You can modify the PCS name.
The following attributes in the System directory are associated with the PCS:
PCS tab
Chapter 2
2-42
Name The PCS name is inherited automatically from theAlcatel-Lucent OmniPCX Enterprise CS during PCScreation in the System Directory. The name can bechanged.
Subnetwork - Node Number Value inherited automatically from the Alcatel-LucentOmniPCX Enterprise CS during PCS creation in theSystem Directory.
Network Value inherited automatically from the Alcatel-LucentOmniPCX Enterprise CS during PCS creation in theSystem Directory, and updated automatically when thenetwork name changes.
Subnetwork Value inherited automatically from the Alcatel-LucentOmniPCX Enterprise CS during PCS creation in theSystem Directory, and updated automatically when thesubnetwork name changes.
PCX The Alcatel-Lucent OmniPCX Enterprise CS nameinherited automatically during PCS creation in theSystem Directory, and updated automatically when theAlcatel-Lucent OmniPCX Enterprise CS name changes.
Description Optional entry
IP Address The PCS IP address used by the Alcatel-LucentOmniVista 4760 Network Management System tocommunicate with PCS. This IP Address is automaticallyinitialized during the first synchronization with the valueof the Physical IP Address. It can be updated in caseNAT/VPN publish a different public IP address reachableto Alcatel-Lucent OmniVista 4760 Network ManagementSystem.
Physical IP Address The PCS IP address used by the Alcatel-LucentOmniPCX Enterprise CS to communicate with the PCS.This IP address uniquely identifies the PCS.
FTP Username Value inherited automatically during PCS creation in theSystem Directory. The value is not automaticallyupdated when the Alcatel-Lucent OmniPCX EnterpriseCS FTP username changes. You must enter the newFTP Username.
FTP Password Value inherited automatically during PCS creation in theSystem Directory. The value is not automaticallyupdated when the Alcatel-Lucent OmniPCX EnterpriseCS FTP password changes. You must enter the newFTP Password.
Connectivity tab
2-43
IP Address The PCS IP address used by the Alcatel-LucentOmniVista 4760 Network Management System tocommunicate with PCS. This IP Address is automaticallyinitialized during the first synchronization with the valueof the Physical IP Address. It can be updated in caseNAT/VPN publish a different public IP address reachableto Alcatel-Lucent OmniVista 4760 Network ManagementSystem
Physical IP Address The PCS IP address used by the Alcatel-LucentOmniPCX Enterprise CS to communicate with the PCS.This IP address uniquely identifies the PCS.
FTP Username Value inherited automatically during PCS creation in theSystem Directory. The value is not automaticallyupdated when the Alcatel-Lucent OmniPCX EnterpriseCS FTP username changes. You must enter the newFTP Username.
FTP Password Value inherited automatically during PCS creation in theSystem Directory. The value is not automaticallyupdated when the Alcatel-Lucent OmniPCX EnterpriseCS FTP password changes. You must enter the newFTP Password.
Connectivity Select:- LAN: to connect the PCS via its IP address- None: The PCS is not directly reachable from the
Alcatel-Lucent OmniVista 4760 NetworkManagement System (different networks). In thiscase, the PCS is reachable via its Com. Server.
Data Collection tab
PCS Id Representation of the PCS Physical IP Address inhexadecimal. This value is automatically built from the IPaddress value. The PCS Id is used as a suffix foraccounting file names available to external applications(see module Accounting - Overview § CollectingRecords ).
Last Polled Accounting File Information on the latest download from the PCS.
Last Polled PTP File Information on the latest download from the PCS.
Last Polled IP File Information on the latest download from the PCS.
Miscelleanous tab
Miscellaneous field headers can be customized to suit the information they provide.
Version tab
PCX Release Automatically completed during PCS synchronization.
PCX Patch ID Automatically completed during PCS synchronization.
MIB Delivery Automatically completed during PCS synchronization.
MIB Patch ID Automatically completed during PCS synchronization.
Chapter 2
2-44
Software download tab
This tab contains parameters used in the PCS software update operation.
table 2.34: PCS Entry — Software Download AttributesUsername maintenance Login name used to connect to the PCX and perform maintenance
operations.
Password maintenance Password associated with Username maintenance.
Master node Enter the DN of the PCX master node that receives softwarepackages from the 4760 server and broadcasts them to this client. Ifthis entry is left blank, this node is considered a master.By default, this field contains the DN of the associated Com. Serverwhich is its master.
Apply in local accountparameters
If checked, the values of the next four parameters will be used asdefined for this PCS. Otherwise, the values defined for thesubnetwork will be used.
Switchover time Select the switchover time to the updated software version. Possiblevalues are:- No switchover (default)- Immediate switchover- 00:00, 00:30, 01:00, ..., 23:30
Last Context ID Unique Identifier of software update operation
Report file Provides status operation for the selected PCS
Physical IP Address The PCS IP address used by the Alcatel-Lucent OmniVista 4760Network Management System to communicate with PCS. This IPaddress uniquely identifies the PCS.
Export language (PCX) Automatically filled during PCX/PCS synchronization
PCX Release Automatically filled during PCX/PCS synchronization
PCX patch ID Automatically filled during PCX/PCS synchronization
Dynamic patch Automatically filled during PCX/PCS synchronization
Secure PCX release Automatically filled during PCX/PCS synchronization
2.6.3.5 Identifying PCXs
For the OmniPCX 4400 and Alcatel-Lucent OmniPCX Enterprise CS:The Node Number field must comply with PCX configuration and be in one of the followingforms:
- R x 100 + N, by default.
- R x 1000 + N, if specified at node installation.
Note 1:R = Subnet No. and N = Node No.
Note 2:For the Alcatel-Lucent OmniPCX Enterprise CS, errors made during entry are not corrected; if an er-ror is made the node must be deleted and created again.
Example:
For node 5 (N=5) which belongs to subnetwork 2 (R=2), according to the case:
2-45
- Node Number field = 205
- Node Number field = 2005
For the OmniPCX Office :In the same subnet, the node number entered must be unique and different from the nodenumber of the OmniPCX 4400 and Alcatel-Lucent OmniPCX Enterprise CS.The node number entered and real OmniPCX Office number may be different.
2.6.3.6 Creating Applications Groups and External Applications
This feature is used to launch:
- Remote URLs via a Web browser (for example, Omnitouch UC administration).
- Windows or Java executable files (other than Alcatel-Lucent OmniVista 4760 NetworkManagement System classes).
2.6.3.6.1 Creating an Applications Group
At installation, no applications groups are created.
To create an applications group:
1. In the nmc root, expand the Applications entry.
2. Select ApplicationsGroups.
3. Select the Create>Applications group command from the shortcut menu.
4. Complete the attributes.
table 2.35: Application Group Entry AttributesName Mandatory entry
Description Optional entry.
Label Optional entry.
Order number Enter a number to enable applications groups to be classified in theapplication launch panel.
Note 1:The “4760 App.” group (reserved for Alcatel-Lucent OmniVista 4760 Network Management Systeminternal applications), cannot be configured in the Directory and is placed in the first position in thelaunch panel.
5. Click Apply.The applications group created is displayed in the tree structure under theApplicationsGroups entry. If this is not the case, check all attributes by repeating theprocedure.
Note 2:Up to 10 groups (maximum) can be created.
2.6.3.6.2 Creating an External Application
At installation, no external applications are created.In the System directory, two tabs can be used to configure an application: the General andUser interface tabs.
Chapter 2
2-46
To configure an external application:
- General tab. This tab allow the application to be identified and the attributes required for itsexecution to be configured (executable, arguments, run directory).
Figure 2.19: System Directory — Create External Application — General Tab
1. In the Applications entry, select ExternalApplications.2. Select the Create>Applications command from the shortcut menu.3. Complete the attributes.
table 2.36: Application Entry — General Tab AttributesName This must be entered (unique identifier in the Directory(cn)).
Description Optional entry.
Type of application Double-click the selected field and select the “Windows application”or “Default browser” drop-down menu.
Name of the binary(executable)
If application type is “Windows application”, complete the Name ofthe binary (executable) field: For example:C:\WINNT\NOTEPAD.EXE.
2-47
Argument List If application type is “Default browser”, enter the URL to be opened:For example: http://Alcatel.fr:8080/webAdmin/AdminServer.If application type is “Windows application”, enter the parameters ofyour Windows application: For example: for Notepad.exe, theargument c:\Doc\read me.txt opens the file “read me.txt” in Notepad.
Run directory Optional entry.
Access rights Double-click the field and select the one of the classes listed in thedrop-down menu to assign assess rights to the application (seemodule Security - Overview ). The same rights as an Alcatel-LucentOmniVista 4760 Network Management System internal applicationmay be assigned.The default value of the attribute is External applications 1.
4. Click Apply.The applications created is displayed in the tree structure under theExternalApplications entry. If this is not the case, check all attributes by repeating theprocedure.
- User interface tab. This tab displays user interface attributes.
Figure 2.20: System Directory — Create External Application — User Interface Tab
Chapter 2
2-48
1. Select an external application in the ExternalApplications entry.2. Complete the attributes.
table 2.37: Application Entry — User Interface Tab AttributesLabel Optional entry (16 characters maximum).
Belonging to the group Mandatory entry for the application to be added to the applicationlaunch panel. This attribute is used to link the application with anexternal applications group.1. Click to the right of Belonging to the group. The link editor is
displayed in a separate window.2. Complete the search area.3. Click to launch a search and display the result in the data
area.4. Select the result of the search.5. Click OK. The link linking the application with an applications
group is displayed in the Belonging to the group field.6. End.
Order number Enter a number to specify the order in which the application will bedisplayed in the group in the application launch panel.
Tooltip Optional entry. This attribute is used to display full application namewhen the cursor is positioned over the symbol representing theapplication.
Icon 32x32 (GIF) This attribute is used to select the application icon. Double-click thefield to select a file (via a file selection window). The file must be inGIF format (preferably 32x32). The icon is displayed in theapplication launch panel. If this attribute is not configured, a defaulticon is assigned to the application.
3. Click Apply.The client application must be restarted to apply the modifications to the Directory anddisplay the applications in the application launch panel.
2.6.3.6.3 Deleting an External Application or Applications Group
To delete an application:
1. In the Applications entry, expand ExternalApplications.
2. Select an application.
3. Select the Delete command from the shortcut menu.
To delete an applications group:
1. In the Applications entry, expand ApplicationsGroups.
2. Select an applications group.
3. Select the Delete command from the shortcut menu.
2.6.4 Registering an Eye Box
Eye Box is a software suite that offers Internet, voice and data solutions for the small andmedium enterprise.
2-49
To register an Eye Box:
1. Select the Network/ Subnetwork for Eye Box registration, from the System tree.
2. Select Create >Eye Box from the Shortcut menu. The window for registering the Eye Boxis displayed. By default the window is in General tab.
Figure 2.21: System Directory Window: Creating an Eye Box
3. Complete the following attributes in the General window.
table 2.38: Eye Box Registration: General Tab AttributesAttributes Values
Name The name of the Eye Box to be registered
Description Description text for the Eye Box
URL for management The URL for accessing the Eye Box Admin application in the Eye Boxserver
Subnetwork The name of the subnetwork to which the Eye Box is connected
Network The name of the network to which the Eye Box is connected
Chapter 2
2-50
4. Select Organization tab.
5. Complete the following attributes in the Organization window.
table 2.39: Eye Box Registration: Organization Tab AttributesAttributes Values
Company Company name
RSC Client Double click the selected field and select the RSC client from the displayedEdit DN window
Department Department name
City City name
Country Country name
6. Select Miscellaneous tab.
7. If there are any miscellaneous data, enter them in the fields Misc. 1 to Misc. 5 in theMiscellaneous window. The miscellaneous field headers can be customized. For moreinformation refer to module Interface - Customizing dictionaries .
8. Click Apply to register the Eye Box.
2.7 Synchronizing PCX data
2.7.1 Overview
PCX data synchronization is bi-directional:
- PCX to Directory synchronization means the loading of PCX telephone data to updatesystem data required by Alcatel-Lucent OmniVista 4760 Network Management Systemapplications. This synchronization can be performed manually, or automatically, or can bescheduled.
- Updating System directory data can extend to the company directory via links.
- Company directory to PCX synchronization is the updating of PCX data following changesto specific company directory fields (Name, First name, Cost center). Thissynchronization is automatically performed in real time.
Important:
PCX data synchronization only concerns the OmniPCX 4400 and Alcatel-Lucent OmniPCX Enter-
prise CS, it does not apply to the OmniPCX Office.
Types of data synchronized:MIB, DID range, Entities, Attendant consoles, Attendant groups, Logical attendant, Logicalattendant group, Project number, Shelf, Board, Logical links, Trunk group, Voice mail, Users,Directory, Data terminals, Speed dial numbers, Remote users. Also attributes related toOmniPCX 4400 \ Alcatel-Lucent OmniPCX Enterprise CS software updates: Physical IPaddress, Export language, PCX release, PCX patch ID, PCX dyn patch ID, PCX securerelease, Master PCX report status.
Data not synchronized and free for use:Some attributes are free for use for the Alcatel-Lucent OmniVista 4760 Network ManagementSystem administrator. As they are not taken into account by the PCX-4760 synchronization
2-51
process, they can be used to store administrative information. They remain unchanged afterdaily or weekly synchronizations. Network expert members and Alcatel-Lucent OmniVista4760 Network Management System administrators can customize these attribute names usingthe CustomDict tool. The following attributes are customizable:
- OmniPCX 4400 \ Alcatel-Lucent OmniPCX Enterprise CS \ OmniPCX Office:• Attributes: pbmisc1 to pbmisc5• Tab: Miscellaneous
- Shelf:• Attributes: rackmisc1 to rackmisc5• Tab:Miscellaneous
- Board:• Attributes: boardmisc1 to boardmisc5• Tab: Miscellaneous
- Users:• submisc1 to submisc5• Tab: Miscellaneous
2.7.2 PCX to System Directory Synchronization
A PCX to Directory synchronization can be:
- Partial: modification of data that has changed since the last synchronization.
- Complete: update of all System directory data originating from the PCX,
- Automatic in real time, see module Directory - Managing links between the Directory andthe PCX (option).
- Dedicated to software download information
- Global: this synchronization synchronizes PCXs of all available networks. This operation isstarted from the root of the system directory (nmc). Daily and weekly synchronizations areglobal synchronizations. In case of a synchronization failure for 32 days, Alcatel-LucentOmniVista 4760 Network Management System Clients switch to restricted mode. The onlyway to return to "normal" mode is to perform an adequate synchronization on each nodes.
Partial or complete synchronization can be performed in two modes:
- Immediate
- Scheduled
By default, a partial synchronization is scheduled every day and every week. A completesynchronization is performed in specific cases:
- Selection of this type of synchronization by the manager
- PCX initial synchronization
- Repetitive failure of partial synchronization. The number of failures is managed in thesystem directory: nmc/servername/Server/SyncLdapPbx/Specific/ Maximum number offailed general synchronization
Synchronization is performed one PCX following another, in four stages:
1. Connecting to the PCX.
Chapter 2
2-52
2. Downloading specific PCX data to the System directory.
3. Triggering automatic link creation procedures between telephone extensions and persons(Company directory option).See module Directory - Managing links between the Directory and the PCX .
4. Updating company directory entries.
2.7.2.1 Synchronized Data
After the first synchronization, three branches are displayed under the PCX branch:
- Configuration: entities, DID ranges.
- Hardware: shelves, boards, trunk groups, segments.
- Phone Devices: extensions.
Check that these three branches are present after the initial synchronization.
To check the last synchronization performed:
1. Click the System tab.
2. Select the PCX (path: nmc > network > subnetwork >PCX).
3. Check attribute values in Data collection:• Date Of Last Modification, must correspond to the date of the last synchronization.• Last Polled Accounting File, if the Accounting Process option is selected in PCX
configuration.• Last Polled PTP File• Last Polled IP File
2.7.2.2 Partial Synchronization
Partial synchronization includes changes performed since the date of last loading for entries ofthe following types:
- Users*
- Directory
- Data terminals
- Speed dial numbers*
- Remote users*
(*) "User", "Speed dial number" and "Remote user" entries are loaded on nodes depending onthe attributes configured on the nodes (see Directory > System >, then, for each PCX, > DataCollection tab, "Load System Speed Dial Number", "Load Users Alias" and "Load RemoteUser" attributes).
Modifications made to any other data required for correct operation of the Alcatel-LucentOmniVista 4760 Network Management System are synchronized without taking the date of thelast change into consideration. This data consists of:
- DID range
- Entities
- Attendant console
2-53
- Attendant groups
- Logical attendant
- Logical attendant group
- Project number
- Shelf
- Board
- Links
- User groups
- Trunk group
- Voice mail
- etc.
2.7.2.3 Data Synchronization for Software Download
The data synchronization process for software download updates the data of the synchronizedPCX. The synchronized data are:
- The main CPU IP address
- The standby CPU IP address
- The software release
2.7.2.4 Complete Synchronization
Complete synchronization includes changes made to all entries without considering the date ofthe last loading.
2.7.2.5 Procedure for Immediate Mode
1. Select, as appropriate:• A PCX, to synchronize the data of this PCX.• A subnetwork, to synchronize the PCXs of this subnetwork.• A network, to synchronize the PCXs of this network.
2. Open the shortcut menu and select, as appropriate:• The Synchronization > Complete command.• The Synchronization > Partial command.
The Scheduler is displayed to perform any synchronization scheduling required.
3. Check Now, and keep Repeat: noneSee module Scheduler - Overview .
4. by either:• Click Apply to launch synchronization without closing the task/job scheduling window.
Three tasks will be performed simultaneously.To display the status of any of these tasks:• Select Display the parameters.• In Description, choose between Partial or Complete LDAP/PCX
Chapter 2
2-54
Synchronization (as appropriate), Load accounting tickets and PTP counters,or Load accounting tickets and PTP counters or Load IP tickets.
• To display the status of any of the tasks, click the Status tab.• Click OK to launch synchronization and close the task/job scheduling window. PCX
data is synchronized.In the tree, the PCX Configuration, Hardware and Phone devices branches are created orupdated when synchronization is complete.
2.7.2.6 Procedure for Scheduled Mode
1. Select, as appropriate:• A PCX, to synchronize the data of this PCX.• A subnetwork, to synchronize the PCXs of this subnetwork.• A network, to synchronize the PCXs of this network.
2. Open the shortcut menu and select, as appropriate:• The Synchronization > Complete command.• The Synchronization > Partial command.
The Scheduler is displayed to perform any synchronization scheduling required.
3. Select As scheduled, then configure scheduling.See module Scheduler - Overview .
4. by either:• Click Apply to launch synchronization without closing the task scheduling window.• Select OK to launch synchronization and close the task scheduling window.PCX data will be synchronized at the scheduled time.
2.7.2.7 Real-Time Synchronization
Real-time synchronization is performed via event reporting.
Each modification of an attribute on a PCX leads (in real time) to:
- The sending of an event.
- The triggering of a synchronization on the transmitting object.
- Updating the System directory.
- Any update of the Company directory.
See module Directory - Managing links between the Directory and the PCX .
Configuring settings:
Real-time synchronization requires activation of event reception in the System directory andevent transmission on each PCX.
In the System directory (can only be accessed by authorized users). This operation isperformed for each individual PCX:
1. Select a PCX
2. Select the PCX tab
3. Select a mode different from None for the Alarm Reception mode parameter
4. Apply the changes.
2-55
In PCX Configuration:
1. In online (connected) mode (PCX tab), select Installation > 1.
2. Select the Synchro.4400 - 47xx directory attribute.
3. Apply the changes.
2.7.3 Synchronization Optimization
2.7.3.1 Limitation of Data Retrieved at First Synchronization
As of R4.2, it is possible to limit the ticket collection during the first synchronization. Themanager can select the most recent tickets only. This limitation reduces the amount of dataexchanged and the length of synchronization. By default the number of days is specified as 2and is configurable.
To configure synchronization optimization:
- Select the path nmc > 4760_Server_Name > Servers > 4760_Server_Name >SyncLdapPbx, then click the Specific
- Select the Days of records retrieved during first synchronization attribute and enterthe number of days for which the last records are collected.
This attribute is used only for the first synchronization of a PCX, i.e. when no accounting ticketor no VOIP ticket or no PTP ticket are recorded for the defined PCX.
This attribute is defined for all PCXs associated to the Alcatel-Lucent OmniVista 4760 NetworkManagement System.
2.7.3.2 Synchronization by Slice
Synchronization by slice is useful for large networks and consists in distributingsynchronization over several days (one slice per day).Enter the ID of the subnet group (slice) and the number of slices in the System directory.To configure Synchronization by slice in the System directory:
1. Select the path nmc > 4760_Server_Name > Servers > SyncLdapPbx, then click theSpecific tab
2. Select the syncldappbxslicesnumber attribute and enter the number of slice in thesystem
3. For each subnetwork of the System Directory define its slice number:• Open the Synchronization tab• Enter the slice number in the Slice number for general synchronization parameter
2.7.3.3 Simultaneous Synchronization of PCX
By default, the synchronization process synchronizes each PCX one by one. In case of manyPCXs to synchronize, this can take some time.
Simultaneous synchronization (also called parallel synchronization), where several PCXs aresynchronized together, allows to greatly reduce synchronization time.
For large networks (hundreds of PCXs), synchronization should not take more than eighthours, and simultaneous synchronization is mandatory.
Chapter 2
2-56
To configure simultaneous synchronization:
- In the Directory application, select the System tab
- Open your server branch
- Open the Servers branch
- Click SyncLdapPbx entry to open the synchronization properties window
- Open the Specific tab
- In the field: Number of simultaneous synchronizations, enter the number of PCXs tosynchronize simultaneouslyUntil R4.2, up to 8 PCXs can be synchronized simultaneously.As of R5.0, up to 18 PCXs can be synchronized simultaneously.
2.8 Web Directory Client - Operation
2.8.1 Web Directory Client Overview
The Web Directory Client allows you to access the Company Directory using one of thefollowing browsers on a Windows platform:
- Microsoft Internet Explorer 7
- Mozilla Firefox 2.0
In a variety of languages you can use the Web Directory Client to:
- view and print directory entries,
- make an automatic call or send an e-mail,
- modify the information in your directory entry (subject to authentication),
- create or modify other entries, depending on your access rights (subject to authentication),
- maintain a Personal Address Book (subject to authentication).
2.8.2 Connecting with a Browser
1. Open an HTML browser window on a PC that can access the Alcatel-Lucent OmniVista4760 Network Management System server over the network.
2. In the browser address bar enter:• either the server IP address,• or the server URL, for example: http://server name.The Alcatel-Lucent OmniVista 4760 Network Management System Directory Accesswindow will appear.In the event of an addressing problem, consult the network administrator. Theadministrator will find useful technical information in the installation documentation.
3. Choose a language from the drop down box in the upper right corner of the window.
4.
2-57
.
The Web Directory Client window will appear.
2.8.3 The Web Directory Client Window
Figure 2.22: Web Directory Client Window
The Web Directory Client window has four main areas:
- Area 1:The logo bar at the top of the window contains three toolbox icons: forAuthentication, Associated Station Management, and on-screen Help.
- Area 2: The left side of the window diplays the authentication status, and contains theName Search box for quick searches, directory bookmarks, and themes.
- Area 3:The central area contains five tabs: Browse, Search, Results, Detail, and Editwith which you view and modify directory entries.
- Area 4:The right panel contains control buttons which vary depending on the current taband authentication.
Chapter 2
2-58
The following sections describe how to perform various tasks in the Web Directory Clientwindow.
2.8.4 Logging in — Authentication
You must identify yourself to the Alcatel-Lucent OmniVista 4760 Network Management Systemto perform the following tasks:
- Manage your personal address book.
- Create or modify your directory entry.
- Customize the view, print, and update parameters.
- View confidential information.
Note 1:This task requires additional access rights granted by the administrator.
- Manage directory entries other than your own.
Note 2:This task requires additional access rights granted by the administrator. If you are an anonymoususer, or have not be granted rights, you may access this function. It is only when applying changesthat the message "The client user access privileges are insufficient" will appear.
To log in:
1. Click the icon, located in the upper right part of the window.
A login dialog box is displayed.
2. Enter your Alcatel-Lucent OmniVista 4760 Network Management System login andpassword and click Valid.
3. If there is a problem with authentication, an error message will appear in red. In this case,correct the error and click Valid to try again, or click Cancel to abandon the task.
To disconnect:
1. Click the Authentication icon , located in the upper right part of the window.
A confirmation dialog box is displayed.
2. Click Disconnect.
2.8.5 Associating your Phone Set
In order to make an automatic call, you must associate your phone set with the Web DirectoryClient session:
1. Click the Associated Station Management icon, located in the upper right part of
the window.An Associated Station Management dialog box appears.
2. Enter your extension and secret code for the phone and click Valid.
3. If there is a problem with association, an error message will appear in red. In this case,
2-59
correct the error and click Valid to try again, or click Cancel to abandon the task.
Note:
You are not required to identify yourself each time you make a call. A cookie associated with the current
browser is saved on your computer. The cookie contains the associated set authentication and is used
whenever you access the Web Directory Client with the same browser.
2.8.6 Browsing the Directory Tree
1. To navigate the directory tree:• Click the directory level icons in the Browse tab.• Use [Tab] and [Shift] + [Tab] to move from one level to another.• Use [Enter] to display the sub-levels for a directory level.• Click the bookmarks displayed on the left side of the window.
2. To create a bookmark, select the directory level in the Browse tab. Click the Bookmarkthis Level icon , or [Alt] + [+] (Firefox browser only).
The bookmark appears on the left side of the window.
Note 1:You can create up to seven bookmarks, including the Address Book bookmark.
3. To delete a bookmark, select the bookmark you wish to delete. Click the Delete thisBookmark icon , or [Alt] + [-] (Firefox browser only).
The bookmark disappears from the left side of the window.
4. To display attributes for levels in the directory tree, select the directory level and click theLevel Attributes icon .
The level attributes display in the Detail tab.
Note 2:
You can return to the Browse tab from anywhere on the Web Directory Client interface with [Alt] + [b]
(Firefox browser only).
2.8.7 Searching for a Directory Entry
To perform a quick search:
1. Click a bookmark or the directory level you wish to search in the Browse tab.
2. Enter the beginning letters of the person's last name in the Name Search box.
3. Click OK.A list of matching entries appears in the Results tab.
Note 1:
You can return to the Name Search box from anywhere on the Web Directory Client interface with [Alt] +
[q] (Firefox browser only).
To perform an advanced search:
Chapter 2
2-60
1. Click a bookmark or the directory level you wish to search in the Browse tab.
2. Click the Search tab.The path of the selected directory level appears at the top of the tab.Filter criteria boxes appear.
3. Using the drop down boxes, select the field to search and the type of operation. In the lastfield, enter the search value.
Remark:Searches are not case sensitive. For example, if you enter paul or PAUL. the search will return theentry Paul in both cases. However, letters with accents are differentiated from unaccented letters.
4. To add a criteria, click the More criterias icon , or [Alt] + [+] (Firefox browser only).
5. To delete a criteria, click the Less criterias icon , or [Alt] + [-] (Firefox browser
only).
6. To clear all search criteria, click the Clear icon , or [Alt] + [c] (Firefox browser only).
7. Click OK to perform the search.A list of matching entries appears in the Results tab.
Note 2:
Results of a search request depend on your access rights to the Directory application.
2.8.8 Viewing Directory Entries
To view directory entries:
1. Perform a search, or select the directory level in the Browse tab, then click the Resultstab or [Alt] + [r] (Firefox browser only).Directory entries display in a grid on the Results tab. The directory path of the displayedentries shows on the line above the grid.
2. To sort the entries, click on the column title of the column you wish to sort by.
3. Use [Tab] and [Shift] + [Tab] to move from one Extension to the next in the grid.
Note:
You can customize the attributes that display. See § Customizing the Results Display and Print Paramet-
ers .
2.8.9 Printing Directory Entries
To print directory entries:
1. Find the directory entries you wish to print using a search or by browsing.The resulting list of directory entries displays in the grid.
2. From the Results tab, click the Print All Results icon , or [Alt] + [p] (Firefox browser
only).A print preview window appears along with the print configuration dialog box.
2-61
Note:
You can customize the attributes that print. See § Customizing the Results Display and Print Parameters
.
2.8.10 Viewing Detailed Information for an Entry
To view the details for a directory entry:
1. From the display on the Results tab, click the Name field of the entry you want to seedetails for.The attributes for the entry appear in the Detail tab.
2. To view all the attributes for this entry, click the All Attributes icon .
A window with the additional attributes appears. Confidential information appearsdepending on your access rights granted by the administrator.
3. To list the people associated with an assistant, click the List of individuals linked to thissecretary icon .
The list of people is displayed in the Results tab.
4. To list the assistants associated with a person, display the person's directory entry in theDetails tab. Click the List of individuals linked to this manager icon .
The list of assistants is displayed in the Results tab.
Note 1:
You can use [Alt] + [r] to return to the Results tab from the Detail tab (Firefox browser only).
Note 2:
You can customize different attributes to display on the Detail tab. See § Customizing the Detail and Edit
Parameters .
2.8.11 Making an Automatic Call
Important:
This feature is not available to you if you are an OmniPCX Office user.
To make an automatic call using the Web Directory Client:
1. Display the directory entry for the person you wish to call. Depending on the STAP rightsconfigured for your set, you may first have to pick up the receiver.
Note:The number you are calling must be able to be dialed. Otherwise, the administrator must write a pre-fix rule (see the module Directory - Managing prefixes ).
2. From the Results tab, or the Details tab, click the person's Extension. If you have beenidentified, the call is made. If not, a window requesting you to identify the set from whichyou are making the call is displayed.
3. The Web Directory Client allows 3 party conference calls. During a call, click the number ofa second person to include in the call.
Chapter 2
2-62
4. When the call is finished, you may click the Hang Up icon , or [Alt] + [h] (Firebox
browser only).
2.8.12 Sending an e-mail
To send an e-mail using the Web Directory Client:
1. Display the directory entry for the person you wish to send e-mail to.
2. From the Results tab, or the Details tab, click the person's Mail address.If a default mail client is defined on the computer, it is launched and a new message dialogbox appears with the destination e-mail address filled in.
2.8.13 Viewing your Personal Address Book
To use the Personal Address Book, you must log in (see § Logging in — Authentication ).Personal address entries are masked to any other directory user, even the administrator.
To view the entries in your Personal Address Book, click the Address Book bookmark, thenclick the Results tab, or perform a search.
Note:
Select the Address Book or Directory level of the directory tree before searching.
2.8.14 Creating a Personal Address Book Entry
To create an entry in your Personal Address Book:
1. Log in (see § Logging in — Authentication ).
2. Select the Address Book level in the directory tree, either in the Browse tab, or byclicking the Address Book bookmark.
3. Click the Add Entry icon .
The Edit tab appears.
4. Enter the information in the different fields.
Caution:You must enter a value in the Name field. This is the full name that will display in the grid onthe Results tab. If Name is not present, the entry name will not be displayed in the Resultstab, or in the “AddressBook” tree of the Alcatel-Lucent OmniVista 4760 Network ManagementSystem application.
5. Click the Save Entry icon , or [Alt] + [s] (Firefox browser only).
Note 1:
To modify an existing Personal Address Book entry, see § Modifying a Directory Entry .
Note 2:
You can customize the enterable fields for the Personal Address Book entries. See § Customizing the
Detail and Edit Parameters .
2-63
2.8.15 Deleting a Personal Address Book Entry
To delete an entry in your Personal Address Book:
1. Log in (see § Logging in — Authentication )
2. Find the Address Book entry you wish to delete using a search or by browsing.
3. From the Results tab, click the Nameof the entry.The Detail tab appears.
4. From the Detail tab, click the Delete Entry icon .
A confirmation dialog box appears.
5. To delete the entry, click Delete. Otherwise click Cancel.A confirmation of the deletion appears.
6. Click Close
2.8.16 Adding a Company Directory Entry
If you have appropriate rights granted by the administrator, you can add entries to theCompany directory. To add an entry:
1. Log in (see § Logging in — Authentication ).
2. Select the directory level in the Browse tab and click the Add Entry icon .
A new personal entry appears in the Edit tab.
3. Enter the information for the new person (see § Modifying a Directory Entry ).
4. To save the entry, click the Save Entry icon .
The entries for the directory level appear in the Results tab, including the new entry.
2.8.17 Deleting a Company Directory Entry
If you have appropriate rights granted by the administrator, you can delete entries from theCompany Directory. To delete an entry:
1. Log in (see § Logging in — Authentication ).
2. From the Results tab, click the Name of the entry you wish to delete.The information for the entry appears in the Detail tab.
3. Click the Delete Entry icon .
A dialog box appears asking for confirmation.
4. Click Delete to delete the entry, or Cancel to abandon the task.A dialog box appears with a confirmation message.
5. Click Close.
Chapter 2
2-64
2.8.18 Modifying a Directory Entry
You can modify your own directory entry and the entries in your Personal Address Book. Tomodify other entries, you need access rights granted by the administrator.
To modify a directory entry:
1. Log in (see § Logging in — Authentication ).
2. Find the directory entry you wish to modify using a search or by browsing.
3. In the Results tab, click the Name of the entry you wish to modify.The attributes for the entry display in the Detail tab.
4. Click the Edit tab.The attributes display in the Edit tab, where you can change the values in the fields.
5. To change the password:a. Click the Change Password icon , or [Alt] + [p] (Firefox browser only).
An Enter new password dialog box appears.b. Enter the new password in both fields. Click Valid to confirm, or Cancel to abandon
the task.A confirmation dialog box appears.
c. Click Close.
Note 1:To change a password other than your own, you must have rights assigned by the administrator.
6. You may wish to associate one or more assistants, managers, or other people with thisdirectory entry. To create a link to another directory entry:a. Select the Add Links icon next to the type of link you wish to add (Assistant,
Manager, or See Also).An Add Links dialog box appears.
b. Enter search criteria in the filter boxes to find the person(s) you wish to link to. Click theOK button next to the filter boxes.The results of your search are displayed.
c. Select entries by checking the boxes to the left of the names. You can use the SelectAll and Unselect All buttons at the bottom of the dialog box.
d. Once you have made your selection, click the Ok button at the bottom of the dialogbox.The names appear in the appropriate field on the Edit tab.
7. To delete a link (Assistant, Manager, or See Also) associated with this directory entry:a. Select the name you wish to delete the link for in the appropriate field (next to the Add
Links icon ).
The name is highlighted.b. Click the Delete a Value icon , or [Alt] + [-] (Firefox browser only).
The name disappears from the appropriate field.
8.
2-65
, or [Alt] + [s] (Firefox browser only).
A dialog box appears displaying either a confirmation of the update, or a messagedescribing a problem with updating (for example, insufficient rights).
9. Click OK.
Note 2:
You can use [Alt] + [r] to return to the Results tab from the Edit tab (Firefox browser only).
2.8.19 Modifying Attributes of a Company Directory Level
If you have sufficient rights granted by the administrator, you can update the attributes of theCompany and Department levels of the directory tree. To update attributes:
1. Log in (see § Logging in — Authentication ).
2. Select the directory level in the Browse tab and click the Level Attributes icon .
The level attributes appear in the Detail tab.
3. Click the Edit tab.The level attributes appear in the Edit tab and can be modified like other directory entries(see § Modifying a Directory Entry ).
4. To save the changes, click the Save Entry icon .
2.8.20 Customizing the Search Filters
You may customize the filters you use to build search criteria. Only the administrator cancustomize the default filters for all users.
To customize the filters for an advanced search on the Search tab:
1. Log in (see § Logging in — Authentication ).
2. From the Search tab, click the Customize icon .
A window appears showing the filter parameters to configure.
Note:The User Parameters tab is selected. If you are an administrator and you wish to customize the de-fault parameters for all users, select the Default Parameters tab.
3. Select the search class from the Search Classes drop down box.The filter attributes which currently appear for this class are listed in the right list box in theFilter Attributes area. Attributes not configured to appear are listed in the left list box.
4. To add a filter attribute, select it in the left box and click the Add icon .
The filter attribute moves from the left box to the right box and becomes available forbuilding search criteria.
5. To remove a filter attribute from the list of possible attributes, select it from the right boxand click the Remove icon .
Chapter 2
2-66
The filter attribute moves from the right box to the left box and becomes unavailable forbuilding search criteria.
6. To change the order of the filter attributes, select an attribute in the right box and use theUp and Down icons to move the attribute up or down in the list.
7. To add, remove, and order conditions available for building search criteria, use the Add,Remove, Up, and Down arrow icons in the Condition List area.
8. To reset the user parameters to the default, from the User Parameters tab, click Default.
9. To save the customized settings, click Save.A confirmation message appears at the bottom of the Filter Parameters box.
10. When you are done customizing parameters, click Close.
2.8.21 Customizing the Results Display and Print Parameters
You may customize the attributes that appear in the grid when you display and print directoryentries. Only the administrator can customize the default parameters for all users.
To customize the grid display on the Results tab:
1. Log in (see § Logging in — Authentication ).
2. From the Results tab, click the Customize icon .
A window appears showing the grid parameters to configure.
Note:The User Parameters tab is selected. If you are an administrator and you wish to customize the de-fault parameters for all users, select the Default Parameters tab.
3. Enter the number of entries you wish to display on each screen in Number of lines perpage.
4. Enter the total number of entries to display in Maximum number of lines.
5. To allow sorting the display by column, check the Grid Sort check box.
6. The attributes which currently display are listed in the right list box in the Grid Attributesarea. Attributes not configured to display are listed in the left list box.To add an attribute to display on the grid, select it in the left box and click the Add icon .
The attribute moves from the left box to the right box and will be displayed.
7. To remove an attribute from the grid display, select it from the right box in the GridAttributes area and click the Remove icon .
The attribute moves from the right box to the left box and is removed from the display.
8. To change the order of the grid attributes, select an attribute in the right box and use theUp and Down icons to move the item up or down in the list.
9. To add, remove, and order the attributes that print for each entry, use the Add, Remove,Up, and Down arrow icons in the Print Attributes area.
10. To reset the user parameters to the default, from the User Parameters tab, click Default.
11. To save the customized settings, click Save.A confirmation message appears at the bottom of the Grid Parameters box.
2-67
12. When you are done customizing parameters, click Close.
2.8.22 Customizing the Detail and Edit Parameters
You may customize the attributes that appear on the Detail and Edit tabs when you displaydetails and modify entries. Only the administrator can customize the default parameters for allusers.
To customize the parameters:
1. Log in (see § Logging in — Authentication ).
2. To customize parameters displayed on the Detail tab, click the Details tab.
3. To customize parameters on the Edit tab, click the Edit tab.
4. Click the Customize icon .
A window showing the three areas of the tab appears. A dialog box where you canconfigure the attributes you want to display also appears.
Note:The User Parameters tab is selected. If you are an administrator and you wish to customize the de-fault parameters for all users, select the Default Parameters tab.
5. Customize the parameters for each area separately. The attributes which currently displayin Area 1 are listed in the right list box in the Area 1 area of the parameters dialog box.Attributes not configured to display are listed in the left list box.To add an attribute to display, select it in the left box and click the Add icon .
The attribute moves from the left box to the right box and will be displayed.
6. To remove an attribute from the display, select it from the right box in the Area 1 area andclick the Remove icon .
The attribute moves from the right box to the left box and is removed from the display.
7. To change the order of the attributes within Area 1, select an attribute in the right box anduse the Up and Down icons to move the attribute up or down in the list.
8. To allow the photo parameter to display, check the Photo presence check box.
9. To add, remove, and order the attributes that display in Area 2 and Area 3, use the Add,Remove, Up, and Down arrow icons in the Area 2 and Area 3 areas.
10. To reset the user parameters to the default, from the User Parameters tab, click Default.
11. To save the customized settings, click Save.A confirmation message appears at the bottom of the Detail or Edit Parameters box.
12. When you are done customizing parameters, click Close.
2.8.23 Selecting a Theme
Up to four different themes are available for the Web Directory Client. A theme defines thecolors, fonts, heading styles, and background of the Web Directory Client window. The themesare listed in the lower left corner of the window. The current theme is shown by an arrow -->.To select a different theme, click on the name of the theme. The new theme styles are appliedimmediately. More or fewer display elements are customized, depending on the theme.
Chapter 2
2-68
2.8.24 Modifying a Theme
Theme 1 is always the default theme for an anonymous user. Only theme name and logo canbe changed.
Theme 2 and 3, only theme name and logo can be changed.
Theme 4 support more complex customisation. To recover the initial theme 4 , you can copyback the Themex content to Theme4 folder.
To modify a theme, you must be an administrator.
1. Log in (see § Logging in — Authentication ).
2. Select the theme you wish to modify.(Edit) will appear next to the theme name.
3. Click the theme name again.A copy of the Web Directory Client window appears on which the different displayelements are indicated by a number in parentheses. A Theme name dialog box where youcan configure the display elements also appears.
4. Enter the name for the theme.
5. Using the numbers in parentheses to guide you, enter values for the display elements youwish to modify:• For image elements, enter the name of an image file (png or gif format), or click the
Browse... icon to bring up a Choose File dialog box. A tooltip will indicate the size ofan image file.
• For color elements, enter the HTML color format or click the color square to the right ofthe field to bring up a Color Chooser dialog box.
• In Font Family enter a list of fonts in order of preference.• In Font Size enter the font size in pixels.
6. To save the changes, click the Save icon.A confirmation message displays at the bottom of theTheme name dialog box
7. Click Close.
Note:
These parameters are stored in CSS files in the directory: ...\4760\Client\Themes and can be modified
with an editor.
2.9 Web Directory Client - Configuration
2.9.1 Configuring Sets for an Automatic Call
This feature is not available to OmniPCX Office users.To make the automatic call feature available to a user, the user's set must be managed in theConfiguration application with the STAP (Simple Telephony Application Protocol) function inthe USERS object:
- Forbidden: automatic call is not authorized.
- Off-hook: automatic call is authorized when the receiver is picked up.
2-69
- Authorized: automatic call is authorized with or without picking up the receiver of ahandsfree set.
Note:
Calls cannot be made with analog and DECT (PWT) sets if the receiver is not picked up.
2.9.2 Fields for Automatic Dialing.
By default, the user of the Web Directory Client can make calls by clicking extension number,ISDN number, and Mobile. This list can be completed by the fields Miscellaneous 1 toMiscellaneous 5 via prefix management. See module Directory - Managing prefixes .
2.9.3 Global Parameters
The administrator can customize the default parameters which apply to all Web DirectoryClient users. Most of these parameters are customized in the Web Directory Client, including:
- Attributes displayed for entries in the results grid (see module Directory - Web DirectoryClient - Operation § Customizing the Results Display and Print Parameters ),
- Attributes printed in the results grid (see module Directory - Web Directory Client -Operation § Customizing the Results Display and Print Parameters ),
- Attributes available for building advanced search filters (see module Directory - WebDirectory Client - Operation § Customizing the Search Filters ),
- Attributes on detail display (see module Directory - Web Directory Client - Operation §Customizing the Detail and Edit Parameters
- Attributes for editing (see module Directory - Web Directory Client - Operation §Customizing the Detail and Edit Parameters ),
- Attributes for update and display of Personal Address Book entries (see module Directory -Web Directory Client - Operation § Customizing the Detail and Edit Parameters ),
- Theme display: Directory background, logo, toolbox bar, OK button, and font family andsize (see module Directory - Web Directory Client - Operation § Modifying a Theme
The administrator can customize the following Web Directory Client global parameters in theAlcatel-Lucent OmniVista 4760 Network Management System System Directory, as describedbelow (default values are in parentheses):
- If the Authentication icon is present on the tool bar (present)
- Maximum number of entries in Personal Address Book (500)
- If the Edit tab is present (present)
- If creation of entries is allowed (allowed subject to authentication)
- Font size (12)
- If the Browse tab is present (present)
- If the Associated station management icon is present on the tool bar (present)
- If the Theme menu is present (present)
- If the Search tab is present (present)
- If the Customize icon is present (present)
Chapter 2
2-70
To change the global parameters:
1. Launch the Directory application.
2. Click the System tab.
3. Select the path Nmc > NmcConfiguration > GlobalPreferences > DirectoryClient>GlobalParameters.
4. Modify the attributes in the GlobalParameters table.
5. To save the modifications, click the Apply the changes icon. .
2.10 Managing prefixes
2.10.1 Overview
The Alcatel-Lucent OmniVista 4760 Network Management System allows automatic calls fromthe Web Directory Client between a telephone set associated with the user and a telephonenumber in the LDAP directory.This phone number is presented in a unique manner to all Web Directory Client users andcannot be directly used from the set/extension keypad (if the caller and called party belong todifferent subnetworks or are located in two different countries).To allow this number to be dialed from the Web Directory Client, prefix rules must beconfigured.
Note 1:
The “+” and “()” characters are not used for dialing.
These rules allow:
- For a directory that is shared by users in different countries or areas: users to see thecomplete number (including prefix). Two users in the same country or area will see thecomplete number displayed but do not have to dial it to call each other.
- For users on different subnetworks: users to dial the inter-network call prefix.
The rules are dynamically applied when the call is made. The directory always shows numbersin the form they were entered.
Note 2:
ISDN number as synchronized by the PCX is not complete (for example, in France it is presented on nine
digits – 155667000), to allow it to be dialed it must be completed by adding the carrier prefix 0 in the
“ISDN prefix” field when the PCX is declared. The number then becomes 0155667000 and the prefix
rules can be applied.
Note 3:
The 4059 attendant application does not use STAP call and no prefix rule. The 4059 attendant dials the
number transmitted by Alcatel-Lucent OmniVista 4760 Network Management System. The transmitted
number should not to be written using pseudo cannonical format (eg: +33 (1) 55667000). Used numbers
must have the following format: 0 0155667000 or 0 00 33155667000, depending on the numbering dis-
criminator set in the PCX.
If cannonical format is used, TAPI setting must be modified on 4059 PC and respect exactly cannonical
2-71
format to allow windows to apply properly conversion rule.
2.10.2 Management Rules
2.10.2.1 Operation
The Web Directory Client application responds to directory searches by presenting a Webpage showing administrative data.Only a few attributes of the Web page allow automatic calls.It is necessary to:
- Write a call rule for the attribute.
- Display the attributes on the Web page.
- Grant read rights for this attribute.
A list of attributes is presented below:
- telephoneNumber: internal number defined as a string of digits only, updated atsynchronization with the PCX (For example: 3010). The internal call rule is used.
- IsdnNumber that, if it is a set linked to a directory record, is automatically constructed fromthe internal phone number, DID translation or entity data and the ISDN prefix configuredfor the network, subnetwork or the PCX.If the set is linked with a directory record, this number cannot be modified manually.If the set is not linked to a directory record, this number can be updated manually, forexample: (+33) 12 34 56 78. The external call rule is used.
- mobile, updated automatically. The external call rule is used.
- One of the attributes misc 1, misc 2, ..., misc 5, that can be used to store speed dialnumbers. By default, no rule is specified.
Two rules, LDAP NmcPrefixRule1 (rule for calls between networks), NmcPrefixRule2 (rulefor external calls) can be defined for each of these attributes so that, when the phone numberis clicked, the Web Directory Client calculates the correct number.The rules are applied on the PCX, subnetwork, or network to which the calling extensionbelongs.The transformation rules are applied after any characters that are not digits have been deleted.Deletion of characters and transformation are performed by the Web Directory Client beforethe call is made.
The NmcPrefixRule1 rule is mainly used to transform an internal number when a call is madebetween subnetworks.The NetworkDestination and SubnetworkDestination attributes specify for whichdestinations the instance of the rule is applicable.The prefixToAdd attribute specifies the prefix to be added to reach the above destinations.
The NmcPrefixRule2 rule is mainly used to transform a number when making an external call.The PrefixToDelete attribute specifies which numbers must be deleted (international orregional prefix), while the PrefixtoAdd attribute specifies the prefix to be added.
Note:
These rules are applicable to all numbers recorded in the directory. This means that all numbers must be
entered in the same format with no optional numbers (for example, a carrier prefix).
Chapter 2
2-72
2.10.2.2 Default Configuration
By default, the telephoneNumber attribute is linked with the rule for Rule for call betweennetworks and the international ISDN Number and mobile attributes are linked to the Rulefor external call.
Figure 2.23: Prefix Management Rule Tree
2.10.2.3 Configuring Settings
To configure prefix management rule parameters:
- Place the cursor in the directory System tree.
- Select the network, subnetwork, or PCX concerned by the rule.
- Select Create from the shortcut menu.
- Select Rule for calls between networks (rule 1) or Rule for external calls (rule 2).
- Enter the attribute values in the box to the right (refer to § Detailed Examples ).The attribute becomes "dialable".
2.10.3 Detailed Examples
2.10.3.1 Call between Subnetworks
Assuming there are two networks. Network N1 consists of three subnetworks (SN1.1, SN1.2,SN1.3), network N2 consists of two subnetworks (SN2.1, SN2.2).
2-73
Figure 2.24: Call between Subnetworks
The Extension number attribute is linked to the Inter-network calls rule, which correspondsto the default configuration.The following table presents the prefixes to use to set up calls between the subnetworks.
table 2.40: Prefixes to Use in Calls between SubnetworksCalled party Subnetwork
1.1Subnetwork
1.2Subnetwork
1.3Subnetwork
2.1Subnetwork
2.2Calling party
Subnetwork1.1
NotApplicable
No prefixPrefix 6* Prefix 4 Prefix 4
Subnetwork1.2
No prefix NotApplicable Prefix 6 Prefix 4 Prefix 4
Subnetwork1.3
Prefix 6 No prefixNot Applicable
Prefix 4 Prefix 4
Subnetwork2.1
Prefix 4 Prefix 4 Prefix 4Not
ApplicableNo prefix
Subnetwork2.2
Prefix 4 Prefix 4 Prefix 4No prefix Not Applicable
Instances of the Inter-network calls rule must then be defined as follows. When nodestination is mentioned, no rule is applied.
(*) : subnetwork SN1.1 calls subnetwork SN1.3
Chapter 2
2-74
Figure 2.25: Inter-network Call Rule Tree
2.10.3.2 External Call
A common Alcatel-Lucent OmniVista 4760 Network Management System directory managestwo networks (network N1 in France and network N2 in the USA).
Figure 2.26: External Call
The ISDN number attribute is linked to the External calls rule (default configuration).Numbers of this type must match according to calling party location.
table 2.41: External call — Examples
Caller Called Party (NumberPresented) Number Dialed
Network 1(FR) 33 1 55 66 7000 (1) 00 1 55 66 7000
Network 1(FR) 1 819 555 111 (2) 000 1 819 555 111
Node 2.1.1 (USA) 33 1 55 66 7000 (3) 9 011 33 1 55 66 7000
Node 2.1.1 (USA) 1 819 444 222 (4) 9 1 819 444 111
Node 2.1.1 (USA) 1 617 555 111 (5) 9 555 111
Applying the rule:
2-75
- (1) for a call in France, remove the 33 and add 00.
- (2) for a call from France to the USA, add 000.
- (3) for a call from the USA to France, add 9 011
- (4) for a long-distance call within the USA, remove the 1 and add 91.
- (5) for a local call in the USA, remove the 1 617 and add 9.
In network 1, the prefix for external calls (trunk seize or ARS) is 0. It is 9 on network 2. Theinternational ISDN numbers are saved as they must be dialed when calling from anothercountry, i.e. with the country code (33 1 55 66 7000).
The instances of the external calls rule must then be defined as follows:
Figure 2.27: External Call Rule Tree
This configuration allows the following different cases to be met:The item at the start of each line refers to the rule defined in the above tree.
- Saved number: 33 1 12 34 56 78Item 1. Number to be dialed from an extension on network 1 (FR): 0 01 12 34 56 78Item 3. Number to be dialed from an extension on network 2 (USA): 90 11 33 1 12 34 56
Chapter 2
2-76
78
- Saved number: 49 1234 56 789Item 2. Number to be dialed from an extension on network 1 (FR): 0 00 49 1234 56 789Item 3. Number to be dialed from an extension on network 2 (USA): 90 11 49 1234 56 789
- Saved number: 1 617 123 4567Item 2. Number to be dialed from an extension on network 1 (FR): 0 00 1 617 123 4567Item 5. Number to be dialed from an extension on subnetwork 2.1 (USA): 9 123 4567
- Saved number: 1 619 123 4567Item 2. Number to be dialed from an extension on network 1 (FR): 0 00 1 619 123 4567Item 4. Number to be dialed from an extension on subnetwork 2.1 (USA): 9 619 123 4567
2.11 Appendix A: Using LDIF files
2.11.1 Overview
LDIF: (LDAP Data Interchange Format)
LDAP: (Lightweight Directory Access Protocol)
The Alcatel-Lucent OmniVista 4760 Network Management System directory can export orimport entry definitions by means of LDIF files.A single LDIF file import operation allows a large number of directory entries to be addedand/or modified. Importing LDIF files does not delete any entry.For export and import procedures, see the module Directory - Company tab §Importing/Exporting Entries .
Remark:
Because the LDIF format is a text file format, you can edit LDIF files with any software compatible with
this format (Word, WordPad, etc.). Take care: accented characters are coded and lines, larger than 80
characters, are split.
2.11.2 Entries, Description
The Alcatel-Lucent OmniVista 4760 Network Management System directory consists of seventypes of entries:
- Company (Organization) type entries.
- Country type entries.
- Locality (City) type entries.
- Department (Organizational Unit) type entries.
- Room (Office) type entries.
- Group (GroupofUniqueNames) type entries.
- Person (Organizational Person) type entries.
Each entry is assigned a distinguished name (or directory name of the entry). This name isunique and defines the position of the entry in the directory tree structure and the unique ID ofthe record (UID).
2-77
See module Directory - Appendix B: Detailed structure of the LDAP directory .
Example:
For a Person entry, located in the tree as follows:
Figure 2.28: Company Directory Tree
the distinguished name must be:
For a description of object classes and entry attributes, see module Directory - Appendix B:Detailed structure of the LDAP directory .
2.11.2.1 Company (Organization) Type Entries
These entries define a company within the organization. Each Company entry is characterizedby:
- its distinguished name, object classes, and mandatory attributes:
- optional attributes:
Caution:
The Company entry type located at the top of the Company directory tree structure is configured
during installation of Alcatel-Lucent OmniVista 4760 Network Management System and must not
be modified.
2.11.2.2 Country Type Entries
These entries define a country within the organization. Each Country entry is characterizedby:
- its distinguished name, object classes, and mandatory attributes:
Chapter 2
2-78
- optional attributes:
2.11.2.3 Locality (City) Type Entries
These entries define a city within the organization. Each City entry is characterized by:
- its distinguished name, object classes, and mandatory attributes:
- optional attributes:
2.11.2.4 Department (Organizational Unit) Type Entries
These entries define a department within the organization. Each Department entry ischaracterized by:
- its distinguished name, object classes, and mandatory attributes:
- optional attributes:
2.11.2.5 Room Type Entries
These entries define a room within the organization. Each Room entry is characterized by:
- its distinguished name, object classes, and mandatory attributes:
- optional attributes:
2.11.2.6 Group (GroupofUniqueNames) Type Entries.
These entries define a group within the organization. Each Group entry is characterized by:
2-79
- its distinguished name, object classes, and mandatory attributes:
- optional attributes:
2.11.2.7 Person (Organizational Person) Type Entries
These entries define a person within the organization. Each Organizational Person entry ischaracterized by:
- its distinguished name, object classes, and mandatory attributes:
- optional attributes:
2.11.3 LDIF File Structure
LDIF file structure complies with the following rules:
- Entries must be separated by blank lines.
- When the entries define a tree structure (for example: Company > Countries >Department > Person), the order of entries in the LDIF file must be identical.
- for importing, the LDIF file can specify the operation to perform, add/modify/remove. WithAlcatel-Lucent OmniVista 4760 Network Management System, you must select one of thefollowing three options at the time of import:• Add and modify: to import new and modified entries.• Add only: to import new entries only.• Modify only: to import modified entries only.
Chapter 2
2-80
Figure 2.29: Company Directory Tree
Figure 2.30: Sample LDIF File Structure
2.12 Appendix B: Detailed structure of the LDAP directory
2.12.1 Overview
LDAP: (Lightweight Directory Access Protocol) This acronym designates a protocol used toaccess directory servers that manage data in a hierarchical manner.
The LDAP model is based on entries. An entry is a collection of attributes. Attributes are
2-81
grouped by class. Each entry can be defined by several classes and therefore by the union ofattributes of these classes. Entries are placed in a hierarchical structure which reflects theorganization of a company. In this appendix, classes and their attributes used in theAlcatel-Lucent OmniVista 4760 Network Management System company directory aredescribed.
2.12.2 List of Classes
table 2.42: LDAP Directory ClassesClasses Description
Country Definition of a country, structuring class
City Definition of a city (in the broad sense),structuring class
Organization (*) Definition of a company, mainly structuringclass
OrganizationalUnit (*) Definition of a department, mainly structuringclass
InetOrgPerson (*) Definition of a person
GroupOfUniqueNames (*) Definition of a group
Room (*) Definition of a room
A4400User Ancillary class to complete the previousstandard classes with attributes specific toAlcatel-Lucent OmniVista 4760 NetworkManagement System or missing attributes.
(*) Class that can be linked to System directory SETS (see List of SET classes andcorresponding 4400 objects). This class is thus managed by the LDAP 4760 server "IntegrityPlugin"; it allows links between entries of this type and System directory 4400 SETS to becreated automatically.
2.12.3 List of SET Classes and Corresponding 4400 Objects
List of System directory classes that represent 4400 objects and that can be linked to companydirectory entries. Example: A "User" can be linked to a "Person".
table 2.43: LDAP Directory Classes in System Tree4760 Classes Translation Corresponding 4400
Objects
User Users User
UserAlias User alias User_Alias
AbbreviatedNumber Abbreviated (speed dial)number
Direct_Abbreviated_Number
AbbreviatedNumberAlias Abbreviated (speed dial)number alias
Direct_Abb_Number_Alias
RemoteSubscriber Remote user Phone_Book(Phone_Book_Type=Remote)
Chapter 2
2-82
4760 Classes Translation Corresponding 4400Objects
ServiceNumber Service number Phone_Book(Phone_Book_Type=PB_Service_Number)
2.12.4 Types of Attributes
table 2.44: Types of LDAP Directory AttributesCIS Character strings that are not case sensitive
CES Case sensitive character strings
INT Integer
Tel Phone number
DN Link to another entry
Bin Binary
2.12.5 Country Class (Country)
A COUNTRY entry is only used to structure the organization of a company (it is a node of thecompany tree).
table 2.45: LDAP Directory Country Class AttributesAttributes Type Translation Description
C CIS Country 2-character code ofISO 3166 countries(4760 clients translatethese country codes)
Description CIS Description Free field
CI (*) CIS Confidentiality CL_G (green), CL_O(orange), CL_R (red),CL_A (admin)
Misc1 (*) CIS Miscellaneous 1 Free field
Misc 2 to Misc 50 (*)separately
CIS Miscellaneous 2 toMiscellaneous 50
Free field
(*) Attribute from the A4400User ancillary class
2.12.6 City Class (City)
A CITY entry is only used to structure the organization of a company (it is a node of thecompany tree).
table 2.46: LDAP Directory City Class AttributesAttribute Type Translation Description
L CIS City Name of the city
2-83
Attribute Type Translation Description
Description CIS Description Free field
St Description County/State State in English
CI (*) CIS Confidentiality CL_G (green), CL_O(orange) or CL_R(red), CL_A (admin)
Misc1 (*) CIS Miscellaneous 1 Free field
Misc 2 to Misc 50 (*)separately
CIS Miscellaneous 2 toMiscellaneous 50
Free field
(*) Attribute from the A4400User ancillary class
2.12.7 Organization Class (Company)
A COMPANY entry is used to structure the company tree and to define the company itself.
table 2.47: LDAP Directory Organization (Company) Class AttributesAttributes Type Translation Description
O CIS Company Name of the company
Telephonenumber Tel Phone No. 4400 internal number
InternationalISDNNumberTel ISDN number ISDN number
FacsimileTelephoneNumberTel Fax Fax number
Mail (*) CIS E-mail address E-mail address
Description CIS Description Free field
Secretary (assistant)(*)
DN Secretary (assistant) Link to the record of aperson
Manager (*) DN Manager Link to the record of aperson
Seealso DN See also Link to any record
CI (*) CIS Confidentiality CL_G (green), CL_O(orange) or CL_R(red), CL_A (admin)
Ou (*) CIS Department Name of department
EntityName (*) CIS Entity name 4400 entity name
CostCenterName (*) CIS Cost center name Name of 4400 costcenter
BuildingName (*) CIS Building Name of the officebuilding
Floor (*) CIS Floor Floor of the office
RoomNumber (*) CIS Office/Room No. Office/Room No.
PostalAddress CIS Address Address of thecompany (multilines)
Chapter 2
2-84
Attributes Type Translation Description
PostalCode CIS Zip code Zip code of theCompany
L CIS City Name of the city
St Description County/State State in English
C (*) CIS Country 2-character code ofISO 3166 countries(4760 clients translatethese country codes)
Misc1 (*) CIS Miscellaneous 1 Free field
Misc 2 to Misc 50 (*)separately
CIS Miscellaneous 2 toMiscellaneous 50
Free field
A4400FaxSet (*) DN Fax set Link to a SET entry inthe System directory
A4400MiscSet (*) DN Miscellaneous sets Link to a SET entry inthe System directory
A4400PrimarySet (*) DN Main set Link to a SET entry inthe System directory
A4400SecondarySet(*)
DN Secondary set Link to a SET entry inthe System directory
(*) Attribute from the A4400User ancillary class
2.12.8 OrganizationalUnit (Department) Class
A DEPARTMENT entry is used to structure the company tree and to define a department ofthe company.
table 2.48: LDAP Directory OrganizationalUnit (Department) Class AttributesAttributes Type Translation Description
Ou (*) CIS Department Name of department
O CIS Company Name of the company
Telephonenumber Tel Phone No. 4400 internal number
InternationalISDNNumberTel ISDN number ISDN number
FacsimileTelephoneNumberTel Fax Fax number
Mail (*) CIS E-mail address E-mail address
Description CIS Description Free field
Secretary (assistant)(*)
DN Secretary (assistant) Link to the record of aperson
Manager (*) DN Manager Link to the record of aperson
Seealso DN See also Link to any record
2-85
Attributes Type Translation Description
CI (*) CIS Confidentiality CL_G (green), CL_O(orange) or CL_R(red), CL_A (admin)
EntityName (*) CIS Entity name 4400 entity name
CostCenterName (*) CIS Cost center name Name of 4400 costcenter
BuildingName (*) CIS Building Name of the officebuilding
Floor (*) CIS Floor Floor of the office
RoomNumber (*) CIS Office/Room No. Office/Room No.
PostalAddress CIS Address Address of thecompany (multilines)
PostalCode CIS Zip code Zip code of theCompany
L CIS City Name of the city
St Description County/State State in English
C (*) CIS Country 2-character code ofISO 3166 countries(4760 clients translatethese country codes)
Misc1 (*) CIS Miscellaneous 1 Free field
Misc 2 to Misc 50 (*)separately
CIS Miscellaneous 2 toMiscellaneous 50
Free field
A4400FaxSet (*) DN Fax set Link to a SET entry inthe System directory
A4400MiscSet (*) DN Miscellaneous sets Link to a SET entry inthe System directory
A4400PrimarySet (*) DN Main set Link to a SET entry inthe System directory
A4400SecondarySet(*)
DN Secondary set Link to a SET entry inthe System directory
(*) Attribute from the A4400User ancillary class
SET (see § List of SET Classes and Corresponding 4400 Objects )
2.12.9 InetOrgPerson Class (Person)
A PERSON entry is a leaf of the company tree and is used to define a person of the companyand/or an Alcatel-Lucent OmniVista 4760 Network Management System user.
table 2.49: LDAP Directory InetOrgPerson (Person) Class AttributesAttributes Type Translation Description
Sn CIS Name Last name
Chapter 2
2-86
Attributes Type Translation Description
Givenname CIS First name
Cn CIS Full Name Is initialized with"Name + First name"during creation of aperson with the 4760but remainsindependent of thelast name and firstname
UID CIS User ID LDAP Logon = 4760user name
Userpassword Bin Password LDAP password =4760 user password
JpegPhoto Bin Photo JPEG format photo
O CIS Company Name of the company
Ou (*) CIS Department Name of department
Telephonenumber Tel Phone No. 4400 internal number
InternationalISDNNumberTel ISDN number ISDN number
FacsimileTelephoneNumberTel Fax Fax number
Mobile Tel Mobile Mobile number
Pager Tel Pager Pager number
Mail (*) CIS E-mail address E-mail address
EmployeeNumber CIS Employee number Employee number
Title CIS Function Function of theemployee
Description CIS Description Free field
Absence (*) CIS Absence Free description ofemployee absence
CI (*) CIS Confidentiality CL_G (green), CL_O(orange), CL_R (red),CL_A (admin)
LabeledURI CES Internet Address Internet addressfollowed by a labelseparated by a space
EntityName (*) CIS Entity name 4400 entity name
CostCenterName (*) CIS Cost center name Name of 4400 costcenter
BuildingName (*) CIS Building Name of the officebuilding
Floor (*) CIS Floor Floor of the office
RoomNumber (*) CIS Office/Room No. Office/Room No.
2-87
Attributes Type Translation Description
PostalAddress CIS Address Address of thecompany (multilines)
PostalCode CIS Zip code Zip code of theCompany
L CIS City Name of the city
St Description County/State State in English
C (*) CIS Country 2-character code ofISO 3166 countries(4760 clients translatethese country codes)
Secretary (assistant)(*)
DN Secretary (assistant) Link to the record of aperson
Manager (*) DN Manager Link to the record of aperson
Seealso DN See also Link to any record
HomePhone Tel Home phone number Home phone number
HomePostalAddress CIS Home address Home address(multilines)
CarLicense CIS Car license Car license
Misc1 (*) CIS Miscellaneous 1 Free field
Misc 2 to Misc 50 (*)separately
CIS Miscellaneous 2 toMiscellaneous 50
Free field
A4400FaxSet (*) DN Fax set Link to a SET entry inthe System directory
A4400MiscSet (*) DN Miscellaneous sets Link to a SET entry inthe System directory
A4400PrimarySet (*) DN Main set Link to a SET entry inthe System directory
A4400SecondarySet(*)
DN Secondary set Link to a SET entry inthe System directory
(*) Attribute from the A4400User ancillary class
SET (see § List of SET Classes and Corresponding 4400 Objects )
2.12.10 GroupOfUniqueNames Class (Group)
A GROUP entry is a leaf of the company tree and is used to define a group. A group containsa list of links to any directory entries.
table 2.50: LDAP Directory GroupOfUniqueNames (Group) Class AttributesAttributes Type Translation Description
Cn CIS Full Name Name of the group
Uniquemember DN Members Links to any entries
Chapter 2
2-88
Attributes Type Translation Description
O CIS Company Name of the company
Ou (*) CIS Department Name of department
Description CIS Description Free field
CI (*) CIS Confidentiality CL_G (green), CL_O(orange) or CL_R(red), CL_A (admin)
EntityName (*) CIS Entity name 4400 entity name
CostCenterName (*) CIS Cost center name Name of 4400 costcenter
BuildingName (*) CIS Building Name of the officebuilding
Floor (*) CIS Floor Floor of the office
RoomNumber (*) CIS Office/Room No. Office/Room No.
PostalAddress CIS Address Address of thecompany (multilines)
PostalCode CIS Zip code Zip code of theCompany
L CIS City Name of the city
St Description County/State State in English
C (*) CIS Country 2-character code ofISO 3166 countries(4760 clients translatethese country codes)
Secretary (assistant)(*)
DN Secretary (assistant) Link to the record of aperson
Manager (*) DN Manager Link to the record of aperson
Seealso DN See also Link to any record
Misc1 (*) CIS Miscellaneous 1 Free field
Misc 2 to Misc 50 (*)separately
CIS Miscellaneous 2 toMiscellaneous 50
Free field
A4400FaxSet (*) DN Fax set Link to a SET entry inthe System directory
A4400MiscSet (*) DN Miscellaneous sets Link to a SET entry inthe System directory
A4400PrimarySet (*) DN Main set Link to a SET entry inthe System directory
A4400SecondarySet(*)
DN Secondary set Link to a SET entry inthe System directory
(*) Attribute from the A4400User ancillary class
SET (see § List of SET Classes and Corresponding 4400 Objects )
2-89
2.12.11 Room Class (Room)
A ROOM entry is a leaf of the company tree and is used to define a Room.
table 2.51: LDAP Directory Room Class AttributesAttributes Type Translation Description
Cn CIS Full Name Name of the Room
RoomNumber CIS Office/Room No. Number of the Room
Telephonenumber Tel Phone No. 4400 internal number
InternationalISDNNumberTel ISDN number ISDN number
FacsimileTelephoneNumberTel Fax Fax number
Description CIS Description Free field
CI (*) CIS Confidentiality CL_G (green), CL_O(orange), CL_R (red),CL_A (admin)
O CIS Company Name of the company
Ou (*) CIS Department Name of department
EntityName (*) CIS Entity name 4400 entity name
CostCenterName (*) CIS Cost center name Name of 4400 costcenter
BuildingName (*) CIS Building Name of the officebuilding
Floor (*) CIS Floor Floor of the office
PostalAddress CIS Address Address of thecompany (multilines)
PostalCode CIS Zip code Zip code of theCompany
L CIS City Name of the city
St Description County/State State in English
C (*) CIS Country 2-character code ofISO 3166 countries(4760 clients translatethese country codes)
Secretary (assistant) (*) DN Secretary (assistant) Link to the record of aperson
Manager (*) DN Manager Link to the record of aperson
Seealso DN See also Link to any record
Misc1 (*) CIS Miscellaneous 1 Free field
Misc 2 to Misc 50 (*)separately
CIS Miscellaneous 2 toMiscellaneous 50
Free field
Chapter 2
2-90
Attributes Type Translation Description
A4400FaxSet (*) DN Fax set Link to a SET entry inthe System directory
A4400MiscSet (*) DN Miscellaneous sets Link to a SET entry inthe System directory
A4400PrimarySet (*) DN Main set Link to a SET entry inthe System directory
A4400SecondarySet (*) DN Secondary set Link to a SET entry inthe System directory
(*) Attribute from the A4400User ancillary class
SET (see § List of SET Classes and Corresponding 4400 Objects )
2.12.12 A4400User Class
Ancillary class to complete the previous standard classes with attributes specific toAlcatel-Lucent OmniVista 4760 Network Management System or missing attributes.
table 2.52: LDAP Directory A4400User Class AttributesAttributes Type Translation Description
A4400FaxSet (**) DN Fax set Link to a SET entry inthe System directory
A4400MiscSet (**) DN Miscellaneous sets Link to a SET entry inthe System directory
A4400PrimarySet (**) DN Main set Link to a SET entry inthe System directory
A4400SecondarySet(**)
DN Secondary set Link to a SET entry inthe System directory
Absence (**) CIS Absence Free description ofemployee absence
BuildingName CIS Building Name of the officebuilding
C CIS Country 2-character code ofISO 3166 countries(4760 clients translatethese country codes)
CI (**) CIS Confidentiality CL_G (green), CL_O(orange), CL_R (red),CL_A (admin)
Cn CIS Full Name Name of the Room
CostCenterName (**) CIS Cost center name Name of 4400 costcenter
EntityName (**) CIS Entity name 4400 entity name
FacsimileTelephoneNumberTel Fax Fax number
Floor (**) CIS Floor Floor of the office
2-91
Attributes Type Translation Description
Givenname CIS First name
InternationalISDNNumberTel ISDN number ISDN number
L CIS City Name of the city
Mail CIS E-mail address E-mail address
Manager DN Manager Link to the record of aperson
Misc1 (**) CIS Miscellaneous 1 Free field
Misc 2 to Misc 50 (*)separately
CIS Miscellaneous 2 toMiscellaneous 50
Free field
O CIS Company Name of the company
Ou CIS Department Name of department
PostalAddress CIS Address Address of thecompany (multilines)
PostalCode CIS Zip code Zip code of theCompany
RoomNumber CIS Office/Room No. Number of the Room
Secretary (assistant) DN Secretary (assistant) Link to the record of aperson
Sn CIS Name Last name
St Description County/State State in English
Telephonenumber Tel Phone No. 4400 internal number
(**) Non standard attribute, specific to Alcatel-Lucent OmniVista 4760 Network ManagementSystem.
SET (see § List of SET Classes and Corresponding 4400 Objects )
2.13 Appendix C: LDIF Management Tools
2.13.1 Overview
The LDIF management tools allow you to synchoronize the Alcatel-Lucent OmniVista 4760Network Management System Company Directory by importing and exporting LDIF files to andfrom other commercially available directories, and to migrate from the 4755 directory to theAlcatel-Lucent OmniVista 4760 Network Management System Company Directory.
ConvertLdif is an LDIF file mapping tool. It allows you to:
- Add parent entries if they are not already in the LDIF file.
- Modify attribute values.
- Substitute attribute and LDAP class names.
- Modify the entry tree structure.
- Add attributes with set (fixed) or calculated values.
Chapter 2
2-92
ExportLdap is used to export data from an LDAP directory to a LDIF file. This tool is moresophisticated than the Netscape LDAP export tool (LdapSearch) as it can be used to specifyattributes to be omitted in LDAP search results.
ImportLdap is used to import LDIF data into an LDAP directory. This tool is moresophisticated than the Netscape LDAP import tool (LdapModify) as it can be used to add ormodify entries; If an entry already exists in LDAP, ImportLdap modifies it. If the entry does notexist, ImportLdap adds it.
LinkDn is used to build links (DN type attributes) from any attribute value. For example, anassistant (secretary) link may be calculated from assistant name or telephone number.
PurgeLdap is used to delete entries from a LDAP directory using a LDAP filter. For example, itcan be used to delete entries that were not in the last LDIF import for synchronization withanother directory and therefore ensure consistency between the two directories (see theexamples to understand how this consistency between two directories can be ensured).
Ldif2Csv and (Csv2Ldif) are used to convert LDIF files to CSV and CSV files to LDIF. Thesetools maintain compatibility with Excel during the migration of the 4755 directory to the 4760directory. You can also use Microsoft Exchange to export and import directories in CSVformat.
ReplaceInLdif allows a character string to be replaced while staying in LDIF format. ThusLDIF files must not be edited with a mere text editor.
purifyldif, allows the fields described in the LDIF file to be deleted if they are not compatiblewith the 4760 server LDAP entry scheme. This way there can be no LDIF file import rejected.
encodeldif is used to encode LDIF files from ANSI format to UTF8-Base64 format. This allowsnon-ASCII characters to be imported (accented characters or unfamiliar characters).
All these tools take the form of DOS commands with arguments and options. They require a4760 environment, which means that they must be launched from the directory 4760\bin.
2.13.2 ConvertLdif
ConvertLdif is an LDIF file mapping tool. It enables attribute and LDAP class names to bereplaced, entry tree structure to be modified, attribute values to be modified and attributes withset or calculated values to be added. It is also used to add parent entries if they are notalready in the LDIF file.
table 2.53: ConvertLdif ParametersUse: ConvertLdif [options] file
file LDIF input file
Options:
–mc mcfile Mapping classes config file (unicode)
–ma mafile Mapping attributes config file (unicode)
–da dafile Default attributes config file (unicode)
–p pltfile Placement config file (unicode)
–e rejfile Save rejected entries in "rejfile"
–cp Create parents of each entry if DN contains attributeI, c, o or ou
2-93
–op op One of add, modify, or delete (LDAP changeoperation)
(Output to stdout, and errors to stderr).
Example:
ConvertLdif -ma myMaFile.conf -cp fileToConvert.Idif>convertedFile.Idif
Caution:
Config files must be in UNICODE.
2.13.2.1 Mapping Classes (-mc)
Syntax of the class mapping configuration file:
To replace a class name:OldClassName=>NewClassName
To delete a class:ClassName=>
To add a class:=>ClassName
2.13.2.2 Mapping Attributes (-ma)
-ma mafile mapping attributes config file (unicode)
Syntax of the attribute mapping configuration file:
To replace an attribute name for a specific class:ClassName.OldAttrName=>NewAttrName
To replace an attribute name for all classes:*.OldAttrName=>NewAttrName
To delete an attribute from a specific class:ClassName.OldAttrName=>
To delete an attribute from all classes:*.OldAttrName=>
Note:
Attribute mapping is also performed for DNs.
Caution:
Rules for "mapping attributes" are applied after rules for "mapping classes", which means that
mapping attributes operate on the output obtained from mapping classes.
2.13.2.3 Default Attributes (-da)
-da dafile default attributes config file (unicode)
Syntax of the default attributes configuration file:
To add an attribute/value for a specific class or for all classesClassName.AttrName==Expression*.AttrName==Expression
Chapter 2
2-94
To replace the value of an attributeClassName.AttrName=>Value*.AttrName=>Expression
To save a value in a fileFILE:pathname==Expression
To save a value in a file by overwriting itFILE:pathname=>Expression
To substitute the value of an attributeClassName.AttrName.Value=>Expression*.AttrName.Value=>Expression
table 2.54: Attribute SyntaxExpression:
% <attribute name>% : Value of <attribute name>
% <attribute name>[i]% : Character n (nth character) of %<attribute name>%
<string> : Character string
%rdn_i% : Value of th rdn (dn: ...nrdn_3,rdn_2,rdn_0)
%rdn_i[i]% : Character n of %rdn_i%
IMPORT_TIMESTAMP% : Date and time GMT (format: yyyymmddhhmmssZ)
7bit: keep only 7-bit characters
Examples:
1. *.description==my description (adds description attribute and its value to all entries)
2. person.mail=>%givenname%.%sn%@%ou%.%o%.fr (replaces the mail value in Person type entries)
3. person.uid=>7bit :%givenname%%sn% (replaces "uid" value in person type entries by the first namefollowed by the name but only taking characters on 7 bits)
4. person.ou=>%rdn_1% (replaces the "ou" value in Person type entries with "rdn1")
5. person.o=>%rdn_0% (replaces the "o" value in Person type entries with "rdn0")
6. *.Version=>IMPORT_FROM_DRH_%IMPORT_TIMESTAMP% (adds the Version attribute with IM-PORT_FROM_DRH_ + date/time GMT)
7. FILE:purgeFile.txt=>(&(Version=*)(!(Version>=%Version%))) (save the LDAP filter in a file, this filterallows entries with a Version less than the value calculated in 6 to be retrieved))
8. *.c.France=>FR (substitute FR for France in all c attributes)
Caution:
Rules for "Default attributes" are applied after rules for "mapping attributes", which means that
the "Default attributes" operate on the output obtained from "mapping attributes".
2.13.2.4 Placement (-p)
-p pltfile placement config file (unicode)
Syntax of the placement configuration file:
2-95
To place (move) entriesOldParentDn=>Expression
To delete certain DNsOldParentDn=>
To add to the end of all DNs==Expression
To replace all DNs=>Expression
Expression:
%<attribute name>%: Value of <attribute name>
%<attribute name>[i]%: character n (nth character) of the value of <attribute name>
<string>: character string
Examples:
1. =>uid=%uid%,ou=%ou%,o=alcatel(replaces each DN with a DN calculated from the "uid" and "ou" of each entry).
2. ou=nmd,o=alcatel,o=directoryroot=>ou=nmd,ou=eND,o=alcatel,o=directoryroot(places entries under nmd)
3. ou=nmd,ou=eND,o=alcatel,o=directoryroot=>ou=nmd,o=alcatel,o=directoryroot(places entries under nmd)
4. c=FR=>(deletes the c=FR suffix of all entries)
Caution:
Rules for "Placement" are applied after rules for "Default attributes", which means that "Place-
ment" operates on the output obtained from "Default attributes".
2.13.2.5 Create Parents (-cp)
To add parent entries to existing entries if the parent part of each of their DNs includes the L,C, O or OU attribute.For L: LOCALITY type entry createdFor C: COUNTRY type entry createdFor O: ORGANIZATION type entry createdFor OU: ORGANIZATIONALUNIT type entry created
Example:
The EXAMPLE.LDIF file contains:
Dn: uid=laurent dupont,ou=marketing,l=colombes,c=FR,o=alcatel,o=directoryrootGivenname: laurentSn: dupontCn: laurent dupontObjectclass: topObjectclass: person
Chapter 2
2-96
Objectclass: personObjectclass: organizationalPersonObjectclass: inetOrgPerson
After command "ConvertLdif –cp exemple.ldif > exemple2.ldif", exemple2.ldif contains:
Dn: o=directoryrooto=directoryrootObjectclass: topObjectclass: organization
Dn: o=alcatel,o=directoryrooto: alcatelObjectclass: topObjectclass: organization
Dn: c=FR,o=alcatel,o=directoryrootc: ENObjectclass: topObjectclass: country
Dn: I=colombes,c=FR,o=alcatel,o=directoryrootI: colombesObjectclass: topObjectclass: locality (city)
Dn: ou=marketing,l=colombes,c=FR,o=alcatel,o=directoryrootou: marketingObjectclass: topObjectclass: organizationalUnit
Dn: uid=laurent dupont,ou=marketing,l=colombes,c=FR,o=alcatel,o=directoryrootGivenname: laurentSn: dupontCn: laurent dupontObjectclass: topObjectclass: personObjectclass: organizationalPersonObjectclass: inetOrgPerson
2.13.2.6 Operations (-op)
-op op One of add, modify, or delete (LDAP change operation)
To add an LDAP operation (add, modify, or delete) to the LDIF file. This operation is added toall entries.
Advantages: This allows standard LDAP import tools to be used to add, modify, or deleteentries on a LDAP server.
Disadvantages: Only one operation may be selected per LDIF file
It is preferable to use the ImportLdap tool (allows LDAP additions and modifications to be
2-97
performed from the same LDIF file) and PurgeLdap (allows entries to be deleted from a LDAPfilter).
2.13.3 ExportLdap
table 2.55: ExportLdap ParametersUse: ExportLdap -b basedn [options] filter
ExportLdap -b basedn [options] -f file
baseDn base dn for search
filter RFC-1558 compliant LDAP search filter
file file containing an LDAP search filter
options:
-h host LDAP server name or IP address (default:localhost)
-p port LDAP server port number (default:389)
-D binddn bind dn
-w passwd bind password
-l attrs comma-separated list of attributes to retrieve(if -l omitted, all attributes are returned)
-o attrs comma-separated list of attributes to omit
-s scope one of base, one or sub (default:sub)
-n do not export binary values
Example:
ExportLdap –b o=alcatel –h myHost –l sn,cn,o,ou -s sub sn=de*
2.13.4 ImportLdap
ImportLdap is used to import LDIF data into an LDAP directory. This tool is moresophisticated than the Netscape LDAP import tool (LdapModify) as it may be used to add ormodify entries (if an entry already exists in LDAP it modifies it, otherwise it adds the entry).
table 2.56: ImportLdap ParametersUse: ImportLdap [options] file
file LDIF input file (Idif without change operations)
options:
-h host LDAP server name or IP address (default:localhost)
-p port LDAP server port number (default:389)
-D binddn bind dn
-w passwd bind password
-c continuous mode (do not stop on errors)
-e rejFile save rejected entries (ldif syntax errors) in "rejFile"
-a add only entries (default: add or modify)
-m modify only entries (default: add or modify)
Chapter 2
2-98
-d delete missing attributes (modify mode)
-r rejImpFile save rejected entries during IMPORT in LDIF file"rejImpFile"
The LDIF file must not contain any LDAP operations.
Without the –a and –m options, existing entries in LDAP are modified, the others are added.
For an entry to be modified, the –d option is used to delete attributes in the LDAP that are notpresent in the LDIF file.
Caution:
Do not use directory roots:
- o=directoryroot
- o=”company name”,o=directoryroot
otherwise the ACL security rules are deleted!
2.13.5 LinkDn
LinkDn is used to build links (DN type attributes) from any attribute value. For example, anassistant (secretary) link may be calculated from assistant name or telephone number.
table 2.57: LinkDn ParametersUse: LinkDn-b basedn [options] -f file
baseDn base dn for search
file config file containing from/to attributes (unicode)
options:
-h host LDAP server name or IP address (default:localhost)
-p port LDAP server port number (default:389)
-D binddn bind dn
-w passwd bind password
Syntax of the configuration file
To have AttrName equal to the DN of the FilterClass type entry whose FilterAttr attribute is #equal to FromAttrValue or
ClassName.AttrName=>FromAttr,FilterClass.FilterAttr;...(ClassName and FilterClass can be replaced by *)
Example:
If the misc1 attribute contains the assistant's (secretary's) name or phone number, misc2 contains the
manager's name or phone number, the content of the configuration file is:
*.secretary=>misc1 ,person.cn ;misc1 ,person.telephonenumber
*.manager=>misc2 ,person.cn ;misc2 ,person.telephonenumber
2.13.6 PurgeLdap
2-99
PurgeLdap is used to clean entries from an LDAP directory using an LDAP filter. For example,it can be used to delete entries that were not in the last LDIF import for synchronization withanother directory and ensure data consistency between the two directories (see the examples(3) to understand how consistency between two directories can be ensured).
table 2.58: PurgeLdap ParametersUse: PurgeLdap-b baseDn [options] filter
PurgeLdap-b baseDn [options] -f file
baseDn base dn for search
filter RFC-1558 compliant LDAP search filter
file file containing an LDAP search filter
options:
-h host LDAP server name or IP address (default:localhost)
-p port LDAP server port number (default:389)
-D binddn bind dn
-w passwd bind password
2.13.7 Ldif2Csv, Csv2Ldif
To convert LDIF files to CSV (Ldif2Csv) and CSV files to LDIF (Csv2Ldif)
table 2.59: Ldif2Csv ParametersUse: Ldif2Csv [options] <filename>
options:
-cs sep column separator (default: ,)
-ms sep multivalued attribute separator (default: ;)
-e rejfile save rejected entries in "rejfile"
-u unicode format
table 2.60: Csv2Ldif ParametersUse: Csv2Ldif [options] <filename>
options:
-cs sep column separator (default: ,)
-ms sep multivalued attribute separator (default: ;)
-e rejfile save rejected lines in "rejfile"
Example:
Ldif2Csv –cs; -ms, myFile.ldif > myFile.csv
Csv2Ldif cs; -ms, myFile.csv > myFile.ldif
Remark:
Csv2Ldif recognizes CSV files in unicode and Ldif2Csv allows a CSV file to be generated in unicode.
This allows LDIF file data to be modified with a unicode editor (Excel for example).
Note:
Chapter 2
2-100
The DN column must be completed in the CSV file, otherwise the LDIF file cannot be directly used (see
"Convertldif tool" for information on how to enter the DN).
In addition, the DN value includes “,” symbols and, if the comma is also used as column separator, the
DN must be placed in inverted commas.
2.13.8 ReplaceLdif
The ReplaceLdif.exe utility is used to replace an attribute value with another one in an ANSIformat LDIF file. In an LDIF file, too long a value can be written on several lines. ReplaceLdifconsiders this to make all replacements successful.
Command format:
- Use: ReplaceLdif <filename> "<what>" "<with>"
Example:
ReplaceLdif ansiLdifFile.ldif "old string" "new string" > output.ldif
2.13.9 PurifyLdif
The PurifyLdif.exe utility is used to make LDIF files from another system compatible with the4760 directory diagram. This is used to avoid import errors in the Alcatel-Lucent OmniVista4760 Network Management System directory caused by LDIF files not produced by the 4760.
Procedure:
1. Add the A4400User ancillary class to each entry.
2. Delete unknown classes and attributes from the diagram (the diagram comes from the -hhost or localHost)
3. If option -b: delete UID mail userpassword attributes if non-ASCII [x20,x7F]
4. If option -e: create a log file containing all faults that have occurred
Command format:
- use: purifyLdif [options] <input ldif file>
- options
1. -h host LDAP server name or IP address (default: localhost)
2. -p port LDAP server TCP port number (default: 389)
3. -e rejfile save rejected entries in "rejfile"
4. -b 7-bit check (UID, mail and userpassword)
Example:
purifyLdif -h myLdapServer -p 389 -e error.log foreignLdifFile.ldif > output.ldif
2.13.10 EncodeLdif
The EncodeLdif.exe utility is used to encode LDIF files from ANSI format to UTF8-Base64format. This allows non-ASCII characters to be imported (accented characters or unfamiliarcharacters).
Command format:
2-101
- use: EncodeLdif <input ldif file>
Example:
EncodeLdif ansiLdifFile.ldif > output.ldif
2.13.11 Examples
Several examples of how this set of tools can be used are presented below.
2.13.11.1 Example 1: Domino -> 4760
Example showing the mapping of an LDIF Domino file to render it compatible with a 4760.The initial LDIF file, (Domino.Ldif), is the result of exporting an Alcatel directory from LotusDominoThe following is an extract:dn: CN=Jean-Emile NEZES, OU=FR,O=ALCATELcn: Jean-Emile NEZESshortname: [email protected]: [email protected]: [email protected]: topobjectclass: personobjectclass: organizationalPersonobjectclass: inetOrgPersonobjectclass: dominoPersongivenname: Jean-Emilesn: NEZESmailaddress: [email protected]: +33 (0)1 23 45 67 89
To render this entry compatible with the 4760 directory:
1. Remove or replace the class dominoPerson.
2. Remove or replace the attributes "shortname" and "mailaddress".Replace them with the 4760 class, A4400User
3. Remove or replace the attributes shortname and mailaddress.
4. Replace the "OU" attribute by "C" in the DN and add "C" to the entry.
5. Create parent entries:
- Country, C=FR
- Company, O=ALCATEL
- Root, O=DIRECTORYROOT
The command and content of the configuration files required to perform these five operationsare:ConvertLdif -mc mc.conf -ma ma.conf -da da.conf -cp Domino.LDIF > 4760.LDIFWhere:mc.conf (mapping classes) contains:
Chapter 2
2-102
dominoPerson=>A4400userto replace dominoPerson with A4400userma.conf (mapping attributes) contains:*.shortname=>*.ou=>c*.mailaddress=>to delete shortname mailaddress and replace "ou" with "c" in the DNda.conf (default attributes) contains:*.c=>%rdn_1%InetOrgPerson.uid=>%givenname%%sn%To add "c" with the value from the DN and to recalculate "uid"-cp is used to create the entries O=ALCATEL,O=DIRECTORYROOT andC=FR,O=ALCATEL,O=DIRECTORYROOTOutput file 4760.LDIF will contain:
dn: o=DIRECTORYROOTobjectclass: topobjectclass: organizationo: DIRECTORYROOT
dn: o=ALCATEL,o=DIRECTORYROOTobjectclass: topobjectclass: organizationo: ALCATEL
dn: c=FR, o=ALCATEL,o=DIRECTORYROOTobjectclass: topobjectclass: countryc: EN
dn: CN=Jean-Emile NEZES,C=FR,O=ALCATEL,o=DIRECTORYROOTcn: Jean-Emile NEZESuid: JEmilemail: [email protected]: topobjectclass: personobjectclass: organizationalPersonobjectclass: inetOrgPersonobjectclass: A4400Usergivenname: Jean-Emilesn: NEZESc: ENtelephonenumber: +33 (0)5 94 22 33 66
2.13.11.2 Example 2: 4755 -> 4760
The 4755 directory must be exported in text format (with tabs as column separators), here thefile dir4755.txt is obtained.
2-103
The first line of the dir4755.txt file must be deleted: \\CLASS_Directory_common.Mapping will then depend on the attributes entered in the 4755 directory. This example startswith a 4755 directory with the following columns completed:
Last NameFirst nameDirectory\Directory NumberDepartmentCost CenterDirectory\SubnetDirectory\Alias NumberLast ModifiedSubnet TypeNode NameNode NumberData TypeAssociated Set NumberEquipment NumberAssistant (Secretary) Directory NumberTeleMarketing AgentLanguage IdentifierEntity NumberLast Checked
As the Service attribute is entered, we will map it in "OU" and use it in the DN to put entriesinto a hierarchy.
Here is the batch file containing the commands to be performed:
Csv2Ldif -cs " " -ms "$" dir4755.txt > dir1.ldif
ConvertLdif -mc mc.conf -ma ma.conf -da da.conf -p p.conf -cp dir1.ldif > dir2.ldif
ImportLdap –h 4760Host –D 4760UserDn –w passwd -e rejfile.log dir2.ldif
Del dir1.ldif
Del dir2.ldif
-cs " ": the column separator is a tab-ms "$": the multivalued separator is set to $ to avoid the default value ( ;) being interpreted.
mc.conf contains:=>top=>person=>organizationalPerson=>InetOrgPerson=>A4400userTo add classes top, person, organizationalPerson, InetOrgPerson, A4400user
ma.conf contains:*.Last Name=>sn
Chapter 2
2-104
*.First Name=>givenName*.Directory\Directory Number=>telephoneNumber*.Service=>ou*.Cost Center=>CostcenterName*.Directory\Subnet=>*.Directory\Alias Number=>*.Last Modified=>*.Subnet Type=>*.Node Name=>*.Node Number=>*.Data Type=>*.Associated Set Number=>*.Equipment Number=>*.Assistant (Secretary) Directory Number=>*.TeleMarketing Agent=>*.Language Identifier=>*.Entity Number=>*.Last Checked=>
da.conf contains:*.cn=>%sn% %givenname%*.uid=>7bit:%givenname% %sn%p.conf contains=>uid=%uid%,ou=%ou%,o=Alcatel, o=directoryRoot
-cp: to add the parent entries O=ALCATEL and OU=%OU%,O+ALCATEL
-e rejfile.log: You should always check if any entries were rejected during import. Themapping configuration can then be modified to avoid rejects.
2.13.11.3 Example 3: Novell <-> 4760
Example of two-way synchronization between a NOVELL directory and the 4760 directory. TheNovell directory is considered to be the master. Synchronize the 4760 with all Novell Personattributes, then import 4760 phone numbers (only) to Novell. We also want to take advantageof this synchronization to change the hierarchy of entries.
Here is an example DN in the Novell directory:
cn=ROUSSEAU Jean,ou=103,ou=1,o=BAT-A,l=Courbevoie,c=FR
where: ou=103 represents an office number.
ou=1 represents a floor number.
o=BAT-A represents the name of the building.
On the 4760 we wish to obtain:uid=JeanROUSSEAU, I=Courbevoie,c=FR,o=alcatel,o=directoryRoot with the additionalattributes:roomNumber = 103floor = 1
2-105
buildingName = BAT-AI = Courbevoiec = FRo = alcateluid = JeanRousseau
Here is the command and configuration file for Novell -> 4760 synchronization:
1. Batch file:ExportLdap -b "c=FR" -h NovellHost -D "UserDN" -w "Passwd" "objectclass=*" >novell1.ldifConvertLdif -mc mc.conf -ma ma.conf -da da.conf -p p.conf -cp novell1.Idif>novell2.IdifImportLdap -h 4760Host -D "UserDN" -w "Passwd" -c -r novell3.ldif novell2.ldifPurgeLdap -b "c=FR,o=alcatel" -h 4760Host -D "UserDN" -w "Passwd" -f purgeFilter.txtImportLdap -h 4760Host -D "UserDN" -w "Passwd" novell3.ldif
2. novell1.Idif:dn: cn=ROUSSEAU Jean,ou=103,ou=1,o=BAT-A,l=Courbevoie,c=FRobjectClass: inetOrgPersonobjectClass: organizationalPersonobjectClass: personobjectClass: topobjectClass: ndsLoginPropertiesACL: 2#subtree#cn=ROUSSEAU Jean,ou=103,ou=1,o=BAT-A,l=Courbevoie,c=FR#ACL: 6#entry#cn=ROUSSEAU Jean,ou=103,ou=1,o=BAT-A,l=Courbevoie,c=FR#ACL: 2#entry#[Public]#messageServerACL: 2#entry#[Root]#groupMembershipACL: 2#entry#[Root]#networkAddressaccessCardNumber: 2407mail: [email protected]: 2252initials: JRgivenName: JeanfullName: Jean ROUSSEAUsn: ROUSSEAUcn: ROUSSEAU Jean......
3. mc.conf (mapping classes):ndsLoginProperties=>ndsContainerLoginProperties=>=>a4400User
4. ma.conf (mapping attributes)*.ACL=>*.initials=>*.fullName=>*.accessCardNumber=>*.Language=>
5. da.conf (default attributes) :InetOrgPerson.c=>%rdn_0%InetOrgPerson.o=>alcatelInetOrgPerson.l=>%rdn_1%InetOrgPerson.buildingName=>%rdn_2%
Chapter 2
2-106
InetOrgPerson.floor=>%rdn_3%InetOrgPerson.roomNumber=>%rdn_4%InetOrgPerson.employeeNumber=>%uid%InetOrgPerson.uid=>7bit:%givenname%%sn%*.misc5=>FROM_NOVELL_%IMPORT_TIMESTAMP%FILE:purgeFilter.txt=>(&(misc5=FROM_ NOVELL _*)(!(misc5>=%misc5%)))The "misc5" attribute will be used to store an import date to allow the PurgeLdap tools todelete all entries that were not added or modified at the last import. To do this, PurgeLdapwill use the LDAP filter that was stored in the "purgeFilter.txt" file.
6. p.conf:=>uid=%uid%,l=%l%,c=%c%,o=%o%,o=directoryRoot
7. –cp: to create the new parents, l=xxx,c=FR,o=alcatel ,o=directoryRoot
8. ImportLdap Novell2.ldif creates or modifies entries, the entries rejected by the server arestored in Novell3.ldif.
9. PurgeLdap eliminates entries whose misc5 starts with FROM_NOVELL_ and with a valueless than that calculated by ConvertLdif.
Here is the command and configuration file for 4760 —> Novell synchronization:
1. Batch file:ExportLdap -b "c=FR,o=alcatel" -h 4760Host -D "UserDN" -w "passwd"–l "telephonenumber,cn,roomNumber,floor,buildingName,l,c""objectclass=person" > 4760_1.ldifConvertLdif -p p.conf 4760_1.ldif> 4760_2.ldifConvertLdif -ma ma.conf 4760_2.ldif > 4760_3.ldifImportLdap -h NovellHost -D "UserDN" - w "passwd -c 4760_3.ldif 2> import.log
2. 4760_1.ldif:Will contain 4760 "Person" type entries from the base c=FR,o=alcatel, o=directoryRootwith their attributes, telephonenumber, cn, roomNumber, floor, buildingName, l, c
3. p.conf:=>cn=%cn%,ou=%roomNumber%,ou=%floor%,o=%buildingName%,l=%l%,c=%c%The DN must first be recalculated before removing excess attributes. It is for this reasonthat two successive ConvertLdif operations are used, the first with the "–p" option and thesecond with "–ma".
4. ma.conf:*.roomNumber=>*.floor=>*.buildingName=>*.l=>*.c=>*.cn=>Here, all the attributes that were used to reconstitute the DN are removed so that only thephone number remains.
5. 4760_3.ldif:dn: cn=ROUSSEAU Jean,ou=103,ou=1,o=BAT-A,l=Courbevoie,c=FRtelephonenumber: 456454465ImportLdap will only modify the telephonenumber attribute.
2-107
Chapter 2
2-108
3.1 Overview
3.1.1 Overview
The Configuration application is part of the Alcatel-Lucent OmniVista 4760 CommunicationManagement System (called Alcatel-Lucent OmniVista 4760 Network Management System inthis document).
The tree window has 2 tabs:
- The Network tab, used to select PCXs for a remote configuration and also to modify theirnetwork attributes.
- The PCX tab, that displays the current configuration of connected Alcatel-Lucent OmniPCXEnterprise CSs or OmniPCX 4400s. You can access this tab if the Network tab iscompleted correctly and a PCX connection set up.
Note:
The OmniPCX Office is configured via the dedicated OMC interface.
Important:
Operating instructions for the Alcatel-Lucent OmniVista 4760 Network Management System con-
figuration application, along with a description of its special features, are given below. For stand-
ard PCX administration, please refer to the network equipment documentation.
For information regarding security, refer to module Security - Overview § Managing Access Pro-
files .
To use the OMC interface, please refer to the OMC documentation.
Alcatel-Lucent OmniPCX Enterprise CS or OmniPCX 4400
You can configure several Alcatel-Lucent OmniPCX Enterprise CSs or OmniPCX 4400ssimultaneously, provided that they have the same software release.PCXs are configured in connected mode, that is, online. You can modify data or performimport or export operations within the table.
PCX data must first be downloaded before it can be managed.
The configuration data of each PCX node is organized as a MIB:
- The node can be expanded as a component tree.
- These components represent object classes (for example: USERS).
- each object may be used to access the corresponding instances, (User Object: a useridentified by his directory number N° 9876, N° 9877..., Trunk group object, items N° 0, 1,2...) in order to manage them.
- Attribute is the name of items to be managed for each instance of the object (DirectoryNo., keyboards, programmable keys, timers, etc.).
OmniPCX Office
Alcatel-Lucent OmniVista 4760 Network Management System runs the OMC configuration
3
3-1
interface acting as a gateway to the OmniPCX Office. Starting with release 4.0 of theAlcatel-Lucent OmniVista 4760 Network Management System, you can connect to severalOmniPCX Offices at one time provided each OmniPCX Office is running release 5.0 orgreater.The following OmniPCX Office applications are accessible using OMC:
- Configuration,
- Automatic Call Distribution Configuration,
- Automatic Call Distribution Statistics,
- OTS Management.
Alcatel-Lucent OmniVista 4760 Network Management System also launches a Web browserfor OmniPCX Office Internet Access management.
3.2 Network tab
3.2.1 Preliminary steps
See module Directory - System tab for information about how to:
- Declare the network.
- Declare the subnetwork.
- Declare the PCXs.
- Running a synchronization via the System Directory.
3.2.2 Network tab, description
The Network tab shows the tree structure of one or more PCX networks.___change-begin___
___change-end___
Figure 3.1: Tree structure of PCX network
The tree contains different types of entries:
table 3.1: Entries of PCX network tree structure
Chapter 3
3-2
Symbol Entry type
Tree root
Network (for example: Alcatel)
Subnet (for example: Downtown)
OmniPCX 4400
Alcatel-Lucent OmniPCX EnterpriseCS
OmniPCX Office
Passive Communication Server(PCS)
Eye Box
3.2.3 Connecting to a PCX
All PCXs declared on the Alcatel-Lucent OmniVista 4760 Network Management System serveras configurable (the Process configuration attribute on the PCX tab in the System directoryis checked) are displayed in the tree structure except for pseudo PBXs and other devices thatare not compatible with the configuration.
3.2.3.1 Connecting to an Alcatel-Lucent OmniPCX Enterprise CS, an OmniPCX 4400or a PCS
3.2.3.1.1 Connection procedure for maintenance
Connection with the selected PCX may be via Telnet protocol or via SSH protocol. The type ofprotocol used is selected according to the SSH connection attribute on the Connectivity tabin the System directory, which can be configured in the PCX declaration (see moduleDirectory - System tab § Declaring a PCX ).
The name of the SSH client provides information about the user login and the target machine.The host name is either:
- the value of the attribute Hostname on the Connectivity tab in the System directory (thisvalue must be unique among all PCXs).
- an identifier built from the node, subnetwork, and network numbers of the PCX.
The SSH client embedded in the Alcatel-Lucent OmniVista 4760 Network ManagementSystem allows the SFTP transfer between the Alcatel-Lucent OmniVista 4760 NetworkManagement System server and the Alcatel-Lucent OmniPCX Enterprise CS (menu Plugins >
3-3
SFTP transfer)
Note 1:
The Security license is required to use secure connection to the PCX via SSH.
To connect:
1. Select the Connect command from the shortcut menu.For both types of connection (TELNET or SSH), a separate window opens to allow theadministrator to identify himself to the PCX and to run specific PCX commands formaintenance purposes.
To disconnect:
1. (When a session is running) Select the Disconnect command from the shortcut menu.
Connection to a PCS:
1. Use the Configuration application to connect to a PCS through a Telnet or an SSHsession.
2. Select the Connect command from the shortcut menu.
The host name provided by the SSH client is an identifier that is framed from the PCS IPaddress, the node, subnetwork and network numbers.
Note 2:
The type of protocol (Telnet or SSH) to be used, is selected according to the SSH connection attribute of
the PCX.
3.2.3.1.2 Connection and object model (MIB) loading procedure
1. To configure a single PCX, click to select it in the tree. To configure several PCXssimultaneously, use the mouse and the SHIFT or CTRL keys to select them.
Remark:Only PCXs with the same release can be configured simultaneously. They can belong to differentnetworks. The SHIFT and CTRL keys have no effect when an incorrect multi-selection is attempted.
2. Click the icon in the dynamic icon toolbar or select the Configure command from the
shortcut menu.
The procedure for switchover to connected (online) mode (PCX tab) is performed as follows:
1. The server retrieves the PCX release at the specified address and identifies it.
2. If the server was able to retrieve the release (version), the application loads the PCX's MIBand displays it in the tree.
3. Double-click the icon to display the complete tree structure of the PCX's MIB.
Note 1:If the server does not recognize the PCX software release, it has to query the PCX to download theMIB. To do this, it uses the FTP account (logon and password). This is usually entered when thePCX is declared. Contact your installation technician, if necessary.
Note 2:The Passive communication server configuration is not available.
3.2.3.1.3 Connection time
Chapter 3
3-4
- Average time to set up an Alcatel-Lucent OmniVista 4760 Network Management SystemPPP connection with a PCX:• Using a modem: 1 minute.• Using a TA : 30 seconds.
- Connection inactivity timeThe connection inactivity timeout may be modified:1. Run the Directory application, then select the PCX.2. Click the Connectivity tab.3. Configure the Timeout PPP attribute:
The timeout must be less than 10 minutes (PCX timeout).
Note:On disconnection, the connection remains established for 15 seconds.
An application may use this time (recovery time) to dialog with the PCX without the connection pro-cedure having to be repeated.
However, if the port is needed for a connection with another PCX, disconnection is immediate.
3.2.3.1.4 Local (internal) save of object models (MIBs)
At each connection to the Alcatel-Lucent OmniPCX Enterprise CS or OmniPCX 4400, theobject model (MIB) is compared to the one stored on the Alcatel-Lucent OmniVista 4760Network Management System client PC.
If object model version or configuration profile or language are different, the new object modelis automatically loaded.The following window is displayed. This window allows object model save settings to beselected:
Figure 3.2: Object model saving properties window
Note:
This window can also be viewed at any time via the Configuration>Object model save menu.
The window is composed of the following sections:
- Local save: the box is checked (selected) by default. It allows you to specify if you want tomake a local save of the MIB. If you uncheck (deselect) the box, the MIB will not beinternally saved (same effect as the Cancel button displayed in the window). At thefollowing connection, the Alcatel-Lucent OmniVista 4760 Network Management Systemwill again offer to save the MIB internally.This allows you to save time when making subsequent PCX connections: the system willdirectly search for the MIB in the local directory.
3-5
- Number of saved object models: the system displays the number of previously savedMIBs. The List button gives access to the “Local object model management” screen, thatdisplays the names of previously saved MIBs and date of save. Obsolete MIBs can bedeleted in this screen.
- Maximum number of saved object models: the system displays the maximum number ofsaved MIBs (default, 5). This number can be configured. If this number is exceeded, youcan either delete existing MIBs or increase the maximum number possible.
- Save directory: the system displays the default save directory. If you want to change this,click Search to select the desired directory, then confirm.
- Click OK to save the MIB.
Notes:
This procedure also applies when saving the client MIB on the server.
You must delete the MIB in order to save a new one whenever a profile is changed, as the change in pro-
file updates the access rights to classes and attributes on the server but doesn't reset the local MIBs.
3.2.3.2 Connecting to an OmniPCX Office
In the tree, after selecting an OmniPCX Office via the shortcut menu, you can:
- Run the OMC configuration application in online mode, in which the application isconnected to the PCX and configuration operations can be applied on the PCX.
- Run the OMC configuration application in offline mode. The application is not connected tothe PCX and the configuration operations are stored in a backup file and are applied to thePCX later.
- Run OMC in online mode to:• Schedule save of configuration data for a OmniPCX Office or set of OmniPCX Offices
in a network/subnetwork to theAlcatel-Lucent OmniVista 4760 Network ManagementSystem server application.
• Schedule restore of configuration data for a OmniPCX Office from the Alcatel-LucentOmniVista 4760 Network Management System server application to the OmniPCXOffice.
• Schedule download of a new release to the OmniPCX Office or a set of OmniPCXOffices in a network/subnetwork.
- Run a browser to configure the Internet Access service management application.
Note:In the tree, several OmniPCX Offices may be selected simultaneously when using the Internet Ac-cess service management application.
Notes:
OMC is a separate application from the Alcatel-Lucent OmniVista 4760 Network Management System
and must be installed on every 4760 client PC where it will be used, either for offline or online manage-
ment, or on the 4760 server PC for scheduled operations.
Alcatel-Lucent OmniVista 4760 Network Management System releases 4.0 and greater support only
OMC. Only Alcatel-Lucent OmniVista 4760 Network Management System releases 4.0 and greater sup-
port OMC. You may launch OMC for more than one OmniPCX Office at a time, provided that each Omni-
PCX Office is of release 5.0 or greater.
Chapter 3
3-6
3.2.3.2.1 Connection procedure
1. Select the PCX in the tree by clicking it.
2. Depending on the connection mode selected:• In Online mode, click the icon in the dynamic icon toolbar or select the
Configure> Online mode command from the shortcut menu.In Alcatel-Lucent OmniVista 4760 Network Management System and if the appropriatePCX and OMC releases (versions) are installed, the Alcatel-Lucent OmniVista 4760Network Management System server sets up the connection in the appropriate mode.When the PCX has not yet been synchronized in the Alcatel-Lucent OmniVista 4760Network Management System, PCX release is not yet known.At initial connnection, you can specify selected connection mode (active or passivemode):1. Select the PCX in the tree by clicking it.2. Select the Configure > Online mode > Passive or Active mode command from
the shortcut menu.• In Offline mode, select the Configure> Offline mode command from the shortcut
menu.The OMC interface is launched automatically (the OMC interface must be installed).
3. Select the desired PCX User account, enter the corresponding Password, and click OK.
Note:When the PCX database is loading in offline mode, if the error, “Programmer/User error: -28” is dis-played, contact your installer.
4. In the window, expand the PCX client tree structure.
5. To use the OMC interface, please refer to the appropriate document.
The PCX configuration data is saved in the directory “4760_ARC/OXO/data/NetworkNo./Subnetwork No./Node No.” on the Alcatel-Lucent OmniVista 4760 Network ManagementSystem server.
4760_ARC is the shared directory containing saved (backup) files (.cdb).
Sharing is implemented at Alcatel-Lucent OmniVista 4760 Network Management Systemapplication installation, with read-only access for all users.The administrator is responsible for granting "write" rights to users who require these.To access the shared directory, the user must be a network user.
3.2.3.2.2 Saving/Restoring and Downloading with OmniPCX Offices
See module Configuration - Saving/Restoring and Downloading with OmniPCX Office .
3.2.3.2.3 Connecting to Internet Access
To connect:
1. Select the PCX in the tree by clicking it.
2. Select the Internet Access command from the shortcut menu.Internet access is launched.
3. The first time this is used, confirm the certificate allowing secure HTTPS connection.
3-7
4. For more information, refer to the OmniPCX Office documentation.
To disconnect:
1. With the browser running, use the Disconnect Internet Access command in the shortcutmenu.
3.2.3.3 Connection failure
In the event of a connection failure, the user can check and correct the settings of the selectedPCX(s).
When the connection fails, the attributes to be checked in priority are:
- IP Address
- FTP Username
- FTP Password
Contact your installation technician, if necessary.
3.2.3.4 Disconnecting
Disconnection procedure:
1. Click the icon in the dynamic icon bar.
2. Disconnection results in switchover to offline (disconnected) mode (Network tab).
3. To reconnect, select the PCX, then click the icon.
3.2.4 Administering the Eye Box
The Eye Box admin, the web application in the Eye Box server is accessed by the Eye BoxAdmin URL that is set during the registration of the Eye Box in the Alcatel-Lucent OmniVista4760 Network Management System System directory. The Eye Box suite includes a webbased administration interface which can be launched from the Configuration and theTopology applications.
To administer the Eye Box:
1. Select the Eye Box from the network tree.
2. Select Eye Box Administration from the shortcut menu. A web browser is launched toconnect the Alcatel-Lucent OmniVista 4760 Network Management System client to theEyebox web server.
___change-begin___
Chapter 3
3-8
___change-end___
Figure 3.3: Eye Box administration window
3. Perform the administration task in the displayed Eye Box administration console. Toterminate the session, select Disconnect Eye Box Administration from the Eye Boxshortcut menu.
Note:
The Eye Box administration can also be performed from the Topology application, using the Configura-
tion option in the shortcut menu.
3.3 PCX tab
3.3.1 Preliminary steps
The following information only concerns the configuration of an OmniPCX 4400 and anAlcatel-Lucent OmniPCX Enterprise CS.
PCXs are configured in connected (online) mode.
3-9
3.3.1.1 PCX tab, description
The PCX tab may contain one or more PCX configuration tree structures.
Each PCX tree is automatically constructed from its own MIB.
The PCX tree contains different types of items, for example:
- node
- object
- instance
Example: The user object contains instance 32000.Each instance contains attributes that can be modified. An instance can also contain secondlevel objects that contain second level instances and so on.
3.3.1.2 View/Modify PCX configuration
For general data display and modification operations, see:
- module Interface - Viewing data ,
- module Interface - Data search ,
- module Interface - Modifying data .
3.3.1.2.1 Terms used
Identification attributes: identification of an instance is unique. Attributes representing itsidentification cannot be modified from the Configuration application.
Example:
The identification of a User is performed via the Directory No. instance attribute.
3.3.1.2.2 New grid (table)
This command displays a window consisting of search and data fields.
1. Select an object or an instance in the tree.
2. You can either:• Select the New Grid (table) command from the shortcut menu.• Click the icon in the dynamic icon bar.
3.3.1.2.3 Optimizing parent display
To avoid needless repetition of common attribute data, the display can be optimized with theicon.
Example: A list of users with a common host PCX. By clicking , the display switches from
Chapter 3
3-10
table to record mode and vice versa. The common attribute is then presented as the name ofthe window.
3.3.1.2.4 Selecting attributes
The Select attributes command is used to display only the attributes you require for a type ofitem.
1. Select the Attributes Selection command from the record or table shortcut menu.
2. Customize the attribute display by either:• Selecting or deselecting each box.• Deselecting all boxes by clicking Deselect all.• Selecting all boxes by clicking Select all.
3. Click OK.
3.3.1.2.5 Attribute help
The Attribute Help... command displays shortcut help for PCX objects and attributes.
1. Select an attribute.
2. Select the Attribute Help... command from the shortcut menu.
3.3.1.2.6 Graphical configuration of a set keypad
This feature is specific to User type instances. It is used to configure the programmable keysof an Alcatel series 8 and 9, set and the programmable and directory keys of a REFLEX set :
1. Select a User type instance with a REFLEX or Alcatel series 8 and 9 set.
2. Select the Graphical View command from the shortcut menu or click the icon in the
dynamic menu bar. A window representing the REFLEX or Alcatel series 8 and 9 set isdisplayed.
3. Click the key to configure or select it by number from the Directory Keys orProgrammable Keys tabs for REFLEX or Alcatel series 8 and 9 sets and from theProgrammable Keys tab for Alcatel series 8 and 9 sets:• In record mode, the record corresponding to the key is displayed.• In table mode, the line corresponding to the key is highlighted.
Remark:Modifying a set key may change the content of the associated keys. Use the Refresh command inthe shortcut menu to view the modifications.
4. Complete the attributes.See module Interface - Modifying data § Updating attributes .
5. Click Apply to accept changes.
3.3.1.2.7 Transferring a REFLEX set to an Alcatel Series 8 and 9 set
When a REFLEX set is replaced by an Alcatel series 8 and 9 set, the directory keys are nolonger valid.To remedy this and transfer the directory keys of the original REFLEX set to the programmablekeys of the new Alcatel series 8 and 9 set, perform the following procedure:
1. Export user directory keys.
3-11
2. Convert user directory keys (see step 5).
3. Import user directory keys (see step 6).To replace a REFLEX set with an Alcatel Series 8 and 9 set:
1. Select one or more Users with a REFLEX set.
2. Select the Export repertory key command from the shortcut menu.A window is displayed.
3. Enter a file name (.txt) in a local PC directory.
Note 1:An associated conversion file (*converted.txt) is created in the same directory. This file contains theold directory keys converted into programmable keys. Key number in this file is not significant.
4. Click OK.
5. In the attributes window, modify set type to convert REFLEX set to Alcatel series 8 and 9set.
Note 2:The system modifies set parameters and deletes keys that cannot be conserved on the new type ofset.
6. Select the Import repertory key command from the shortcut menu.A window is displayed.
7. Select the conversion file.
8. Click OK.The directory keys are loaded in the system as programmable keys (according to the limitof available places on the target set).
Note 3:The file (.log) contains a list of keys that could not be reimported due to a lack of space on the newset.
If you want to change the Alcatel series 8 and 9 set back to a REFLEX set, a standard importof the initial file restores all directory keys on the REFLEX set.
3.3.1.2.8 Inter-application switching
Switching from one application to the other depends on licenses and user rights.
The Accounting, Directory, Alarms and SIP tabs are used to switch between thecorresponding applications and to obtain information on the selected item.
Switching to alarms and events
For alarms, objects providing a link to the Alarms or events application are:
- PCX node
- Shelf
- Interface board
- Terminal
- Inter-node link data
For events, objects providing a link to the Alarms application are:
Chapter 3
3-12
- UsersTo switch to alarms/events of an instance:
1. Select an instance and switch to record mode.
2. Select the Alarms tab.Alarms application functions for this instance are now available.
See module Alarms - Overview .Depending on the type of instance selected, either the alarm or event list is displayed.
Example:
You want to acknowledge an interface board alarm from the Configuration application:
1. Select an interface board.
2. Click the Alarms tab to display alarms.
3. Select an alarm.
4. Select the Acknowledge command from the shortcut menu.
5. Click the Configuration tab or select another instance in the tree to return to the Configuration win-dow.
Switching to the company directory
This function simplifies directory management following creation of a new User.
For example, assuming you have just created a new User, "Joe Hill, extension 1111", byclicking the Directory tab:
- If his record is displayed, Joe Hill already exists in the company directory with this phonenumber.
- If the Setting Links window is displayed, the link Joe Hill does not exist in the directorywith this number. In this case, you must:• Either, create a record in the directory,• Or, search for an existing entry in the directory by clicking Search, then establishing a
link to this entry.Once this is done, the link between the set (extension) and the directory entry is created.
The PCX instances concerned are:
- User
- User alias
- Abbreviated (Speed dial) No.
- Abbreviated (Speed dial) No. aliasTo switch to the directory:
1. Select an instance and switch to record mode.
2. Select the Directory tab.You can now:• Create a directory entry if the instance concerned has no directory entry.• View/modify a directory entry.• Create/modify/delete a link in a directory entry.• Delete a directory entry and its link.
3-13
To create a directory entry or link in an existing directory entry:
1. Click Replace in the Setting links window, then click Create.
2. Select the type of entry you want to Create.
3. Click the Attribute tab.
4. Confirm by clicking Create, then OK.
Links can also be managed with the directory by selecting a User or User alias instance, etc. inthe tree and clicking Setting links in the shortcut menu.
3.4 Handling instances
3.4.1 Management commands
The tree structure has commands for simple or advanced PCX configuration operations inconnected (online) mode.Setting links: runs the company directory link management assistant.Open/Close: expands or collapses the selected branch.Filter: limits tree structure content to a selection of chosen attributes.Create: creates an instance at the selected position.Delete: deletes the currently selected item.Import/Export (scheduled): commands to import or export configuration data (scheduledmode is an option) .Refresh: updates the display.New Grid (table): opens a separate new edit window.Graphical View: opens a Reflex or IP Phone set configuration window.Object model save opens a PCX MIB save window (OmniPCX 4400 and Alcatel-LucentOmniPCX Enterprise CS).Connect: opens a Telnet or SSH session and a connection with the PCX (OmniPCX 4400 andAlcatel-Lucent OmniPCX Enterprise CS).Commands are shaded when they are unavailable for the currently selected item. Forexample, Graphical view is displayed for a selected Reflexes set user.
Note:
You can also Copy/Paste some items in the tree structure (node, shelf, board... ):
1. Select this item in the tree structure.
2. Use the Ctrl and C keyboard shortcut to copy the item. Item ID is placed in the 4760 clipboard.
3. Use the Ctrl and V keyboard shortcut to paste the item.
• Into the Topology application, to reroute alarms.
• Into Alarm filters, to perform an action if there is an alarm for a specific object.
Management commands are also available via icons in the main data window:moves the selected item on edited lines.
positions recurrent data at the top of the record.
Chapter 3
3-14
switches display between record and column modes.
creates a record.
locates the information displayed in the main window in the tree.
prints the information displayed in the main window.
.confirms creations and modifications.
deletes the currently selected item.
3.4.2 Creating instances
3.4.2.1 Simple creation
You can create create instances:
- from the tree shortcut menu.
- from the data field shortcut menu (this menu also allows several new instances to becreated simultaneously).
1. Select instances. by either:• selecting an object or an instance in the tree.• or, using the search field or the tree to display one or more instances in the data field.
See module Interface - Data search .
2. Create instances. by either:• selecting the Create command from the shortcut menu one or more times.• clicking the icon. The new instances are shown in the data field.
3. Complete the attributes.
4. Click to accept your changes.
Example:
Adding a user.
1. Select Node (node name) > User.
2. Select the Create command from the shortcut menu.
3. Complete the attributes.
3-15
table 3.2: Attributes for adding a userAttributes Values
Directory Number Set (extension) No.
Physical address (shelf address, interfaceboard address, equipment address, etc.)
For each shelf, board, or equipment address:• Specific value known by the user.• 255: the extension is reserved but its
physical address is not configured.• -1: the physical address is automatically
configured by the PCX.
Set Type Identifies the type of extension (selection viathe scrolling menu).
4. Click to accept your changes.
Note:
When you create or modify a value, the Alcatel-Lucent OmniVista 4760 Network Management System
checks the syntax. A dialog box displays giving the authorized characters and the size limit. If the string
entered is too long (for example the value for Directory Name), the value is truncated to the limit.
When the name of an attribute is prefixed by UTF-8, the value can support any UTF-8 characters
(Chinese or Russian characters). In this case, the length limit for the value varies according to the char-
acter set used (2 or 3 UTF-8 characters may be used to display a single Chinese character, for example).
3.4.2.2 Creating a User from a user profile
The Profiled users object allows a user to be created using an extension and theprogrammable keys of the extension (or of other extensions) as a model:
1. Select the Profiled users object.
2. Select the Create command from the tree shortcut menu.An instance record is displayed in the data field.
3. Complete the attributes.See module Interface - Modifying data § Updating attributes .
table 3.3: Attributes for creating a user from a user profileAttributes Values
Directory Number Set (extension) No.
Phone book Name (Dial by name) Name associated with the set/extension
Phone book First name (Dial by name) First name associated with the set
Set Type Identifies the type of extension (selection viathe scrolling menu).
Chapter 3
3-16
Attributes Values
Physical address (shelf address, interfaceboard address, equipment address, etc.)
For each shelf, board, or equipment address:• Specific value known by the user.• 255: the extension is reserved but its
physical address is not configured.• -1: the physical address is automatically
configured by the PCX.
Station profile from Identifies the model extension by its extensionNo.
Key profile from Identifies programmable keys of modelextension(s).
4. Click to accept your changes.
The new instance is displayed in the tree under the Users object.The Profiled users object remains empty.
3.4.2.3 Creating a series of users in one step
To optimize data entry operations, several entries can be created simultaneously when theyhave several similar parameters. Example (with users):
1. Place the cursor on the Users branch and select the Create command. A blank record isdisplayed.
2. Update the directory number by entering the first and last entries in the user "range" to becreated: 4010:4020 to create 11 new users. An entry table is displayed.
3. Update user parameters that differ, then apply your modifications.
3.4.3 Deleting/Moving instances
3.4.3.1 Simple deletion
The Delete command allows one or more selected instances to be deleted from the tree or thedata field:
1. Select the instance(s) to be deleted.
2. Select the Delete command from the shortcut menu.The symbol appears, either:
• at the top of an instance record,• at the beginning of the line of concerned instances in a table.
3. Click to accept your changes.
3.4.3.2 Moving an extension
You want to move an extension from node 1 to node 2:
3-17
1. Select Node 1 > User > extension (extension name and No.).
2. Enter the attributes:
table 3.4: Attributes for moving an extensionAttribute Value
Location node Node 2 No.
Shelf Address New address on node 2
Board Address New address on node 2
Equipment Address New address on node 2
3. Click OK.
3.4.3.3 Action
Some instances have an Action tab from which you can launch a specific action.
Example actions:
- Forced deletion of a user.
- Moving an Interface Board.
3.4.3.3.1 Forced deletion of a user
Forced deletion is an action specific to User type instances. It allows a user's extension to bedeleted, even if it voicemail messages remain:
1. Select one or several User instances.
2. Click the Action tab.
3. Select the Forced delete value in the Action attribute of each instance to be deleted.
Remark:The possible values are preconfigured. To display the Forced delete value, use one of the followingmethods:
• Click in the value field and type F.
• Double-click in the the value field and select the Forced deletion action from the drop-down list.
4. Click to accept your changes.
3.4.3.3.2 Moving an Interface Board
Moving a board is an action specific to Interface board type instances. This action is used to:
- change board position in the same shelf,
- move boards from one shelf to another shelf.To move an interface board:
1. Double-click Shelf, then click to select a shelf.
2. Select one or more Interface board instances.
3. Select the Action tab.
4. Select the Move value in the Action attribute of each instance to be moved.
Chapter 3
3-18
Remark:The possible values are preconfigured. To display the Move value, use one of the following methods:
• Click in the value field and type M.
• Double-click in the value field and select the Move action from the drop-down list.
5. Confirm by pressing Enter or by clicking another field.The following attributes are displayed:• Shelf, to identify the target shelf.• Board address, to identify the target board.
6. Complete the attributes.
7. Click to accept your changes.
3.4.4 Import/Export
These commands are used to import or export all or part of the PCX data as text files. Byexporting a file, you can easily edit configuration data offline using a spreadsheet application.The data can then be reimported to the initial PCX or any other PCX.
Example:
You can export a telephone feature class of service, modify some settings in the file, then reimport the
modified file.
3.4.4.1 Import/Export rules
- The .txt extension (default selection) indicates that the language used for the name ofattributes and their values is the same as that used in the Configuration application.
- The .prg extension indicates that the format used is an internal format (object and attributekeywords), independent of the language used by the Alcatel-Lucent OmniVista 4760Network Management System.
- Source object type must be identical to destination object type.
- Sub-objects may be imported separately.
- If the value of an attribute in the source file does not comply with the model of thedestination attribute, an error message is displayed.
- If the source file contains more attributes than the destination, the additional attributes areignored.
- If the source file contains less attributes than the destination, the missing attributes arecompleted with the default values.
- If the source file contains attributes entered with modifications that have not yet beenapplied (Modification, Creation, and Deletion symbols), these modifications are conservedin the import/export files.
- Pay special attention to the Secret Code field when importing. Starting with Alcatel-LucentOmniVista 4760 Network Management System release 4.0, an export file will contain amasked Secret Code ("****"). An import will update the Secret Code if the value is clearlywritten in the file (for example "1234"). No modification will be made if the field contains"****".
3-19
- When you import a file (for example, users.txt), an import log file is created in the samedirectory with the extension .log (for example users.log).
3.4.4.2 Exporting
The Export command allows a file containing all or part of the configuration data for one ormore PCXs to be created.
3.4.4.2.1 Export from the tree
1. Select one or more objects in the tree using the Shift or Ctrl keys.
Remark:Select a PCX to select all its objects.
2. Select the Export command from the shortcut menu.The export window is displayed.
3. Specify the path, extension, and name of the backup file.
4. Click Save.The export selection window is displayed.
5. Specify classes to be exported and click OK.
6. Select or clear the object classes to be exported.
7. Click OK to save the file and return to the tree.
3.4.4.2.2 Exporting from the data area
1. Select all or part of the instances in the data area.
2. Select from the shortcut menu:• The Export Grid (Table) ... > Export Selected Grid(s)... command to export the
selected instances.• The Export Grid... > Export All Grids... command to export all grid (table) instances.
3. Specify the path, extension, and name of the backup file.
4. Click Save to save the file and return to the data area.
3.4.4.3 Importing
The Import command allows a previously exported (and possibly modified) file to be loaded.
3.4.4.3.1 Import from the tree
1. Select any object in the tree.
2. Select the Import command from the shortcut menu.
3. The import window is displayed.
4. Select the source file.
5. Click Open.The import selection window is displayed.
6. Select or deselect the object classes to be imported.
7. Click OK to import the file and return to the tree.
Chapter 3
3-20
Remark:
The data imported is automatically placed in the tree.
3.4.4.3.2 Importing from the data area
1. Use either the search field or the tree to display the destination object table.
2. Select the Import Grid... command from the data area shortcut menu.
3. Select the source file.
4. Click Open.The file is loaded in the editing table.
Remark:
If the imported file contains destination object instances which belong to one or more PCXs that are un-
declared, a dialog box is displayed. This box is used to replace the name of an undeclared PCX with the
name of one of the declared PCXs.
3.4.4.4 Scheduling Import/Export
To schedule import/export:
1. Select the object or object instances,
2. Select Scheduled Import/export in the shortcut menu.
3. Create a file name (if exporting) or select the corresponding file (if importing).
4. Select the attributes to be imported or exported.
5. Click OK to confirm.
6. Program the import or export via the Scheduler (see the module Scheduler - Overview ).
3.4.4.5 Using Import/Export, example
The following example shows the procedure to follow to copy all of a set's programmable keysto other sets of the same type:
1. Select the Users object.
2. Select the Export command from the shortcut menu. A window is displayed.
3. Specify file name and location and click Save. A class selection window is displayed.
4. Validate only the PCX name, Users, and Programmable key options, then click OK. Datais exported and the file is created.
5. Edit the file in a spreadsheet or text editing application (Notepad) and save your changes.Close the editing application to make the file available for import.
6. Import the file onto the PCX via the Import command in the shortcut menu. Loadingbegins. This may take several minutes depending on the number of configuration lines tobe validated.
3.4.5 Troubleshooting
Data imported or exported in schedule mode is only saved in the directory\4760\Webclient\data\import.
3-21
Anomaly: The server \import directory is always displayed as empty in the Alcatel-LucentOmniVista 4760 Network Management System windows, whereas the Windows Explorershows files in this directory.
Cause: Conflicting or incorrectly configured Apache server HTTP port number.
Solution: Check for any inter–application sharing of ports. Check port number (80 by default)in the directory, System > Nmc > ServerName > Servers > ServerName > Apache >Serviceport.
3.5 Saving/Restoring and Downloading with OmniPCX Office
3.5.1 Preliminary steps
OmniPCX Office save/restore/download operations performed from a Alcatel-LucentOmniVista 4760 Network Management System use the OMC application running as abackground task.For correct operation, the password configured on the Alcatel-Lucent OmniVista 4760 NetworkManagement System side must match the one used for the OMC application.
To modify OmniPCX Office/OMC password (if necessary):
1. Start the Directory application.
2. Click the System tab.
3. Click the PCX in the tree structure.
4. Click the Connectivity tab.
5. In the OMC Config password attribute, modify the password (if necessary) so that it is thesame as the password used for the OMC application.
During the database backup, the OmniPCX Office database is saved on the Alcatel-LucentOmniVista 4760 Network Management System server in the directory 4760_ARC/OXO/data.This directory must be shared in order for the 4760 client to access it. By default, the share isnot open at 4760 server installation time.
To open the share:
1. Create a local user on the 4760 server and authorize the share for this user.
Note:For Alcatel-Lucent OmniVista 4760 Network Management System release 4.0 and greater, the sharename is OXO-databases by default.
2. In the Directory application, click the System tab.
3. Select the entry NmcConfiguration > GlobalPreferences > Config > OXOAccess.
4. Enter the name of the local user created in step 1 in the User name for access to theshared directory attribute.
5. Enter the password of the local user created in step 1 in the Password for access to theshared directory attribute.
The attribute Share name is set by default to the name of the share as it was configured atinstallation time. For Alcatel-Lucent OmniVista 4760 Network Management System release 4.0and greater this value is OXO-databases. In the case of an upgrade from a prior release, thevalue is 4760-pm5.
Chapter 3
3-22
Caution:
If an Alcatel-Lucent OmniVista 4760 Network Management System release prior to 4.0 has been
uninstalled before a new installation of release 4.0 or greater, or if the name of the share has been
modified, check the value of the Share name attribute.
3.5.2 OmniPCX Office configuration preferences
The Alcatel-Lucent OmniVista 4760 Network Management System release 4.1 enables you toset the OmniPCX Office configuration preferences from the Alcatel-Lucent OmniVista 4760Network Management System client.
3.5.2.1 Configuring the OmniPCX Office database directory
The OmniPCX Office database root directory is located by default at <4760_ARC>/OXO/datain the Alcatel-Lucent OmniVista 4760 Network Management System server. This location canbe changed in the OXO Preferences window. Also the automated maintenance of theOmniPCX Office database directory can be performed from the OXO Preferences window.
To configure the OmniPCX Office database directory:
1. Select Preferences> Configuration> OXO Preferences from the menu bar. The OXOPreferences window is displayed.
3-23
Figure 3.4: OXO Preferences window
2. Click Backup/Restore OXO tab in the OXO Preferences window.
3. Click Search to select the folder for the Backup location of the OXO database. TheBackup location window is displayed
4. Select the required folder from the displayed list. To create a new folder, enter the name ofthe folder to be created in New Folder.
5. Click Select to complete the folder selection. To exit the Backup location window, clickCancel.
Note:The OmniPCX Office database can also be located in a network resource. If you use the network re-source, enter the name of the resource according to the format \\<OXOFileServer>\<OXOdb>.
6. Select the attribute for setting the database disk space threshold, in Type of Control.• Available Disk Space: The threshold is based on the empty disk space of the
database.• Maximum Record volume: The threshold is based on the maximum amount of data
that can be stored in the database.
7. Select the units for the threshold attribute, in Units.
8. Enter the values for the First Threshold and the Second Threshold. These values triggerthe alarms.
9. Select the units for the record life of the database, in Units.
10. Enter the amount of time for retaining the records in the database, in Delay.
11. Click OK to set the configuration data. Click Cancel to exit the window.
3.5.2.2 Configuring the OmniPCX Office version directory
The OmniPCX Office version directory is located by default at <4760_ARC>/OXO/data in theAlcatel-Lucent OmniVista 4760 Network Management System server. This location can bechanged in the OXO Preferences window.
To configure the OmniPCX Office version directory:
1. Select Preferences> Configuration> OXO Preferences from the menu bar. The OXOPreferences window is displayed.
2. Click OXO Software Update tab in the OXO Preferences window.
3. Click Search to select the location for the version directory, in Version path. The Backuplocation window is displayed
4. Select the required folder from the displayed list. To create a new folder, enter the name ofthe folder to be created in New Folder.
5. Click Select to complete the folder selection. To exit the Backup location window, clickCancel.
Note:The OmniPCX Office versions can also be located in a network resource. If you use the network re-source, enter the name of the resource according to the format \\<OXOFileServer>\<OXOVersion>.
6. Select the attribute for setting the version directory space threshold, in Type of Control.• Available Disk Space: The threshold is based on the empty disk space of the
Chapter 3
3-24
database.• Maximum Record volume: The threshold is based on the maximum amount of data
that can be stored in the database.
7. Select the units for the threshold attribute, in Units.
8. Enter the values for the First Threshold and the Second Threshold. These values triggerthe alarms.
9. Click OK to set the configuration data. Click Cancel to exit the window.
3.5.2.3 Configuring the scheduled task parameters
To configure the parameters for the execution of scheduled tasks:
1. Select Preferences> Configuration> OXO Preferences from the menu bar. The OXOPreferences window is displayed.
2. Click OXO Scheduled Tasks Parameters tab in the OXO Preferences window.
3. In Number of retries, enter the number of retries that are allowed when a task fails.
4. In Number of parallel execution, enter the number of tasks that can executedsimultaneously.
5. In Retry Delay, enter the time interval allowed between two consecutive retries.
6. Click OK to set the configuration data. Click Cancel to exit the window.
3.5.2.4 Configuring the OmniPCX Office database shared directory name
The OmniPCX Office database directory is accessed by the OMC through a shared directoryon the Alcatel-Lucent OmniVista 4760 Network Management System server, during the OMCconfiguration session of an Alcatel-Lucent OmniVista 4760 Network Management Systemclient. The shared directory with a default name OXO-databases is created during theinstallation and its access is restricted. The server administrator has to grant access andauthorize the network connection to the shared directory.To configure the OmniPCX Office database shared directory name:
1. Select Preferences> Configuration> OXO Preferences from the menu bar. The OXOPreferences window is displayed.
2. Click Shared Directory Parameters tab in the OXO Preferences window.
3. Enter the name of the shared directory according to the format\\<ServerName>\<SharedDirectoryName>, in Shared Directory Name. This name shouldmatch the shared directory name in the Alcatel-Lucent OmniVista 4760 NetworkManagement System server.
Note:A network resource can also be used for the OmniPCX Office backup that is accessible by the OMC.It should be the same network resource name specified in the OXO Save/Restore tab (refer to thesection § Configuring the OmniPCX Office database directory ). In this case the OXO databaseshared directory in the Alcatel-Lucent OmniVista 4760 Network Management System server shouldbe removed.
4. Enable Secure Shared Directory to secure and restrict the access to the shared directory.
5. In Authorized User Name, enter the user name according to the format\\<ServerName>\<UserName>.
6. In Authorized User Password, enter the password to access the shared directory.
3-25
7. Click OK to set the configuration data. Click Cancel to exit the window.
3.5.2.5 Using network resource
From the Alcatel-Lucent OmniVista 4760 Network Management System release 4.1, theOmniPCX Office database and the versions can be located in a network resource. For moredetails, refer to sections § Configuring the OmniPCX Office database directory , § Configuringthe OmniPCX Office version directory and § Configuring the OmniPCX Office database shareddirectory name .
3.5.3 OmniPCX Office scheduled save
The save operation downloads OmniPCX Office configuration data to the Alcatel-LucentOmniVista 4760 Network Management System server application.
This task is scheduled.
Scheduling the task
1. Click the PCX in the tree structure.
2. Select the Schedule> Save command from the shortcut menu.The Task Type window of the Scheduler application opens.
3. Select Simple job or Synchronized task, then click Continue.The scheduling window of the Scheduler application opens automatically (entitled "Save").
4. Complete the task scheduling settings (see module Scheduler - Overview ).
5. Click OK to confirm the creation of the task.
Running the task
The Scheduler runs the task (see module Scheduler - Overview ).
The OmniPCX Office configuration data is saved in a file stored in the directory “4760-ARC/OXO/data/Network No./Subnetwork No./Node No.” on the Alcatel-Lucent OmniVista 4760Network Management System server.The name of the saved file (limited to 8 characters) is automatically created by the OMCapplication, in the following format:<YYMMDDHH>.cdb where <YYMMDDHH> is the date and time of task execution.
Note:
The directory “4760_ARC/OXO/data” must be shared with read/write rights under the name 4760–OMC
for the user specified in the Directory under the entry NmcConfigura-
tion>GlobalPreferences>Configuration>OXOAccess.
At installation, sharing is configured without access rights.
Execution status and the corresponding log file can be viewed in a report (see moduleScheduler - Overview § Execution reports ).
3.5.4 Scheduled save of network/subnetwork OmniPCX Offices
The save operation downloads the configuration data for a set of OmniPCX Offices in anetwork/subnetwork to the Alcatel-Lucent OmniVista 4760 Network Management Systemserver application.
Chapter 3
3-26
Scheduling
To schedule this task:
1. In the tree structure, click the OmniPCX Office network or subnetwork.
2. Select the Schedule> Save command from the shortcut menu.The operation is performed for each of the PCXs in the network/subnetwork following theprocedure described in § OmniPCX Office scheduled save .
Parallel (concurrent) operations
To configure the number of operations performed in parallel:
1. Start the Directory application.
2. Click the System tab.
3. Select the entry Nmc > NmcConfiguration > GlobalPreferences >Configuration.
4. Select the entry OXOAccess.The maximum number of operations executed simultaneously is limited to 10.
5. Complete the number of execution operations that can be performed in parallel in theNumber of simultaneous executions attribute.
Retries
Parallel executions may fail due to a lack of modem resources. A retry mechanism isimplemented at task execution level
To specify the number of retries if the operation fails:
1. Start the Directory application.
2. Click the System tab.
3. Select the entry Nmc > NmcConfiguration > GlobalPreferences >Configuration.
4. Select the entry OXOAccess.
5. In the Max No. of retries attribute, enter the maximum number of retries to be made if theoperation fails.By default, three retry attempts are made.The rules for creating save (backup) files obey the same specifications as described in §OmniPCX Office scheduled save .
3.5.5 OmniPCX Office scheduled restore
You can restore saved (backup) configuration data for a OmniPCX Office from theAlcatel-Lucent OmniVista 4760 Network Management System server to the OmniPCX Office.
Scheduling the task
1. Click the PCX in the tree structure.
2. Select the Schedule> Restore command from the shortcut menu.• The Restore window is displayed.
3-27
Figure 3.5: OmniPCX Office schedule restore window
3. Click Browse to open the dialog box.
4. Use the dialog box to select the appropriate save (backup) file in the directory “4760-ARC/OXO/data/Network No./Subnetwork No./Node No.” on the Alcatel-Lucent OmniVista4760 Network Management System server.
5. Click OK.The Restore window is now displayed with this file name.
6. Make sure the Immediate reset box is selected so that the PCX will be restartedimmediately once the data has been restored (the PCX must be restarted for the restoreddata to take effect).
7. Click OK to confirm the restore operation.The scheduling window of the Scheduler application opens automatically (entitled"Restore").
8. Complete the task scheduling settings (see module Scheduler - Overview ).
9. Click OK to confirm the creation of the task.
Running the task
The Scheduler runs the task (see module Scheduler - Overview ).
Save (backup) file data is read by the OMC application and loaded to the PCX.
Once the restore operation is complete, the PCX is restarted (if immediate reset has beenenabled by the user, see step 6).
Execution status and the corresponding log file can be viewed in a report (see moduleScheduler - Overview § Execution reports ).
Important:
Within the OMC application, compatibility is ensured for only the latest release. This means that a
database saved with PMI 410 can be restored with OMC release 5.0.
Therefore, it is recommended:
- to install the same release of the OMC application on the client stations and the Alcatel-Lucent
OmniVista 4760 Network Management System server.
- if the OMC application must be reinstalled, to first uninstall the current release of the OMC ap-
plication on all client stations and the Alcatel-Lucent OmniVista 4760 Network Management Sys-
tem server. After installing the new release of OMC, resave all the PCXs in order to recreate the
databases. If the operation is successful, you may delete the old databases saved on the Alcatel-
Lucent OmniVista 4760 Network Management System server.
Chapter 3
3-28
3.5.6 Scheduled download of releases to a OmniPCX Office
Releases are downloaded using the following procedure:
- Transfer a new release to the PCX.
- Change PCX release.
Scheduling the task
To schedule this task:
1. Click the PCX in the tree structure.
2. Select the Schedule> Software Update command from the shortcut menu.• The Software Update window is displayed.
Figure 3.6: Software update window
3. Click Browse to open the dialog box.
4. Using the dialog box, select the appropriate release in the shared directory“4760_ARC/OXO/SW” on the Alcatel-Lucent OmniVista 4760 Network ManagementSystem server.
5. Click OK.The Restore window is now displayed with this file name.
6. In the Swap title field, check (select) the following box:• Immediate for immediate switchover between releases (after disconnecting from the
OMC application).• Delayed for deferred switchover between releases.
In the Date field, enter the date and time when switchover is to be performed.This box is selected by default and displays OmniPCX Office date and time.
7. Click OK to confirm the download.The scheduling window of the Scheduler application opens automatically (entitled"Software Download").
8. Complete the task scheduling settings (see module Scheduler - Overview ).
9. Click OK to confirm the creation of the task.
Running the task
The Scheduler runs the task (see module Scheduler - Overview ).
The download mechanism transfers the difference between the release installed on the PCXand the new release.
3-29
A data save (backup) is performed on the node.
The switchover is performed at the date and time specified by the user.
Execution status and the corresponding log file can be viewed in a report (see moduleScheduler - Overview § Execution reports ).
Note:
The download (upgrade) is not performed unless the source and target releases belong to the same ma-
jor version.
3.5.7 Scheduled download of releases for OmniPCX Offices in anetwork/subnetwork
Release upgrade downloads the configuration data for a set of OmniPCX Offices in anetwork/subnetwork to the Alcatel-Lucent OmniVista 4760 Network Management Systemserver application.
1. In the tree structure, click the OmniPCX Office network or subnetwork.
2. Select the Schedule> Software Update command from the shortcut menu.The operation is performed for each of the PCXs in the network/subnetwork following theprocedure described in § Scheduled download of releases to a OmniPCX Office .
Download (upgrade) operations are performed in parallel (simultaneously).The mechanism used for parallel execution of download tasks is the same as that described in§ Scheduled save of network/subnetwork OmniPCX Offices .
Note:
When the task is performed, the system checks the OMC version downloaded from the server and the re-
lease of each OmniPCX Office are the same major version.
Chapter 3
3-30
4.1 Overview
4.1.1 Overview
The Accounting application is part of the Alcatel-Lucent OmniVista 4760 CommunicationManagement System (called Alcatel-Lucent OmniVista 4760 Network Management System inthis document).
This application is used to configure the parameters of Accounting, Traffic analysis, and theVoIP Performance analysis option.Depending on the licenses installed, some parts of the application may be grayed out (shaded)or not applicable.
Note:
The data received from the Passive Communication Server is considered to be coming from the Alcatel-
Lucent OmniPCX Enterprise CS and is processed as the Alcatel-Lucent OmniPCX Enterprise CS data.
4.1.2 Accounting
Accounting is configured via the Parameters, Carriers and Organization tabs:
1. The Parameters tab is used to:• Configure filters for accounting record loading.• Calculate carrier cost comparison.• Manage carrier parameters: currencies and taxes. This data is required to configure
carriers correctly in the Carriers tab.
2. The Carriers tab is used to configure carriers (period, adjustment coefficient, tariff, region,direction, calendar).
3. The Organization tab shows charged items in tree structure form: stations, attendants,voice mail, etc.In addition, data for each entry in the tree is displayed in 6 tabs:• Properties (description of the entry)• Records (tickets) (x last records of the entry)• Masks (mask applied to the entry)• Costs (cost profile applied to the entry)• Tracking (tracking profile applied to the entry)• Tracking status* (counters and thresholds displayed)
Note 1: (*) Tracking options available depending on the license installed.
Note 2: The directory entry is inserted in the Organization if the directory license is installedand if a link has been created between the Company Directory and the System directory.
4.1.3 Traffic Analysis
This optional module features the Parameters and Organization tabs.
4
4-1
Traffic analysis section is accessed through the following path Parameters > Loading >Traffic analysis.
4.1.4 Performance Analysis for Voice over IP
This optional module features the Parameters and Organization tabs.To configure Voice over IP performance analysis, select the path Parameters > Loading >Voice over IP.
Note:
This module is operational from release OmniPCX Enterprise 6.2 (f3.301) and OmniPCX Office 5.0.
4.1.5 Specific Menu
When the Accounting/Traffic/VoIP application is run, the toolbar provides a drop-down listwith the same name.
table 4.1: Accounting/Traffic Menu CommandsCommands Description
Archive records See module Accounting - Database maintenance §Archiving/Restoring Records .Restore records
Purge See module Accounting - Database maintenance § DeletingData Manually .
Compute cost Following some modifications in Accounting, the costs recordedin the base must be updated. See module Accounting -Organization tab § Exceptional Processing - RecalculatingCosts, Counters and Subscriptions .
Total calculation See module Accounting - Parameters tab § Recalculating TotalCounters Manually .
Detect exceedingthresholds
See module Accounting - Organization tab § DetectingExceeded Thresholds (Scheduled or Manual) .
4.1.6 Terminology
4.1.6.1 Accounting/ Traffic Analysis
Ticket: a ticket is a record generated by the PCX which groups the characteristics of a call (forexample: number called, call type, duration, etc.). Records are stored in the PCX in the form offiles that can be transferred to the Alcatel-Lucent OmniVista 4760 Network ManagementSystem.
Counter: Traffic analysis data managed by the PCX, e.g. : number of public incoming call foran attendant
Total Counter: totalized counter managed by the Alcatel-Lucent OmniVista 4760 NetworkManagement System. e.g.: monthly number of calls per user
Indirect carrier: characterizes a second carrier that can be accessed via a first carrier. Thecost of a call made via two successive carriers is always calculated according to call durationand is equivalent to the sum of the cost of both carriers.
Chapter 4
4-2
ISDN: Integrated Services Digital Network.
DISA: Direct Inward System Access. This type of access enables a station outside a companyto make calls via the company PCX without being charged except, possibly, for the callbetween the external set and the PCX.
4.1.6.2 Performance Analysis for Voice over IP
Ticket: gives information on a call segment (a segment is defined by two network devicesused for VoIP performance analysis at RTP level). Each device at the end of a segmentgenerates a record.
IP File: files created by the PCXs and stored on the PCXs. A file contains the recordsgenerated by equipment attached to the PCX for one hour.
Out of range record: record for which at least one measurement is out of range.
Out of range records (tickets) rate: the percentage of out of limit records over a givenperiod.
4.1.7 Operating Principle
The Accounting application ensures calculation and distribution of call costs to chargeableentries (user, attendant, trunk group, etc.) that are grouped in a tree structure referred to asthe Organization.
The Traffic analysis application (accessed via the “Accounting/Traffic/VoIP” icon) allowsyou to analyze traffic for items in the Organization (trunk groups, users, DECT (PWT) sets,etc).
VoIP, an optional module of the Traffic analysis application, is used to analyze the VoIPperformance quantitatively (information on quantity and duration) and qualitatively (informationon network problems affecting call quality: excessive delay, high packet loss rates, etc.).The devices concerned are: IP boards and IP-phones (e-Reflexes and Alcatel Series 8),Softphone and 4645 voice mail.
Accounting, traffic analysis, and VoIP performance analysis data are used by the Reportsapplication. This application is dedicated to the generation of reports on chargeable entries inthe Organization.See module Accounting - Basic operation .Accounting with an OmniPCX Office has special features that must be considered – seemodule Accounting - Basic operation § Accounting with the and the Alcatel Office .
4.1.8 Pre-Configuration
4.1.8.1 Loading Records into the Database
To configure Accounting, Traffic analysis and/or performance analysis of VoIP correctly,perform the following operations in the order shown:
1. Configure data loading in the Parameters tab:• For traffic analysis, select the cost centers to be observed and counters to be loaded.
4-3
Caution:The default total (daily and weekly tasks) only applies to trunk groups, attendants, and at-tendant groups. This data does not apply to user data and DECT data.
It is possible to modify tasks to calculate the total for all counters, see: module Account-ing - Parameters tab § Modifying Counter Calculation Scheduling
• For accounting, select the records (tickets) to be loaded according to call type,duration, etc.
• For VoIP performance analysis, select the counters to be loaded and the IP addressesto be loaded.
See module Accounting - Parameters tab .
Note 1:In each case (accounting, traffic analysis and VoIP performance analysis), there is an Alarms tabproviding access to the corresponding alarms.
2. For accounting (only), update the Carriers tab:• Specify carrier tariffs (rates) to ensure cost calculation when accounting records are
first downloaded.See module Accounting - Carriers tab .
3. In the System directory:• Enable or disable automatic creation of directory entries* and the list of initiating items.• Enable or disable Global accounting for undeclared PCXs. See module Accounting
- Basic operation § Processing Accounting for Undeclared PCXs :• Select the accounting mode, see: module Accounting - Basic operation §
Accounting Processing Modes• Define whether accounting and/or VOIP tickets are collected from PCSs
()
4. Trigger a synchronization. The Organization is updated and you can assign cost, mask,and tracking profiles as well as assign subscriptions. See module Accounting -Organization tab .
Note 2:
(*) See module Directory - Company tab § Creating Entries Automatically.
4.1.8.2 Collecting Records
To make PCX accounting or VOIP files available to external applications, these files must bestored in a 4760 server directory.Perform these operations:
1. In the System Directory, select the PCX.
2. Click theData Collection tab.
3. In the “data area”, double-click the Record/Ticket Collection attribute field and select:• Accounting: to store accounting files only• VOIP: to store VOIP files only• Accounting and VOIP: to store accounting and VOIP files
At synchronization, the files will be stored in the directory 4760\data\collector.
The accounting files are name: TAXAxxxx.DAT (for Alcatel-Lucent OmniPCX Enterprise CS),
Chapter 4
4-4
taxaxxxxx.alz (for OXO), taxaxxxxx.ofc (for OmniPCX Office)
The VOIP files are name: IPXXX.DAI (only for Alcatel-Lucent OmniPCX Enterprise CS)
Note:
See the module Directory - System tab § Declaring a PCX .
4.2 Basic operation
4.2.1 Accounting Data Processing on the Alcatel-Lucent OmniVista 4760Network Management System Server
The following figure shows the key stages of Alcatel-Lucent OmniVista 4760 NetworkManagement System accounting management via the processing of data generated followinga call.
Figure 4.1: Accounting Management Process
At 14h00, Michael Buxton makes a call via PCX (A). On call completion, an accounting record("ticket") containing a set of call data is generated and saved to a file.
At 1h00, during synchronization, server B downloads the files containing the traffic analysiscounters, accounting records (tickets), and VoIP performance analysis tickets.
At 1h30, accounting record data is extracted and call cost is calculated from carrier data (D1),see § The two Modes of Calculation for further details.
Option (E):
- Tracking can be used for Michael Buxton (number of calls, cost, etc.),
- Billing (charging) of M. Buxton's calls can be increased (marked up) according to a costprofile that includes:• The carrier used.• The type of calls made (private, business, internal, etc.).• Subscription for extension type and services offered.
4-5
At 10h00 the following day, the accounting manager uses the Reports application to generatea state (F) listing the details of calls routed by the PCX. To guarantee confidentiality, partial ortotal masking may be applied to data shown in reports.
This diagram highlights the separation that exists between the management of carrier costsand charged costs.The Accounting application has a dedicated interface to configure each type of data.
4.2.2 Different Uses
4.2.2.1 Global Accounting
In a PCX network (PCX1–PCX2), the Alcatel-Lucent OmniVista 4760 Network ManagementSystem server accounting manager can use costs (accounting) for calls on a single PCX in thenetwork (PCX1) and ignore costs for users on other PCXs (PCX2).
In this instance, common when the network extends over several sites with sharedmanagement, the manager performs detailed accounting on the PCX(s) on his site and willhandle other site calls as a global cost, external to the site.
4.2.2.2 The Advantages of Global Accounting
Global accounting per node mode:
- Simplifies accounting for a site in a large PCX network.
- Limits the volume of data in the database and optimizes processing.
- Reduces the number of components in the organization.
With two distinct modes (accounting file transfer enabled or disabled), this method meets theneeds of a high-traffic network. See § The two Modes of Global Accounting per Node .
Important:
When this mode is enabled on a PCX, no traffic analysis can be performed as this is based on en-
tities created in the organization. The PTP Process option is therefore disabled automatically.
4.2.3 Accounting Processing Modes
A total of five different types of accounting management are offered on each PCX:
1. None – no accounting.
2. Organization update without record retrieval.
Chapter 4
4-6
3. Global accounting per node without record retrieval.
4. Global accounting per node with record retrieval.
5. Detailed accounting.
Selection is performed on each PCX configuration record in the System directory via theAccounting Process attribute.
4.2.3.1 None - No Accounting
Applying this accounting mode to a PCX enables the following operations:
- The organization is not updated.
- Accounting files are downloaded only to ensure traffic analysis when the PTP Processoption is selected. No accounting functions are performed using these files.
- For traffic analysis, records for users of this PCX that are output by another PCX areloaded into the database, then assigned to chargeable entries created in the organization.
- If the PTP Process option is disabled:• No entity is created in the organization.• Records for PCX users output by another PCX are loaded into the database then
assigned to indeterminate level entities.
4.2.3.2 Organization Update Record (Ticket) Retrieval
Applying this accounting mode to a PCX enables the following operations:
- The organization is always updated.
- Accounting files are downloaded only to ensure traffic analysis when the PTP Processoption is selected. No accounting functions are performed using these files.
- For traffic analysis, records for users of this PCX that are output by another PCX areloaded into the database, then assigned to entries created in the accounting organization.
4.2.3.3 The two Modes of Global Accounting per Node
With accounting file retrieval:
- PCX accounting files are downloaded to the server. The entities of this PCX are notcreated in the accounting organization,
- Accounting records for users of this PCX are assigned to a single global entity configuredunder the Global accounting per node level of the organization,
- When accounting records for users belonging to other PCXs are loaded, the processingperformed depends on the Process accounting option of the PCX identified by therecord:• If the identified PCX is declared in the System directory, the record is processed
according to the accounting mode selected for the PCX.• If the identified PCX is not declared in the System directory, the record is processed
according to the Global accounting for undeclared PCXs attribute. See § ProcessingAccounting for Undeclared PCXs .
Without accounting file retrieval:
- PCX accounting files are not downloaded to the server. The entities of this PCX are notcreated in the Accounting organization,
4-7
- Accounting records for users of this PCX that are output by another PCX are loaded intothe database. They are then assigned to a single global entity created under the Globalaccounting per organization node level.
4.2.4 Processing Accounting for Undeclared PCXs
When records are loaded, those from PCXs declared in the System directory are includedand processed according to the Accounting Process attribute. Records from unknown PCXsare processed and placed in the organization depending on the Global accounting forundeclared PCXs option available in the System directory Nmc > ServerName > Servers >Loader — Specific tab:
1. Option selected: Records are assigned to a Global accounting by node entity. Records cansubsequently be reassigned if they were not declared in the PCX. This is not possible if theoption is not selected.
2. Option deselected: Records are automatically assigned to an indeterminate entity level.
Accounting per cost center for users of PCXs that cannot be synchronized with theOmnivista 4760 (4300, non-Alcatel PCX)
That is, a network composed of at least one OmniPCX 4400 to which one or more PCXs thatcannot be synchronized with the Alcatel-Lucent OmniVista 4760 Network ManagementSystem are connected via ABCF or QSIG trunk group. Calls to the public network from allusers of the PCX network transit via the OmniPCX 4400. All accounting records are thusgenerated by the OmniPCX 4400. As described above, by default, the records of the users ofnodes that cannot be synchronized are stored at the indeterminate entity level of theaccounting organization. As a result, reports cannot be generated per cost center or name forthese records.The remedial solution is as follows:
1. In the System directory, create a virtual OmniPCX 4400 PCX without connectivitymanagement under the same networks and subnetworks as those of the previouslycreated OmniPCX 4400. The node-network number must be the same as that specified inthe records in the chargedNode field. Select Detailed accounting.
2. Create the users by importing LDIF files. To maintain the standard organization, first importthe Telephonic Devices level. User LDIF files must contain (amongst other information)cost center name. The corresponding entry is automatically created in the accountingorganization (CC and set). The corresponding records, possibly stored under theindeterminate entity level, are automatically reported under the correct level.
Note:
Users can only be created by importing a LDIF file. To delete a user from the System directory, use the
command provided for this purpose. If a user is relocated from a PCX that cannot be synchronized to the
OmniPCX 4400, a new entry will be created in accounting after synchronization. This contains the name
of the new PCX. Special care must be taken with respect to the number of users allowed by the license.
Any creation performed via LDIF import is to be counted. Synchronization failure alarms should be gener-
ated for non 4400 PCXs.
4.2.5 Different Call Costs
4.2.5.1 Terms Used
Chapter 4
4-8
Unanswered Call Initial Cost adds an additional fee which applies to calls with zero duration.
Answered call initial cost adds an additional fee which applies to calls with non null duration.This cost corresponds to the call setup cost.
The minimum cost is used so that the Invoiced cost of a call, whether answered or not, is atleast equal to the minimum cost. This cost is applied whatever the duration of the call.
Invoiced cost is equivalent to (first carrier cost + any second carrier cost) multiplied by apossible adjustment coefficient.
Routing delay (to the connection) is only included when calculating cost duration. Thiscorresponds to the average delay for routing the call to the called extension, for calls whichbegin before the called party picks up the receiver (for example: analog link). This routingdelay is deducted before calculating the total call duration so as to avoid unjustifiedovercharging.
Tariff segment is used to include changes in call charging. It is expressed in cost/duration.Example: the first 5 minutes of a call are charged at 1.00 Dollar/min, then each additionalminute at 0.50 Dollar.
Direct or Indirect access. Indirect access characterizes the use of a carrier that can beaccessed via another carrier. An access is said to be direct when it transits via a trunk groupdedicated to the carrier in order to establish a call. An access is said to be indirect if it uses afirst carrier to reach a second carrier.
4.2.5.2 The two Modes of Calculation
Call cost calculation can be ensured:
- By the PCX which performed the call. This mode is called PCX cost.
- By the Alcatel-Lucent OmniVista 4760 Network Management System, which can performthe calculation depending on call duration or the number of units transmitted by the carrierto the PCX during the call.
Whatever the type of tariff, total call cost corresponds to the total of:
- An initial cost.
- A conversation cost.
This total cost cannot be less than a minimum cost.
An increase or a decrease (price marked up/down) can be applied to call cost via anadjustment coefficient.
The module Accounting - Carriers tab lists the parameters that must be entered in theconfiguration screens depending on the method of calculation adopted.
4.2.5.3 Calculation Performed by Alcatel-Lucent OmniVista 4760 NetworkManagement System
4.2.5.3.1 Calculation Based on Units (or Signals)
The result of the calculation is obtained by multiplying the number of units by the unit price.
The carrier must transmit pulses for this method to be used.
4.2.5.3.2 Calculation Based on Duration
To set up duration accounting, the following data is retrieved from the accounting record: the
4-9
called number and the date, time and duration of the call.
Call duration can consist of an initial duration and/or tariff segments.
For duration accounting, cost can be indiscriminately defined:
- In steps, i.e. in signal (pulse) simulation: with rounding up or down.
- Proportionally to time, with an accuracy to the nearest second.
Figure 4.3: Basic Configuration
table 4.2: Basic Configuration ParametersT1: initial duration A: initial cost
T2: call duration B : proportional cost
C: total cost of call
Figure 4.4: Advanced Configuration
table 4.3: Advanced Configuration Parameters
Chapter 4
4-10
T0: answer delay A: answered call initial cost
T1: initial duration B : proportional cost
T2: call duration C: total cost of call
C1: minimum cost
C2: unanswered call initial cost
C3: initial unit * unit cost
Note:
C3 is included when A is zero.
4.2.5.4 Calculation Performed by the PCX
Call cost is calculated by the PCX, then incorporated into the accounting record. This is AOC(Advice Of Charge).
An adjustment can be applied to the cost transmitted.
Adopting this method of calculation requires the Cost Info item to be provided in eachaccounting record provided by the PCX(s) and, therefore, costs to be set on each networkPCX.
Initial cost and minimum cost are not included when this method is used.
4.2.5.5 Call Transfer Management
In the case of call transfer, several records are transmitted by the PCX, whereas the carriermanages only one call. When the mode of calculation adopted is duration mode, initial costsare included only once.
4.2.5.6 Downloading the Record (Ticket) to the User's Node
On some networks, a user may have his call routed to a PCX other than the host PCX onwhich he is declared. An option in PCX2 configuration enables accounting records to bedownloaded to the PCX of the user making the call. User accounting is thus ensured for all hiscalls.
The Alcatel-Lucent OmniVista 4760 Network Management System includes and manages anytime difference between the PCXs (PCX1 and PCX2):
Figure 4.5: Downloading User Record between Different PCXs
4.2.6 Specific Features of Multi-Carriers
4.2.6.1 Multi-Carrier Configuration
A site can route calls using several carriers, depending, for example, on the destination or the
4-11
time at which the call is made. Each carrier can be distinguished by reading data contained inthe record:
- Identification of the number of the trunk group taken by the call.
- Dialed number prefix identifier.
4.2.6.2 Indirect Carriers
An indirect carrier (also known as a cascaded carrier) is a carrier that is accessed via an initialcarrier (directly accessed).
Direct carrier cost calculation is called 1st carrier cost. Indirect carrier cost is calculatedexclusively from duration and is called 2nd carrier cost.
The sum of these two costs, added to ISDN service cost, gives call cost.
Note:
This feature is available only when the ARS function is used in the PCX.
4.2.6.3 Remote Trunk Group
A Call Server can use a remote Media Gateway located in a different charging area of thepublic network. Calls using trunk groups supported by this remote Media Gateway must abideby the charging area of the remote media gateway.
As of R4.2, the Alcatel-Lucent OmniVista 4760 Network Management System accountingapplication takes the trunk group used into account for cost calculation.
Figure 4.6: Example of Two Trunk Groups of the same PCX Leading to Two DifferentCharging Areas
The trunk group is a parameter of the accounting application.
Chapter 4
4-12
The used trunk group identification is included in the charging ticket.
Distributed Trunk Group
A trunk group can be distributed on several Media Gateways. But these Media Gateways mustbe located in the same charging area. A given trunk group cannot be distributed on differentcharging areas.
4.2.6.4 Multi Timezone
Large networks can be deployed over several timezones. As of R5.0, accounting ticketstransferred from the Alcatel-Lucent OmniPCX Enterprise CS include the local timezone of theuser. This data, called , is taken into account for call cost calculation.
Restrictions
VoIP tickets and performance counters do not take into account the multi timezone feature.
The Alcatel-Lucent OmniPCX Enterprise CS must be in R9.0 or higher, to provide ticketsincluding a field.
Filters, used for reports, do not take into account the time zone. Filtering operations are alwaysperformed with the Com Server system date/time.
4.2.7 Accounting with the OmniPCX Office
4.2.7.1 Special Features
The OmniPCX Office have the following special features:
- The loading of files (PCX to PC) containing accounting records is followed by deletion fromthe hard drive of the PCX. For this reason, for an external accounting application, use theaccounting files stored in the PC 4760 server directory (4760\data\collector) (see moduleAccounting - Overview § Collecting Records ).
- By default, records are downloaded with the number of the set, date/time and numbercalled. The PCX must be configured to transmit the User name in the record.
- To guarantee accurate call accounting:• If ARS is used by the PCX, Carrier data is included in the record (ticket). An indirect
carrier code must therefore be configured in the Carrier tab.• If the PCX uses carrier-dedicated trunks, carrier ID must be configured in the Carrier
tab at Trunk group connection level.
4.2.7.2 Managing OmniPCX Office Cost Centers
The cost centers of these PCXs can be fully managed in the accounting organization.
After initial synchronization, chargeable entries are displayed under a single identical costcenter. Sets can be moved from one cost center to another.
- By Copy/Paste1. Select the sets to be moved, then the Copy command.
The set from the old center and its records are made historical.2. Select the new cost center object and use the Paste command.
The same set is created in the new cost center with the corresponding new records.
- By Cut/Paste
4-13
1. Select the sets to be moved, then the Cut command.2. Select the new cost center object and use the Paste command.
The set and its records are displayed in the new cost center.
Caution:
Total counters are not calculated immediately, they are calculated at the next scheduled task of
total counter calculation.
Total counters can also be calculated immediately with the Recalculate total counters command
(see: module Accounting - Parameters tab § Recalculating Total Counters Manually ).
When generating accounting reports, use the Cost center field. Some (or all) entries in theOrganization can then be accurately filtered.
4.2.7.3 OmniPCX Office Operating in Multi-Company Mode with ARS
Two identical carriers can be configured, provided that:
- Carrier data is different for the two carriers.
- Trunk group connections (external accesses) are different.
The carrier is identified by the Trunk group identity, contained in records.The following example describes the configuration operations to be performed on theAlcatel-Lucent OmniVista 4760 Network Management System .
On the OmniPCX Office side:
- Company A: Trunk group 0, carrier info F
- Company B: Trunk group 0, info carrier L. Trunk group management (objet: External Lines)is interpreted as follows:For R1.1.30.04 or higher:• Trunk group 0, access ID: N001 —> Information record: 001• Trunk group 4, access ID: N002 —> Information record: 002For releases lower than R1.1.30.04:• Trunk group 0, access ID: N001 —> Information record: 000• Trunk group 4, access ID: N002 —> Information record: 001
On the 4760 side:Carriers tab:
- In the Carriers section:Specify FT1 and FT2 with, as type, direct
- In the Indirect Carrier Code section:In the OmniPCX Office subnet, specify the entry FT1 with, as code: FIn the OmniPCX Office subnet, specify the entry FT2 with, as code: L
- In the Trunk Group Connection section, assign each PCX trunk group to a carrier:For OmniPCX Office PCXs, assign trunk group 000 to carrier FT1For OmniPCX Office PCXs, assign trunk group 001 to carrier FT2
4.3 Organization tab
Chapter 4
4-14
4.3.1 Overview
This tab is dedicated to the supervision of charged entries: user, attendant, directory entry, etc.
The organization graphical interface consists of:
- The tree structure of chargeable entries.
- An editable area consisting of 6 tabs: Properties, Records, Masks, Costs, Tracking*, andTracking Status*, updated according to the entry currently selected in the tree structure.
Note:* Options available depending on the license installed.
Tree structureThe accounting tree structure gives an overview of the current and past Organization.Accounting and traffic analysis reports can be generated on an active or inactive entry in theOrganization from the Reports application
Properties and recordsYou can view the properties of each entry as well as the content of the last accounting recordsreceived from the PCX.
MasksTo ensure data remains confidential, you can apply a masking profile to entries that hides datain the accounting reports.A mask can be apply to the tree structure according to user's rights.
CostsCosts allow specific cost adjustment coefficients (variables) to be associated with entries.Adjustments are applied when reports are generated.
Tracking and Tracking statusThis optional module, for accounting, traffic analysis, and VoIP traffic analysis, is used to trackthresholds exceeded and fluctuations in costs, duration, number of calls, and quantities. Theuse of DISA (Direct Inward System Access) can also be tracked.
4.3.1.1 Dynamic Icons
These are located in the upper left part of the accounting graphical interface and can only beviewed when the Organization tab is displayed. A detailed description is provided below.
table 4.4: Dynamic IconsIcons Description
Access to masking profile configuration.
Refreshes (updates) organization display
Selected - disables display of active items in thetree structure only
Access to call cost profile configuration.
4-15
Icons Description
Access to tracking profile configuration.
Access to the "assign tracking profiles by family(type of entry)" interface.
4.3.1.2 Updating the Organization
The complete and detailed description of the Organization is managed in a database and isupdated following:
- Notification sent by the System or Company directories.
- Processing of an accounting or administration record.
- A manual operation in the Organization.
4.3.1.3 Directory Notifications
Directory notifications concern modifications performed:
- either, by a manual operation carried out in the Directory application,
- or, automatically during synchronizations with the PCX.
These notifications are dynamically included by Accounting and its database. They include:
- Creation of an entry that did not previously exist.
- Deactivation of an entry and creation of another entry if a major change is made(modification of name, first name, or cost center).
- Update of an entry if a minor change is made (for example, change of E-mail or address).
Active/Inactive: Switching between the two modes is performed either automatically followinga synchronization with the PCX or manually following a Copy/Paste operation.
Example 1:
1
When first launching the Alcatel-Lucent OmniVista 4760 Network Management System, if aPCX is declared:
1. The Directory recovers objects configured in the PCX.
2. The Directory notifies Accounting that these objects exist.
3. Accounting creates the entries in its internal database and updates the Organization byplacing the items under the appropriate cost centers.
Example 2:
2
Via the Alcatel-Lucent OmniVista 4760 Network Management System directory, a user isassigned to another cost center:
1. The original user switches to inactive mode.
2. A user is created under the relevant new cost center. This cost center is also created, ifrequired.
Chapter 4
4-16
Example 3:
3
A trunk group is deleted in the PCX.
The trunk group is disabled in the Accounting database.
Note:
The modification of the attributes FirstName (extended format) and Name (extended format) in the
System Directory, only updates the directory data and does not deactivate the concerned object.
4.3.1.4 Accounting Records (Tickets)
The loading of accounting records allows the record to be associated with a chargeable entryof the Organization and call cost to be calculated.The correspondence is made using the telephone number of the calling party and his hostPCX. If there is no corresponding entry, an undefined entry is created and the record classedin this entry. See § Undefined Record Entities .Accounting records do not allow configuration changes to be detected.
“Project” accounting records are processed in the same way as standard accounting recordsand then linked to a project entry. If this association fails, an inactive project entry is placed inthe tree.
4.3.1.5 Traffic Analysis Counters
The processing of these counters is similar to that of accounting records (tickets). Eachcounter or group of counters is associated with a set (user, attendant, etc.).
Exception: If the counter/entry association fails, no item is created in the tree and the counteris not included.
4.3.2 Tree Structure
The root of the tree structure is the Meta company (parent company) (by default, NMC).Under this root, there is a structured organization based on cost centers and/or levels.
Cost centers come from the System directory.
The management mode for cost center Names is selected during Alcatel-Lucent OmniVista4760 Network Management System server installation:
- Either, cost center names are automatically retrieved with those of the PCX (for theOmniPCX 4400 and Alcatel-Lucent OmniPCX Enterprise CS) at synchronization.
- Or, their names are manually entered in the Company directory.
Whatever the mode used:
- The Organization consists of cost centers and the chargeable entries are automaticallyplaced below them.
- Before performing the first synchronization, you can customize the Organization bycreating levels (department, building, etc.).
- Once in use, synchronization mode cannot be changed subsequently.
If no cost center is identified, PCX entries are directly placed under the root of theOrganization. In all cases, you can customize the Organization by manually adding local
4-17
levels above cost centers.
In an RSC context, the cost center names must be unique among the different RSC customersso that the chargeable entities of the different RSC customers are placed in their respectivecost centers. If the cost center names are automatically retrieved from the PCX, themanagement of cost center names has to be done in the PCX.
Prolonged use of the tree structure may result in an inaccurate display. To refresh and updatethe tree structure display, click .
4.3.2.1 Tree Structure Components
The organization contains the following items:
table 4.5: Tree Structure ComponentsIcons Description
Users
Attendant
Attendant group
Station group
Voice mail (VM)
Data Terminal
Trunk Group
Link
Undefined Entity
Level
Cost center
Directory entry
Project Code
Chapter 4
4-18
Icons Description
Level (for undefined record entities)
Level for global accounting per node
Pilot
StatisticPilot
The chargeable entries are placed under the cost centers and correspond to the objectsretrieved by the PCX and record generators:
- Users
- Attendants
- Data terminals
Chargeable entries from PCXs that are not associated with cost centers, are placed on thesame level as cost centers:
- Attendant groups
- Station groups
- Projects
- Voice mail
- Trunk groups
- Links
Each accounting record received is associated with a chargeable entry of the organization thathas adjustable cost, masking, and tracking properties. It is correctly assigned by using dataretrieved from the record.
If there is a failure, a series of searches is launched on the other data provided in theaccounting record. Refer to § Undefined Record Entities .
Placed at the root, the Global accounting by node level groups data for PCXs with the globalaccounting mode enabled. See § Global Accounting per Node Level .
Note:
In an RSC context, the project names must be unique among the different RSC customers so that the
costs of different RSC customers are placed in their respective projects. Management of project names is
done in the PCX.
4.3.2.2 Undefined Record Entities
These are created, then placed under the level when an accounting record cannot be
associated with an entry shown in the organization tree structure. This usually results from:
- either an offset between synchronizations (partial or total) with the PCXs and loading of
4-19
accounting records,
- or an incorrect or incomplete record generated by the PCX (system restart, switchover tobackup mode, etc.).
In the case of an offset, the next synchronization ensures correct assignment of the record tothe chargeable entry.
In the case of an incorrect record, a manual operation must be performed.
An Undefined Entity is always inactive and has the phone number and PCX propertiesprovided by the record that initially created it. It may have several accounting records assignedto it.
4.3.2.3 Local Levels
Local levels are used to:
- Make the organization easier to read and use.
- Set up a tree structure entirely dedicated to accounting that does not resemble thedirectory tree structure.
- Establish tree structure display restrictions according to access level. See § RestrictingAccess to Organization Data .
The number of items grouped under a branch of the organization is displayed betweenbrackets.
Figure 4.7: >Tree structure for accounting
Various types of levels are offered:
- Local level - manual creation: A local level does not have any specific properties and canbe created indiscriminately under:• The root directory with the default name: nmc.• Another local level.
This level is only recognized and included in the Accounting application. These levels haveno matching level in either the directory or the PCX configuration.
Levels are automatically activated or deactivated under the following conditions:
- A level is active if it has at least one active station.
- A level is inactive if it does not have any active stations.
- NMC level: This is the highest level. It represents the accounting root and cannot bemoved or deleted. It is always active.
- Undefined level: This special level is located at the root. It receives undefined entities and
Chapter 4
4-20
has the following features:• It cannot be created manually.• It may contain directories that were created manually.• It cannot be deleted or removed.• Its name can be modified.• You can apply profiles in it.
Restrictions on a local levelTwo levels located at the same position in the tree structure cannot have the same name.
4.3.2.4 Cost Centers
This concerns both local level and chargeable entries. A cost center is always located justabove one or more chargeable entries. It is:
- either, automatically managed by synchronization with the PCXs.
- or, manually updated.
In the same way as for local levels, the cost center can be used to restrict access to part of thetree structure (items and associated data). See § Restricting Access to Organization Data .
4.3.2.5 Global Accounting per Node Level
Placed at the root, this level is created at installation with an inactive status. It cannot becreated, moved, or deleted.In this level, global entities by node are coded with a generic name label (*****-) preceding thePCX identifier. (E.g. *****-1000602 where network number = 1 and PCX network number =602).A single global entity is created by node.After each loading operation, records from a PCX identified at this level are associated with itsgeneric name.
The Reports application has a basic Type field (in the Query tool organization file) acceptinguser, attendant, global entity, undefined entity, etc. as filters. You can thus create reportstargeting a specific level of the organization.
4.3.2.6 Chargeable Entries (Excluding Cost Centers)
All chargeable entries are managed (created, moved, deleted, deactivated) automatically viasynchronization with the System directory. They are the final items of the tree.
A final item can be located under:
- The root
- A local level
- A cost center
- A directory unit
A final item is characterized, at minimum, by:
- A network number
- A subnet number
- A PCX number (except for single projects per company)
4-21
- A station or project or trunk group number (or a name for links)
Chargeable items are as follows:
User: telephone station.
Station Group: final item linked to a set of users via a telephone connection.
Attendant: special telephone station.
Attendant Group: final item linked to a set of attendants via a telephone connection.
Trunk Group: a set of PCX trunks. It is characterized by a trunk group number preceded by F,then a code for trunk group type:
- S for a single trunk group,
- C for a compressed trunk group,
- P for an incoming trunk group with precedence.
Voice Mail: groups voice mail calls.
Data Terminal: specific station allowing data to be sent. UA type stations fitted with a TA(Terminal Adapter) interface are considered and shown as Users with the Associated dataterminal attribute validated (if the terminal is detected second). When the station is detectedsecond, the terminal is historized and the user created.
Project: a call made by a user can also be assigned to a project by means of a special code.As a result, accounting records are associated with this type of entry. A project ischaracterized by its number and is unique within a company.
Link: represents an ABC link between PCXs. It is only characterized by a name.
Undefined Ticket Entity: an entry created following reception of an accounting record thatcannot be associated with a chargeable entry of the organization. See § Undefined RecordEntities .
4.3.3 Restricting Access to Organization Data
See module Security - Overview § Restricting access to organization data.
4.3.4 Managing Organization Items
Five main actions can be performed in the Organization tree:
- § Filtering
- § Creating
- § Deleting
- § Cutting and Pasting
- § Copying and Pasting
- § Open All
- § Backdating
These action are accessed by right-clicking the chargeable entry concerned (for “Edit”, see §Editing ).
The values of non-modifiable fields are shown in italics.
Chapter 4
4-22
4.3.4.1 Filtering
The shortcut menu Filter command allows a search to be run and the results of this search tobe displayed in the Organization tree:
1. Select an active entry in the tree.
2. Select the Filter command from the shortcut menu. A search window is displayed.
3. Complete the items and run the search. After a few moments, the result is displayed in thetree.
4.3.4.2 Creating
Only local levels and cost centers can be created. They are identified by a name.To create a level:
1. Click the appropriate parent location.
2. Select the Create > Local level or Create > Cost center command from the shortcutmenu. A partially-completed form is shown in the main window.
3. Enter the desired name and confirm.
The following characters must NOT be used: *, “,=,,,/,\,%,_ (underscore).
4.3.4.3 Deleting
Deleting an active item results in the associated records and counters being deleted.To delete a level:
1. Click the level to select it.
2. Select the Delete command from the shortcut menu. A confirmation dialog box isdisplayed.
3. Confirm. Any entries grouped under the level and their associated records and the trafficanalysis counters are deleted from the organization and the database.
4.3.4.4 Assigning a Cost Center to Chargeable Entries
As a general rule, cost center is provided by the PCX for chargeable entries. This is the casefor:
- OmniPCX Office and Alcatel Office sets.
- or OmniPCX 4400 and Alcatel-Lucent OmniPCX Enterprise CS sets.
The cost center is managed at PCX level, or, if there is one, at Directory level. Modificationscannot be made in the Organization tab.
There are other chargeable entries that can be directly managed in the Organization tab.These are chargeable entries for which the PCX does not supply cost center information. Thisis the case for:
- All Alcatel Office chargeable entries.
- All OmniPCX Office chargeable entries.
- Attendant groups, set groups, voice mail, trunk groups and logical links.
For this type of entries, a cost center may be assigned in two ways:
- In the System Directory, by completing the Default cost center attribute in data
4-23
collection.
- By "Cut/Paste" or "Copy/Paste" operations when chargeable entries are placed in a costcenter or the root.
Warning:Performing move operations using Cut/Paste is not recommended when purgeoperations have started (at three-month intervals by default).This is due to the fact that recalculation of daily total counters only covers recordscurrently stored in the database.When a set is moved from a cost center (CC1) to another cost center (CC2):- The total counters for records in the database are transferred to cost center CC2- However, the total counters for purged records remain in CC1Thus, the total reports:- Still show the old CC1 records for the set, even though it is now in CC2- Are not complete for cost center CC2, as the period preceding the purge is missing
4.3.4.5 Moving Cost Centers between Levels
4.3.4.5.1 Cutting and Pasting
This operation consists in moving a branch (cost center, local level) to another local level. Thebranch moved inherits profiles (mask, cost) from its new position, except for entries thatalready have a specific profile (this profile is kept).
Figure 4.8: Moving a Branch between Different Local Levels
Remark:
If the cost center moved was initially under a local level, this local level is rendered inactive.
An inactive item cannot be copied.
4.3.4.5.2 Copying and Pasting
This operation consists in copying a branch (cost center, local level) and pasting it into anotherlocal level of the organization. When the operation is complete, the branch initially copiedbecomes inactive (historical) and conserves the records (tickets) assigned to it. The copy iscreated with no records.
4.3.4.6 Open All
The Open all shortcut command is used to expand the branches of the Organization tree.To develop a level:
Chapter 4
4-24
1. Click the level to select it.
2. Select the Open all command from the shortcut menu.
3. All entries grouped under the selected level are displayed in the Organization tree.
4.3.4.7 Backdating
When a set's cost center has changed, the ”Assign earlier date to creation” operationconsists in backdating this assignation to apply if on the effective date.
Figure 4.9: Backdating Cost Center Configuration
T1: Administrative assignment T2: Update by notifying the System directories.
Set A is assigned to Cost Center CC1. Starting from September 1st, set A is administrativelyassigned to Cost Center CC2. However, the update is only performed on the PCX onSeptember 10th. Accounting records for the period from 1st to 9th September are assigned toCC1.
To assign these records correctly to CC2, the copied set, located under CC2, must bebackdated by assigning September 1st as its date of creation.To assign all records of inactive set A to the new active set A, assign the date of creation ofinactive set A to the new set A.
To modify the creation date of a chargeable entry:
- Select the desired active entry (set or directory entry).
- Select the Assign Earlier Date to Creation command from the shortcut menu. TheAssign Earlier Date to Creation dialog box is displayed.
- Enter the new date and time of creation to be assigned to the selected entry and confirm.The date entered must obey two constraints:• Be anterior to (before) the date of creation of the active set.• If the same set has been successively made historical, be posterior to (after) the date
of creation of the last inactive set.
Note:
For performing the global backdating process and managing all the entities of a PCX newly put in ser-
vice, refer to the Installation manual (see the Server post-installation section of the Alcatel-Lucent Omni-
Vista 4760 Network Management System Installation manual) and the tool ToolsOmniVista.exe.
4.3.5 History Criteria
History is characterized by a set that is switched from active mode to inactive mode. Eachtype of entry in the Organization has specific historical criteria linked with the Intrinsic
4-25
properties of the entry. Modifying any one of these properties results in making the entryhistorical.
Chargeable entries are no longer valid following:
- A major modification.
- A manual move operation (cut/paste).
Inactive entries are shaded in the Organization tree structure.
Figure 4.10: Organization Tree Structure
An undefined entity is always inactive.
A level (cost center, directory entry, local level, etc.) is deactivated if all the entries groupedunder this level are inactive. This level is activated if one of the entries becomes active. As aresult, if you create a local level, it is inactive because it is empty. Copying active sets underthis level activates it.
To only display active entries in the Organization, click .
Note:
The modification of the attributes FirstName (extended format) and Name (extended format) in the
System Directory, only updates the directory data and does not deactivate the concerned object.
4.3.6 Entry Properties
Select an item in the tree to view its corresponding properties on the 6 tabs in the edit area:
- Properties
- Records
- Masks
- Costs
- Tracking
- Tracking status
4.3.6.1 Editing
To view the basic properties of the item currently selected in the tree structure:
- Click the Properties tab.
Chapter 4
4-26
The list of attributes varies according to the type of item selected in the organization.
Example:
The type of set for a user, the trunk group number for a trunk group or the group number for an attendant.
The names of the following items can be modified:
- Company (the root of the tree structure).
- Local levels
- Business code numbers
Addresses and E-mail can be modified for all items except Directory entries (sets orpeople). Any other parameter is displayed in read-only mode.
To modify parameters, use the Directory application (see the module Directory - Company tab).The attributes FirstName (extended format) and Name (extended format) are used to storethe long strings (upto 42 bytes) or UTF8 strings (e.g. Chinese or Russian characters). You canmodify these attributes by changing the associated instance in the PCX (if available) or theassociated entry in the System Directory.
4.3.6.2 Viewing the Last Accounting Records Received
To view the content of the last records received for the entry currently selected in the treestructure:
- Click the Records tab.
Data displayed in columns can be masked:
- Start date and time of call
- Called number
- Call duration in seconds
- etc.
For a final item in the tree structure (for example: a user), the last records assigned to this itemare displayed.
For an intermediate item (for example: a cost center), the last records received by all thechargeable entries located under this item are displayed.
At the bottom of the edit area, the number of records displayed is shown.To modify this number:
1. Click Modify the number required... A dialog box is displayed.
2. Enter the number of records you want to view in the edit area.
3. Click OK to confirm.
4.3.6.3 Viewing Counters - Tracking Status (Optional)
For each entry, you can view the current state of counters via the Tracking Status tab.
These counters are updated when accounting records are loaded and recalculated when:
- An entry has been converted to a set. If the tracking profile was assigned by family, it maybe obsolete after conversion.
4-27
- A set is moved under a person.
- A record is reassigned to a person (following an LDIF import for example).
- A set is moved by a cut and paste operation. The new position inherits records from the oldposition.
- Set creation is backdated.
The following counters (daily and monthly) can be displayed:
- Cost, duration, number of calls for incoming calls
- Cost, duration, number of calls for outgoing calls
- Cost, duration, number of calls for incoming DISA calls
- Cost, duration, number of calls for outgoing DISA calls
- Cost, duration, number of calls for subscriptions
- Cost, duration, number of calls for incoming and outgoing calls
- Cost, duration, number of calls for outgoing private calls
Daily counters are listed on the left, monthly counters on the right.
The counters are represented by orange progress bars.
When a monitoring profile is applied to an entry (via the Tracking tab), thresholds arerepresented by red triangles.
To view the status of the counters according to a specific date:
- Select the appropriate date in the corresponding list areas.
You cannot display daily and monthly counters for which accounting records were not loadedcorrectly.
See § Managing Tracking Profiles .
4.3.7 Profiles
Alcatel-Lucent OmniVista 4760 Network Management System has a dedicated interface formanagement of each type of profile: masking, costs, and tracking. See the following sections.
4.3.7.1 Managing Masking, Cost, and Tracking Profiles.
The tracking, cost, and masking profile management interfaces are accessed via the toolbaricons. These icons are displayed when you select the Organization tab.
table 4.6: Organization IconsIcons Description of the Interface
Masking profile to ensure call data confidentiality.
Cost profile for call cost mark up/down.
Tracking profile to track operation.
Chapter 4
4-28
Icons Description of the Interface
Default tracking profile to assign default trackingaccording to type of entry.
Profiles allow preferences to be grouped in order to avoid having to make identical andrepetitive setting operations.
A default profile is always available.
A profile is assigned when configuring Organization entries (see § Applying Profiles ).
4.3.7.2 Applying Profiles
The same profile can be applied to several entries at the same time. The same entry can onlyhave one cost profile and one tracking profile at a time.
A cost, masking or tracking profile is applied to an Organization entry. The tracking profile canbe extensively used as it can also be applied to a carrier or a direction.
4.3.7.3 Inherited Profiles
Masking and cost profilesBy default, an entry inherits from its parent (i.e. the entry to which it is linked): if you assign aprofile to a cost center, all the stations located under the cost center inherit the same profile.
You can also delete this inheritance and assign a specific profile to one of the stations:
1. In the bottom Costs tab, deselect the Inherited profile option.
2. From the list located to the right of the option, select the profile to be applied.
3. Click Apply to accept changes.
You can reset all the profiles assigned under a branch and restore the inheritance:
1. Select the appropriate level in the tree structure.
2. Select the Refresh command from the shortcut menu of the edit area. The profile specifiedin the selected level is automatically assigned to the entries located under its branch.
Tracking profilesUnlike masking and cost profiles:
- The "inheritance" concept (hierarchy in the tree) is not used.
- A tracking profile can also be applied to a Carrier or a Direction.
By default, an entry (user, cost center, etc.) takes the profile of its entity. However, you canassign a specific tracking profile to it and then restore the default inheritance again.
Respective assignment per chargeable entry type is performed via the Default trackingprofile manager. See § Assigning Default Tracking Profiles .
4.3.8 Managing Mask Profiles
4.3.8.1 Masked Data
Masks ensure the confidentiality of accounting record data when:
- Reports are generated.
4-29
- The last records for a set are viewed via the bottom Records tab.
The following record data may be masked:
- Called number
- Caller number
- PIN (Personal Identification Number)
- Cost (PCX cost, ISDN service cost, etc.)
- Destination area (City/Country name)
- Call duration
- Call date
4.3.8.2 Masking Characteristics
Digital fields can be partially or totally masked. Other fields are completely masked.
Masking can vary according to the type of call:
- Personal - use of a PIN
- Project
- Professional – applies to incoming, outgoing, and network calls
- Guest – applies to calls made by a Guest type organization entry
Masked data is not deleted from the database. In reports, it is replaced by masking characters,see § Masking Characters . As a result, if you apply to, or remove masking from, an entry, youobtain, alternately, masked and unmasked reports.
With 4-digit masking, the following report is obtained:
table 4.7: 4–digit MaskingBefore Masking After Masking
1234567890 123456****
3615 ****
You can configure a minimum number of digits to be displayed. As a result, for 6-digit maskingwith a minimum number of 4, the following report is obtained:
table 4.8: 6–Digit MaskingBefore Masking After Masking
1234567890 1234******
3615 3615
Masking can also be configured on the PCX. The PCX then generates records containingtruncated numbers replaced by the character "_".
There are two management profiles:
- The default masking management profile.
- An additional masking management profile, that can only be accessed by theadministrator. This additional profile is used to view the data with fewer maskedcharacters.
Chapter 4
4-30
table 4.9: Administrator Masking ProfileDefault Masking
ProfileAdministrator Masking
Profile
123456**** 12345678**
4.3.8.3 Masking Characters
Masking features are as follows:
- The length of the masked data is respected.
- Figures (cost and duration) are replaced by “0”.
- Dates are replaced with spaces.
- Phone digits are replaced with “*”.
- Character strings are replaced by a series of “____” (underscores).
4.3.8.4 Important Concepts for Grouped and Total Reports
At installation, a default masking profile is applied to the organization root. This profile cannotbe renamed or deleted. Howewer, you can reset masked digit to 0 to render it inactive. Thisprofile has two additional call categories: masked and unmasked group used systematicallyfor grouped reports.
Masking may be Not applicableto Total reportssince these do not include organizationstatus.
4.3.8.5 Creating a Mask Profile
To access Management - Mask Profiles:
- Click the icon in the menu bar.
Figure 4.11: Management — Mask Profiles Window
4-31
The manager has:
- On the left side, a box listing all configured profiles.
- On the right side, the detailed content of the profile currently selected.
Originally, the manager has the Default profile.
The profile management interface has the following icons:
table 4.10: Management — Mask Profile IconsIcons Function
Create a profile
Copy a profile
Modify profile name
Delete a profile
To create a profile:
1. Click . The Creation window is displayed.
2. Enter the name of the profile, then confirm. The name is added to the list.
3. Configure masking rules as follows:• click +, a line is added to the table,• configure masking settings for each class of call (personal, project, normal, guest)• configure the masking settings you want to assign to the various digital data.To mask City, Duration, or PIN type, select the corresponding option.Both the Initial Number and Displayed Number boxes present in the area at the bottomof the window give an overview of the masking currently configured in the table.The sign is displayed at the start of each new line.
4. Click Apply to accept changes.To modify a profile:
1. Select the appropriate profile from the list.
2. Click directly the entries to be modified and update them. The sign is displayed at thestart of each modified line.
3. Click Apply to accept changes.To remove masking applied to a call type:
1. Select the line containing the masking to be deleted by clicking at the start of the line.
2. Click -. The sign is displayed at the start of each deleted line.
3. Click Apply to accept changes.
4.3.8.6 Unmasking Report Data
Chapter 4
4-32
The data displayed in the bottom Records tab is not affected by the profile unmasking rules.Only reports are affected via the report generation commands available from the shortcutmenu: Generate report w/o mask.Use of this feature is reserved to members of the Access masked data group that isconfigured in Company directory > CompanyName > Administration > Groups.Assigning users to this group configures all passwords required when unmasked reports aregenerated.By default this group includes no members.Unmasking can be indirectly accessed by users with Accounting write rights. By modifyingmasking profile properties, all data can be displayed.
4.3.8.7 Applying a Mask to an Entry
A profile can be assigned to different entries in the Accounting Organization.
By default, an entry inherits from its parent (i.e. the item to which it is linked). As a result, if youassign a profile to a cost center, all the sets located under that cost center inherit the samemasking profile.
You can delete this inheritance and assign a specific profile to the desired set: You can alsoreset the profiles assigned under a branch and restore the inheritance with the Resetcommand from the shortcut menu.To mask the call data of an entry:
1. Click the appropriate entry.
2. Click the Masks tab at the bottom of the window.
3. Deselect the Inherited profile option.
4. To the right of the option, select the tracking profile to be applied from the list.The item is masked and the features configured in the selected profile are displayed in thetable.
5. Accept your changes.
Caution:
There are no mask profiles for business numbers located in the organization tree structure. These
specific masks are applicable at the level of stations or directory entries (and/or cost center, local
level) of the organization that are liable to dial these project code numbers.
4.3.9 Managing Cost Profiles
You can assign specific costs to all entries in the tree structure. These costs are adjustmentsfor call cost based on the carrier.
4.3.9.1 Creating a Cost Profile
To access Cost Profile - Manager:
- Click the icon in the menu bar. The Manager window is displayed.
The graphical interface of the Manager consists of three different parts. These are, from left toright:
- A list containing configured profiles.
4-33
- A table of valid periods.
- A table of charged costs and extension and service subscriptions.
Figure 4.12: Cost profile — Manager Window
By default, the list has the Default cost profile.
table 4.11: Cost Profile — Manager IconsIcons Function
Create a profile
Copy a profile
Modify profile name
Delete a profile
To create a cost profile:
1. Click . A dialog box is displayed.
2. Enter the name of the profile, then confirm. The name is added to the list.
3. Specify the validity period as follows.• Click the + icon, a line is displayed.• Enter a validity start and a validity end date in dd/mm/yyyy format.
4. Fore each type of call, cost, and set (depending on the tabs), enter or select the parameterin the drop-down menu.
Chapter 4
4-34
5. Apply your changes.
Each valid period can include specific details in terms of:
- Cost charged per call type.
- Extension subscription made available.
- Subscription to services offered.
Modifications made to periods are applied when you click Apply.
4.3.9.2 Charged Cost (before Tax)
Difference between the percentage and the linear equation
Where x = cost of accounting records (basic cost)
A = value to be entered
B = value to be entered (only available for linear equations)
Fort each call type, cost adjustment may consist in (as appropriate):
- Adding a percentage, for example 10% (in this case A=10),
- Adding a fee, for example 1 Dollar (in this case B =1).
Percentage:
Individual cost = x + A/100 x
With A= 10 and x = 50, an individual cost of 55 is obtained
Linear equation:
Individual cost = Ax + B
With A= 2, B=1 and x = 50, an individual cost of 101 is obtained, that is 2 x 50 + 1
Note:
VAT does not apply to value B.
Apply your modifications.
Caution:
There are no cost profiles for project code numbers in the organization tree structure. These spe-
cific cost profiles are applicable at the level of stations or directory entries (and/or cost center,
local level) of the organization that are liable to dial these business code numbers.
4.3.9.3 Cost of Subscriptions (Station, Service)
Important note: Because station and voice mail characteristics are stored on the PCX, aninitial synchronization must be performed before configuring subscription costs per stationtype.
4.3.9.3.1 Configuring
A subscription cost profile consists of:
- A standard subscription.
- And/Or a voice mail subscription*.
- And/Or a DID line subscription*.
4-35
- And/Or subscription according to the type of set*.
Note:
(*) : For the OmniPCX 4400 and Alcatel-Lucent OmniPCX Enterprise CS only.
In addition, for each subscription, the following are specified:
- Frequency (daily, weekly or monthly).
- The currency in which cost is expressed.
- The value-added tax.
- Valid duration.
Example:The following subscription cost profile has been configured for a hotel whose guests stay forseveral days:
table 4.12: Cost Profile ExamplesFrom the 01/01/04 to the30/04/04
Station 4020=1 $ per dayStation 4035=2 $ per dayVoice mail = 1.2 $ per day with a tax of5.5%
From the 01/06/04 to the30/06/04
DID line =3 $ per monthStation 4035=2 $ per month
From the 01/07/04 to the31/07/04
DID line = 1.3 $ per month
The cost of a subscription is calculated according to frequency, duration, and validity. Inaddition, periods must be homogeneous. For a profile valid from 1/1/2000 to 1/1/2004 with astandard subscription that is charged monthly, other subscription costs must also beconfigured for monthly charging.A subscription from the 1st of January to the 31st March can be specified, but not from the10th January to the 12th March. Thus, a hotel manager wanting to increase subscriptions forthe high season (15th June to the 15th August) is constrained to maintain a monthly frequencyor switch to weekly subscriptions.
4.3.9.3.2 Managing Subscription Costs
Accounting records including only subscription costs are generated. They are then processedin the same way as other records generated by the PCX. As a result, subscription charging isperformed after each synchronization.
Subscription records are created at the start of the period:
- Every day for daily records.
- Every Sunday for weekly records.
- On the first day of the month for monthly records.
Time fields are set to 00:00:00 in each record.
The subscription cost calculation never processes the current day.
Subscription record processing may take several days. During this time, the subscription costcalculation cannot be run.
Chapter 4
4-36
With a monthly subscription, users arriving in the current month will only be charged from thefirst of the following month.
Note:
- Users from the OmniPCX Office do not have voice mail or a station, only a standard subscription ismanaged.
- Subscription records can be cleaned either during accounting cleaning or by a specific manualcleanup operation.
4.3.9.3.3 Integrating Subscriptions into Reports
Subscription periods must be determined with regard to the interval at which reports aregenerated.Subscriptions are configured on non-sliding periods. This means that any month (or week orday) started is due.
The Report application has specific fields for subscriptions.
4.3.9.4 Assigning a Cost to an Entry
As for masks, if you assign a profile to a set, the calculated costs for the set include the profilefeatures.To assign a cost to an entry:
1. Click the appropriate entry.
2. Click the Costs tab.
3. Deselect the Inherit profile option.
4. Select the cost profile to be applied from the list. The characteristics configured in theselected profile are displayed in the table.
5. Accept your changes.
4.3.10 Managing Tracking Profiles
Tracking consists in configuring tracking thresholds grouped in a profile and applying themeither to one or more Organization entries, or to a type of entry. Only a single tracking profilecan be applied to a tree structure item.
4.3.10.1 Tracked Data Code
Accounting, Traffic analysis*, and VoIP traffic analysis* data (managed by the Defaulttracking profile manager) can be tracked.
For each item of data tracked, there is:
- A list of applicable periods (half-hourly, daily, monthly, total).
- A default threshold.
- A list of possible call types (for Accounting and Traffic analysis).
- An action (option): send an alarm and/or E-mail.
Note 1:
(*) : Options available only on the OmniPCX 4400 and Alcatel-Lucent OmniPCX Enterprise CS (and de-
4-37
pending on the licenses installed).
table 4.13: Tracked DataTracked Data Tracking
PeriodDefault
ThresholdCall Type Action
(Option)
Accounting
Cost D/M/Y (1) 100 Standard list (2)
Duration D/M/Y (1) 20:00:00 Standard list (2)
Number of calls D/M/Y (1) 100 Standard list (2)
Cost variation D/M/Y (1) 10 Standard list (2)
Duration variation D/M/Y (1) 10 Standard list (2)
Number of calls variation D/M/Y (1) 10 Standard list (2)
Traffic Analysis
Rate of abandon on callednumbers
D/M/Y (1), 1/2h 10 Incoming publiccalls
Trunk group: Duration ofexceeding R1 threshold
D/M/Y (1), 1/2h 0:03:00 Inc./Out. calls
Rate of abandon on Attendantgroups
D/M/Y (1), 1/2h 5 Incoming calls Alarm/E-mail
Voice over IP
Sent volume D/M/Y (1), 1/2h 100
Received volume D/M/Y (1), 1/2h 100
Rate for Out of range records D/M/Y (1), 1/2h 15
Note 2:
(1) : D/M/Y: daily, monthly, yearly
(2) : Standard list:
- Incoming/Outgoing calls
- Incoming calls
- Outgoing calls
- Incoming calls via DISA
- Outgoing calls via DISA
- Outgoing private calls
- Subscriptions
Threshold units depend on the value tracked:
- Cost thresholds are expressed in the reference currency.
- Duration thresholds are expressed in seconds.
- Variation thresholds are expressed as a percentage.
- Volume thresholds are expressed in MB.
A profile can track several types of data according to different periods.
Chapter 4
4-38
Note 3:
For VoIP, tracking profiles can be assigned to an object class (IP-Phones, boards). However, a profile
cannot be assigned to a precise organization object (instance).
Example:
You can track station usage and, at the same time, track:
- Whether daily call costs for the extension exceed a threshold of 100.
- Whether monthly call costs for the extension exceed a threshold of 2000.
4.3.10.2 Data Variation Rate
Monthly variation for a data item (cost, duration, number of calls) is calculated by dividing thevalue of the item for the current month by the average value of the item over the last x months.Weekly and yearly variation is calculated in a similar manner.These values can be modified in the System directory: Nmc > NmcConfiguration >GlobalPreferences > Accounting > Monitoring parameters. This concerns values for daily,monthly, and yearly moving average periods.
4.3.10.3 Creating a Tracking ProfileTo access the Tracking profile manager:
1. Click the Organization tab.
2. Click . The Manager window is displayed.
The Manager contains the following icons:
table 4.14: Tracking Profile Manager IconsIcons Function
Create a profile
Copy a profile
Modify profile name
Delete a profile
To create a tracking profile:
1. Click to configure a new profile. The creation dialog box is displayed.
2. Enter profile ID name.
3. Click + to configure a new line for tracking data via:• Tracking value• Tracking period:
4-39
• Daily: Monday to Sunday from 00:00 to 24:00,• Monthly: from January to December from the first day to the last day of the month.
• Threshold: free entries.• Call Type: select according to the tracking value.• Action (option): This is the operation launched if the preset threshold is exceeded.
Possible actions are: send an alarm and/or E-mail.• E-mail: Complete this field if the selected action involves sending E-mail. Enter the
address where the message will be sent.
Note:The E-mail server address is requested at Alcatel-Lucent OmniVista 4760 Network ManagementSystem Server installation. It can however be updated in the System directory: Nmc > ServerName> Mail Server. Contact your network administrator.
4. Repeat step 3 for each new type of tracking to be added to the profile.
5. Click OK to confirm that the data entered is correct.To delete a type of tracking:
1. Select the line by clicking at the start of the line.
2. Click –. The line is deleted from the tracking table.
Example tracking profile
The Watch Cost profile transmits an alarm to the E-mail address [email protected] if oneof the following two conditions arises:
- The 10000 monthly consumption threshold for outgoing calls is exceeded.
- The daily duration of incoming calls exceeds 1hr15min.To modify a profile:
1. Select the appropriate profile from the list.
2. Click to select the parameters to be modified and update them. The sign is displayed atthe start of each modified line.
3. Click Apply to accept changes.To remove a tracking period:
1. Select the appropriate line by clicking at the start of the line.
2. Click –.The sign is displayed at the start of each deleted line.
3. Click Apply to accept changes.
4.3.10.4 Setting Up Tracking
Tracking can be set up for either:
- An entry in the Organization
- A carrier
- A direction
- A City/country name
A profile is assigned to a carrier or a direction for each individual entry.
A profile can be assigned to an entry in the Organization in two ways.
Chapter 4
4-40
4.3.10.4.1 Assignment by Organization Entry Type
See § Assigning Default Tracking Profiles .
4.3.10.4.2 Targeted Assignment
A tracking profile can be applied to a targeted entry:
1. Click the entry to which you want to apply tracking.
2. Click the bottom Tracking tab.
3. Deselect the Default Tracking option.
4. Select the desired type of tracking from the list. The characteristics configured in theselected profile are displayed in the table.
As soon as a profile has been applied to an entry, thresholds are immediately calculated and ifthresholds are exceeded, the actions configured (alarm and/or E-mail) are immediatelytriggered.
To check whether tracking thresholds have been exceeded, click the Tracking Status tab(see module Accounting - Carriers tab § Setting up Cost Tracking ).
4.3.10.5 Assigning Default Tracking Profiles
The Default tracking profile manager can be used to:
- Select the profile to be applied to a specific type of entity.This management operation avoids having to perform sorting operations in theorganization to select a type of entry and assign it a profile.
- Force assignment of profiles to types of entry in the Organization for which the profile isalready set.
Note:
The profile manager offers a different selection depending on whether you access it via the organization
tab or carriers tab displayed on the screen.
To manage default tracking of an item in the carrier configuration:
1. Select the Carrier tab.
2. Click to display the Default tracking profile manager.
Figure 4.13: Default Tracking Profile Manager WindowTo manage default tracking for other entities:
4-41
1. Select the Organization tab.
2. Click to display the Default tracking profile manager. The Manager window is
displayed. It presents a list of entries that can be managed via the tree structure such as,users, attendants, trunk groups, etc.
Figure 4.14: Default Tracking Profile Manager Window
3. Select the Profile to be linked to the desired Entity Type.The profile applies only to entities using the default profile (“Default Tracking" boxselected).
4. If you want to force assignment to all entities, select the corresponding Reset Profileoption.The “Default Tracking” box of each entity is then forced to "YES".
5. Click OK to accept changes.The threshold counters are automatically recalculated.
The Associated profile area lists the tracking profiles configured via the Tracking profilemanager.
To check or configure a profile without closing the Default tracking manager:
1.
Chapter 4
4-42
(on the right side of the Default tracking profile manager window.
Reset Profile options are deselected each time the manager is opened.
Example 1:
1
You want to associate the previously configured Control tracking profile with all the CostCenters in the organization:
1. Select Control in the Associated profile cell located opposite the Cost Centers entitytype.
2. Click Apply to accept changes.
3. Click OK to close the window.The Control tracking profile is applied to all cost centers in the organization.
Example 2:
2
You want to delete all tracking profiles applied to User and Attendant entities:
1. Select the Reset Profile options for User and Attendant entity types.
2. Leave the Associated profile box blank.
3. Click Apply.All tracking profiles applied to users and attendants are removed.
To check a tracked entry in the organization:
1. Click the entry in the tree structure to select it.
2. Click the Tracking Status tab.
4.3.10.6 Detecting Exceeded Thresholds (Scheduled or Manual)
EXPERT MODE
By default, a utility to detect exceeded thresholds is run every Saturday at 8 pm after the totalcounters have been calculated. This scheduling can be modified. The task can also be runmanually via the interface available via the Accounting/Traffic/VoIP > Detecting exceededthresholds menu. This interface, dedicated to accounting, traffic analysis, and VoIP trackeddata, has the following sections:
- Detection period (common to Accounting, Traffic analysis, and VoIP)The Since the last detection option avoids having to enter an explicit period. If you selectFixed period, you can:• Specify a start date and an end date.• Specify no date: The calculation period is limited by the dates of the oldest record and
that of the most recent record (usually the current date).• Only specify a start date: The end date is that of the most recent record in the
database.• Only specify an end date: The start date is that of the oldest record in the database.
- Counter type (common to Accounting, Traffic analysis, and VoIP)You can select half-hour, daily, monthly, or yearly.
- Tracked data code
4-43
Select the desired data by selecting or clearing the corresponding options. The Noaccounting, No traffic analysis, or No Voice over IP options disable the data for eachdomain. The options are shaded and no longer available.Accounting has an additional Call Type section and an advanced settings window (Advanced button) for variation tracking settings: time period for moving average. See §Data Variation Rate .
- If you have a tracking license, select the Notify threshold crossings option and specifythe max. number of alarms. By deselecting this option, any overflow detected duringcalculation results in no action being taken. See § Creating a Tracking Profile .
Click OK to accept your changes. The Scheduler is displayed to perform any task schedulingrequired. By default, calculation is performed immediately with two retry attempts if it fails.
4.3.11 Updating Costs in the Database
EXPERT MODE
4.3.11.1 Standard Cost Management
New accounting records are downloaded from the PCX(s) to the Alcatel-Lucent OmniVista4760 Network Management System server during each synchronization (complete or partial).Each record characterizes a call that can be incoming, outgoing, internal etc. depending on thefilters applied on the server and/or PCX.Call cost is calculated according to:
- The tariffs (rates) of the carrier used for the call.
- Any adjustment coefficients.
The cost thus calculated is assigned to the chargeable entry identified by the accountingrecord. Assignment and cost are then saved in the database. This data is used to update theTotal counters. See module Accounting - Parameters tab § Configuring Total Accounting,Traffic Analysis, and VoIP Performance Analysis Counter Calculation. .
Operations to be performed: Configure filters for record loading on the Alcatel-LucentOmniVista 4760 Network Management System and on the PCX to reduce the number ofrecords processed. Check that each synchronization is correctly performed by the schedulerand that accounting report data is consistent.
4.3.11.2 Exceptional Processing - Recalculating Costs, Counters and Subscriptions
Despite standard cost and subscription processing, data in the database may becomeobsolete in the following cases:
- A carrier's characteristics have been modified. The Carrier Cost for each recordassociated with this carrier must be recalculated.
- An adjustment or subscription profile applied to one or more entries in the organization hasbeen modified.
To update costs or subscriptions, Alcatel-Lucent OmniVista 4760 Network ManagementSystem offers a recalculation feature (that can be configured and scheduled):
- Scheduling: Recalculation can be performed at regular intervals using the Scheduler.
- Configuring: You can select the data to be recalculated by date, type of cost (carrier costsand/or variable costs), or subscriptions.
To recalculate costs or subscriptions:
Chapter 4
4-44
1. In the Carriers tab tree, click the carrier containing data to be recalculated,
2. In the menu bar (Accounting/Traffic/VoIP), select the Compute cost command. A dialogbox is displayed.
3. Configure cost recalculation by updating the fields:• From - To: Limit the number of records in the database to be recalculated in terms of
record creation date interval• Carrier Cost(s) - Variable Cost(s): Validate the types of costs to be recalculated.
Select the Carrier Cost(s) option if the changes made concern the carrier. Select theVariable Cost(s) option if an adjustment profile has been added or modified.
• Records cover (Records to include): Select the records to be included in thedatabase: All records, Loaded records, or Archived records.
• Fixed Cost(s): select this option to update subscription records if a subscription profilehas been modified.
Caution:
• Subscription recalculation is based on deletion of records followed by a new additionof subscription records. Processing time may be long, depending on the number ofrecords involved.
• If an initially active user becomes inactive and recalculation is performed, the userloses his subscriptions for the recalculated period.
• From this time on, monthly/weekly/daily subscriptions will only be calculated if theset was present at the start of the month/week/day. Sets created during the period willonly have a subscription from the start of the following period.
• Calculate total counters: Select this option if you want to update total counters.• Force cost calculation: Select this option to calculate all costs. By default, only data
related to a carrier configuration change is recalculated.
4. Confirm. The Scheduler window is displayed.
5. Using the Scheduler, you can configure immediate or delayed recalculation with afrequency value, if desired. See module Scheduler - Overview .
Note 1: Depending on the number of records affected by the cost recalculation, processingmay take some time.
Note 2: Reports generated before a carrier is modified are not updated and, as a result, mayinclude costs that are obsolete with regard to the carrier's new characteristics.
Note 3: After recalculation, the Record (Ticket) tab is not updated automatically. A new querymust be forced by changing the number of records displayed.
4.4 Parameters tab
4.4.1 Overview
Enter parameters common to all carriers before declaring any carriers.
4-45
Figure 4.15: Parameters tree
Access these parameters by clicking the Parameters tab.
Parameters are distributed throughout the tree structure under the following branches:
1. Loading.
2. Parameters common to all carriers (currencies, taxes, countries).
3. Cost comparison – to enable and disable cost comparison calculation.
4. Accounting Organization.
Note:
In each “Accounting, Traffic analysis and VoIP performance analysis IP” window, there is a second
Alarms tab to view the alarms for loading operations.
4.4.2 Configuring Record Loading
Under the Loading branch, configure the filters for data from PCXs. The filters are applied todata before it is loaded in the database.
Filter configuration has a direct impact on database updating and thus on the reports obtained.
The Loading branch is divided into three additional branches: Accounting, Traffic Analysisand Voice over IP.
Note:
The attributes in grayed (shaded) italics cannot be modified.
4.4.2.1 Accounting
Chapter 4
4-46
To configure accounting record loading: Access the Loading > Accounting branch. Theeditable area offers a dedicated interface for selective filter activation. By default, no filter isactivated.
To apply restrictive filters, use the list of options. Accounting record filtering can be performedaccording to:
- Duration thresholds (in seconds)
- Cost thresholds
- Call type
- Node (PCX)
Figure 4.16: Selective Filter Activation Window
Note:
Selecting an option means that you confirm downloading the type of data selected.
Filtering records according to a thresholdCall duration (sec)
This attribute is displayed in a list. Scroll down the list to select the type of comparison youdesire:
- Duration (sec) must be >=
- Duration (sec) must be >
This threshold filters records characterizing calls shorter than a specific duration. Thethreshold is expressed in seconds and must be an integer.
Example 1:
For a duration > 0, accounting records with a duration of 0 are not loaded into the database.
Call (Communication) Cost
4-47
This attribute is displayed in a list. Scroll down the list to select the type of comparison youdesire:
- Cost must be >=
- Cost must be >
This filter is applied to the cost calculated by the Alcatel-Lucent OmniVista 4760 NetworkManagement System.
Example 2:
Cost must be >= 2.5. Accounting records characterizing all calls with a cost less than 2.5x (where x is
the currency defined in the Alcatel-Lucent OmniVista 4760 Network Management System) are not stored
in the Alcatel-Lucent OmniVista 4760 Network Management System database.
Communication TypeSelect (check) the options required to authorize the loading of records with the Comm. Typedata item completed as Unspecified, Voice, Data type.
Call TypeThe types of call to be included must have been previously selected on the OmniPCX 4400 orAlcatel-Lucent OmniPCX Enterprise CS. Select the options required to authorize loading ofrecords with Call type information completed as Incoming, Outgoing, Network type. Byselecting Network, you store inter-PCX and internal calls.
Charged Party NodeThis section allows data loading according to the PCX selected to be checked. It lists all PCXsdeclared in the System directory. To avoid loading the records of PCXs that are notdeclared in the Alcatel-Lucent OmniVista 4760 Network Management System, deselect theUndeclared option. If you do not want to include the records of a specific PCX, deselect theoption for the corresponding PCX.
Example 3:
You are using the accounting of PCX A consisting of 5000 users. PCX A is located in a network of 3
PCXs (A, B and C) containing a total of 17,000 users. However, your license only allows you to manage
a maximum of 5,000 users.
To avoid exceeding this capacity, it is advisable to prevent user record loading for PCXs B and C by
deselecting the corresponding options. The records of the 3 PCXs are downloaded and only records for
the chargeable items of PCX A are loaded into the database.
Remark:
Filters and restrictions on record creation can also be configured in the internal configuration of a PCX.
Data masked on the PCX cannot be recovered.
The limits on the PCX side take precedence over those of the Alcatel-Lucent OmniVista 4760 Network
Management System. Consequently, you must check for consistency if filters are applied on both sides.
The Alarms tab is used to view alarms related to loading.
4.4.2.2 Traffic Analysis
To configure loading of Traffic analysis counters:
1. Access the Loading > Traffic Analysis branch.
2. In the bottom Filter tab, configure:
Chapter 4
4-48
• Observed objects (objects to be analyzed)• Observed days (days to be analyzed)• Cost centers to be analyzed,• The calculation thresholds of the T1 and T2 counters,
Select the objects to be analyzedSelect or clear the objects for the counters to be downloaded at synchronization. If you want toperform traffic analysis only for DECT/PWT handsets or Trunk groups, select the twocorresponding options. You will considerably reduce synchronization times and optimizedatabase operation.
Figure 4.17: Observed Objects Configuring Area — Traffic Analysis
Select the days analyzed and time period analyzed
- Select the days of the week to be analyzed.
- Indicate the start and end time (half hour) which mark the period to be analyzed. Bydefault, the period is from 00:00 to 23:30 and does not impose any time limitation.
Figure 4.18: Observed Days Configuring Area — Traffic Analysis
Select cost centers to be analyzed,The cost centers are displayed in two boxes:
- The left box lists centers that can be tracked and analyzed.
- The right box displays the cost centers for which traffic tracking and analysis is enabled.
4-49
Figure 4.19: Observed Cost Centers Configuring Area — Traffic Analysis
To confirm analysis of all available cost centers, select the Observe all option.
To select analysis of certain cost centers:
1. Select the Analyze selected items option,
2. Then select and deselect cost centers by transferring them from one box to the other usingthe and buttons.
You can select several cost centers simultaneously using the Ctrl key (non-adjacent costcenters) or the Shift key (adjacent cost centers).
Remark:
When Accounting is first launched, the Observe all option is selected as cost centers are unknown.
They are included during the first synchronization and you can then select Analyze selected items.
Configuring calculation thresholds for user counters (T1 and T2).T1 and T2 are waiting thresholds for incoming external calls (calling trunks). These thresholdsare not related to the waiting thresholds for attendants, that can only be modified via PCXconfiguration (Applications object > Traffic analysis).
By default, T1 and T2 are respectively set at 30 sec. and 60 sec. You can set them accordingto the site.
These thresholds are used by specific fields when generating traffic analysis reports.
Figure 4.20: User Counters Threshold Configuring Area — Traffic Analysis
4.4.2.3 Voice over IP
To configure IP record loading:
1. Access the Loading > Voice over IP branch.
2. In the bottom Filter tab, configure:• Observed objects (objects to be analyzed)• Observed days (days to be analyzed)• IP masks.Select object types to be observedBy default, all are selected. Select or deselect the objects (IP set, board, Softphone, 4645voice mail) to be downloaded at synchronization.
Figure 4.21: Observed Objects Configuring Area — Voice over IPSelect the days analyzed and time period analyzed• Click the weekdays to be analyzed (by default, Monday through Friday).• Indicate the start and end time which mark the period to be analyzed. By default, the
Chapter 4
4-50
period is from 00:00 to 23:30 and does not impose any time limitation.
Figure 4.22: Observed Days Configuring Area — Voice over IPSelect the IP addresses to be analyzedLoading and reports require filters to be used on local and remote IP addresses. Thesefilters may be complete addresses (e.g. 155.132.39.88) or subnetwork masks (e.g.155.132.255.255 or 155.132 allowing, in this example, only records from subnet 155.132 tobe received).
Note 1:By default, no filter is enabled.
• Click +, a line is created in the table.• Enter the local IP address filter in the Source Mask column and the remote IP address
filter in the Target Mask column. The + sign is displayed at the start of each linecreated.
Note 2:The filters are applied when the first synchronization is performed.
Figure 4.23: IP Masks Configuring Area — Voice over IP
3. Click to accept your changes.
4.4.3 Configuring Total Accounting, Traffic Analysis, and VoIP PerformanceAnalysis Counter Calculation.
EXPERT MODE
Totaled counters are calculated and managed by the Alcatel-Lucent OmniVista 4760 NetworkManagement System using data from the PCXs. They are useful for:
- Optimizing the time required to generate the most common types of report: Total reports,offered in the Reports application.
- Facilitating the detection of some exceeded tracking thresholds in the tracking feature. Seemodule Accounting - Organization tab § Data Variation Rate .
The use of counters requires them to be regularly calculated.
4.4.3.1 Modifying Counter Calculation Scheduling
4-51
By default, the Scheduler ( see module Scheduler - Overview ) includes a daily Total countercalculation task. Maximum duration for this job is set to 7 hours. By default, calculation islimited to certain objects.
Depending on the database and usage of the Alcatel-Lucent OmniVista 4760 NetworkManagement System, configure execution of this job.
To total all objects:
1. Use the weekly and daily jobs.
2. Edit the job for calculation of total counters.
3. Then, for traffic analysis for example, replace the argument “-PtpType ATT,ATG,TRG” bythe argument “-PtpType ALL” in the Arguments field.
4.4.3.2 Recalculating Total Counters Manually
To update total counters:
1. Select Total calculation... from the Accounting/Traffic menu of theAccounting/Traffic/VoIP application. A window is displayed.
2. Select the calculation period for which you want to run the calculation:• Since the last Total calculation: Select this option to update counters without
reconsidering their current value. This is the option used by the job scheduled bydefault in the Scheduler.
• On a fixed period: Select this option if you want to specify an interval. Only a specificnumber of current counters can be recalculated.
CAUTION: This option may cause some total counters to be reset if the source data hasbeen deleted in the database (automatic maintenance purge).
3. Using the Accounting , Traffic analysis, and VoIP tabs, select:• The Call Types to be included for accounting.• The Total objects.When the All objects option is selected, the total determines the objects to be totaledaccording to the objects validated for loading (Parameters tab) at each execution.
4. If desired, select the Detect threshold exceeded and notification options by specifying themax. number of alarms that can be generated.
5. Click OK to run the calculation. Processing may take some time depending on the amountof data handled.
Repeat this procedure to manually update other types of counters.
4.4.3.3 Recommendations
Simultaneous launch with other applications: Avoid running recalculation while anotherprogram, that may modify, add, or delete database data, is running Example: traffic analysiscounter loading, or cleaning.Calculation period: As a period is calculated from the previous period, traffic analysis countercleaning must be considered. For example: yearly counters are calculated from monthlycounters.
If daily counters are stored for 6 months, monthly counters must be calculated at an interval ofless than 6 months.
Chapter 4
4-52
4.4.4 Configuring Parameters Common to All Carriers
To configure parameters common to all carriers:
1. Click the Parameters tab.
2. Update the branches linked with Carrier parameters: Currency, Tax, Country.
4.4.4.1 Managing the List of Currencies
To specify a new currency:
1. In the tree structure, select the branch Carrier Parameters > Currency, and the Createitem from the shortcut menu.
2. Update the Properties and Conversion Rate tabs.
Properties tabThis tab contains the following parameters:
- Currency Name: Euro, Pound, Dollar, etc.
- Symbol: €, £, $, etc. When reports are printed, currency names are replaced by symbols.
- Reference currency: yes/no. Only one currency can be selected as the referencecurrency. Call cost calculations are performed and saved in this currency. You can,however, print reports including another currency.
Caution:
The selected reference currency cannot be changed. It is offered at Alcatel-Lucent OmniVista
4760 Network Management System server installation by selection of a country name. For EURO
ZONE countries, it is highly advisable to declare the Euro as reference currency. Otherwise, the
database will have to be reset if you subsequently want to do this.
Conversion Rate tabWith the exception of the reference currency, configuration records have a conversion taballowing their exchange rate with respect to the reference currency to be entered.
Conversion rate is specified by a valid period. A valid period without an End date indicatespermanent validity.
If you want to manage an exchange rate variation over time, you must specify a new validperiod (shortcut menu > Add).
To delete a valid period and the associated exchange rate:
1. Select the appropriate line.
2. Click .
Remark:
You have configured several currencies: this allows carrier tariffs to be entered according to the different
currencies as accounting handles currency conversion.
4.4.4.2 Managing the List of Taxes
To configure a new tax:
1. In the tree structure, select the Carrier parameters > Tax branch.
4-53
2. From the shortcut menu, select Create.
3. In the Properties tab, enter the name of the tax.
4. In the Tax Rate tab, specify the current rate according to a specific valid period. Severalrates can be configured via different valid periods.
4.4.4.3 Managing the List of Countries
A country is specified by:
- A name.
- A symbol, shown in reports.
The country list configured under this branch is available when configuring carriers.
To create a country:
1. In the tree structure, select the Carrier parameters > Country branch.
2. In the shortcut menu, select Create, a blank line is added to the edit field table.
3. Update Country name and Symbol.
4.4.5 Activating Calculation of Comparison Carrier Costs
To compare carrier costs (active carriers/simulation carriers), you can declare carriers asSimulation type
Cost calculation may require a large amount of resources, depending on the number ofcarriers declared. You can enable or disable calculation for Simulation type carriers in orderto optimize processing times.
To disable any calculation with simulation carrier data:
1. Access the Parameters > Cost calculation > Cost Comparison branch.
2. Deselect the Calculate Comparison Costs option.
While the option is deselected, tariff comparison reports cannot be generated.
To enable cost calculation of simulation carrier calls:
1. Access the Parameters > Cost calculation > Cost Comparison branch.
2. Select the Calculate Comparison Costs option.
4.4.6 Viewing the Accounting Organization
The Accounting organization branch allows you to view:
- The number of active, inactive and undefined entity items per type. For example: numberof attendants, number of stations (extensions), etc.
- The number of levels: company, PCX/local levels, cost centers.
The Accounting organization contains the following tabs:
- Level Statistic
- Extension Statistic
- Statistics Record
Chapter 4
4-54
- Clipboard (not used).
Figure 4.24: Accounting Organization Window
4.5 Carriers tab
4.5.1 Overview
Carriers can be fully configured in three ways:
- Importing a data file § Carrier Data Import and Export Commands .
- Creating a pulse type carrier. As creating a carrier with pulse-based accounting requiresonly a few settings to be made, only a single configuration screen is required. If this is thecase, refer to § Creating a Pulse Type Carrier.
- Completing the Parameters and Carriers tabs in the order shown below.
4-55
Figure 4.25: Carrier Tree
Configuring a carrier by the third method consists in completing the branches in the followingorder:
1. In the Parameters tab, configure data common to all carriers (currencies, taxes, andcountries). See module Accounting - Parameters tab .
2. In the Carriers tab, declare carrier name and enter carrier properties. See § DeclaringCarrier Name and Entering Carrier Properties .
3. Define the carrier calendar (specific days and public holidays). See § Configuring CarrierCalendar .
4. Create the valid period for the following items:• Cost adjustment coefficients• Tariffs and time zones• Regions• Directions• Country or city names• Tariffs for ISDN services
See § Configuring a Valid Period .
5. Configure the tariffs (rates) offered by the carrier and any time zones. See § Configuringthe Tariffs to Be Applied and § Configuring Time Periods and Tariff Segments .
6. Configure regions. See § Configuring Regions .
Chapter 4
4-56
7. Configure directions. See § Configuring Directions (Destinations) .
8. In addition, you can configure:• A - Cost adjustment coefficients (see § Configuring Cost Adjustment Coefficients ).• B - Indirect carrier codes (see § Configuring Indirect Carrier Identifier Codes ).• C – The trunk groups assigned and the trunk groups associated with each carrier (see
§ Specify the Trunk Groups Assigned and the Prefixes Associated with each Carrier ).• D – Specific charging for ISDN services (see § Configuring Specific Charging for ISDN
Services ).• E – A list of direction types (see § Configuring Direction (Destination) Types ).• F – Direction areas configured by city/country names (see § Configuring Direction
Areas by City/Country Name ).• Any cost tracking (see § Setting up Cost Tracking ).
Data inheritance links between the different branches require that the order of the above listbe followed exactly.
When a carrier is configured by importing data files and you want to protect certain parametersin the tree structure, you must configure these parameters as Protected parameters.
If the parameter is classified as a Not Protected type and you import carrier data, the validperiods of your data may be modified automatically.
4-57
Figure 4.26: Carrier Configuration Process Schema
4.5.1.1 Updating Data Common to All Carriers
Chapter 4
4-58
This operation, which consists in managing the list of currencies, countries, and taxes, isdescribed in the module Accounting - Parameters tab .
4.5.1.2 Declaring Carrier Name and Entering Carrier PropertiesTo declare a carrier:
1. Click the Carriers tab in the tree area and select the Carrier branch.
2. Select the Create command from the shortcut menu.
3. Update carrier properties in the Properties tab.
NameThis is the name used to identify the carrier. The same identifying name cannot be assigned totwo carriers.
SymbolEnter a symbolic name with 5 letters maximum. Two carriers cannot have the same symbol.Symbols can be used in reports to replace long carrier names.
TypeConfigure which type of call the carrier is to be used for:
- Incoming
- Outgoing
- Indirect outgoing (for indirect carriers)
- Network (internal network, private link and internal calls to the PCX)
For PRIVATE trunk groups of TL type, the carrier on this trunk group must be declared as anetwork type and not as an outgoing type.
If there is any doubt about the call type, print out a report containing the Call Type.
An Indirect outgoing type carrier can only be accessed via an Outgoing type carrier
StateA carrier is configured according to 3 types:
- Active: The carrier is included in call cost calculations.
- Inactive: The carrier is not included in cost calculation. However, carrier characteristics arenot deleted from the application.
- Comparison: If you want to simulate the use of a carrier for some directions to comparetariffs (rates) with other carriers, configure the carrier with Simulation status.
Note:
To enable computation for simulation type carriers, you must also select the option located in the Para-
meters > Computing > Cost Comparison > Calculate Comparison Costs tab. You can then compare
the costs obtained with the active and simulated carriers in accounting reports. A large number of sim-
ulated carriers increases processing time during loading of accounting records (tickets).
Carrier prefixSpecify the carrier prefix.
Country, Currency and Taxes
1. Select (from the three the drop-down lists) the properties to be applied to the carrier. The
4-59
content of the drop-down lists is managed in country list management in the Parameterstab, on the Carriers parameters branch.
2. Confirm carrier creation. Branches are automatically created under the branch of the newcarrier.
4.5.1.3 Configuring Carrier Calendar
When a carrier is created, the Calendar branch is automatically created. It is mainly used toenter specific tariffs for public holidays.To configure a carrier calendar:
1. Double-click the carrier whose calendar you want to modify.
2. Click the Calendar branch.
3. Select the Create command from the shortcut menu and then enter the Specific DayType Name (for example: specific days, public holidays). Confirm.Under each Specific Day Type created, there is a corresponding Specific Date branch.
4. Select the Specific Date branch and then run the Create command from the shortcutmenu.
5. Create the specific days linked with the Specific Day Type and, if needed, select thepermanent annual valid period (valid each year) option.
The types of days configured in the calendar are available in the tariff (rate) configurationinterface.
4.5.1.4 Configuring a Valid Period
When creating a carrier, a Period branch is automatically created. Each period containssettings for adjustment coefficients, regions, directions, tariffs, etc.To create a period:
1. Click the Period branch and then run the Create command from the shortcut menu.
2. In the blank period, enter a valid start date.Period end date is completed automatically when the next period is created.
3. Add any Comments.
4. Click Apply to accept changes.
The following branches are automatically created under the period: adjustment, tariff (rate),region, ISDN service, direction, city/country name.
4.5.1.5 Configuring the Tariffs to Be Applied
A tariff is configured for a valid period:
1. Create a tariff under the tariff branch via the shortcut menu.
2. Enter the parameters listed below.
NameEnter an identifying name for the tariff (international, London, vicinity, etc.)
ClassificationNot Protected: the tariff can be updated by importing a data file.
Protected: the tariff is protected against data file imports.
Chapter 4
4-60
See § Carrier Data Import and Export Commands for import and export tools.
Tax included in AOC (Advice Of Charge) only for computation mode: with cost shown
Yes: The tax is shown in the cost transmitted by the PCX in the accounting record
No: The tax is not shown in the cost transmitted by the PCX in the accounting record.
Calculation mode:The choices offered are:
- Duration accounting
- Accounting calculated by the PCX
- Accounting calculated according to the number of units transmitted by the PCX
Case 1: Duration accountingIf the call cost is calculated using the duration indicated in the accounting record, select one ofthe following modes:
- Duration: round down
- Duration: exact
- Duration: round up
Round up means that any stage started is chargeable, whereas round down means that astage is only counted if complete.
Exact indicates charging to the nearest second.
Example:
For a 90 sec call charged at 10 cents/min, accounting varies according to the mode of Calculation selec-
ted:
- Rounding up gives a call cost of 20 cents because two stages are counted. A call with aduration of between 61 sec and 120 sec would give the same cost.
- Rounding down gives a call cost of 10 cents because only one stage is counted. A call witha duration of between 61 sec and 119 sec would give the same cost.
- Exact duration charging would give a cost of 15 cents (90 X 1/60 sec.).
Case 2: Accounting calculated by the PCXIf call cost is calculated by the PCX:
- Select Cost given by the PCX .
Caution:In this case, Alcatel-Lucent OmniVista 4760 Network Management System does not convert.The currency declared in the PCX must therefore be the same as the reference currency.
Case 3: Accounting calculated according to the number of units transmitted by the PCXIf call cost is calculated using the number of units contained in the accounting record (ticket):
- Select Based on unit.
Common voice and dataIf voice and data transmission are not charged at the same rate:
- Clear the Voice and data option. In this case, time periods must be configured separatelyfor each type of call.
4-61
Currency
- Select the currency that you want to use to configure accounting data.The list of available currencies is managed in the Parameters > Carriers parameters >Currency tab.
Tax
- Select the tax to be used for calculating taxes included for amounts calculated according tothis tariff.Taxes and rates are managed in the Parameters > Carriers parameters > Tax tab.
Adjustment
1. Select an adjustment coefficient to be applied to the tariff. See § Configuring Directions(Destinations) (Configuring cost adjustment coefficients).
2. Specify the different costs by time period. See § Configuring Time Periods and TariffSegments (Configuring time periods).
4.5.1.6 Configuring Time Periods and Tariff Segments
4.5.1.6.1 Time Periods
Certain carrier tariffs vary according to the type of day, time, or call duration.
To configure time periods:
- Click Tariff to display the Time period branch.
The table below shows the parameters to be entered, according to the Calculation Modeadopted in the upper Tariff branch.
table 4.15: Carrier Tariff ParametersDuration PCX cost Unit cost
Voice/Data X
Day Type X
Start Time Zone X
End Time Zone X
Name X
Unanswered Call Initial Cost X X
Answered Call Initial Cost X X
Minimum Cost X
Initial Duration X
Initial Unit X X
Unit Duration X
Unit Cost X X
Adjustment X X X
Legend:X: field concerned
Voice/Data: This characterizes the type of information transmitted during the call. If the tariff
Chapter 4
4-62
was previously configured with the Common Voice and Data option, this parameter is set toVoice/Data. However, if you configured a distinction between tariffs according to the type ofcall, you must specify for which type of data the configured time period is to be applied.
Day type:
The list offers the following types:
- Monday to Sunday (day of the week selected individually).
- Working days (Monday to Friday).
- Weekend (Saturday and Sunday).
- Daily (Monday to Sunday).
The Day type list also contains any specific days configured under the carrier's Calendarbranch.
Start Time Zone/End Time Zone
These two fields define the start and the end of the time period. Total time periods must form acomplete day. Only the Start Time Zone field must be completed as End Time Zone isautomatically completed with the start of the next period.
Name: This is the name identifying the time period.
Unanswered Call Initial Cost: This is an additional cost applied to unsuccessful calls (callduration zero).
Answered Call Initial Cost: This is an additional cost applied when the call is successful (callduration is not zero). When this cost is zero, duration and initial cost are included.
Minimum Cost: This is the minimum cost for all calls.
Initial Duration: This parameter (in seconds) is linked to Initial Unit.
Initial Unit: This parameter (in seconds) is linked to Initial Duration. During Initial Duration,"n" Initial Units are counted according to Unit Cost.
Unit Duration: This parameter (in seconds) is linked to Initial Cost. It is the duration duringwhich Unit Cost is counted.
For duration accounting with rounding up or down or per unit, this duration corresponds to astage.
Note:
Initial Duration and Initial Unit are only included when Answered Call Initial Cost is zero.
For proportional duration accounting, this duration is, generally:
- Set at 60 if you enter a Unit Cost per minute.
- Set at 1 if you enter a Unit Cost per second.
4-63
Figure 4.27: Cost Vs Time
c: cost; t: time
table 4.16: Cost Vs Time ValuesUnit Duration 60
Unit Cost 0.14
Unit Cost: Cost is configured in the reference currency (see module Accounting - Parameterstab § Managing the List of Currencies It is linked to Unit Duration (see above).
Adjustment: Apply markup/markdown to basic cost (see § Configuring Cost AdjustmentCoefficients ).
After confirming the time period, the Segment branch is automatically created and containsSegment 1, which has a Unit Duration and a Unit Cost equivalent to that defined in the timeperiod.
4.5.1.6.2 Segments
Segments are configured under the Time Zone branch, depending on whether charging variesin the time period.
Charging Varies in the Time Period (Zone):
1. Configure duration of application for segment 1. By default, this segment does not have anend date for application (Segment Duration: 0). The cost/duration ratio of segment 1 istherefore applied to the entire time period.
2. Create a segment for each stage change (cost/duration ratio).
Chapter 4
4-64
Figure 4.28: Charge Vs Time
A: accounting per stage (round up)
B : accounting to the nearest second
c: cost; t: time
table 4.17: Charge Vs Time ValuesSegment S1 S2 S3
Segment Duration 180 120 00
Unit Duration 60 60 60
Unit Cost 1 0.25 0.10
To create a segment:
1. Under the time period of your choice, select the Segment branch.
2. Select the Create command in the edit area shortcut menu. A blank line appears in the editarea.
3. Configure the segment via the following fields:• Segment Number: This determines the number of the order in which time period
segments are read. Segment numbers do not have to be consecutive.• Segment Duration: Enter the duration for which the segment is applied. At the end of
this time, the next segment is read.• Unit Duration and Unit Cost: These two parameters define charging and the duration
for which Unit cost is counted.
Charging does not vary within the duration of the time period:
The Unit Duration and Unit Cost values entered in the time period are used to automaticallycreate segment 1 with a Segment Duration of zero. The cost/duration ratio of segment 1 istherefore applied to the entire time period.
4.5.1.7 Configuring Regions
The Region branch contains a list of:
4-65
- calling regions (outgoing calls). These are the regions which contain at least one of thePCXs defined in the System Directory.
- Called Region. These are regions that can be accessed via one or more call Prefixes.
Each region includes the following branches:
- PCX
- Prefix
- Trunk Group
Updating these three "sub" branches determines the type of region: calling and/or called andthe used trunk group.
Figure 4.29: Configuring Regions
Dir 1 characterizes the direction between Region RP and Region SE
Dir 2 characterizes the direction between Region SE and Region RP.To configure a calling region:
1. Click the Region branch.
2. Select the Create command from the shortcut menu.
3. Enter an identifying Name.
4. Classify the region as Not Protected or Protected type. A Protected classificationprevents region update by data file import.
Chapter 4
4-66
5. In the PCX branch, specify the name of the PCXs responsible for routing calls and theirrespective Access phone numbers. The access number corresponds to the telephonenumber on which the PCX can be reached.
To configure a called region:
1. Click the Region branch.
2. Select the Create command from the shortcut menu.
3. Enter an identifying name.
4. Classify the region as Not Protected or Protected type. A Protected classificationprevents region update by data file import.
5. In the Prefix branch, enter access prefixes for this region individually.
Example 1:
Single carrier
Figure 4.30: Single Carrier Example
The Prefix - Carrier Dependent option must be enabled when a complete identification of thedirection requires the carrier indicator prefix to be added.
Example 2:
Multi-carrier
Figure 4.31: Multi-Carrier Example
4-67
The combination used by Alcatel-Lucent OmniVista 4760 Network Management System iscompared with the start of the called number contained in the accounting record for carrieridentification.
Note 1:
Carrier AX has prefix 1616. However, use of this carrier requires its prefix to be dialed followed by the
prefix of carrier FT: 1616 0 xxxxxxxxx (where x is the called number).
FT does not charge calls which are accessed via 1616 and must not be considered as a primary carrier.
By including carrier FT's prefix (0) with that of AX (1616), you ensure that calls are correctly assigned to
both carriers.
Note 2:
The Servi carrier has been configured only to facilitate handling of emergency and toll free numbers in-
dependent of the carrier.To configure a trunk group:
1. Select the Create command from the shortcut menu
2. Enter the Trunk Group identifier
3. Select Network.Subnetwork.PCX
4. Enter the Access phone number
Note 3:
The couple trunk group/PCX must be unique to all charging areas.
Note 4:
A trunk group is by default in the charging area of the PCX. Only trunk groups in a different charging area
must be declared.
4.5.1.8 Configuring Directions (Destinations)
A direction, or destination, allows calls to be grouped according to the regions in which callsoriginate or arrive. A tariff is applied to each Calling Region - Called Region pair.
Example:
Paris -> North of France.
1. Select a calling region.
2. Select a called region.
3. Specify the tariff to be applied to calls taking this direction.
4. Apply any adjustment coefficients.
5. Specify indirect carrier if this direction can be accessed via an indirect access.
6. Classify the direction as Not Protected or Protected type. A Protected classificationprevents direction update by data file import.
7. Enter an answer (routing) delay if required.
Note:
The region, tariff and adjustment lists offered correspond to the items previously configured in the upper
branches.
Chapter 4
4-68
The list of available secondary carriers corresponds to the carriers previously configured as Indirect out-
going type in the Carrier branch.
Answer delay
This answer (routing) delay corresponds to the average time in seconds between the end ofdialing and the receiver of the called set being picked up.
This parameter is only considered when cost calculation is based on duration and when thecarrier's infrastructure cannot manage calling party line seize.
Multiple routing for the same direction
You can configure several directions with the same two regions to manage calls routed by:
- One or more carriers.
- Cascaded carriers.
In this way, you can configure a preferred direction for call routing using indirect access(routing with carrier A then carrier B) and configure another route with direct access in thecase of congestion (only carrier A).
Cost tracking can be used on a direction.
Direction including an undefined region
The example below shows a list of directions with PARIS as the calling region. The firstdirection in the list (PARIS -) has an unspecified called region.
This direction (PARIS -) is used to include the directions of calls which are not specified by theother five directions: Paris - London, Paris - Mobile, etc.
Figure 4.32: Example — Tree Structure of Direction with Undefined Region
The unspecified region is added to the list of specified directions. Combinations are multiple,as shown in the following example:
table 4.18: All Directions ExampleRegion A Region B Example
Paris London Paris - London
All directions London - London
Paris All directions Paris -
All directions All directions -
Region A: calling region
4-69
Region B: called region
4.5.1.9 Configuring Cost Adjustment Coefficients
An adjustment is configured in one of the following forms:
- A linear equation (Ax+b).
- A percentage (A%).
This can be a markdown or a markup (reduction or increase).
An adjustment configured under a carrier is indiscriminately applied to:
- A Tariff.
- A Direction.
To configure an adjustment:
- Click the Adjustment branch.
- Select the Create command from the shortcut menu,
- Update the fields and confirm.
An adjustment can be used to ensure monetary unit conversion in certain PCX calculationmode cases.
4.5.1.10 Configuring Indirect Carrier Identifier Codes
Under this branch, identify indirect carriers (second carrier) within each subnet.
Fully configuring this branch improves cost calculation performance.
The carrier code to be entered corresponds to the carrier information shown on theaccounting record (ticket).To update this:
1. Select the Network.SubNetwork including the indirect carrier.
2. Specify the indirect Carrier. The list contains indirect carriers subsequently declared.
3. Enter carrier ID Code.
4. Apply your changes.
Note:
An indirect carrier can have a different code on different subnets.
Because assigning the same code to two carriers is not allowed, do not complete this section if this con-
figuration is used on the site.
4.5.1.11 Specify the Trunk Groups Assigned and the Prefixes Associated with eachCarrier
Fully updating this branch improves cost calculation performance.
A search for the direct carrier used can be performed in two different ways:
- Retrieving the Called Number from the accounting record and then searching for thePrefix with the best match in each Direction for all carriers.
- Or, retrieving the Trunk Group Number of the trunk group taken by the call from the
Chapter 4
4-70
accounting record and then searching the Trunk Group Connection branch for the carrierassigned to this trunk group.
The second method is much more efficient because there are fewer repetitions whensearching. In addition, two directions with the same prefix cannot be confused.To assign each PCX trunk group to a carrier:
1. Click the Trunk Group Connection branch,
2. Select the Create command from the shortcut menu,
3. Create the assignment by specifying the PCX, the Trunk Group, the Carrier, theassociated Prefix, and any Adjustment Coefficient.
4. Apply your changes.
Note:
To avoid any inconsistency, you cannot configure two identical pairs in this section (trunk group n — pre-
fix X) for two carriers of different types.
4.5.1.12 Configuring Specific Charging for ISDN Services
The Accounting application can handle additional costs linked to the use of ISDN services foreach carrier.
Transmission of ISDN data depends on the subscriptions taken out with the carriers.
List of services: Charge information, Unconditional call forwarding, Text Messaging.
Charging is systematically performed for each call, except for text messages where it isperformed for each message sent.To configure charging for a service:
1. Click the Trunk Group Connection branch.
2. Select the Create command from the shortcut menu.
3. Create the assignment by entering the PCX, Trunk Group, Carrier, the correspondingPrefix and any Adjustment Coefficient.
4. Apply your changes.
4.5.1.13 Configuring Direction (Destination) Types
Via this branch, you can manage the list of available directions (destinations), for example:internal, international, national.
The list of types of direction managed in this branch is subsequently used in the City/Countryname branch. This data is only used to give additional information in reports.
4.5.1.14 Configuring Direction Areas by City/Country Name
To customize the generation of reports based on carrier data, a City name (or Country name)and a Direction Type can be associated with a Calling Region and an associated Prefix.
4-71
Figure 4.33: Schematic Diagram for Configuring Direction Areas by City/Country Name
Example:
If you have large configurations of international carriers, you can specify to which country the carrier is
assigned. Thus, you can easily generate reports by country and by currency.
Complete the following fields to configure areas:
- Calling Region: The list offers the entries configured in the Calling Region branch
- Called Prefix: This is the prefix to dial to reach the city/country area.
- City/Country name: This is the name to assign to the area that can be reached by theprefix entered.
- Direction Type: The list offers the directions configured under the Direction Type branch.
Cost tracking can be used on a City/Country name.
Note:
The more City/Country names are declared, the longer the cost calculation will take. Declare the City/
Country name and the Direction Type only if necessary.
4.5.1.15 Setting up Cost Tracking
See module Accounting - Organization tab § Managing Tracking Profiles.
The graphic interface of the Tracking Status tab is described in the section, Counter Display -Tracking Status (optional).
Tracking is assigned in the Tracking tab at the bottom right. The check is performed in theTracking Status tab.
Tracking tabTo enable carrier tracking:
1. Clear the Default Tracking option,
2. Select a tracking profile from the list. The characteristics of the selected profile aredisplayed in the table.
Tracking Status tab
If a tracking profile has been applied to the carrier, on this tab you can display:
- Thresholds configured in the tracking profile applied to the carrier. They are displayed inthe form of red marks.
- Monthly and daily consumption counter status.
You can quickly check whether consumption counter thresholds have been exceeded.
4.5.2 Removing a Carrier
A carrier is removed by deleting all its configuration settings (tariff, region, direction, calendar,etc.) from Accounting.To remove a carrier:
1. Select the carrier in the tree structure.
2. Run the Delete command from the shortcut menu. Confirmation is requested. The carrier
Chapter 4
4-72
is removed from the database and carrier tree structure.
Caution:
If a cost calculation is performed after removing a carrier, all the costs of the records concerning
this carrier are reset to 0.
4.5.3 Example of a Carrier Configuration
The following example lists the operations required to declare a single carrier. The calculationmethod used is pulse (signal) mode.
1. In the carrier tab tree, create a carrier and update its various properties.
2. Under this carrier, create a valid period.
3. Under the valid period, specify a tariff (rate), with the following item as calculation mode:Based on unit.
4. Under this configured tariff, create a time period from 0 to 24 hours, then set a Unit price(e.g. 10 cents).
5. Create a Direction without specifying the source or destination region and assign thepreviously configured tariff.
6. For PCXs other than the OmniPCX 4400 or Alcatel-Lucent OmniPCX Enterprise CS,specify the carrier code used on the PCX in Indirect carrier code.
4.5.4 Carrier Data Import and Export Commands
Import and export tools are available to:
- Archive carrier data easily.
- Optimize the entry of similar data.
- Use some or all carrier data on several Alcatel-Lucent OmniVista 4760 NetworkManagement Systems.
The list of files corresponding to an export or import operation is written to file (INF format file).
The import and export commands are available in the Carrier tab tree, via the shortcut menu.
Figure 4.34: Carrier Tab — Shortcut MenuTo import this data:
4-73
1. Select an item in the tree structure.
2. Select the Import command from the shortcut menu. A results dialog box is displayed.
3. Specify the location of the inf data file containing the list of files to be imported.
4. Confirm.The import is launched.
To export data:
1. Select the period you want to export in the tree structure.
2. Select the Export command from the shortcut menu. A results dialog box is displayed.
3. Enter the name to be assigned to the data file. Its extension must be .inf. Specify thedirectory in which you want to save the exported files.
4. Confirm the export.All the data is saved in the exported files.
Note:Carrier data export is performed for each period.
To schedule an import or export, select the Scheduled Import or the Scheduled Exportcommand from the shortcut menu. The Scheduler is displayed.For more information, refer to module Accounting - Managing carrier data files - EXPERTMODE .
4.5.5 Creating a Pulse Type Carrier.
The "Create" command is available in the Carrier tab tree structure via the shortcut menu.
Figure 4.35: Carrier Tab — Shortcut Menu
1. Select the “Carrier” node or the node of a specific carrier.
2. Select the Create a pulse type carrier command from the shortcut menu.
Chapter 4
4-74
Figure 4.36: Create a Pulse Type Carrier Window
3. Enter the creation parameters:Name: This field is mandatory. This is the name used to identify the carrier. The sameidentifying name cannot be assigned to two carriers.Symbol: This field is mandatory. Enter a symbolic name with 5 letters maximum. Twocarriers cannot have the same symbol. Symbols can be used in reports to replace longcarrier names.Start Date: This is the date on which the period starts (by default, the current date).Tariff: This is the name of the tariff (by default, based on unit). The tariff created in thisway will implicitly use the “Based on unit” mode of calculation.Unit Cost: This field is mandatory. Cost is configured in the reference currency (seemodule Accounting - Parameters tab § Managing the List of CurrenciesAnswered Call Initial Cost: This is an additional cost applied when the call is successful(call duration is not zero). When this cost is zero, initial cost is included.Unanswered Call Initial Cost: This is an additional cost applied to unsuccessful calls (callduration zero).Country, Currency and Taxes: Select (from the three the drop-down lists) the propertiesto be applied to the carrier. The content of the drop-down lists is managed in country listmanagement in the Parameters tab, on the Carrier Parameters branch.Network.SubNetwork.PCX: If required, create the assignment by designating the PCX(from the drop-down list), the Trunk Group, the corresponding (trunk seize) Prefix andany Adjustment Coefficient.
4-75
Note:If a PCX is selected, the Trunk Group field must be completed.
Caution:The pulse type carrier rapid creation screen only allows a carrier based on a pulse tariff to becreated and does not allow rapid modification of the information entered. To perform modific-ations on the carriers created in this screen, refer to the full carrier configuration proceduredescribed in § Overview .
4.6 Database maintenance
4.6.1 Overview
Regular PCX data downloads and the generation of reports take up, over time, a large amountof space on the hard drive of the server hosting the Alcatel-Lucent OmniVista 4760 NetworkManagement System. Alcatel-Lucent OmniVista 4760 Network Management Systemperformance is affected when the database reaches a critical size.
In order to optimize the speed of calculation required for the generation of reports and to avoidsaturating the hard drive, the Alcatel-Lucent OmniVista 4760 Network Management Systemfeatures dedicated, automatic, configurable maintenance operations.
The purpose of these operations is to delete obsolete data (for example, tickets (records) olderthan 3 months) from the database.
4.6.2 Deleting Old Data Automatically
Here is a list of the data purged (cleaned) within a default interval. Execution frequencies anddeletion criteria can be configured:
- Daily deletion of Traffic analysis counters:• Time period counters more than 45 days old.• Daily counters more than 94 days old.• Monthly counters more than 15 months old.• Yearly counters more than 36 months old.
- Daily deletion of Total counters:• Daily counters more than 35 days old.• Monthly counters more than 15 months old.• Yearly counters more than 36 months old.
- Weekly deletion:• Accounting records more than 94 days old.• Daily tracking counters more than 94 days old.• Monthly tracking counters more than 15 months old.• Inactive stations without records, tracking counters or traffic analysis counters.• Inactive levels without stations (*).• Detailed reports more than 94 days old.• An entire carrier configuration more than 94 days old (see § Recommendations ).
(*) The following are not affected by the cleaning operation (purge): root, companies, and
Chapter 4
4-76
undefined levels. 94 days corresponds to 3 months + 1 day in order to guarantee 3 completemonths.
Accounting/Traffic/VoIP default cleaning values can be modified by accessing the Systemdirectory: NMC > Server_name > Servers > Server_name > NMCDataBase.
4.6.3 Recommendations
Total countersTotal counters are generated by the Alcatel-Lucent OmniVista 4760 Network ManagementSystem using accounting records. If you delete accounting records in a period [T1-T2], thenrun a calculation of total counters for the same period again, you will obtain a result of zero fortotal counters.Cleaning total counters has no affect on accounting records. Although, there is a risk ofresetting tracking analysis counters (option) that use specific total counter values.
Relationship between the records and the carrier dataTo ensure normal database operation, it is preferable to store configuration data for alonger period than records. This will avoid links between records and carrier configurationdata being lost.If you want to store a full year of your record archives, set a carrier data cleaning operation(purge) at 396 days (365 + 31 days).
4.6.4 Deleting Data Manually
There is a dedicated interface for manual deletion of accounting and traffic analysis data. Themultiple options offered allow targeted deletion.Select the Only restored records option to delete records (tickets) marked during the restorephase (see § Restoring Records ).
The interface can only be accessed from the Accounting/Traffic/VoIP application via theAccounting/Traffic/VoIP > Purging menu.
Manually cleaned data cannot be retrieved. Be sure to archive this data before deleting it.
Note:
As manually cleaning of records is extremely lengthy, it is preferable to do this at night or at the weekend.
4.6.5 Archiving/Restoring Records
By default, a weekly record archiving task is programmed.
- This task archives records from the date of the previous archiving operation until thecurrent date minus 31 days. This is because, over the previous 31 days, record archiving isnot applicable as the records are used for analysis for reports and are present both in theAlcatel-Lucent OmniVista 4760 Network Management System database and in the PCXdatabases (Alcatel-Lucent OmniPCX Enterprise CS and OmniPCX 4400).
- Each archive file is conserved for 94 days, which means that records may be kept for up to125 days maximum (94 days maximum conservation + 31 days archiving delay). After thistime, records are deleted.
4-77
Figure 4.37: Archiving Records
The files are archived in directories by year/month/date. In each directory, the files are namedby node, year, month and date.
Figure 4.38: File Arrangement in Directory
Accounting has two manual commands to implement record transfer. The interfaces areaccessed via the Archive records and Restore records items in theAccounting/Traffic/VoIP menu.
4.6.5.1 Manual Record Archiving Operations
Via this interface:
1. Select archiving period as On a fixed period or from the date of the From last archive(default option).These parameters can be modified in the System Directory: NMC > Name server >Servers > Server_name > Accounting.
2. Specify the path to the archive directory by clicking Search....
3. Click OK. The Scheduler is displayed to perform any required scheduling.
4.6.5.2 Restoring Records
Via this interface:
1. Specify the path to the records to be restored using the Search command.
2. Where appropriate, specify period.
3. The Tag records as “from an archive” option can be used to subsequently cleantargeted restored records (Only restored records option for cleaning - see § DeletingData Manually ).
Chapter 4
4-78
4. The Insert recalculated costs option is used to recalculate restored record costs with thecurrent accounting configuration, provided that the valid date of the carrier matches thevalid date of the records.
5. Click OK to run the restore operation.
4.6.6 Scheduling Maintenance Tasks
Cleaning operations of accounting and traffic analysis data are scheduled in a weekly task. Ifthis weekly task takes too long, make the frequency of this task shorter.
4.6.7 Updating Accounting organization
This feature reassigns all tickets and PTP counters to the active entities.
- Any tickets and PTP counters assigned to an inactive entity are re-assigned to an activeentity if the entities have the same ChargedNumber and PCX.
- All inactive entities and their directory's entries are removed.
To update Accounting organization:
1. In the 4760\ bin directory, double click on the ToolsOmnivista.exe icon, enter a passworddirectory manager, then the following windows appears:
Figure 4.39: E:\4760\bin\ToolsOmnivista.exe window
2. Select 2 "Accounting Organization Update"
3. To the question do you want to continue answer "YES".
4. The process starts:
4-79
Figure 4.40: E:\4760\bin\ToolsOmnivista.exe window
4.7 Managing carrier data files - EXPERT MODE
4.7.1 Overview
Import and export tools are available to:
- Facilitate carrier configuration archiving.
- Optimize the entry of similar data.
- Use part of or the entire carrier configuration on several Alcatel-Lucent OmniVista 4760Network Management Systems.
Chapter 4
4-80
4.7.2 Accessing the Import and Export Commands
See module Accounting - Carriers tab § Carrier Data Import and Export Commands .
4.7.3 File Description
The files concerned by data import and export operations are the following:
table 4.19: Import/ Export File ExtensionsFile name Extension
Information file .inf
Region file .rgn
City/Country file .ccn
Direction file .dir
Tariff file .trf
Calendar file .cal
Adjustment file .adj
Installation file .itl
Trunk Group .trg
Information file
This file contains general information on:
- The import (version, date, object shutdown).
- The carrier (name, prefix, currency, country).
This file is mandatory.
This file is required for any import. It contains general information on the carrier and a list ofthe names of the other imported files:
Only information file data has to be contained in a single file. The other data can be distributedamong several files with the same extension.
With the exception of the information file, all files must contain a header identifying eachcolumn. This line must appear before the data.
Region file
This file contains a list of carrier regions. These regions are made up of a set of prefixes. Theydefine zones from the carrier's viewpoint.
In this file, it can be specified whether the prefix depends on the carrier or not.
City/Country name file (CCN: City/Country Code)
This file contains relationships between prefixes and country or city names. This information isused in reports by the tracking service.
Direction file
This file contains the full list of directions (destinations) and associated tariffs. Each direction ismade up from the regions defined in the region files.
4-81
Tariff (rate) file
This file contains information on tariffs (type of calculation type, day, time period, cost/minute,etc.).
Calendar file
This file contains the names and dates of public holidays. If no name is specified, dates aregrouped under the name Public holidays.
Adjustment file
This file contains cost adjustment coefficient information.
Facility file
This file contains information on adjustments.
Installation file
This file contains the user regions useful for determining the directions to be imported:according to the PCX location, this file is specific to each client.
Trunk Group file
This file contains the user regions useful for determining the directions to be imported:according to the trunk group access location, this file is specific to each client.
4.7.3.1 General Principles
4.7.3.1.1 Key Words
Key word syntax and case are as follows:
Information file key words
- VERSION: file version number.
- CARRIER_NAME: carrier name.
- CARRIER_INITIAL: carrier initials.
- CARRIER_PREFIX: carrier prefix.
- CARRIER_PREFIX_INCLUDED: YES or NO.
- CARRIER_TYPE: carrier type (OUTPUT_FIRST_CARRIER: outgoing -
- INPUT_FIRST_CARRIER: incoming - NETWORK_CARRIER: network -
- OUTPUT_SECOND_CARRIER: second outgoing).
- EFFECT_DATE: data valid date.
- STOP_UNUSED_OBJECTS: determines the shutdown of unused objects (YES or NO).
Caution:As from release 2.1, this parameter is no longer interpreted.
- CURRENCY: carrier currency.
- TAX: name of the tax applied to the carrier.
- COUNTRY: carrier country.
- RGN_FILE: region file name.
Chapter 4
4-82
- CCN_FILE: city/country file name.
- DIR_FILE: direction file name.
- TRF_FILE: tariff file name.
- CAL_FILE: calendar file name.
- ADJ_FILE: adjustment file name.
- ITL_FILE: installation file name.
- TRG_FILE: trunk group file name.
Calendar File Key Words
YYYY: specifies an annually repeated date.
Region and Direction File Key Words
- DEPENDENT: prefix depends on carrier prefix.
- NOT_DEPENDENT: the prefix does not depend on the carrier prefix.
Tariff File Key Words
- CHARGEUNIT: calculation per unit.
- ROUNDDOWN: duration calculation - rounded down to the lower time unit.
- ROUNDUP: duration calculation - rounded up to the upper time unit.
- PROPORTIONAL: duration calculation.
- AOC: uses the cost provided by the PCX.
- VOICE: tariff for voice calls.
- DATA: tariff for data calls.
- VOICE_DATA: tariff for common voice and data.
- DAILY: daily (from Monday to Sunday).
- HOLIDAY: public holidays specified in the calendar files.
- WEEKEND: weekend (Saturday and Sunday).
- MONDAY: Monday.
- TUESDAY: Tuesday.
- WEDNESDAY: Wednesday.
- THURSDAY: Thursday.
- FRIDAY: Friday.
- SATURDAY: Saturday.
- SUNDAY: Sunday.
Adjustment File Key Words
- PERCENTAGE: adjustment based on a percentage.
- LINEAR_EQUATION: adjustment based on a linear equation.
4-83
4.7.3.1.2 Field Separator
A tab is used to separate each field. To apply a default value, do not enter a value and movedirectly to the following field by adding a tab.
4.7.3.1.3 Comments
"%" is the comment character. Any line beginning with this symbol is ignored.
4.7.3.1.4 Header
@ is the header character. A line beginning with this symbol is a header line; there can only beone header line per file and it is mandatory in all but the information file.
Region File Header
- PREFIX: prefix column.
- REGION: region name column.
- CARRIER_PREFIX_DEPENDENCY: column indicating dependency on the carrier prefix.
City/Country Name File Header
- CALLING: calling prefix column.
- CALLED: called prefix column.
- CCN: city/country name designation.
- DIRECTION_TYPE: direction type column.
Direction File Header
- CALLING: calling region name column.
- CALLED: called region name column.
- TARIFF: tariff name column.
- ADJUSTMENT: adjustment name column.
- SECOND_CARRIER: second carrier name column (if needed).
Calendar File Header
- DAYTYPE: day type column (identical to the column present in the tariff file).
- DATE: specific date column.
Tariff File Header
- TARIFF: tariff name column.
- CALCULATIONMODE: calculation mode column.
- VOICEDATA: tariff type column (voice, data, or common voice and data).
- DAYTYPE: day type column.
- STARTTIMEZONE: start time column.
- ENDTIMEZONE: end time column.
Chapter 4
4-84
- SEGMENT: segment number column.
- SEGMENTDURATION: segment duration column.
- COSTPERUNIT: segment cost per unit column.
- UNITDURATION: segment unit duration column.
- INITIALCOSTANSWERED: initial cost for an answered call column.
- INITIALCOSTNOANSWERED: initial cost for an unanswered call column.
- MINIMUMCOST: minimum cost.
- INITIALUNITS: initial cost column.
- INITIALDURATION: initial duration column.
- LABEL: time period name column.
- ADJUSTMENT: adjustment name column.
- CURRENCY: tariff currency column.
- TAX: column of the tax applied to the tariff.
Adjustment File Header
- ADJUSTMENT: adjustment name column.
- ADJUSTMENT_TYPE: adjustment type column.
- PARAMETER_A: first parameter column.
- PARAMETER_B: second parameter column.
Installation File Header
- REGION: region name column.
- NUMBER: telephone number column.
- NODE: PCX name column.
Trunk Group File Header
- REGION: name of the region
- NUMBER: access phone number
- NODE: PCX information
- TRUNKGROUP: trunk group number
4.7.3.1.5 Dates
Date format is as follows: YYYYMMDD
Separators are not allowed.
4.7.3.1.6 Decimal Values
The decimal separator is a point (period).
4.7.3.1.7 Text Field
4-85
For all text fields, you must respect the case (capital or lower case letters) of values alreadypresent in the database.
Note:
In all files, the field separator is a tab. For clarity, the fields shown in the examples have been aligned.
4.7.3.2 Information File
4.7.3.2.1 Field Definition
This file does not apply the standard format (a header line, several data lines), each line has akey word and its associated value.
- VERSION: file version number (currently: 1).
- CARRIER_NAME: carrier name (50 characters maximum).
- CARRIER_INITIAL: carrier initials (5 characters maximum). The first letter of the carrier isused by default.
- CARRIER_PREFIX: carrier prefix (10 characters maximum).
- CARRIER_PREFIX_INCLUDED: the carrier prefix is included in the prefix files (YES orNO). By default, the value is YES.
- CARRIER_TYPE: the carrier type (OUTPUT_FIRST_CARRIER (by default),INPUT_FIRST_CARRIER, NETWORK_CARRIER or OUTPUT_SECOND_CARRIER).
- EFFECT_DATE: the data valid date.
- STOP_UNUSED_OBJECTS: unused objects must be stopped (YES or NO). By default,the value is NO.
Caution:As from release 2.1, this parameter is no longer interpreted.
- CURRENCY: the carrier currency name. By default, the reference currency is used (50characters maximum).
- COUNTRY: the carrier country name (50 characters maximum).The key words below are used to give the names of the data files. The data can bedistributed over several files but there can only be one file per line.
- ADJ_FILE: adjustment file name.
- RGN_FILE: region file name.
- CCN_FILE: "city/country name" file name.
- DIR_FILE: direction file name.
- TRF_FILE: tariff file name
- CAL_FILE: calendar file name.
- ITL_FILE: installation file name.
- TRG_FILE: trunk group file name.
4.7.3.2.2 Example
Chapter 4
4-86
Note:
This example uses 2 region files: franceT1.rgn and franceT2.rgn.
(1) As from release 2.1, the STOP_UNUSED_OBJECTS parameter is no longer interpreted.
4.7.3.3 Region File
4.7.3.3.1 Field Definition
Prefix Region Dependency
Where:
- Prefix: the prefix (20 characters maximum).
- Region: the region associated with the prefix (50 characters maximum).
- Dependency: the prefix depends on the carrier prefix (DEPENDENT or NOTDEPENDENT). By default, the value is DEPENDENT.
In a full description of a dependent prefix, the carrier prefix comes before the dependent prefix.Conversely, a prefix which is not dependent is valid regardless of the carrier. Service prefixesare generally not dependent (see the example).
4.7.3.3.2 Example
4-87
4.7.3.4 City/Country Name File (CCN)
4.7.3.4.1 Field Definition
Calling Called Ccn Direction type
Where:
- Calling: the calling (originating) name or prefix.
- Called: the called (destination) prefix (20 characters maximum).
- CCN: the city or country name associated with the prefixes (50 characters maximum).
- Direction type: direction type name (50 characters maximum).
It is advisable to use a calling region name rather than a prefix.
To be applied for CALLING.
4.7.3.4.2 Example
4.7.3.5 Direction File
Chapter 4
4-88
4.7.3.5.1 Field Definition
Calling Called Tariff Adjustment
Where:
- Calling: calling region name.
- Called: called region name.
- Tariff: tariff applicable for this call.
- Adjustment: the adjustment applicable for this call.
4.7.3.5.2 Example
4.7.3.6 Tariff (Rate) File
4.7.3.6.1 Field Definition
The tariff file header must be written on the same line; a tab is used as the separationcharacter. For clarity, this header is in the form of a column.
- TARIFF Tariff
- CALCULATIONMODE Calculation mode
- VOICEDATA Voice/data
- DAYTYPE Day type
- STARTTIMEZONE Start time
- ENDTIMEZONE End time
- SEGMENT Segment
- SEGMENTDURATION Segment duration
- COSTPERUNIT Cost per unit
- UNITDURATION Unit duration
- INITIALCOSTANSWERED Answered call cost
- INITIALCOSTNOANSWERED Unanswered call cost
- MINIMUMCOST Minimum cost
- INITIALUNITS Number of units
- INITIALDURATION Initial duration
4-89
- LABEL Label - Time period name
- ADJUSTMENT Adjustment
- CURRENCY Currency
- TAX Tax
Where:
- Tariff: tariff name (50 characters maximum).
- Calculation mode: the calculation mode (CHARGEUNIT, ROUNDUP, ROUNDDOWN,PROPORTIONAL or AOC).
- Voice/Data: the type of call to which this tariff is applied (VOICE, DATA or VOICE_DATA).
- Day type: the day type for which costs are defined (DAILY, HOLIDAY, MONDAY, etc.). Bydefault, the value is DAILY.
- Start time: the time period start time in HHMM format. By default, the value is 0000.
- End time: the time period end time in HHMM format is not used, the next time period starttime is used for continuity. By default, the value is 2400.
- Segment: segment number. By default, the value is 1 (the first segment).
- Segment duration: segment duration in seconds. By default, the value is 0; this representsthe duration of the last segment.
- Cost per unit: the cost for one unit of the segment. By default, the value is 0.
- Unit duration: the duration of a unit in seconds. By default, the value is 0.
- Answered call cost: the cost of an answered call. By default, the value is 0.
- Unanswered call cost: the cost of an unanswered call. By default, the value is 0.
- Minimum cost: the minimum call cost. By default, the value is 0.
- Number of units: the number of initially credited units. By default, the value is 0.
- Initial duration: initial duration in seconds. By default, the value is 0.
- Label: time period name.
- Adjustment: adjustment applied to the tariff (if necessary).
- Currency: tariff currency (if different to carrier currency).
- Tax: tax applied to the tariff (if necessary).
4.7.3.6.2 Example
Chapter 4
4-90
4.7.3.7 Calendar File
4.7.3.7.1 Field Definition
Day type Date
Where:
- Day type: specific day name (50 characters maximum).
- Date : the date belonging to this type of day in YYYYMMDD format. The YYYY key wordidentifies a valid date each year.
4.7.3.7.2 Example
4.7.3.8 Adjustment File
4.7.3.8.1 Field Definition
Adjustment Type Parameter A Parameter B
Where:
- Adjustment: adjustment name (50 characters maximum).
- Type: adjustment type (PERCENTAGE or LINEAR EQUATION).
- Parameter A: the percentage or the first parameter in the equation.
- Parameter B: the second parameter in the equation. By default, the value is 0.
4.7.3.8.2 Example
4-91
4.7.3.9 Installation File
4.7.3.9.1 Field Definition
Region Number Node
Where:
- Region: the name of the region for which you want to perform the import (50 charactersmaximum).
- Number: a telephone number defining the region (20 characters maximum).
- Node: the name of the PCX installed in this region (syntax identical to that managed on theAlcatel-Lucent OmniVista 4760 Network Management System).
4.7.3.9.2 Example
4.7.3.10 Trunk Group File
4.7.3.10.1 Field Definition
Region Number Node Trunk Group
Where:
- Region: the name of the region for which the import is going to be done (50 charactersmaximum)
- Number: a telephone number defining the region (20 characters maximum)
- Node: the name of the PCX to which the trunk group belongs
- Trunk Group: the number of trunk group installed in this region
4.7.3.10.2 Example
Chapter 4
4-92
4.7.4 Carrier Description
Successive stages of a complete import:
- Carrier import
- Region import
- Calendar import
- Adjustment import
- Tariff import
- Direction import (direction and city/country names)
- Facilities import
Remark:
All errors are contained in a file with the .log extension.
The import never removes an object, it can only create or update the information of the objects present in
the files. Any deletions required are performed manually or by a purge.
Caution:
Objects not present in the files are not deleted but the valid periods are updated if the
STOP_UNUSED_OBJECT option is set to YES (up to release 2.1).
As from release 2.1, the STOP_UNUSED_OBJECT parameter no longer has any meaning and is
ignored. There are now two cases when an import is performed:
- The date on which imported data takes effect is the same as the start of the current valid peri-od. In this case, the import behaves like an update of the current period. Existing data is up-dated with any new parameters, data that does not exist in the database is created, old datathat is not re-imported remains present in the databases as previously.
- The date on which imported data takes effect is posterior to (after) the start of the current val-id period. In this case, the current period and all attached data are stopped at the date onwhich the new import takes effect. A new period is created with the date at which the impor-ted file takes effect as start date. All imported data is attached to this new period.
4.7.4.1 Creating a Carrier
4.7.4.1.1 Mandatory File
The information file is required to create a carrier.
4.7.4.1.2 Execution Constraints
The carrier is created before any other object. If creation fails, the import ends immediately.
4.7.4.1.3 Description
When reading the information file, the name of the carrier found in the file is searched for in thedatabase. If the carrier is not found, it is created according to the parameters in the file.Otherwise, information is compared with existing data to determine whether import cancontinue (prefix and currency identity).
If the carrier's currency does not exist, it is created but the exchange rate still remains to be
4-93
configured. If the carrier's country does not exist, it is created.
4.7.4.1.4 Errors
If there is an error during carrier creation, the import is canceled.
- the data valid date must be before the oldest configuration date.
- If the carrier exists, its prefix must be the same as the prefix present in the file.
- If the carrier exists, its currency must be the same as the currency present in the file.
- The carrier symbol must be unique within the database.
4.7.4.2 Creating and Updating Regions
4.7.4.2.1 Mandatory File
The region or installation file or trunk group file is required to create or update the regions.
4.7.4.2.2 Execution Constraints
Before creating or updating a region, the carrier must have been declared.
4.7.4.2.3 Description
For each line in the region or installation files or trunk group , there are several possible cases:
- The region does not exist, it is created.
- A region with the same name exists, the valid date is the same as the start date of the lastvalid period. The region is updated with the prefixes and/or PCXs or trunk group of thefiles.
- A region with the same name exists, the valid date is more recent than the start date of thelast valid period. The region data is discarded and replaced by the data present in the file(a new valid period is created).
4.7.4.2.4 Errors
Errors are stored in the .log file and the line is rejected if:
- The region exists as a specific region.
- The prefix has already been imported.
- The prefix is dependent on the carrier, it is included in the file but does not begin with thecarrier prefix.
- There is no number for the trunk group
4.7.4.3 Creating and Updating Specific Dates
4.7.4.3.1 Mandatory File
The calendar file is required to create or update specific dates.
4.7.4.3.2 Execution Constraints
Before creating or updating a region, the carrier must have been configured.
4.7.4.3.3 Description
Chapter 4
4-94
For each type of day contained in the file, the corresponding dates are added (except if theyalready exist). If day type is not specified, the dates are grouped under the day type, Publicholidays (translated into all languages).
4.7.4.4 Creating and Updating Adjustments
4.7.4.4.1 Mandatory File
The adjustment file is required to create or update adjustments.
4.7.4.4.2 Execution Cconstraints
Before creating or updating an adjustment, the carrier must have been declared.
4.7.4.4.3 Description
For each line of the adjustment files, there are several possible cases:
- The adjustment does not exist, it is therefore created.
- An adjustment with the same name exists, the valid date is the same as the start date ofthe last valid period. The adjustment is updated.
- An adjustment with the same name exists, the valid date is more recent than the start dateof the last valid period. The adjustment data is discarded and replaced by the data presentin the file (a new valid period is created).
4.7.4.4.4 Errors
Errors are stored in the .log file and the line is rejected if:
- The adjustment exists as a specific adjustment.
- The adjustment has already been imported.
- The adjustment type is not valid.
4.7.4.5 Creating and Updating Tariffs
4.7.4.5.1 Mandatory File
The tariff file is required to create or update tariffs.
4.7.4.5.2 Execution Constraints
Before creating or updating a tariff, the carrier must exist, if the tariff requires an adjustment,the adjustment must exist.
4.7.4.5.3 Description
For each line in the tariff file, there are several possible cases:
- The adjustment does not exist, it is therefore created.
- A tariff with the same name exists, the valid date is the same as the start date of the lastvalid period. The tariff is updated with the time periods contained in the file.
- A tariff with the same name exists, the valid date is more recent than the start date of thelast valid period. Tariff data is discarded and replaced by the data from the file (a new validperiod is created).
4-95
For an existing tariff, the calculation mode and the common voice/data parameter cannot beupdated.
4.7.4.5.4 Errors
Errors are stored in the .log file and the line is rejected if:
- The tariff exists as a specific tariff.
- The tariff calculation mode is different from the existing mode or does not exist.
- The tariff voice/data field is not compatible with the existing field or does not exist.
- Day type, currency, tax, or adjustment for this tariff does not exist.
4.7.4.6 Creating and Updating Directions
4.7.4.6.1 Mandatory File
The direction file is required to create or update directions. The imported directions depend onthe presence and the content of the .itl file and the .trg file.
4.7.4.6.2 Execution Constraints
Before creating or updating a direction, the carrier, regions and tariffs must exist. If thedirection requires an adjustment, the adjustment must exist.
4.7.4.6.3 Description
The source (originating) region is a special case:
- If the .itl and the .trg file are not present, all the directions (with calling region empty),contained in the file are imported.
- If the .itl and/or .trg file is present, only directions whose source region corresponds to theregions defined in the .itl or in the .trg file are imported (matching region prefix and PCXnumber).
For each line of the direction file, there are several possible cases:
- The direction does not exist, it is therefore created.
- A direction between the two regions exists, the valid date is the same as the start date ofthe last valid period. The direction is updated.
- A direction between both regions exists, the valid date is more recent than the start date ofthe last valid period. The direction data is discarded and replaced by the data present inthe file (a new valid period is created).
4.7.4.6.4 Errors
Errors are stored in the .log file and the line is rejected if:
- The direction exists as a specific direction.
- The direction has already been imported.
- Region, tariff, adjustment, or indirect carrier does not exist.
4.7.4.7 Creating and Updating City/Country Names
4.7.4.7.1 Mandatory File
Chapter 4
4-96
The city/country name file is necessary to create or update the city/country names.
4.7.4.7.2 Execution Constraints
Before creating or updating a city/country name, the carrier and regions must have beendefined.
4.7.4.7.3 Description
For each line in the city/country name file, there are several possible cases:
- The city/country name does not exist, it is therefore created.
- A region city/country name to the prefix exists, the valid date is the same as the start dateof the last valid period. The city/country name is updated.
- A region city/country name to the prefix exists, the valid date is more recent than the startdate of the last valid period. The city/country name data is discarded and replaced by thedata present in the file (a new valid period is configured).
4.7.4.7.4 Errors
Errors are stored in the .log file and the line is rejected if:
- The city/country name has already been imported.
- The region does not exist
4.7.4.8 Creating and Updating Facilities
4.7.4.8.1 Mandatory File
The facility file is required to create or update facilities.
4.7.4.8.2 Execution Constraints
Before creating or placing a service, the carrier exists.
4.7.4.8.3 Description
For each line of the facilities files, there are several possible cases:
- The service does not exist, it is therefore created.
- A service with the same name exists, the valid date is the same as the start date of the lastvalid period. The service will be updated.
- A service with the same name exists, the valid date is more recent than the start date ofthe last valid period. Service data is discarded and replaced by the data from the file (anew valid period is created).
4.7.4.8.4 Errors
The error is stored in the .log file and the line is rejected if:
- The service has already been imported.
- The predefined name of the service is not valid.
- Calculation mode is not valid.
4-97
4.7.5 Carrier Data Dependency
The import can be performed partially but the relationship between some data means that youhave to:
- either include the required data in the import,
- or ensure that the required data is present in the database.
The table below highlights file inter-dependency according to the import to be performed.
table 4.20: File Inter-Denpendency for ImportingFile type
Operations .inf .rgn .itl .cal .adj .trf .dir .ccn .fct .trg
Carrier import X
Region import X X O O
Calendar import X X
Adjustment import X X
Tariff import X O O X
Direction import X O O O O X O
City/country nameimport X O X O
Facilities import X X
Full import X X X X X X X X X X
X: mandatory
O: optional
4.7.6 General Restrictions
Direction files that do not use region files are not supported.
Thus, the region file can be created by assigning prefix name as its name. As many regions asprefixes are therefore created.
Currencies and taxes created during carrier import are not completed and the symbols are leftblank. You must manually enter currency exchange rate (with respect to the referencecurrency) and tax rate.
Upper and lower case letters for names in all files must be respected.
In the tariff files, the EndDateTime field must not be defined. The end of a time period iscalculated with respect to the beginning of the next one.
4.7.7 Compatibility with Version 4715/4740 4.x
This version of the data file is mostly compatible with version 4715/4740 4.x, a few fields areno longer used.
The prefix file is renamed as the region file. Its .pfx extension is replaced by the .rgn extensionbut the content remains unchanged.
Chapter 4
4-98
In the information file, the carrier prefix is no longer optional and the currency is no longerdefined by its symbol but by its full name.
In the direction file, the category is no longer used.
In the calendar file, the Day Type column is added but remains optional.
The facility file is new but remains optional.
4.7.8 Import Processing Duration
The duration of an import depends on:
- computer performance,
- the quantity of data contained in the files,
- the size of the database.
The import generally takes a few minutes. It can be scheduled to be performed when theserver is not being intensively used.
If the import is canceled, no items are imported.
4-99
Chapter 4
4-100
5.1 Use
5.1.1 Overview
The Report application is part of the Alcatel-Lucent OmniVista 4760 CommunicationManagement System (called Alcatel-Lucent OmniVista 4760 Network Management System inthis document).
5.1.1.1 Terminology
Report definitionA definition defines the contents of a report. It consists of:
- Identification properties.
- All the database fields to be retrieved from the database as well as any operations (filter,sort, calculate). Such operations are performed from the Querytool.
- Formatting settings, configured using the Designer.
Predefined definition
In order to meet most current requirements, the application is provided with default definitions.These definitions must be copied in order to then be either customized or generated.
ReportA report is obtained by generating a definition. The content and data formatting of a reportdepend on the definition.An unlimited number of reports can be generated from a report definition.
QuerytoolThis tool is for creating and updating the contents of the definitions. It includes tools forselecting, filtering, and sorting database fields.
DesignerThis tool is used to configure definition formatting. It includes graphic tools for presentingdatabase fields and inserting images, text, formulae, etc.
TemplateThis is a report containing logos, text, and graphic objects. It is mandatory to combine atemplate (even if left blank) with any new report. By default, the user has two sampletemplates.
Database fieldsA database field is an item that is added to a definition to define a precise type of datacontained in the database: cost center, set, date, percentage Absent status, percentagePrivate processed, etc.
If you insert the Duration database field in a definition, you will get 0:25, 1:34, etc. type callduration in the reports generated.
The character § in a database field generates a "carriage return" when reports are output.
5.1.1.1.1 Accounting Terminology
5
5-1
Detailed reportThis type of report is generated from a definition of the same type. The detailed report doesnot group data retrieved from the database.
For example, if you insert the Set and Called number database fields in a detailed definition,the reports generated will list each number called for each set: If a set has dialed the samenumber 25 times, the detailed report will list the set 25 times with the same called number.
Grouped reportThis type of report is also generated from a definition of the same type.This type of report groups data retrieved from the database.
For example, if you insert the Set and the Called number database fields into a groupeddefinition, the reports generated will group identical called numbers for each set together. If aset has dialed the same number 25 times, the grouped report will list it only once with thiscalled number.
5.1.1.1.2 Traffic Analysis Terminology
Traffic analysis counter:These items are primarily generated by the PCX. Their function is to combine operatinginformation to analyze traffic (for example, set release or call duration). These counters areavailable when creating Traffic analysis definitions by inserting database fields.
Time interval:1/2 hour, day, month, year. Each result is the total (accumulated) result for the values enteredin the report filters. A time interval enables counter values to be in effect for a selected timeperiod. The days entered are totaled half-hourly, daily, monthly, or yearly.
5.1.1.2 Operating Principle
The Reports application is used to manage accounting, traffic analysis, VoIP traffic
analysis and alarm reports:
- Design
- Creation
- Generation
- Classification
- Archiving
Note:
Accounting, traffic analysis, VoIP traffic analysis, alarms , RSC and audit reports are available according
to the license installed on the server.
Reports are generated:
- By using the database containing information on calls and PCX network traffic.
- Depending on the chargeable items configured in the Organization tree: cost center, user,trunk groups, directory entry, customer etc.
To always obtain reports containing the latest data, you must have a database that is regularlyupdated by PCXs synchronization.
Caution:
Chapter 5
5-2
For Report Purge/ Cleaning settings:
- The half hourly counter based report is consistent only for 45 days (default value) after whichthe report will not contain any data and so these reports cannot be compared with the daily,monthly or the yearly reports.
- The daily data based report is consistent only for 94 days (default value) after which the re-port will not contain any data and so these reports cannot be compared with the monthly orthe yearly reports.
- The monthly data based report is consistent only for 15 months (default value) after which thereport will not contain any data and so these reports cannot be compared with the yearly re-ports.
To generate a report, you can use:
- The copy of a predefined report definition (customized or not) placed in your personalfolder.See § Generating a Report .
- A definition created according to your needs.See § Creating a Customized Definition .
- The import of a report definition which may come from another user or another server.See § Exporting/Importing a Report Definition .
5.1.1.3 Report Size Limits
The size of generated or exported reports is limited with respect to the number of lines orpages.
To view and modify these parameters:
1. Open the System directory.
2. Expand the branch nmc > NmcConfiguration > GlobalPreferences > ReportingTool>Parameters.
When extracting, the size of generated reports is limited in function of the value (n) of theattribute "Maximum number of lines in database" .
Note 1:
The following rules must be applied:
- If no line is masked for display in the designer:
• The report will not display more than (n) lines.
• If the report is longer than (n) lines, a message indicating that the report is truncated is displayedat the end of the report.
- If a number of lines are masked for display (e.g. Grouped (Summary) reports),
• the limitation continues to apply to the lines extracted by the Querytool and not to the lines dis-played.For example, a report in which the lines are masked to display only totals (via a formula in theDesigner), may thus be based on truncated data. The totals do not then cover all the data in thedatabase and consequently are incorrect. A message indicating that the report is truncated isdisplayed.
When exporting, report size is limited in number of lines for TXT export and in number ofpages for other formats (Html, Pdf, Excel).
5-3
The maximum number of lines for TXTexport is defined by the value of the attribute"Maximum number of lines in TXT format".
The maximum number of pages of Report printouts or exports is defined, for each availableformat, by the value of the following attributes:
- Maximum number of pages in HTML format
- Maximum number of pages in PDF format
- Maximum number of pages in Excel format
Note 2:
The number of pages is calculated according to report viewer data and may be different from the number
of pages effectively printed or exported.
Example: a 10-page report may be printed on 11 hard copy (paper) pages.
5.1.1.4 Restrictions
- To export reports in languages which characters are not ISO LATIN, particular fonts mustbe configured (attributes name of font family for pdf export and Available font style(pdf export) in nmc> <server_name>.
- If there is not sufficient drive space, reports are no longer generated. In this case, amessage is displayed at generation.
- For OmniPCX Office it is not possible to generate:• Accounting reports for DISA calls and some accounting report database fields
(Company directory related fields, etc.).• Traffic analysis reports.• VoIP reports.
- The supported browsers to view HTML reports are:• Microsoft Internet Explorer 7• Netscape Navigator 7.1 and higher• Mozilla Firefox 1.0, 1.5, 2.0
5.1.2 Description
5.1.2.1 Description of the Graphic Interface
By default, the graphic interface is provided with:
- A tree structure including the following files:• An Accounting (*) folder grouping accounting definitions and reports.• A Traffic Analysis (*) folder grouping Traffic Analysis definitions and reports.• Beyond threshold (*) designed for tracking reports.• Voice over IP (*) grouping definitions and reports for VoIP traffic analysis.• Alarms and Events (*) grouping alarm and event definitions and reports.• Templates which group templates for report formatting.
- Three configuration tabs:• Properties: This contains general information on the item selected in the tree
structure.
Chapter 5
5-4
• Querytool: This provides access to the structure specification interface.• Designer: This tab contains functions and graphic tools to improve the layout of
reports generated from the definition.
Reminder:For a clearer view of the tree structure, the right border and be dragged with the mouse (seemodule Interface - Main window § Sizing panels ).
Note 1:
(*) : These files include:
- A folder providing a list of definitions of predefined reports.
- A folder with the name of the user connected to the server. The personal folder is protected via ac-cess rights.
Report availability according to license
table 5.1: License Requirement for ReportsReports Accounting Traffic
analysisBeyondthreshold
Voice overIP
Alarms andEvents
Audit Templates
Licenses
Accounting X X X
Traffic analysis(2)
X X(1) X
VoIP trafficanalysis (2)
X(1) X X
Alarms X X
Audit X X
(1): The Accounting license is mandatory. The Traffic analysis and VoIP traffic analysislicenses are required to access reports concerning these features.(2): Not available for Alcatel Office.
Note 2:
In all the applications the RSC subfolder is visible in the predefined reports folder only if the RSC license
is available.
5.1.2.2 Description of the Icons
Report management is performed via the tree structure, which includes the following symbols:
: folder
: report definition
: generation in progress
: generation successful - shown in blue
5-5
: unmasked report
: report not complete - shown in red (see note)
: template
: accounting records from the PCXs.
: VoIP records from the PCXs.
: total counters calculated on the server from accounting records.
: total counters calculated on the server from VoIP records.
Note:
A report may not be generated because of cancelation by the user or due to a processing error that oc-
curred during the generation process.
5.1.2.3 Identifying Items
The number of items contained in a folder is displayed between brackets to the right of thefolder's name. This is also the case for definitions and their related reports.
A report definition can only be located in a folder. Reports based on the definition are locatedunder this definition.
Report identification complies with the following rules:
- The default name given to the report corresponds to its date and time of generation.
- The name is followed by a list of additional filters applied during the generation process.
The non-modifiable properties that are entered automatically are displayed in the fields initalics.
5.1.2.4 Creating a Folder
In order to classify definitions, it is advisable to create folders in your personal files:
1. Click the desired level in the tree structure.
2. Select Add > Folder. A dialog box is displayed.
3. Enter the name of the new folder and confirm. The new folder is displayed in the treestructure.
The Property tab of the folder contains the following information:
- name
Chapter 5
5-6
- Node type: folder
- Number of Folders: displays the number of folders directly contained in this level.
- Number of Definitions: displays the number of report definitions directly contained in thislevel.
- Author
- Creation date
- Description and Keywords
The modifiable properties of a folder are Name, Description, and Keywords. It is recommendedthat you do not create two files with the same name on the same level.
5.1.2.5 Deleting a Folder
Deleting a folder involves removing all items in this folder.To delete a folder from the tree structure:
1. Click the desired level in the tree structure.
2. Select Delete from the shortcut menu. A confirmation dialog box is displayed.
3. Confirm. The folder is removed from the tree structure.
5.1.2.6 Copying a Folder
Copying a folder implies copying the definitions included in the folder.To copy a folder:
1. Select the desired folder.
2. Select Copy from the shortcut menu.
3. Place the cursor in the tree structure at the location where you want to copy the folder,then select Paste in the shortcut menu. The folder is copied.The option is not available in the shortcut menu when the selected location isinappropriate.
5.1.3 Data Access Restrictions
The assignment of access rights to different users is performed via the Security module.The use of display domains in the Accounting organization impacts the Reports application.Example: Mr. Davenport belongs to the Lambda display domain, he cannot generate reportson individuals of the organization belonging to another domain – see the module Security -Overview .
5.1.4 Copying a Report Definition
To use a predefined report definition, you must make a copy in your personal folder.
1. Select the desired report definition from the predefined reports.
2. Select Copy from the shortcut menu.
3. Select the desired personal folder and then Paste from the shortcut menu. A modifiablecopy is placed at the location you have selected.
5-7
4. Select the new definition and, if necessary, modify its characteristics by following theprocedures described in § Entering Properties for a Definition .
5.1.5 Modifying a Report Definition
All the definitions contained in your personal folders may be modified. The changes made viathe Querytool or Designer must be saved by .
If you modify a definition from which you have already generated reports, the reportswill be deleted for consistency.If you want to keep the reports, you can either duplicate the definition in order to modify itscopy, or export the reports beforehand in the format of your choice (TXTF, HTML, PDF, Excel)(see § Scheduling Report Generation ).If you modify the structure specification of an item, you must also specify the change inthe layout of the report through the Designer option.
5.1.6 Exporting/Importing a Report Definition
To reuse definitions on other servers or under different user accounts, use the export feature.The definitions are exported in text format and may be edited using a standard editor. Alldefinitions, including the predefined definitions, may be exported.Export procedure:
1. Select the desired definition.
2. Select Export from the shortcut menu. A dialog box is displayed.
3. Enter a file name (.def) and a location, then confirm. The file is saved.Import procedure:
1. Position the cursor in the tree structure at the desired location.
2. Select Import from the shortcut menu. A dialog box is displayed.
3. Select the desired file (.def), and confirm. The definition is created in the tree structure. ItsAuthor field is assigned the name of the connected user.
5.1.7 Generating a Report
A report is generated by one of the following sources:
- A copy (customized or not) of a predefined report definition placed in your personal folder,§ Copying a Report Definition .
- A definition customized to meet your needs, § Creating a Customized Definition .
- The import of a report definition which may come from another user or another server, §Report Export Options .
The generation command is identical in the three cases.
To generate a report from a definition:
1. Select the desired definition from one of your personal folders.
2. Select Generate Report from the shortcut menu.
Chapter 5
5-8
3. Enter any filter values during generation, then confirm. A timer (presenting generation dateand time) is displayed below the definition.
When generation is complete:
- The timer is replaced by the colored Report icon:• Blue: report generation completed successfully.• Red: there was an error while generating.
- Generation Time is displayed in the Properties tab.
To view the generated report, double-click the icon representing it. The report is displayed in aseparate window – see § Displaying a Report on the Screen .
Remarks:
- Report generation, export, and printing can be scheduled using the Scheduler, § Scheduling ReportGeneration .
- Generation can also be interrupted, § Interrupting Report Generation .
5.1.8 Generating an Unmasked Report.
See module Security - Overview § Generating an Unmasked Report.
5.1.9 Interrupting Report Generation
To interrupt report generation while in progress:
1. Select the icon which shows generation progress.
2. Select Cancel Generation in the timer shortcut menu.
The timer is replaced by the Report fault icon displayed with the following status: The
generation process has been canceled.
5.1.10 Scheduling Report Generation
§ Configuring the Server for Network Export Scheduling – Scheduling is used for reportgeneration, which is useful in the case of lengthy data processing. Repeated report generationcan also be scheduled via the Scheduler.Scheduling also offers additional options, that are not available with immediate generation:
1. Select the desired report definition from your personal folders.
2. Select Scheduler... from the shortcut menu.
3. Enter any filter values when generating. An Options dialog box is displayed.
4. Select one or more options: Print, Export To File, E-mail and Check memory for largeexported reports, depending on the operations you want to perform.• Print: as soon as it is generated, the report is sent to the default printer on the server.
This printer must be accessible at the time of printing.• Export To File: by selecting this option, the format of the export file (TXT, HTML, PDF,
5-9
or Excel) and its location are requested (via the Wizard), see § Report Export Options .• E-mail: same as the previous option. Enter an E-mail address (replaces the
designated directory and file name – see § Report Export Options ).• Check memory for large exported reports: This option ensures best performance for
exporting the reports with the scheduler such as duration of export, maximum numberof simultaneous exports, etc. This can be used only for the export of very large reports,but accordingly the performance can decrease. The simultaneous export of reports isnot advised.
5. Select Simple job (independent job) or Synchronized task (integrated with anotherjob). The Scheduler is displayed.
6. In the Scheduler, select the As Scheduled option, then schedule the job – see themodule Scheduler - Overview § Scheduling
7. Click Apply.
Notes 1:
The report definitions associated with a scheduling operation are not protected and may be modified be-
fore automatic generation occurs. They should be named to differentiate them from other definitions. If a
scheduled report is generated after its definition has been modified, a blank report is produced. To avoid
this, reschedule definition execution.
Notes 2:
With the Directory application, it is not possible to display the destination of a scheduled report sent via
mail. This information can be edited in the SQL table.
5.1.11 Scheduling Report Generation for a Customer List
This scheduling mode is available only with the RSC license.To schedule generation of reports for a list of customers:
1. Select the desired report definition which includes a column Customer associated with afilter, from your personal folders.
2. Select Schedule customer list from the shortcut menu. The List of customers dialogbox is displayed.
3. Select the list of customers for report generation. To generate the reports for all thecustomers select the option Complete list. The Options dialog box is displayed.
4. Select the filters for report generation.
5. Select one or more of the following options: Print, Export To File, or E-mail, dependingon the operations you want to perform.• Print: as soon as it is generated, the report is sent to the default printer on the server.
This printer must be accessible at the time of printing.• Export To File: by selecting this option, the format of the export file (TXT, HTML, PDF,
or Excel) and its location are requested (via the Wizard), see § Report Export Options• E-mail: same as the previous option. Enter an E-mail address (replaces the
designated directory and file name – see § Report Export Options ).
Note 1:The file format for export or mail is the default format and it can be overwritten by the format chosenfor each RSC customer entry in the Directory using the Report preference tab (for more informa-tion refer to module Directory - Company tab § Managing Entries ).
Chapter 5
5-10
Note 2:The default e-mail address is used when the e-mail address is not specified in the RSC customerentry in the Directory (customer contact tab) (for more information refer to the module Directory -Company tab § Managing Entries ).
6. Select Simple job (independent job) or Synchronized task (integrated with anotherjob). The Create a task in the Scheduler dialog box is displayed.
7. In the Start Date, select the As Scheduled option, then schedule the job – see the moduleScheduler - Overview § Scheduling
8. Click Apply.When the generation is complete you will find the generated reports equal to the number ofcustomers you have selected, under the report definition.
Note 3:
The report definitions associated with a scheduling operation are not protected and may be modified be-
fore automatic generation occurs. They should be named to differentiate them from other definitions. If a
scheduled report is generated after its definition has been modified, a blank report is produced. To avoid
this, reschedule definition execution.
Note 4:
In case of failure during the scheduled export of report, it is possible to continue export instead of re-
exporting from the beginning of the list.
In case of failure during mail export of report, the export operation can be bypassed & it can be sent later.
5.1.12 Displaying a Report on the Screen
Reports are viewed in a separate window. This allows advanced features for reviewing reports.Each time you double-click a report icon in the tree structure, a report appears in a separatewindow. Displayed reports are accessed via the icons in the toolbar located at the bottom ofthe main screen.
5.1.12.1 Description of a Display Window
5-11
Figure 5.1: Directory Entry Window
The main parts of the graphic interface are:
- The report's group header list (1)
- An area for report display (2)
The commands available are (3):
- Export
- Search
The interface also has:
- Navigation buttons to navigate through the report (4)
- A slider bar (4)
- A scrollbar for the page displayed (7).
- Pagination display (5)
Report content consists of data retrieved from the database and all incorporated graphic items(6).
5.1.12.2 Navigating Through the Report
Use one of the following methods to navigate within the report:
1. The navigation buttons and slider in the bottom part of the screen:to go to the first page.
to go to the previous page.
to go to the next page.
to go to the last page.
for quick move.
2. Use direct access to the group headings.The left side of a display window lists the group headings defined in the definition.To view data related to one of these group headings, click the desired heading.
3. Use the scroll bars in the area that displays the report contents.
5.1.12.3 Using FeaturesTo export a report:
1. Display the report on the screen.
2. Click Export. The Export window is displayed.
3. Select the type of export by clicking File or E-mail, then Next.For a File: export.1. Select the format the report is to be saved in: TXT, HTML, PDF, Excel format. Click
Apply. A dialog box is displayed.2. By default, the exported file has the same name as the report. You can change this
Chapter 5
5-12
name, then browse to specify the desired file saving location.3. Click Export.
Report data is exported.For an E-mail: export.1. Enter the E-mail address(es) of the recipient(s) and any additional text to be included.
Click Next.2. Select the format the report is to be saved in: TXT, HTML, PDF, Excel format. Click
Apply.To print a report:
1. Display the report on the screen.
2. Click Print. A print dialog box is displayed.
3. Select the printer to be used and configure print settings. Enter the report pages that are tobe printed. Confirm. Printing begins.A dialog box is displayed during the entire printing process. You may interrupt printing fromthis dialog box by clicking Cancel.
To search for data in a report:
1. Display the report on the screen.
2. Click Search. A dialog box is displayed.
Figure 5.2: Data Search Window
3. Complete the edit box, then click . The search process is launched. The occurrences
found by the search process appear highlighted in the report and the number ofoccurrences appears in the lower part of the search window.
to go to the first occurrence.
to go to the previous occurrence.
to go to the next occurrence.
to go to the last occurrence.
5.1.13 Report Export Options
§ Configuring the Server for Network Export Scheduling – A report can be exported in twoways:
5-13
- By clicking the icon in the displayed window of the report to be exported.
- Or, by selecting Export in the shortcut menu that appears on the instance of the report.Reports are exported via a graphical wizard:
1. Select the type of export destination, File or E-mail. Then click Next.
2. Select export format: TXT, HTML, PDF, or Excel:• TXT: The exported report is presented in the form of tables corresponding to the
different columns selected in the Querytool. Formulas and charts are not exported.• PDF: The report can be viewed with Acrobat Reader. The format of the exported report
is similar to that displayed on screen except that the vertical navigation tree does notappear.
• HTML: The report is exported to a directory with the same name as the file. Thisdirectory also contains graphic items saved separately as PNG format files. The reportcan be viewed using an HTML browser. The format of the exported report is similar tothat displayed on screen (without the vertical tree).
• Excel: The report is presented in the form of Excel files compatible with Microsoft®Excel 97. The format of the exported report is similar to that displayed on screen(without the vertical navigation tree - that is not shown). Charts are not exported.
3. For an export to file: Enter a name and a location for the exported file. By default, it takesthe name of the definition from which the report originated, followed by its generation date.File name may be modified but the extension for the format selected must be kept: txt,html, pdf or xls.For an export by E-mail: The procedure is similar to exporting to a file. The wizardrequests the entry of one or more destination addresses that must be separated by a “,”and, if required, the entry of attached text.A file name and location are not needed because the default name (see exporting to a file)is used.For an export to a printer: Printing can only be performed on the default printer declaredon the server.
5.1.14 Creating a Customized Definition
An accounting definition cannot be created in the traffic analysis, beyond threshold, VoIP oralarms directory and vice-versa.To create a complete definition:
1. Declare the new definition in the tree structure.See § Declaring the New Definition in the Tree Structure. .
2. If required, update the Properties of the definition in the Property tab.See § Entering Properties for a Definition .
3. Define the report's contents by selecting the database fields and operations to beperformed (sort, filter, total, average). These operations are performed in the Querytooltab.See § Defining the Contents of the Definition - the Querytool .
4. Format the items selected via the Querytool by inserting formulas, graphics, etc. Theseoperations are performed with the Designer.
Chapter 5
5-14
Reports can now be generated from this definition. They will contain data from the databaseaccording to:
- The data selected with the Querytool.
- The formatting applied with the Designer.
The reports are displayed in a separate window – see § Displaying a Report on the Screen
5.1.14.1 Report Data Sources - Selection Criteria
The accounting, traffic analysis, and VoIP traffic analysis reports can be generated by usingtwo different data sources:
1. Data generated by the PCX (records and counters).
This data is extracted from files retrieved at each synchronization between theAlcatel-Lucent OmniVista 4760 Network Management System server and the PCX. Thesefiles contain the accounting, VoIP records, the traffic analysis counters and the PCXmodification history (Audit).
2. The total counters generated by the Alcatel-Lucent OmniVista 4760 Network ManagementSystem server.
Permanent management of these calculated counters is performed using the datagenerated by the PCX. Total counters are assigned to each chargeable entry in theOrganization.
These counters help you to optimize the time required to generate the most common types ofreports. Total report definitions are grouped in the same folder.Total report restrictions
- Unlike a accounting record-based detailled report, a report of totals cannot be establishedon several levels of the same branch of the organization.Because a counter assigned to a level n inherits totals from the same counter on lowerlevels n-1, you must establish reports at the same level (n) in the tree structure.
Figure 5.3: Organization TreeStructureIn the example tree structure shown, you can generate a total report on:• Either, a combination of levels D, L, and P.• Or, only on level S.
- Moving a tree structure item by a copy-paste operation is only effective for the total ofrecords in the database. The total for purged (cleaned) records will not reflect the move inthe organization tree.
5-15
5.1.14.2 Declaring the New Definition in the Tree Structure.
A - Accounting
1. Select a personal tree structure level in the Accounting folder.
2. Select Add > Definition from the shortcut menu. The definition creation wizard isdisplayed.
table 5.2: Accounting Reports Creation Parameters(1) Source (2) Item (3) Type
Accounting records/
Detailed
Grouped
Total counters—
day
month
year
Entity
Organization
Project
Carrier
City/Country name
Direction
3. Specify the Source (1) of data to be used by the definition: accounting records or totalcounters. A definition based on total counters will significantly reduce the time required togenerate the corresponding reports. Click Next.
4. If your definition is based on total counters, select the targeted item (2). This choicedetermines the list of fields subsequently available in the Query tool.
5. Select Report type (3): Detailed or Grouped, then click Next.The wizard now displays a list of templates. By default, the list contains the two presettemplates: Template and Compact template. If you have previously defined templates inthe application, they are also listed.
6. In the list, click the template to be applied to all reports generated from the definition.
7. Name your definition in the corresponding field, then click Next. The wizard displays a newdialog box.
8. Enter a brief Description and Keywords characterizing the data targeted by the newdefinition.
Chapter 5
5-16
9. Click Apply. The wizard is closed.The name of the new definition is displayed in the tree structure. The definition's Propertytab can be updated.See § Entering Properties for a Definition .
Note 1:
At any time, you can return to a previous menu in the wizard menus by clicking Previous.
B - Traffic analysis
1. Select a personal tree structure level in the Traffic analysis directory.
2. Select Add > Definition from the shortcut menu. The definition creation wizard isdisplayed.
table 5.3: Traffic Analysis Reports Creation Parameters(1) Observation
(analysis) period (2) Observed item (3) Type
Attendant Group
1/2 hour Attendants Detailed
Day Called Numbers
Month Sets Grouped
Year DECT/PWT handsets
ADPCM channels
Base stations
DECT/PWT system
5-17
(1) Observation(analysis) period (2) Observed item (3) Type
Trunk Groups
3. Select Observation period (1), then click Next.
4. Select Observed item (2), then click Next.
5. Select Type of report (3), then click Next.The wizard now displays a list of templates. By default, the list contains the two presettemplates: Template and Compact template. If you had previously defined templates inthe application, they are also listed. In the list, click the template to be applied to all reportsgenerated from the definition.
6. Name your definition in the corresponding field, then click Next. The wizard displays a newdialog box.
7. Enter a brief Description and Keywords characterizing the data targeted by the newdefinition.
8. Click Apply. The wizard is closed.The name of the new definition is displayed in the tree structure. The definition's Propertytab can be updated.See § Entering Properties for a Definition .
Note 2:
At any time, you can return to a previous menu in the wizard menus by clicking Previous.
C - Beyond threshold
1. Select a personal tree structure level in the Beyond threshold directory.
2. Select Add > Definition from the shortcut menu. The definition creation wizard isdisplayed.
3. Select report type: Detailed or Grouped, then click Next.The wizard now displays a list of templates. By default, the list contains the two presettemplates: Template and Compact template. If you have previously defined templates inthe application, they are also listed.
4. In the list, click the template to be applied to all reports generated from the definition.
5. Name your definition in the corresponding field, then click Next. The wizard displays a newdialog box.
6. Enter a brief Description and Keywords characterizing the data targeted by the newdefinition.
7. Click Apply. The wizard is closed.The name of the new definition is displayed in the tree structure. The definition's Propertytab can be updated.See § Entering Properties for a Definition .
Note 3:
At any time, you can return to a previous menu in the wizard menus by clicking Previous.
Chapter 5
5-18
D - Voice over IP
1. Select a personal tree structure level in the VoIP folder.
2. Select Add > Definition from the shortcut menu. The definition creation wizard isdisplayed.
3. Select the data source to be used by the definition: Records or Total counters. Adefinition based on total counters will significantly reduce the time required to generate thecorresponding reports. Click Next.
4. Select report type: Detailed or Grouped, then click Next.The wizard now displays a list of templates. By default, the list contains the two presettemplates: Template and Compact template. If you have previously defined templates inthe application, they are also listed.
5. In the list, click the template to be applied to all reports generated from the definition.
6. Name your definition in the corresponding field, then click Next. The wizard displays a newdialog box.
7. Enter a brief Description and Keywords characterizing the data targeted by the newdefinition.
8. Click Apply. The wizard is closed.The name of the new definition is displayed in the tree structure. The definition's Propertytab can be updated.See § Entering Properties for a Definition .
Note 4:
At any time, you can return to a previous menu in the wizard menus by clicking Previous.
E - Alarms and events
1. Select a personal tree structure level in the Alarms and Events folder.
2. Select Add > Definition from the shortcut menu. The definition creation wizard isdisplayed.
3. Select the data source to be used by the definition: Alarms or Events, then click Next.
4. Select report type: Detailed or Grouped, then click Next.The wizard now displays a list of templates. By default, the list contains the two presettemplates: Template and Compact template. If you have previously defined templates inthe application, they are also listed.
5. In the list, click the template to be applied to all reports generated from the definition.
6. Name your definition in the corresponding field, then click Next. The wizard displays a newdialog box.
7. Enter a brief Description and Keywords characterizing the data targeted by the newdefinition.
8. Click Apply. The wizard is closed.The name of the new definition is displayed in the tree structure. The definition's Propertytab can be updated.See § Entering Properties for a Definition .
Note 5:
5-19
At any time, you can return to a previous menu in the wizard menus by clicking Previous.
Caution:
When fields are selected in the Querytool, the "Not empty" filter must be added, otherwise empty
lines may appear at report generation.
F - Audit
1. Select a personal tree structure level in the Audit folder.
2. Select Add > Definition from the shortcut menu. The definition creation wizard isdisplayed.
3. Select report type: Detailed or Grouped, then click Next.When Detailed is selected, the wizard now displays a list of templates. By default, the listcontains the two preset templates: Template and Compact template. If you havepreviously defined templates in the application, they are also listed.
4. In the list, click the template to be applied to all reports generated from the definition.
5. Name your definition in the corresponding field, then click Next. The wizard displays a newdialog box.
6. Enter a brief Description and Keywords characterizing the data targeted by the newdefinition.
7. Click Apply. The wizard is closed.The name of the new definition is displayed in the tree structure. The definition's Propertytab can be updated.See § Entering Properties for a Definition .
5.1.14.3 Entering Properties for a DefinitionTo update the properties of a definition:
1. Click the definition in the tree structure,
2. Click the Property tab in the edit area. The following properties are displayed:• The Name of the definition. This is displayed in the tree structure.• Node Type. This is the type of item currently selected in the tree structure.• Definition Type. This can be either a grouped or detailed type.• Number of Reports. This is the number of reports generated from the definition. If this
number is not zero, this means that there are reports under the definition.• Author.• Creation Date.• Any Description entered when creating the definition.• Keywords, entered when creating the definition.
The modifiable properties are name, description, and keywords.See § Defining the Contents of the Definition - the Querytool .
5.1.14.4 Defining the Contents of the Definition - the Querytool
With the Querytool, select the data and the operations to be included in the definition. Whengenerating a report, the Querytool accesses the database in order to retrieve, sort, and classifythe data searched for, depending on the selection made in the Querytool.
This tab is only available for report definitions.
Chapter 5
5-20
To define the contents of a definition:
1. Select the desired definition in the tree structure.
2. Access the Querytool graphic interface by clicking the Querytool tab.
3. After configuring in the Querytool, click (in the top toolbar) to save your
settings. The contents of the Designer are updated automatically.
4. Then access the Designer interface to modify the formatting.See § Defining Presentation - the Designer .
5.1.14.4.1 Description of the Querytool Interface
The Querytool can be divided into two different parts:
- The upper part contains the list of available database fields for the selected definition.These database fields are classified by similarities. The § symbol represents the carriagereturn that is performed in the field in the report.
- The lower part contains the fields selected in the upper part and offers sorting, multi-criteriafilters, and counting functions.
Figure 5.4: Query Tool Window
5.1.14.4.2 Adding a Field to the Definition
To add a field to the definition, search for it in the fields list of the Querytool (upper part) thendouble-click it. The field is then inserted into the lower part in a new column located to the right
5-21
of any existing columns. You can insert the same database field several times to applydifferent filters to it.
Important:
For a total accounting report, the Call Type field must be added and a filter including Incoming
Calls or Outgoing Calls and excluding Inc./Out. calls configured. See § Defining a Filter .
Note:
The field Customer (in Organization subfolder) is mandatory if the report is to be generated for several
RSC customers.
5.1.14.4.3 Deleting a Field from the Definition
To delete a field from the definition, open the shortcut menu on the border of the columncontaining the field, then select Delete field. The column is deleted and the other columnsmove to the left to fill the free space created.
Note:
To open the shortcut menu correctly, your cursor must be positioned on the top border of the column that
contains the column text.
5.1.14.4.4 Changing the Order of the Columns
The order of the columns may be modified by drag-and-drop.
- Click the top border of the column you want to move and hold down the mouse button.
- Drag the mouse between two columns of your choice. A dotted square representing a"move" is displayed.
- Release the button to position the column at the desired location.
5.1.14.4.5 Configuring Column Attributes
Each selected field is placed in a column where attributes can be applied (sort type, sortposition, operations, etc.).
Modifying a Field Value
The field assigned to the column can be replaced:
- by another database field,
- by a complex expression.
Replacing a database field with another database field
Select the database field to be assigned to a column in the Field value list area.
Entering a complex expression
Caution:
Multiplication and division operations must not be performed on fields in the Querytool. This is
because the result obtained is equal to the total of the operation of the fields (for example: Total
(field A ÷ field B) and not the operation of the totals of the fields (for example: Total field A ÷ Total
field B).
To define a complex expression such as PCX cost + charged cost X 1.10:
-
Chapter 5
5-22
button located to the right of Field value. The expression editor is displayed in a
separate window.
The expression editor consists of:
- A digital keypad similar to that of a calculator.
- A list of available items.
- An edit box in which the current expression is displayed.
Figure 5.5: Expression Editor Window
To enter a formula:
- Click on the desired items and digital operators. All the items are progressively displayed inthe edit box.
To delete part of the expression:
- Click DEL. The item located to the far right is deleted.
To finish creating the expression, click OK. The field is displayed in the column.
Modifying the Label of the Field Entered in the Report
By default, reports have labels corresponding to the database field names in the definition.
To customize a database field label:
- Select the desired column, then modify the field label.
- Position the § character in the string to apply a carriage return in the field in the report.
5-23
Note:
The field labels Name (extended format) and FirstName (extended format) for all the definitions, can
be changed by editing the LdapAttributes dictionary (field RT_utf8name and RT_utf8firstname), using the
CustomDict tool. For more information refer to module Interface - Customizing dictionaries .
Performing a Mathematical Operation on a Field
Mathematical functions can be applied to fields in order to optimize data use. Functionsapplicable to a field depend on:
- The type of data inherent to the field (text or numerical).
- The type of report: detailed or grouped.
When a detailed report is created, you cannot include calculations of averages or totals (forexample) in the Querytool. You may define them in the Designer by inserting a formula.
Group byFor group type reports, this is the default operation. Similar data inherent to the selected fieldis grouped together.
CountThis operation allows occurrences of data in a field to be counted.
Example 1:
In a grouped type definition, insert the Called Number field twice using two different columns. Assign the
Group By operation to one of the columns and Count to the second column.
The report will show the number of times each number was called.
MinimumThis attribute retrieves the data item with the lowest value from the concerned field.
Example 2:
Prepare a report showing the shortest calls made for each set. The report is of the grouped type and in-
cludes the Set and Duration fields.
table 5.4: Field values for generating report of shortest calls for each set — ExampleQuerytool:
Field value Set Duration
Field label Set Duration
Operation Group By Minimum
Sort type Ascending Ascending
Sort Order 1 2
Display Detail Detail
MaximumThis attribute retrieves the item of data with the highest value from the concerned field.
Example 3:
Prepare a report showing the most expensive calls for each Cost Center. The report is of grouped type
and includes the fields, Set and Invoiced Cost.
Chapter 5
5-24
table 5.5: Field values for generating report of expensive calls for each cost center — ExampleField value Cost Center Invoiced Cost
Field label Cost Center Invoiced Cost
Operation Group By Maximum
Sort Type Ascending Ascending
Sort Order 1 2
Display Detail Detail
TotalThis attribute totals all the data of the concerned field.
AverageThis attribute calculates and returns the average of all data of the concerned field.Inconsistency is tracked. For example, the minimum or the maximum operations cannot beapplied to the Cost center and Set fields.
Sorting Field Data - Type of Sorting
This attribute defines a sorting method to be followed for the data in the selected fields beforeit is included in the reports. You can select Ascending or Descending, or not select a filter.If the display is equivalent to a group header, the type of sorting and the order areautomatically updated. However, the sort type may be modified depending on thecharacteristics of the related database.
Defining a Sorting Order between Columns
This attribute is not available if the the display is Group Header or Not Present. This attributedefines a sorting order between columns. Data in the field with sorting position number 1 issorted first. Then, sorting is performed for the column with sort position number 2, then 3, andso on. If the attribute is left blank, no sorting is applied.
Defining a Filter
Filters are used to create targetted reports to be defined. Filters are defined using the selectioncriteria editor to facilitate entry of multiple criteria.
Criteria may be applied to fields that do not appear when reports are printed. These fields mustinclude the Display attribute set to Not Present.
Filtering date:To filter data in the database by time, apply a filter to the Date/Hour database field. You mayselect a suggested filter value (yesterday, last week, the two last months, etc.) or enter a date,complying with the following entry format:
- French: JJ/MM/AA HH:mmHH: time (24-hour clock),
- English: MM/DD/YY hh:MM AM or PMhh: time (12-hour clock) AM (morning) or PM (afternoon)
To filter on a day in all totalled, detailed, hit-list, and daily (except for time type) reports, filteron 00:00, i.e.:
- In French: date = JJ/MM/AA 00:00
5-25
- In English: date = MM/DD/YY 00:00 AM
Also use this rule to filter monthly reports for a given month.
Filter Editor
This is a tool that enables one or more selection criteria to be defined. Multi-criteria filters canbe applied by using the AND and OR logical operators (e.g. cost center 25 AND invoiced cost1000).
Syntax is as follows:
Field name [comparison operator] [free entry] or selection in a list.
[comparison operator] = equal to, not equal to, contain, begin with, etc.
[free entry] = this can be a text or a numerical value. Use values consistent with the type ofdata inherent to the field (text or numeric).
To add a line to a filter:
1. Click +. A blank line is displayed.
2. Select the logical operator (AND or OR) that defines the relationship between the newcriterion and the previous one.
3. Specify the filter on the new line.
4. Click End to close the filter editor. The full value of the filter is displayed in the Filter field.
To delete a line from a filter:
- Click the button (located just before the filter line to be deleted). The line is deleted fromthe expression editor.
To delete all filters:
1. Delete all text entered in the filter fields.
2. Click OK to close the filter editor.
Enabling Entry of the Additional Filter for Report Generation
If you want to be able to add filters during report generation, select the Generation time filteroption.
This option increases the flexibility of reporting as it is no longer necessary to create a reportfor each different report filter.
Example:
Define a selection criteria for the Date/hour and Set fields, then enable the Generation Time Filter op-
tion for these two criteria. Thus, before each report is generated, you can define the appropriate filter for
these two fields respectively.
Selecting Field Display Mode
For each column, three display modes are offered:
Not PresentThe data of the field is not displayed in the report. You may, however, apply a selectioncriterion to this field in order to filter the data of the other fields of the definition.
Detail
Chapter 5
5-26
All data in the field is entered in the report.
Group HeaderSelect this display to get an overview and improved readability of the report. Group Headerdisplay presents a horizontal display of data in the field to avoid unnecessary repetition in acolumn.
The first group header is automatically placed at the beginning of each new page. Whether ornot the field can be sorted depends on the display. See § Sorting Field Data - Type of Sorting .
Limiting the Amount of Data in the Report (Hit List Report: _)
The Hit-list Report option is useful to prepare reports showing classifications, for example:
- The sets totaling the longest call times.
- The most expensive calls.
- The least expensive directions.To obtain a Hit-list report:
1. Assign a Sort Type (ascending or descending) to the fields concerned,
2. Check (select) the Hit list report box at the bottom left and enter a value in the Hit-Listfield to limit the number of data items classified in the report.
5.1.14.4.6 Examples of Criteria Expressions
The equal to, less than, more than operators, etc.
- Cost Center equal to 248This expression selects cost center number 248.
- Called Number beginning with 06.This expression selects numbers beginning with 06 (e.g. 06504030, 0602030, etc.)Advanced expressions are edited on several lines.
- Communication type equal to data AND Duration greater than 600 AND invoiced costgreater than 5.This expression selects data transmissions greater than 6 min and with a cost greater than5 Dollars (if the Dollar is the currency of the rate applied).
5.1.14.5 Defining Presentation - the Designer
The Designer has the graphic capability to design formatting to be applied to reports based ona definition.
By default, the formatting associated with a definition consists of:
- Template items (see § Using Templates ) selected at definition creation.
- Fields selected using the Querytool. The fields and their labels are automatically placed inthe report. They are outlined, aligned, and joined together.
A magnetic grid makes the placement and alignment of items easier.
Important:
The Designer includes the page formatting of the default printer. If connecting to the printer is dif-
ficult (slow network, automatic standby, etc.), tab display is slow.
5.1.14.5.1 Report Structure
5-27
To facilitate report formatting, the Designer divides the report into several independent areas.By default, the report is made up of 7 adjacent areas divided from top to bottom into:
1. Report header
2. Page Header
3. The group header, if field Display is Group Header in the Querytool
4. Detail
5. The group footer, if field Display is Group Header in the Querytool
6. Page footer
7. Report footer
Six areas form three inseparable pairs:
- Report Header/Report FooterThe items which make up these areas are displayed at the start and end of the report.
- Page Header/Page FooterThe items that make up these two areas are displayed at the top and bottom of each page.
- Group Header/Group FooterIf the report definition includes Group header fields, the data items are located before andafter the fields in the Detail area.
The Detail area is the main area of the report because, by default, it contains all the Detaildisplay mode database fields.
The items that can be added to each area are described in the table in § Using the ToolbarIcons and Shortcut Menu Icons .
5.1.14.5.2 Using the Toolbar Icons and Shortcut Menu Icons
You can insert several items, such as, text boxes, formulas, graphics, etc. by using:
- Dynamic toolbar icons:: Save settings
: Formatting for printing.
: Insert label
: Insert database field
: Insert formula
Insert image
: Insert chart
Chapter 5
5-28
: Insert date (of generation)
: Insert page number
: Insert details of the filter applied
: Insert the report save path.
: Reduce to the minimum (optimize field height).
- Each area's shortcut menu. Right-click the relevant area to access the availablecommands.The commands have the same effects as the icons, plus there are the following additionalcommands:• Modify background color.• Insert a page break.• Change grid size.• View (allows calculation results to be used).
The table below shows which items can be inserted according to the area in the report.
X: function available
table 5.6: Items Inserted in ReportReportheader
Pageheader
Groupheader
Detail Groupfooter
Pagefooter
Reportfooter
Back-groundcolor
X X X X X X X
Insertatextbox
X X X X X X X
Insertadatabasefield
X X X
Insertaformula
X X X X
Insertanimage
X X X X X X X
5-29
Reportheader
Pageheader
Groupheader
Detail Groupfooter
Pagefooter
Reportfooter
Insertachart
X X X X
Insertaspecialfield
X X X X X X X
Insertapagebreak
X X X X X
Visibility(scope) X X X X
Changegrid (table)size
X
Note:
The headers that can be inserted into group headers and footers are those located in the upper areas.
Grid resolution is common to all areas.
5.1.14.5.3 Modifying Area Background Color
This feature is only available in the area's shortcut menu.To apply the desired color to an area's background:
1. Position the cursor in the area where you want to change color.
2. Select the desired color in the color palette of the Background Color submenu.
5.1.14.5.4 Inserting a Text Box
Use this command to add comments and notes to reports generated from the definition.The insertion procedure is as follows:
1. Position the cursor in the area where you want to insert text.
2. Select Insert Text Field from the shortcut menu. A new box is automatically inserted in thearea with the default text, "Text". You can also drag the icon to the desired area.
3. Double-click the text box to edit its properties.
4. In the Properties window:• Specify attributes, font and color.• Enter text in the Text field. A preview window is continuously updated. Before
validating text, you can see exactly how the text will appear in the report.
5. Click Apply. Your customized text box is displayed in the related area.
Chapter 5
5-30
6. In the Text field, use the shortcut menu to add a border, if required (see § Adding a Borderto, and Removing a Border from, an Item ).
5.1.14.5.5 Inserting a Database Field
You can insert database fields (previously selected in the definition Querytool) into the report:To insert a database field:
1. Position the cursor where you want to insert the database field.
2. Select Insert Database Field from the shortcut menu. The list of available fields isdisplayed in a separate window. You can also drag the icon to the desired area.
3. You can select the field by double-clicking it. The field is displayed in the report.
5.1.14.5.6 Inserting a Formula
A formula may include mathematical operations combined with database fields.The fields must be present in the Detail area when the formula is created.
Example:
Average (ISDN Cost) + Total (Invoiced Cost) * 1.10
Formulas are created by using a Formula Editor.
Ratios and averages with figures after the decimal point cannot be generated in a report.To insert a formula:
1. Position the cursor where you want to insert a formula.
2. Select Insert Formula from the shortcut menu. You can also drag the icon to the
desired area. The Formula Editor is displayed. This is a separate graphic interface usedto create formulas.
Figure 5.6: Formula Editor Window
This editor includes:
5-31
- A digital keypad similar to that of a calculator.
- An interactive area that displays the list of mathematical functions available (average, total,maximum, minimum, count) and numeric database fields.
- An edit box that displays the formula currently being entered.
To create a formula, click the different keypad keys and functions. You are helped with dataentry and the interactive area is updated as you create the formula.
To delete part of the expression in the edit box, click DEL.The item on the far right of the field is then deleted.
To end formula creation, click Apply.
5.1.14.5.7 Customizing Cost Display
Cost display may be customized (font, thousands separator, number of decimal places, etc.)To customize cost display:
1. Select a database field or formula and click Properties in the shortcut menu. A dialog boxis displayed.
Note:Several fields and/or formulas can be selected simultaneously.
2. Modify display properties.
3. Click Apply to save your changes.
5.1.14.5.8 Inserting an ImageTo insert a graphic:
1. Position the cursor where you want to insert an image,
2. Select Insert Image from the shortcut menu, a browser window is displayed. You can alsodrag the icon to the desired area.
3. Select the image to be inserted, then click Open. The image is inserted in the selectedarea.
Note:
The browser window has a preview window.
The image inserted must be in JPG, JPEG, or GIF format.
The maximum size allowed per image is 32,000 bytes (i.e. 31.25 KB).
5.1.14.5.9 Inserting a ChartTo insert a chart:
1. Position the cursor where you want to insert the chart.
2. Select Insert Chart from the shortcut menu. The Chart Properties/Chart Type window isdisplayed. You can also drag the icon to the desired area.
3. Select the type of chart desired by clicking its symbol: bar chart, curve, pie chart, plot chartand stacked bar chart and multi-counter pie chart. Click Next. The Chart Properties/ChartData window is displayed.
Chapter 5
5-32
4. Select the database field to be assigned to the X axis.
5. Select the database field(s) which is (are) to be assigned to the Y axis in the Data Sorcesand Chart Data lists.
6. Click Next. The Chart Properties window is updated with 4 tabs:• Chart Title: Enter the label, the names of the axes and their location. A preview
window displays the chart.• Axes: Validate label names and their orientation (vertical or horizontal) in the chart.• 3-D Style: Adjust the depth, elevation, and rotation levels to be applied to the chart.
Some of the 3-D effects are not available according to the type of chart, e.g. rotationfor the plot chart.
• Thresholds: Specify a Min No. Slices for the chart and the Threshold to limit thedisplay of many small values by grouping them into a single entry called Others.
7. Click End. The chart is displayed in the report.To edit a chart's properties:
1. Select the chart,
2. Select Property from the shortcut menu. The Chart property window is displayed.To resize the chart:
- Drag the anchor points surrounding the chart.To move a chart within an area:
1. Click the center of the chart to select it. An intersecting arrow cursor is displayed.
2. Drag the chart to the desired location.
5.1.14.5.10Inserting a Special Field
Special fields that can be inserted into a report are:
- The saved path (location) of the report on the server.
- Generation date
- Page number
- FilterTo insert a special field:
1. Position the cursor where you want to insert the special field.
2. Select Insert Special Field > Date/Page Number/Filter from the shortcut menu. Thespecial field is displayed in the report with modifiable properties matching those of a textbox.
You can insert special fields by dragging the following icons onto the report:
: Report path
: Report generation date
: Page number
5-33
: Filter
The special filter field enters details of any filters (applied during report generation) in thereport.
5.1.14.5.11Inserting a Customer Field
This feature is subject to RSC license.Special fields for customer details can be inserted into a report. These fields are filled in withthe customer data for all the reports that are generated through the option Schedulecustomer list in the shortcut menu.The following details are added to the report:
- Customer name
- Address
- Zip code
- Locality
- Country
5.1.14.5.12Inserting a Page Break
Insertion or removal of a page break is defined in the Insert Page Break option from theshortcut menu in the relevant area. Only one page break is allowed per area.To insert a page break:
1. Position the cursor where you want to insert a page break.
2. Select Insert Page Break from the shortcut menu. A notch is displayed in front of the labelto confirm insertion of a page break.
5.1.14.5.13Adding a Prefix and/or Suffix to a FormulaTo add a prefix and/or suffix to a formula (brackets, monetary values, %, etc.)
1. Select a formula in the field and formula area.
2. Select Properties from the shortcut menu.
3. Enter the prefix and/or suffix to be added.
4. Click Apply to save your changes.
5.1.14.5.14Using the Result of Operations (View/Scope)
This is the feature called View or Scope in the database management domain. Visibility refersto the ability to use in an area, A, the result of a calculation executed in another area, B. Thisfeature is useful for optimizing lengthy data processing times by reducing their number.
By default, all areas can view the Detail area.Implementation procedure:
1. Position the cursor on the area A where you want to configure Scope.
2. Select Visibility > area B from the shortcut menu. The Visibility application offers, in theform of options, the list of areas containing formulas that can be used.
If you insert a formula in area A, the list of all operations performed in area B will be available.
Chapter 5
5-34
5.1.14.5.15Changing Grid Size
The grid is made up of a mesh of points whose pitch (space between two points in the grid)can be changed:
1. Select Change Grid Size from the shortcut menu. A dialog box is displayed.
2. Enter the new resolution value of between 2 and 10. Grid resolution is updated.
Grid resolution is common to all areas.
5.1.14.5.16Reducing Area Size to the Minimum
A tool enables the area height to be reduced to the smallest size without altering incorporatedgraphic items.
To optimize area size, click .
5.1.14.5.17Modifying Page Format
The vertical border displayed in the designer represents the page's right border. To modify thisborder, you must have a declared printer:To modify page format:
1. Click , the Formatting window is displayed.
2. Update orientation, formatting, and the page margins, then click OK.
5.1.14.5.18Adding a Border to, and Removing a Border from, an Item
By default, the detail area database fields and their associated labels are outlined.To add a border:
1. Select the desired items.
2. Open the shortcut menu and select the Border option.A notch is displayed next to the Border label.
To remove a border:
1. Select the desired items.
2. Open the shortcut menu and select the Border option.The notch next to the Border disappears.
You can add or delete a border on one or more items simultaneously. To do this, make amultiple selection.
5.1.14.5.19Handling Graphic Items
Selecting mMultiple Graphic Items
You can select several non-adjacent items in the report to reduce the number of delete, move(drag), and alignment operations:To select multiple graphic items:
1. Keep the Ctrl key pressed down.
5-35
2. Select the different items by clicking them. All the selected items are displayed with theirrespective anchor points.
Moving a GraphicItem
An item is moved by dragging it. An item cannot be moved from one area to another.
Resizing a Graphic ItemTo resize a text box, a database field, an image, or a chart:
1. Click the item. The anchor points are displayed around the item.
2. Move the anchor points by dragging until you get the desired size.
Resizing a text box does not affect either the size of the characters or the related attributes.
Some database field labels may have long character strings. To insert a "line break" in theselabels, you may insert or move the § character in the string.
Removing a Graphic Item
You can remove one or more items simultaneously.To remove a graphic item:
1. Select the item(s) to be removed,
2. Select Remove from the shortcut menu.
Aligning Several Graphic Items
To improve report legibility, you can align several items in it. These items can be left-aligned orright-aligned:To align several graphic items:
1. Select the different items to be aligned § Selecting mMultiple Graphic Items .
2. Select Align to the Left or Align to the Right from the shortcut menu.The items are aligned on the magnetic grid. See § Changing Grid Size .
5.1.15 Using Templates
By default, the tree structure includes the Templates folder , which, by default, contains
two templates. These cannot be deleted. These are the same templates that apply toaccounting, traffic analysis, VoIP traffic analysis, beyond threshold, and alarms reportdefinitions.
The Templates folder is for grouping all your customized templates. Definitions cannot becreated in it.
5.1.15.1 Usefulness
The template is used to specify complete formatting in order for it to be applied to severaldefinitions (for example, insert logos, headers, footers, etc.). Templates help avoid repeatingidentical formatting.
5.1.15.2 Using Templates
Chapter 5
5-36
Using a template consists of three steps.
1. Create your own templates by inserting the desired graphic items into them: images, text,etc.
2. Create a definition and assign the desired template to it.
3. Generate a report from the definition. The report consists of:• The data retrieved from the database as defined by the Querytool.• Any items incorporated using the Designer.• Graphic items contained in the Template when it was applied.
Note:
No link is created between templates and definitions. If you modify a template which was previously ap-
plied to a definition, no change or update is performed on the reports (current or future) based on this
definition.
5.1.15.3 Creating a Template
A template can only be created in the Templates folder or in one of its sub-folders.
Two tabs are required to update templates: Property and Designer. Access to the Querytoolremains disabled.To create a template:
1. Click the Templates folder or one of its sub-folders.
2. Select Add > Template from the shortcut menu. A dialog box is displayed.
3. Enter the name of the template, then confirm. The new template is displayed in the treestructure.
4. If required, update modifiable data in the Property tab: Description and Keywords.
5. Define the template's contents in the Designer tab (its features are similar to those offeredfor a definition), then save your formatting.See § Defining Presentation - the Designer .
Note:
A template is made up of several different areas:
- Report Header
- Page Header
- Page Footer
- Report Footer
Unlike a definition, a template has no Detail area.
5.1.15.4 Retrieving a Template
You can create a template from a copy:
1. Select the desired template.
2. Select Recover from the shortcut menu. The template is copied to your personal folder.
5.1.15.5 Exporting a Template
5-37
You can export each template in order to import it into the personal folder of another accountor to another Alcatel-Lucent OmniVista 4760 Network Management System server.
1. Select the desired template.
2. Select Export from the shortcut menu. A dialog box is displayed.
3. Enter the export file's name (.def), then specify the directory it is to be saved in.
4. Confirm. The template is exported and can be edited with a text editor.
5.1.15.6 Importing a Template
You can reimport previously exported templates:
1. Specify the path to the import file in the Templates folder.
2. Select Import from the shortcut menu. A dialog box is displayed.
3. Select the template to be imported (.def), then confirm. The template is imported into theTemplates folder. The creation date of an imported template corresponds to its importdate.
5.1.15.7 Deleting a Template
There is no link between templates and definitions. Any template, except the two defaulttemplates, may be deleted:
1. Select the desired template.
2. Select Delete from the shortcut menu. A confirmation dialog box is displayed.
3. Confirm. The template is deleted from the tree structure.
5.1.16 Configuring the Server for Network Export Scheduling
Network export scheduling requires prior configuration of the Alcatel-Lucent OmniVista 4760Network Management System server. You also need the following information:
- The logon and the password of the local server administrator – OsAdmin.
- The logon and the password of the Alcatel-Lucent OmniVista 4760 Network ManagementSystem administrator – OmniAdmin.
- The logon (OsUser) and password (OsPassword ) of a domain network user.
Procedure:
1. Log on to the PC server as OsAdmin, then select Start > Programs > Administration tools> User manager.
2. Select Local strategy > Assign user rights. A window is displayed. Select the optionDisplay advanced user rights.
3. Give the OsUser the following rights by positioning your cursor on the corresponding fieldsand by opening the Security menu:• To operate as a part of the operating system.• To increase the quotas.• To replace a process level token.• Open a local session.
4. Run the Alcatel-Lucent OmniVista 4760 Network Management System client and connect
Chapter 5
5-38
as Adminnmc.
5. Launch the Directory application, then click the System tab.
6. Browse the tree until you reach the following: Nmc > ServerName > Servers >ServerName> ExecdEx, then click the bottom tab NT account.
7. Complete the fields:• User: [Dom_Work]\OsUser.
Note:For a Windows 2000 domain: Dom_Work is equivalent to domain name. For a Workgroup:Dom_Work is equivalent to the name Host 4760.
• Password: OsPassword.
5.1.17 Using Multi-Language Reports
5.1.17.1 Requirements
Predefined reports are displayed in the language used for connection (for example, if youconnected using English, reports are displayed in English. If you connected using French,reports are displayed in French).
To avoid a combination of languages being used in final reports, the predefined reports mustbe copied, modified and generated in a single "connection" language.
If you are aware of this rule, you may apply it on an individual language basis to createmulti-language reports (reports in English, French, Spanish, etc.)You can also generate reports in the languages that are specially defined for report generationand they are not available in the other applications of the Alcatel-Lucent OmniVista 4760Network Management System client. For more information refer to the module Interface -Startup and Shutdown § Starting .
5.1.17.2 Procedure
For example, to create reports in two languages, English and French:
Step 1: Create a directory for each language
1. Create a directory for each language, EN for English, FR for French (see § Creating aFolder ).
Step 2: Copy reports to the English language directory
You MUST be connected "in English" to copy predefined reports to the English (EN) directory.
1. Connect using English (EN). The predefined reports are translated into English.
2. Select the desired report definition from the predefined reports.
3. Select Copy from the shortcut menu.
4. Select the EN directory, then select Paste from the shortcut menu.
Step 3: Copy reports to the French language directory
1. Connect using French (FR). The predefined reports are translated into French.
2. Select the desired report definition from the predefined reports.
3. Select Copy from the shortcut menu.
5-39
4. Select the FR directory, then select Paste from the shortcut menu.
Step 4: Use the reports according to the desired language
You have created language-based (EN and FR) report directories.You can now connect to the relevant directory using the corresponding language to generateor modify reports:
- To modify or generate English language reports, first make sure you are connected usingEnglish as "connection" language.
- To modify or generate French language reports, disconnect and then reconnect usingFrench as "connection" language.
5.2 Predefined accounting reports
5.2.1 Types of Reports
Predefined reports are classified by type:
- Total reports
- Detailed reports
- Traffic analysis reports
- Hit lists
- Cumulative reports
- Subscription (fixed cost) reports
- DISA call reports
- RSC reports (available only with appropriate license)
5.2.2 List of Predefined ReportsTotal reports (9 reports)
- Level
- PIN (Personal Identification Number)
- Project Code
- Directory entry
- Cost by set (multi-currency)
- Direct carrier comparison
- Carriers comparison
- Direct carrier comparison/ direction
- Total Report Cost By User GroupDetailed reports (7 reports)
- PIN (Personal Identification Number)
- Cost By Station
Chapter 5
5-40
- Duration By Station
- Project Code
- Directory entry
- Cost By Station - Extended Format
- Detail Report Cost By User GroupTraffic analysis (6 reports)
- Speed Dialing
- Trunk Group
- Duration threshold
- Cost threshold
- Incoming/outgoing Calls by User Group
- Answered/NonAnswered calls by User GroupHit list (9 reports)
- Cost By cost center
- Cost By station
- Duration By cost center
- Duration By station
- Called numbers
- Direction type
- Directory entry
- Cost By Station - Extended format
- Hit List Cost By User GroupCumulative reports (13 reports)
- Daily cost By Station
- Monthly cost By Station
- Monthly direction type
- Monthly cost By cost center
- Yearly cost By cost center
- Daily station traffic
- Daily duration By cost center
- Monthly carrier
- Yearly carrier
- Daily duration threshold
- Monthly cost threshold
- Monthly direction
- Monthly Cost By Station - Extended formatSubscriptions (6 reports)
5-41
- Annual report
- Monthly synthesis By cost center
- Monthly synthesis
- Detailed monthly report By cost center
- Monthly fixed cost
- Detailed billDISA communications (4 reports)
- Hourly communications synthesis
- Daily communications synthesis
- Monthly communications synthesis
- Monthly DISA useRSC reports (14 reports)
- Cost By Station
- Cost By cost center
- Answered calls (by station)
- Unanswered calls (by station)
- Called number
- Direction type
- Call processing analysis by week
- Call processing analysis by day
- Call processing analysis by hour
- Day trunk group load analysis
- Answered calls (by station) - Extended format
- Unanswered calls (by station) - Extended format
- Cost By Station - Extended format
- RSC Report Cost By User Group
5.2.3 Database Fields (Headers)
This section lists the database fields available when report definitions are printed.
Note:
Depending on the report definition, some fields may not be available.
The character § in a database field generates a "carriage return" when reports are output.
The 137 standard fields are classified in seven sections:
- The Organization section contains 41 fields for the Accounting tree structure (seemodule Accounting - Organization tab ) such as cost center, level Directory-related fields(if this module is included in the license), name, address, etc. Set number is included inthis section.
Chapter 5
5-42
- The Records section contains 30 fields present in call records, such as the number called,call duration, etc.
- The Cost section contains 18 fields, generated by the Alcatel-Lucent OmniVista 4760Network Management System with cost information, such as call cost, direct carrier cost,subscription cost, etc....
- The Carrier section contains 15 fields, generated by the Alcatel-Lucent OmniVista 4760Network Management System, with carrier information such as direct carrier name,direction types, etc.
- The Services section contains 32 fields with ISDN service information (call forwarding,charge information, text messaging) and PCX service information (collective (system)speed dial number, transfer, DISA, etc.).
- The Date section contains 7 fields with date information (date/time, etc.).
- The Projects section contains 3 fields with project code information.
5.2.3.1 Organization
Cost CenterAddress (cost center)Zip Code (cost center)City (cost center)Country (cost center)Cost center and organization values entered for this cost center in the accounting tree.Extensions must be linked to a cost center.
Name (directory)Address (directory)Zip Code (directory)City (directory)Country (directory)Department (directory)Company (directory)Information on a person (individual) from the Company directory.
Note 1:
These database fields are not generated by the OmniPCX Office.
E-mail addressNameAddressZip codeCityCountryExtension (set) numberExtension and organization values entered in the Accounting tree.
LevelAddress (level)
5-43
Zip Code (level)City (level)Country (level)Information on level in the Accounting tree structure.
Example:
Country/Company/Department/level 1...
PIN (Personal Identification Number)This item contains the Personal Identification Number.
Note 2:
This database field is not generated by the OmniPCX Office.
PCXThis item contains the PCX name
TypeType of entity in the flow chart liable to assume the following values:
- Users
- Attendants
- Attendant Group
- Station group
- Voice Mail
- Data terminal
- Project
- Trunk Group
- Logical Link
- Undefined entity
- Global Entity
Employee NumberThis item shows employee number (e.g. the number assigned by the human resourcesdepartment). It is entered in the Company directory.
Note 3:
This database field is not generated by the OmniPCX Office.
Miscellaneous 1, 2, 3These items contain customized information that are entered in the company directory. Theseinformation will be updated automatically for the corresponding Person in the Organization tabin the Query Tool.
Note 4:
This database field is not generated by the OmniPCX Office.
Cost profileThis item shows the cost profile applied to the entity.
Chapter 5
5-44
Local pathThis item shows the path in the accounting tree structure.
Address (project)ZipCode (project)Locality (project)Country (project)These fields are related to the information of the project in the accounting tree structure.
CustomerCustomer addressCustomer zip codeCustomer cityCustomer countryThese fields are related to the details of the PCX owner (customer) and are filled in with thevalues managed in directory.Name (extended format)First name (extended format)These fields are used to store long strings (up to 42 bytes) or UTF8 strings.
5.2.3.2 Records
Called NumberThis item shows the public network number dialed (dialed number may be modified by theARS). It consists of a maximum of 26 digits. If digit masking is enabled, digits on the far rightare replaced by the "*" character.
No. of CallsThis item shows the number of calls for a specific criterion (grouped report).
DurationThis item shows call duration.
Call Type (detailed)This item gives information on call direction.The predefined list of the filter includes the following items:
1. PSTN Outgoing Call
2. PSTN outgoing call through private network
3. Private Network Call
4. PCX network call
5. PSTN incoming call to private network
6. Private network incoming call to private network
7. PSTN or private network outgoing call through private network
8. PSTN or private network incoming call through private network
9. Private network incoming call
10. PSTN Incoming Call
5-45
11. PSTN incoming call through private network
12. Unspecified
13. Private network outgoing call to public network
14. Private network outgoing call to private network
15. PCX-PCX call
16. PCX-transit call
17. Local Call Count
18. Non Answered Calls
Grouped Call TypeThe possible values are:
- Outgoing call
- Incoming call
- PCX/internal call
- Network call
- Subscription
By applying the Subscription filter on the data field, you can identify a subscription's ownedchargeable items.
Call Type (Cumulative)The possible values are:
- Outgoing call
- Incoming call
- Network outgoing call
- Subscription
- Incoming/ Outgoing call
- DISA outgoing call
- DISA Incoming call
Caution:
Select only one call type for generating the report. Selection of two call types will result in double
data. For example, if you select call types Outgoing call + Incoming/ Outgoing call, the result will
contain double data.
Communication TypeThis item shows the type of communication.The predefined list of masks includes the following items:
- Unspecified
- Voice
- Data
- Other Feature Activated
Chapter 5
5-46
- Other Feature Deactivated
Cost TypeThis item contains information on call cost type.The predefined list of masks includes the following items:
- Unspecified
- Analog Trunk Call
- ISDN Circuit Switched Call
- ISDN Packet Call X.25 B channel
- X25 Packet Call X25 D channel
- Digital non-ISDN Call
PCX costThis item shows call cost sent by the PCX in the record.It is included if the mode of calculation selected in Accounting is PCX cost.
Charge UnitsThis item shows the number of charge units (charge pulses) for a call. Charge pulses are sentby the public network (or generated by the PCX in the case of ISDN accounting notification).It should be noted that this number of charge units is not always greater than zero. This isbecause there may be zero charge units for an incoming call, a call via a private network, or acall via a public network that does not generate charge units.
Pers./Prof.This item, supplied by the PCX, shows if it is a personal, professional, or business (project)call.
Initial Dialed NumberFor an incoming call, this item shows the number of the extension called. This number is notnecessarily the number of the extension that answered (e.g. pick-up, forwarding, etc.). For anoutgoing call, it is the number dialed.
Trunk PCX numberThis item shows the number of the trunk node which the call was routed through.
Trunk PCXThis item shows the name of the trunk node which the call was routed through.
Full name of Trunk PCXThis item shows the full name of the trunk node which the call was routed through.
Acting Extension NumberThis item shows the number of the extension initiating the call.
Note 1:
This database field is not generated by the OmniPCX Office.
Transferring NumberIn the case of call transfer, this is the extension that transferred the call.
Note 2:
This database field is not generated by the OmniPCX Office.
5-47
Trunk GroupThis item shows the number of the trunk the call was routed through.
TrunkThis item shows the number of the trunk the call was routed through.
Note 3:
This database field is not generated by the OmniPCX Office.
Waiting DurationIn the case of an incoming call, this item shows how long the set was ringing before beingpicked up. In the case of an outgoing call (the caller belongs to your PCX network), the fieldvalue is 0.
Subscription TypePossible values are: station subscription, voice mail possession, SDA (DID) line possession.
Record OriginPossible values are: Loaded record (record from a PCX), Restored record (record from anarchive).
Incoming call countOutgoing call countThese items show the number of incoming or outgoing calls.
Incoming call durationOutgoing call durationThese items show the duration of incoming or outgoing calls.
DISA call typeThis item shows DISA call type (incoming or outgoing).
Note 4:
This database field is not generated by the OmniPCX Office.
Incoming DISA countOutgoing DISA countThese items show the number of incoming or outgoing DISA calls.
Note 5:
These database fields are not generated by the OmniPCX Office.
Incoming DISA durationOutgoing DISA durationThese items show the duration of incoming or outgoing DISA calls.
Note 6:
These database fields are not generated by the OmniPCX Office.
5.2.3.3 Costs (in Reference Currency)
Chapter 5
5-48
Figure 5.7: Cost Components
Direct Carrier Cost w/o taxDirect Carrier Cost w/taxThis item shows the part of call cost assigned to the direct carrier (without any ISDN costs) (1).
ISDN Cost w/o taxISDN Cost w/taxThis item shows the part of call cost assigned to the direct carrier's ISDN services.
Indirect Carrier Cost w/o taxIndirect Carrier Cost w/taxThis item shows the part of call cost assigned to the indirect carrier (2).
Communication Cost w/o taxCommunication Cost w/taxThis item shows total cost of the call (Direct carrier cost + ISDN cost + Indirect carrier cost)(A).
Invoiced Cost w/o taxInvoiced Cost w/taxThis item shows call cost after applying the cost profile [3], that may be applied in the flowchart (for example: ax + b). (B)
Comparison cost w/o taxComparison cost w/taxThis item shows simulated cost obtained with a comparison carrier. This cost is to becompared with Communication cost (A').
Subscription w/o taxSubscription w/taxThis item indicates the cost of any (A) subscriptions.
Incoming call costOutgoing call costThese items show the cost of incoming or outgoing calls.
Incoming DISA costOutgoing DISA costThese items show the cost of incoming or outgoing DISA calls.
Note:
These database fields are not generated by the OmniPCX Office.
5.2.3.4 Carrier
5-49
Direct CarrierDirect Carrier Name
Direct carrier Calling RegionDirect carrier Called RegionName of the calling/called region for the call, managed in direct carrier directions (Accounting,Carrier tab).
Direct Carrier Dir. TypeThis field corresponds to type of destination (for example: National/International, etc.) used forthe call defined in a city/country name ( module Accounting - Basic operation ). It is common toall carriers.
Direct Carrier CCNThis item shows the name of the country, city or user corresponding to the number called(configured as described in the module Accounting - Basic operation ).
Direct Carrier tariffName of the tariff (set of rates) used for the call (configured as described in moduleAccounting - Basic operation ).
TaxName of the tax used for a carrier's tariff (managed in module Accounting - Basic operation ).
Indirect CarrierIndirect carrier name.
Ind. carrier Called RegionInd. carrier Calling RegionName of the calling/called region for the call, managed in indirect carrier directions ( moduleAccounting - Basic operation ).
Ind. Carrier Dir. TypeThis field corresponds to type of destination (for example: National/International, etc.) used forthe call defined in a city/country name ( module Accounting - Basic operation ). It is common toall carriers.
Ind. Carrier CCNThis item shows the name of the country, city or user corresponding to the number called(configured as described in the module Accounting - Basic operation ).
Ind. Carrier tariffName of the tariff (set of rates) used for the call (configured as described in moduleAccounting - Basic operation ).
Direct carrier comparisonIndirect carrier comparisonThese items show the carriers selected for the comparison calculation as defined in the list ofcarriers.
5.2.3.5 Services
Charge at end (of call)Charge During CallAdv. of Charge Setup
Chapter 5
5-50
Calling Line ID Pres.Mask Calling Line IDCall Is WaitingConn. Line ID Pres.Conn. Line ID Rest. (called party ID masked)Malicious Call IDText MessagingSubaddressUser-User OperationText Messaging UUSCall Forw. Uncond.ARSISDN Basic CallSystem Speed Dial Numb.ISDN Fax Server
Call Forw. BusyCall Forw. No AnswerISVPNAttendant OperationOVPNPriority Incoming CallOverflow Pri To PubOverflow Pub to PrvSubstitutionTransferTransitISDN Voice MailCall Forw. Uncond.DISAThese headings are call attributes or options, showing whether or not services were usedduring a call.
Note:
This DISA field is not generated by the OmniPCX Office.
5.2.3.6 Date
Date/HourDate/ End of communication timeHalf HourHourDateDayWeek DayWeek
5-51
MonthYearMonthYearThese fields are typically used to filter the data contained in the database. These are a fewexamples of available filters for the Date field: this hour, last hour, today, yesterday, this week,last week, this month, last month, first quarter, 2nd quarter, 3rd quarter, this year, etc.
5.2.3.7 Projects
Project CodeThis item contains the project number that was entered by the caller and sent by the PCX. It ismainly used to charge call costs to a product or party's project.
Project NameThis item contains the project name corresponding to the project number.
Project pathThis item shows the path in the accounting tree structure.
5.2.4 Report Presentation (Examples)
5.2.4.1 Total Reports
Chapter 5
5-52
Figure 5.8: Total Reports — Directory Entry
5-53
Figure 5.9: Total Reports — Level
5.2.4.2 Detailed Reports
Chapter 5
5-54
Figure 5.10: Detailed Reports — Cost by Set
5-55
Figure 5.11: Detailed Reports — Duration by Set
Chapter 5
5-56
Figure 5.12: Detailed Reports — Directory Entry
5-57
Figure 5.13: Detailed Reports — Cost by User Group
In this example, the application limits the report to directory entries whose Department fieldsequals NMD.
5.2.4.3 Traffic Analysis
Chapter 5
5-58
Figure 5.14: Traffic Analysis — Cost Threshold
5-59
Figure 5.15: Traffic Analysis — Trunk Group
5.2.4.4 Cumulative Reports
Chapter 5
5-60
Figure 5.16: Cumulative Reports — Monthly Cost by Set
5-61
Figure 5.17: Cumulative Reports — Daily Traffic on Sets
5.2.4.5 Subscription Calls
Chapter 5
5-62
Figure 5.18: Subscriptions — Annual Report
5-63
Figure 5.19: Subscriptions — Monthly Synthesis by Cost Center
Chapter 5
5-64
Figure 5.20: Subscriptions — Monthly Synthesis
Figure 5.21: Subscriptions — Monthly Detailed Report by Cost Center
5-65
Figure 5.22: Subscriptions — Monthly Subscription cCost
Chapter 5
5-66
Figure 5.23: Subscriptions — Bill
5.2.4.6 DISA Communications
5-67
Figure 5.24: DISA Communications — Hourly Communication Synthesis
Chapter 5
5-68
Figure 5.25: DISA Communications — Daily Communication Synthesis
5-69
Figure 5.26: DISA Communications — Monthly Communication Synthesis
Chapter 5
5-70
Figure 5.27: Cumulative Reports— Monthly DISA Use
5.2.4.7 RSC Reports
The following RSC reports can be generated on acquiring the appropriate license.
- Cost by Station: This report lists the ten most expensive stations (based on outgoingcalls) and is available for Alcatel-Lucent OmniPCX Enterprise CS and OmniPCX Office.
- Cost by cost center: This report lists the cost centers sorted in descending order basedon the cost and is available for Alcatel-Lucent OmniPCX Enterprise CS and OmniPCXOffice.
- Answered calls (by station): This report presents the traffic analysis data of theanswered calls per station. This report is based on the accounting CDR and is intended tobe used for OmniPCX Office.
- Non-answered calls (by station): This report presents the traffic analysis data of thenon-answered calls per station. This report is based on the accounting CDR and isintended to be used for OmniPCX Office.
- Call number: This report lists the fifty most expensive called numbers and is available forAlcatel-Lucent OmniPCX Enterprise CS and OmniPCX Office.
- Direction type: This report presents the cost details with respect to the direction type ofthe calls and is available for Alcatel-Lucent OmniPCX Enterprise CS and OmniPCX Office.
- Call processing per week: This report presents the number of incoming calls in a month
5-71
which is sorted per week from Monday to Friday between 8am and 6pm. This report isbased on the accounting CDR and is intended to be used for OmniPCX Office.
- Call processing per day: This report presents the number of incoming calls in a monthwhich is sorted per day from Monday to Friday between 8am and 6pm. This report isbased on the accounting CDR and is intended to be used for OmniPCX Office.
- Call processing per hour: This report presents the number of incoming calls in a monthwhich is sorted by hours from Monday to Friday between 8am and 6pm. This report isbased on the accounting CDR and is intended to be used for OmniPCX Office.
- Intra-day trunk load analysis: This report presents the number of incoming and outgoingcalls in a day which is sorted by hours from 8am to 6pm. This report is based on theaccounting CDR and is intended to be used for OmniPCX Office.
- RSC Reports Cost By User Group: This reports presents the number of calls, the totalduration of these calls and the total cost of these calls for the RSC groups.
Figure 5.28: RSC Reports — Cost by Station
Chapter 5
5-72
Figure 5.29: RSC Reports — Answered Calls (by Station)
Figure 5.30: RSC Reports — Non_Answered Calls (by Station)
5-73
Figure 5.31: RSC Reports — Called Number
Chapter 5
5-74
Figure 5.32: RSC Reports — Direction Type
5.3 Predefined traffic analysis reports
5.3.1 Report Contents
5.3.1.1 Report Groups
The contents of predefined reports for different groups of observed items are briefly outlinedbelow.
Reminder:
The OmniPCX Office does not allow traffic analysis reports to be generated.
5-75
Remark:
Half-hourly type reports are not shown in the report tree structure. However, these reports can be gener-
ated from hourly reports by replacing the Hour header with Half-hour.
5.3.1.1.1 Trunk Groups
Results are expressed in number of calls and in duration.
Predefined reports are generated for a trunk or set of trunks.
Types of predefined reports: hourly, daily, monthly, summary, detailed, hit-list.
Predefined reports contain filters on: date, user node, trunk number.
The predefined reports that can be generated concern:
- External outgoing calls.
- Call distribution.
- Incoming call distribution.
- Outgoing call distribution.
- Occupation thresholds.
- Traffic.
Hit-list reports, for example, can be used to view the 30 trunk groups with the greatest totaltraffic.
5.3.1.1.2 Called Numbers
The data used in reports is extracted from an analysis of accounting records. This data,generated by the application, is stored in result counters. Predefined reports are used to viewthe (incoming) numbers most often called (hit-list) and to track processing following a call.
Results are expressed in number of calls and in duration.
Only calls from the public network are included. These reports are generated for a call numberor set of numbers.
Types of predefined reports: hourly, daily, total, detailed, hit-list.
Predefined reports contain filters on: date, set number, user node, cost center.
Hit-list reports are used to view the most often called (incoming) 15 numbers and the numberof calls presented to them.
Example reports:
- Incoming call processing.
5.3.1.1.3 Sets
The data used in reports is extracted from analysis of both accounting records and trafficanalysis files. This data, generated by the application, is stored in result counters. Predefinedreports are used to view, for example, the 30 terminals with the most traffic (hit-list) and totrack processing after a call to a number.
Results are expressed in number of calls and in duration.
Predefined reports are generated for a terminal or group of terminals.
Chapter 5
5-76
Types of predefined reports: hourly, daily, summary hit-list.
Predefined reports contain filters on: date, set number, user node, cost center.
Example reports:
- Presented calls processing.
- The traffic handled by sets.
5.3.1.1.4 Attendant Groups
Results are expressed in number of calls and in duration.
Predefined reports are generated for an attendant group or set of groups.
Types of predefined reports: hourly, daily, monthly, summary, detailed, hit-list.
Predefined reports contain filters on: date, group number, user node.
Example reports:
- Absence from the group for an attendant.
- Calls presented.
- Average waiting time for a call.
- Outgoing call processing.
- Incoming call processing.
- Call distribution.
- Origin of external incoming calls.
- Operating mode.
- Attendant management mode.
Hit-list reports are used, for example, to view, the 30 attendant groups with the highest numberof abandoned calls.
5.3.1.1.5 Attendants
Results are expressed in number of calls and in duration.
Predefined reports are generated for an attendant or set of attendants.
Types of predefined reports: hourly, daily, monthly, total, detailed, hit-list.
Predefined reports contain filters on: date, group number, attendant number, user node.
The predefined reports that can be generated concern:
- Attendant activity.
- Individual call waiting time before attendant answer.
- Processing of individual calls presented.
- Call distribution.
- Incoming calls processed outside the group.
- Incoming calls processed from the group.
- Outgoing call processing.
5-77
- Duration of attendant set states.
Hit-list reports are used, for example, to view, the 30 attendant sets that have processed thehighest number of incoming calls.
5.3.1.1.6 DECT/PWT
Types of predefined reports: hourly, daily, monthly, total, hit-list.
The observed items are classified by type: ADPCM, Sets, Handoff.
Example reports: For a base station, the predefined reports give the total number of Handoffoperations, the assignments established by the base station and their duration, and abnormalADPCM channel releases.
5.3.1.2 Types of Reports
The different types of reports correspond to the data processing performed (total, detailed,hit-list), or to the analysis period included (hour, day, month).
Note:
Several results are obtained by totaling the contents of counters: for a counter, its contents are totaled for
a specified analysis period. Filtering deals with the node data of this item(s), for the analyzed period spe-
cified.
Total type
Each result is the total (accumulated) result for the values entered in the report filters. Enteringa time allows the values of the counters between the start and end times (time period) to beincluded. Days entered are totaled for the same time periods as configured by filtering. Themaximum number of days included is equal to 1 month as these reports are based on the datacontained in the half-hour counters.
Detailed type
The results corresponding to the values entered in the report filters are totaled by analyzeditem.
Example 1:
For trunk group 1, for trunk group 2, etc.
Entering a time allows the values of the counters between the start and end times (time period)to be included. Days entered are totaled for the same time periods as configured by filtering.The maximum number of days included is equal to 1 month as these reports are based on thedata contained in the half-hour counters.
Hit-list type
The results corresponding to the values entered in the report filters are totaled by analyzeditem.
Example 2:
For trunk group 1, for trunk group 2, etc.
However, only the items with the highest results are output. Entering a time allows the valuesof the counters between the start and end times (time period) to be included. Days entered aretotaled for the same time periods as configured by filtering. The maximum number of daysincluded is equal to 1 month as these reports are based on the data contained in the half-hourcounters.
Chapter 5
5-78
Half-hourly type
Each result is the total (accumulated) result for the values entered in the report filters. Enteringa time allows the values of the counters between the start and end times (time period) to beincluded. Days entered are totaled each half-hour for the same time periods as configured byfiltering. The maximum number of days included is equal to 1 month.
Hourly type
Each result totals the results corresponding to the values entered in the report filters eachhour. The time period for analysis corresponds to the storage time period. Days entered aretotaled for the same time periods as configured by filtering. The maximum number of daysincluded is equal to 1 month.
Daily type
Each result totals the results corresponding to the values entered in the report filters each day.The time period for analysis corresponds to the storage time period. The start and end date isused to generate, for each day included in the period, the daily counters corresponding to thetime period. The maximum number of days that can be observed is equal to 3 months. Youcan filter the days to be included (1 to 31).
Monthly type
Each result totals the results corresponding to the values entered in the report filters eachmonth. The time period for analysis corresponds to the storage time period. The start and endmonth is used to generate, for each month included in the period, the monthly counterscorresponding to the time period. The number of months that can be analyzed is limited to 12.Yon can filter the months to be included (1 to 12).
5.3.1.3 Report Presentation
There are different types of report presentation.
5.3.1.3.1 Tables
Reports presented as a total table
This type of table is supplied in summary type reports. It always includes a single result perheading. This result is obtained by totaling all counters with the same NAME (see list ofcounters for each table) for the parameters and period specified in the filter.
Reports presented as a detailed table
This type of table is found in the detailed or hourly type reports. It always includes a detailedlist of items (e.g. set by set or hour by hour). A global result line gives the total of the detailedresult lines. When printed out, each page includes the top part of the table and its number.
5.3.1.3.2 Pie Chart
These reports are presented in total reports. Data presented in a pie chart is always expressedas a percentage. The results provided always give the total of counters with the same NAME(see list of counters for each report of this type) for the items and period specified in the filter.
5.3.1.3.3 Bar Chart
These reports are presented for Half-hourly, Hourly, Daily, Monthly, Yearly, and Hit-list reports.
The results provided in these charts are expressed as a number or duration (seconds).
Except for the hit-list report, which has the analyzed items on the X axis, the label for the X
5-79
axis for all other reports depends on report type:
00:00 to 24:00 for half-hourly type reports,
00 to 23 for hourly type reports,
1 to 28/29/30/31 for daily type reports,
1 to 12 for monthly type reports,
199x to 20xx for annual (yearly) type reports.
Bar chart with superimposed results
Results for half an hour, hour, day, month and year are shown on the same bar using differentcolors. The number of results superimposed is unlimited.
Bar chart with untotaled multiple results
Each result is represented by a bar. For the same period (half-hour, hour, day, month, year),the bars overlap.
Hit-list bar chart
This report always gives a single result. The maximum number of items shown in the chart is30 (this can be modified).
5.3.2 List of Predefined ReportsTrunk groups (13 reports)
- Summary report
- Detailed report
- Hit-list
- Detailed report - Extended formatHalf-hour reports
- Busy thresholdHourly reports
- Detailed report
- Traffic
- Outgoing requests
- Busy threshold
- Call distributionDaily reports
- Call distributionMonthly reports
- Call distributionRSC reports
- Day trunk group load analysisCalled extensions (7 reports)
- Detailed report
- Hit-listHourly reports
Chapter 5
5-80
- Incoming calls processing
- DetailTotal reports
- Incoming calls processing
- Summary reportDaily reports
- Incoming calls processingStations (5 reports)
- Summary report
- Hit-listHourly reports
- Presented calls Processing
- TrafficDaily reports
- Presented calls ProcessingAttendant groups (29 reports)
- Hit-listTotal reports
- Call distribution
- Origin of external incoming calls
- Wait time (external calls)
- Incoming calls processing
- Summary report
- Waiting time (PCX calls)Detailed reports
- Operation mode
- Calls processingHourly reports
- Calls processing
- Call distribution
- Call presentation
- Operation mode
- Incoming calls
- Average waiting time
- Outgoing callsDaily reports
- Call distribution
- Presented calls
- Call presentation
5-81
- Incoming calls
- Outgoing callsMonthly reports
- Call distribution
- Call presentation
- Incoming calls
- Outgoing callsRSC reports (available only with appropriate license)
- Call processing analysis per attendant group
- Call processing analysis per week
- Call processing analysis per day
- Call processing analysis per hourAttendants (24 reports)
- Hit-listTotal reports
- Summary report
- External individual calls
- Call distribution
- PCX individual calls
- Attendant statesDetailed reports
- Calls processing
- ActivityHourly reports
- Detailed report
- Call distribution
- Incoming calls taken
- Attendant states
- Activity rate
- Outgoing callsDaily reports
- Call distribution
- Incoming calls taken
- Outgoing calls
- Attendant states
- Activity rateMonthly reports
- Call distribution
Chapter 5
5-82
- Incoming calls taken
- Outgoing calls
- Attendant states
- Activity rateWireless (8 reports)
- Global view on base stations
- Hit-list on break rate
- Traffic peaks hit-listHourly, daily and monthly reports
- System
- Bases stations
- ADPCM channels
- PWT/Wireless Handsets
- Handoffs
5.3.3 Database Fields (Headers)
Note 1: In reports, average duration corresponds to total duration of calls over the 1/2 hourperiod divided by the total number of calls STARTED during this same 1/2 hour period.The number of calls started does not include calls started in the 1/2 hour period preceding the1/2 hour period analyzed.This is why the average duration defined for a whole day can be higher than the averageduration seen on a half-hourly basis.As a rule, this discrepancy is compensated by the quantity of calls.
Note 2: Depending on the report definition, some fields may not be available.
Note 3: The character § in the database field generates a "carriage return" when reports areoutput.
5.3.3.1 Trunk Group Fields
This analysis is performed on all calls (i/c, o/g, transiting) made through the trunk group orlogical link.
A trunk group is the logical representation of the physical links allowing a PCX to be linked to apublic switchboard or to PCX nodes.A logical link is the logical representation of the set of physical links allowing 2 PCX nodes(OmniPCX 4400/Alcatel-Lucent OmniPCX Enterprise CS only) of the same subnet to beconnected (Alcatel ABC-F2 protocol).
Reminder: Node is the term used for any PCX, Alcatel or non-Alcatel, connected to theOmniPCX 4400/Alcatel-Lucent OmniPCX Enterprise CS of the analyzed trunk or link. In therest of this document, the term trunk group is used in a general sense (trunk group or logicallink), the term link is used for specific cases.
- Fields displayed in predefined reports:Trunk Group NumberLogical link numbers are identified by the "-1" sign as they have logical numbers that can
5-83
be modified. Thus, if you want to generate a report including data on links, you cannotapply a filter based on the Trunk Group Number database field. A filter must be used onthe Name field.NameNo. TrunksNo. Trunks (Inc)No. Trunks (Outg)Name (Extended format)DateDayWeekdayWeekMonthYearPCX numberPCXCustomerCustomer addressCustomer zip codeCustomer cityCustomer countryIncoming callsThese are all the calls received via the analyzed trunk group, regardless of the result of thecall: abandon, answer, transit.Incoming to other nodesThese are all the calls received from other nodes via the analyzed trunk group, regardlessof the result of the call: abandon, answer, transit.Incoming calls for nodeThese are all the calls received for a node via the analyzed trunk group, regardless of theresult of the call: abandon, answer, transit.Outgoing callsThese are all the calls transmitted via the trunk group, regardless of the result of the call(abandon, answer) and the origin of the request (trunk group or set on the node, anothernode, speed dial number).Outgoing from other nodesThese are all the calls transmitted via the trunk group, regardless of the result of the call(abandon, answer) and the origin of the request (set or trunk group on another node,speed dial number).Outgoing calls from nodeThese are all the calls transmitted via the trunk group, regardless of the result of the call(abandon, answer) and the origin of the request (set or trunk group on the node, speed dialnumber).Total outgoing requests OverflowsThis counter is incremented each time an outgoing call is transmitted (or transmission isattempted) on another trunk group due to total occupation of the analyzed trunk group. Forsuccessive overflows, each trunk group increments its own counter.This counter is not incremented if overflow is not configured in management or if analysisis performed on a logical link.FailuresThis is all outgoing calls requested directly or by overflow and denied (busy tone) due tototal occupation of the trunk group.
Chapter 5
5-84
This counter is not incremented if analysis is performed on a logical link.AssignmentsThis is the total occupation time for all trunks or B channels making up the trunk group orlogical link.Assignment duration (Inc)This is the total occupation time for all trunks making up the trunk group for incoming calls.Assignment duration (Outg)This is the total occupation time for all trunks making up the trunk group for outgoing calls.Busy (greater than R1 %)This is the assignment time during which the trunk group has an occupation rate greaterthan R1. The R1 threshold can be set in Alcatel OmniPCX 4400/Alcatel-Lucent OmniPCXEnterprise CS management; the default value is 70 %.The R1 threshold is common to all trunk groups.BusyTotal time that the trunk group is occupied.
- Formulas commonly used in predefined reports:% OverflowExpressed as a percentage, this counter is associated with the following formula:C2 * 100/C1,C2 = Overflows,C1 = Outgoing calls + Failures + Overflows (= Total number of trunk group seize attempts),This counter is not incremented if analysis is performed on a logical link.% FailuresExpressed as a percentage, this counter is associated with the following formula:C3 * 100/C1,C3 = Failures,C1 = Outgoing calls + Failures + Overflows (= Total number of trunk group seize attempts),This counter is not incremented if analysis is performed on a logical link.Avg duration outgoingThis is the average duration of outgoing calls on this trunk group. It is the total trunk groupassignment time for outgoing calls divided by the number of outgoing calls.
5.3.3.2 Called Number Fields
Direct calls to the set's main call number are analyzed. As a result, calls presented followingoverflow, transfer, or forwarding are not included. The secondary call numbers of multiline setsand PCX groups are not analyzed.
The aim is to analyze traffic to a specific number and the answer quality for calls to thisnumber, regardless of the physical entity that processes or abandons the call.
Only calls from public trunk groups are analyzed.
- Fields displayed in predefined reports:Extension (set) No.UsersName (directory)Cost centerEmployee numberMisc. 1, 2, 3Date
5-85
DayWeekdayWeekMonthYearPCX numberPCXCustomerCustomer addressCustomer zip codeCustomer cityCustomer countryIncoming callsThese are the direct public calls to the analyzed number, regardless of the result of the call(call taken, no answer, abandon, overflow, etc.).Incoming TakenThese are the direct public calls to the analyzed number that were taken, regardless of theentity that handled the call (set called, another set, voice mail, attendant, etc.).Incoming AbandonThese are the direct public calls to the analyzed number that ended with the callerabandoning before receiving an answer.Wait Time before Aband.This time is the wait time before abandon for direct public calls to the analyzed number thatend with abandon on the set called or on another entity.NO. called Taken byThese are the direct public calls to the analyzed number, taken by the set with this number.No. Taken by called (< T1)These are the direct public calls to the analyzed number, taken by the set with this numberwith a waiting time before they are taken that is less than T1. Threshold T1 can be set onthe Alcatel-Lucent OmniVista 4760 Network Management System.No. Taken by called [T1,T2]These are the direct public calls to the analyzed number, taken by the set with this numberwith a waiting time before they are taken that is greater than or equal to T1 and less thanT2. Thresholds T1 and T2 can be set on the Alcatel-Lucent OmniVista 4760 NetworkManagement System.No. Taken by called (> T2)These are the direct public calls to the analyzed number, taken by the set with this numberwith a waiting time before they are taken that is greater than or equal to T1. Threshold T2can be set on the Alcatel-Lucent OmniVista 4760 Network Management System.Conv. DurationThis is the total time spent in conversation for all direct public calls to the analyzed number,taken by the set with this number.No. Abandon calledThese are direct public calls to the analyzed number that ended with the caller abandoningon the set with this number.No. Taken After RedirThese are the direct public calls to the analyzed number, taken after being redirected toanother entity (overflow, forwarding, etc.). This other entity can be a set, an attendant,voice mail, paging, etc.No. Taken After Redir (< T1)These are the direct public calls to the analyzed number, taken after being redirected to
Chapter 5
5-86
another entity (overflow, forwarding, etc.). This other entity can be a set, an attendant,voice mail, paging, etc. Waiting time before being taken was less than T1. Threshold T1can be set on the Alcatel-Lucent OmniVista 4760 Network Management System.No. Taken After Redir [T1,T2]These are the direct public calls to the analyzed number, taken after being redirected toanother entity (overflow, forwarding, etc.). This other entity can be a set, an attendant,voice mail, paging, etc. Waiting time before being taken was greater than or equal to T1and less than T2. Thresholds T1 and T2 can be set on the Alcatel-Lucent OmniVista 4760Network Management System.No. Taken After Redir (> T2)These are the direct public calls to the analyzed number, taken after being redirected toanother entity (overflow, forwarding, etc.). This other entity can be a set, an attendant,voice mail, paging, etc. Waiting time before being taken was greater than or equal to T2.Threshold T2 can be set on the Alcatel-Lucent OmniVista 4760 Network ManagementSystem.No. Abandon After RedirThese are the direct public calls to the analyzed number, that ended with the callerabandoning after being redirected to another entity (overflow, forwarding, etc.). This otherentity can be a set, an attendant, voice mail, paging, etc.Wait TimeThis time is the wait time before direct public calls to the analyzed number were answered,regardless of the entity that handled the call (set called, another set, voice mail, attendant,etc.).
- Formulas commonly used in predefined reports:% TakenExpressed as a percentage, this counter is associated with the following formula:C2 * 100/C1,C2 = Incoming calls takenC1 = Incoming calls.Avg wait time incoming takenThis duration is the average calculated wait time% No. called Taken byExpressed as a percentage, this counter is associated with the following formula:C4 * 100/C1,C4 = Taken by called party,C1 = Incoming calls.% No. Abandon calledExpressed as a percentage, this counter is associated with the following formula:C3 * 100/C1,C3 = Incoming AbandonedC1 = Incoming calls.% Incoming Aband.Expressed as a percentage, this counter is associated with the following formula:C6 * 100/C2,C6 = Abandons on called party,C2 = Incoming calls.Avg conv. durationThis is the average time spent in conversation for direct public calls to the analyzed
5-87
number, taken by the set with this number.This counter is obtained with the following formula:C5/C4,C5 = Conversation duration time,C4 = Calls taken by called party,
5.3.3.3 Station Fields
This analysis concerns calls that called the set regardless of the initial called number.
This concerns calls obtained directly by pick-up, overflow, or forwarding and excludes callsobtained by transfer or routing by the attendant.
Reminder:Public call = incoming or outgoing call via a trunk group declared as "public" type in OmniPCX4400 or Alcatel-Lucent OmniPCX Enterprise CS management.Private call = incoming or outgoing call via a trunk group declared as "private" type inOmniPCX 4400 or Alcatel-Lucent OmniPCX Enterprise CS management.External call = "public" or "private" type incoming or outgoing call .PCX/internal call = incoming or outgoing call to or from the same PCX or an ABC-F2 or QSIGconnected PCX (whether or not it belongs to the same subnet).
Fields displayed in predefined reports:
Extension
Users
Name (directory)
Cost center
Employee number
Miscellaneous 1, 2, 3
Name (extended format)
First name (extended format)
Date
Day
Weekday
Week
Month
year
PCX number
PCX
Customer
Customer address
Customer zip code
Customer city
Chapter 5
5-88
Customer country
No. Taken By TerminalThese are the incoming public calls presented to the analyzed set that were answered.
Abandon On TerminalThese are the incoming public calls presented to the analyzed set and abandoned by the callerbefore the analyzed set answered.
Conv. Duration (ext incoming)This is the total time spent in conversation for external incoming calls taken by the set.
Conv. Duration (ext outgoing)This is the total time spent in conversation for external outgoing calls made by the set.
Conv. Duration (PCX calls)This is the total time spent in conversation for incoming and outgoing PCX calls made or takenby the set.
5.3.3.4 Attendant Group Field
Reminder:Public call = incoming or outgoing call via a trunk group declared as "public" type in OmniPCX4400 or Alcatel-Lucent OmniPCX Enterprise CS management.Private call = incoming or outgoing call via a trunk group declared as "private" type inOmniPCX 4400 or Alcatel-Lucent OmniPCX Enterprise CS management.External call = "public" or "private" type incoming or outgoing call .PCX call = incoming or outgoing call to or from the same PCX or an ABC-F2 or QSIGconnected PCX (whether or not it belongs to the same subnet).
Fields displayed in predefined reports:
Group Number= number assigned to the attendants group.
Name= name assigned to the attendants group.
Extension = group set number.
Attendants In Group= number of attendants working in the group during the full 1/2 houranalyzed.
Name (extended format)
First name (extended format)
Date
Day
Weekday
Week
Month
Year
PCX number
PCX
Customer
5-89
Customer address
Customer zip code
Customer city
Customer country
5.3.3.4.1 Call Presentation to the Group
Fields displayed in predefined reports:
Incoming CallsThis is the total of all public, private, and internal incoming calls presented to the group,regardless of the result of the call: taken, abandoned, or overflowed (overflows increment thecounter of the group they overflow to).
Incoming Calls (Direct)Among the calls presented to the group, those that called the group number directly.
Incoming Calls (Indirect)Among the calls presented to the group:
- Those initially received on the sets and presented to the group by dialing the switchboard'sinternal number or by overflow because of no answer from the set initially called.
- Those initially received by another attendant or another group and presented to theanalyzed group because of overflow on no-answer.
Routing resumption and standard on-holds are not included. In opposition to direct calls, thesecalls will be labeled "indirect".
Public IncomingThese are all the incoming public calls presented to the group, regardless of the result of thecall: taken, abandoned, or overflowed, and regardless of the call type, direct or indirect.
Public Incoming (Recall)Among the incoming public calls presented to the group, (taken, abandoned or overflowed),those received on the sets and presented to the group by dialing the switchboard's internalnumber.
Private IncomingThese are all the incoming private calls presented to the group, regardless of the result of thecall: taken, abandoned, or overflowed, and regardless of the call type, direct or indirect.
Private Incoming (Recall)Among the incoming private calls presented to the group, (taken, abandoned or overflowed),those received on the sets and presented to the group by dialing the switchboard's internalnumber.
External Incoming (Direct)Among the calls presented to the group, those that called the group by dialing the externalnumber or by direct routing of the trunk group (BCA, etc.).
External Incoming (No answer station)Among the indirect external calls to the group, those that called a set directly and werepresented on no-answer from the set initially called (overflow on no answer, overflow on busyor immediate overflow).
Chapter 5
5-90
External incoming (No answer Grp/Att)Among the indirect external calls to the group, those that called an attendant group orattendant and were presented on no-answer from the attendant group or attendant initiallycalled (overflow on no-answer, overflow on busy or immediate overflow).
External Incoming (Recalls)Among the indirect external calls presented to the group, those received on the sets andpresented to the group by dialing the switchboard's internal number.
PCX IncomingThese are all the incoming PCX calls presented to the group: taken, abandoned or overflowed,regardless of the result of the call and regardless of the call type: direct or indirect.
PCX incoming (Direct)Among the PCX calls presented to the group, those that called the group number directly.
PCX Incoming (Indirect)Among the PCX calls presented to the group, those received on the sets and presented to thegroup by dialing the switchboard's internal number or those presented following an overflowfrom another attendant or group.
PCX Incoming (Recall)Among the indirect external calls presented to the group, those received on the sets andpresented to the group by dialing the switchboard's internal number.
PCX incoming (No answer Grp/Att)Among the PCX calls to the group, those that called an attendant group or attendant and werepresented on no answer from the attendant group or attendant initially called (overflow on noanswer, on busy, or immediate overflow).
5.3.3.4.2 Calls Taken by the Group
- Fields displayed in predefined reports:Incoming TakenThese are the calls that were answered by an attendant in the analyzed group.This counter is incremented regardless of the type of call (public, private, or PCX), andregardless of the origin of the call (direct, redial, or overflow).Incoming Taken (< T2)These are, among the calls that were answered by an attendant in the analyzed group,those with a waiting time before answering that was less than T2. Threshold T2 can be setin OmniPCX 4400 or Alcatel-Lucent OmniPCX Enterprise CS management.This counter is incremented regardless of the type of call (public, private, or PCX), andregardless of the origin of the call (direct, redial, or overflow).Incoming Taken (> T2)These are, among the calls that were answered by an attendant in the analyzed group,those with a waiting time before answering that was greater than or equal to T2. ThresholdT2 can be set in OmniPCX 4400 or Alcatel-Lucent OmniPCX Enterprise CS management.This counter is incremented regardless of the type of call (public, private, or PCX), andregardless of the origin of the call (direct, redial, or overflow).Avg wait time incoming takenThis time is the average waiting time before incoming calls to the group were taken, whentaken by an attendant in this group.This counter is incremented regardless of the type of call (public, private, or PCX), and
5-91
regardless of the origin of the call (direct, redial, or overflow).Incoming AbandonThese are the calls presented to the group that ended with the caller abandoning before anattendant in the analyzed group answered.This counter is incremented regardless of the type of call (public, private, or PCX), andregardless of the origin of the call (direct, redial, or overflow).External TakenThese are the external calls that were answered by an attendant in the analyzed group.This counter is incremented regardless of the origin of the call (direct, redial, or overflow).External Taken (< T1)These are the external calls that were answered by an attendant in the analyzed groupwith a waiting time before answering that was less than T1. Threshold T1 can be set inOmniPCX 4400 or Alcatel-Lucent OmniPCX Enterprise CS management.This counter is incremented regardless of the origin of the call (direct, redial, or overflow).External Taken [T1,T2]These are the external calls that were answered by an attendant in the analyzed groupwith a waiting time before answering that was greater than or equal to T1 and less than T2.Thresholds T1 and T2 can be set in OmniPCX 4400 or Alcatel-Lucent OmniPCXEnterprise CS management.This counter is incremented regardless of the origin of the call (direct, redial or overflow).External Taken (> T2)These are the external calls that were answered by an attendant in the analyzed groupwith a waiting time before answering that was greater than or equal to T2. Threshold T2can be set in OmniPCX 4400 or Alcatel-Lucent OmniPCX Enterprise CS management.This counter is incremented regardless of the origin of the call (direct, redial, or overflow).Avg wait time external takenThis time is the average waiting time before external calls to the group were taken, whentaken by an attendant in this group.This counter is incremented regardless of the origin of the call (direct, redial, or overflow).External Aband.These are the external calls presented to the group that ended with the caller abandoningbefore an attendant in the analyzed group answered.This counter is incremented regardless of the origin of the call (direct, redial, or overflow).Avg wait time external aband.This time is the average waiting time before abandon for external calls abandoned in thegroup.This counter is incremented regardless of the origin of the call (direct, redial, or overflow).External RedirectedThis time is for all external calls presented to the attendants that were rerouted to anotherentity (sets, etc.).PCX TakenThese are the PCX calls that were answered by an attendant in the analyzed group.This counter is incremented regardless of the origin of the call (direct or indirect).PCX Taken (< T1)These are, among the PCX calls that were answered by an attendant in the analyzedgroup, those with a waiting time before answering that was less than T1. Threshold T1 canbe set in OmniPCX 4400 or Alcatel-Lucent OmniPCX Enterprise CS management.This counter is incremented regardless of the origin of the call (direct or indirect).PCX Taken [T1,T2]
Chapter 5
5-92
These are the PCX calls that were answered by an attendant in the analyzed group with awaiting time before answering that was greater than or equal to T1 and less than T2.Thresholds T1 and T2 can be set in OmniPCX 4400 or Alcatel-Lucent OmniPCXEnterprise CS management.This counter is incremented regardless of the origin of the call (direct or indirect).PCX Taken (> T2)These are the PCX calls that were answered by an attendant in the analyzed group with awaiting time before answering that was greater than or equal to T2. Threshold T2 can beset in OmniPCX 4400 or Alcatel-Lucent OmniPCX Enterprise CS management.This counter is incremented regardless of the origin of the call (direct or indirect).Avg wait time PCX takenThis time is the average waiting time before PCX calls to the group were taken, whentaken by an attendant in this group.This counter is incremented regardless of the origin of the call (direct or indirect).PCX Aband.These are the PCX calls presented that ended with the caller abandoning before anattendant in the analyzed group answered.This counter is incremented regardless of the origin of the call (direct or indirect).Avg wait time PCX aband.This time is the average waiting time before abandoning PCX internal calls presented tothe group.PCX RedirectedThis time is for all PCX calls presented to the attendants that were rerouted to anotherentity (sets, etc.).
- Formulas commonly used in predefined reports:% Incoming Taken (> T2)Expressed as a percentage, this counter is associated with the following formula:C2 * 100/C1,C2 = Incoming Taken (> T2),C1 = Incoming calls.% Incoming AbandonExpressed as a percentage, this counter is associated with the following formula:C3 * 100/C1,C3 = Incoming Abandon,C1 = Incoming calls.
5.3.3.4.3 Outgoing Calls Made by the Group
Fields displayed in predefined reports:
Outgoing CallsThis is the total of outgoing public, private and PCX calls made by each attendant in the group,regardless of the result of the call (answer, attendant busy, or abandoned).
Public OutgoingThis is the total of outgoing public calls made by each attendant in the group, regardless of theresult of the call (answer, attendant busy, or abandoned).
Private OutgoingThis is the total of outgoing private calls made by each attendant in the group, regardless of
5-93
the result of the call (answer, attendant busy, or abandoned).
PCX OutgoingThis is the total of outgoing PCX calls made by each attendant in the group, regardless of theresult of the call (answer, attendant busy, or abandoned). This counter is incremented eachtime that an attendant transfers a call to a subnet set.
5.3.3.4.4 Group Status and Operation Mode
Fields displayed in predefined reports:
Absent StateThis is the total time during which the attendant group remains in the absent state: if a callcomes to an attendant and receives no answer, after a timer has elapsed, the attendant isconsidered absent. An attendant group is considered absent when all the attendants areabsent.
Day ModeThis is the total time during which the attendant group is in day mode.
FWD1 ModeThis is the total time during which the attendant group is in transfer 1 mode.
FWD2 ModeThis is the total time during which the attendant group is in transfer 2 mode.
Night ModeThis is the total time during which the attendant group is in night mode.
5.3.3.5 Attendant Fields
Reminder:Public call = incoming or outgoing call via a trunk group declared as "public" type in OmniPCX4400 or Alcatel-Lucent OmniPCX Enterprise CS management.Private call = incoming or outgoing call via a trunk group declared as "private" type inOmniPCX 4400 or Alcatel-Lucent OmniPCX Enterprise CS management.external call = "public" or "private" type incoming or outgoing call .PCX call = incoming or outgoing call to or from the same PCX or an ABC-F2 or QSIGconnected PCX (whether or not it belongs to the same subnet).
Fields displayed in predefined reports:
Group Number
Extension
Attendant number
Cost center
Name (extended format)
First name (extended format)
Date
Day
Weekday
Chapter 5
5-94
Week
Month
Year
PCX number
PCX
Customer
Customer address
Customer zip code
Customer city
Customer country
5.3.3.5.1 Call Presentation to the Attendant
Fields displayed in predefined reports:
The calls that arrive on the number of the group to which the analyzed attendant belongs areconsidered as presented to the group and not the attendant, even if they were taken by theattendant. Only the calls that dialed the attendant's specific number are considered aspresented to the attendant.
Incoming CallsThis is the total of all public, private and PCX incoming calls presented to the attendant'sspecific number, regardless of the result of the call: taken, abandoned, or overflowed(overflows increment the counter of the group they overflow to), regardless of the type of call:direct or indirect.
Note:
Overflows increment the counter of the attendant they overflow to.
Public Incoming (Direct)Among the public calls presented to the attendant's specific number, those that called theattendant directly by dialing the external number or by direct routing of the trunk group (BCA,etc.).
Public Incoming (No answer at station)Among the indirect public calls presented to the attendant's specific number, those that calleda set directly and were presented to the attendant on no answer from the set initially called(overflow on no answer, overflow on busy, or immediate overflow).
Public Incoming (No answer Grp/Att)Among the indirect public calls presented to the attendant's specific number, those that calleda group or an attendant directly and were presented to the attendant on no answer from thegroup/attendant initially called (overflow on no answer, overflow on busy, or immediateoverflow).
Public Incoming (Recall)Among the indirect public calls presented to the attendant's specific number, those initiallyreceived on the sets and presented to the attendant by dialing the internal number. Routingresumption and standard on-holds are not included.
Public Incoming (Indirect)
5-95
Among the public calls presented to the attendant, those received on the sets and presentedto the attendant either by dialing the switchboard's internal number, or by overflow fromanother attendant.
Private Incoming (Direct)Among the private calls presented to the attendant's specific number, those that called theattendant directly by dialing the external number or by direct routing of the trunk group.
Private Incoming (No answer at station)Among the private calls presented to the attendant's specific number, those that called a setdirectly and were presented to the attendant on no answer from the set initially called (overflowon no answer, overflow on busy, or immediate overflow).
Private Incoming (No answer Grp/Att)Among the private calls presented to the attendant's specific number, those that called a groupor an attendant directly and were presented to the attendant on no answer from thegroup/attendant initially called (overflow on no answer, overflow on busy, or immediateoverflow).
Private Incoming (Recall)Among the private calls presented to the attendant's specific number, those initially receivedon the sets and presented to the attendant by dialing the internal number. Routing resumptionand standard on-holds are not included.
Private Incoming (Indirect)Among the private calls presented to the attendant's specific number, those received on thesets and presented to the attendant either by dialing the switchboard's internal number, or byoverflow from another attendant.
External Incoming (Direct)Among the external calls presented to the attendant's specific number, those that called theattendant directly by dialing the external number or by direct routing of the trunk group.
PCX Incoming (Direct)Among the PCX calls presented to the attendant's specific number, those that called theattendant directly by dialing the internal number.
PCX Incoming (Recall)Among the PCX calls presented to the attendant's specific number, those initially received onthe sets and presented to the attendant by dialing the internal number.
PCX Incoming (No answer Grp/Att)Among the PCX calls presented to the attendant's specific number, those that called a groupor an attendant directly and were presented to the attendant on no answer from thegroup/attendant initially called (overflow on no answer, overflow on busy, or immediateoverflow).
PCX Incoming (Indirect)Among the PCX calls presented to the attendant's specific number, those received on the setsand presented to the attendant either by dialing the switchboard's internal number, or byoverflow from another attendant.
5.3.3.5.2 Calls Taken by the Attendant
- Fields displayed in predefined reports:Incoming Taken (Grp+Ind)
Chapter 5
5-96
This is the total of all public, private, and PCX incoming calls answered by the analyzedattendant, whether the calls were presented to the group number or the analyzedattendant's specific number.Incoming Taken (Grp)This is the total of all public, private, and PCX incoming calls presented to the groupnumber and answered by the analyzed attendant:Incoming Taken (Ind)This is the total of all public, private, and PCX incoming calls presented to the analyzedattendant's specific number and answered by it.Incoming Taken (< T2)This is the total of all public, private, and PCX incoming calls presented to the analyzedattendant's specific number and answered by it after a waiting time before being taken thatis less than the T2 threshold.Threshold T2 can be set in OmniPCX 4400 or Alcatel-Lucent OmniPCX Enterprise CSmanagement.Incoming Taken (> T2)This is the total of all public, private, and PCX incoming calls presented to the analyzedattendant's specific number and answered by it after a waiting time before being taken thatis greater than or equal to the T2 threshold. Threshold T2 can be set in OmniPCX 4400 orAlcatel-Lucent OmniPCX Enterprise CS management.Incoming AbandonThese are the direct public calls to the analyzed number that ended with the callerabandoning before receiving an answer.External Taken (Grp+Ind)These are all the external incoming calls answered by the attendant, whether the callswere presented to the group number or the attendant's specific number.External Taken (< T1)These are all the external incoming calls presented to the attendant's specific number andwith a waiting time before being taken by it lower than the T1 threshold.Threshold T1 can be set in OmniPCX 4400 or Alcatel-Lucent OmniPCX Enterprise CSmanagement.External Taken [T1,T2]These are all the external incoming calls presented to the attendant's specific number andwith a waiting time before being taken by it greater than or equal to the T1 threshold andlower than the T2 threshold.Thresholds T1 and T2 can be set in OmniPCX 4400 or Alcatel-Lucent OmniPCXEnterprise CS management.External Taken (> T2)These are all the external incoming calls presented to the attendant's specific number andwith a waiting time before being taken by it greater than or equal to the T1 threshold.Threshold T2 can be set in OmniPCX 4400 or Alcatel-Lucent OmniPCX Enterprise CSmanagement.Avg wait time external takenThis time is the average waiting time before external calls presented to the attendant'sspecific number were taken.Public Taken (Grp+Ind)These are all the public incoming calls answered by the attendant, whether the calls werepresented to the group number or the attendant's specific number.Public Taken (Grp)These are all the public incoming calls presented to the group number and answered by
5-97
the attendant.Public Taken (Ind)These are all the public incoming calls presented to the attendant's group number andanswered by the group number.Public Taken [T1,T2]These are all the public incoming calls presented to the attendant's specific number andwith a waiting time before being taken by the attendant number that is greater than orequal to the T1 threshold and less than the T2 threshold.Thresholds T1 and T2 can be set in OmniPCX 4400 or Alcatel-Lucent OmniPCXEnterprise CS management.Public Taken (> T2)These are all the public incoming calls presented to the attendant's specific number andwith a waiting time before being taken by the attendant number that is greater than orequal to the T1 threshold.Threshold T2 can be set in OmniPCX 4400 or Alcatel-Lucent OmniPCX Enterprise CSmanagement.Avg wait time public takenThis time is the average waiting time before public calls presented to the attendant'sspecific number were taken.Public Aband.These are all the public incoming calls presented to the attendant's specific number thatended with the caller abandoning before an attendant answered.Public Aband. [T1,T2]These are all the public incoming calls presented to the attendant's specific number andabandoned by the caller, with a waiting time before abandon that is greater than or equalto the T1 threshold and less than the T2 threshold.Thresholds T1 and T2 can be set in OmniPCX 4400 or Alcatel-Lucent OmniPCXEnterprise CS management.Public Aband. (> T2)These are all the public incoming calls presented to the attendant's specific number andabandoned by the caller, with a waiting time before abandon greater than or equal to theT2 threshold.Threshold T2 can be set in OmniPCX 4400 or Alcatel-Lucent OmniPCX Enterprise CSmanagement.Avg wait time public aband.This time is the average waiting time before abandon for public calls presented to theattendant's specific number and abandoned by the caller.Private Taken (Grp+Ind)These are all the private incoming calls answered by the attendant, whether the calls werepresented to the group number or the attendant's specific number.Private Taken (Grp)These are all the private incoming calls presented to the group number and answered bythe attendant.Private Taken (Ind)These are all the private incoming calls presented to the attendant's group number andanswered by it.Private Taken [T1,T2]These are all the private incoming calls presented to the attendant's specific number andwith a waiting time before being taken by the number that is greater than or equal to the T1threshold and less than the T2 threshold.
Chapter 5
5-98
Thresholds T1 and T2 can be set in OmniPCX 4400 or Alcatel-Lucent OmniPCXEnterprise CS management.Private Taken (> T2)These are all the private incoming calls presented to the attendant's specific number andwith a waiting time before being taken the number that is greater than or equal to the T1threshold.Threshold T2 can be set in OmniPCX 4400 or Alcatel-Lucent OmniPCX Enterprise CSmanagement.Avg wait time private takenThis time is the average waiting time before private calls presented to the attendant'sspecific number were taken.Private Aband.These are all the private incoming calls presented to the attendant's specific number thatended with the caller abandoning before an attendant answered.Private Aband. [T1,T2]These are all the private incoming calls presented to the attendant's specific number andabandoned by the caller, with a waiting time before abandon that is greater than or equalto the T1 threshold and less than the T2 threshold.Thresholds T1 and T2 can be set in OmniPCX 4400 or Alcatel-Lucent OmniPCXEnterprise CS management.Private Aband. (> T2)These are all the private incoming calls presented to the attendant's specific number andabandoned by the caller, with a waiting time before abandon that is greater than or equalto the T2 threshold.Threshold T2 can be set in OmniPCX 4400 or Alcatel-Lucent OmniPCX Enterprise CSmanagement.Avg wait time private aband.This time is the average waiting time before abandon for private calls presented to theattendant's specific number and abandoned by the caller.PCX Taken (Grp+Ind)These are all the PCX incoming calls answered by the attendant, whether the calls werepresented to the group number or the attendant's specific number.PCX Taken (Grp)These are all the PCX incoming calls presented to the group number and answered by theattendant.PCX Taken (Ind)These are all the PCX incoming calls presented to the attendant's group number andanswered by it.PCX Taken (< T1)These are all the PCX incoming calls presented to the attendant's specific number andwith a waiting time before being taken by the number that is less than the T1 threshold.Threshold T1 can be set in OmniPCX 4400 or Alcatel-Lucent OmniPCX Enterprise CSmanagement.PCX Taken [T1,T2]These are all the PCX incoming calls presented to the attendant's specific number andwith a waiting time before being taken by the number that is greater than or equal to the T1threshold and less than the T2 threshold.Thresholds T1 and T2 can be set in OmniPCX 4400 or Alcatel-Lucent OmniPCXEnterprise CS management.PCX Taken (> T2)
5-99
These are all the PCX incoming calls presented to the attendant's specific number andwith a waiting time before being taken by the number that is greater than or equal to the T1threshold.Threshold T2 can be set in OmniPCX 4400 or Alcatel-Lucent OmniPCX Enterprise CSmanagement.Avg wait time PCX takenThis time is the average waiting time before PCX calls presented to the attendant's specificnumber were taken.PCX Aband.These are all the PCX incoming calls presented to the attendant's specific number thatended with the caller abandoning before an attendant answered.PCX Aband. [T1,T2]These are all the PCX incoming calls presented to the attendant's specific number andabandoned by the caller, with a waiting time before abandon that is greater than or equalto the T1 threshold and less than the T2 threshold.Thresholds T1 and T2 can be set in OmniPCX 4400 or Alcatel-Lucent OmniPCXEnterprise CS management.PCX Aband. (> T2)These are all the PCX incoming calls presented to the attendant's specific number andabandoned by the caller, with a waiting time before abandon that is greater than or equalto the T2 threshold.Threshold T2 can be set in OmniPCX 4400 or Alcatel-Lucent OmniPCX Enterprise CSmanagement.Avg wait time PCX aband.This time is the average waiting time before abandon for PCX calls presented to theattendant's specific number and abandoned by the caller.
- Formulas commonly used in predefined reports:% PCX Taken (> T2)Expressed as a percentage, this counter is associated with the following formula:C2 * 100/C1,C2 = Incoming Taken (> T2),C1 = Incoming Aband.This is the total of all public, private and PCX incoming calls presented to the attendant'sspecific number that ended with the caller abandoning before an attendant answered.% Incoming Abandon.Expressed as a percentage, this counter is associated with the following formula:C3 * 100/C1,C3 = Incoming AbandonC1 = Incoming Calls.
5.3.3.5.3 Outgoing Calls
Fields displayed in predefined reports:
Outgoing CallsThis is the total of outgoing public, private, and PCX calls made by the attendant, regardless ofthe result of the call (answer, attendant busy, or abandoned).
External OutgoingThese are the outgoing external calls made by the attendant, regardless of the result of the call
Chapter 5
5-100
(answer, attendant busy, or abandoned).
Public OutgoingThese are the outgoing public calls made by the attendant, regardless of the result of the call(answer, attendant busy, or abandoned).
Private OutgoingThese are the outgoing private calls made by the attendant, regardless of the result of the call(answer, attendant busy, or abandoned).
PCX OutgoingThese are the outgoing PCX calls made by the attendant, regardless of the result of the call(answer, attendant busy, or abandoned).This counter is incremented each time that an attendant transfers a call to a subnet set.
5.3.3.5.4 Key Activation
Fields displayed in predefined reports:
Hold Key ActivThis is the number of times the multiple on-hold feature is activated by the attendant (whethersuccessful or not).
Transfer Key ActivationThis is the number of times the multiple transfer feature is activated by the attendant (whethersuccessful or not).
5.3.3.5.5 Attendant States
To optimize the process, the Active state is not used in the predefined reports dedicated tothe attendant state. These reports only highlight the attendants state while they are "active".
Active stateThis is the total time during which the attendant is "active" (plugged in). This includes periodswhen the attendant is busy, in management mode, idle, or absent.
- Fields displayed in predefined reports:Busy StateThis is the total time during which the attendant is busy, that is, on a call.Idle StateThis is the total time during which the attendant is inactive: connected but not busy, away,or in management mode.Management StateThis is the total time spent by the attendant in management, that is, in Guide mode,Service mode, trunk group reservation, or authorization of outgoing public calls.Absent StateThis is the total time during which the attendant remains in the absent state: if a call comesto an attendant and is not answered, after a timer has elapsed, the attendant is consideredas absent. The attendant switches from the absent state by pressing a key on the terminal.
- Formula commonly used in predefined reports:% ActivityExpressed as a percentage, this counter is associated with the following formula:C1 * 100/C2,C1 = Busy state + Management state,
5-101
C2 = Busy state + Management state + Idle state + Absent state.
5.3.3.6 DECT/PWT Headers
5.3.3.6.1 DECT/PWT Wireless System
- Fields displayed in predefined reports:Inc. Paging RequestsThis is the total number of paging requests (incoming calls).Paging FailuresInc. Paging Failures: this is the total number of unsuccessful paging requests (incomingcall, no answer from DECT/PWT user despite paging attempts).Paging AttemptsPaging broadcast: this is the total number of paging attempts (3 attempts maximum foreach request, defined on initialization. The maximum number of paging attempts perDECT/PWT user can be modified in system management).Handoff between boardsLink handoffs: this is the total number of simple connections supported by the system(connection between two different boards).Handoff on boardsBearer handoffs: this is the total number of connections supported by the system(connection in the same board).ADPCM Assignment FailuresThis is the total number of ADPCM assignment failures (ADPCM unavailable: busy, orout-of-service).Unauthorized CallsThis is the total number of unauthorized calls (IPUI N invalid for the system).
- Formula commonly used in predefined reports:% Paging FailuresExpressed as a percentage, this counter is associated with the following formula:C3 * 100/C1,C3 = Paging,C1 = Incoming Calls.
5.3.3.6.2 Base Stations
- Fields displayed in predefined reports:ACT shelf numberBoard NumberRadio Board NumberBase NumberPARI NumberAssignmentsThis is the total number of links established per base station.Assignment DurationThis is the total time during which the links are busy for each base station.Abnormal ReleasesThis is the total number of failures per base station (loss of board, set outside the coveragearea).Traffic Peaks
Chapter 5
5-102
This is the total number of traffic peaks per base station (number of calls exceeding a setthreshold).Peak ThresholdThis is the threshold defined for traffic peaks.Intracluster Handoffs (successful)This is the total number of inter-cluster handoffs (base station handoff on the samecluster).For RBS base stations:• a cluster is a set of base station cells of the same DECT/PWT board.For IBS base stations:• a cluster is a cell.Intercluster Handoffs (successful)This is the total number of simple switchovers per base station (cluster handoff).Hourly break rateThis is the total number of abnormal releases for each assigned time (Bases), expressedas an hourly average.
- Formula commonly used in predefined reports:Avgerage Assignment DurationThis is the average time during which the links are busy for each base station.This counter is obtained with the following formula:C3/C2,C3 = Assignment Duration,C2 = Number of assignments Traffic peaks.
5.3.3.6.3 ADPCM
Fields displayed in predefined reports:
ACT shelf number
Board Number
Radio Board Number
APDCM Number
PARI Number
AssignmentsThis is the total number of links established per ADPCM channel.
Assignment DurationThis is the total time during which the links are busy for each ADPCM channel.
5.3.3.6.4 DECT/PWT Wireless Sets
Fields displayed in reports:
Extension (set) number
Users
Name (directory)
Cost Center
5-103
Employee number
Miscellaneous 1, 2, 3
Handoff AttemptsThis is the number of handoff attempts per DECT/PWT user.
Paging FailuresThis is the total number of paging failures (no answer) per DECT/PWT user.
Abnormal ReleasesThis is the total number of failures (loss of board, out of range, loss of radio connection).
5.3.3.6.5 Hourly Break Rate
Field displayed in predefined reports:
Hourly break rateThis is the total number of abnormal releases (sets) for each assigned time (ADPCM),expressed as an hourly average.
5.3.4 Report Presentation
5.3.4.1 Trunk Groups
Summary reportThis presents a summary of incoming and outgoing traffic on the selected trunk group(s). Itcan be used for regular tracking of the correct sizing of the installation and to detect anyanomalies or traffic peaks - that can then be analyzed in greater depth in subsequent reports.It is a total report. This means that data on selected PCXs, trunk groups, from periods ofanalysis and tracking periods is totaled. The data is made available as a table. Results areexpressed in the number of calls and duration (hour, minutes, seconds).
Figure 5.33: Trunk Groups — Summary Report
Detailed report
Chapter 5
5-104
This report is used to analyze and compare the respective load of each trunk group. It allowsthe manager to make essential decisions on the optimization and sizing of the different trunkgroups.The data is made available as a table. Results are expressed in number of calls, percentage,and duration (hh:mm:ss). Refer to § Trunk Group Fields for the meaning of the percentagesshown.
Figure 5.34: Trunk Groups — Detailed Report
Detailed report (extended format)This report is same as the Detailed report, except that the name is available in extendedformat.
5-105
Figure 5.35: Trunk Groups — Detailed Report (Extended Format)
Hit-ListThis report enables the 30 most used trunk groups to be displayed. The data is made availableas a bar chart and a table. Results are expressed in number of calls, percentage, or duration(hh:mm:ss).
Chapter 5
5-106
Figure 5.36: Trunk Groups — Hit List
Hourly reports: detailed reportThis report gives a detailed analysis of the changes in the number of calls and traffic over thecourse of a day for the selected trunk group(s). The data is made available as a table.
5-107
Results are expressed in number of calls, percentage, and duration (hh:mm:ss). Refer to §Trunk Group Fields for the meaning of the percentages shown.
Figure 5.37: Hourly Reports — Detailed Report
Reminder 1:
For the selected period of analysis (in this report: previous week), the results for each time period (range)
are added. For example, the results for time period 16:00:00 correspond to the total of all calls between
16h00 and 17h00 over the course of the previous week.
Hourly reports: trafficThis report gives a detailed analysis of the changes in traffic over the course of a day for theselected trunk group(s). The data is made available as a bar chart and a table. Results areexpressed in duration (hh:mm:ss).
Chapter 5
5-108
Figure 5.38: Hourly Reports — Traffic
Reminder 2:
For the selected period of analysis (in this report: previous week), the results for each time period (range)
are added. For example, the results for time period 16:00:00 correspond to the total of all calls between
16h00 and 17h00 over the course of the previous week.
5-109
Hourly reports: Outgoing RequestsThis report shows the changes in the number of outgoing seize attempts for the selected trunkgroup(s) over the course of the day and the number of failed attempts (overflow to anothertrunk or failure). It allows the manager to detect any saturation and make the decisionsrequired to remedy the situation; if, for example, there is a high number of failures, it may benecessary to resize the trunk groups in question or to configure overflow between trunkgroups.The same type of report exists in hourly reports (results presented per hour), daily reports(results presented per day), and monthly reports (results presented per month). The data ismade available as a bar chart and a table. Results are expressed in the number of calls.
Chapter 5
5-110
Figure 5.39: Hourly Reports — Outgoing Requests
Reminder 3:
For the selected period of analysis (in this report: previous week), the results for each time period (range)
are added. For example, the results for time period 16:00:00 correspond to the total of all calls between
16h00 and 17h00 over the course of the previous week.
5-111
Hourly reports: Call distributionThis report shows changes in the number and type of calls over the course of a day. The sametype of report exists in hourly reports (results presented per hour), daily reports (resultspresented per day), and monthly reports (results presented per month).The data is made available as a bar chart and a table. Results are expressed in the number ofcalls.
Chapter 5
5-112
Figure 5.40: Hourly Reports — Outgoing Requests
Reminder 4:
For the selected period of analysis (in this report: previous week), the results for each time period (range)
are added. For example, the results for time period 16:00:00 correspond to the total of all calls between
16h00 and 17h00 over the course of the previous week.
Daily reports: Call distributionThis report shows the changes in the number and type of calls over the course of the month.The same type of report exists in hourly reports (results presented per hour), daily reports(results presented per day), and monthly reports (results presented per month).The data is made available as a bar chart and a table. Results are expressed in the number ofcalls.
5-113
Figure 5.41: Daily Reports — Call Distribution
Monthly reports: Call distributionThis report shows the changes in the number and type of calls over the course of a the year.The same type of report exists in hourly reports (results presented per hour), daily reports(results presented per day), and monthly reports (results presented per month).The data is made available as a bar chart and a table. Results are expressed in the number ofcalls.
Chapter 5
5-114
Figure 5.42: Monthly Reports — Call Distribution
RSC reports: Intra-day trunk load analysisThis report presents the number of incoming and outgoing calls in a day which is sorted byhours from 8am to 6pm. This report is based on the Alcatel-Lucent OmniPCX Enterprise CScounters and is available only for Alcatel-Lucent OmniPCX Enterprise CS.
5.3.4.2 Called Extensions
Detailed reportThis report shows the quality of telephone service for any selected extension: number of callspresented, percentage of calls taken and abandoned, average waiting time before being takenor abandoned, etc. It can be used, for example, to analyze whether forwarding mechanisms (toassociate set, voice mail, etc.) operate correctly.The data is made available as a table. Results are expressed in the number of calls,percentage, and duration (hour, minutes, seconds).
5-115
Figure 5.43: Daily Reports — Called Extensions
Hit-ListThis report is used to view the most often called (incoming) 30 call numbers and the number ofcalls presented to them. The data is made available as a bar chart and a table. Results areexpressed in the number of calls.
Chapter 5
5-116
Figure 5.44: Hit List
Hourly reports: Incoming Calls ProcessingThis report is available in hourly, daily, monthly and yearly form. It gives a breakdown ofanswered and unanswered calls. It enables the manager to track changes in the quality ofphone service on the basis of a simple analysis of data, the number of calls abandoned andthe number taken.The data is made available as a bar chart and a table. Results are expressed in the number ofcalls. The example shows an hourly report. It shows change in call processing by hourlyperiods for all extensions called in the installation during the period of analysis (previousweek).
5-117
Figure 5.45: Hourly Reports: Called Extensions — Incoming Calls Processing
Reminder:
Chapter 5
5-118
For the selected period of analysis (in this report: previous week), the results for each time period (range)
are added. For example, the results for time period 16:00:00 correspond to the total of all incoming calls
between 16h00 and 17h00 for all days of the week month.
Total reports: Incoming Calls ProcessingThis report gives a summary of the breakdown of answered and unanswered calls. It enablesthe quality of phone service to be rapidly and easily assessed. The data is made available as apie chart and a table. Results are expressed as a number and percentage.
Figure 5.46: Total Reports; Called Extensions — Incoming Calls Processing
Total reports: Summary reportThis gives an overview of the quality of service. Any anomalies can be rapidly detected andthen analyzed via detailed reports. It is a total report, which means that data on selectednodes, cost centers, extensions called, and period of analysis is totaled.The data is made available as a table. Results are expressed in the number of calls,
5-119
percentage, and duration (hour, minutes, seconds).
Figure 5.47: Total Reports: Summary Report
Daily reports: Incoming Calls ProcessingThis report is available in hourly, daily, monthly and yearly form. It gives, on an hourly, daily,etc. basis, a breakdown of answered and unanswered calls. It enables the manager to trackchanges in the quality of phone service on the basis of a simple analysis of data, the numberof calls abandoned and the number taken.The data is made available as a bar chart and a table. Results are expressed in the number ofcalls. The example shows a daily report. It shows changes in call processing by a daily periodand for all extensions called in the installation during the period of analysis (previous month).
Chapter 5
5-120
Figure 5.48: Daily Reports— Incoming Calls Processing
5.3.4.3 Terminals
Summary reportThis gives an overview of the quality of service offered by the sets analyzed. Any anomaliescan be rapidly detected and then analyzed via detailed reports. This report can also providedetailed data on the quality of service and Operation mode of a set, particularly if a filter isused on the number of the set to be analyzed.
5-121
It is a total report, which means that data on selected PCXs, sets, period of analysis, andtracking period is totaled. The data is made available as a table. Results are expressed in thenumber of calls and duration (hour, minutes, seconds).
Figure 5.49: Terminals: Summary Report
Hit-ListThis report is used to determine major consumers of company phone resources. The managermay want to offer appropriate tools to these specific users which are appropriate to their callprofile. The data is made available as a bar chart and a table. Results are expressed induration (hh:mm:ss).
Chapter 5
5-122
Figure 5.50: Terminals: Hit-list
Hourly reports: Presented Calls ProcessingThis report shows changes in the quality of service over the day for the selected set(s). Thesame type of report exists in daily reports (results presented per day) and monthly reports(results presented per month).The data is made available as a bar chart and a table. Results are expressed in the number of
5-123
calls.
Figure 5.51: Hourly Reports: Incoming Calls Processing
Reminder 1:
For the selected period of analysis (in this report: previous month), the results for each time period
(range) are added. For example, the results for time period 16 correspond to total traffic between 16h00
Chapter 5
5-124
and 17h00 over the course of the previous month.
Hourly reports: TrafficThis report shows changes in set load over the day, according to the different types of traffic:PCX, external incoming, external outgoing. The data is made available as a bar chart and atable. Results are expressed in duration (hh:mm:ss).
Figure 5.52: Hourly Reports: Traffic
Reminder 2:
For the selected period of analysis (in this report: previous week), the results for each time period (range)
are added. For example, the results for time period 16:00:00 correspond to the total of all set traffic
between 16h00 and 17h00 over the course of the previous week.
Daily reports: Presented Calls ProcessingThis report shows changes in the quality of service over the day for the selected set(s). Thesame type of report exists in hourly reports (results per hours) and monthly reports (results permonth).The data is made available as a bar chart and a table. Results are expressed in the number of
5-125
calls.
Figure 5.53: Daily Reports: Presented Calls Processing
5.3.4.4 Attendant Groups
Hit-ListThis report is used to compare the quality of service of the various groups. It enables, forexample, a group with too high a workload to be detected.The data is made available as a bar chart and a table. Results are expressed as a percentage.Refer to the section describing counters for the meaning of the percentages shown.
Chapter 5
5-126
Figure 5.54: Hit List
Total reports: Call DistributionThis report gives totals of calls presented to or made by the group. It enables the workload ofthe group(s) analyzed to be measured. It is a total report, which means that data on selectedPCXs, attendant groups, period of analysis, and tracking period is totaled.The data is made available in a pie chart and a table. Results are expressed in the number ofcalls and as a percentage of the total calls shown in this report.
5-127
Figure 5.55: Total Reports: Call Distribution
Reminder 1:
Chapter 5
5-128
The "PCX outgoing" counter is incremented each time a call is transferred by an attendant to a set in the
subnet.
Total reports: Origin of external incoming callsThis report is used to analyze the reasons for which attendants are called: direct calls, redial,or overflow following no answer, and to obtain information:
- A large number of direct calls indicates that not enough DID numbers are (probably)distributed outside the company.
- A large number of overflows on no answer indicates, for example, that users do notsufficiently use the tools placed at their disposal when the called party is absent: voicemail, forwarding to secretary/assistant, etc.
- A large number of redials indicates, for example, an unusually high number of errors:incorrect DID numbers, routing errors, etc.
It is a total report, which means that data on selected PCXs, attendant groups, period ofanalysis, and tracking period is totaled.The data is made available as a pie chart and a table. Results are expressed in the number ofcalls and as a percentage of the total calls shown in this report.
5-129
Figure 5.56: Total Reports: Origin of External Incoming Calls
Total reports: Wait time (external calls)This report shows the distribution of external calls according to waiting (on-hold) time beforebeing answered. The thresholds used, T1 and T2, are quality criteria set by the company:Thresholds T1 and T2 can be set in OmniPCX 4400 or Alcatel-Lucent OmniPCX EnterpriseCS management. It is a total report, which means that data on selected PCXs, attendantgroups, period of analysis, and tracking period is totaled.The data is made available as a pie chart and a table. Results are expressed in the number ofcalls and as a percentage of the total calls shown in this report.
Figure 5.57: Total Reports: Wait Time (External Calls)
Total reports: Incoming Calls ProcessingThis report gives a summary of the breakdown of answered and unanswered calls. It enablesquality of phone service of the group(s) analyzed to be rapidly and easily assessed. It is a totalreport, which means that data on selected PCXs, attendant groups, period of analysis, andtracking period is totaled.The data is made available as a pie chart and a table. Results are expressed in the number ofcalls and as a percentage of the total calls shown in this report.
Chapter 5
5-130
Figure 5.58: Total Reports: Incoming Calls Processing
Total reports: Summary reportThis gives an overview of the quality of service offered by attendant group(s) Any anomaliescan be rapidly detected and then analyzed via detailed reports.This report can also provide detailed data on quality of service and Operation mode of a group,particularly if a filter is used on the number of the group to be analyzed. It is a total report,which means that data on selected PCXs, attendant groups, period of analysis, and trackingperiod is totaled.The data is made available as a table. Results are expressed in the number of calls,percentage, and duration (hour, minutes, seconds).
5-131
Figure 5.59: Total Reports: Summary Report
Detailed reports: Operation modeThis report enables the Operation modes used by each group to be analyzed and compared.The data is made available as a table. Results are expressed in duration (hh:mm:ss).
Chapter 5
5-132
Figure 5.60: Detailed Reports: Operation Mode
Hourly reports: Call distributionThis report shows changes in the number and type of calls over the course of a day. Thisenables the manager to assess the number of attendants required to handle incoming andoutgoing traffic.The same type of report exists in hourly reports (results per hour), daily reports (results perday), and monthly reports (results per month). The data is made available as a bar chart and atable. Results are expressed in the number of calls.
5-133
Figure 5.61: Hourly Reports: Call Distribution
Reminder 2:
For the selected period of analysis (in this report: previous week), the results for each time period (range)
are added. For example, the results for time period 16:00:00 correspond to the total of all incoming calls
between 16h00 and 17h00 for all days of the week month.
Hourly reports: Call presentationThis report shows change in quality of service over a day. This enables the manager to resizethe attendant group if required. Threshold T2 can be set in OmniPCX 4400 or Alcatel-LucentOmniPCX Enterprise CS management.The same type of report exists in hourly reports (results per hour), daily reports (results perday), and monthly reports (results per month). The data is made available as a bar chart and atable. Results are expressed in the number of calls.
Chapter 5
5-134
Figure 5.62: Hourly Reports: Call Presentation
Hourly reports: Incoming CallsThis report shows changes in the distribution of public, private, and PCX calls throughout theday. This enables the manager to compare the different types of traffic being serviced byattendant groups and to find the causes of any malfunctions: too many PCX calls to a group orgroups may be the reason for poor service quality with respect to external calls.The same type of report exists in hourly reports (results per hour), daily reports (results perday), and monthly reports (results per month). The data is made available as a bar chart and atable. Results are expressed in the number of calls.
5-135
Figure 5.63: Hourly Reports: Incoming Calls
Reminder 3:
For the selected period of analysis (in this report: previous week), the results for each time period (range)
are added. For example, the results for time period 16:00:00 correspond to the total of all incoming calls
between 16h00 and 17h00 over the course of the previous week.
Chapter 5
5-136
Hourly reports: Average waiting timeThis report shows changes in the average waiting time before external and PCX calls aretaken (over the day). It enables the manager to identify any saturation occurring over thecourse of the day and to take corrective action. It also shows whether attendants are assigningpriority to external or internal traffic.The same type of report exists in hourly reports (results per hour), daily reports (results perday), and monthly reports (results per month). The data is made available as a bar chart and atable. Results are expressed in duration (in seconds in the bar chart and hh:mm:ss in thetable).
5-137
Figure 5.64: Hourly Reports: Average Waiting Time
RSC reports: Call processing analysis per attendant groupThis report shows the monthly traffic analysis data of the Alcatel-Lucent OmniPCX EnterpriseCS attendant group. It is based on the Alcatel-Lucent OmniPCX Enterprise CS counters anddoes not have any filters on the working days or the working hours. This report is availableonly for the Alcatel-Lucent OmniPCX Enterprise CS.
Chapter 5
5-138
RSC reports: Call processing analysis per weekThis report shows the number of incoming calls in a month which is sorted per week fromMonday to Friday between 8am and 6pm. It is based on the Alcatel-Lucent OmniPCXEnterprise CS counters and is available only for the Alcatel-Lucent OmniPCX Enterprise CS.RSC reports: Call processing analysis per dayThis report shows the number of incoming calls in a month which is sorted per day fromMonday to Friday between 8am and 6pm. It is based on the Alcatel-Lucent OmniPCXEnterprise CS counters and is available only for the Alcatel-Lucent OmniPCX Enterprise CS.RSC reports: Call processing analysis per hourThis report shows the number of incoming calls in a month which is sorted per hour fromMonday to Friday between 8am and 6pm. It is based on the Alcatel-Lucent OmniPCXEnterprise CS counters and is available only for the Alcatel-Lucent OmniPCX Enterprise CS.
5.3.4.5 Attendants
Hit-ListThis report allows the number of calls handled by the different attendants to be compared. Itenables, for example, an attendant with too high a workload to be detected. The data is madeavailable as a bar chart and a table. Results are expressed in the number of calls.
5-139
Figure 5.65: Hit-List
Total report: Summary reportThis gives an overview of the quality of service offered by the attendant(s). Any anomalies canbe rapidly detected and then analyzed via detailed reports.This report can also provide detailed data on the quality of service and Operation mode of anattendant, particularly if a filter is used on the number of the attendant to be analyzed.It is a total report, which means that data on selected PCXs, attendant groups, attendants,period of analysis, and tracking period is totaled.The data is made available as a table. Results are expressed in the number of calls andduration (hour, minutes, seconds).
Chapter 5
5-140
Figure 5.66: Total Report: Summary Report
Total Report: External Individual CallsThis report presents (in the form of a summary):
- The distribution of answered and unanswered external calls.
- The distribution of external calls according to wait (on-hold) time before being answered.The thresholds used, T1 and T2, correspond to the quality criteria set by the company: T1and T2 can be set in Alcatel-Lucent OmniPCX Enterprise CS and OmniPCX 4400management.
Only calls to the attendants' specific number are presented in this report.It thus provides an initial measurement of the quality of service offered by the individualattendants. A similar report is described in the section covering "Attendant Groups", anddescribes the quality of service provided by groups.It is a total report, which means that data on selected PCXs, attendant groups, attendants,period of analysis, and tracking period is totaled.Results are expressed in the number of calls and as a percentage of the total calls shown inthis report.
5-141
Figure 5.67: Total Report: External Individual Calls
Total report: Call distributionThis report totals all calls handled or made by the attendants under analysis, whetherpresented on the group number or the attendant's specific number.It is a total report, which means that data on selected PCXs, attendant groups, attendants,period of analysis, and tracking period is totaled.The data is made available in a pie chart and a table. Results are expressed in the number ofcalls and as a percentage of the total calls shown in this report.
Note 1:
The "Outgoing PCX calls" counter is incremented each time a call is transferred by an attendant to a set
in the subnet.
Chapter 5
5-142
Figure 5.68: Total Report: Call Distribution
Total report: PCX individual callsThis report shows the distribution of internal ("local") calls according to wait (on-hold) timebefore being answered. In this case, the quality of attendant service with respect to companystaff is measured.The thresholds used, T1 and T2, are quality criteria set by the company: T1 and T2 can be set
5-143
in Alcatel-Lucent OmniPCX Enterprise CS and OmniPCX 4400 management. Only calls to theattendants' specific number are presented in this report.Again, it is a measurement of the quality of service offered by the individual attendants that isanalyzed in this report. A similar report is described in the section covering "AttendantGroups", and describes the quality of service provided by groups.It is a total report, which means that data on selected PCXs, attendant groups, attendants,period of analysis, and tracking period is totaled.Results are expressed in the number of calls and as a percentage of the total calls shown inthis report.
Figure 5.69: Total Report: PCX Individual Calls
Total report: Attendant statesThis report is used to assess the effective workload of the attendants analyzed and the typesof tasks performed: management operations or call answering.These measurements allow the observations made on the basis of the previous reports to beexplained. A high busy/occupied time, for example, would explain wait times that are too longand allow the manager to make the decision to add an attendant.It is a total report, which means that data on selected PCXs, attendant groups, attendants,period of analysis, and tracking period is totaled.The data is made available as a pie chart and a table. Results are expressed as durations(hh:mm:ss) and as percentages.
Chapter 5
5-144
Figure 5.70: Total Report: Attendant States
Detailed report: Calls ProcessingThis report is used to analyze and compare the respective workload of each attendant. Itallows the manager to make the decisions required to optimize call distribution between theattendants. T2 can be set in Alcatel-Lucent OmniPCX Enterprise CS and OmniPCX 4400management.The data is made available as a table. Results are expressed in number of calls, percentage,and duration (hh:mm:ss). Refer to the section describing counters for the meaning of thepercentages shown.
5-145
Figure 5.71: Detailed Report: Calls Processing
Detailed report: ActivityThis report allows the effective workload of each attendant to be compared and any anomaliesdetected. If all management operations are performed by the same attendant, for example, thiswill result in unacceptable response times.Better distribution of tasks between attendants will result in improved quality of service.The data is made available as a table. The results are expressed as a percentage of timespent in each state.
Chapter 5
5-146
Figure 5.72: Detailed Report: Activity
Hourly report: detailed reportThis report allows the changes in attendant workload over the course of the day and theresulting quality of service to be analyzed.It allows the decisions required to optimize attendant work to be taken, for example,performing both the work of an attendant with that of visitor greeting will be prohibited between10 and 11 o'clock to avoid any drop in the quality of service provided.The data is made available as a table. Results are expressed in number of calls, percentage,and duration (hh:mm:ss). Refer to the section describing counters for the meaning of thepercentages shown. T2 can be set in Alcatel-Lucent OmniPCX Enterprise CS and OmniPCX4400 management.
Note 2:
For the selected period of analysis (in this report: previous month), the results for each time period
(range) are added. For example, the results for time period 16 correspond to the total of all incoming calls
between 16h00 and 17h00 for all days of the previous month.
5-147
Figure 5.73: Hourly Report: Detailed Report
Hourly report: Call distributionThis report presents changes in the types of tasks performed by the selected attendant(s) overthe course of a day: handling of incoming calls to the group, handling of incoming calls to theattendant's specific number, outgoing calls.The same type of report exists in half-hourly reports (results per half-hour), daily reports(results per day), and monthly reports (results per month).The data is made available as a bar chart and a table. Results are expressed in the number ofcalls.
Note 3:
For the selected period of analysis (in this report: previous month), the results for each time period
(range) are added. For example, the results for time period 16 correspond to the total of all calls pro-
cessed or made between 16h00 and 17h00 for all days of the previous month.
Chapter 5
5-148
Figure 5.74: Hourly Report: Call Distribution
Hourly report: Incoming calls TakenThis report presents changes in the types of calls processed by the selected attendant(s) overthe course of a day: public, private, local (i.e. PCX/internal) calls made to the group orattendant's specific number.
5-149
The same type of report exists in half-hourly reports (results per half-hour), daily reports(results per day), and monthly reports (results per month).The data is made available as a bar chart and a table. Results are expressed in the number ofcalls.
Note 4:
For the selected period of analysis (in this report: previous month), the results for each time period
(range) are added. For example, the results for time period 16 correspond to the total of all incoming calls
between 16h00 and 17h00 for all days of the previous month.
Figure 5.75: Hourly Report: Incoming Calls Taken
Hourly report: Attendant statesThis report shows change in attendant status over a day.The same type of report exists in half-hourly reports (results per half-hour), daily reports(results per day), and monthly reports (results per month).The data is made available as a bar chart and a table. Results are expressed in duration (inseconds in the bar chart and hh:mm:ss in the table).
Note 5:
For the selected period of analysis (the previous month, for example), the results for each time period are
added. For example, the results for time period 16 correspond to total time spent in each state between
between 16h00 and 17h00 over the course of the previous month.
Chapter 5
5-150
Figure 5.76: Hourly Report: Attendant States
Hourly report: Activity rateThis report presents changes in the activity rate of the selected attendant(s) over the course ofthe day.The time for which the attendant is considered to be active is the total of the times spent in themanagement or busy states. It allows the the manager to see attendant global workload.The same type of report exists in daily reports (results presented per day) and monthly reports(results presented per month).The data is made available as a bar chart and a table. Results are expressed as a percentage.Refer to the section describing counters for the meaning of the percentages shown.
5-151
Figure 5.77: Hourly Report: Activity Rate
Hourly report: Outgoing CallsThis report allows the number of outgoing calls made by the attendant(s) in the course of a dayto be analyzed.A high number of outgoing public calls may indicate that the attendants are frequently
Chapter 5
5-152
requested by site users to make national or international calls that are otherwise barred tosome users.Reminder: The "Outgoing PCX calls" counter is incremented each time a call is transferred byan attendant to a set in the subnet.The same type of report exists in half-hourly reports (results per half-hour), daily reports(results per day), and monthly reports (results per month).The data is made available as a bar chart and a table. Results are expressed in the number ofcalls.
Note 6:
For the selected period of analysis (in this report: previous month), the results for each time period
(range) are added. For example, the results for time period 16 correspond to the total of all calls made
between 16h00 and 17h00 for all days of the previous month.
5-153
Figure 5.78: Hourly Report: Outgoing Calls
5.3.4.6 DECT/PWT
These reports are half-hourly, hourly, daily, monthly or yearly reports for the following objects:
- System
Chapter 5
5-154
- Radio base stations
- ADPCM
- Sets
- Handoffs
- Hourly break rate
The different reports include a bar chart presenting the most significant counters and a tablewith the title of the different columns shown.
Example reports: For a base station, the predefined reports give the total number of Handoffoperations, the assignments established by the base station and their duration, and abnormalADPCM channel releases.
Classifications in increasing order of busy threshold exceeded and break (cut-off) rates may beestablished for each base station (hit-list type reports).
Figure 5.79: Daily Reports: System
5-155
Figure 5.80: Daily Reports: Base Stations
Chapter 5
5-156
Figure 5.81: Daily Reports: ADPCM Channels
Figure 5.82: Daily Reports: Handover
5-157
Figure 5.83: Traffic Peaks Hit List
Chapter 5
5-158
Figure 5.84: Hit List on Break Rate
5-159
Figure 5.85: Global View on Base Stations
5.4 Predefined threshold exceeded reports
5.4.1 Overview
The Accounting, Traffic analysis and VoIP traffic analysis licenses are required to accessAccounting, Traffic analysis and VoIP traffic analysis threshold exceeded reports.These thresholds must have been previously configured in the tracking profiles (see moduleAccounting - Organization tab § Managing Tracking Profiles ).
5.4.2 List of predefined reports
- Set monitoring (daily duration)
- Tracking Attendants by Groups (abandon rate)*
- Track Trunk Group (Duration of R1 going beyond)*
Note:(*) Not available for OmniPCX Office and Alcatel Office.
5.4.3 Database fields (headers)
This section lists the database fields available to edit report definitions.
Chapter 5
5-160
Note:
The character § in the database field generates a "carriage return" when reports are output.
5.4.3.1 Description
Application codeThis field shows the type of records for which a threshold has been configured (accounting,traffic analysis, VoIP).
Object descriptionThis database field shows the name of the tracked object.
Tracked data codeThis database field shows the type of data tracked (duration, cost, number of calls, quantity(volume), etc.).
5.4.3.2 Threshold
Threshold with integer formatThreshold with float formatThreshold with time formatThreshold with cost formatThreshold with percent formatThese database fields specify the value and format of the report threshold.
Counter with integer formatCounter with float formatCounter with time formatCounter with cost formatCounter with percent formatThese counters allow the total of the tracked value to be calculated.
5.4.3.3 Data
ActionThis database field shows the type of action programmed if the threshold is exceeded (sendE-mail, alarm, or both).
E-mail AddressThis database field shows the E-mail address of the recipient if sending an E-mail has beenprogrammed if a threshold is exceeded.
5.4.3.4 Dates
Counter frequencyThis database field specifies the frequency at which the counter is reset (half hourly, daily,monthly, and yearly).
Threshold crossing dateThis database field shows the date on which the exceeded threshold was detected by theAlcatel-Lucent OmniVista 4760 Network Management System.
Date of the counter
5-161
This database field shows the start of the period of analysis.
5.4.4 Report presentation
5.4.4.1 Beyond threshold (example: Set monitoring (daily durations))
This report is used to detect users that have exceeded a daily call duration threshold.The example given lists the users that have exceeded a daily call duration threshold of 5mn,the date on which the overshoot occurred (25/02/03 15:47:47 (date of detection)) and total callduration for these users on that day.A similar report may be created for cost, variation rate, and volume (number of calls)thresholds according to the different tracking periods (half-hourly, daily, monthly, or yearly).
Note:
The threshold must have been previously entered in the Accounting, Traffic analysis, and VoIP traffic
analysis tracking profiles.
Chapter 5
5-162
Figure 5.86: Beyond threshold: Set monitoring
5.4.4.2 Beyond threshold (Example: Tracking Attendants by Groups (abandon rate))
This report is used to detect attendant groups that have exceeded a daily call abandonthreshold.The example given lists the attendant groups that have exceeded a daily call abandonthreshold of 5%, the date on which the overshoot occurred (25/02/03 15:47:47 (date ofdetection)) and total call duration for these attendant groups on that day.
5-163
A similar report may be created for the abandon rate on called numbers.
Note:
The threshold must have been previously entered in the Accounting, Traffic analysis, and VoIP traffic
analysis tracking profiles.
Figure 5.87: Beyond threshold: Groups of operators monitoring
5.4.4.3 Beyond threshold (Example: Track Trunk Group (Duration of R1 goingbeyond))
Chapter 5
5-164
This report is used to detect the trunk groups supporting a high traffic load and the time thispeak occurred.The Traffic analysis “Busy” counter measures the duration of assignment during which thetrunk group has a busy rate greater than R1 (this threshold can be set in the OmniPCX 4400and Alcatel-Lucent OmniPCX Enterprise CS, by default it is 70%).In addition, the user has set the minimum threshold for this overshoot time in the trackingprofile.For example, a trunk group that has an occupation rate higher than 70% for 25mn over ahalf-hour period (threshold = 25:00 per half-hour) triggers an alarm that is shown in the report.
5-165
Figure 5.88: Beyond threshold: Trunk group monitoring
5.5 Predefined Audit Reports
5.5.1 Predefined Detailed Report
This report displays the list of operations performed.
Figure 5.89: Example of Detailed Report
- Date/Hour: date of action
- Action: type of action (creation, modification, deletion)
- MaoObject: name of the mao object
- ServerName: name of the server from which the action is performed
- MaoUser: user name
5.5.2 Predefined Total Reports
Chapter 5
5-166
5.5.2.1 Operation Hourly Synthesis
This report displays the synthesis of operations hour per hour.
Figure 5.90: Example of Operation Hourly Synthesis
Hour per hour, the audit manager can see which action has been performed.
Information is displayed with a grid and with a diagram
5.5.2.2 Operation Daily Synthesis
This report displays the synthesis of operations day per day.
5-167
Figure 5.91: Example of Operation Daily Synthesis Page 1
Day per day, the audit manager can see which action has been performed.
Information is displayed with a grid and with a diagram
5.6 Predefined VoIP reports
5.6.1 Overview
These reports are available only with Alcatel-Lucent OmniPCX Enterprise CS release 6.2 andhigher and OmniPCX Office 5.0 and higher. A VoIP traffic analysis license is mandatory togenerate these reports.VoIP call records are created by IP phones (e-Reflex and Series 8) and INT-IP and GA/GDboards. They are sent to the Alcatel-Lucent OmniPCX Enterprise CS or the OmniPCX Office atthe end of the call. There are at least two records per IP segment (for more information onrecord downloading, see module Accounting - Parameters tab § Voice over IP ).VoIP performance reports allow the number and quality of VoIP calls to be monitored. Theycan be used to plan adaptations of the IP network according to variations in the number andquality of calls. They also allow audio quality problems to be monitored and anticipated.
Chapter 5
5-168
The tree structure for VoIP traffic analysis reports is composed of:
- Traffic analysis reports, giving information on the number (volume) of VoIP calls with thepackets sent, received, and lost.
- Out of range reports, giving the quality of VoIP calls.
Note:
For VoIP performance reports to present consistent data on "out of range" records from Alcatel-Lucent
OmniPCX Enterprise CSs, IP parameters must be configured consistently on all the Alcatel-Lucent Omni-
PCX Enterprise CS in the network (from release 5.1).
All equipment must be reset for the selected parameter settings to be applied.
Once a choice has been made, such as, for example, to set the “Direct RTP” parameter to Yes or No,
this parameter must be the same everywhere.
5.6.2 Definitions
DelayDelay is the time a test packet (transmitted every 5 seconds) takes to make the round tripbetween two IP terminals. Delay must be less than 400 ms for acceptable audio quality (lessthan 150 ms for excellent audio quality).The VOIP ticket gives the delay data for the ranges [0,40] ms, [40,80] ms, [80,150] ms,[150,250] ms and greater than 250 ms. If the calculated average delay is greater than 150 ms,the VOIP ticket is marked as Out of range.
Jitter, jitter bufferJitter is packet transmission delay variation due to variation in network traffic load. Tocompensate for such variation, a jitter buffer is used to store incoming frames and restitutethem a few milliseconds later at constant speed.Jitter must be less than 50 ms for acceptable audio quality (less than 20 ms for excellent audioquality).This parameter is not taken into account by the Alcatel-Lucent OmniVista 4760 NetworkManagement System (not relevant for all types of equipment).
Lost packets rateThis is the percentage of lost packets with respect to the number of packets transmitted. Thisrate must be less than 3% for acceptable audio quality (less than 1% for excellent audioquality).The VOIP ticket gives the number of lost packets. If the calculated lost packets rate is greaterthan 3%, the VOIP is marked as Out of range.
BFI (Bad Frame Interpolation)BFIs are "ghost" packets transmitted by the called terminal DSP to replace lost packets. BFIsare obtained by interpolating the previous frames.If the calculated BFI rate is greater than 3%, the VOIP is marked as Out of range.The number and concentration (bursts) of consecutive BFIs are indicative of transmissionquality.This parameter is not taken into account by the Alcatel-Lucent OmniVista 4760 NetworkManagement System (not relevant for all types of equipment).
BFI burst (concentration)This is the number of BFIs, whether consecutive or not, transmitted during a given time
5-169
interval.If there was a BFI burst (at least 3% of BFI generated in a short period) and if such a burstconcerns 5% of the communication, the ticket is marked as Out of range.
EncryptionEncryption is a mark in the VOIP call record which enables you to identify whether encryptionwas performed during the communication.
Out of rangeVOIP call records that are extracted from the PCX provide parameters that enable you toqualify the communication. If one of the parameters Delay, Lost packet rate, BFI or BFI bursthas the value out of the default limits, the VOIP ticket is marked as Out of range. Through thereport you can find if a call is Out of range and the corresponding parameter which is not withinthe default limit.
5.6.3 List of predefined reportsTraffic analysis
- IP addresses (3 reports)• Summary report• Detailed report• Summary report - Encryption
- Equipment (5 reports)• Summary report• Detailed report• Hit list on volumes• Hit list on erlangs• Summary report - Encryption• Half-hour reports (3 reports)
• Volume• Duration• Erlang
• Daily reports (1 report)• Volume
• Monthly reports (1 report)• Volume
Out of range
- IP addresses (3 reports)• Summary report• Detailed report• Summary report - Encryption
- Equipment (4 reports)• Summary report• Detailed report• Hit list on out of range records• Summary report - Encryption
Chapter 5
5-170
- Half-hour reports (2 reports)• Out of range records• Ticket distribution
- Daily reports (2 reports)• Out of range records• Ticket distribution
- Monthly reports (2 reports)• Out of range records• Ticket distribution
RSC reports (2 reports)
- Overview of your enterprise VoIP quality
- Overview of your enterprise VoIP quality per equipment
5.6.4 Database Fields (headers)
Note:
The character § in the database field generates a "carriage return" when reports are output.
5.6.4.1 Equipment
Equipment typeThis database field shows the type of equipment from which records originated (coupler board,IP terminal, etc.).
BoardThis database field shows the number of the node-location of the coupler board from which therecords originated. The field is empty if the equipment is not a coupler board.
Phone numberThis database field shows the telephone number of the IP terminal from which the recordsoriginated. The field is empty if the equipment is a coupler board.
Sender IP addressReceiver IP addressThese fields respectively give the IP address of the equipment from which the recordsoriginated and the IP address of the equipment called.
5.6.4.2 Date
Date/HourHalf hourHourDateDayWeekdayWeekMonth
5-171
YearThese fields are typically used to filter the data contained in the database. These are a fewexamples of available filters for the date field: this hour, last hour, today, yesterday, this week,last week, this month, last month, first quarter, 2nd quarter, 3rd quarter, this year, etc.
5.6.4.3 PCX
PCX numberPCXCustomerThese fields give the number of the subnetwork and the name of the PCX to which the callingequipment is connected.Customer addressCustomer zip codeCustomer cityCustomer countryThese fields give the details of the customer (PCX owner).
5.6.4.4 Traffic
Comp. algorithmThis field shows the algorithm used for voice compression (G.711, G.723, or G.729).
FramingThis field shows the time interval (in ms) between transmission of two packets.
Tickets countThis counter gives the selected ticket numbers.
DurationThis field gives call duration.
Sent packetsReceived packetsLost packetsThese counters respectively give the number of packets sent, received, and lost.
Sent volumeReceived volumeLost volumeThese counters respectively give the volumes (in MB) sent, received, and lost.
Average delay (ms)Delay (0–40ms)Delay (40–80ms)Delay (80–150ms)Delay (150–200ms)Delay (40–80ms)Delay (>250ms)These counters respectively give the average round trip delay for a call and indicate whetherthe delay is between 0–40ms, 40–80ms, etc.
Chapter 5
5-172
EncryptionThis field is a boolean which indicates that the VOIP communication segment was encryptedor not and can be used with Detailed reports based on IP tickets.Encryption tickets countThis field is used to calculate the sum or the rate of the encrypted IP tickets and can be usedonly with reports based on IP tickets.
5.6.4.5 Out of range
Out of rangeThis field shows whether one or more criteria are out of range.
Out of range tickets countThis counter gives the number of records with one or more criteria out of range.
Out of range delayThis field shows whether record delay is out of range.
Out of range delays countThis counter gives the number of records with a delay that is out of range.
Encryption out of range tickets countThis counter gives the number of encrypted tickets when one or many criteria are notrespected.
Out of range packet lossThis field shows if the packet loss rate is out of range.
Out of range packet loss rate countThis counter gives the number of records with packet loss rate out of range.
Out of range BFI rateThis field shows whether the BFI rate is out of range.
Out of range BFI rate countThis counter gives the number of records with a BFI rate that is out of range.
Out of range BFI burstThis field shows whether the BFI burst is out of range.
Out of range BFI burst countThis counter gives the number of records with a BFI burst that is out of range.
Within the rangeThis field indicates whether all criteria are within the limits.
In-range tickets countThis counter gives the number of records with all criteria within the limits.
5.6.5 Report presentation
5.6.5.1 Traffic analysis
The traffic analysis reports give information on the number (volume) of VoIP calls with thepackets sent, received, and lost.
5-173
This volume includes compression rate and silences (SID).Special reports have been designed to present the information about encryptioncommunications in case the Encryption feature is set up in the PCX network.
Figure 5.92: Traffic analysis: IP addresses — Summary report
Figure 5.93: Traffic analysis: Equipments — Summary report
Chapter 5
5-174
Figure 5.94: Traffic analysis: Equipments — Detail
5-175
Figure 5.95: Traffic analysis: Equipments — Hit list on volumes
Chapter 5
5-176
Figure 5.96: Traffic analysis: Equipments — Hit list on erlangs
5-177
Figure 5.97: Half — hour reports: Equipments — Volume
Chapter 5
5-178
Figure 5.98: Half — hour reports: Equipments — Duration
5-179
Figure 5.99: Half — hour reports: Equipments — Erlang
Chapter 5
5-180
Figure 5.100: Daily reports: Equipments — Volume
5-181
Figure 5.101: Monthly reports: Equipments — Volume
5.6.5.2 Out of range
The "out of range" reports give information on the quality of VoIP calls. Quality thresholds areset on the Alcatel-Lucent OmniVista 4760 Network Management System for the followingsignificant criteria (loss rate, average delay, BFI rate and BFI burst ). If one of these thresholdsis exceeded, the record is classified as "out of range" and counted for global qualitymonitoring.VoIP traffic analysis records may be generated:
Chapter 5
5-182
- Between two IP addresses or two series of IP addresses to analyze traffic and quality on aspecific segment of the IP network.
- For a type of Alcatel-Lucent OmniPCX Enterprise CS device, IP Phone or board, or for aspecific device, to obtain a summary of traffic and quality or to identify a faulty device.
Special reports have been designed to present the information about encryptioncommunications in case the Encryption feature is set up in the PCX network.
Figure 5.102: Summary report: IP addresses
Figure 5.103: Detailed report: IP addresses
The equipments Out of range reports display is the same as IP Address OUt of range report.
5-183
Figure 5.104: Hit list on out of range tickets
Chapter 5
5-184
Figure 5.105: Half — hour reports: Out of range tickets rate
5-185
Figure 5.106: Daily reports: Out of range tickets rate
Chapter 5
5-186
Figure 5.107: Monthly reports: Out of range tickets rate
5.6.5.3 RSC reports
RSC reports are available only with the appropriate license.RSC reports include the following:
- Overview of your enterprise VoIP quality: It is a summary report based on the VoIPrecords and it gives information about the out of range records.
- Overview of your enterprise VoIP quality per equipment: This report gives the
5-187
information of 50 equipments which produce the most out of range records.
5.7 Predefined reports on alarms and events
5.7.1 List of predefined reportsAlarms (3 reports)
- Alarms resolution time
- Alarm daily synthesis
- Daily synthesis by severityEvents (1 report)
- Events daily synthesisRSC reports (1 report)
- Alarms detailed by severity and reception date
5.7.2 Database fields (headers)
5.7.2.1 Organization
PCXThis field gives the name of the PCX.
CustomerCustomer addressCustomer zip codeCustomer cityCustomer countryThese fields show the details of the customer (PCX owner).
5.7.2.2 Date
Day (notification)Month (notification)Year (notification)Notification timeThese fields show the day and date of alarm notification by the PCX.
Reception timeAcknowledgment timeResolution timeThese fields respectively show the dates on which the alarm was received, acknowledged, andresolved by the Alcatel-Lucent OmniVista 4760 Network Management System.
Acknowledgment durationResolution durationThese fields show the time taken to acknowledge and resolve the alarm.
5.7.2.3 Object
Chapter 5
5-188
Type (from hardware)This field indicates the type of equipment that emitted the A4400 alarm (OmniPCX4400/Alcatel-Lucent OmniPCX Enterprise CS), NMC (Alcatel-Lucent OmniVista 4760 NetworkManagement System), ALIZE (OmniPCX Office), RMA-RMA board (in the OmniPCX4400/Alcatel-Lucent OmniPCX Enterprise CS).
Local severity
Global severity
5.7.2.4 Incidents
IdentifierThis field gives the order in which the alarm was transmitted by the PCX.
Incident numberThis field gives the order in which the alarm was received by the Alcatel-Lucent OmniVista4760 Network Management System.
Additional textThis field gives a brief description of the alarm.
SeverityThis field gives alarm severity (critical, major, minor, warning, indeterminate).
DiagnosticThis field gives diagnostic code.
Probable causeThis field gives the probable cause of the alarm (error, malfunction, failure, etc.).
Incident typeThis field gives alarm type (equipment, environment, call, etc. alarm).
Managed objectThis field shows the sender of the alarm.
StateThis field indicates whether the alarm is active, acknowledged or cleared.
Acknowledged byResolved byThese fields show the name of the person who acknowledged the alarm and the name of theperson who cleared the alarm.
CriticalMajorMinorWarningUnspecifiedThese fields allow sorting or totaling by severity.SignAction
5.7.2.5 Events
5-189
Managed objectThis field shows the sender of the event.
TypeThis field shows the type of event (creation, modification, or deletion).
CreationDeletionModificationInformationThese fields allow sorting or totaling by type of event.
5.7.3 Report presentation
5.7.3.1 Alarms
Alarms resolution time
This report is used to check the quality of network maintenance by daily output of the averagetime (delay) required to clear alarms.The report includes a bar chart.
Note:
An alarm is considered to be cleared when the administrator has set it to "cleared" in the Alcatel-Lucent
OmniVista 4760 Network Management System alarms application.
Chapter 5
5-190
Figure 5.108: Alarms resolution time
Alarm daily synthesisThis report is a summary of alarms that occurred on the network over a given period (bydefault, the previous month).Alarms are totaled daily by severity.This report is used for monthly tracking of alarms, their severity and any sudden surge ofalarms on certain days.
5-191
Figure 5.109: Alarm daily synthesis
Figure 5.110: Alarm daily synthesis
Chapter 5
5-192
Daily synthesis by severity
This report is identical to the alarm daily synthesis but is for alarms of a given severity, forexample major alarms.The report includes a bar chart.
Figure 5.111: Daily synthesis by severity
5-193
Figure 5.112: Daily synthesis by severity
5.7.3.2 Events
Events daily synthesis
This report is used to track the number of daily actions performed by the Alcatel-LucentOmniVista 4760 Network Management System configuration application on theOmniPCX 4400and Alcatel-Lucent OmniPCX Enterprise CS for a monthly period (default setting) and by typeof action (creation, deletion, modification).This report allows maintenance to be tracked.
Chapter 5
5-194
Figure 5.113: Events daily synthesis
5-195
Figure 5.114: Events daily synthesis
5.7.3.3 RSC reports
This report is used for the Remote Service Center and it presents the details of the alarmsfiltered for a customer and grouped by severity for the preceeding month.
Chapter 5
5-196
Figure 5.115: Alarms detailed by severity and reception date
5-197
Chapter 5
5-198
6.1 Overview
6.1.1 Alarm Management: General
The Alarm application is used to view and track:
- PCX alarms and events.
- Internal alarms sent by Alcatel-Lucent OmniVista 4760 Communication ManagementSystem (called Alcatel-Lucent OmniVista 4760 Network Management System in thisdocument). applications.
The alarm server runs as a background task and, on the Alcatel-Lucent OmniVista 4760Network Management System client side, an audio signal may be emitted when a new alarm isreceived.
Figure 6.1: Alarm Management Process Diagram
Alarms that have been processed may be retransmitted by the Alcatel-Lucent OmniVista 4760Network Management System to a hypervisor in the form of SNMP traps.
Alarms are transmitted in real time. A synchronisation (alarms are transmitted again) isrequired by the Alcatel-Lucent OmniVista 4760 Network Management System in the followingcases:
- Restart of the Alarm application
- EFD (Event Forwarding Discriminator) refresh failure
- Command ( )
During a synchronisation, the PCXs monitored by the Alcatel-Lucent OmniVista 4760 NetworkManagement System only transmit active correlated alarms. Alarms are not retransmitted afteran Alcatel-Lucent OmniPCX Enterprise CS synchronization.
6
6-1
Note:
The Passive Communication Server alarms are not managed by the Alcatel-Lucent OmniVista 4760 Net-
work Management System Alarms application.
6.1.2 Specific Menu
When the Alarms application is running, the Preferences menu bar offers an Alarmssubmenu containing the following items:
- Configuration: To configure default display mode refer to module Alarms - Viewing alarms§ Alarm history and active alarms .To add predefined signatures refer to module Alarms - Configuring Alarm Application §Adding a Predefined Signature or a Predefined Action .To modify predefined signatures refer to module Alarms - Configuring Alarm Application §Modifying a Predefined Signature or a Predefined Action .To delete predefined signatures refer to module Alarms - Configuring Alarm Application §Deleting a Predefined Signature or a Predefined Action ..
- SNMP Filter: To filter alarms retransmitted as SNMP traps, refer to module Alarms -Configuring Alarm Application § Filtering Alarms to Send SNMP Traps ..
- Alarm Filters: To configure sending of an E-mail or running of a script when an alarm isdetected, refer to module Alarms - Configuring Alarm Application § Defining Action Takenon Alarm Reception ..
6.1.3 Terms Used
6.1.3.1 Alarm
An alarm indicates a malfunction with degree of severity and changes status according to thesteps taken to correct this malfunction.
6.1.3.1.1 Types of Alarms
- Communication alarm.For example: PCX connection failure.
- Equipment alarm.For example: Terminal loss.
- Processing error alarm.For example: Error detected during cost calculation.
- Environmental alarm.For example: Power supply problem.
- Quality of Service alarm.For example: The link with the Alcatel-Lucent OmniVista 4760 Network ManagementSystem has been cut off long enough to produce a loss of events.
Chapter 6
6-2
- RADIUS alarmsFor example: RADIUS servers are disabled, communication failure or other issues withRADIUS server, and also when authentication mode involves RADIUS server while noservers are configured or no security is allowed in license file.
6.1.3.1.2 Alarm Status
- Active: New alarm.
- Acknowledged: Alarm considered, handled.
- Cleared: The problem has been solved.
6.1.3.1.3 Color Code/Severity
There are five levels of severity, each is color coded. The minimum level of severity isindeterminate, the maximum level of severity is critical.
Figure 6.2: Color Code/ Severity
Cleared alarm: white.
6.1.3.1.4 Correlated Alarm
An alarm corresponds to a problem, with a start corresponding to the detection of the problemand an end corresponding to the clearing of the problem:
- When the end of the problem can be detected by the PCX , the alarm is referred to ascorrelated.
- When the end of the problem cannot be detected by the PCX , the alarm is referred to asuncorrelated. Correction must be performed manually by the application user.
6.1.3.2 Event
An event is generated by the PCX network. It gives information and has no severity or status.
Applications do not generate events.Examples of events that may occur:
- Object creation.
- Object deletion.
- Change of attribute value.
- ...
6-3
6.2 Setting reception parameters
6.2.1 Licenses
The alarm server has several operating modes according to the licenses installed.
With one Alarm license:
If the Alarm license is present, the alarm server receives and stores:
- Alarms and events from PCXs that are declared in the System directory and that have analarms license.
- Alcatel-Lucent OmniVista 4760 Network Management System internal alarms.
Without an Alarm license:
If an Accounting, Traffic analysis, or Directory license is present, the alarm server receivesand stores:
- Only events from PCXs that are declared in the System directory and that have analarms license.
- Alcatel-Lucent OmniVista 4760 Network Management System internal alarms.
If none of the PCXs declared has an alarms license, only Alcatel-Lucent OmniVista 4760Network Management System internal alarms are handled by the alarm server.
6.2.2 Setting PCX Alarm and Event Reception Parameters
To set the PCX alarm and event reception parameters, you must:
- Configure the System directory for alarm and event reception and for SNMP tracking.
- Configure the PCX for event reception.
6.2.2.1 Configure the System Directory to Receive Alarms and Events and TransmitSNMP Traps.
These operations are performed for each PCX individually.To receive alarms and events from a PCX:
1. Select the PCX from the System directory.
2. Select a value for the attribute Alarm reception mode to define the way the alarms andevents are to be received from the PCX, from the following list.• None: No alarm or event is to be processed by the Alcatel-Lucent OmniVista 4760
Network Management System server (OmniPCX 4400, Alcatel-Lucent OmniPCXEnterprise CS and OmniPCX Office).
• HTTP notification: An http notification is sent to request an IP connection in order toreceive the alarms (OmniPCX Office only).
• Permanent IP connectivity: The Alcatel-Lucent OmniVista 4760 NetworkManagement System server establishes a permanent IP connection to receive thealarms and events (OmniPCX 4400, Alcatel-Lucent OmniPCX Enterprise CS andOmniPCX Office).
• Through supervision node: A supervision node centralizes the alarms and events for
Chapter 6
6-4
this node. The Alcatel-Lucent OmniVista 4760 Network Management System receivesalarms and events (including alarms and events for the current node) only from thesupervision node (Alcatel-Lucent OmniPCX Enterprise CS only).
• RMA calls: The alarms are sent through an RMA box (Alcatel-Lucent OmniPCXEnterprise CS only).
• PPP urgent alarm call: All the alarms are received through a single call (OmniPCXOffice only).
3. Click Apply to accept the changes.To transmit SNMP traps generated from PCX alarms to a hypervisor:
1. Create a Hypervisor entry in the System directory.
2. Enter its IP address.
3. Select a PCX from the System directory.
4. Check the Managed by SNMP proxy attribute box.
5. Click Apply to accept changes.
6.2.2.2 Configuring the PCX for Event Reception
This operation is performed for each individual PCX and is required to ensure correctsynchronization of PCX objects.To enable event reception from a PCX:
1. Open the Configuration application in connected mode (PCX tab).
2. Select System >.
3. Check the Synchro.4400 - 47xx directory attribute.
6.2.3 Configuring Centralized Alarms for a Network Node
For an Alcatel-Lucent OmniPCX Enterprise CS or OmniPCX 4400 network, a centralized alarmPCX may be specified. To do this:
- Configure the centralized alarm PCX.
- Configure the System directory for centralized alarms.
6.2.3.1 Configuring the Centralized Alarm PCX
This operation is only to be performed on the centralized alarm PCX.To declare nodes supervised by the centralized alarm PCX:
1. Launch the Configuration application and connect to the desired PCX.
2. Select Applications > Incident manager > Supervised node.
3. Declare all nodes to be supervised by the PCX.
Note:Do not declare the centralized alarm PCX in the list of nodes to be supervised.
6.2.3.2 Configuring the System Directory for Centralized Alarms
This operation must be performed in the sequence shown below (mandatory).To declare the centralized alarm PCX:
1. Declare all the PCXs (supervisor and supervised) in the System directory without
6-5
updating the Alarm reception mode attribute (None by default).
2. Select the supervisor PCX and update the attribute Alarm reception mode with its exactreception mode.
3. Select all the supervised nodes and update the attributeAlarm reception mode with theoption Through supervision node.
4. Click Apply to accept the changes.
Note:If you want to switch from a non-centralized configuration to a centralized configuration:
a. In the System directory, select the option None as the value for the attribute Alarm receptionmode for all the PCXs for which you want to centralize the alarms, including the supervisor PCX.
b. Declare the supervised PCXs on the supervisor PCX.
c. Select the supervisor PCX and update the attribute Alarm reception mode with its exact recep-tion mode.
d. Select all the supervised nodes and update the attribute alarm reception mode with the optionThrough supervision node.
6.2.4 Configuring Alarms (Incidents) Filtering on a PCX
Alarm filtering allows to optimize services on a PCX:
- Reduce the flow between the PCX and the Alcatel-Lucent OmniVista 4760 NetworkManagement System server
- Reduce the processing time on the Alcatel-Lucent OmniVista 4760 Network ManagementSystem server
- Suppress repetitive alarms
- Select relevant alarms for a specific configuration
To configure alarm filtering on PCX :
1. Open the Configuration application
2. Expand the tree structure and select the target PCX
3. Select: Application > Alarm management
4. Review/modify the following attributes:
Chapter 6
6-6
Network Severity Select the alarms to be sent to the Alcatel-Lucent OmniVista4760 Network Management System server.Possible values are:• None: alarms are not sent• Critical: only critical PCX alarms are sent• Indeterminate: indeterminate and critical PCX alarms are
sent• Major: major , indeterminate and critical PCX alarms are
sent• Minor: minor , major, indeterminate and critical PCX
alarms are sent• Informational: warning, minor, major, indeterminate and
critical PCX alarms are sent• Clear: all alarms are sent except if the alarm is defined in
a filter
Topological Network Yes: topological alarms are sent to the Alcatel-LucentOmniVista 4760 Network Management System server.No: topological alarms are not sent.
The other attributes are not specific to PCX alarm filtering.
5. Confirm your entries
For more information on PCX alarms, see the corresponding documentation.
6.3 Viewing alarms
6.3.1 Overview
For general viewing and modification, see:
- module Interface - Viewing data ,
- module Interface - Data search ,
- module Interface - Modifying data .
6-7
Figure 6.3: Main window — Alarms application
6.3.2 Alarm counters
The application interface has three alarm counters:
1. The main window counter.
2. The alarm counter with degree of severity.
3. The data field counter.
6.3.2.1 Main window counter
An alarm counter is displayed at the bottom of the main window.
It is used to display:
- The number of active alarms received by the server.
- The maximum severity of these alarms.
Place the cursor on this counter to display the number of active alarms received by degree ofseverity.
Chapter 6
6-8
Figure 6.4: Alarm counter
This counter is always operational, even when the ALARMS application is not running. Thecolor of the frame of this counter shows the maximum severity of active alarms.
6.3.2.2 Alarm counter with degree of severity
Colored counters are displayed in the data field of the Alarm window. They display the numberof active alarms received by degree of severity, according to a color code.
Values:
table 6.2: Alarm counter values — Example0 25 4 0 0
Background color:
table 6.3: Alarm counter colors— ExampleRed Orange Yellow Blue Violet
6.3.2.3 Data field counter
A counter on a white background shows the number of events or alarms listed in the data field.
See module Alarms - Configuring Alarm Application § Setting List Size
6.3.3 Browsing from trees
The Alarm and Event trees are automatically constructed according to alarms and eventsreceived by the alarm server:
- They consist of network items that are the source of alarms or events stored in thedatabase.
- They are dynamically refreshed when a network item not yet shown is the source of a newalarm (or event).
- They are dynamically updated to display the alarms received (see § Special features of theAlarm tree ).
Only items that generated alarms (or events) are displayed in the trees.
6.3.3.1 Description of the trees
The Alarm and Event trees are separate.
6.3.3.1.1 Alarm tree
Network items that are the source of alarms are:
6-9
For alarms from the PCX:
- Network• Subnet
• PCX• Other items, such as:
• Inter-node links• Shelves• etc.
For alarms from applications:
- Server• Name of the application
• Name of the module
6.3.3.1.2 Event tree
Network items that are the source of events from the PCX are:
- Network• Subnet
• PCX• Other items, such as:
• Translator• Users• Directory• Speed dialing• etc.
6.3.3.2 Special features of the Alarm tree
For each item, a colored circle may be displayed. This may represent, either:
- For a collapsed branch: maximum alarm severity for items and sub-items.
- For an expanded branch: maximum alarm severity for the item.
The alarm tree display is refreshed as soon as the degree of severity for an item changes.
6.3.4 Browsing from the data field
6.3.4.1 Displaying alarms and events
You can display alarms and events:
- In the form of a list, in a table.
- In detail, as a record.
To display alarm details, either:
Select the Details command from the shortcut menu, or click the icon.
Chapter 6
6-10
To display the list, either:
Select the List command from the shortcut menu, or click the icon.
6.3.4.1.1 Viewing alarms
Alarms in a table
In table format, the columns displayed are:
- No.
- Severity
- Diagnostic
- Managed Object
- Notification Date
- Additional Text
- Event Type
- Probable Cause
table 6.4: Alarm fieldsFields Values
No. This number is incremented each time an alarm is received andis assigned by the alarm server. By default, in this column,alarms are sorted in ascending order corresponding to thechronological order of reception.
Severity Shows the severity of the alarm. There are six levels of severity,each is color-coded. The minimum level of severity isindeterminate, the maximum level of severity is critical.
Diagnostic Incident number associated with the alarm.
Managed Object Identifies the object that is the source of the alarm.
Notification Date Date and time at which the alarm was generated.
Additional text Description of the alarm.
Event Type Event type identification.
Probable Cause Identification of the probable cause.
Alarms in record format
The following fields are available in record format:
- No.
- Managed Object
- Event type
- Notification date
- Probable cause
- Severity
6-11
- Reception date
- Notification ID
- Additional text
- Information
- Diagnostic
Fields used for providing the comments for the alarms:
- Sign
- Action
- Remark
Additional fields displayed on acknowledgement or clearing:
- Acknowledged: Name
- Acknowledged: Date
- Cleared: Name
- Cleared: Date
table 6.5: Additional alarm fieldsFields Values
Reception date Date and time at which the alarm or event was received by thealarm server.
Notification ID Number incremented each time an alarm is generated. This isassigned by the PCX. For application alarms, this numberidentifies the alarm.
Acknowledged: name Name of the user who acknowledged the alarm.
Acknowledged: date Date and time at which the user acknowledged the alarm.
Cleared: name Name of the user who cleared the alarm.
Cleared: date Date and time at which the user cleared the alarm.
Information Incident number associated with the alarm.
Diagnostic Detailed description of the alarm and steps to take to correctthe problem.
Sign Name of the responsible person who treated the problem. Formanaging the sign values refer to the sections module Alarms- Configuring Alarm Application § Adding a PredefinedSignature or a Predefined Action , module Alarms -Configuring Alarm Application § Modifying a PredefinedSignature or a Predefined Action and module Alarms -Configuring Alarm Application § Deleting a PredefinedSignature or a Predefined Action .
Chapter 6
6-12
Fields Values
Action Action performed by the responsible person. For managing thesign values refer to the sections module Alarms - ConfiguringAlarm Application § Adding a Predefined Signature or aPredefined Action , module Alarms - Configuring AlarmApplication § Modifying a Predefined Signature or a PredefinedAction and module Alarms - Configuring Alarm Application §Deleting a Predefined Signature or a Predefined Action .
Remark Additional remark related to the problem.
Remarks:
The name of the fields Sign, Action and Remarks are customizable (for more information refer to mod-
ule Interface - Customizing dictionaries ) These names will also be used in alarm reports (for more in-
formation refer to module Reports - Predefined reports on alarms and events ).
6.3.4.1.2 Viewing events
Events in table format
In table format, the columns displayed are:
- No.
- Managed Object
- Notification Date
- Event Type
- Reception Date
table 6.6: Event fieldsFields Values
No. This number is incremented each time an alarm is received andis assigned by the alarm server. By default, in this column,events are sorted in ascending order corresponding to thechronological order of reception.
Managed Object Identifies the object that is the source of the event.
Event Type Event type identification.
Notification/Reception Date Date and time at which the event was generated/received.
Events in record format
In record format, fields without a value are not displayed.
Record format includes:
- Table format fields:• No.• Managed Object• Event Type• Notification Date• Reception Date
6-13
- The following specific fields:• Notification ID• Information
table 6.7: Specific event fieldsFields Values
Notification ID Number incremented each time an event is generated. Thisis assigned by the PCX.
Information Coded data on the event from the PCX.
6.3.4.2 Sorting on a column
By default, alarms and events are sorted in ascending order according to the No. column ( ).
At any time, you can sort on another column, in ascending or descending order, byright-clicking the column header.
6.3.4.3 Alarm history and active alarms
Display history:
- All alarms are displayed.
- Active alarms are color-coded. Cleared alarms are white.
Display active:
- Only active alarms are displayed in active mode.
- Each new alarm received is added to the list.
- An alarm disappears from the list after automatic or manual clearing (it remains in thehistory).
Example:
A minor correlated alarm (yellow) is displayed. When cleared, it disappears from the active list. In the
history, it turns white and a cleared alarm is displayed.
Configuring default display mode
You can select the default display mode:
1. Select Preferences > Alarms > Configuration.The Notification window is displayed.
2. Select or clear the Review history per default box.
3. Click OK.
Switching between the history and active displays:
1. Click the icon to switch to the history or active display.
6.3.5 Filtering
The Alarms application search section has a special mode of operation - a filter that may be
Chapter 6
6-14
enabled or disabled.
Filter status (enabled or disabled) may modify:
- List display.
- The value of the data field counter.See § Data field counter .
by either:
- Click to depress the button to enable the filter (it turns dark gray).
- Click to release the button to disable the filter.
See module Interface - Overview for search criteria.
6.4 Managing alarms
6.4.1 Requirements
Acknowledgement, clearing and/or deletion can only be performed by users with theappropriate rights.See module Security - Overview .
6.4.2 Acknowledging an alarm
Acknowledging an alarm shows that the alarm has been considered and that someone isdealing with the problem.
You can only acknowledge active alarms. These are new alarms.
To acknowledge an alarm:
1. Select the alarm in the data area.
2. Select the Acknowledge command from the shortcut menu.
6-15
Figure 6.5: Alarm acknowledging
When an alarm has been acknowledged:
- Its appearance changes (color of frame and white background).
- It remains active and visible in active mode.
- The Name field, visible in a record, contains the User Name (name of the person whoacknowledged it).
6.4.3 Signing an alarm
The user who troubleshoots the alarm can sign the alarm by using a predefined signature.To sign the alarm:
1. Display the alarm in record format. For more information refer to module Alarms - Viewingalarms § Displaying alarms and events
2. Select the Sign field. A list of user names is displayed.
3. Select a user name from the list.
4. Select the Action field. A list is displayed.
5. Select an action from the list.
Chapter 6
6-16
6. Enter the remarks if you have any, in Remark.
7. Click Apply to sign the alarm.
Note:
You can provide all the three values sign, action and remarks or any combination of them based on the
requirement.
6.4.4 Clearing an alarm
Clearing an alarm shows that the problem indicated by the alarm has been solved.
Only uncorrelated alarms may be cleared.
To clear an alarm:
1. Select the alarm in the data area.
2. Select the Clear command from the shortcut menu.
Server Alarms and Topology applications are notified of this change of status.
6-17
Figure 6.6: Alarm clearing
In active mode, when an alarm is cleared, it no longer appears in the list of alarms. However, itremains visible in history mode.
Remark:
Correlated alarms are cleared automatically.
6.4.5 Deleting a branch
You can delete a branch of the Alarms or Events trees using the shortcut menu:
1. Select a sub-level of the tree structure.
2. Select the Delete a branch command from the shortcut menu.All alarms corresponding to the selected level (and all sub-levels) are deleted from the
Chapter 6
6-18
alarms database. All entries for the selected object are also deleted from the database andare no longer displayed in the tree structure.
6.5 Configuring Alarm Application
6.5.1 Configuring Alarm Cleaning
The alarm and event history is reloaded at application startup.
Alarm cleaning is scheduled. This work task is executed daily - module Scheduler - Overview .
You can configure cleaning by limiting the number of alarms and events that remain in thehistory after cleaning.
Event cleaning criterion:
The oldest events are deleted.
Alarm cleaning criterion:
1. Cleared alarms that are older than the number of days specified in Purge limit forincidents (days) are deleted.
2. A critical alarm is sent if the number of alarms reaches 80% of the limit specified in Purgelimit for incidents (days).
3. If the number of alarms exceeds the limit specified in Purge limit for incidents (days), thecleared and uncorrelated alarms which are not signed by the user are deleted startingwith the oldest, until the number of alarms are within the specified limit.
4. If the number of alarms still exceed the limit specified in Purge limit for incidents (days),all the alarms that are not signed by the user are deleted starting with the older alarms first,until the number of alarms are with in the specified limit.
To set alarm cleaning parameters:
1. In the Directory application, select System tab > Server_name > Servers >Server_name >Alarm server.
2. Enter the Purge limit for incidents (days) attribute (value expressed in number of days,default value 45 days)
3. Enter the Purge limit for incidents (days) attribute (value expressed in number of alarms,default value 10,000).
4. Enter the Purge limit for events (days) attribute (value expressed in number of days,default value 45 days)
5. Enter the Purge limit for events (days) attribute (value expressed in number of events,default value 10,000).
6. Click Apply to confirm your changes.
Note 1:
Obsolete signatures are deleted from the predefined signature list by the daily alarm purge.
Note 2:
Cleaning the alarm tree: An item in the tree is automatically deleted when the last alarm associated with
the item is deleted from the database. Depending on the scheduled cleaning interval for alarms recorded
in the database, the tree may still contain a PCX even though the PCX was deleted from the System dir-
6-19
ectory.
If you want to delete an item that is still displayed in the tree without waiting for all its alarms to be
cleaned, see the module Alarms - Managing alarms § Deleting a branch.
To set alarm reports cleaning parameters:
1. In the Directory application, select System tab > Server_name > Servers >Server_name >Alarm server.
2. Enter the Purge limit for reports (days) attribute (value expressed in number of days,default value 45 days)
3. Click Apply to confirm your changes.
6.5.2 Setting List Size
The number of alarms and events allowed in the data field is limited.It is between 10 and 2,000. By default, it is set at 1,000.
To set the maximum value:
1. Select Preferences > Alarms > Configuration.The Notification window is displayed.
2. Complete the List Size fields, for alarms and events.
3. Click OK.
6.5.3 Requesting an Audio Signal for an Alarm or Event
You can set an audio signal for alarm and event reception:
1. Select Preferences > Alarms > Configuration.The Notification window is displayed.
2. Select or clear the Play sound when notifications arrive box.
3. Click OK.
Note:
On the server, an audio signal showing the severity and type of alarm may be used (see module Alarms -
Managing alarms § Specifying a script).
6.5.4 Adding a Predefined Signature or a Predefined Action
You can create predefined signatures to be used by the operator when signing an alarm.To add a predefined signature:
1. Select Preferences > Alarms > Configuration. The Notification window is displayed.
2. Enter the name of the user to be added to the predefined signature list.
Note:You must be in the Sign tab to include a name. By default the system selects the Sign tab.
3. Click Add.
4. Click OK to save the predefined signature.
Chapter 6
6-20
To add a predefined action:
1. Select Preferences > Alarms > Configuration. The Notification window is displayed.
2. Select the Action tab.
3. Enter the action to be added to the list.
4. Click Add.
5. Click OK to save the predefined action.
6.5.5 Modifying a Predefined Signature or a Predefined Action
You can modify the user name and the action by selecting the respective tabs.
1. Select Preferences > Alarms > Configuration.The Notification window is displayed.
2. Select the Sign and Action tabs to modify the names and the actions respectively.
3. Select the item you want to modify and perform the modifications.
4. Click Modify. A confirmation window is displayed.
5. Click OK.
6.5.6 Deleting a Predefined Signature or a Predefined Action
To delete a predefined signature:
1. Select Preferences > Alarms > Configuration.The Notification window is displayed.
2. Select the Sign and Action tabs to delete the names and the actions respectively.
3. Select the item you want to delete.
4. Click Remove. A confirmation window is displayed.
5. Click OK.
6.5.7 Defining Action Taken on Alarm Reception
Select Preferences > Alarms > Alarm filters to define the criteria allowing the followingactions to be performed when certain types of alarms are received:
- Send E-mail.
- Run a script.
The Alarm Filters window is displayed.
6-21
Figure 6.7: Alarm Filter Window
6.5.7.1 Creating a Filter
Alarm filters include:
- Alarm filtering keys (criteria).
- Predefined actions:• Send E-mail• Run script
Each filter triggers sending of E-mail or running a script when an alarm matching the filteringkey settings is received.When installing the server, an E-mail server may be declared. During operation, theadministrator may also declare it in the System Directory at the following location: Nmc >ServerName > Mail Server.
A filter may include:
- One or more E-mail addresses.
- A single script.
To create a filter, you must:
1. Name the filter.
2. Specify the filtering keys.
3. Specify the E-mail addresses and/or script.
Chapter 6
6-22
6.5.7.1.1 Naming a Filter
1. Enter the name of the filter in the (1) field.
2. Click Add.The name disappears from field (1) and appears in the list of filters (2).
6.5.7.1.2 Specifying Filtering Keys (Criteria)
1. Select a key (3).
2. Select an operator (4).
3. Select or enter a key value (5).
Adding/removing filtering keys:
- Click to add a filtering key.
- Click to remove a filtering key.
Note:
If the key is a hierarchical object, copy the object (shelf, board ...) from the Configuration application
(Ctrl + C) and paste it to the filter (Ctrl + V)
6.5.7.1.3 Adding an E-mail Address
Note:
The default address of the sender is “omnivista@<4760server_name>.<DNSsuffix_name>”. This address
may be modified in the System directory.
1. Enter an address in field (6).
2. Click Add.The address disappears from field (6) and appears in the list of addresses (7).
3. by either:• Click OK to confirm and close the window.• Click Apply to confirm without closing the window.
6.5.7.1.4 Specifying a Script
A script is an executable file (.bat only) that is run when an alarm matching the specifiedfiltering keys is received. A file with an .exe extension can be run via a service or .bat file.To simplify use, scripts that open an window or a graphic interface are not authorized.
1. Click the Script tab.
2. Complete the field, click Search to select a file.
3. You can add one or more of the following parameters:
table 6.8: Script Parameters
6-23
Value to Be Entered Parameter
$eventtype Type of event
$severity Alarm severity
$probablecause Probable cause
$managedobject Managed object
$objecthierarchy Managed object
$incidentnumber Notification number
$addinfo Information
$addtext Additional text
$notificationtime Notification date/time
$receptiontime Reception date/time
Example:journal.bat §eventtype. This script must be in C:\system32, if no other location is specified. Thisutility can create a log.txt file listing alarms with a description and time of detection. The contents ofjournal.bat are then:
• time /T >> log.txt
• echo %1 >> log.txt
The second command line transmits the §eventtype argument for it to be written in the log.txt file.
4. by either:• Click OK to confirm and close the window.• Click Apply to confirm without closing the window.
6.5.7.1.5 Possible Value of Parameters
Parameters and possible values for script in the alarm server (with alarmtrigger).
$eventtype
$eventtype : Type of event (OSI values)
0 : Unknown
1 : Attribute value change
2 : Communication alarm
3 : Environmental alarm
4 : Equipment alarm
5 : Integrity violation
6 : Object creation
7 : Object deletion
8 : Operational violation
9 : Physical violation
10 : Processing error alarm
11 : Quality of service alarm
12 : Relationship change
Chapter 6
6-24
13 : Security service or mechanism violation
14 : State change
15 : Time domain violation
$severity
$severity : Severity (OSI values)
1 : Critical
2 : Major
3 : Minor
4 : Warning
5 : Indeterminate
6 : Clear
$probablecause
$probablecause : probable cause (OSI values)
0 : Unknown
1 : Adapter error
2 : Application Subsystem Failure
3 : Bandwidth Reduced
4 : Call Establishment Error
5 : Communications Protocol Error
6 : Communications Subsystem Failure
7 : Configuration or Customization Error
8 : Congestion
9 : Corrupt Data
10 : Cpu Cycles Limit Exceeded
11 : Data Set or Modem Error
12 : Degraded Signal
13 : DTE-DCE Interface Error
14 : Enclosure Door Open
15 : Equipment Malfunction
16 : Excessive Vibration
17 : File Error
18 : Fire Detected
19 : Flood Detected
20 : Framing Error
21 : Heating or Ventilation or Cooling System Problem
22 : Humidity Unacceptable
6-25
23 : Input Output Device Error
24 : Input Device Error
25 : LAN Error
26 : Leak Detected
27 : Local Node Transmission Error
28 : Loss of Frame
29 : Loss of Signal
30 : Material Supply Exhausted
31 : Multiplexer Problem
32 : Out of Memory
33 : Output Device Error
34 : Performance Degraded
35 : Power Problem
36 : Pressure Unacceptable
37 : Processor Problem
38 : Pump Failure
39 : Queue Size Exceeded
40 : Receive Failure
41 : Receiver Failure
42 : Remote Node Transmission Error
43 : Resource at or Nearing Capacity
44 : Response Time Excessive
45 : Retransmission Rate Excessive
46 : Software Error
47 : Software Program Abnormally Terminated
48 : Software Program Error
49 : Storage Capacity Problem
50 : Temperature Unacceptable
51 : Threshold Crossed
52 : Timing Problem
53 : Toxic Leak Detected
54 : Transmit Failure
55 : Transmitter Failure
56 : Underlying Resource Unavailable
57 : Version Mismatch
$managedobject
$managedobject : Concerned object (translated string)
$objecthierarchy
Chapter 6
6-26
$objecthierarchy : Concerned object (non translated string)
Many levels separated by \
Number of object : : instance
16 : OmniVista 4760
17 : Application
18 : Module
19 : Level
7 : network
8 : subnetwork
89 : A4400 / OXE
59 : A4200 / OXO
instance : 'string', #integer
$incidentnumber
$incidentnumber : Identifier of notification : For which come from OXE, it is a number ofemission order.
This field does not appear in the grid but only in the detail of the alarm.
$addinfo
$addinfo : Concatenation of many fields which give details on the nature of the problem.
For OXE alarm : 2 0 #<ID>
For internal alarm : 10 0 #<ID> 1 '<HOSTNAME>' 2 '<KEY>
For OXO alarm : 11 0 #<ID>
ID = Identifier of the diagnosis
$addtext
$addtext : Wording of diagnosis
6.5.7.2 Modifying an Existing Filter
You can:
- Rename the filter.
- Modify filtering keys.
- Modify, delete, or add E-mail addresses.
- Replace or delete a script.
6.5.7.2.1 Renaming a Filter
1. Select a name in list (2).
2. Click Modify.
3. Modify the name.
6-27
4. by either:• Click OK to confirm and close the window.• Click Apply to confirm without closing the window.
6.5.7.2.2 Modifying Filtering Keys
1. Select a filter in list (2).
2. Modify the filtering keys.See § Specifying Filtering Keys (Criteria) .
6.5.7.2.3 Modifying an Address
1. Select a filter in list (2).
2. Select the address in list (7).
3. Click Modify.
4. Modify the address.
5. by either:• Click OK to confirm and close the window.• Click Apply to confirm without closing the window.
6.5.7.2.4 Deleting an E-mail Address
1. Select a filter in list (2).
2. Select the address in list (7).
3. Click Remove.
4. by either:• Click OK to confirm and close the window.• Click Apply to confirm without closing the window.
6.5.7.2.5 Adding an E-mail Address
1. Select a filter in list (2).
2. Add an address.See § Adding an E-mail Address .
6.5.7.2.6 Replacing a Script
1. Select a filter in list (2).
2. Click the Script tab.
3. Replace the script.See § Specifying a Script .
6.5.7.2.7 Deleting a Script
1. Select a filter in list (2).
2. Click the Script tab.
3. Select the script.
Chapter 6
6-28
4. Delete it with the Del key.
5. by either:• Click OK to confirm and close the window.• Click Apply to confirm without closing the window.
6.5.7.2.8 Deleting a Filter
1. Select a filter in list (2).
2. Click Remove.
3. by either:• Click OK to confirm and close the window.• Click Apply to confirm without closing the window.
6.5.8 Filtering Alarms to Send SNMP Traps
You can filter traps sent by the PCX or the Alcatel-Lucent OmniVista 4760 NetworkManagement System.
1. Select Preferences > Alarms > SNMP Filter.
2. The SNMP Filter window is displayed.
3. Configure the filter:• Select the source (alize, omnipcx4400 or internalAlarms).• Select trap type (Correlation or Diagnostic).• Select the operator.• Select comparison value:
• True or False for Correlation traps.• A positive integer for Diagnostic traps. A list of integers may be specified,
separated by “;” and/or a range of integers, separated by “-” (e.g. 1;5;10-100;120).• Click OK to confirm and close the window.
6-29
Chapter 6
6-30
7.1 Overview
7.1.1 Overview
The Topology application is part of the Alcatel-Lucent OmniVista 4760 CommunicationManagement System (called Alcatel-Lucent OmniVista 4760 Network Management System inthis document).
The topology enables the user to display and monitor operation of:
- Networks and subnetworks
- PCXs
- Links between PCXs
- Sensitive applications
Warning: Only correlated alarms are displayed in Topology screens (alarms for which thesystem can detect the end). For example, you cannot display the unexpected restart of a PCX,however, you are informed of the disconnection of a board.For each correlated alarm, there is a corresponding clearing alarm to provide resolution advice(for example: board put back into service).
The Passive Communication Servers are not managed by the Topology application.
7.1.2 Description of the interface
See module Interface - Overview for ergonomics.
See module Alarms - Overview for information on alarm management.
The interface of the Topology application is composed of three windows:
1. The tree structure window
2. The main window
3. The zoom (navigation) window.
Note:
With the zoom out feature, you can view the entire main window on your display. When icons are too
small, they are replaced by grey squares.
7.1.2.1 The tree structure window
This window has Standard and Custom tabs.
7.1.2.1.1 Standard tab
This tab is used to navigate the tree structure of PCX networks defined in the Systemdirectory. Click an item to display information on the item in the main window.
Note:
In Standard view, customization of network topology is limited to adding background images.
7
7-1
If you select a PCX in the tree structure, the shortcut menu offers the following commands:
- Configuration: runs the Configuration application on the PCX in connected mode. If thePCX is an OmniPCX Office, the OMC interface is started (preinstallation is required).
- Internet Access: opens a browser and launches a remote connection to the OmniPCXOffice.
- Connection: opens a Telnet or SSH session and makes remote connection to theAlcatel-Lucent OmniPCX Enterprise CS or OmniPCX 4400.
If you select an Eye Box in the tree structure, the shortcut menu offers the following command:
- Configuration: opens a browser to connect the Alcatel-Lucent OmniVista 4760 NetworkManagement System client to the Eye Box web server, in order to perform the Eye Boxadministration tasks. Also starts the configuration application.For more information refer to module Configuration - Network tab § Administering the EyeBox.
7.1.2.1.2 Custom tab
This tab is used to customize the organization of PCX networks defined in the Systemdirectory. By default, a blank tree structure is displayed.
7.1.2.2 The main window
This window has Topology and Alarm tabs.
Like the tree structure, the topological views are dynamic and display the severity of alarmsassociated with network items and links. The topology is only affected by correlated alarms;i.e. only alarms with an incident start and end can result in changes in the topology views andin the tree structure.
7.1.2.2.1 Topology tab
When this tab is selected, the main window displays a graphical representation of thesub-items of the item selected in the tree structure.
If you select an item in the window, the shortcut menu offers (at minimum) the followingcommands:
- Open: displays the items located under the selected item.
- Alarms: displays the alarms associated with the selected item in the main window.
If you select a PCX, the shortcut menu offers the following additional commands:
- Configuration: runs the Configuration application on the PCX in connected mode. If thePCX is an OmniPCX Office, the OMC interface is started (preinstallation is required).
- Internet Access: opens a browser and launches a remote connection to the OmniPCXOffice.
- Connection: opens a Telnet or SSH window and makes remote connection to theOmniPCX 4400 or Alcatel-Lucent OmniPCX Enterprise CS.
In Standard view, the topology screen provides the following tools in the lower section:
table 7.1: Normal mode icons
Chapter 7
7-2
to switch to Edit mode. This tool is only enabled ( ) if you have
customization rights and if you have selected the Custom tab in thetree structure window.
to zoom-out on the topology display
to zoom-in on the topology display
to display the previous view
to display the next view
to add or replace a background image
to delete the background image
In Edit mode, the topology screen provides the following tools in the lower section:
table 7.2: Edit mode iconsto return to Run mode
to zoom-in on the topology display
to zoom-out on the topology display
to display the previous view
to display the next view
to add or replace a background image
to delete the background image
tool for selecting and moving graphic items
to create a custom view
to create a network item
7-3
to create a link between network items
to create a line of text
to create a polygonal colored background
to create a rectangular colored background
to modify a polygonal background
7.1.2.2.2 Alarms tab
When this tab is selected, the main window displays a list of alarms (if any) for the objectselected in the Topology tab. By default, only current correlated alarms (uncleared) aredisplayed.
The Alarms History button (light gray background) allows a complete history of alarms
to be displayed. The Current Alarms= button (dark gray background) allows only current
alarms to be displayed.
The Remove filter button (dark gray background) allows uncorrelated alarms to be also
displayed. The Set filter button (light gray background) allows only correlated alarms to
be displayed.
7.1.2.3 The zoom window (navigation box)
This area, located in the lower left part of the screen, offers an overall view of the topology. Ithas a moveable frame that you can move by dragging. The position of the frame marks theboundary of an area whose content is displayed in the main on the right of the window.The size of this window can be modified by moving its side edges.
7.1.3 The two display views
The topology can be displayed according to two display sview, accessible via the two tabs:
- Standard view
- Custom view (customizable network display).
7.1.3.1 Standard view
In this tab, all network items registered on the server are displayed. The tree is structuredaround the networks, subnetworks and PCXs.
The Topology tab presents the sub-items of the item currently selected in the tree structure.By clicking Alcatel-Lucent OmniVista 4760 Network Management System server in the rightwindow, for example, you can view important services and applications such as the Scheduler,the CMISE server, synchronization, etc. .
Chapter 7
7-4
7.1.3.2 Custom view
Custom view allows you to:
- Create your own graphical views with the network items and images of your choice.
- Reroute alarms to custom network items.
- Associate executable actions with custom network items.
To access custom view, click the related tab.
7.1.3.3 Save\Read option
To configure the topology views available at Topology application startup:
- 1. Open the Preferences Menu2. Select Topology3. Select Configuration, then a window opens.4. Select the value of the Read Save Configuration parameter from the drop-down list.
The available choices are:• Custom & standard configuration• Custom configuration• Standard configuration
5. Click OK to validate
Note:
To be effective this configuration requires a restart of the Topology application.
At application startup, views are generated from backup data if it exists. Otherwise Directory data is
used.
7.1.3.4 Refresh Saved Configuration
A Refresh operation compares the saved topology and the real topology. The real topology isobtained after synchronization. After a refresh operation, old items are removed and new itemsare placed in their default position.
Click the menu bar button to start a refresh operation.
Note:
In the custom topology, a refresh operation checks for consistency and not new items. If you want to see
new items (e.g. PCX), add them manually.
7.1.3.5 Display options
7.1.3.5.1 Display of VPN\OXE Links
In both display views (standard and custom), display of VPN\OXE links can be enabled ordisabled:
1. Open the Preferences menu.
2. Select Topology.
3. Click Configuration.
7-5
4. Select or deselect the Display VPN\OXE links box.
5. Click OK to confirm.
7.1.3.5.2 Alcatel-Lucent OmniVista 4760 Network Management System server display incustom view
To have a graphical view of the Alcatel-Lucent OmniVista 4760 Network Management Systemservices with a colored notification of alarms in the custom tree:
1. Open the Preferences menu
2. Select Topology\Configuration, a"Configuration window"opens
3. Select Display 4760server
4. Click OK to confirm
Note:
To be effective, these configurations requires a restart of the Topology application.
7.1.3.5.3 Display virtual ACT
In standard view, virtual shelves (hybrid ACTs, Alcatel-Lucent OmniPCX Enterprise CS ACT 0,INT-IP boards, etc.) are not displayed by default in the standard topology. If you want them tobe displayed:
- In the System directory, expand the NMC > Network_name > Subnetwork_name >PCX_name > Hardware tree structure, select the virtual shelf, then deselect the Virtualequipment box, or,
- In custom Topology view, create a network item and reroute the alarms specific to thevirtual shelf to it.
7.1.4 Network component symbols
7.1.4.1 Representation of an Alcatel-Lucent OmniPCX Enterprise CS type PCX
Representation of Alcatel-Lucent OmniPCX Enterprise CS architecture with ACT andEnterprise Media Gateways and Appliance Server.
Chapter 7
7-6
Figure 7.1: Alcatel-Lucent OmniPCX Enterprise CS type PCX
By double-clicking one of the Media Gateways, you can display its equipment:
Figure 7.2: Alcatel-Lucent OmniPCX Enterprise CS PCX equipment
7.1.4.2 Representation of an OmniPCX 4400 type PCX
A OmniPCX 4400 type PCX is represented by the icon. Double-click the icon to display
PCX equipment:
Figure 7.3: OmniPCX 4400 PCX equipment
By default, node shelves are shown in the form of racks positioned on top of each other andthat cannot be moved.
To display a peripheral shelf as a separate icon that can be freely positioned as shown below,configure the Remote locationattribute directly on the PCX.Using the Configuration application, select the node, then the shelf, and set the Remotelocation attribute to YES.
7-7
Figure 7.4: Link between remote PCXs
7.1.4.3 Representation of an OmniPCX Office type PCX
A OmniPCX Office type PCX is represented by the icon. Its equipments cannot be
displayed.
7.1.4.4 Representation of an Eye Box
An Eye Box is represented by the icon. Its equipments cannot be displayed.
7.1.5 Managing custom views
7.1.5.1 CreationTo create a custom view:
1. Select the Custom tab in the tree structure window.
2. In the main window, click to enable Edit mode.
3. Click , place the cursor at the desired location in the window, then left-click. A dialog
box is displayed.
4. Enter View Name, then select Network items by positioning them in the Select Objectsarea using the direction arrows.
5. Select the Show connected PCXs box to display the PCXs connected via a logical link toone of the PCXs displayed but not included in the selection of PCXs displayed.
6. Add a background image, if desired:• Click Browse. A window is displayed.• Select the desired image in the dedicated directory: \4760\data\Topology\maps. The
formats supported are ivl, jpg, and gif. The image may be a map, a diagram, etc.• Click Add.... The custom topological view is automatically updated according to your
selection.
7. Click OK to confirm.
Note:When you modify a custom view, the Perform Layout check box is displayed in the dialog box.Deselect this box so that existing networks items are not rearranged in the window. In this case, newnetwork items are displayed in the upper left corner of the window.
To create a network item:
Chapter 7
7-8
1. Select the Custom tab in the tree structure window.
2. In the main window, click to enable Edit mode.
3. Click , place the cursor at the desired location in the window, then left-click. A dialog
box is displayed.
4. Enter the Label for the item (30 characters maximum). This text will be displayed under theitem.
5. Select Plinth size:• No plinth: the item will be represented by its icon.• Large: item size will be 32 x 32 pixels.• Small: item size will be 16 x 16 pixels.
6. Add an icon:• Click Browse.... A window is displayed.• Select the desired icon in the dedicated directory: \4760\data\Topology\icons. The
formats supported are gif and jpg.• Click Select.
7. Enter a Short description of the item (40 characters maximum). This text will be displayedunder the label.
8. If required, enter a Long description of the item (250 characters maximum). In Standardview, this text will be displayed as a pop-up when the cursor is placed on the item.
9. Click OK to confirm.To create a link:
1. Select the Custom tab in the tree structure window.
2. In the main window, click to enable Edit mode.
3. Click , place the cursor on the first item and drag and drop it to the second item. A
dialog box is displayed.
4. Enter the Label for the link (30 characters maximum). This text will be displayed next tothe link.
5. Enter a Short description of the link (40 characters maximum). This text will be displayedunder the label.
6. If required, enter a Long description of the link (250 characters maximum). In Standardview, this text will be displayed as a pop-up when the cursor is placed on the link.
7. If required, modify Line width (default value, 5 pt).
8. If required, modify Line style (solid or dashed line).
9. If required, modify Link color.
10. Click OK to confirm.To create a label:
1. Select the Custom tab in the tree structure window.
2. In the main window, click to enable Edit mode.
7-9
3. Click , place the cursor on the first item and drag and drop it to the second item. A
dialog box is displayed.
4. Enter the Label (30 characters maximum).
5. If required, enter a Long description of the link (250 characters maximum). In Standardview, this text will be displayed as a pop-up when the cursor is placed on the link.
6. If required, modify Font size (default value, 12 pt).
7. If required, modify Text color.
8. Click OK to confirm.To create a colored background :
1. Select the Custom tab in the tree structure window.
2. In the main window, click to enable Edit mode.
3. Click or , then create the background using the mouse. For a polygonal
background, double-click the last point to end creation. A dialog box is displayed.
4. If required, modify Background color.
5. If required, deselect the Translucent box to have an opaque background.
6. Click OK to confirm.
7.1.5.2 ModificationTo reroute alarms to a custom object:
1. Open the Alarms or Configuration application:• In Alarms, select alarm source in the tree structure (node, coupler board, etc.).• In Configuration, connect to the PCX and select the alarm source in the tree
structure.• Copy the source by pressing Ctrl + C.
2. In the Topology application, select the Custom tab in the tree structure window.
3. In the main window, click to enable Edit mode.
4. Select the object (view, network item, or link), then click Alarms re-targetting... in theshortcut menu. A dialog box is displayed.
5. Add the source of alarms to be rerouted to the object:• Click Add....• Place the cursor in the Source Object hierarchy field.• Paste the source by pressing Ctrl + V.• Click OK to confirm.
6. If required, configure a filter for rerouted alarms:• Select the desired alarm in the list.• Select the Use filter box.• Select filter criteria.
7. If required, add the source of alarms that are not to be rerouted to the object:
Chapter 7
7-10
• Repeat operations 1 to 5.• In the list, select the line and check (select) the Excluded Hierarchy box.
Note:This allows you, for example, to reroute alarms from a PCX except for alarms from its links with othernodes that you want to reroute to a custom "links" object.
8. Click OK to confirm.To configure the actions that can be executed by a custom object:
1. Select the Custom tab in the tree structure window.
2. In the main window, click to enable Edit mode.
3. Select the object (view, network item, or link), then click Configure user actions... in theshortcut menu. A dialog box is displayed.
4. Add the commands that will be accessible via the item's shortcut menu:• Click Add.... A dialog box is displayed.• Enter the Name of the action.• Select the Command Line for the action. The formats supported are exe, bat, and
cmd. This command must be executable on the Alcatel-Lucent OmniVista 4760Network Management System Client PC.
• Select the Working directory.• Click OK to confirm.
5. If required, specify the action to be performed when the item is double-clicked:• Select the desired action from the list.• Click Default action.• In the list, the Default action box of the action is selected.
6. If required, modify the order of actions in the item's shortcut menu:• Select an action.• Click Move up or Move down.
To modify a custom object:
1. In Edit mode, select the view in the tree structure.
2. In the main window, select the object, then in the shortcut menu click ModifyTo modify a custom view:
1. In Edit mode, select the view in the main window.
2. In the shortcut menu, click Modify
Remark:
• If the option “Perform Layout” is enabled, all PCXs are rearranged.
Remember to disable (deselect) this option if you want to keep your manual arrangement.
• You need to reselect “ Show connected PCXs " if you want to view links to PCXs that are notdisplayed.
To delete a custom object:
1. In Edit mode, select the object in the main window.
2. Click Delete in the shortcut menu.To move graphic items in a topological view:
7-11
1. In Edit mode, click the selector.
2. Drag and drop to reorganize the graphical layout of items.To save changes to your custom topology:
1. Click in the dynamic menu bar.
2. Confirm the save. Your layout will be recovered each time you open the application.To delete your custom topology:
1. Click to switch to Standard view.
2. Click in the dynamic menu bar and confirm deletion.
3. Exit and then reopen the Topology application. The standard topology is restored.To check the coherency of the saved configuration
- Click the button in the dynamic menu bar and confirm the check.
7.1.6 Graphic coding of alarms
In the tree structure:The presence of an alarm on a network item is indicated by a colored dot to the left of the iconsymbolizing the alarm.When an alarm is received, the color and information about the concerned network item areupdated, if required. The severity levels of the alarms follow the same coding as that used inthe Alarms application (see table below).
In the topological view:Alarms are symbolized by counters and information bubbles. As for the tree structure, the colorused depends on the maximum severity of the alarm assigned to the item and its associatedsub-items. See module Alarms - Setting reception parameters § Configure the SystemDirectory to Receive Alarms and Events and Transmit SNMP Traps. .Coding adheres to the following rules:
Frame color: Indicates the highest level of severity of all the alarms (acknowledged or not).
Chapter 7
7-12
Fill color of the box: Indicates the highest level of severity of uncleared alarms.Fill color of the bubble: Indicates the highest level of severity of unacknowledged alarms.Counter X: Number of uncleared alarms.Counter Y: Number of unacknowledged alarms.
table 7.3: X and Y counter lettersLetter Severity level Color code
I Indeterminate Pink
C Critical Red
M Major Orange
m minor Yellow
w warning information Blue
table 7.4: Display and meaning, examples
Alarms Symbol Frame Backgroundcolor
No alarm (all cleared) Gray Gray
2 major alarms received Orange Orange
2 acknowledged major alarms Orange Gray
2 acknowledged major alarms+ 1 unacknowledged minor
alarmOrange Yellow
2 acknowledged major alarms+ 1 unacknowledged warning Orange Blue
7-13
Chapter 7
7-14
8.1 Overview
8.1.1 Overview
Scheduler is an application of Alcatel-Lucent OmniVista 4760 Communication ManagementSystem (called Alcatel-Lucent OmniVista 4760 Network Management System in thisdocument).
8.1.1.1 Terminology
Scheduler: This application manages the automatic execution of tasks. A task can be:
- Executed in immediate or deferred mode.
- Unique or repeated.
- Independent or synchronized with another task.
Job: Entity including one or more tasks performed simultaneously.
Task: Executable operation or running an Alcatel-Lucent OmniVista 4760 NetworkManagement System internal or external service.
For more information, refer to § Execution process .
8.1.1.2 Access to the application
Direct access: You can run the Scheduler by clicking in the Applications toolbar.
Indirect access: When a programmable operation is run, the Scheduler is automaticallydisplayed. You can configure a start time and a possible repetition frequency (time interval) forthe task.
Example:
PCX synchronization is available from the System directory.
8.1.1.3 The scheduler menu
The Scheduler has a specific menu: Preferences > Scheduler > Configuration – §Customizing the scheduler .
8.1.2 Description of the interface
The interface is divided into two sections:
- A tree structure presenting a list of tasks and jobs is displayed on the left.
- A detailed information window with the job and task scheduling and status tabs isdisplayed on the right side.
8
8-1
Figure 8.1: Scheduler window
8.1.2.1 Tree structure window
The items shown in the tree structure are the following:
(orange) job disabled (not scheduled, i.e. has to be run manually).
(red) job active (job waiting to be run).
(green) job running.
task scheduled a,d waiting to run.
task idle (has to be run manually).
task running,
(green frame) execution report – successful status.
Chapter 8
8-2
(red frame) execution report – failed status.
8.1.2.2 Display preferences
By default, the scheduler lists all jobs without applying any filter. You can view other users'jobs and their scheduling. You cannot modify these jobs. A display filter is available to ensurethat you only display your own jobs: select the option Preferences > Scheduler > User >Show only my jobs.
8.1.2.3 Detailed information window
Jobs and tasks have dedicated tabs:
- Job. Scheduling (see § Scheduling ).
- Subjob options (Options for depending jobs, see § Subjob Options ).
- Task Retry Options (see § Retry options ).
- Task Definition (see § Task definition ).
- Status (see § Status ).
8.1.3 Predefined and current jobs
Any Alcatel-Lucent OmniVista 4760 Network Management System application may use thescheduler to schedule or perform jobs in deferred mode.Possible tasks are listed below. Tasks performed at regular intervals are preprogrammed andtheir respective frequencies are specified in brackets :
1. Directory• Full LDAP/PCX synchronization.• Partial LDAP/PCX synchronization [daily, weekly]• Import/Export LDAP.• Password Policy [weekly]
2. Accounting/Traffic analysis• Archive accounting records [weekly]• Purge carrier configuration [weekly]• Calculate total counters [daily, weekly]• Purge old accounting data [weekly]• Purge old traffic analysis counters [daily, weekly]• Recalculate costs.• Load IP records [daily, weekly]• Load accounting records [daily, weekly]• Detect exceeding thresholds [daily, weekly]
3. Alarms• Purge alarms [daily, weekly]• Purge alarm reports [daily, weekly]
4. Maintenance• Restart server [weekly]
8-3
• Save OmniPCX 4400 and Alcatel-Lucent OmniPCX Enterprise CS databases.• Defragment Alcatel-Lucent OmniVista 4760 Network Management System databases• Save Alcatel-Lucent OmniVista 4760 Network Management System database• Alcatel-Lucent OmniPCX Enterprise CS/ OmniPCX 4400 software update
5. Configuration• Import PCX.• Export PCX.• Save OmniPCX Office databases.• Restore OmniPCX Office databases• Download OmniPCX Office releases
6. Reports• Generate reports.
7. Security: search of expired password [weekly]
8. Audit: upload, store and purge of Audit data [daily]
Tasks linked with an application not included in the license are listed but not performed.Although execution status is always displayed as successful, the log file confirms that thetask is inactive.
Note:
Report templates associated with scheduling are not protected and can be modified. If this is the case,
the task may fail or give inconsistent results.
To purge alarms, parameters are available in the System directory: NMC > Server NameAlcatel-Lucent OmniVista 4760 Network Management System > Servers > Server_name >Alarm server.
To purge Accounting and Traffic analysis data, parameters are available in the Systemdirectory: NMC > Server_nameAlcatel-Lucent OmniVista 4760 Network Management System> Servers > Server_name > NMCDatabase.
To purge Audit data, parameters are available in the System directory: NMC > Server NameAlcatel-Lucent OmniVista 4760 Network Management System > Servers > Server_name >Audit server.
8.1.4 Jobs to schedule after installing the Server
After installing the software programs, you must schedule two Maintenance jobs:
1. Set parameters for the Maintenance application according to your PC. See moduleMaintenance - Maintenance § Configuring Settings.
2. Schedule the execution of the two following tasks: Defragmentation of databases andBackup (save) of databases via the Maintenance application.
8.1.5 Execution process
Chapter 8
8-4
Figure 8.2: Scheduling execution process
On the date programmed for job execution, T1, the Scheduler simultaneously runs tasks Aand B.When tasks A and B are complete, the Scheduler deals with task T2 and simultaneouslyruns tasks C and D.Options:Automatic repeats: You can define a number n of automatic repeats so as to be able torelaunch a task that failed. A timer can be used to set the time before each attempt. If failure isconfirmed, an internal alarm is displayed in the Alarms application.Stop On Error: A condition for execution can be configured so that a job will only beperformed if all tasks in the previous job are run successfully. If this option is selected on jobT1, tasks C and D of job T2 must wait until tasks A and B have been correctly processed to berun.Delta between T1 and T2: This is a time-out before launching dependent jobs.
In practice, the name of a job created under another job (T2) is specified automatically andcannot be modified.
8.1.6 Execution reports
8.1.6.1 Description of the reports
A copy of the structure of each job is placed at the same level of the tree structure. This copyis intended to collect job and task execution reports. When a job is complete (successful ornot), a report is created and classified in chronological order. The role of the report is to recordthe essential steps of job execution and specify the location of the corresponding log file.
A report contains the following data:
- Status (this can be successful or failed).
- The effective duration including any repetitions and delays.
- Effective start date.
- Effective end date.
- The log file, giving the location of the execution report file on the server.
8.1.6.2 Viewing reports
To view a report:
1. Click the Status tab.
8-5
Figure 8.3: Scheduler window — viewing reports
8.1.6.3 Managing reports
Reports are created automatically. Old reports are regularly deleted by maintenance. Only jobreports are manually deleted. This results in any reports on associated tasks being deleted.To delete reports:
1. Click the desired report(s) to select it (them). Select multiple reports using the Ctrl or Shiftkeys.
2. Select the Delete command from the shortcut menu. The selected report(s) is (are)removed from the list after confirmation.
To print a report:
1. Click the report to select it.
2. Select the Print command from the shortcut menu in the editing area. The report is sent tothe default printer.
8.1.7 Managing scheduled operations
8.1.7.1 Available commands
Chapter 8
8-6
Jobs and tasks are managed via shortcut menus:
1. For a job:• New Job: Adds a new blank inactive job to the tree.• New task: Adds a task to the job.• Execute Now: Executes a pending job immediately.• Abort: Stops a job in the course of execution.• Enable: Activates a selected inactive job.• Disable: Deactivates a pending job.• Delete: Deletes a job or task.• Paste: Pastes a copy of a previously copied task into the tree structure.
2. For a task:• Cut: Deletes a task for a subsequent move to another job.• Copy: Copies a task for a subsequent copy to another job.• Delete: Deletes a task.• Refresh: Updates the display.
8.1.7.2 Common operations
To execute a programmed task immediately without it being necessary to reschedule it:
1. Select the desired job in the tree structure.
2. Open the shortcut menu by right-clicking,
3. Select Execute Now. The first tasks are run .
When execution is complete, a report is created, then placed in the dedicated structure.
To create a job, you can either create it directly via the Scheduler (see § Available commands) or indirectly via one of the other Alcatel-Lucent OmniVista 4760 Network ManagementSystem applications. In the latter case, two choices for creation are offered via the dialog box:
- Simple job:1. Check this option if you want to create a job that is neither dependent on nor included
in another job. This is equivalent to creating a job with a single task.The programming, definition, retry, and status tabs are displayed in a dialog box.
2. Update the different tabs and apply your entries.
- Synchronized task1. Check this option if you want to include your task in a job (present or not present in the
Scheduler). A dialog box with three tabs is displayed.2. You can view programming of the various Scheduler tasks and jobs by using the
shortcut menus.3. If you want to include your new task in one of the jobs in the Scheduler, click it in the
tree structure, then click Apply. The task is added.4. If you want to include your new task in a job that has not yet been created:
• Select the parent job from which you want to create your job.• Run the New Job command. A Properties window is displayed.• Complete the window and confirm. The new job is displayed in the tree structure.
8-7
• Select the new job and complete the three tabs, then confirm.To deactivate a job:
1. Select the desired job in the tree structure.
2. Right-click to open the shortcut menu.
3. Select Disable, the task switches to idle .
To activate a job:
1. Select the desired job in the tree structure.
2. Right-click to open the shortcut menu.
3. Select Enable:• Start date is exceeded and the job is not to be repeated: the associated tasks switch to
idle .
• Start date is compatible with current server time and with start delay: the firstassociated tasks switch to Running status .
• Start date is later than current server time (the maximum start delay is included): theassociated tasks switch to Waiting status .
To abort a running job:
1. Select the desired running job .
2. Right-click to open the shortcut menu.
3. Select Abort, the job switches to idle status as do associated tasks .
8.1.8 Scheduling parameters
A job can be reprogrammed at any time, provided that it is not running. Jobs and tasks havededicated tabs:
- Job. Scheduling,
- Task Definition.
- Subjob options (Options for depending jobs).
- Task Retry Options.
- Status.
8.1.8.1 Scheduling
An execution interval can only be configured for a job via the Scheduling tab, that contains
Chapter 8
8-8
the following information:
1. A Description of the task shown in the Scheduler tree structure.
2. Maximum Start Delay. This is the maximum delay allowed to run a task that was notperformed on the scheduled date.Example: the defragmentation scheduled for Saturday with a maximum delay of one daywill not be performed if the PC is shut down on Friday and restarted on Monday.
3. The Start Date can be either Now or As Scheduled for a deferred launch.Specify a date on the calendar (accessed via ).
4. The Repeat interval is configured by various criteria, as desired.Example 1:Repetition: WeeklyEvery: 3 Week(s)The job is launched every 3 weeks, on the same day of the week as that of the firstexecution.Example 2:Repetition: MonthlyEvery: 1 Month(s)Date :Day: First SundayThe job is launched on the first Sunday of every month.Example 3:Repetition: MonthlyEvery: 1 Month(s)Date :Day: Last dayThe job is launched on the last day of every month. Leap years are included to ensurepermanent execution.
5. An Ending Date if the job repetition interval is to be limited over time. Check the AsScheduled option, then use the calendar to specify the desired date and time.
When the date limit is reached, the job automatically switches to idle state.
6. Exclude Days is to be completed if you do not want the task to be run on one or morespecified days of the week.
Check consistency between excluded days and repeated interval settings. If a start datecoincides with an excluded day, it is automatically put back to the first authorized day.
8.1.8.2 Task definition
This tab is dedicated to advanced settings for experienced users.
- Description: This field displays the name of the tasks listed in the tree structure. It must becompleted.
- Host Name: the name of the Alcatel-Lucent OmniVista 4760 Network ManagementSystem server.
- Service type:
8-9
• Service: Default value - select this option if the task is performed by an NMC service tobe specified in the list located under the option. The Action field contains thecommand corresponding to the service.
• NMC Process: Select this option if the task is performed by an NMC process. Thenenter the name of the process. You can also specify execution options in theArguments field.
• External Process: Select this option if the job is performed by an NMC externalprocess. Then, update the Executable and Arguments fields.
To simplify use, scripts that open an MS-DOS window are not supported. However, pop-upmessages can be sent with the net send command.
Note:With some external processes like net send, to avoid display problems in case of accentuated char-acters in executives reports add "-oem_output" in the Executable field before the executable name.
- Job Owner: Indicates task owner name. This parameter cannot be modified.
8.1.8.3 Retry options
- Number of retries: Specify the number of attempts for a job to be relaunchedautomatically after execution fails.
- Time Between Retries:* Specify time between two attempts in number of days, hours,minutes and seconds.
- Maximum execution time*: Enter an execution time limit so that you can control total jobexecution time.
(*) These two parameters cannot be less than Scheduler configuration preferences (see §Customizing the scheduler ).
8.1.8.4 Subjob Options
Delay dependent job start: Time for end of execution of current job before processing thenext job. The specified time does not include the seconds.
Stop On Error: Enable this option if you want a task to be aborted when one of its sub-tasks isexecuted incorrectly. By default, this option is enabled.
8.1.8.5 Status
This tab presents status during job execution or the task currently selected in the treestructure. It also presents the name of the licensed application that the currently selected job inthe tree structure depends on.
8.1.9 Copy a task in order to customize it
By combining Copy/Paste operations, you can customize a predefined task separately.Example of customization with alarm purge:
1. Create a job at the root of the tree structure and name it New purge. Confirm creation
2. In the predefined Daily job, cut the Purge alarms job, and paste it in New purge.
3. Schedule the New purge job according to your needs and confirm.
8.1.10 Customizing the scheduler
Chapter 8
8-10
Reserved to experienced administrators.
This interface is exclusively reserved to members of the Administrators group of the Schedulerapplication ( module Security - Overview ).
To configure the Scheduler, some settings must be configured via the interface (accessedfrom the menu Preferences > Scheduler > Configuration).
Scheduler Preferences:Scheduling Start Delay (sec.) : The NMC scheduler service is among the first services to belaunched when the computer is started up. However, some NMC services that are liable to runjobs defined in the Scheduler require more time to start. Thus, it is necessary to postponescanning for jobs to be run, in order to leave more time for these services to start.Execution report storage duration (duration to be kept): Parameter to be defined in termsof days and hours. This avoids saturating the hard drive with an increasing number of reports.
Task preferences:Minimum repeat interval: To be defined in terms of days, hours, minutes, and seconds. Thisparameter sets a limit for the Time Between Retries field in the task retry options. Tasks witha time interval less than this parameter cannot be scheduled.Minimum "maximum duration": Parameter to be defined in terms of days, hours, andminutes. No task can be scheduled with a Maximum execution time lower than this value.Max No. of retries: Limits the maximum number of retries that can be scheduled for a task.Tasks with a number of retry attempts higher than this parameter cannot be scheduled.
All these settings can be displayed (read-only) by clicking at the top of the tree structure.
8-11
Chapter 8
8-12
9.1 Maintenance
9.1.1 Overview
9.1.1.1 Presentation of the Maintenance Application
The Maintenance application is part of the Alcatel-Lucent OmniVista 4760 NetworkManagement System (called Alcatel-Lucent OmniVista 4760 Network Management System inthis document). This application provides the following functions:
- Backup (immediate or scheduled) and restore of:• Alcatel-Lucent OmniVista 4760 Network Management System server databases.• PCX data.
Note 1:As of R5.0, the backup files archived on the Alcatel-Lucent OmniVista 4760 Network ManagementSystem can be deleted (see: § Purging Operations ).
- Defragmentation (immediate or scheduled) of Alcatel-Lucent OmniVista 4760 NetworkManagement System server databases
- Rebooting (immediate or scheduled) of the NMC service
- Scheduled software updates for one or more OmniPCX 4400/Alcatel-Lucent OmniPCXEnterprise Communication Server
- Viewing the status of scheduled software updates
Note 2:
The PCXs concerned are the OmniPCX 4400 and Alcatel-Lucent OmniPCX Enterprise Communication
Server.
For the OmniPCX Office, see module Configuration - Saving/Restoring and Downloading with OmniPCX
Office .
9
9-1
Figure 9.1: Maintenance Window for a PCX
Figure 9.2: Maintenance Window for a PCS
The window on the left shows the Maintenance application tree structure, which is divided intotwo sections.
- The PCX network, made up of networks, sub-networks and PCX systems
- The Alcatel-Lucent OmniVista 4760 Network Management System server name
The window on the right lists operations available for the item currently selected in the treestructure. In order to access the server maintenance commands, select the corresponding iconin the tree structure to display maintenance operations on the right side of the screen.
The table below lists maintenance operations for each type of item in the selected treestructure:
Note 3:
All PCX operations apply to OmniPCX 4400 and Alcatel-Lucent OmniPCX Enterprise Communication
Server.
table 9.1: Maintenance OperationsItem Possible operations
Root - Backup of all PCX systems- Software update- Software update status
Network - Backup of all PCX systems in the network- Software update- Software update status
Subnetwork - Backup of all PCX systems in the subnetwork- Software update- Software update status
Main andstand-by ComServers
- PCX - backup- PCX - Restore- Software Update- Software Update Status
Chapter 9
9-2
Item Possible operations
Server - Databases - Scheduled backup- Databases - Immediate backup- Restore databases- Databases - Scheduled defragmentation- Databases - Immediate defragmentation- NMC scheduled reboot- NMC immediate reboot
PassiveCommunicationServer (PCS)
- Software Update- Software Update Status
9.1.1.2 Maintenance Preferences Menu
When the Maintenance application is launched, the Preferences menu bar offers asub-menu: Maintenance > Configuration. This provides access to a maintenanceconfiguration interface. See § Configuring Settings .
9.1.1.3 Access to Network Drives
When a backup or software update is initiated, a default directory is offered. This defaultdirectory is specified in preferences (see § Configuring Settings ). According to yourrequirements, you may choose a different location that is detected by the Server. Check youraccess rights for the network drives you want to use to make sure the operation does not fail.
9.1.2 Alcatel-Lucent OmniVista 4760 Network Management SystemMaintenance
Backup operations concern:
- The Sybase database: accounting records, traffic analysis counters, VoIP traffic analysisrecords, alarm records, audit records and all reports and definitions
- The SunOne directory database: Alcatel-Lucent OmniVista 4760 Network ManagementSystem system configuration and directories database
- the customized dictionaries
- The scheduler files
- The loader files
When performing a Backup/Restore operation, all services are unavailable (except those beingused by the Backup/Restore function). The other applications are inaccessible. Whenperforming a backup or Restore operation, the application generates a .log file in the
directory of the Alcatel-Lucent OmniVista 4760 Network Management Systemserver (%inst is the installation directory).
9.1.2.1 Immediate Backup Operation
1. In the Maintenance tree structure, select the Alcatel-Lucent OmniVista 4760 NetworkManagement System server icon. The Operations window is displayed.
2. In the operations window, double-click Databases - Immediate backup. The Backupdialog box appears.
9-3
Note:The default root location for the backup is managed in the Maintenance Preferences menu (see §Configuring Settings ). The default is .
3. If you want to change the path:• Deselect the box Save in the default directory.• Click Search.• Select the directory or drive to which you want to save data.• Select the directory to which the data is to be saved.
4. Confirm your selection.A new subfolder is created in the chosen directory, named with the date of the backup.
9.1.2.2 Scheduled Backup Operation
For more information, see module Scheduler - Overview .
9.1.2.3 Restore Operation
1. In the Maintenance tree structure, select the Alcatel-Lucent OmniVista 4760 NetworkManagement System server icon. The Operations window is displayed.
2. In the Operations window, double-click Restore databases. The Restore dialog box isdisplayed.
3. Select the directory where the files to restore are found.
4. Confirm your selection.
9.1.2.4 Defragmenting Databases
Defragmentation consists in optimizing the availability of data on the drive and can beperformed in immediate or scheduled mode. This operation enhances performance ofsearching, reading, and writing operations on the server. The operation takes approximately2.5 hours on a standard PC for a database containing 5,000 users. The execution frequency ofthis maintenance operation must be scheduled according to the intensity of server use.
Before defragmentation:
- It is advisable to close all Alcatel-Lucent OmniVista 4760 Network Management Systemapplications on the server and client stations.
During the defragmentation phase:
- The server is unavailable.
- The status window lists progress data and informs you of the result of the operation.
9.1.2.5 NMC Reboot
To guarantee Alcatel-Lucent OmniVista 4760 Network Management System serverperformance, a task runs a weekly reset. This task is shown in the Scheduler and can berescheduled or canceled according to your requirements.To restart the NMC immediately, select NMC immediate reboot.To modify the automatic restart:
1. Select NMC scheduled reboot, then confirm. A dialog box is displayed.
2. The main scheduling features of the job appear: start date, frequency, etc.
Chapter 9
9-4
3. Several configuration options are available:
- To reschedule the job, select Schedule... . The scheduler is displayed.
- To temporarily deactivate the job, select Disable. Scheduling characteristics are storedand the Enabled attribute displays NO.
- To reactivate the previously deactivated restart job, select Activate. The Enable attributechanges to YES.
- To cancel the restart (reboot) job, select Cancel. The job is removed from the scheduler.
9.1.3 OmniPCX 4400/Alcatel-Lucent OmniPCX Enterprise CommunicationServer Maintenance
Caution:
If you are operating on a client console, you must ensure that the backup/restore directories or
drives are located on the server or on drives which can be accessed by the server. Access rights
for network drives must allow this operation.
9.1.3.1 Backup Operations
9.1.3.1.1 Overview
The Maintenance application allows you to perform either the backup of a single PCX or thebackup of all PCXs on a subnetwork, network, or on nmc or root level.
The backup can be immediate or scheduled. Scheduled backups allow to perform repetitivearchiving operations at a specific frequency.
Launching a PCX(s) data backup from the Alcatel-Lucent OmniVista 4760 NetworkManagement System automatically triggers:
- A local backup of selected files on the PCX(s) hard disk. Backup files are saved in thedirectory: regardless of the type backup (immediate orscheduled). For scheduled backups, the mao-dat and cho-dat files saved in the directory:
are no longer used.
- The backup files transfer from the PCX(s) to the Alcatel-Lucent OmniVista 4760 NetworkManagement System. Backup files are saved in the directory defined in the Configurationwindow accessible from the Maintenance > Preferences menus (see § ConfiguringSettings ).By default, backup files are saved in the directory: . Asub-folder is created for each backup named where is thenetwork number, is the subnetwork number, and is the PCX node.
Note:For every backup, a file is transferred from the PCX ( directory) to the backupdirectory of the Alcatel-Lucent OmniVista 4760 Network Management System. It provides informationon backup operations.
9.1.3.1.2 Preliminary Operations
The following operations are mandatory to do PCX backup operations.
Configuring the Swinst Password
9-5
1. Open the Directory application and click the System tab.
2. Expand the tree structure and select the target PCX.
3. In the right hand-side of the window, click the Connectivity tab and enter the swinstpassword in the corresponding field.
4. Repeat this operation for each PCX concerned by the backup operations
Activating the Automatic Database Save
1. Open the Directory application and click the System tab.
2. Expand the tree structure and select the target PCX.
3. In the right hand-side of the window, click the Data Collection tab and check theAutomatic Database Save box.
4. Repeat this operation for each PCX concerned by the backup operations
Configuring the Maintenance Account and Password
1. Open the Directory application and click the System tab
2. Expand the tree structure and select the target PCX
3. In the right hand-side of the window, click the Software Download tab and enter theMaintenance account and password in the corresponding field (MTCL account andpassword)
4. Repeat this operation for each PCX concerned by the backup operations
Note:
Maintenance account is must for taking backup of Alcatel-Lucent OmniPCX Enterprise CS.
9.1.3.1.3 Backup of a single PCX
1. Expand the Maintenance tree structure and select the target PCX.
2. In the Operations frame, double click the PCX - backup option. The right hand-side of thewindow displays backup parameters.
Chapter 9
9-6
Figure 9.3: Backup Parameters Window
3. Select the type(s) of files to download (specific files according to the PCX release) byselecting the corresponding options: MAO, Accounting data, Voice guides, Traffic analysisdata, Voice mail data, etc.
4. Select the location where the files are to be archived. You can place the files in the defaultdirectory by clicking the Save in the default directory option. If this option is not selected,specify the save location via the Search option.
5. Click the icon to confirm.
The task type selection window is displayed.
6. Select the type of job: Simple (default option) or Synchronized task. For more details,see: module Scheduler - Overview .
7. Click Continue.The scheduler window is displayed.
9-7
Figure 9.4: Scheduler Window
8. In the Start Date frame, select the type of backup: Immediate (Now field) or scheduled (Asscheduled field).
9. If the As scheduled field is validated, configure the start time and date, backup frequency,and end date. For more details, see: module Scheduler - Overview § Scheduling .
10. Click Ok to launch backup and close the scheduler window.A summary of the schedule is displayed when a scheduled backup is programmed.
9.1.3.1.4 Backup of multiple PCXs
1. Expand the Maintenance tree structure and select the target level (subnetwork, network,or root as desired).
2. In the Operations frame, double click the backup of all PCX systems option. The righthand-side of the window displays PCXs backup parameters (see: figure: BackupParameters Window )
3. Follow steps 3. to 10. detailed: § Backup of a single PCX and click Ok when finished(operations are identical).
9.1.3.2 Restore Operation
Chapter 9
9-8
Launching PCX data restore operation from the Alcatel-Lucent OmniVista 4760 NetworkManagement System automatically triggers:
- The backup files transfer from the Alcatel-Lucent OmniVista 4760 Network ManagementSystem to the PCX hard disk. The backup files are saved in the directory:
.
- A restore operation of the backup files on the PCX hard disk.
To launch a PCX data restore operation, carry out the following operations:
1. Expand the Maintenance tree structure and select the target PCX.
2. In the Operations frame, double click the PCX - restore option. The right hand-side of thewindow displays restore parameters.
Figure 9.5: Restore Parameters Window
3. Select the file type(s) to restore by selecting the corresponding options: MAO, Accountingdata, Voice guides, Traffic analysis data, Voice mail data, etc.
4. Select the location where the files are archived using the Search option. Be sure to knowthe network, subnetwork, and node number of the PCX in order to select the relevantdirectory.
5. Click the icon to confirm.
A progress bar is displayed in front of the files selected. If one or several file(s) selectedare not present in the corresponding backup directory, they are displayed on a redbackground:
9-9
9.1.4 Purging Operations
As of R5.0, the purging operations allow to delete the backup files archived in theAlcatel-Lucent OmniVista 4760 Network Management System. These can be backup files fromthe Alcatel-Lucent OmniVista 4760 Network Management System or Alcatel-Lucent OmniPCXEnterprise CS.
This operation is carried out from the Directory application:
1. Open the Directory application
2. In the window on the left, select the System tab and expand the tree structure as follows:where the
is your Alcatel-Lucent OmniVista 4760 Network Management System.
3. Select either:• The directory to define deletion parameters for Alcatel-Lucent
OmniPCX Enterprise CS backup files• The directory to define deletion parameters for Alcatel-Lucent
OmniVista 4760 Network Management System backup files
4. In the right hand-side of the window, select the Directory tab.
Chapter 9
9-10
Figure 9.7: Directory Tab Example
5. Enter information in:• The Path field: to specify the access path to the backup files to delete• The Clean-up Delay field: to enter the life time of backup files before deletion
6. Click the icon to apply modifications.
9.1.5 Software Update
9.1.5.1 Overview
9.1.5.1.1 What is Software Update?
The Software Update feature allows the network manager to update Alcatel-Lucent OmniPCXEnterprise CS software (versions and patches) from an Alcatel-Lucent OmniVista 4760Network Management System.
The software update feature can update the main CPU, backup CPU and PCS (PassiveCommunication Server).
The Software Update feature performs remote updates. An installer, with a PC Installer,performs the same work but locally. With Alcatel-Lucent OmniVista 4760 NetworkManagement System, roaming between sites is avoided.
9.1.5.1.2 Software Update Process
9-11
Some CPU are declared master and get the software directly from the Alcatel-LucentOmniVista 4760 Network Management System application. Some CPU are declared clientand get the software from master CPUs. A PCS can also be declared as a Master and canhave its client PCS.
When a master CPU (or PCS) is selected for a software download, all CPUs (or PCSs) whichrefers this master CPU (or PCS) are also selected for a software download.
1. Initiating: the network manager configuresand initiates the software update process
2. Downloading, Alcatel-Lucent OmniVista 4760Network Management System sends to themaster CPUs (or PCS) via FTP:• New version (or patch)• Client downloading details• Switching instructions
3. Delivering, master CPUs sends to the clientCPUs:• New version (or patch)• Switching instructions
4. Switching: CPUs (master and client) rebooton the inactive partition which becomes theactive partition.
The CPU version and the new version (or patch) must be compatible.
A PCS (Passive Communication Server) must be updated before its CPU. If not, in case ofdatabase transfer before the PCS update, the received data base must be in version n and thePCS in version n-1. In this case, the database is not usable.
If the PCS is updated before its CPU, a database in version n received on a PCS in versionn+1 is translated and can be used.
9.1.5.2 Configuration
9.1.5.2.1 Connectivity for Software Update
The connectivity for software update is defined in the Connectivity tab of PCX/PCS Directorywindow.
Chapter 9
9-12
Figure 9.8: Connectivity Tab Example
Connection type: indicates the connectivity between Alcatel-Lucent OmniVista 4760 NetworkManagement System and CPU/PCS.
For PCS:
- If the PCS is directly reachable via Ethernet, select: LAN
- If the PCS is only reachable via its Com Server, select None. This case happens when thePCS is connected in a different network.
9.1.5.2.2 Enable Remote Download Option
The Remote Software Download option (also called Software Download global flag) allows toenable (or to disable) the remote software download feature.
This option can be set in two ways:
- From the Maintenance application:1. In the Maintenance application, select Preference in the top menu bar.2. In the pull down menu select Maintenance and Configuration.3. Select the Software Update tab4. Click the check box Remote Software Download to enable the software download
feature.
9-13
Figure 9.9: Maintenance Preference Window
- From the Directory application:1. In the System tab, open the server name branch2. Open the Servers branch3. Open the server name branch4. Open the SaveRestore branch5. Click the OxeSoftwareDownload option to display the software download server
configuration
Chapter 9
9-14
Figure 9.10: OmniPCX Software Download Server Configuration
6. Validate the Remote Software Download checkbox
9.1.5.2.3 Master and Client Configuration
To configure Alcatel-Lucent OmniPCX Enterprise CS the software update feature, definemaster CPUs and client CPUs. The feature master or client is defined in the SofwareDownload tab of the PCX (or PCS) Directory window.
9-15
Figure 9.11: Software Download Configuration Tab
Master node: For a master CPU, leave this field blank. For a client, enter its master CPUdetails.
A similar window is available for PCS.
For more information on this window, see: module Directory - System tab § Declaring a PCX .
9.1.5.3 Operation
1. Select a PCS, node, subnetwork, network, or the root in the maintenance tree.
2. Select Software update.The Software update window appears:
Chapter 9
9-16
Figure 9.12: Maintenance — Software Update Window — Choice of a Software Version
3. In the Choice of a software version tab, select a software version in the default directoryfrom the drop down box, or select Search for software version. Enter a directory path inVersion path, or use the Search... function.
Note 1:The default directory is managed in the Maintenance Preferences menu (see § Configuring Settings).
To identify a PCX software package, check for the presence of the following files in<version>/installinux directory.
Static patch Secured staticpatch
Dynamic patch Secured dynamicpatch
Full version
Patch X X X X
Patchdyn X X
Seculinux.list X X
rload X X X X X
4. Click Continue.According to the entry selected (PCS, node, subnetwork, network or root), theAlcatel-Lucent OmniVista 4760 Network Management System compares the software
9-17
version of each of the PCXs and determines if it can be updated with the selected softwareversion. The names of the PCXs selected, what role each PCX plays (master or client),and the date of the switch to the new software installation are displayed in theCompatible(s) sub-tab of the Selected target(s) tab:
Figure 9.13: Maintenance — Software Update Window — Select Target(s)The Alcatel-Lucent OmniVista 4760 Network Management System completes this tableaccording to the attributes entered for: (• the subnetwork on the OXE Software download tab in the System directory• or the Software Download tab of the PCX if the corresponding Apply in local
account parameters attribute is set• or the Software Download tab of PCS if the corresponding Apply in local account
parameters attribute is setThe minimal software versions required for the master and the client are specified inPreferences tab of the OXE Software download. These attributes are used to find thecompatible and incompatible PCXs.Any PCX that cannot support the selected release to be downloaded is listed in theIncompatible(s) sub-tab. The current software version, and the reason for the refusal arelisted.
5. Select the PCXs you wish to upgrade in the Compatible(s) sub-tab. You may change theSwitchover date by clicking the field. Possible values are:• No switchover
Chapter 9
9-18
• Immediate switchover after software installation• Delay before switch: select a delay period which starts once the software installation is
completed• Switch date: select a date and an hour
Note 2:It is recommended not to schedule a switch over, when a full version upgrade is pending.
6. Click Apply.A window appears for scheduling the task.
7. Enter an installation date, or choose to launch the update immediately.
9.1.6 Software Update Status
To check the status of the last software update operation:
1. Select the entry in the maintenance tree and click Software Update Status.If the entry selected is a PCX, then the details of the update operation are displayed.Otherwise, a list of PCXs is displayed in the Software updates in progress tab:
Figure 9.14: Maintenance — Software Update Status WindowTo update the displayed details, click Refresh (To get the Refresh button, select the PCXand right-click).
2. For more information on the status of the update for a particular PCX, click the PCX nameor select the Software update details tab.More information is displayed showing the context of the software update: the softwareversion/ patch name, the master PCX, the client PCXs, and the name of the log file. Todisplay the log file in the default browser, click the log file name.To get the status file from the master PCX, click Refresh.
Note 1:If the switch time for a PCX has not been reached, the software version shown in the status windowwill not have been updated. In this case the installation status is OK but the version has not yetchanged.
9-19
Note 2:The log file is transferred from each master PCX during either a PCX to System Directory partial orcomplete synchronization, a configuration connection, or by the Alcatel-Lucent OmniVista 4760 Net-work Management System server when the software update task is launched.
9.1.7 Configuring Settings
To access the configuration settings, in the toolbar, select Preferences > Maintenance >Configuration. The Configuration window is displayed. The settings are configured via thefollowing tabs:
- Backup/Restore 4760
- Backup/Restore PCX
- PCX Software Update
- Temporary files
The settings required for correct operation of maintenance operations concern:
- The location of the default directories for storage of Alcatel-Lucent OmniVista 4760Network Management System and PCX backups, and temporary files.
- The thresholds based on available disk space for the storage of the backup and temporaryfiles.
- Archive storage time for backup files.
- The location of the software versions for downloading and updating remote OmniPCX4400 \ Alcatel-Lucent OmniPCX Enterprise CS
9.1.7.1 Setting Default Backup and Temporary File Storage Directories
1. In the Configuration window, select the tab according to the type of files for which youwish to set a default directory, either Backup/Restore 4760, Backup/Restore PCX, orTemporary files.
2. Enter the directory path in Backup location, or find it by selecting Search.
3. Click Apply to save the setting.
9.1.7.2 Configuring Disk Space Thresholds
1. In the Configuration window, select the tab according to the type of files for which youwish to configure thresholds for, either Backup/Restore 4760, Backup/Restore PCX, orTemporary files.
2. Select the Type of Control in terms of:• Maximum archive size.• Or, available drivespace.
3. Select Unit and select the unit included for threshold values (%, KB, MB, GB).
4. Specify the threshold values:• First threshold: depending on the tracking type, available hard drive space or archive
size from which a minor alarm is transmitted.• Second threshold: depending on the tracking type, the available hard drive space or
the archive volume value from which a major alarm is transmitted.
Chapter 9
9-20
Note:Backups (Saves) are no longer performed until automatic backup cleaning or manual cleaningbrings drive space below the second threshold.
5. Click Apply to save the settings.
9.1.7.3 Defining Record Life
1. In the Configuration window, select the tab according to the type of files for which youwish to define a record life for, either Backup/Restore 4760 or Backup/Restore PCX.
2. Select the Unit (month or day) to be used.
3. Specify record storage time according to the unit selected.All records saved on the server for a period exceeding the length of time specified in thisfield are deleted. This storage check is performed daily by the Scheduler.
4. Click Apply to save the settings.
9.1.7.4 Setting Directory for Access to Software Versions
To define the directory where the software versions will be accessible during the softwareupdates:
1. In the Configuration window, select the PCX Software Update tab.The system shows the default path in Software version location.
2. To change the location, click Search.The Software version location dialog box is displayed, allowing access to all directorieson all drives of the Alcatel-Lucent OmniVista 4760 Network Management System server,and all remote directories readable by the Alcatel-Lucent OmniVista 4760 NetworkManagement System server.
3. Select a directory and click OK. The system registers the new location in the LDAPdatabase in the Path attribute of the OXE Software Download object class of theSave-Restore service.
Note:If you choose a directory on another computer, the network expert must share the directory. See theSecurity chapter of the Alcatel-Lucent OmniVista 4760 Network Management System InstallationManual.
4. Click Apply to save the setting.
9-21
Chapter 9
9-22
10.1 Overview
10.1.1 Overview
As of R5.0, the Audit application allows to display management operations performed on anAlcatel-Lucent OmniPCX Enterprise CS, supervised by the Alcatel-Lucent OmniVista 4760Network Management System.
With the Audit application, the security manager has a complete view of all configurationoperations performed on the Alcatel-Lucent OmniPCX Enterprise CS network.
Operations supervised by the Audit application are command details: when and by whomAlcatel-Lucent OmniPCX Enterprise CS configuration has been modified.
The Audit application works with information recorded in audit files stored on theAlcatel-Lucent OmniPCX Enterprise CS.
A synchronization operation allows to retrieve these audit files in the Alcatel-Lucent OmniVista4760 Network Management System. These files are processed and audit information is storedin the audit database.
The graphical user interface of the audit application:
- Displays summaries of operations
- Displays details of individual operations
- Filters information to display pertinent information only
The audit database is also used to perform predefined or customized audit reports. For moreinformation on reports, see: module Reports - Use .
Note:
The Audit application is compatible with Alcatel-Lucent OmniPCX Enterprise CS R7.1 and higher.
10.2 Configuration procedure
10.2.1 License
The Audit application requires a specific license to:
- Retrieve audit information from the Alcatel-Lucent OmniPCX Enterprise CS
- Access the Audit graphical user interface
- Display audit reports
The audit license is included in the license file named , located in the directory:
Example of a license file:
10
10-1
Audit = 1
The line Audit = x defines audit rights:
- Audit = 0 means the audit application is not available
- Audit = 1 means the audit application is available
Note:
The line Signature = ... protects the nmc.license file. You cannot edit this license file. Contact Alcatel-Lu-
cent for modification.
10.2.2 Audit Application Configuration
The Audit application configuration is performed in the Directory window.
To access audit application configuration:
1. Select the System tab in the left part of the Directory window
2. Open the branch of your Alcatel-Lucent OmniVista 4760 Network Management System(SYS0005 in the example below)
3. Open the branch: Server
4. Open the branch of your Alcatel-Lucent OmniVista 4760 Network Management System(SYS0005 in the example below)
5. Click on AuditServer to display the configuration of the audit server___change-begin___
Chapter 10
10-2
___change-end___
Figure 10.1: Access to Audit Application Configuration
In the General tab, the following information is displayed:
- Name
- Description
- Service Path
- Argument List
- Datapath
- Status of the jobs
In the NT account tab, the following information is displayed:
- Username:
- Password:
In the Specific tab, the following information is displayed:
- Audit Process: validate the checkbox to enable the Audit application (this parameter isalso called Audit Global Flag)
- Purge Limit for System Log (days): enter the life time of System Log records in thedatabase
10-3
- Purge Limit for MAO Log (days): enter the life time of MAO Log records
- Purge Limit for Log File (days): enter the life time of Log record
- Purge Limit for Export Log File(days): enter the lifetime of exported csv log files.Exported files (in the default directory) older than this lifetime are automatically deleted
- Minimum OXE Version: indicates the Alcatel-Lucent OmniPCX Enterprise CS minimumversion compatible with the present release of the Alcatel-Lucent OmniVista 4760 NetworkManagement System
- CORBA port
- Keep one backup: if this flag is enabled, the purging process will not affect the lastestexported csv file.
10.2.3 Audit Alcatel-Lucent OmniPCX Enterprise CS Configuration
The Alcatel-Lucent OmniPCX Enterprise CS to audit must be configured:___change-begin___
___change-end___
Figure 10.2: Access to Alcatel-Lucent OmniPCX Enterprise CS Audit Configuration
1. Select the desired Alcatel-Lucent OmniPCX Enterprise CS in the PCX tree of the Systemtab
2. Select the Data Collection tab:
Chapter 10
10-4
• Process Audit: validate the checkbox to enable audit on the selected Alcatel-LucentOmniPCX Enterprise CS
• Audit Last Record: displays the last audit-relevant information downloaded from theAlcatel-Lucent OmniPCX Enterprise CS
3. Select the Software download tab:• Username maintenance: enter the user account used for maintenance on the
Alcatel-Lucent OmniPCX Enterprise CS. Typically, the account is used• Password maintenance: enter the password associated to the username above
10.2.4 Audit Manager Access Rights
To access the audit graphical user interface, the Alcatel-Lucent OmniVista 4760 NetworkManagement System user must be authorized.
To give access rights to a user:
1. Open an administrator session on the Alcatel-Lucent OmniVista 4760 NetworkManagement System
2. In the menu bar, click on Security to open the drop down list
3. Click on Audit to open the Access Control Editor window
4. Click the Add.. button to open the Add Users window
5. In the Add Users window, select the new audit manager among the displayed users andclick OK
6. Select the appropriate Access Level for the selected audit manager:• Read: the manager can only read audit information• All: the manager can perform all audit commands• No Access: the manager cannot access audit application
7. Click OK, the audit access rights are given to the selected user___change-begin___
___change-end___
Figure 10.3: Example of Access Control Window
10-5
In the example above, John Smith is granted the rights of audit manager.
10.3 Retrieving Audit Information
10.3.1 Overview
The Audit application works with information recorded in audit files located on theAlcatel-Lucent OmniPCX Enterprise CS. These files must be retrieved from eachAlcatel-Lucent OmniPCX Enterprise CS supervised by the Alcatel-Lucent OmniVista 4760Network Management System.
In case of Call Server duplication or Spatial Redundancy, audit files are only retrieved from themain CPU.
Audit files are retrieved from the Alcatel-Lucent OmniPCX Enterprise CS during asynchronization operation.
The Audit application processes these files and stores the related information in the auditdatabase.
If the or files are not processed properly, an internal alarm is generated.
Note 1:
Audit files are not retrieved from PCSs. Audit files cannot be retrieved with bulk imports.
Note 2:
No internal alarm is generated in case of audit file download failures.
10.3.2 Alcatel-Lucent OmniPCX Enterprise CS Audit Files
Audit files are automatically created or updated on the Alcatel-Lucent OmniPCX EnterpriseCS, each time an operation is performed. These files are text files and can be displayed on theAlcatel-Lucent OmniPCX Enterprise CS with UNIX tools (for example: )
10.3.2.1 mao_hist File
The file contains the history of commands. Each time amodification is performed in the database, a new line is added. The database can bemodified via the tool, Alcatel-Lucent OmniVista 4760 Network Management System (orOmnivista 4760i) application or Alcatel-Lucent OmniPCX Enterprise CS audit/broadcastprocess.
Example of file:
Meaning of fields:
Chapter 10
10-6
7: this number is the number of mao records.
Each line contains:
- The action date and time
- The action performed: CREATE, UPDATE, DELETE, ACTION, ACTION_MAO andACTION_ACCOUNTING.
- For actions: CREATE, UPDATE or DELETE, the andparameters specify the mao objectFor example: means that thenumbering plan descriptor number 51 of node 22 have been deleted. Number 1 means nochoice as used in the tool. For more information on the tool, see the relatedAlcatel-Lucent OmniPCX Enterprise CS technical documentation.
- For ACTION_MAO the following information gives the mao action:• MAO on• MAO off• MAO reset• BROADCAST on• BROADCAST off• Mastercopy On• Mastercopy Off• Mastercopy Wait Stand_by
- The information in parentheses indicates the identity of the manager who has performedthe action being scrutinized:• : remote application identity• : remote identity (broadcast application)
0 = subnetwork number, 21 remote node
The file can contain a maximum of 1000 records. When the file is full,the system copies it in the file. Up to 2000 mao records in all can be stored.
Note:
Records about ACTION_MAO and ACTION_ACOUNTING actions are not inserted in the audit database.
This information is not processed by the audit server.
10.3.2.2 mao_hdet File
The file contains the details of each record stored in thefile. Only records with the actions: CREATE, UPDATE or DELETE are detailed.
When the file content is copied in the file, the filecontent is copied in the file.
Note:
Detailed readable record information is available in the file which is
generated with the command.
Information recorded in this file is similar to the information displayed with the tool.
10.3.3 Retrieving Audit Data
10-7
10.3.3.1 Launching Synchronization
Synchronization retrieves audit files from the specified Alcatel-Lucent OmniPCX EnterpriseCS.
To launch a synchronization:
1. Start the Directory application
2. Right click the Alcatel-Lucent OmniPCX Enterprise CS of your choice
3. Select the desired synchronization type:• Complete: the whole information, including audit files, is retrieved• Partial: the whole new information, including audit files, is retrieved• Audit Information: only audit information is retrieved
An immediate, a scheduled or a periodic synchronization can be performed to retrieve auditinformation.___change-begin___
___change-end___
Figure 10.4: Example of Launching an Audit Information Synchronization
For more information on synchronization, see: module Directory - Synchronizing PCX data
10.3.3.2 Synchronization Process
Chapter 10
10-8
To retrieve audit information, the Alcatel-Lucent OmniVista 4760 Network ManagementSystem:
1. Opens an (or if transfers are secured) session, with the Username maintenanceaccount, as defined: module Audit - Configuration procedure § Audit Configuration .
2. Retrieves audit files from the Alcatel-Lucent OmniPCX Enterprise CS
3. Stores temporarily these files in thedirectory:where represents the network number and the subnetwork number of the specifiedAlcatel-Lucent OmniPCX Enterprise CS.
4. Loads audit information in the audit database
5. Deletes the temporary files of the directory
6. Stores the last record in the specified Alcatel-Lucent OmniPCX Enterprise CS data. Thisinformation can be displayed in the Data Collection tab, parameter Audit Last Record ofthe specified Alcatel-Lucent OmniPCX Enterprise CS.This information is useful to retrieve new audit information only.
The synchronization process can be verified in:
- The Create multiple tasks in the Scheduler window (this window is opened to launch asynchronization): click the radio button of the task and select the Status tab
- The Scheduler application: select your synchronization report and in the right part of thewindow select the Status tab
Example of messages in the Status tab window for an audit synchronization:
In this example: an RSH session is successfully opened and audit files are successfullyretrieved.
10.4 Displaying Audit Information
10.4.1 Audit Graphical User Interface Access
10-9
icon to launch the audit graphical user interface.
The system checks the license of the Alcatel-Lucent OmniVista 4760 Network ManagementSystem and the manager access rights.
Note:
In the Configuration application, you can also access the audit grid for the specified PCX.
10.4.2 PCX Tree
A PCX tree allows to select an Alcatel-Lucent OmniPCX Enterprise CS.
The PCX tree is similar to the one used in the directory application.
Note:
In addition, the PCX tree allows to start the Configuration application on a specified PCX.
To start the Configuration application:
- Select the specified PCX
- Right click
- Select Configure
10.4.3 Mao Grid
The mao grid displays actions performed by the user on an object.
Chapter 10
10-10
___change-begin___
___change-end___
Figure 10.5: Example of Mao Grid
Meaning of the displayed fields:
- HistoryId: record identifier
- ServerName: name of the server
- User: name of the user account
- Date: date of the action
- Action: action performed by the user (creation, modification, deletion)
- Object: name of the object
- NodeId: node number
- Attribute1 to Attribute5: mandatory attributes
Note:
The mao grid is not refreshed dynamically. To refresh the grid:
- Select an element in the tree structure
- Right click and select Refresh
10.4.4 Mao Detail Information
Details for a specific action can be displayed: double click a line of the mao grid.___change-begin___
10-11
___change-end___
Figure 10.6: Example of Mao Detail Window
In this window, the changed attributes are displayed.
10.4.5 Filtering
Audit information can be filtered to display only specific records.___change-begin___
___change-end___
Chapter 10
10-12
To activate filters:
1. Set the filter first level.To activate this filter:a. Select one of the following fields:
• ServerName: name of the server through which the PCX is accessed• User: name of the user logged on the PCX• MaoDate: PCX date of the action• Action: name of the action performed• Object: object name on which the action is performed• NodeID: node number of the PCX
b. Select the operator Not Equal, Equal ...c. Enter or select valueUsed the icon to add an extra condition (optional).
2. Set the filter second level.To activate this filter:a. Select the field Attribute 1 ... Attribute 5b. Select the operator Not Equal, Equal ...c. Enter the valueUsed the icon to add an extra condition (optional).
3. Click the icon to activate filtering
Note:
Filtering fields are translated according to the user language. mao object names are always in English.
10-13
___change-begin___
___change-end___
Figure 10.8: Example of Filtering Audit Records
10.4.6 Audit Information from the Configuration Application
From the Configuration application, you can also access audit information for the specifiedPCX.
Click the Audit tab to display the audit grid.
Chapter 10
10-14
___change-begin___
___change-end___
Figure 10.9: Audit Information from Configuration Application Example
The complete list of audit records is displayed. Object selection for audit information issupported only for Shelf, Board and User from the tree.
10.5 Maintenance
10.5.1 Purging Audit Records from Database
The audit database is purged automatically of the oldest information. Information older thanwhat is specified in the audit configuration is automatically deleted. For more information onaudit configuration, see: module Audit - Configuration procedure § Audit ApplicationConfiguration .
10.5.2 Exporting Log Information
The Export feature allows to export audit information from the audit database:
- Open the audit application
- In the PCX tree, select an Alcatel-Lucent OmniPCX Enterprise CS
- Right click and select Export.
- Select the type of export:• Click Immediate on local drive for an immediate operation.
Select the type of data to save:• Click History to save history information• Click Detail to save detailed information
10-15
A browser opens:• Navigate to the specified directory• Enter the filename of the exported file• Click Save. The audit information of the selected Alcatel-Lucent OmniPCX
Enterprise CS is exported to a CSV (Comma-Separated Values) format file.• Click Scheduled on server
Select the type of saved data:• Click History to save history information• Click Detail to save detailed informationA browser opens in the directory:• Navigate to the specified sub directory only• Enter the filename of the export file• Click Export. The audit information of the selected Alcatel-Lucent OmniPCX
Enterprise CS is exported to a CSV (Comma-Separated Values) format file.A window opens to select the desired type of task:
• Select: Simple job and click Continue. The Create a task in the scheduler...window is opened to define the specified task. For more information on thiswindow, see: module Scheduler - Overview .
• Select: Synchronized task and click Continue. The Create a task in thescheduler... window opens to define the specified task. For more information onthis window , see: module Scheduler - Overview .
___change-begin___
___change-end___
Figure 10.10: Example of Exported File
Note:
An option allows to select an immediate or scheduled export.
10.5.3 Save and Restore of Audit Database
The Alcatel-Lucent OmniVista 4760 Network Management System database backup andrestore process includes the backup and restore of audit information. For more information onbackup and restore, see: module Maintenance - Maintenance § Maintenance .
Chapter 10
10-16
10-17
Chapter 10
10-18
11.1 Overview
11.1.1 Overview
As of R5.0, the SIP Manager application, embedded in the Alcatel-Lucent OmniVista 4760Network Management System, provides a graphical user interface enabling SIP devices'commissioning and SIP devices' daily maintenance. This application allows to deploy quickly alarge quantity of SIP devices.
The SIP Manager application enables, notably:
- To configure SIP users (creation, update and deletion)
- To configure SIP devices (creation, update and deletion)
- To assign one or several SIP devices to a SIP user (i.e. SIP User-Device links)
- To make configuration data accessible to SIP devices (for their commissioning)The configuration data accessibility can be carried out immediately or on a scheduledbasis (when it applies to all SIP devices)
- To make software versions accessible to SIP devices (for their update)The software version accessibility can be carried out on a specific type of SIP device andcan be immediate or scheduled
- To import SIP users and/or data related SIP devices to a file (in CSV format)The CSV format is compatible with any text editor (information is separated bysemicolons).
Several operations relating to SIP device configuration and assignment can also be performedfrom the Configuration application of the Alcatel-Lucent OmniVista 4760 NetworkManagement System (see: § Interaction with the Configuration Application ).
The SIP Manager application operates in association with a dedicated server named DeviceManagement (or DM). The DM server is installed on a computer running the Alcatel-LucentOmniVista 4760 Network Management System server and includes a database (with LDAPdirectory) where are stored:
- SIP users configuration data (in particular: Uniform Resource Identifier (URI), user name,login and password)
- SIP devices configuration data (in particular: device type, MAC address, Proxy andRegistrar attachment)
- The software version of SIP devices
SIP user data synchronization with the PCX is required. When a SIP user is created via theSIP Manager application, the PCX database is updated with the SIP user data. When a SIPuser is created on the PCX, the DM server database, in turn, is updated with the SIP userdata.
Both databases (PCX and DM server) must be manually synchronized the very first time theSIP Manager application is started.
11.1.2 Preliminary Operations
11
11-1
11.1.2.1 Checking the License Enabling SIP Manager Application Access
A specific license is required to access the SIP Manager application. It is included in thelicense file named , located in the directory: .
Caution:
This license does not define the maximum number of SIP devices (and non Alcatel-Lucent
devices) supported by the SIP Manager application. These limits are determined by the API
Framework license on the DM server (based on FlexLm server). The maximum number of SIP
users is limited by the number of users that can be configured in the Alcatel-Lucent OmniVista
4760 Network Management System.
To check the license status:
1. From the computer desktop, go to the directory: .
2. Select the license file and open it in a text editor.
Example:
3. Verify that the line = 1 is presentThe SIP Manager application is not available If the license file containsor the SIP Manager key is not available.
11.1.2.2 Configuring Access Parameters to the DM Server
Access parameters to the DM server must be configured in the Directory application:
1. Open the Directory application and click the System tab.
2. Select nmc.
3. In the right hand-side of the window, click the Directory tab.In the Directory tab, the parameters required to access the DM server are displayed.
___change-begin___
Chapter 11
11-2
___change-end___
Figure 11.1: DM Server Access Parameters Configuration Window
4. Enter the following details:• The DM server name in the Name field• The IP address of the DM server in the Server IP address field
Caution 1:Do not use the host name of the DM server.
• The port number used to access the DM server in the HTTP Port field. The defaultvalue is 8080
Caution 2:Use a different HTTP port number than the one used for the Alcatel-Lucent OmniVista4760 Network Management System server (default value: 80), as the two servers run onthe same computer.
• The port number used to access the Web Based Management (WBM) in the HTTPSPort field. The default value is 8443
Notes:
• The port numbers used are the ones defined at the time of the DM server installation.
• Only one DM server can be configured for the entire system (network, sub-networks and variousnodes).
5. Click the icon to apply your modifications.
11.1.2.3 SIP Manager Application Access Rights
The access rights to the SIP Manager application must be defined for each potential user.
To give access rights to a user:
11-3
1. Open an administrator session on the Alcatel-Lucent OmniVista 4760 NetworkManagement System.
2. In the menu bar, select the SIP Manager option from the Security menu.The Access Control Editor window opens
3. Click the Add.. button.The Add Users window opens
4. Select the new SIP manager among the displayed users and click OK.
5. Select the appropriate Access Level for the selected SIP manager:• Read: the manager can only read SIP user/device information• All: the manager can perform all SIP commands• No Access: the manager cannot access the SIP Manager application
6. Click OK.The SIP Manager access rights are given to the selected user
11.1.3 Accessing the SIP Manager Application
Accessing the SIP Manager application can be done:
- By selecting the SIP Manager option in the Applications menu.
- By clicking the icon.
The system checks the license of the Alcatel-Lucent OmniVista 4760 Network ManagementSystem and manager access rights.
Note:
A warning message is displayed when the connection to the DM server fails.
11.1.4 SIP Manager Application Main Window___change-begin___
Chapter 11
11-4
___change-end___
Figure 11.2: SIP Manager Application Main Window Example
The SIP Manager application main window is divided into six different areas:
1. A SIP user/device list area: displays the complete list of configured SIP users and SIPdevices in the SIP Manager application (see: § SIP User/Device List Area Presentation ).
2. A search area: allows to apply a specific filter for SIP users or SIP devices supervision(see: § Search Area Presentation )
3. A properties area: displays detailed information on the selected SIP user(s) or SIPdevice(s) by theme (see: § Properties Area Presentation )
4. A toolbar: includes specific icons dedicated to SIP user and SIP device configuration:
Icon Definition
To assign a SIP device to a SIP user
To export a template of SIP users and/or devices or toimport SIP users and/or SIP devices' information from a file.This last operation allows to restore a configurationpreviously saved on the computer
5. Two information fields: when the SIP device tab is selected, two additional fields appear atthe bottom right of the SIP Manager interface. It displays:
11-5
• The number of Alcatel-Lucent SIP devices configured and the maximum number ofAlcatel-Lucent SIP devices supported by the SIP Manager application (licensecontrol).
• The number of third party SIP devices configured and the maximum number of thirdparty SIP devices supported by the SIP Manager application (license control).
6. A status bar: displays the result of operations carried out from the SIP Manager application(errors, warnings, and information messages).
11.1.4.1 SIP User/Device List Area Presentation
The SIP user/device list area content depends on the tab selected.
11.1.4.1.1 Networks Tab
The Networks tab provides a tree structure organized into two branches:
- The > > branch. It displays the configuration of SIP usersaccording to the node they belong to. SIP devices assigned to a SIP user are displayedbelow the corresponding SIP user information (i.e. User-Device link).This branch enables to:• Select one or several configured SIP users to display their parameters in the properties
area (multiple selections are allowed).This operation can also apply to the User-Device link defined under a SIP user.
• Access configuration options via a contextual menu at node level:
Option Definition
Create SIP user To create a new SIP user
Export Template To export a template file for SIP users, SIPdevices and links. This template appears as anempty file (no data) with predefined headers
Import To import SIP Users and/or SIP devices datafrom a file
Refresh To refresh the SIP user list
• Access configuration options via a contextual menu at SIP user level:
Option Definition
Create SIP device To create a new SIP device
Setting links To create a User-Device link
Delete To delete an existing SIP user
Refresh To refresh the User-Device links
• Access configuration options via a contextual menu at SIP device level:
Option Definition
Deploy Configuration file To send configuration data to a SIP device
Delete Links To remove a User-Device link
- The branch. It displays the configured SIP devices not assignedto any SIP user.This branch enables to:
Chapter 11
11-6
• Select one or several configured SIP devices to display their parameters in theproperties area (multiple selections are allowed).
• Access configuration options via a contextual menu:
Option Definition
Create SIP Device To create a new SIP device
Delete To delete an existing SIP device
Note 1:This option is available if the branch contains alreadyconfigured SIP devices.
Refresh To refresh the SIP device list
Note 2:
Only systems of the Alcatel-Lucent OmniPCX Enterprise Communication Server type in R5.0 are dis-
played in the tree structure. Systems of the type:OmniPCX Office and OmniPCX 4400 are not displayed.
11.1.4.1.2 Parameters Tab
The Parameters tab allows to access SIP device types list defined in the DM server. Itdisplays their common parameters in the properties area. All parameters (i.e. configurationdata) common to a SIP device type are registered in a dedicated configuration file in the DMserver.
For R5.0, the available SIP device's type is STCom (for both Thomson ST2022 and ST2030).
11.1.4.2 Search Area Presentation
The search area is only available when the Networks tab is selected and the tree structure isexpanded to the level of a specific node.
When a node is selected, the search area provides a field allowing to select the criteria onwhich the filter must apply. This filter can be used to limit SIP users or SIP devices display inthe properties area. For more information on filter configuration, see: module Interface - Datasearch .
11.1.4.3 Properties Area Presentation
When a SIP user or SIP device is selected from the Networks tab, its parameters aredisplayed in the properties area and classified by theme:
- For SIP users configuration, two tabs are accessible: General and OXE. The parametersdisplayed in these tabs correspond to the PCX parameters required to configure SIP usersoperating in SEPLOS mode. Mandatory parameters are written in bold characters andread-only parameters are written in italic characters.When SIP users are configured via the SIP Manager application, their parameters arestored in the database of the DM server (LDAP directory). They are used to create (orupdate) SIP users on the PCX.To know the meaning of these parameters, refer to the SIP End Point Level of Servicedocumentation of the OmniPCX Enterprise relating to operations on the SIP Com Server.
- For SIP device configuration, several tabs are accessible (genericValues, sip, etc.). Whenconfigured via the SIP Manager application, the parameters displayed in these tabs arestored in the database of the DM server (LDAP directory). They are used to create (orupdate) a specific configuration file sent later to the SIP devices (see: § Making
11-7
Configuration Data Accessible to SIP Devices ). The configuration file of each SIP devicecontains at least a unique MAC address. Mandatory parameters are written in boldcharacters and read-only parameters are written in italic characters.For more information on the meaning of:• The parameters of genericValues tab: refer to the SIP End Point Level of Service
documentation of the OmniPCX Enterprise relating to operations to perform on SIPsets.
• The parameters of the other tabs: refer to the manufacturer documentation of thecorresponding SIP device.
Tabs are located at the bottom of the properties area.___change-begin___
___change-end___
Figure 11.3: SIP Device Parameters Display Example
If several SIP users or SIP devices are selected, their parameters are displayed in a grid. ForSIP devices, only common parameters are displayed in a grid in the General tab.___change-begin___
Chapter 11
11-8
___change-end___
Figure 11.4: Grid Display
When a SIP device type is selected in the Parameters tab, the properties area displays thecommon parameters for a SIP device type. This selection mode is useful to carry out the sameoperation on several SIP devices in one go.
11.1.5 Additional SIP Features in the Alcatel-Lucent OmniVista 4760 NetworkManagement System Main Window
Specific menu and icons appear in the Alcatel-Lucent OmniVista 4760 Network ManagementSystem main window when the SIP Manager application is opened.___change-begin___
___change-end___
Figure 11.5: Alcatel-Lucent OmniVista 4760 Network Management System Main WindowExample
A SIP Manager menu is added to the menu bar. It provides access to the following options:
11-9
Option Definition
WBM To open a session of the WBM application (path:
)
Deploy Firmware To update the software version of SIP device. Update iscarried out per SIP device type.
Installed Firmware To display the list of software versions already sent to SIPdevices. Display is carried out per SIP device type.
Deploy configuration filesfor all devices
To send configuration data to all the SIP devices.
Certain options are also available from the icon bar. The correspondence between the menuoptions and icons is:
Icon Definition
Deploy Firmware
Deploy configuration files for all devices
WBM
11.1.6 Interaction with the Configuration Application
When a SIP user is selected in the tree structure of the Configuration application mainwindow, a SIP Manager tab is displayed behind the other tabs (Configuration, Accounting,etc.).
The SIP Manager tab allows to display the parameters of the SIP device already assigned tothe selected SIP user. When several SIP devices are associated to the selected SIP user, allparameters common of these SIP devices are displayed.
If several SIP devices are already assigned to the SIP user, a selection window opens listingthe available assigned SIP devices. If the selected SIP user has not been assigned any SIPdevice, the SIP Manager tab content is empty.
The SIP Manager tab allows to:
- Create and assign a SIP device to a SIP user (by clicking the icon). The configuration
file can be sent to the SIP device at a later point
- Assign a SIP device to a SIP user (by clicking the icon). This operation is similar to
the operation described: § Adding a User-Device Link .
11.1.7 Operations
11.1.7.1 Configuring SIP Users
11.1.7.1.1 Creating a SIP User
1. From the SIP Manager application interface, click the Networks tab.
Chapter 11
11-10
2. Expand the tree structure and select the target PCX.
3. Access the contextual menu and select Create SIP User.Parameters relating to this SIP user are displayed in the properties area.
___change-begin___
___change-end___
Figure 11.6: SIP User Configuration Window
4. Click the corresponding tab at the bottom of the window and enter parameters as desired.
Reminder:Mandatory parameters are written in bold characters and read-only parameters are written in italiccharacters.
5. Click the icon to confirm SIP user creation.
11.1.7.1.2 Modifying SIP User Data
1. From the SIP Manager application interface, click the Networks tab.
2. Expand the tree structure and select the target SIP user(s) (multiple selections areallowed).The parameters relating to the selected SIP user(s) are displayed in the properties area.
3. Click the corresponding tab at the bottom of the window and modify parameters asrequested.
Reminder:Mandatory parameters are written in bold characters and read-only parameters are written in italiccharacters.
4. Click the icon to apply modifications.
11-11
11.1.7.1.3 Deleting a SIP User
1. From the SIP Manager application interface, click the Networks tab.
2. Expand the tree structure and select the target SIP user(s) (multiple selections areallowed).
3. Access the contextual menu and select Delete.A confirmation window opens.
4. Click Yes to confirm the SIP user deletion.If SIP devices were assigned to the SIP user deleted, they are now displayed in theUnallocated Devices branch.
11.1.7.2 Configuring SIP Devices
11.1.7.2.1 Creating a SIP Device
1. From the SIP Manager application interface, click the Networks tab.
2. If the new SIP device must not be assigned to a SIP user, click the Unallocated Devicesbranch.
3. If the SIP device must be assigned to a SIP user, expand the tree structure and select thetarget SIP user to which the new SIP device must be assigned.
4. Access the contextual menu and select the SIP device type: ST2022 or ST2030(supported options in R5.0).Parameters relating to this SIP device are displayed in the properties area.
5. Click the corresponding tab at the bottom of the window and complete the parameters.
Reminder:Mandatory parameters are written in bold characters and read-only parameters are written in italiccharacters.
6. Click the icon to confirm SIP device creation.
11.1.7.2.2 Modifying SIP Device Data
1. From the SIP Manager application interface, click the Networks tab.
2. If the SIP device is assigned to a SIP user, expand the tree structure and select the targetSIP device.
3. If the SIP device is not assigned to a SIP user, click the Unallocated Devices branch andselect the target SIP device.
4. In the properties area, click the corresponding tab at the bottom of the window and modifySIP device parameters as requested.
Reminder:Mandatory parameters are written in bold characters and read-only parameters are written in italiccharacters.
5. Click the icon to apply modifications.
11.1.7.2.3 Deleting a SIP Device
1. From the SIP Manager application interface, click the Networks tab.
Chapter 11
11-12
2. If the SIP device is assigned to a SIP user, expand the tree structure and select the targetSIP device.
3. If the SIP device is not assigned to a SIP user, click the Unallocated Devices branch andselect the target SIP device.
4. Access the contextual menu and select delete.A confirmation window opens.
5. Click Yes to confirm the SIP device deletion.
11.1.7.3 Configuring the User-Device Links for a SIP User
11.1.7.3.1 Adding a User-Device Link
1. From the SIP Manager application interface, click the Networks tab.
2. Expand the tree structure and select the target SIP user to which the SIP device must beassigned.
3. Click the icon or access the contextual menu and select Setting Links.
A search window opens with the list of SIP devices defined in the Unallocated Devicesbranch.
___change-begin___
11-13
___change-end___
Figure 11.7: User–Device Link Configuration Window
4. Select a SIP device in the displayed list.A search area can be used to limit the SIP devices displayed in the list.
5. Click OK to apply your modifications for this SIP user.The selected SIP device is assigned to the SIP user.
11.1.7.3.2 Removing a User-Device Link
1. From the SIP Manager application interface, click the Networks tab.
2. Expand the tree structure and select the target SIP device.
3. Access the contextual menu and select Delete Links.A confirmation window opens.
4. Click Yes to apply your modifications for this SIP user.The User-Device link is removed for this SIP user. The SIP device is now displayed in theUnallocated Devices branch.
11.1.7.4 Making Configuration Data Accessible to SIP Devices
11.1.7.4.1 Making Configuration Data Accessible to a Single SIP Device
1. From the SIP Manager application interface, click the Networks tab.
2. Expand the tree structure and select the target SIP device.
3. Access the contextual menu and select Deploy Configuration File.When this operation is completed, a message is displayed in the status bar to notify thatdata are accessible for download.
11.1.7.4.2 Making Configuration Data Accessible to all SIP Devices
1. From the Alcatel-Lucent OmniVista 4760 Network Management System Main Window,click the icon or select the Deploy configuration files for all devices option in the
SIP Manager menu.The task type selection window is displayed.
2. Select the type of job: Simple (default option) or Synchronized task. For more details,see: module Scheduler - Overview .
3. Click Continue.The scheduler window is displayed.
___change-begin___
Chapter 11
11-14
___change-end___
Figure 11.8: Scheduler Window
4. In the Start Date frame, select when the data will be accessible to the SIP devices:immediate (Now field) or scheduled (As scheduled field).
5. If the As scheduled field is validated, define the start time and date, availability frequency,and end date. For more details, see: module Scheduler - Overview § Scheduling .
6. Click Ok to make data accessible to the SIP devices and close the scheduler window.
11.1.7.5 Updating the Software Version of SIP Devices
The software update is carried out per device type.
1. From the Alcatel-Lucent OmniVista 4760 Network Management System Main Window,click the icon or select the Deploy Firmware option in the SIP Manager menu.
The Software Selection Window is displayed.___change-begin___
11-15
___change-end___
Figure 11.9: Software Selection Window
2. Select the SIP device type in the drop-down list located at the top of the window.
3. In the left hand-side of the browser, navigate to the specified directory.Software versions are displayed in the left part of the browser.
4. Select the software version and click Select.The task type selection window is displayed.
5. Follow steps 2. to 10. detailed: § Making Configuration Data Accessible to all SIP Devicesand click Ok when finished (operations are identical).
11.1.7.6 Exporting a Template of SIP Users and/or SIP devices
1. From the SIP Manager application interface, click the Networks tab.
2. Expand the tree structure and select the target node.
3. Access the contextual menu and select Export Template.A template selection window opens.
4. Select the template to export among the following options:• SIP User only• SIP Device only• SIP Users, Devices with links
5. Click OK to validate the selection.A browser is displayed.
6. Navigate to the specified directory where the file must be saved.
7. Click OK to confirm file creation.
11.1.7.7 Importing SIP users and/or SIP devices data from a File
Chapter 11
11-16
The file to import must be located on the Alcatel-Lucent OmniVista 4760 Network ManagementSystem server.
1. From the SIP Manager application interface, click the Networks tab.
2. Expand the tree structure and select the target node. To access the import feature, either:• Access the contextual menu and select Import.• Double-click the target node and click the icon in the properties area.
A template selection window opens.
3. Select the template to import to a file among the following options:• SIP User only• SIP Device only• SIP Users, Devices with links
4. Click OK to validate the selection.A browser is displayed.
5. In the left hand-side of the browser, navigate to the specified directory in which the file issaved.The available files are displayed in the left hand-side of the browser.
6. Follow steps 2. to 10., as detailed: § Making Configuration Data Accessible to all SIPDevices and click Ok when finished.
11-17
Chapter 11
11-18
12.1 Overview
12.1.1 Overview
A user can access the Alcatel-Lucent OmniVista 4760 Communication ManagementSystem (called Alcatel-Lucent OmniVista 4760 Network Management System in thisdocument) applications when he is declared in the Company directory with a password. Thelogin used to access the 4760 is the uid attribute. If the password is empty, the login cannot beused to connect to the 4760. Once the password is set, the login can be used to edit thepersonal LDAP entry and to connect to the Alcatel-Lucent OmniVista 4760 NetworkManagement System client. By default, the only application available is the Log on.Alcatel-Lucent OmniVista 4760 Network Management System of release 4.1 and higher,provides remote user authentication using the RADIUS server. For more information refer to §RADIUS Server .
Users can access the Alcatel-Lucent OmniVista 4760 Network Management Systemapplications according to theirs own rights or to the rights of the group to which theybelong.These groups may be predefined or customized. Members of a group with accessrights to the Alcatel-Lucent OmniVista 4760 Network Management System security featuremay customize these groups and assign individuals to them.The various predefined groups are located in the Company directory under the followingentries:
- Administrators
- Groups
- Managers
12.1.2 Administrator Accounts
The predefined AdminNMC account, which can only be viewed by members of theAdministrators group, is reserved for the installation technician (installer). This account hasaccess to all Alcatel-Lucent OmniVista 4760 Network Management System applicationswithout restriction.
12.1.3 Access Groups
There are 17 predefined access groups. These groups can only be viewed by members of theAdministrators group. By default, all the groups are empty.
12.1.3.1 “Administrators” Group
Members of this group have access to all Alcatel-Lucent OmniVista 4760 NetworkManagement System applications without any restrictions. These group members are the onlyones who have access to the Administration directory of the Company directory and cantherefore administer all account rights except for the rights of the AdminNMC account.Only the administrators can configure the RADIUS server and set the RADIUS serverauthentication mode.
12
12-1
12.1.3.2 “Accountants” Group
Members of this group have access only to Alcatel-Lucent OmniVista 4760 NetworkManagement System features linked with OmniPCX 4400 Accounting and Traffic analysisoperation.
Reminder:
This group cannot access Alcatel-Lucent OmniVista 4760 Network Management System Security.
12.1.3.2.1 Accounting/Traffic
Access to the application with Read level rights. Members can view Accounting and Trafficanalysis information (organization, tracking, last records, etc.).
12.1.3.2.2 Reports
Access to the application with Read level rights. Members can:
- View definitions of reports and predefined models and their own report definitions
- View or generate their own reports
12.1.3.2.3 Alarms
Access to the application with Read level rights. Members can view all correlated oruncorrelated alarms.
12.1.3.2.4 Scheduler
Access to the application with Modify level rights. Members can:
- View all tasks
- Create, edit, or delete only their own tasks
12.1.3.2.5 Other Applications
Access to the Directory, Configuration, Topology, and Maintenance applications isprohibited
12.1.3.3 “Accounting Experts” Group
Members of this group only have access to Alcatel-Lucent OmniVista 4760 NetworkManagement System features linked with Accounting and Traffic analysis administration andoperation.
Reminder:
This group cannot access Alcatel-Lucent OmniVista 4760 Network Management System Security.
12.1.3.3.1 Accounting/Traffic
Access to the application with Management level rights. Members can manage alladministration features of the Accounting and Traffic analysis applications.
12.1.3.3.2 Reports
Access to the application with Modify level rights. Members can:
- View and export definitions of reports and pre-defined models
Chapter 12
12-2
- View, create, edit, delete, or export their own reports, definitions of reports, and models
12.1.3.3.3 Alarms
Access to the application with Read level rights. Members can view all correlated oruncorrelated alarms.
12.1.3.3.4 Scheduler
Access to the application with Modify level rights. Members can:
- View all tasks
- Create, edit, or delete only their own tasks
12.1.3.3.5 Other Applications
Access to the Directory, Configuration, Topology, and Maintenance applications isprohibited
12.1.3.4 “Mask Data Access” Group
The members of this group can generate reports with unmasked data. By default, this groupincludes no members. When at least one member is registered, his/her associated passwordis requested when unmasked reports are generated.
12.1.3.5 “Simplified Configuration” Group
Members of this group have access to the Configuration application with Normal level rightsand to the PCX with Access Profile 10. This group is intended for the task of managing theattendant. Members can:
- Access all instances of Users, Hunt groups, and Speed dialing numbers in all OmniPCX4400 \ Alcatel-Lucent OmniPCX Enterprise CS systems
- View, edit, create, and delete OmniPCX 4400 \ Alcatel-Lucent OmniPCX Enterprise CSobjects and attributes according to the Profile 10 definition (see § Securing Access to theOmniPCX 4400 / OmniPCX Enterprise ).
12.1.3.6 “Network Managers” Group
Members of this group have access to all Alcatel-Lucent OmniVista 4760 NetworkManagement System features linked to an OmniPCX 4400 network operation.
Reminder:
This group cannot access Alcatel-Lucent OmniVista 4760 Network Management System Security.
12.1.3.6.1 Directory
Access to the application with Partial View Red List level rights. Members can view:
- All System directory objects
- Non-personal attributes of green, orange, or red list records in the Company directory
12.1.3.6.2 Configuration
Access to the application with Normal level rights and to the PCX with Advanced user (1)level rights. Members can:
12-3
- Manage all application features
- View, edit, create, or delete only PCX users
- View, edit, create, and delete OmniPCX 4400 \ Alcatel-Lucent OmniPCX Enterprise CSobjects and attributes according to the Profile 1 definition (see § Securing Access to theOmniPCX 4400 / OmniPCX Enterprise ).
12.1.3.6.3 Alarms
Access to the application with Clear level rights. Members can:
- View, acknowledge, or delete all uncorrelated alarms
- View or acknowledge correlated alarms
12.1.3.6.4 Topology
Access to the application with Read level rights. Members can view the standard display andcustomized displays.
12.1.3.6.5 Scheduler
Access to the application with Modify level rights. Members can:
- View all tasks
- Create, edit, or delete only their own tasks
12.1.3.6.6 Maintenance
Access to the application with OmniPCX 4400 maintenance level rights. Members can savePCX data and update OmniPCX 4400 \Alcatel-Lucent OmniPCX Enterprise CS software.
12.1.3.6.7 Other Applications
Access to the Accounting/traffic and Reports applications is prohibited.
12.1.3.7 “Network Experts” Group
Members of this group have access to all Alcatel-Lucent OmniVista 4760 NetworkManagement System applications but have limited access to features linked to OmniPCX 4400network administration.
Reminder:
This group cannot access Alcatel-Lucent OmniVista 4760 Network Management System Security.
12.1.3.7.1 Directory
Access to the application with Total Modification of Company Directory level rights andTotal Modification of Network branches of System Directory level rights. Members can:
- In the System directory:• View, create, edit, or delete all objects of the nmc > networks > subnetworks > PCX
branch• View other objects in the nmc branch
- In the Company directory, view, create, edit, or delete all attributes of all records.
12.1.3.7.2 Configuration
Chapter 12
12-4
Access to the application with Normal level rights and to the PCX with Administrator (0) levelrights. Members can:
- Manage all application features
- View, edit, create, or delete all PCX instances
- View, edit, create, and delete OmniPCX 4400 \ Alcatel-Lucent OmniPCX Enterprise CSobjects and attributes according to the Profile 0 definition (see § Securing Access to theOmniPCX 4400 / OmniPCX Enterprise ).
12.1.3.7.3 Accounting/Traffic
Access to the application with Management level rights. Members can manage alladministration features of the Accounting and Traffic analysis applications.
12.1.3.7.4 Reports
Access to the application with Management level rights. Members can manage all applicationfeatures.
12.1.3.7.5 Alarms
Access to the application with Management level rights. Members can view, acknowledge, ordelete all correlated or uncorrelated alarms.
12.1.3.7.6 Topology
Access to the application with Management level rights. Members can view or modifystandard display and customized displays.
12.1.3.7.7 Scheduler
Access to the application with Management level rights. Members can:
- View, create, or edit all tasks
- Delete only their own tasks
12.1.3.7.8 Maintenance
Access to the application with OmniPCX 4400 maintenance level rights. Members can savePCX data and update OmniPCX 4400 \Alcatel-Lucent OmniPCX Enterprise CS software.
12.1.3.8 “Directory Experts” Group
Members of this group have access to all Alcatel-Lucent OmniVista 4760 NetworkManagement System features linked to Company directory administration.
Reminder:
This group cannot access Alcatel-Lucent OmniVista 4760 Network Management System Security.
12.1.3.8.1 Directory
Access to the application with Total Modification of Company Directory level rights.Members can:
- View all objects in the System directory
- View, create, edit, or delete all attributes of all Company directory records
12-5
12.1.3.8.2 Alarms
Access to the application with Read level rights. Members can view all correlated oruncorrelated alarms.
12.1.3.8.3 Scheduler
Access to the application with Modify level rights. Members can:
- View all tasks
- Create, edit, or delete only their own tasks
12.1.3.8.4 Other Applications
Access to the Configuration, Accounting/Traffic, Reports, Topology, and Maintenanceapplications is prohibited.
12.1.3.9 “Partial View of Green List” Group
Access to the Directory application with Partial view of green list level rights. Members canview:
- All System directory objects
- Non-personal attributes of all green list records in the Company directory.
Reminder:
This group cannot access Alcatel-Lucent OmniVista 4760 Network Management System Security.
12.1.3.10 “Partial View of Orange List” Group
Access to the Directory application with Partial view of orange list level rights. Members canview:
- All System directory objects
- Non-personal attributes of all green or orange list records in the Company directory.
Reminder:
This group cannot access Alcatel-Lucent OmniVista 4760 Network Management System Security.
12.1.3.11 “Partial View of Red List” Group
Access to the Directory application with Partial view of red list level rights. Members canview:
- All System directory objects
- Non-personal attributes of green, orange, or red list records in the Company directory
Reminder:
This group cannot access Alcatel-Lucent OmniVista 4760 Network Management System Security.
12.1.3.12 “Total View of Green List” Group
Access to the Directory application with Total view of green list level rights. Members canview:
- All System directory objects
Chapter 12
12-6
- All attributes of all green list records of the Company directory
Reminder:
This group cannot access Alcatel-Lucent OmniVista 4760 Network Management System Security.
12.1.3.13 “Total View of Orange List” Group
Access to the Directory application with Total view of orange list level rights. Members canview:
- All System directory objects
- All attributes of all green or orange list records in the Company directory
Reminder:
This group cannot access Alcatel-Lucent OmniVista 4760 Network Management System Security.
12.1.3.14 “Total View of Red List” Group
Access to the Directory application with Total view of red list level rights. Members can view:
- All System directory objects
- All attributes of green, orange, or red list records in the Company directory
Reminder:
This group cannot access Alcatel-Lucent OmniVista 4760 Network Management System Security.
12.1.3.15 “Partial Modification of Company Directory” Group
Access to the Directory application with Partial modification of company directory levelrights. Members can:
- View all objects in the System directory
- View, create, edit or delete non-personal attributes of all Company directory records
Reminder:
This group cannot access Alcatel-Lucent OmniVista 4760 Network Management System Security.
12.1.3.16 "Total Modification of Company Directory" Group
Access to the Directory application with Total Modification of company directory levelrights. Members can:
- View all objects in the System directory
- View, create, edit or delete all attributes of all Company directory records
Reminder:
This group cannot access Alcatel-Lucent OmniVista 4760 Network Management System Security.
12.1.3.17 “Directory Security Configuration” Group
Access the Directory application with Directory Security Configuration level rights.Members of this group can access the Audit application
12.1.4 Manager Accounts
12-7
There is one predefined Manager account. This account can be viewed by members of groupswith access to orange list records and can be modified by members of groups with access tothe Directory application with Total Modification of Company Directory level rights.
12.1.4.1 Alcatel 4059
This account is a member of the Partial Modification of Company Directory group. Itspassword must be entered and identical to that entered during A4059 LDAP configuration. Itallows the attendant to access the company directory with Partial modification of CompanyDirectory level rights.
12.1.5 Application Access Rights
The Security application determines access rights for persons or groups . Each applicationhas its own access level.
12.1.5.1 Directory Application
The level rights are:
- No Access: The user is not allowed to start the application.
- Partial view green list: The user can:• view non-personal attributes of green list entries in the Company directory.• view all attributes of all entries in the System directory.
- Total view green list: The user can:• view all attributes of green list entries in the Company directory.• view all attributes of all entries in the System directory.
- Partial view orange list: The user can:• view non-personal attributes of green or orange list entries in the Company directory.• view all attributes of all entries in the System directory.
- Total view orange list: The user can:• view all attributes of green or orange list entries in the Company directory.• view all attributes of all entries in the System directory.
- Partial view red list: The user can:• view non-personal attributes of green, orange, or red list entries in the Company
directory.• view all attributes of all entries in the System directory.
- Total view red list: The user can:• view all attributes of green, orange, or red list entries in the Company directory.• view all attributes of all entries in the System directory.
- Partial modification of Company directory: The user can:• view or modify non-personal attributes of green, orange, or red list entries in the
Company directory.• import for modification or export non-personal attributes of green, orange, or red list
entries in the Company directory.• view all attributes of all entries in the System directory.• export all attributes of all entries in the System directory.
Chapter 12
12-8
- Total modification of Company directory: The user can:• view or modify all attributes of green, orange, or red list entries in the Company
directory.• create, delete, import, or export all green, orange, or red list entries in the Company
directory.• view all attributes of all entries in the System directory.• export all attributes of all entries in the System directory.
- Total modification of all directories: The user can:• view or modify all attributes of all entries in all directories.• create, delete, import, or export all entries in all directories.• secure the application.
12.1.5.2 Configuration Application
The profile levels define the visibility and access to PCX objects and attributes. The level rightsare:
- No Access: The user is not allowed to start the application.
- Normal: The user can perform all management functions of the PCX.
- All: In addition to the Normal rights, the user can define the access profiles for theOmniPCX 4400 \ Alcatel-Lucent OmniPCX Enterprise CS, define security for theapplication.
12.1.5.3 Accounting / Traffic Analysis Application
The access level rights are:
- No Access: The user is not allowed to start the application.
- Read: The user can display the accounting organization, the last accounting records, thetracking data, etc.
- Management: In addition to Read rights, the user can manage all the application features.
- All: In addition to Management rights, the user can define security for the application.
12.1.5.4 Reports Application
The access level rights are:
- No Access: The user is not allowed to start the application.
- Read: The user can view predefined reports, his own definitions, and reports, and generatehis own reports.
- Modify: The user can view, import, and export report definitions and predefined models. Hecan also view, create, edit, delete and generate his own report definitions, models andreports.
- Management: In addition to Modify rights, the user can view, edit, copy, export, and deletedefinitions, and delete the reports of other users.
- All: In addition to Management rights, the user can define security for the application.
12.1.5.5 Alarms Application
12-9
The level rights are:
- No Access: The user is not allowed to start the application.
- Read: The user can display the alarms and events.
- Clear: The user can display events, view and acknowledge correlated alarms, and view,acknowledge, and delete uncorrelated alarms.
- Management: The user can display events, and view, acknowledge, delete, and sign allalarms. The user can also manage the application.
- All: In addition to Management rights, the user can define security for the application.
12.1.5.6 Topology Application
The level rights are:
- No Access: The user is not allowed to start the application.
- Read: The user can display standard and customized views.
- Management: The user can display and modify standard and customized views, and cancreate or delete customized views.
- All: In addition to Management rights, the user can define security for the application.
12.1.5.7 Scheduler Application
The level rights are:
- No Access: The user is not allowed to start the application.
- Read: The user can view scheduled tasks and their reports.
- Modify: In addition to Read rights, the user can create, modify, delete, or execute his owntasks and their reports.
- Advanced modify: In addition to Modify rights, the user can execute tasks owned by otherusers.
- Management: In addition to Advanced modify rights, the user can modify or delete tasksowned by other users.
- All: In addition to Management rights, the user can define security for the application.
12.1.5.8 Maintenance Application
The access rights are:
- No Access: The user is not allowed to start the application.
- OmniPCX 4400 Maintenance: The user can perform maintenance tasks and updatesoftware on the OmniPCX 4400 \ Alcatel-Lucent OmniPCX Enterprise CS.
- All: In addition to OmniPCX 4400 Maintenance rights, the user can perform maintenancetasks on the Alcatel-Lucent OmniVista 4760 Network Management System and definesecurity for the application.
12.1.5.9 Audit Application
Access rights are:
- No Access: The user is not allowed to start the application
Chapter 12
12-10
- Read: The user can display standard and customized views
- All: the user can perform all audit tasks and define security for the application
12.1.5.10 SIP Manager Application
Access rights are:
- No Access: The user is not allowed to start the application
- Read: The user can view all entries from the DM Server
- All: the user can perform all Sip manager tasks and define security for the application
12.1.5.11 External Application
The access rights are:
- No Access: The user is not allowed to start the application.
- Normal: The user can start the application.
- All: The user can start the application and define security for the application.
12.1.6 Managing User Accounts
Accounts in the Administrator group can:
- Create a Manager account
- Create a customized group
- Add a Manager account or company directory entry to a group
- Authorize access to a Manager account or a directory entry or group to an application
12.1.6.1 Password Security Policy
12.1.6.1.1 Overview
As of R4.2, a password policy can be set in order to improve security.
This password policy concerns:
- Password syntax: the system checks that the password does not contain any valueassociated with the user. e.g.: userid, firstname, mail address etc
- Password length: a password must have a minimum number of characters
- Password history: the new password must be different from previous passwords
- Account lock: an account can be locked after a specified number of unsuccessful attempts.When an account is locked, an alarm is generated.
- Password aging: a password has a lifetime and must be changed before its expiration.When a password expires, an alarm is generated.
When the manager defines a password policy, this policy applies to all users.
Note:
This password policy is applicable only for local authentication.
12.1.6.1.2 Policy Configuration
12-11
Configuration of the password policy can be done only by users whose access level is TotalModification of All Directories for the Directory application. By default, adminnmc has theright to view an configure the password policy.
To access the Password Policy window:
1. Select Security in the menu bar
2. Click Password Policy option
Figure 12.1: Password Policy Window — Password Policy Tab
Password policy available options:
- User Password Change• Check Password Syntax: validate the check box to enable verification of password
syntax and enter the password minimum length• Keep Password History: validate the check box to enable password history recording
and enter the minimum number of passwords (excluding current password) that cannotbe successively re-used
• Change Password after First Login or Reset: validate the check box to obligepassword change at the first login or after a password reset by an administrator
- Account Lock• Account Can Be Locked: validate the check box to enable account locking• Number of login attempts permitted: enter the number of incorrect logins accepted
before the account is locked• Unlock by the administrator/Automatic Unlock: select (radio buttons) the account
unlocking process:• Unlock by the administrator: in case of a locked account, the user must contact
the administrator
Chapter 12
12-12
• Automatic Unlock: in case of a locked account, the user must wait for the numberof minutes defined in the Automatic Unlock field
Figure 12.2: Password Policy Window — Aging Password Tab
Aging Password available options:
- Expire Password: validate the check box to enable the aging password feature
- Password Expired (in Days): enter the lifetime of the password
- Password Warning Before (in Days): enter the number of days during which a warningmessage, informing the number of days after which the password gets expired.
- Allow Password Change after (in Days): enter the number of days during which a newpassword cannot be changed
- Expire Regardless of Warning: validate the check box to validate password expiration atthe planned date, whether the user has been warned or not. If this check box is notselected, the password does not expire without a warning to the user
12.1.6.2 Creating a Manager Account
1. Start the Directory application.
2. In the Company tab, expand the Company > Manager branch, then select Manager.
3. In the shortcut menu, select the command Create > Person. A blank record is displayed inthe data area.
4. The Last name and Password attributes must be completed. Check that the User IDattribute automatically takes the value of the Last name. This identifier must be entered inthe User name field when connecting to Alcatel-Lucent OmniVista 4760 NetworkManagement System.
12-13
Note:If you enter the First name attribute, the first letter of this attribute will automatically be placed in theUser ID attribute before the Last name.
5. Complete the other attributes, if required.
6. Confirm the new entry and check that the new account is displayed in the tree structure.
12.1.6.3 Creating a Customized Group
1. Start the Directory application.
2. In the Company tab, expand the Company > Administration > Group branch, thenselect Group.
3. From the shortcut menu, select the command Create > Group. A blank record is displayedin the data area.
4. You must fill in the Name attribute.
5. Complete the other attributes, if required.
6. Confirm the new entry and check that the new group appears in the tree structure.
12.1.6.4 Adding a Manager Account or a Company Directory Entry to a Group
Note 1:
For a Company directory entry, assigning a password is mandatory in order to be able to connect to the
Alcatel-Lucent OmniVista 4760 Network Management System.
1. Start the Directory application.
2. In the Company tab, expand the Alcatel > Administration > Group branch.
3. Select the group to which you want to add the account or directory entry.
4. In the data field, double-click in the Member attribute field, then:• If the Member attribute is empty, left-click the icon.
• If the Member attribute is not empty, select the icon by right-clicking, then select
Add a Value. In the new line displayed, select the icon by left-clicking.
5. In the Edit DN window, select Search > Individuals, In > Company and Where > Lastname, then click the or icon.
6. In the search result, select the desired entry, then click OK.
7. Accept the changes.
Note 2:
An account or a directory entry may belong to several groups and therefore accumulate rights from each
group.
12.1.6.5 Enabling Access of a Manager Account or a Directory Entry or Group to anApplication.
1. Select the desired application from the Security menu.
Chapter 12
12-14
Note:There are two possibilities when granting access rights to an external application (Access rights at-tribute, General tab in the External application entry in the Directory application):
Either use the same access rights as an Alcatel-Lucent OmniVista 4760 Network Management Sys-tem internal application (for example, launching OTUC web management requires access to theCon-figuration application),
or use one of the three external application classes: 1, 2, or 3 (for example, accessing your companyHuman Resources web site requires access to external application class 1).The Access Control Editor window appears.
2. Select Add....
3. In the Add user window:• For a Managers account or a Directory entry, select Search > Individuals, In >
o=Company and Where > Last name, then click the or icon.
• For a group, select Search > Group, In > o=Company and Where > Last name, thenselect the or icon.
4. In the search result, select the desired person or group then select OK.The group or the person is added to the end of the Access Control Editor list.
5. Select the Access Level to the application required for this person or group.
Remark:For the Configuration application, Access Level for the application and access profile for the PCXmust be configured.
6. Click OK to accept the changes.
12.1.7 RADIUS Server
12.1.7.1 Architecture
The Remote Authentication Dial In User Service (RADIUS) server is used with theAlcatel-Lucent OmniVista 4760 Network Management System to integrate the Alcatel-LucentOmniVista 4760 Network Management System to the user architecture, for making the usermanagement easier by centralized authentication. The Alcatel-Lucent OmniVista 4760Network Management System server acts as a RADIUS proxy and forwards all theauthentication requests to the RADIUS server. The Alcatel-Lucent OmniVista 4760 NetworkManagement System does not use the accounting and the access authorization services ofthe RADIUS server.The Alcatel-Lucent OmniVista 4760 Network Management System server allows passwordcentralization through the RADIUS server. The RADIUS server authenticates only theAlcatel-Lucent OmniVista 4760 Network Management System users, and not the Databaseand LDAP administrators.
The user enters the login and password in the Alcatel-Lucent OmniVista 4760 NetworkManagement System client access window. The client sends the authentication request to theAlcatel-Lucent OmniVista 4760 Network Management System server which forwards therequest to the RADIUS servers. Here the Alcatel-Lucent OmniVista 4760 NetworkManagement System server is the Network access server (NAS) and it acts as a RADIUSclient.
12-15
Typical Architectures:
1. RADIUS server directly acknowledges\ rejects the request.
Figure 12.3: RADIUS Server Topology — Example 1
2. RADIUS server acts as a proxy or a gateway to forward the request to the other servers.These servers could be RADIUS servers or any other servers implementing differentprotocols. In this case, the RADIUS server translates and communicates the request/response between the Alcatel-Lucent OmniVista 4760 Network Management System andthe other servers.
Figure 12.4: RADIUS Server Topology — Example 2
Alcatel-Lucent OmniVista 4760 Network Management System server uses the flip-flop policyfor authentication:
Chapter 12
12-16
- Either one or two RADIUS servers are declared. You are recommended to use twoRADIUS servers.
- Alcatel-Lucent OmniVista 4760 Network Management System server invokes a declaredRADIUS server, processes its response and continues to trigger this server until it timesout. When this server is timed out, the Alcatel-Lucent OmniVista 4760 NetworkManagement System server disables this server and calls the other declared RADIUSserver. It will continue to trigger this second server until it times out. Then theAlcatel-Lucent OmniVista 4760 Network Management System server will trigger the firstserver, if it is no more in the disabled state.
- If the configured servers are disabled, the authentication is rejected or proceeded using thelocal password. This has to be defined during the setting of the RADIUS server by theadministrator. Refer § Authentication .
12.1.7.2 Defining RADIUS Server in System Directory
12.1.7.2.1 Configuring a RADIUS Server
To configure a RADIUS server in System Directory:
1. Launch the Directory application.
2. Select the System tab. The system directory tree is displayed.
3. Select the NMC.
4. Select Create> Authentication server from the shortcut menu. The window forconfiguring the RADIUS server is displayed. By default the General tab is selected.
12-17
Figure 12.5: System Directory Window — Configuring RADIUS Server
5. Complete the attributes in the General window.
table 12.1: RADIUS Server: General AttributesAttributes Values
IP Address IP address of the RADIUS server
Description Description of the RADIUS server (optional)
Shared secret Is used for concealing the password and to authenticate the RADIUS serverresponse. This must be entered twice and is valid only when both theentries are equal. The shared secret entered here should be same as theone set in the RADIUS server, for this Alcatel-Lucent OmniVista 4760Network Management System server.
Remote port onauthentication server
UDP port to contact the RADIUS server. By default, it is the standard RFCport 1812.
Local port UDP port used to receive the RADIUS server response (when this value isempty, any available dynamic port is used)
Response Timeout RADIUS server response time out in seconds. (default- 3 seconds)
Chapter 12
12-18
Disable duration Time duration for which the RADIUS server is maintained in the disabledstate. (default- 15 seconds)
6. Select the Miscellaneous tab. In the Miscellaneous window, enter the miscellaneousdata (if any).
7. Click Apply to configure the RADIUS server.
Note:
In Password Policy window, disable all the checkboxes in Password policy tab and in Aging Password
tab.
12.1.7.2.2 Modifying a Radius Server Configuration
To modify a RADIUS server configuration:
1. Launch the Directory application.
2. Select the System tab. The system directory tree is displayed.
3. Select the RADIUS server to be modified, from the system tree.
4. Modify the required attributes in the General & Miscellaneous window. Refer to the table§ RADIUS server: General attributes.
5. Click Apply to accept the changes.
12.1.7.2.3 Deleting a Radius Server
To delete a RADIUS server:
1. Launch the Directory application.
2. Select the System tab. The system directory tree is displayed.
3. Select the RADIUS server to be deleted, from the system tree.
4. Select Delete from the shortcut menu. A confirmation window pops-up.
5. Confirm the deletion. The RADIUS server is deleted.
12.1.7.3 OmniVista 4760 Account Management with RADIUS Server
12.1.7.3.1 User Login
User creation:
Refer to module Directory - Company tab § Creating Entries Manually , for creating a newuser. When the RADIUS authentication is used, the user identifier is used as customer loginand it must be unique. Each Alcatel-Lucent OmniVista 4760 Network Management Systemuser has to be created in the RADIUS server, with the same user identifier as in theAlcatel-Lucent OmniVista 4760 Network Management System. The password is not requiredto be set during the user creation as they are automatically updated during the RADIUSauthentication process.
Caution:
The user identifiers are case sensitive in the RADIUS server. While creating a user, use the same
case for the user identifier in the Alcatel-Lucent OmniVista 4760 Network Management System
and the RADIUS servers.
12-19
Password modification:
When the user password is modified in the RADIUS server, the user should log in to theAlcatel-Lucent OmniVista 4760 Network Management System. This will automatically updatethe password in the LDAP. If the password is not updated in the LDAP, the scheduled jobsmay fail.
12.1.7.3.2 LDAP Connection
When the RADIUS authentication is active, the user is not automatically logged out due to thefactors such as maximum session duration or idle time.
12.1.7.4 Authentication
12.1.7.4.1 Setting the Authentication Mode
To set the authentication mode:
1. Start the Directory application.
2. Select the System tab.
3. Select the Alcatel-Lucent OmniVista 4760 Network Management System from the Systemtree. The Alcatel-Lucent OmniVista 4760 Network Management System window isdisplayed.
Chapter 12
12-20
Figure 12.6: System Directory Window - Setting Authentication Mode
4. In the Authentication mode field, select the type of authentication mode to be set. Localauthentication is selected by default.• Local authentication: Users are authenticated using the password stored in
Alcatel-Lucent OmniVista 4760 Network Management System LDAP directory.• External authentication with local fall-back: The Alcatel-Lucent OmniVista 4760
Network Management System first tries to authenticate the user by calling the RADIUSserver. If the communication with the RADIUS server fails, it tries to authenticate theuser with the password stored in the Alcatel-Lucent OmniVista 4760 NetworkManagement System LDAP directory.
• External authentication only: The Alcatel-Lucent OmniVista 4760 NetworkManagement System authenticates the user by calling the RADIUS server. If thecommunication with the RADIUS fails, the user will not be logged in.
Note 1:As of R4.2, only users who are not belonging to any group or users who are only a member of MaskData Access group will be locally authenticated. All other users are authenticated through RADIUS.
5. Click Apply to set the authentication mode.
12-21
Note 2:
When the user password is changed in the RADIUS server and the user has successfully logged in to the
Alcatel-Lucent OmniVista 4760 Network Management System by RADIUS authentication, the Alcatel-Lu-
cent OmniVista 4760 Network Management System automatically updates the local password.
Caution:
Using the option External authentication is not advised, especially when there is only one RADI-
US server. For trouble shooting when RADIUS server is out of order, refer to the section §
Troubleshooting
12.1.7.4.2 Troubleshooting
RADIUS servers down:The RADIUS server can be down for the following reasons:
a. DirManag tool is not documented.
b. The authentication mode is set to External Authentication, by the administrator.
If the RADIUS server is down when the authentication mode is set to ExternalAuthentication, the Alcatel-Lucent OmniVista 4760 Network Management System cannot beused. If the situation persists for a longer duration, inform the Technical Support .
User login failure:
- The shared secret may be wrong (usually happens after a restoration). It should bere-entered by using the DirManag with LDAP administrator account.
- The Alcatel-Lucent OmniVista 4760 Network Management System server name may notbe in the RADIUS NAS list. Normally when the Alcatel-Lucent OmniVista 4760 NetworkManagement System server is started, it logs the NAS Name and the NAS IP addressused. These values should match the RADIUS server client configuration data, exceptwhen there is another server used as NAS between the Alcatel-Lucent OmniVista 4760Network Management System and the Radius servers. In this case, the public addressgiven by the NAS to the Alcatel-Lucent OmniVista 4760 Network Management Systemmust be used in the RADIUS configuration.
If a specific user login fails, the account may not be defined in the Alcatel-Lucent OmniVista4760 Network Management System (if Alcatel-Lucent OmniVista 4760 Network ManagementSystem Server is the NAS) or there is a specific challenge defined for this account. The log filewill contain the reason for this failure.Login failure can also happen because of characters set (such as Cyrillic alphabet). To avoidsuch internationalization problem logins and passwords are registered in UTF8 format.
Scheduled jobs failure:The jobs scheduled by the Alcatel-Lucent OmniVista 4760 Network Management System user,uses the login and password of the user, to access the Alcatel-Lucent OmniVista 4760Network Management System data. When the password is changed in the RADIUS server andthe user has not logged into the Alcatel-Lucent OmniVista 4760 Network Management Systemafter changing the password in the RADIUS server, the password is not updated in theAlcatel-Lucent OmniVista 4760 Network Management System. Hence the scheduled jobs arenot executed. To refresh the password, the user should reconnect to the Alcatel-LucentOmniVista 4760 Network Management System.
12.1.8 Special Operations
Chapter 12
12-22
12.1.8.1 Generating an Unmasked Report.
To ensure the confidentiality of the accounting report content (numbers called, duration, PINcode, etc.), the data is masked.
To configure called number masking:
1. For each entry in the organization, check its masking profile,
2. Then depending on report generation mode (standard or "unmasked"), apply:• in standard (normal) mode, masking of the 4 final digits.• in "unmasked" mode, masking of the 2 final digits.
Information on how to manage the default profile or a profile specific to part of the organizationis given in module Accounting - Organization tab § Unmasking Report Data .
Caution:
Entries that are not displayed in the organization are linked with the default profile (for example:
station groups
To access "unmasked" mode, when generating reports, call the individuals whose login isrequired to unmask the data.Unmasking is thus not a right to be granted to each user who wants to access unmasked data.The administrator configuring the Alcatel-Lucent OmniVista 4760 Network ManagementSystem must firstly decide with the customer which individuals need access to masked dataand, secondly, add such individuals to the Access masked data group.
To generate an unmasked report:
1. Select the desired definition from one of your personal folders.
2. Select Generate report w/o mask from the shortcut menu. The passwords of all themembers of the Access masked data group must be entered.
3. Enter any filter values during generation, then confirm. A timer (presenting generation dateand time) is displayed below the definition.
When generation is complete:
- The timer is replaced by the colored Report icon:• Blue: report generation completed successfully.• Red: there was an error while generating.
Note:The icon representing the report has a struck out mask symbol attached.
- Generation time is displayed in the Properties tab.
The "unmasked" reports remain available on the server and only the administrators andcreators of these reports can view them. To ensure confidentiality, these users must lock theirworkstations when they are away and remember to delete these reports.
12.1.8.2 Restricting Access to Organization Data
Each time Accounting is started, user rights are checked. There are startup, read-only, andwrite rights.
- No startup rights: the user cannot start Accounting.
12-23
- Read-only rights: full display of the organization. The user can open the tree and viewproperties, recent records, tracking counters, etc.
- Write rights: all accounting features are authorized (create company, assign profiles,delete, etc.).
To round out these access rights, local levels and a cost center can be assigned to a viewing(scope) domain open to selected users.
12.1.8.2.1 Scope (view/display rights)
Scope affects the display of the organization and report generation.Viewing restrictions are set when Accounting is started. User viewing rights are read whenthe organization tree structure is opened. The user can only view data for levels and costcenters for which he has domain viewing rights.
Figure 12.7: Domain Viewing Rights
In the Reports application, when a report is manually or automatically generated, the owner isidentified and his domain viewing rights are checked. Data extracted from the database isscreened according to viewing rights.
12.1.8.2.2 Operation
To access visibility domain management, the visibility domain must first be enabled in theSystem directory.
Perform these steps:
1. In the System directory, enable the option Nmc > NmcConfiguration > GlobalPreferences>Accounting > AccountingParameters > Visibility domain. The organization is then maskedin the NMC root. To interrupt access control and restrictions, deselect this option.
2. Open the Accounting application, click the Organization tab and, in Properties, enter theDomain name attribute (for example: Red).
3. Close the Accounting application.
4. In the company directory, complete the view/display domain for each accounting user(users or groups): Visibility domain for accounting attribute (for the administrator,configure the same Visibility domain for accounting attribute as that entered in theAccounting root).
5. Open the Accounting application and organization tree structure again.
6. Classify the different parts of the organization tree structure in the Accounting application
Chapter 12
12-24
by specifying a domain name for local levels and cost centers: Domain name attribute. Itis not necessary to apply a domain to each level as objects with no domain inherit onefrom their parent.
12.1.8.3 Managing Confidentiality Lists in the Company Directory
The confidentiality lists are used to restrict viewing of and access to individual entries in theCompany directory. There are three lists: green, orange, and red.
Access to entries assigned to these lists is granted to members of the partial / total view ofgreen / orange / red list groups (see § Access Groups ). For example, a member of the Totalview green list can access Company entries on the green list.
To put an individual who is already declared in the Company directory on the green, orange,or red list, edit the Confidentiality attribute on the Company tab (see module Directory -Company tab § Confidential List ). Individuals are on the green list by default.
12.1.9 Securing Access to the OmniPCX 4400 / OmniPCX Enterprise
12.1.9.1 Overview
By default, the Omnivista 4760 application allows all users, whatever their login or PC, tomanage all PCX objects. Access security to the PCX can operate at several different levels:
- SSH/SFTP Protocol: Available starting with Alcatel-Lucent OmniPCX Enterprise CSversion 6.0. This security does not concern the graphical configuration application. TheSSH and the SFTP protocols are used by the Alcatel-Lucent OmniVista 4760 NetworkManagement System server and the client to have secured access to the PCX, instead ofthe Telnet and FTP.
- Access profile: Limits access to one or more PCX object/attribute type. This restriction islocal to the Alcatel-Lucent OmniVista 4760 Network Management System. Think of anaccess profile as a set of management functions. You create the set by selecting objectsand/or attributes which can be viewed and/or modified on the PCX. For example, you candefine a profile for User management, Hardware management, or Expert management.Eleven profiles are available for customization. You can not use this feature to applyrestrictions to a set of PCXs or a set of instances on the PCX.
- Access control by station and login: Limits remote access to the PCX.For each PCX, it is possible to validate the CMISE security (
)The CMISE security restricts PCX management to authorized management stations(Alcatel-Lucent OmniVista 4760 Network Management System).The CMISE security also restricts PCX management to authorized users. Users areidentified with their login. Logins, used by users to open a Alcatel-Lucent OmniVista 4760Network Management System client session, are transmitted to the PCX and checked. Inaddition, a password per PCX (identical for all logins) may be configured.The CMISE security is configured on both the PCX and the Alcatel-Lucent OmniVista 4760Network Management System server (see: § Stations and Users ).
Note:The Alcatel-Lucent OmniVista 4760 Network Management System application connects to the PCXvia its server interface, so it is not possible to authorize or not authorize a specific client station.
- Domain management: Limits access to a set of PCX instances. The previous accesscontrol must be activated. A management domain is a set of PCX instances, for exampleusers and groups of a specific service, identified by a domain number (from 0 to 255,
12-25
inclusive). Authorized logins are then assigned management rights to a domain.
12.1.9.2 SSH
SSH (Secure Shell) is a secure protocol that allows a client to open a session on a server tosend commands or files in secure manner (secure Telnet). See secure connection in moduleDirectory - System tab § Declaring a PCX .
A license is required to use SSH protocol.
12.1.9.3 Managing Access Profiles
This feature allows eleven access levels for PCX objects and attributes to be defined for usersof the Configuration application. Because access profiles are defined globally for the PCX, itis better to work with the PCX running the highest release in order to include the greatestnumber of attributes and objects.
1. Run the Configuration application.
2. Connect to a PCX (Alcatel-Lucent OmniPCX Enterprise CS or OmniPCX 4400).
3. In the Configuration menu, select the Access Profiles command.
4. When loading is complete, the Security window is displayed.
Figure 12.8: Security Window
5. Use the following commands to perform the desired operations:• In the Edit menu, select Search to select the desired object.• To modify object access rights, click the cell corresponding to the object and level that
you want to modify. In the drop-down menu displayed in the cell, select access right:None: the object is not displayed in the tree structure.Read: Object instances can be edited but cannot be modified.Read/Write: Object instances can be edited and modified but cannot be created ordeleted.All: Object instances can be created, edited, modified, and deleted.
6. To configure access rights for selected object instance attributes, double-click the icon,
Chapter 12
12-26
the Class “X” access profile window is displayed.
Figure 12.9: Class “X” Access Profile Window
7. Select or deselect the corresponding box for an attribute to be displayed or hidden at agiven level. When available (depending on the object), the Actions tab gives access to thepossible actions. Select or deselect the actions to be executable or not.
8. Click Close to return to the Security window.
9. Click OK to save your changes.
Caution 1:
If a user profile is modified, you must delete the MIB saved locally on the client PC, using the
menu Configuration > Object model save, in order to save a new loading of the MIB.
Caution 2:
In every new PCX release, new objects and attributes can be defined in the MIB. When updating
the PCX release, remember to update access profiles to hide these new objects and attributes.
By default:
- the Administrator (0) profile gives access to all objects, all attributes, and all actions.
- the Advanced (1) profile restricts access to expert management objects. It is defined in thePCX but can be customized in the Alcatel-Lucent OmniVista 4760 Network ManagementSystem.
- the User (2) profile restricts access to usual management objects. It is defined in the PCXbut can be customized in the Alcatel-Lucent OmniVista 4760 Network ManagementSystem.
- the User Manager (3) profile restricts access to user management objects. It is defined inthe PCX but can be customized in the Alcatel-Lucent OmniVista 4760 NetworkManagement System.
12-27
- the Profile 10 is specially designed for an attendant management task, restricting access tousual attributes for users, hunt groups, and speed dialing numbers. The SimplifiedConfiguration group is assigned Profile 10 as level rights to the Configuration application.
12.1.9.4 Managing Access Control on OmniPCX 4400 \ Alcatel-Lucent OmniPCXEnterprise CS
You may perform the following procedures using mgr or the Alcatel-Lucent OmniVista 4760Network Management System Configuration application. Some data will have to be copied inthe OmniVista 4760 directory.
To launch the configuration procedure on the Alcatel-Lucent OmniVista 4760 NetworkManagement System:
1. Run the Configuration application.
2. Select a PCX (Alcatel-Lucent OmniPCX Enterprise CS or OmniPCX 4400).
3. Right click on the PCX name and select "Configure"
12.1.9.4.1 Grouping PCX Instances
Distribute by domain (0 to 255) the PCX instances for the following objects:
- users,
- hunt groups,
- data terminals,
- the numbering plan.
Note:By default, all the instances are in domain 0.
12.1.9.4.2 Stations and Users
In the Security and access control menu, the entries: User, Station and access control list areinitialized with the character *. In this way all logins and all machines having an Alcatelconfiguration application can connect. Remove the * character, and then manage the users,the user list and the stations.
Managing users
You must use this procedure to manage the Alcatel-Lucent OmniVista 4760 NetworkManagement System logins allowed to access the PCX for management operations.
1. Launch the Configuration application
2. Select Security and Access Control\User Access Control.
3. Create a user and enter values for the following fields:• User name: Authorized login (maximum of 20 characters). This login must be declared
as a manager account or a company entry, with a password, in the Alcatel-LucentOmniVista 4760 Network Management System Directory application (see § ManagingLogin ). The Alcatel-Lucent OmniVista 4760 Network Management System connectionmodule checks the validity of the login and password.
• Management by use authorized: (yes/no), authorises the security accessmanagement
• User validity: (yes/no), can be used to block temporarily the user access
Chapter 12
12-28
• Click to validate.
Managing Access Rights
For each user, create an object Rights User Access Control per management domainassigned to a user:
1. Launch the Configuration application
2. Select Security and Access Control>User Access Control> Rights User AccessControl
3. Create an object and enter values for the following fields:• User name: enter the name of the user• User name: (yes/no), authorizes (or not) security access management• Domain Identifier: (yes/no), can be used to block user access temporarily• User Rights in Domain: select the rights of the user:
• Any Rights: the user has no right on objects of the domain• Read-Only Privileges: the user can only read objects of the domain• Read/Write Privileges: the user can read, create or modify objects of the domain• All Rights: the user can read, create, modify or suppress objects of the domain
• Click to validate.
Managing Lists
The list groups several users authorized to perform PCX management tasks from anauthorized station.
1. Launch the configuration procedure.
2. Select Security and Access Control\ List Access Control.
3. Create a list and enter values for the following fields:• List index: 1 to 8• Broadcast list: define if the list is to be broadcast• User name: enter the user name
4. Click to validade.
Managing Stations
These are management stations (for example the Alcatel-Lucent OmniVista 4760 NetworkManagement System server) allowed remote access to the PCX to perform managementtasks.
1. Launch the configuration procedure.
2. Select Security and Access Control\ Station Access Control .
3. Create a station and enter values for the following fields:• Station Name: OmniVista server name• Secret station code :(optional): this secret code must also be copied in the OmniVista
application (see § Managing CMISE Security ).• User list: the number of the user list used for connecting to the station.
12-29
4. Click to validate.
Note:
: Passwords and station names are written in CAPITAL LETTERS.
12.1.9.5 Managing Alcatel-Lucent OmniVista 4760 Network Management System
12.1.9.5.1 Managing Login
The users declared in § Managing users must be declared in the Company directory. TheUser ID must be identical to the names registered in the PCX. These users must be assigneda password to connect to the Alcatel-Lucent OmniVista 4760 Network Management System,and must be assigned Normal level rights for the Configuration application, either directly orby being added to an appropriate access group. The access profile will determine the accessto PCX objects and attributes.
12.1.9.5.2 Managing CMISE Security
The security CMISE allows the PCX to check the real identity of the remote managementstation with the help of a password.
If the PCX asks for a secret code from theAlcatel-Lucent OmniVista 4760 NetworkManagement System server, CMISE security has to be configured.To configure CMISEsecurity:
1. Run the Directory application.
2. Select the PCX in the system directory.
3. Open the Connectivity tab.• Check the attributeSecure Access for configuration• Enter the password registered for the management station in the PCX into the CMISD
Password field
4. Click to validate.
12.1.10 Securing Access to the Alcatel-Lucent OmniVista 4760 NetworkManagement System
12.1.10.1 IP Sec
IP sec allows IP calls between the Alcatel-Lucent OmniVista 4760 Network ManagementSystem client and Alcatel-Lucent OmniVista 4760 Network Management System server to besecured. An IP sec strategy must be set up in Windows. Please consult your installationtechnician for more information.
12.1.10.2 IP Ports Used for Alcatel-Lucent OmniVista 4760 Network ManagementSystem
Please consult your installation technician for more information.
12.1.10.3 User Account Simultaneous Sessions
Until R4.2, a user account can be used for simultaneous sessions.
Chapter 12
12-30
As of R5.0, it is possible to configure:
- Accounts which may be used in several simultaneous sessions
- Accounts which may be used in one single session at a given time
Note 1:
Accounts, belonging to the administrator group, can open simultaneous sessions.
To configure accounts:
- In the Directory application, select the System tab
- Select your server (SYS005 in the example below)
- In the server property window, validate the Limit User(s) to Single Login checkbox tolimit accounts to a single session at a given time
Figure 12.10: Example of Single Login Configuration
Note 2:Only user with system directory modification access rights can enable or disable the Limit User(s) toSingle Login checkbox.
12-31
Chapter 12
12-32
![contenthub.bvsd.org Course... · Web viewDRAFT. DRAFT. DRAFT. DRAFT. DRAFT. DRAFT. DRAFT. DRAFT. DRAFT. DRAFT. DRAFT. DRAFT. 12/28/2015BVSD Curriculum Essentials32 [Course Name]](https://static.documents.pub/doc/80x56/5e38c5b23f41ba01b81b757e/course-web-view-draft-draft-draft-draft-draft-draft-draft-draft-draft.jpg)
![UvA-DARE (Digital Academic Repository) The VLT-FLAMES ... · arxiv:1704.07131v1 [astro-ph.sr] 24 apr 2017 draft -- draft -- draft -- draft -- draft -- draft -- draft -- draft -- draft](https://static.documents.pub/doc/80x56/60d2c5874625856f4e3584f8/uva-dare-digital-academic-repository-the-vlt-flames-arxiv170407131v1-astro-phsr.jpg)
