TG0095en-Ed03 OmniVista 8770 Troubleshooting Guide

Troubleshooting Guide OmniVista 8770
TGOO95 ed.03 Release 3 and above
OmniVista 8770 Troubleshooting Guide
This document provides the methodology to investigate on Omnivista 8770 issues. Several subjects about accounting,
performance, Security Access, licensing, alarms and SNMP are mentioned here to help integrator working on bad behavior
of the server. This procedure must be applied by OmniVista 8770 experts It is essantial stage prior to any help request made
to ALE Technical Support.
Revision History
Edition 1: January 30, 2019 creation of the document
Edition 2: November 18, 2019 update
Edition 3: November 17, 2021 update
Legal notice:
www.al-enterprise.com The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE. To view other
trademarks used by affiliated companies of ALE Holding, visit: www.al-enterprise.com/en/legal/trademarks-copyright. All other
trademarks are the property of their respective owners. The information presented is subject to change without notice. Neither
ALE Holding nor any of its affiliates assumes any responsibility for inaccuracies contained herein.
© Copyright 2021 ALE International, ALE USA Inc. All rights reserved in all countries.
Table of contents
1. GENERAL OBSERVATIONS ................................................................................................................... 9
1.1. Methodology ................................................................................................................................ 9
1.2. Escalade to Technical Support : ..................................................................................................... 9
1.3. Issues linked to PC, Server, IT environment and application: ......................................................... 10
2. INSTALLATION RECOMMENDATIONS ................................................................................................. 11
2.1. Complying with the installation prerequisites ................................................................................ 11
2.2. Storing the installation data ......................................................................................................... 11
2.3. Initial management and backup ................................................................................................... 11
2.4. Checking the installation ............................................................................................................. 11
2.5. Saving the OmniVista 8770 elements ........................................................................................... 11
3. CHECKING THE INSTALLATION.......................................................................................................... 12
3.1. Principle ..................................................................................................................................... 12

3.2. OmniVista 8770 server services ................................................................................................... 12
3.2.1. OmniVista 8770 Service Manager tool ................................................................................... 12
3.2.2. List of services ..................................................................................................................... 13
3.2.3. Dependency and control of the services ................................................................................ 14
3.3. Launch 8770 client and access to the applications ........................................................................ 15
3.4. Status of the scheduled tasks ...................................................................................................... 16
3.5. Server operation ......................................................................................................................... 16
3.5.1. Configuration ....................................................................................................................... 16
3.5.2. Alarms................................................................................................................................. 16
3.5.3. Event .................................................................................................................................. 16
3.5.4. Topology ............................................................................................................................. 17
3.5.5. Directory (OmniPCX Enterprise/Entreprise) ............................................................................ 17
3.5.6. Accounting .......................................................................................................................... 17
3.5.7. Traffic analysis (OmniPCX Enterprise/Enterprise) ................................................................... 17
3.5.8. VoIP .................................................................................................................................... 18
3.5.9. Export, Print the reports ....................................................................................................... 18
3.5.10. Maintenance ..................................................................................................................... 18
3.6. Check the license ........................................................................................................................ 19
4. FAILURE ANALYSIS ........................................................................................................................... 20
4.1. Analysis by stage ........................................................................................................................ 21

4.2. Analysis on the PCX .................................................................................................................... 22
4.3. Analysis of the client environment ............................................................................................... 22
4.4. Analysis by history ...................................................................................................................... 23
4.5. Analysis of the internal functions of the server ............................................................................. 24
4.6. Analysis of the different logs ....................................................................................................... 24
4.7. Reproduction of the problem ....................................................................................................... 25
OmniVista 8770 - Release 3 and above

OmniVista 8770 Troubleshooting Guide TGOO95 ed.03
© Copyright 2021 ALE International, ALE USA Inc. page 2/236
4.8. Search for a possible workaround ................................................................................................ 25
4.9. Searching if problem known ........................................................................................................ 25
5. COLLECTING DATA AND LOG ............................................................................................................. 27
5.1. 8770 diagnostic description ......................................................................................................... 27
5.2. 8770 Diagnostic steps ................................................................................................................. 29
5.3. Diagnostic result ......................................................................................................................... 29
5.4. 8770 Client log ........................................................................................................................... 30
5.4.1. Application state .................................................................................................................. 30
5.4.2. Java exception ..................................................................................................................... 30
5.4.3. 8770 Client directory ............................................................................................................ 31
5.4.4. Runnmc.bat file ................................................................................................................... 31
5.4.5. Activating the console and java process trace ........................................................................ 31
5.4.6. Modifying log options ........................................................................................................... 32
5.5. PCX OmniPCX Enterprise data import log ..................................................................................... 33
5.6. Directory Web client log ( PHP logs ) ........................................................................................... 33
5.7. Scheduled tasks log .................................................................................................................... 33
5.8. Server log .................................................................................................................................. 34
5.8.1. Log file lists ......................................................................................................................... 34
5.8.2. Setting up extended traces ................................................................................................... 36
5.9. LDAP database log ...................................................................................................................... 37
5.10. LDAP Plugin log ....................................................................................................................... 40
5.11. Installation log ........................................................................................................................ 42
5.11.1. Default Installation trace ................................................................................................... 42
5.11.2. Installation rollback........................................................................................................... 43
6. TROUBLESHOOTING THE OMNIVISTA SERVICES ................................................................................ 44
6.1. NMC Server ................................................................................................................................ 44
6.2. Basic server repair ...................................................................................................................... 45
6.3. Oracle Directory Server ( LDAP Server ) ....................................................................................... 45
6.3.1. Oracle Directory Server not running ...................................................................................... 45
6.3.2. Oracle Directory Server fails to restart ................................................................................... 45
6.3.3. Oracle Directory Server fails to recover its configuration ......................................................... 45
6.3.4. Oracle Directory Server fails to read its dse.ldif configuration file ............................................ 45
6.4. SQL server ................................................................................................................................. 47
6.4.1. Generic log .......................................................................................................................... 47
6.4.2. Enable Mariadb queries log ................................................................................................... 47
6.4.3. Enable ODBC Mariadb log ..................................................................................................... 47
6.5. Apache server ............................................................................................................................ 52
6.6. Wildfly server ............................................................................................................................. 53
7. ACCOUNTING ................................................................................................................................... 54
7.1. Accounting at the PCX end .......................................................................................................... 54
7.1.1. OmniPCX Enterprise ............................................................................................................. 54
7.1.2. OXO .................................................................................................................................... 58

7.2. Data Loading .............................................................................................................................. 60
7.2.1. OomniPCX Enterprise ........................................................................................................... 60
7.2.2. OXO .................................................................................................................................... 62
7.3. Loading to the base .................................................................................................................... 62
7.3.1. OmniPCX Enterprise ............................................................................................................. 62
7.3.2. Assigning the tickets ............................................................................................................ 64
7.3.3. Cost calculation on loading the tickets in the base .................................................................. 66
7.3.4. Recalculating the costs ......................................................................................................... 68
7.4. Data totaling .............................................................................................................................. 69
7.5. Loading to the base .................................................................................................................... 73
7.6. Description of some special cases and solutions............................................................................ 73
7.7. Summary of the main investigation stages ................................................................................... 75
8. TRAFFIC OBSERVATION .................................................................................................................... 76
8.1. Traffic observation on the pcx side .............................................................................................. 76
8.2. Data download by omnivista 8770 ............................................................................................... 77
8.3. Traffic observation on the pcx side .............................................................................................. 78
8.4. The Log File ............................................................................................................................... 79
8.5. Main SQL tables .......................................................................................................................... 80
8.6. The data totaling ........................................................................................................................ 80
8.7. The Report generation ................................................................................................................ 82
8.8. The troubleshooting .................................................................................................................... 85
8.8.1. The summary of the main investigation stages ...................................................................... 85
8.8.2. Randomly, there are some holes (no value present) in the statistic reports .............................. 86
9. TRAFFIC PERFORMANCE COMPARISON .............................................................................................. 89

9.1. Introduction ............................................................................................................................... 89
9.2. Principe of Traffic performance operation in OmniPCX enterprise ................................................... 89
9.3. Differences between traffic performance and accounting operation in OmniPCX Enterprise ............. 89
9.3.1. Example N°1 ....................................................................................................................... 89
9.3.2. Example N°2 ....................................................................................................................... 90
9.3.3. Example N°3 ....................................................................................................................... 90
9.4. Conclusion ................................................................................................................................. 91
10. DISK QUOTA EXCEEDED: SERVER STOPPING .................................................................................. 92
10.1 Presentation............................................................................................................................ 92
10.2 8770 logs ................................................................................................................................ 93
10.3 Check current control .............................................................................................................. 93
10.4 Solution .................................................................................................................................. 95
10.4.1. Clear unnecessary files ...................................................................................................... 96
10.4.2. Decrease disk control ........................................................................................................ 96
10.4.3. Move 8770 files to another drive ........................................................................................ 96
10.4.4. Moving SQL Server database ............................................................................................. 96
10.4.5. Moving backup and temp files ......................................................................................... 100
11. REPORT ...................................................................................................................................... 103

11.1 Export format ........................................................................................................................ 103
11.1.1 TXT Report ........................................................................................................................ 103
11.1.2 PDF Report ........................................................................................................................ 103
11.1.3 EXCEL Report .................................................................................................................... 104
11.2 Scheduled export .................................................................................................................. 105
11.2.1 Options ............................................................................................................................. 105
11.2.2 Scheduled Export as file to a printer .................................................................................... 105
11.2.3 Scheduled Export as file (network drive).............................................................................. 106
11.2.4 Scheduled Export as file to an email server .......................................................................... 109
11.3 Configuring ........................................................................................................................... 110
11.3.1 Configuration report size limits ............................................................................................... 110
11.3.2 Date Options ..................................................................................................................... 111
11.3.3 Scheduled export as email .................................................................................................. 111
11.3.4 Export parameter ............................................................................................................... 112
11.4 Purge ................................................................................................................................... 112
11.5 Limitation ............................................................................................................................. 114
11.5.1 Data comparison ................................................................................................................ 114
11.5.2 Filter limitation ................................................................................................................... 114
11.5.3 Scheduled export ............................................................................................................... 114
11.6 Troubleshooting .................................................................................................................... 115
12. SNMP .......................................................................................................................................... 116

12.1. Opentouch and 8770 configuration ......................................................................................... 116
12.1.1 Opentouch......................................................................................................................... 116
12.1.2 Omnivista .......................................................................................................................... 116
12.2. Checking and test .................................................................................................................. 117
12.2.1 Check the configuration file ................................................................................................ 117
12.2.2 Check the SNMP services .................................................................................................... 118
12.2.3 Sending an alarm ............................................................................................................... 118
12.2.4 Logs .................................................................................................................................. 119
12.2.5 Error cases ........................................................................................................................ 120
12.2.6 Wireshark traces at Omnivista 8770 side ............................................................................. 120
12.2.7 Logs .................................................................................................................................. 121
12.2.8 Display in the Alarm application .......................................................................................... 121
12.3. SNMP Proxy investigation ....................................................................................................... 122
12.3.1 Enabling of Agent snmp logs .............................................................................................. 122
12.3.2 Wireshark traces ................................................................................................................ 122
13. LICENSE ...................................................................................................................................... 124
13.1. Overview .............................................................................................................................. 124

13.2. Content of the license file ...................................................................................................... 125
13.2.1 Omnivista Version key ........................................................................................................ 125
13.2.2 Redundancy, signature, ValidityDays and ExpirationDate keys .............................................. 125
13.2.3 Keys based on server-locking .............................................................................................. 125
13.2.4 Keys based PCx Management ............................................................................................. 126

13.2.5 Modules ............................................................................................................................ 126
13.3. Checking the license .............................................................................................................. 129
13.3.1 Restriced mode .................................................................................................................. 129
13.3.2 Presence of the file ............................................................................................................ 129
13.3.3 Presence of attachment PCX ............................................................................................... 129
13.4. Global synchronization ........................................................................................................... 130
13.5. Number of users ................................................................................................................... 131
13.6. Use of the same license on two Omnivista 8770 servers .......................................................... 132
13.7. Modifying the licenses ........................................................................................................... 136
13.7.1 Changing manually the licenses .......................................................................................... 136
13.7.2 Modifying the capacity / Adding a module ........................................................................... 136
13.7.3 Changing the CPU .............................................................................................................. 136
13.7.4 Migrating the Omnivista 8770 version .................................................................................. 136
13.7.5 Changing the 8770 server, hostname or Windows Operating system ..................................... 137
13.8. Software locks on OmniPcx Enterprise .................................................................................... 137
13.9. Example of current issues ...................................................................................................... 138
14. SECURITY ACCESS ....................................................................................................................... 141

14.1. Purpose ................................................................................................................................ 141
14.2. Object used on OXE side........................................................................................................ 141
14.3. Object used on OXE side........................................................................................................ 142
14.4. Configuration step by step ..................................................................................................... 142
14.5 Security access reinitialization ................................................................................................ 146
14.6 Troubleshooting .................................................................................................................... 147
14.6.1 Authentication Failure ........................................................................................................ 147
14.6.2 Traces OmniPCX Enterprise ................................................................................................ 147
14.6.3 Traces 8770....................................................................................................................... 148
14.7 OmniPCX Enterprise Domain .................................................................................................. 149
14.7.1 Rights & domain ................................................................................................................ 149
14.7.2 Domain in the object .......................................................................................................... 150
15. INTERWORKING ON A VPN / NAT NETWORK ................................................................................ 151

15.1. Overview .............................................................................................................................. 151
15.2. IP Flow ................................................................................................................................. 152
15.3. Specific settings .................................................................................................................... 152
15.3.1. Host file configuration ..................................................................................................... 152
15.3.2. Client modification .......................................................................................................... 152
15.3.3. Firewall setting ............................................................................................................... 153
15.4. Specific settings .................................................................................................................... 154
15.4.1. Alarm error message when port 30500 not available ......................................................... 154
15.4.2. Alarm error message when port 30500 not available ......................................................... 154
15.5. Firewall ................................................................................................................................. 154
16. RTU ............................................................................................................................................ 156

16.1. Overview .............................................................................................................................. 156

16.2. Checking steps ...................................................................................................................... 156
16.3. Known cases ......................................................................................................................... 160
17. Manage MyPhone ......................................................................................................................... 161
17.1. Overview .............................................................................................................................. 161
17.2. Configuration ........................................................................................................................ 161
17.3. How it works ......................................................................................................................... 162
17.4. Logs ..................................................................................................................................... 162
18. Web Based Management .............................................................................................................. 163
18.1 8770 WBM for OXE Configuration : How to clear the OXE MIBs from browsers .......................... 163
19. Web Based Management Performance .......................................................................................... 166
19.1 Overview .............................................................................................................................. 166

19.2 License prerequisites ............................................................................................................. 166
19.3 Configuration ........................................................................................................................ 166
19.4 The log file ........................................................................................................................... 168
19.5 The troubleshooting .............................................................................................................. 168
20. Authenticated certificate deployment ............................................................................................. 172
20.1 Overview .............................................................................................................................. 172

20.2 tools ..................................................................................................................................... 172
20.3 The log files : ........................................................................................................................ 172
21. MSAD Plugin ................................................................................................................................ 173
21.1. Known issues ........................................................................................................................ 173

18.1.1 “Internal error” or “licence failure” message ........................................................................ 173
22. INTERNAL ALARMS LIST .............................................................................................................. 174

22.1. Presentation.......................................................................................................................... 174
22.2. Range ID .............................................................................................................................. 175
22.3. Event .................................................................................................................................... 176
22.4. Cause ................................................................................................................................... 177
22.5. Alarm Server ......................................................................................................................... 179
22.6. Communication Server ........................................................................................................... 180
22.7. License Manager ................................................................................................................... 184
22.8. Service Manager.................................................................................................................... 189
22.9. Scheduler ............................................................................................................................. 192
22.10. SyncLdapPbx......................................................................................................................... 193
22.11. Load accouting ...................................................................................................................... 196
22.12. CMISE .................................................................................................................................. 199
22.13. GCS ...................................................................................................................................... 201
22.14. Load Past Time Performance .................................................................................................. 203
22.15. Alarm Trigger ........................................................................................................................ 206
22.16. Ldap Directory Server ( plugins module ) ................................................................................ 207

22.17. Voice tickets load (OXE/OXO ) ................................................................................................ 208
22.18. Collector module for the SyncLdapPbx Server ......................................................................... 209
22.19. SaveRestore .......................................................................................................................... 209
22.20. Radius .................................................................................................................................. 210
22.21. Password Policy..................................................................................................................... 211
22.22. Audit Server .......................................................................................................................... 212
22.23. Device Management Server.................................................................................................... 213
22.24. Unified User Management ( UUM ) ......................................................................................... 215
22.25. ICE Configuration ( OpenTouch ) ........................................................................................... 216
22.26. RTU ...................................................................................................................................... 216
APPENDIX ........................................................................................................................................... 217
23. APPENDIX 1 : SYNOPTIC OF ACCOUNTING OPERATIONS .............................................................. 217
24. APPENDIX 2 : DESCRIPTION OF OmniPCX Enterprise TICKET FIELDS ............................................. 219
25. APPENDIX 3: EXAMPLE OF TRACE OF COST RECALCULATION ........................................................ 223

26. APPENDIX 4: OPERATIONS BLOCK DIAGRAM ................................................................................ 227
27. APPENDIX 5: DESCRIPTION OF SQL TABLES ................................................................................. 229
28. APPENDIX 6: WEBRTC GATEWAY – TRAFFIC OBSERVATION .......................................................... 233

1. GENERAL OBSERVATIONS
1.1. Methodology
Before reporting a problem to the Ale Technical Support, make sure you have:
• the documents necessary for the setup and the complete management of a functionality,
• complied with the recommendations regarding implementation,
• completed the operation checkpoint,
• used the fault analysis methods described in this document,
• employed the specific troubleshooting paragraph in next chapters.
1.2. Escalade to Technical Support :

By accessing to the Business Partner Web site you can create a service request with type = Technical
Support, product = OmniVista 8770
Provide a clear summary indicating:
• The OmniVista 8770 version and the patches installed accessible by help menu:
• The impacted main module,

• The description of the defect. Screen copy are appreciated.
Add the following information:
• The PCX version managed,
• The date when the problem was raised (to locate the error in the log files),
• Add the “TS” zipped file produced by 8770 diagnostic tool available in windows Menu :

•
• The results of additional test done around the functionality: success and/or failure,
• Server accessibility by remote.
1.3. Issues linked to PC, Server, IT environment and application:
OmniVista 8770 is installed on a Windows system which, by architecture, supports

• Internal hardware (driver),
• Microsoft Windows relative service and function,
• A large set of external software,
• Vmware Server.
You may experience issue that not only impacts OmniVista 8770 but the Server operation itself. Hence
it is essential that you ensure the integrity of the Server and these external applications. You need to
check:
• Status of the disk, and RAM,
• Application errors posted in the Windows Events journal,
• Status of the software installed (the log of these applications).
In the first instance, you should contact the specific support for the Server or these applications.
You may experience issue that seems to affect only OmniVista 8770. This quick analysis can be done
by customer who has dedicated the Server to 8770 usage and is testing Server operation or External
software by activating 8770 software. Ale doesn’t support any server and any external software support.
Anyway we can provide some guiding rule for issue analysis.
First for installation and operation, 8770 rely on basic windows operation, command and service
• Command line like cmd, net,netsh should be allowed
• All IP port used by 8770 should be free and not use by another service. See Security guide
documentation.
Due to client server architecture
• Firewall must be stopped during installation (except windows firewall which is automatically
stopped and restarted during installation)
• Firewall policy should allow 8770 IP flow. See Security guide.
• Antivirus should not prevent 8770 to send mail notification (alarm forwarding or report)

2. INSTALLATION RECOMMENDATIONS
2.1. Complying with the installation prerequisites

The installation procedure guide for the OmniVista 8770 server specifies prerequisites concerning:
• The Server hardware,
• The vmware environment,
• The Windows operating system, Service Pack validated,
• The minimum PCX versions, etc.
This installation procedure is completed by a Security Guide to help you in OmniVista 8770 integration
into customer infrastructure (firewall, antivirus, ports ...).
2.2. Storing the installation data

To avoid losing the installation passwords and the various installation or customization parameters,
store these information items in an installation document.
2.3. Initial management and backup

1 Export the declared PCXs as an ldif file.
2 Start the execution of the daily tasks.
3 Save the OmniVista 8770 database.
4 Copy this backup to a medium independent of the server: external drive, network disk.
2.4. Checking the installation

See Chapter 3: Checking installation.
Depending on the options configured, check that each option works correctly. Note the results of the
tests run in a document.
2.5. Saving the OmniVista 8770 elements

Schedule a backup of the 8770 server at least once a week (by default).

3. CHECKING THE INSTALLATION
3.1. Principle
1 Check server start-up. All the OmniVista 8770 services must have started and stable, check
NMCsvc-x.log file.
2 Logon with a client; make sure all the application can be accessed.
3 Check the status of the scheduled tasks.
4 Check the different functions of the OmniVista 8770.
5 Check the license in the about screen.
3.2. OmniVista 8770 server services
3.2.1. OmniVista 8770 Service Manager tool

Start the Service Manager supplied with OmniVista 8770:
Start > Program > OmniVista 8770 > Service Manager
Or in Control Panel\System and Security\Administrative Tools, the Services tool :

Make sure all the OmniVista 8770 services have started up.
3.2.2. List of services
LDAP server • Oracle Directory Server Control Center

• Oracle Directory Server Enterprise Edition
MariaDb Database • MySQL8770
8770 server Service Manager • NMC Service Manager
Web server created and launched by "NMC Service • Apache
Manager"
OmniVista 8770 internal notification server created and • ORBacus Notify Service
launched by "NMC Service Manager"
Other OmniVista 8770 services created and launched • NMC Alarm Server
by "NMC Service Manager" • NMC Audit Server
• NMC CMISE Server
• NMC Communication Server
• NMC executables launcher
• NMC extractor
• NMC GCS administration server
• NMC GCS config server
• NMC Java Service Definition

• NMC License server
• NMC Loader
• NMC PBX/LDAP synchronization
• NMC Save/Restore
• NMC Scheduler
• NMC Security Server
If one of these services has not started up, consult the log file associated with the service; see chapter
TROUBLESHOOTING THE OMNIVISTA SERVICES.
3.2.3. Dependency and control of the services

The "NMC Service Manager" service installs, launches and controls all the NMCxxx services, as well as
the Apache and Orbacus services. When the "NMC Service Manager" service is started, it searches in
LDAP the definition of the services: executable, parameter, dependent services. These definitions can be
consulted in the system directory, entry:
NMC \ Omnivista8770 \ <Name of the 8770 server> \ <Name of the NMCxxx
service>
A service only starts if all the dependent services have already started. If one of these dependent services
stop, the service also stops.
During the backup or defragmentation phase, the "NMC Service Manager" service is paused in order
not to restart the services automatically. At the end of these operations, the "SaveRestore" service
reactivates the "NMC Service Manager" service.
The dependence tree of the services is as follows:
− For each service, the services that need to be started are indicated by the symbol ">".
− The Rank1 services are started directly.

− A service of Rank2 requires all services of Rank3 are started.
Rank1 Rank2 Rank3 Rank4 Rank5

Apache Scheduler CmisD AlarmServer GCSConfig
>ExecdEx >ComServer >Cmisd >GCSAdmin
CleanMib >LicenseServer >LicenseServer >LicenseServer
>SaveRestore >CleanMib
>NotifyService
ExecdEx Extractor >ExecdEx
>ExecdEx
LicenseServer
AuditServer GCSAdmin SyncLDAPPbx
NotifyService >LicenseServer >Cmisd >GCSAdmin
>CleanMib >LicenseServer
SaveRestore Loader >AlarmServer
>ExecdEx
Scheduler >NotifyService
SecurityServer ComServer
>NotifyService
If the ComServer service has not started:

• the following services will not start-up: CMISD, AlarmServer, GCSAdmin, GCSconfig,
SynchLDAPPBX,
• there will be no access in configuration, alarm feedback or PCX synchronization.
3.3. Launch 8770 client and access to the applications

From the server:
1 Start the 8770 client.
2 Logon as 8770 administrator (account adminnmc).
3 Open the menu Help > About, check the list of available modules in the license.
4 Check that these modules actually appear in the icon bar.
5 Launch each application.
6 For each module, expand the tree, carry out searches and display the grid.
7 Open OmniVista 8770 help.
Complete these checks:

1 By launching 8770 administration by the 8770 Web page.
2 By launching the client from a remote PC.

Then logon using another login. Check that the modules that are open for this login do correspond to
the rights associated with this login.
3.4. Status of the scheduled tasks

1 Open the scheduler Application.
2 Check the status of the following tasks.
• Tasks programmed by default:
 Weekly and Daily.
• Tasks programmed by the 8770 administrator:
 OmniVista 8770 backup (this task must be programmed manually),
 PCX backup (this task must be programmed manually),
 other programmed tasks: report, export configuration.
3.5. Server operation

The tests requested can only be carried out if the license allows this management.
3.5.1. Configuration
PCX OmniPCX Enterprise Access: graphical configuration, telnet console: test by an access to the FTP
server of the PCX.
PCX OXO : graphical configuration (local OMC software is started by the 8770 client).
3.5.2. Alarms
Reset a PCX card or provoke any other PCX alarm and check that this alarm is actually present in the
8770 Alarm application or send events from PCX by a “pingevt” command:
In the case of email notification of the alarms, test this notification see how to configure the mail server
in chapter Scheduled export as email
3.5.3. Event
For OmniPCX Enterprise, enable the system => 47xx directory – 4400 Synchro parameter
(= true). Check that the modification of a user is taken into account:
• arrival of the event in the alarm application,
• technical directory is updated.

3.5.4. Topology
Open the topology application and check that all the PCXs are displayed; otherwise launch a refresh
action to recover the complete list of PCXs.
If the personal view is managed, it will be activated by default on opening the topology; each PCX
present in this personal view must be added manually.
3.5.5. Directory (OmniPCX Enterprise/Entreprise)

Launch the WEB 8770, Directory page:
• search for the directory entries,
• place a click to call (STAP) to an internal number and an ISDN number.
3.5.6. Accounting
PCX side:
• Check the presence of the Accounting lock.
• Check the accounting ticket filters in PCX management.
OmniVista 8770 side:
• Check the list of loading parameters:
under Accounting application > tab Parameters > Loading > Accounting
 Depending on your management, validate the incoming tickets, null duration tickets, null
cost ticket.
 The detailed accounting PCXs must appear in this list and stay valid.
• Generate an accounting ticket:
 Make a telephone call.
 Start synchronization.
 Expand the accounting “organization”, tab “records”.
 Check that the set is present in the organization.
 In the ticket tab for this set, check that the call is present.
 Check that a cost has been assigned to this call.
 Do a detailed cost report per set. (you need to change the filter cost >0 to cost  0 in the
requester tool to avoid empty data when cost =0.
3.5.7. Traffic analysis (OmniPCX Enterprise/Enterprise)

PCX side:
• Check the presence of the Accounting and Traffic analysis locks.
• Validate accounting on the incoming communications.
OmniVista 8770 side:
• Check the loading options

Accounting application > tab Parameters > Loading > Traffic analysis
Accounting application > tab Parameters > Loading > Accounting (an
incoming call and null cost must be loaded)
Accounting application > tab Parameters > Loading > Voice over IP
• Check the status of the daily and weekly scheduled tasks:

 Traffic analysis loading: pmm file loaded for this day.
 Traffic analysis total: detail of the total per object observed. Where appropriate, modify this
totaling task to total all the objects, including the statistics per user (option -PTPtype All).
• Do a report on the attendants, trunk groups and, if requested, on the users, DECT.
3.5.8. VoIP
PCX OmniPCX Enterprise:
• Check the presence of the Accounting lock.
• In management, option “Ticket = Yes in IP object.
OmniVista 8770:
• Check the loading options
under Accounting application > Parameters tab > Loading > Voice over IP
• Do a VoIP report.
Note In the case of an incomplete ticket at the PCX end (field necessary for the quality analysis), these tickets
will not be loaded in the database.
3.5.9. Export, Print the reports

• Under the NMC directory entry > Server name, check the name of the mail server, the sender
mail address, print format (A4, US).
 Export the reports by e-mail, in the format requested by the client.
 Print the report.
3.5.10. Maintenance
PCX OmniPCX OXO:
• Backup the PCX
PCX OmniPCX Enterprise:
• Do an immediate backup.
• Restore this backup on the PCX, this just involves overwriting the PCX local backup.
OmniVista 8770:
• Do a defragmentation.

• Do a backup.
• Restore this backup.
3.6. Check the license

− Start a 8770 client.
− Open the menu Help > About.
− Check:
• there is no exceeding of user capacity,
• the reference PCX has been found.

4. FAILURE ANALYSIS
The failure as seen by the client can have very different causes.
1 Check the management.
2 Search to see if the problem is known and has been corrected in a higher version.
3 Use a specific troubleshooting.
4 Do an analysis of the problem.
You need to carry out several types of analysis:
• Analysis by stage
• Analysis on the PCX
• Analysis of the client environment
• Analysis by history
• Analysis of the internal functions of the server
• Analysis of the different logs
• Reproduction of the problem
• Search for a possible workaround

4.1. Analysis by stage
Check the processing chain point by point.
Depending on the case:
• return to the previous stage,
• repeat all the stages.
Once the stage causing the problem has been identified:
• check the management,
• check the logs associated with this stage.
Checking the previous stage
Example:
No email notification of an alarm Check that the alarms have reached the Alarm application
correctly.
If yes, problem searching must be carried out on the
notification part:
• mail server parameter
• sender address,
• mail server log
Report empty Check that the last ticket is present.
If yes, then the report is incoherent:
• check the filters for this report,
• use a predefined report.
Repeat all the stages
No email notification of an alarm No alarm present in the base.

• PCX end, check:
 the presence of a lock for alarm feedback,
 the presence of an alarm transmission filter to
OmniVista 8770
• OmniVista 8770 end, check:
 the Monitoring alarms option for the PCX in question.
Traffic analysis report empty • PCX end, check:
 the presence of the software locks.
• OmniVista 8770 end, check:
 the traffic analysis loading option for the PCX in
question.
 the traffic analysis loading filter,
 the modification of the PTP total to totalize the users,
 use a predefined report

4.2. Analysis on the PCX
Use the internal tools of the PCX.
If the problem is confirmed with these internal tools, contact the PCX hot line and just state the problems
identified at the PCX side.
Configuration problem, use mgr
Under mgr, display the keys of a user: Do a check on the PCX database by checkdb command
return invalid object
Accounting problem
Read the content of the tickets with the PCX internal tools.
For OmniPCX 4400/Enterprise
Function Tool File location

Accounting Accview /usr4/account
IP IpView /usr4/account
Traffic analysis Dbgobs (tool not supported) /usr4/pmm
Example of issue and troubleshoot action:
Problem Troubleshoot
Incorrect field in an accounting ticket Describe the call type, the time of a communication.
Attach the taxaxxx.dat file associated with this call.
Try to reproduce the call scenario if identified.
Incorrect field in an observation ticket Attach the .pmm and .inf files associated with this call.
(negative value for a counter, etc.) Try to reproduce the call scenario if identified.
Incorrect field in an IP analysis ticket Describe the call type, the equipment (IP Touch 4068 sets),
value=65535 the time of a communication.
Attach the IPxxx.dat file associated with this call.
Try to reproduce the call scenario if identified.
4.3. Analysis of the client environment

Aim
Know the client environment in order to check compatibility with the external applications; see the
document OmniVista 8770 Security Guide Line.
Windows
• Describe the Windows version of the server, of the client: OS / Service Pack / hot fix.
• Does the client have a security or optimization policy forcing it to modify the Windows default
installation: service halt, file deletion, etc.

Anti Virus
• Does it check email transmission frequency?
• Does it check email program exe file allowed to send email (outlook.exe…)
• Does it scan the files used by the client (.jar) => slows down the launch of the client.
Network topology
• IP address of the server, client PCs, PCXs.
• Presence of a router.
• Specific link: VPN, NAT.
Firewall
• Has it been configured according to the OmniVista 8770 IP flows; see the Installation manual,
Security chapter.
• Does it let through incoming connections to the 8770 client? (Corba notification port).
Mail server
• Does it accept a non-authenticated smtp connection?
• Does it control the sender email address?
• Are there limits regarding email size, email send frequency?
External application
• Has the client added other applications on the 8770 server?
4.4. Analysis by history

Determine the last site events:
• Last user actions.
• OmniVista 8770 internal alarms.
• Windows events.
• PCX alarms.
The context is important.
Example : the user has just erased the directory entries (including the logins). Following this operation,
the launch of the client fails
Internal alarm
An alarm signals Could not find The reports are empty

new accounting files
PCX alarm
A logical link is out of service The IP/x25 connection using this logical link no longer
works

The date of the appearance of the problem is important.
Example:
No connection to the PCX since 15/1 On 14/1, the IT department installed a firewall
32 days after installation, the client is If the synchronization was deprogrammed or reference PCX
unable to connect has not been discovered, the license authorizes temporary
operation for 32 days
4.5. Analysis of the internal functions of the server

Refer to CHECKING THE INSTALLATION the installation.
After installation, the access in The Windows Telephony service was not started and this
configuration fails blocks start-up of the 8770 service NMC Com Server
Suddenly the client can no longer connect Check the status of server.
Only the services: service manager nmc database have
started. The LDAP server was halted
4.6. Analysis of the different logs

The detail of the logs is described in chapter Collecting data and logs in this document.
Log accessible client end • Module log

• Client log
• Scheduler status
Log accessible server end • Services log
• Services in extended trace log
• LDAP database log
• Apache WEB server log
• PHP log
• Windows event (application error)
• Installation log
• Patch installation log

4.7. Reproduction of the problem
Try to reproduce the problem in order to identify clearly the user actions leading to the appearance of
the problem.
Example:
java exception in accounting I created a cost center. => java exception

Before validating the creation, I switched
over to the last ticket tab
4.8. Search for a possible workaround

This search is used to help out the client temporarily but also to isolate the problem. Example:
The 8770 client does not connect: Serious Try to use:

error • The client on the server
• The administration via web client
• The client on another pc
• A Windows administrator login
Go back to a simpler management
The backup scheduled on a network drive • Do a backup on a local drive

does not work
• If test ok, redo the management for backup on the
network in immediate mode
4.9. Searching if problem known

Check your OmniVista 8770 server version.
Check whether there is a newer (higher) version (patch, maintenance version, new major release).
If this is the case, consult:
• The readme file and list of problems corrected in last patches available in the BPWS.
• The implementation procedure for this new version.
• The BPWS if your problem is already listed. Consult the Technical knowledge center ( TKC )

5. COLLECTING DATA AND LOG
5.1. 8770 diagnostic description

Thanks to the tool “8770 Diagnostic”, you can extract easily all log and setup data of 8770 in one
single folder C:\TS and get a web page overview of your system state
To run the script, launch 8770 Diagnostic from windows application:
Windows Start menu > OmniVista 8770 > 8770 Diagnostic

The script runs in interactive mode (I, enter, or any other key) or non interactive mode (N key). In
interactive mode there is a pause after each extract action.

Answer “N” for a No interactive mode
Default port : 389
Default password : sql

5.2. 8770 Diagnostic steps
1 Welcome and question for interactive mode

2 Finding 8770 installation path, license, version history
3 Asking for LDAP port, SQL password
4 Retrieving Windows system configuration (hardware, OS, IP, path, event, port used
5 Retrieving 8770 services running
6 Copying 8770 logs files
7 Retrieving last scheduled job report
8 Search managed PCX, version, management options, number of users, last collected files
9 Count number of accounting tickets (date of first one and last one)
10 Display Web report on collected information
11 Compress result as 8770ServerNAME
5.3. Diagnostic result

Web page overview

5.4. 8770 Client log
5.4.1. Application state

For each 8770 client application there is an associated status window with useful information about
• Launching application
• Setup Connection
• Request status
The status window is located just below the application grid.
5.4.2. Java exception

Most client issues are trapped into the status window. But it may happen one specific error was not handled
by 8770 client program. Instead of the status information, there will be a Java exception pop up message.
This exception will trace the last action: like refreshing the grid, resizing window, launching another module...
Please, reproduce the context of such error and provide
• Text capture of the exception
• Client and server log
• A description of your last action

5.4.3. 8770 Client directory
The files of the 8770 client are located in different directories depending if client is launched on a remote
PC or from 8770 server
Client remote Client on server

\Client8770X.X\bin\ 8770Client.log \8770\Client\bin\8770Client.log
5.4.4. Runnmc.bat file

The 8770 client is started by a batch file command: runnmc.bat under :
Client remote Client on server

\Client8770X.X\bin\ \8770\Client\bin\
5.4.5. Activating the console and java process trace

1 Edit the file runnmc.bat.
2 Locate the line starting with START /B "" "C:\8770\OpenJRE\bin\...
3 Replace javaw.exe by java.exe
When the client is next opened, a console window is opened.

In the event of a problem:
1 Select this DOS window.
2 Click Ctrl + Pause and capture the traces.
5.4.6. Modifying log options

By default the log is already activated, you can modify log option by this procedure:
1 Edit the file ominivista.properties.
2 By default, the log file get these parameters
• Tracelevel= option debug
• Saved in rotating file = option R
• first file name = 8770Client.log
• with a size of 5000KB
• up to 2 additional files: 8770Client1.log and 8770Client2.log are created
Here the syntax of such parameters
log4j.rootLogger=debug, R
log4j.appender.R.File=8770Client.log
log4j.appender.R.MaxFileSize=5000KB
log4j.appender.R.MaxBackupIndex=2

5.5. PCX OmniPCX Enterprise data import log
You can import PCX OmniPCX Enterprise data as a text file from the configuration application. The
import run in up to 3 different steps. The result of import action will be summarized in the status window.
Additionally, a new log file is created in same folder as the data file. If the data file is named Users.txt
the log file will be named Users.log.
5.6. Directory Web client log ( PHP logs )

Web Client uses PHP to present the OmniVista 8770 web page In case of issue you will find information
under 8770\Client\log\error.log
How to trace STAP calls?
Follow the procedure below:
− Copy the 8770/php/php.ini original file into 8770/php/php.old
− Edit the 8770/php/php.ini file.
− Search -> Examples :
− Delete the ; in the line
; error_reporting = E_ALL
− Add ; at the beginning of the line
;error_reporting = E_ALL & ~E_NOTICE & ~E_STRICT
− Restart the Apache server.
− Launch a 8770 directory client.
− Select an extension in the directory list.
− Perform a STAP call.
− Check the trace in the file:
8770/Apache2/logs/error.log
5.7. Scheduled tasks log

The parameters of the scheduled tasks can be modified in the *.properties :
• specify the trace level: replace info by debug,
• modify the name of the log file.
List of *.properties files are present under 8770\client\bin.
File name Description

NMCPurgeCarrier Carrier purge
NMCArchive Archive of accounting record
NMCRestore Restore of accounting record
NMCCumulAcc Cumulative counter recalculation
Carrier cumulative counter calculation

Organization cumulative counter calculation
NMCCumulPTP PTP cumulative counter calculation
NMCCumulVOiP VoIP cumulative counter calculation
NMCDetection Detected exceeding threshold
NMCCarrierImport Code book scheduled import
NMCCarrierExport Code book scheduled export
NMCPurgeMonitoring Tracking periodic purge
NMCPurgeInfo Accounting periodic purge
NMCPurgeVOIP VoIP periodic purge
NMCViewer Generate report
NMCPurgereport Report periodic purge
5.8. Server log

By default for each log, 2 rotating log files are created with a size of 5 MB.
The trace files can be consulted with Notepad to trace the activities of the services or specific processing.
5.8.1. Log file lists

The logs are placed in the directory \8770\log.
Service monitoring :
File Name Description
NMCsvc_mgr.log : Service Manager (Services monitoring)
NMCJavaServer.log : Java Service (Java services monitoring)
Ldap server :
NMCLdapPlugins.log : Ldap plugins
NMCSecurityPlugin_ex.log : Aging Password check
Configuration:
NMCICEConfiguration.log : ICE Connectivity and Configuration server
DM.log : Device management server
UUM.log : Unified User Management server
NMCGCS_Config.log : OXE Generic Config server
NMCGCS_Admin.log : OXE Generic Admin server
NMCCMISD.log : Cmisd server – OXE only
NMCMIBCompiler.log : OXE MIB compiler
NMCDictCompiler.log : OXE dictionary compiler
NMCCOM_SERVER.log : Communication Server – OXE, OXO
NMCCOM_SERVER_HttpFrame.log : HTTP Proxy
NMCCOM_SERVER_ModemMonitor.log: Modem monitoring
Synchronizatiion :
NMCSyncLdapPbx.log : SyncLdapPbx Server (main log)
NMCSyncLdapPbx_AlzPoller.log : OXO files poller – not relevant for 1.0
NMCSyncLdapPbx_HttpSrv_1.log : OXO synchronization – not relevant for 1.0

NMCSyncLdapPbx_Inv.log : Reverse synchronization 8770 -> OXE
NMCSyncLdapPbx_InvSynchroDoneOnP History file of operations
bx.log
NMCSyncLdapPbx_Opt.log : Network resource optimization
Alarms:
NMCFaultManager.log : Alarm Server (main log)
NMCFaultManager_A4400ARService.lo OXE alarms reception
g:
NMCFaultManager_AlarmTrigger.log : Action executed on alarms reception
NMCFaultManager_IARService.log : 8770 Internal alarms reception
NMCFaultManager_ICEService.log : ICE alarms reception
IceAlarmDispatcher.log : Traps reception
NMCFaultManager_VNRCVRSVC.log : VitalSuite alarms reception – internal and performance
thresholds)
NMCFaultManager_OfficeDefinitionsRe OXO alarms catalog – not relevant for 1.0
ader.log :
NMCFaultManager_OfficeReceiver.log : OXO alarms reception – not relevant for 1.0
NMCFaultManager_RMA.log : OXE RMA alarms reception
Infra services:
NMCLicServer .log : License server (main log)
NMCLicServer_LicVerif.log : License file check
NMCSecurityServer.log : Security server
NMCexecdex.log : Executable runner
NMCScheduler.log : Scheduler server
NMCsave_restore.log : Save restore server (main log)
NMCsave_restore_NmcMonitorServices.log Save Restore server (service monitoring)
:
WS.log : Client/service web service (common part)
Audit:
NMCAuditServer.log : Audit Server
Accounting / PTP Loader:

NMCLD.log : Loader server
NMCLD_AccOrg.log : Organization map
NMCLD_IP.log : Voip ticket loader – not relevant for 1.0
NMCLD_NewAccPlg.log : Ldap notification reception
NMC_Archive.log : Accouting data archiving
NMC_CumulAcc.log : Accounting cumulative calculation
NMC_CumulPtp.log : PTP cumulative calculation
NMC_Detection.log : Accounting Threshold detection
NMC_PurgeCarrier.log : Carrier data purge

NMC_PurgeInfo.log : Accounting data purge
NMC_PurgeMonitoring.log : PTP data purge
Tools:
NMCCleanMib.log : Clean up process
NMCCleanMib_Mib.log : MIB process
NMCCleanMib_ORBacusNotify.log : Notify data clean up
Reports:
NMCExtractor.log : Report builder
NMCPurgeReport.log : Report purge
5.8.2. Setting up extended traces

1 Open the administration application
module administration tab.
2 Go to nmc \ Omnivista8770
3 Select the server and edit the field Argument List
4 At the start of the line, replace -TraceType 0 by -TraceType --1 (dash TraceType space
dash dash one)
5 Eventually add the option –Tracesize 50 to extend the trace size to files of 50 MB
6 Eventually add the option –TraceNumber 10 to extend the number of rolling log files from 2 to
10

Warning Since this mode slows down the server, after investigation it is essential to return to the default trace
level: -TraceType 0 and remove –TraceSize 50, –TraceNumber 10.
5.9. LDAP database log

List of the log files under \8770\SunONE\slapd-8770\logs :
- Access.log : this log is deactivated by default. To activate it temporarily, use the LDAP server
console
1 Launch LDAP administration console : Start Panel -> Omnivista8770-> Directory Server
Control Center

2 A Web page will be opened, connect as admin with directory manager password (set in
setup steps)
3 Select Directory Servers tab and your server name :
4 Select Server Configuration, Acceess Logging tabs, and Enable the Access logs

5 Logs are enabled abd accessible in default logs folder : /8770/SunONE/slapd-
8770/logs/access
- Error.log : All errors on attributes manipulation are written in those logs file.
[25/janv./2019:02:07:44 +0100] - INFORMATION - conn=-1 op=-1 msgId=-1 -

dn_values2keys(EQUALITY): invalid dn for value $$
They are enabled by default:

5.10. LDAP Plugin log
Additionnal logs about ldap exchanges between 8770 services and ldap database are generated in
NMCLdapPlugins.log. Only requested by Technical support.
Extended traces can be enabled in ldap client embedded in 8770 (\8770\bin\Dirmanag.exe )
- Enter cn=Directory manager and its password:
- Navigate to cn=config -> plugings -> NMC-START01 Integrity Plugin

- Set nsslapd-pluginarg0 “--1”

- Ctrl + S to save
- Oracle Directory Server Enterprise Edition must be restarted
Warning This modification in ldap must be done carefully. Due to slow down working, this value mut be set back
to the default 0 as soon as the logs are catched.

5.11. Installation log
5.11.1. Default Installation trace

Installation process use this temp directory (administrator is your windows login)
\Users\Administrateur.WIN-M11N7C2VVAJ\AppData\Local\Temp\1
You can access to this directory with the system string variable %temp%
Such directory is hidden by default in Windows Explorer, to grant the access, check Show hidden
files and folder
(uncheck hide protected operating system files )

OmniVista8770_report.log Installation report
OmniVista8770_install.log Full log for installation
{C3CF...} {C3CF0589-B127-4C15-A347-E0DCCBC74E87}
This folder contains all required file by the installation
Visual.C++,MariaDb,Python, Driver ODBC
Under /8770/install/patches
Patch_installer.log Patch installation if any patch present
Under /8770/log
Predef_Import.log Installation of predefined reports in database
Localization_kit.log Installation of localization kit
5.11.2. Installation rollback
There are few things that you should know on rollback process:
• If a failure happens before LDAP server and Sybase server are installed, the rollback process will
succeed to retrieve the previous version and data.
• If a failure happens after LDAP server and Sybase server are installed, the rollback process will
try its best to remove binary and data but you should manually complete the uninstall process
and clear the associated registry entry.
• To investigate on the rollback case, edit the OmniVistaInstall.log and locate the string
Sequence: rollback. The few lines before this text, will help you to find the root cause of the
rollback.

6. TROUBLESHOOTING THE OMNIVISTA SERVICES
6.1. NMC Server

First of all, database and server issues should not be mixed with standard operation on OmniVista 8770
server:
• Backup in progress.
• Defragmentation in progress.
• License limit reached.
• Service Shutdown in case of not enough resources (disk or RAM).
So first, check the current logs (nmcsaverestore, nmclicserver, nmcsvc_mgr).
Then, you need to follow OmniVista 8770 server starting process. All NMC Services are started by NMC
service manager provided:
• Server hostname and DNS suffix has not been changed
• LDAP server is started, available, and index are properly set
• NMC executables launcher service ( execdec process ) can be started to monitor the current disk
capacity
• There is enough disk space for all monitored disk, by default 35 % free space
• CPU and Memory is not 100 % used.
To extend the log of server initialization:
1 Launch regedit.exe
2 Locate svc_mgr entry under
HKey_local_Machine\System\CurrentControlSet\Services\Svc_mgr
3 Expand parameter
4 Change tracelevel for the value = FFFFFFFF (8 times F , this means -1)

5 Restart NMC Service Manager
6 Read the 8770\log\NMCsvc_mgr.log log
6.2. Basic server repair

Time of analysis and search of a workaround is time consuming; a faster solution consists on restoring
a valid backup of OmniVista 8770 server.
1 Check you have a valid backup, associated nmc.license, exact list of installation parameter
(see restorecontext.ini file).
2 Uninstall OmniVista 8770.
3 Reboot PC.
4 Reinstalll OmniVista 8770 with same installation parameters.
5 Reload the valid backup.
6.3. Oracle Directory Server ( LDAP Server )

As listed in above chapter, LDAP server is the key access to run properly OmniVista server.
6.3.1. Oracle Directory Server not running

Try to launch it from NMC service manager.
6.3.2. Oracle Directory Server fails to restart

You need to check the \8770\SunONE\slapd-8770\logs log files
6.3.3. Oracle Directory Server fails to recover its configuration

On each start-up, the Oracle Directory Server checks the integrity of its configuration; if there is a
problem, a recovery is launched automatically. If the recovery fails, you may solve the situation manually
either by deleting the last transaction or by rebuilding the initialization file.
Destruction of the transaction and log files:
1 Go under \8770\SunONE\slapd-8770\db,
• delete the files named logxxxx
• delete the files named _dbxxx
2 Restart the Oracle Directory Server Enterprise Edition service.
6.3.4. Oracle Directory Server fails to read its dse.ldif configuration file
Each time the server restarts, it saves the current configuration into dse.ldif file (a file of about 123
kB size). In case of power failure with sudden closure of windows the file may be corrupted and we need
to recover a valid one dse.ldifstartOK.
1 Go to \8770\SunONE\slapd-8770\config

2 Rename dse.ldif file as BADdse.ldif
3 Copy the dse.lifstartOK file and name it dse.ldif
4 Restart the Oracle Directory Server
If no valid dse.ldif is found you can try to recover it from a backup

1 Go to the 8770 default backup directory 8770_ARC : \8770_ARC\8770Backup\<date of
backup>\slapd-8770.zip\8770\SunONE\slapd-8770\config
2 Copy the dse.ldif from \8770_ARC\8770Backup\<date of backup>\slapd-
8770.zip\8770\SunONE\slapd-8770\config to \8770\SunONE\slapd-8770\config
folder
3 Restart Oracle Directory Server and nmc service manager.

6.4. SQL server
On each start-up, the MariaDb SQL database checks data integrity and performs its defragmentation
itself.
Sometimes, it is necessary to force the defrag in the maintenance application: Be aware that this
operation stop temporarily the services.
6.4.1. Generic log

Currently, the global failure of the database at starting are presents in log file:
C:\8770\data\data\<server name>.err
At starting the MariaDb checks that all tables are consistent and well existing in folder :
C:\8770\data\data\nmc5 , files *.ibd.
6.4.2. Enable Mariadb queries log

It is possible to add traces to get the sql queries sent to NMC databases. Modify the my.ini file from:
\Program Files (x86)\MariaDB 5.5\data
Add the following line under the [mysqld] paragraph:
[mysqld]
general-log
general-log-file=queries.log
Restart the SQL service
Log file queries.log will be created in 8770\data\data
6.4.3. Enable ODBC Mariadb log

Sometimes in case of report failure, wrong behavior in alarm application, enable the ODBC driver logs
are very helpful.
Note This tracing log have to be performed only if requested by Technical Support.
1. Launch ODBC administrator (32bits) tool : \Windows\SysWOW64\odbcad32.exe

2. Configure the existing driver ODBC 1.0 Driver used by Omnivista

3. Fills the root user name and its password. \Windows\SysWOW64\odbcad32.exe

4. Enable the Debug option.
5. In Tracing tab, check “Machine Wide tracing for all user identities” , specify the log file path
and start tracing

6. Check the registry as shown below using regedit tool

7. Reboot the server
8. Trace file will be created in three potential location : C:\SQL.LOG or
C:\windows\temp\SQL.log or %temp%\SQL.LOG
By default, the log file is located in c:\windows\temp
Warning Don’t forget to remove those values to get back in default settings.
If the database does not start for unknown reasons, contact Technical Support with .err file and Mariadb
queries log to analyze the situation and determine whether other recovery tests are necessary or whether
the OmniVista 8770 backup must be restored.
6.5. Apache server

Apache is the WEB server of OmniVista 8770. It is launched by NMC service manager.
The initialization uses conf file located in 8770\data\Apache2
• Httpd.conf define basic parameter like the listen port, ...
• The 8770.http.conf defines all alias like http://servername/nmclogog/
Apache is used for several purposes:
• Web directory
• Display of log file in the scheduler module
• Display of topology and alarm application
• Access to integrated help
• Display of OmniPCX 4400 / enterprise graphical view of subscriber set.
If another application uses htttp port (80) Apache will fail to start and these above features will not be
provided (no data).
Make sure the port is not used by another application using netstat command :
netstat -aon | findstr 80
the ports and pid will be listed.
Apache uses a cgi application bases on php files with a large impact on all web page.
To Enable the extended trace:

Go under 8770\data\Apache2 and edit httpd.conf file , search for the following lines and
replace with new values.
• Old:
LogLevel warn
TraceEnable off

• New:
LogLevel trace5
TraceEnable on
Collect the logs under \8770\Apache2\logs\
6.6. Wildfly server
As for Apache server, the wildfly log is collected from \8770\wildfly\standalone\log

7. ACCOUNTING
This chapter contains helpful information for understand the different steps in the Accounting process for
OmniPCX Enterprise and OXO PCXs.
7.1. Accounting at the PCX end
7.1.1. OmniPCX Enterprise

To generate accounting tickets on the PCX that can be used by the OmniVista 8770 server, you must:
− Possess the Accounting users software lock,

− Validate the Applications\Accounting\Files for external accounting parameter,
− Define the ticket types that will be stored in these files (default filters in bold):
Outgoing Public PCX Calls
Public Outgoing Network Calls
PCX Network Calls
Private Outgoing PCX Calls
Private Outgoing Network Calls
Public Incoming PCX Calls
Public Incoming Network Calls
Private Incoming PCX Calls
Private Incoming Network Calls
Priority Incoming Calls
Data Outgoing/Incoming Calls
Public Outgoing 0 Unit Calls
Non-ticketed user
PCX PCX Calls
PCX Transit Calls
PCX/Netw Count. Tick. Duration 0
CDR (Tickets) Management
− Define the number of masked digits; the PCX will replace these masked digits by "----" characters
(example 015566----).
Note 1 Obtaining certain types of tickets is conditioned by the presence of the corresponding software
locks :
PCX-PCX calls
Network_PCX calls
2 In the tickets of users who are not ticketed, ******* replaces the following fields:
Called number, Calling number, CC, Charged number, Acting.

Relevants commands :
In OXE, some commands can be used to read accounting and investigate on accounting tickets.
See below the most useful of them :
Commands Description
account -v Edit the parameters managed
account save To check the content of the tickets, you can first force buffer write in a new
account compress file
accview Read the contents of the files
Specific element searches can be done as follows:
• accview –tf TAXAXXXX.DAT with result capture in a text file.
• accview –mtf TAXAXXXX.DAT. You can search for a character string by
entering /string followed by Enter. The n (next) and p (previous) keys
are used to move to the next/previous occurrence.
• accview –mtf TAXAXXXX.DAT –a Number-
of_the_fields_to_display
Example
accview –mtf TAXAXXXX.DAT –a 1 9 (display fields 1 (called number)
and 9 (call type) of the tickets).
The tickets are stored in /usr4/account folder
Result of a command : accview -tf

The table in Appendix 1 details all the ticket fields.

Others parameters are manageable in OXE settings
System/Other System Param ➢ TrkGrp in ticket for trans.call

Type of information in a transit ticket:
Yes: Trunk group no.
No: Trunk number
System/Other system Param/ ➢ No Charging Ticket For Voice Mail
Accounting Parameters In the case of a call transfer to the outside via a voice mail
menu.
Yes: the call is not charged.
➢ Charge Request
The remote charge request is an ISDN service allowing the
reception of accounting pulses during the communication.
No: the remote charge request is inhibited. Useful especially
in countries where this is a pay service and if this service is
not deemed essential.
➢ Accounting Ticket To User Node

Choice by menu:
Guest/Administrative/All: Accounting ticket download (guest,
administrative or all) from the trunk node to the user's node.
➢ Acc. Ticket To User Node Dur. Met.

Choice by menu:
Guest/Administrative/All: Calculation of duration accounting
on the current node when a ticket (Guest, Administrative or
all) is downloaded from another node.
➢ Transit Ticket for ABCF

Yes: The local transit accounting tickets are taken into
account.
➢ Ticket for OutCall From Empty HG

True : Ticket For OutCall from Empty HG$.
➢ External Calls to Busy Sets

True : Generate accounting ticket of 0 duration.
Users ➢ Charging Category
➢ Cost Center
➢ Dialled number masked

Yes: in the tickets, CalledNumber = ------------------------
Trunk Groups/Local Parameters ➢ Charge Calling And ADN Creation

If the caller belongs to a PCX connected by a QSIG trunk
group to the charging PCX:
Yes: ChargedNumber = Number of the calling station
No: ChargedNumber = QSIG trunk group number

Applications/Voice Mail ➢ Justified
Yes: Messaging outgoing and incoming calls are ticketed
(justified).
No: CalledNumber = ------------------------
OXE traces collecting :
To trace accounting ticket generation traced&

account –rsat
To halt the trace kill –9 n° du process traced&
account –rsat
7.1.2. OXO
To Thanks to the OLD ( Office Link Driver ) available in BP Web site, OXO provides Realtime metering
on IP Network.
In OMC, the metering can be enabled as follows :
\OMC\Metering\metering\External Metering Activation IP
\OMC\Metering\metering\Counting PRINTOUT/FIELDS
\OMC\Users\Base stations list : Select All calls.

For each call, an XML file is produced by OXO and retrieved by 8770.
Example XML ticket :
For further information, refer to the OXO Expert documentation General Application.

7.2. Data Loading
The following trace files must be analyzed to investigate the accounting file download function:
NMCComserver.log (connection to the PCX)
NMCSyncLdapPbx.log (PCX synchronization and FTP transfer)
NMCSyncLdapPbx.log_AlzPoller.log (for OXO)
If no accounting file is downloaded during a synchronization, a "warning" level alarm is generated:
10018 There are no accounting files to download from this call server
The “Security Guide” documentation provides useful information about the ports and protocols used for
the data transfer.
7.2.1. OomniPCX Enterprise

The File download is started by the synchronization task.
The type of accounting managed is "Detailed accounting" or "Global accounting by node with record
retrieval".
OmniVista 8770 downloads the file ACCOUNT.LIS by ftp. It contains the list of available files. The
account used for the transfer is adfexc.
Check the management at the OmniVista 8770 end:

FTP user: adfexc
FTP password: same as the one managed at the PCX end (adfexc by default)
Where appropriate, test the account by an ftp connection from a DOS window.
OmniVista 8770 downloads, by ftp, the new files available since the last synchronization. The name of
the last file downloaded is read in the field: Data collection\Last polled Accounting file in
configuration application.

The files are saved in the following directory :
8770\data\loader\network=xx\subnetworknodenumber=yyy
The files present are used by the loader for ticket insertion in the database.
If there is a problem on a ticket (incorrect format), the file may be rejected. In this case, it is stored in a
"Rejected" directory.
During the synchronization, OmniVista 8770 will create, or update on the PCX, a 4760.acc file in the
/usr4/tmp directory. If OmniVista 8770 subsequently no longer connects to the PCX, the latter will
periodically generate incidents:
0276 : External accounting application : No recovery
If appropriate, delete this file or analyze the reason why the retrievals no longer take place.

7.2.2. OXO
Notes
Requirement: OLDriver must be installed in 8770 server with administrator privileges..
The File download is started by the synchronization task.

The type of accounting managed is "Detailed accounting" or "Global accounting by node with record
retrieval".
OmniVista 8770 retrieves the tickets available by ftp. These tickets are erased from the PCX after
retrieval.
The OXO Buffer can stored up to 1,000 tickets.

Tab: Connectivity \ FTP password: tuxalize (by default)
C:\>ftp <CR>
ftp>open @IP 30021 <CR>
connected to @IP
220 Alize Session Manager FTP Server
User <@IP:<None>>:ftp_nmc <CR>
331 Password required for ftp_nmc
Password:tuxalize <CR>
230 User ftp_nmc Logged in
ftp>bye <CR>
The files are saved in directory

8770\data\loader\network\alizenodenumber in the form TAXAxxxxx.ALZ.
The files present are used by the loader for ticket insertion in the database.
If there is a problem on a ticket (incorrect format), the file may be rejected. In this case, it is stored in a
"Rejected" directory.
Since the tickets are, by default, no longer available after retrieval and loading, it may be useful to keep
the files for specific investigations. This option must only be validated temporarily to avoid hard disk
saturation.
In the system directory, enter value "1" in the field:
PC_name/Servers/PC_name/loader/specific tab/keeptaxafileafterloading
7.3. Loading to the base
7.3.1. OmniPCX Enterprise
The log files (8770\log) concerned by the loading in the base are as follows:

• NMCLD
This is the main file. It contains the name of the tickets file processed, the quantities of tickets
processed (read, inserted, rejected) and, where appropriate, information regarding the unique
nature of the ticket. In extended trace on the loader, there are details regarding the cost
calculation (carrier, tariff, etc.).
• NMCLD_AccOrg / NMCLD_NewACCPlg
Organization update information.
• NMCLD_CostCalculation
Lists all the tickets for which a cost could not be assigned on loading in the base.
• NMCCostRecalculation_CostCalculation
Lists all the tickets for which a cost could not be assigned on recalculation.
• NMCCostRecalculation
Detail of the cost recalculation in extended trace; see Appendix 3.
Main SQL tables description :
• ticket
Contains, more particularly, the information extracted from the PCX tickets and the costs
calculated on loading. The entityid field provides the link to the chargeableEntity table.
Query example
select * from ticket where initialstartdatetime >=’2006-09-22’ and
initialstartdatetime <’2006-09-23’
• ChargeableEntity
Contains all the chargeable entries (sets, trunk groups, etc.)
Query example
select * from chargeableentity where chargednumber=’3200’
• Pbx
Contains the list of the PCXs
Query example
select * from pbx
• CarrierTrunkGroupConnection
Contains the data used to assign a carrier according to the outgoing trunk group of a call.
Note
To reduce the synchronization duration of OXE and accounting retrieving, you can disable the
accounting tickets collection coming from PCS : In administration application :
/nmc/Omnivista8770/”hostname”/NmcArchive/Accounting

7.3.2. Assigning the tickets
The sets and other chargeable entities and the cost centers are created using set information retrieved
by synchronization.
The tickets are loaded into the base (ticket table) after a filter control and a "unique nature" control which
tests whether the tickets are already present in the base.
− Check the filters on the call types and charged nodes in the Accouting/traf/VoIP application :
Parameters tab \Loading\Accounting

Each ticket must be assigned to an entity in the organization. For the tickets from an OmniPCX
Enterprise, the search is first carried out on the "Set number/PCX number" combination. If several
entities exist, the one with the latest creation date is selected.
If this combination does not exist, the search is done on the set number in the entire network in which
the PCX is managed. If this also fails, an entry is created under the "Undefined" level.
If the number of the PCX read in the ticket (ChargedPartyNode) does not exist, the processing of the
ticket will depend on the following parameter in Administration application:
nmc \ Omnivista 8770 \ Server Name \ Service \ Loader
Global accounting for undeclared PCXs:

Yes: The ticket is assigned to the PCX under the "Global accounting" level.
No: The ticket is assigned to an entry under the "Undefined" level. If it does not exist, it will be
created.
Warning
The feature “extrasubscriber” taking in account the tickets of sets declared in a non Alcatel PCX
connected by a QSIG trunk group to an OmniPCX Enterprise, is no more supported in 8770.

7.3.3. Cost calculation on loading the tickets in the base
The different steps in cost calculation are:

• Search for direct and indirect carriers corresponding to the call type.
• Search for a direction (calling region/called region).
• Application of a tariff.
Search for outgoing carriers
There are two separate direct carrier search methods depending on the management undertaken:
1 Indication of a correspondence between the call outgoing trunk group and the carrier.
This management is recommended whenever possible as it optimizes the search.
Manage Trunk Group Connection in the Carriers tab.
2 Search for the most precise correspondence between the called number and one of the prefixes of
the various carriers managed.
The existence of an indirect carrier depends on the value of the ticket CarrierCode field.
• CarrierCode = 0
=> No indirect carrier
• CarrierCode = 1
=> Possible existence of an indirect carrier.
The corresponding code is searched for amongst those managed in Carriers \ Indirect
Carrier Codes. If it exists, a check is made on the corresponding carrier found:
 Outgoing:
In this case, it is a direct carrier. The analysis is made on the called number.
 Indirect outgoing:
The called number is analyzed according to the data of the indirect carrier found. The indirect
cost is calculated.
You must then search for the direct carrier with outgoing type. A direction is found by analysis
of the called number. It is retained if the Indirect Carrier field contains the name of
our indirect carrier.
Cost calculation errors generate minor level alarm :

13001 Cost calculation error during record loading from PCX
To limit the number of cost calculation errors due to numbers called not present in the tickets (case of
certain incoming calls), incorrect numbers or numbers not yet managed as a prefix in a carrier, we
recommend managing a default direction in one of the carriers:
Calling region: empty
Called region: empty

Make sure the parameter in Accounting / parameters / loading / accounting / Threshold "Duration
(sec) must be =>" with the value 0' and "Cost must be =>" with the value 0.0.
It is assigned an "Unknown direction" tariff.

7.3.4. Recalculating the costs
In case of a problem on the call cost (missing or assumed incorrect), redo a calculation by setting
extended traces. The huge quantity of information generated implies certain recommendations:
− Do the trace on the shortest period possible (example, the day of 21/09/2006)
From 21/09/2018
To 22/09/2018
− Modify the arguments ( Argument list ) in loader task definition in the administration application.
Change -TraceType 0 by -TraceType –-1 -TraceNumber 10 –TraceSize 100
TraceType --1 gives an extended trace,
TraceNumber 10 generates 10 log files,
TraceSize 100 is used to obtain 2 rotating traces of 10 MB each. This size can be adjusted
according to the number of tickets recalculated and the results obtained (loss of information or not).

The analysis is done by consulting the following logs successively:
NMCCostRecalculation_CostCalculation then NMCCostRecalculation
Warning
The carriers used must be validated for the period recalculated (check the start and end validity dates).
7.4. Data totaling
− The log file concerned is NMC_CumulAcc.

To obtain extended traces, the management differs according to the version installed:
Modify the file 8770\client\bin\NMCCumulAcc.properties
On the first line, replace info by debug.
− The unit data from the "ticket" table are totaled in different tables to speed up report generation.
This is a pre-processing of the base data. This task is programmed by default in the daily and weekly
jobs. It can also be executed from the Accounting application (Total calculation).
The data totaled are:
• Duration
• Number of calls
• Costs
These three types of data are totaled for the following objects:
Object Destination table Source table

E - Entities (sets) EntityDailyCounter (+monthly+yearly) chargeableentity
O – Cost centres and levels OrgDailyCounter (+monthly+yearly) organisation
P – Project codes ProjectDailyCounter (+monthly+yearly) Chargeableentity (entity type=6)
C – Carriers CarrierDailyCounter (+monthly+yearly) Carrier
D – Directions DirectionDailyCounter (+monthly+yearly) Direction
N - City/Country name (CCN) CcnDailyCounter Ccn

Note
By default, the total is not done on the project codes in the daily and weekly tasks. If necessary, the task
can be created in the scheduler.
For specific requirements, it is also possible to select certain particular call types for a recalculation.
Note
In the daily and weekly tasks, by default only the totals on the following call types will be calculated:
Inc./Out. calls, Incoming calls, Outgoing calls.
To add the other types of calls, you must modify the predefined arguments in the Task definition
tab for the Organization cumulative counters calculation task

com.alcatel_lucent.nms8770.appl.client.apps.accounting.cumulative.CounterCalculator -New -Half -
Daily -Monthly -Yearly -Table E,O,P,C,D,N -AccType
IN_OUT,IN,OUT,PRV_OUT,IN_DISA,OUT_DISA,SUB -ACC -PtpType ALL -PTP -VoipType ALL -VOIP -
Detect Yes -Notify Yes -MaxAlarms 50 -TraceType NMCL_ALL -TraceFile "" -TraceTime 1 -LdapLogin
"$SCHED_OWNER" -LdapPassword "$SCHED_PASSWORD" -LdapHost "$SCHED_LDAPHOST" -LdapPort
"$SCHED_LDAPPORT" -LdapDN "$SCHED_LDAPNMCDN" -Host "$SCHED_HOSTNAME"
The abbreviations corresponding to the optional totals are:
• IN_DISA : Tickets for incoming DISA calls
• OUT_DISA : Tickets for outgoing DISA calls
• PRV_OUT : Tickets for outgoing personal calls
• SUB : Subscription tickets
Example of modification for totaling subscription tickets:
-Table E,O -AccType IN_OUT,IN,OUT,SUB -ACC
− It can be useful to consult the data provided by "Tracking Status" to assess the totaled data for the
number of calls, durations and costs of the different entities of the organization.
Open the Account/traf/VoIP application :

7.5. Loading to the base
The log file concerned is NMCExtractor (preferably in extended trace –TraceType --1).
Report generation constitutes the final phase of the accounting process. In case of doubt or dispute over
the data obtained, the previous steps must be reviewed with the investigation elements detailed in the
previous chapters.
In the event of a problem, to distinguish between the base data and the totaled data, it is important to
know on which table a report is based. This information is inferred from the Definition field of each
report definition:
Accounting – Ticket ==> Ticket table
Accounting – Entity – Daily ==> EntityDailyCounter table
7.6. Description of some special cases and solutions
− Unanswered calls (incoming and outgoing) do not appear in the reports.

 Validate the loading of tickets with duration = 0
− The data from a detailed report are different from those from a totaled report.
 Check the ticket conservation duration in the base in the administration application :
nmc\Omnivista8770\ServerName\nmcdatabase
“cleanticketandaffiliatedoldthan” parameter.

It is likely that the monthly table used for the totaled report contains data that no longer exist in the
"ticket" table used to generate the detailed report.

7.7. Summary of the main investigation stages
Below are the main investigation stages if a partial or total absence of data in a report is noted:
− Check the presence of the tickets on the PCX (case of an OmniPCX Enterprise)
accview
− Has the file concerned been transferred?
Name of the last file transferred
− Has it been loaded into the base or is it still waiting to be loaded or has it been rejected?
NMCLD_x.log under 8770\data\loader\...
− Check the table on which the report is based
Name of the definition \definition
− If it concerns a totaled table, make sure the totals have been made
NMCCumulAcc_x.log and Daily tasks report
− Is there a problem with a similar predefined report definition or is the problem just with a specific
report created for the client?
ALE Technical Support cannot help you debug customized reports.
You can contact ALE Professional Services for assistance.
− If the investigations described in this document do not enable you to solve the problem, open a
Service Request and include the elements necessary for an investigation:
Detailed description of the problem (call type, call date)
Log files
Report definition
Report export
PCX ticket in .dat format
PCX ticket in text format

8. TRAFFIC OBSERVATION
This chapter contains a summary of the information which is useful for understanding the different steps
in the Traffic Observation process for the OmniPCX Enterprise PCXs. The main aim is to provide
investigation elements from file generation on the PCX through to report generation with OmniVista
8770.
This procedure must be applied by OmniVista 8770 experts. It is an essential stage prior to any help
request made to ALE Technical Support.
8.1. Traffic observation on the pcx side
The Traffic Observation tool is an evaluation tool which is used to obtain dimensioning information for
certain OmniPCX Enterprise resources (attendant sets, trunks, etc.).
The aim is not to have absolutely precise figures at a given time, but to observe the evolutions over time.
Refer to the chapter 9 TRAFFIC PERFORMANCE COMPARISON for explanations about certain apparent
differences between the results obtained on the one hand by accounting reports and on the other by
Traffic Observation reports.
The files are generated under /usr4/pmm.
Cwwdnnoo.pmm These are the data files created every half hour. They are retrieved by the OmniVista
87700.
ww : week number
d : indication of the day U : Sunday
M : Monday
T : Tuesday
W : Wednesday
J : Thursday
F : Friday
S : Saturday
nn : corresponds to the half hour observed (00 to 47)
oo : index from 00 to 99
Cwwdxxnn.pmm These are the accumulated data files per day. They are created at midnight. They
are not retrieved by the OmniVista 8770.
Cwwdxxnn.inf These are the configuration files which are saved every day at midnight or every
time the Traffic Observation starts. They contain all the instance data (MCDU, Cost
center, Name, etc.) observed by the Traffic Observation for the periods which will
follow. It should be noted that if the user modifies the management, these
modifications will only be taken into account the next time these files are saved.
They are retrieved by the OmniVista 8770.
Pmm2.lis File containing the list of files C*.pmm and C*.inf generated (it is updated every
half hour).
It is retrieved by the OmniVista 8770.

The basic Traffic Observation data comes essentially from the half-hourly .pmm files. However, certain
reports also extract part of the information from the Traffic Observation and accounting tickets:
• Called Numbers ("incoming" calls direct to the terminals)
• Terminals ("incoming" calls handled by terminals)
If we want to use this type of report, the storage of accounting tickets in compressed files (files for
external accounting) must be validated on the PCXs.
As the useful information is taken from the incoming tickets, you must also authorise the storage of this
type of ticket by management filter.
Relevant commands
dbgobs –r [filename pmm or inf] Read the content of the files

obsappli Utility used to view the data per half hour or day.
Must be launched from /usr4/pmm
account –v Display the accounting configuration
8.2. Data download by omnivista 8770
The Traffic Observation must be authorised by the OmniVista 8770 licence (Traffic performance lock)
The following trace files must be analysed to investigate the accounting file download function:
• NMCComserver.log (connection to the PCX)
• NMCSyncLdapPbx.log (PCX synchronization and FTP transfer)
If no Traffic Observation file is downloaded during a synchronization, a "warning" level alarm is
generated:
10019 There's no traffic observation files to download from this call
server
The Security Guide documentation provides useful information about the ports and protocols used for
the data transfer.
File download is started by the synchronization task
• The Ptp Process option is validated.
• The Accounting Process option is left at No if this functionality is not used. The ticket files
will, however, be downloaded to extract certain Traffic Observation data.
• OmniVista 8770 downloads the file pmm.lis by ftp. It contains the list of available files. The
account used for the transfer is adfexc.
ftp username: adfexc
ftp password: same as the one managed at the PCX end (adfexc by default)
Where appropriate, test the account by an ftp connection from a DOS window.

• OmniVista 8770 downloads, by ftp, the new files available since the last synchronization. The
name of the last file downloaded is read in the field: Last polled Ptp file (“Data
Collection” tab).
• The files are saved in a directory
8770\data\loader\network=xx\subnetworknodenumber=yyy
The files present are used by the loader for information insertion in the database.
8.3. Traffic observation on the pcx side
By default, only the data in the following objects are loaded:

− Attendants Group.
− Attendants.
− Trunk Groups.
−
Where necessary, validate other objects and manage the complementary information.

8.4. The Log File
The log file (8770\log) concerned by the loading in the base is NMCLD
The file contains the name of the files handled and the information about the elements inserted into the
base.
First of all, the useful accounting ticket information is extracted and loaded:
-(*** PTP_SUB ***) End Loading CountersSub in Base

-( PTP_SUB ) Nb Total ==> TicketsIncommingRead = 175
-( PTP_SUB ) Nb Total ==> CountersInMemoryBeforeDB = 149
-( PTP_SUB ) Nb Total rejected by DayHourFilters = 0
-( PTP_SUB ) Nb Total rejected CompanyAndCCFilters = 0
-( PTP_SUB ) Nb Total ==>EntityId not found = 13
-( PTP_SUB ) Nb Total ==> CountersRegectedbecauseEntityId not found = 40
-( PTP_SUB ) Nb ==> CountersInsetedInSub30mn = 105
-( PTP_SUB ) Nb ==>CountersUpdatedInSub30mn = 4
-( PTP_SUB ) Nb Total ==>CountersUsedInSub30mn = 109
Then the data in the .pmm files is loaded
Net.Subnet.Pbx[PbxName]
Candidates=Inserted+Updated+FilteredOut+WithoutKey+AllZero+InfZero+DbRejected
-0.6.604 [Nd4] ATT: 255 = 31 + 0 + 0 + 0 + 224 + 0 + 0
-0.6.604 [Nd4] ATG: 34 = 34 + 0 + 0 + 0 + 0 + 0 + 0
-0.6.604 [Nd4] TRG: 153 = 41 + 0 + 0 + 0 + 112 + 0 + 0
-0.6.604 [Nd4] SUB: 17051 = 122 + 12 + 0 + 0 + 16917 + 0 + 0
-0.6.604 [Nd4] HDS: 11951 = 182 + 0 + 0 + 0 + 11769 + 0 + 0
-0.6.604 [Nd4] BST: 1564 = 379 + 0 + 0 + 0 + 1185 + 0 + 0
-0.6.604 [Nd4] DCT: 17 = 16 + 0 + 0 + 0 + 1 + 0 + 0
-0.6.604 [Nd4] APM: 7344 = 110 + 0 + 0 + 0 + 7234 + 0 + 0
-Total (17 files) 38369 = 915 + 12 + 0 + 0 + 37442 + 0 + 0 Duration = 12s Rate
= 3197 candidates/s (1s /file)
[24/10/2006 09:57:54] 6992 LD: inserted files : 17

[24/10/2006 09:57:54] 6992 LD: rejected files : 0
If a loading problem occurs, an alarm is generated with a diagnostic number between 17000 and
17020. Refer to the Technical Communication TC0823 List of OmniVista 4760 internal alarms.
Any rejected files are contained in the directory
8770\data\loader\network=xx\subnetworknodenumber=yy\rejected

8.5. Main SQL tables
The data extracted from the accounting tickets and the .pmm half-hourly files is inserted into half-hourly
tables whose names finish with "30mn". For each object there are daily, monthly and yearly tables.
Name Object
Atg30mn Attendant Groups
Att30mn Attendants
Sub30mn Terminals and Called numbers
Trg30mn Trunk Groups
Bst30mn DECT bases
Dct30mn DECT system parameters
Hds30mn DECT/PWT Wireless sets
Apm30mn DECT ADPCM channels
The description of the columns in all these tables is provided in Appendix 2.
8.6. The data totaling
The unitary data from the half-hourly tables is totalled up in daily, monthly and annual tables to
accelerate report generation. This is a pre-processing of the base data. This task is programmed by
default in the daily and weekly jobs. It can also be executed from the Accounting application (Total
calculation).
The screen shot below shows a totalling example for the day of 24th September.

Warning
By default, only the following tables are totalled in the daily jobs:
− Attendant Groups (ATT).
− Attendants (ATG).
− Trunk groups (TRG).
This corresponds to the data loaded by default. Refer to the paragraph Loading parameters.
If data which corresponds to other objects is loaded, the "Traffic performance cumulative counters
calculation" job arguments must be modified in the scheduler. You must add the additional tables
you want to total.
For a workload question, it is best to only validate the tables likely to be used to generate reports:
-PtpType ATT,ATG,TRG,DCT,BST,APM,HDS,SUB
If all the tables must be totalled, the argument may be -PtpType ALL.
Becarefull : do not delete -PTP
The log file concerned by the totalling is NMC_CumulPtp.log.

To obtain extended traces, the management differs according to the version installed:
Modify the file 8770\client\bin\NMCCumulPtp.properties
On the first line, replace info by debug.

8.7. The Report generation
The Report generation constitutes the final phase of the Traffic Observation process. In case of doubt or
dispute over the data obtained, the previous steps must be reviewed with the investigation elements
detailed in the previous chapters.
In case of issue, to distinguish between the base data and the totalled data, it is important to know on
which table a report is based. This information is inferred from the content of the Definition field of
each report definition:
In this example, the definition is based on the Terminals and Called numbers daily table:
Subdaily
The data in this table is obtained by totalling the Sub30mn data.
Precision on a few types of report
− Called numbers (public incoming calls initial dialled number) reports
We observe how the incoming public calls intended for a particular set number are handled.
When the data is extracted from the incoming accounting tickets, an analysis is performed in relation
to the InitialDialledNumber field which is the number called initially. It is used to determine
what happens to the calls:
• Direct answer on the called set,
• Answer after overflow to another set,
• Response delay in relation to thresholds T1 and T2,
• Caller abandon.
The results are recorded in the Sub30mn table which contains the columns which characterise the
different processing cases for the calls.

The data in the "Called number" reports are extracted from these fields.
Column Description
NrIniTakDir1 Call taken by the initial destination before T1
NbrIniTakDir12 Call taken by the initial destination between T1 and T2
NbrIniTakDir2 Call taken by the initial destination after T2
NbrIniTakRed1 Call taken by another set before T1
NbrIniTakRed12 Call taken by another set between T1 and T2
NbrIniTakRed2 Call taken by another set after T2
NbrInAbdDir Call abandoned by the caller before answer while ringing on the initial destination
NbrInAbdRed Call abandoned by the caller before answer while ringing on the end set
Notes
1 In a "Called number" report on a set (number) X, we analyse what has happened to the calls
initially intended for it. Therefore, this does not include the calls taken by this set X after
overflow, transfer or call forward which were not initially intended for it.
2 The secondary call numbers of multiline sets and PCX group numbers are not analyzed.
− Terminals (First answer to public incoming calls) reports

These reports describe the quality of the first answer to the incoming public calls (reponse or
abandon). This information is extracted from the incoming accounting tickets.
It takes account of the calls which looked for a set independently of the initially called number. This
concerns the calls obtained either directly or by interception, overflow or forward.
It excludes the calls obtained by set transfer or routing by attendant (real or automatic)
(these are not first answers).
While data is extracted from the incoming accounting tickets, an analysis is performed in relation
to the ChargedNumber field to determine what happens to the calls:
• Answer
• Cancel
The results are recorded in the Sub30mn table which contains the columns which characterise the
2 processing cases for the calls.
The data in the "Terminals" reports are extracted from these fields.
Column Description
NbrCHgTak Calls answered
NbrChgAbd Calls abandoned by the caller before answer
In addition, the reports provide conversation duration information for local outgoing and incoming
public calls. This data is extracted from the .pmm Traffic Observation files.

Note
1 In this type of report, the call numbers come from accounting tickets, while the durations
come from the .pmm Traffic Observation files.
2 In a "Terminals" report, there may seem to be an inconsistency between the number of
incoming public calls and the conversation duration for this same type of call.
This is due to the fact that for the number of calls we exclude the calls obtained by set transfer
or attendant routing (real or automatic) although the duration of these calls is totalled.

8.8. The troubleshooting
8.8.1. The summary of the main investigation stages
Below are the main investigation stages if a partial or total absence of data in a report is noted:
Check the presence and content of the half- Dbgobs –r filename

hourly.pmm files on the PCX. The presence of the
corresponding .inf file is vital
Have the files concerned been transferred? Name of the last file transferred
Has the base been loaded or are the files still NMCLd_x.log 8770/data/loader/...
waiting to be transferred or rejected?
Check the table on which the report is based Name of the definition \definition
NMCCumulPtp_x.log
If it concerns a totalled table, make sure the totals / Daily tasks
have been made report
Is there a problem with a similar predefined report Ale Technical Support cannot help you debug
definition or is the problem just with a specific customized reports.
report created for the client? You can contact Ale Professional Services for
assistance.
If the investigations described in this document do Detailed description of the problem (call type, call
not enable you to solve the problem, open a date)
Service Request and include the elements Log files
necessary for an investigation Report definition
Report export
.pmm half-hourly files with the corresponding
.inf file.
Capture of the file content in text mode.

8.8.2. Randomly, there are some holes (no value present) in the statistic reports
This issue can be checked in the database as shown below
Data missing
1. Check the ODBC driver version
There is an issue on the SQL driver 2.0.15 (release 3.2.08.x).

Please check the technical alert TC2445 (purge doesn’t work correctly)

2. The issue is appeared after a rehosting or long period without synchronisation
Apply the procedure below :
1. Change the value below from “2” to “30”
2. Delete the last .pmm file retreived
3. Launch a synchronization complete-separate

4. Check the loader status in the scheduler and the the presence of .pmm file in
8770/data/loader/networknumber=x/subnetworknumber=x
Warning This operation can take several hours

To check everything works correctly, you can check the timestamp of the loader log
(8770/log/MNCLD_x.log)

9. TRAFFIC PERFORMANCE COMPARISON
9.1. Introduction
So-called "crossover" observations between accounting data and traffic performance data (Past Time
Performance – PTP) are often difficult to interpret.
The aim of this chapter is to describe the specific details for each of these two applications.
These comparisons can be made between:
- incoming accounting tickets and called extensions on PTP in terms of the number of calls and
the duration,
- the number of outgoing accounting tickets and the number of outgoing allocations per trunk
group on PTP,
- the number of incoming accounting tickets and the number of incoming allocations per trunk
group on PTP,
- the total accounting duration (incoming or outgoing) per trunk group and the total allocation
duration (incoming or outgoing) per trunk group on PTP.
9.2. Principe of Traffic performance operation in OmniPCX enterprise
The traffic performance in the OmniPCX Enterprise is an evaluation tool for PABX traffic, which is used
to determine whether the system is suitably dimensioned with regard to real traffic, or whether there
may be insufficient resources during certain periods (for example, an insufficient number of trunk lines).
Note For an OmniPCX Enterprise in a network, PABX clocks are sources of inaccuracies. These clocks are
not the same on all nodes (even if the clocks have been synchronized, there may be differences of
several minutes). These differences depend on the clock synchronization plan and the network
architecture, and mean that the half-hour periods used to calculate the traffic observation results are
not the same on the different nodes in the network (for example, 10:00-10:30 on node x is not the
same as 10:00-10:30 on node y).
9.3. Differences between traffic performance and accounting operation in

OmniPCX Enterprise
9.3.1. Example N°1
Trunk group N° 200

Total number of PTP calls : 699
Total number of accounting calls : 708
Difference :9
Total PTP duration : 19:39:58

Total accounting duration : 17:40:23
Difference : 01:59:35, or approximately two hours
It is normal for the total PTP duration to be greater than the accounting duration.
The difference in duration divided by the number of calls, in other words approximately 2 hours/700 =
10 seconds per call, shows an average time which represents the ring back tone time (reservation time
for a resource on the trunk group before the remote subscriber off-hooks, see explanation in paragraph
9.3).
9.3.2. Example N°2
Trunk group N° 201 (dedicated trunk group for calls to GSM networks)
Total number of PTP calls : 142

Total number of accounting calls : 147
Difference :5
Total PTP duration : 02:59:01

Total accounting duration : 02:17:51
Difference : 00:41:10
The average waiting time before off-hooking is approximately 17 seconds, slightly greater than for trunk
group N° 200 (example N° 1). This seems logical as this is a dedicated trunk group for mobile network
calls, and therefore has a longer call routing time.
9.3.3. Example N°3
Trunk OmniPCX Enterprise network with two nodes
ABC-F link
Node 1 Node 2
The total for incoming calls counted on Node 1 is not the same as the total for outgoing calls on Node
2 for the 10:00 – 10:30 and 10:30 – 11:00 periods.

Period Node Out. Inc. calls Total Node Out. Inc. calls Total N1->N2 N2->N1 Duration
calls duration calls duration call call difference
difference difference
10:00- N1 422 395 18:12:25 N2 395 430 18:08:05 8 0 0:04:20
10:30
10:30- N1 429 442 18:10:35 N2 447 440 17:57:05 11 5 0:13:30
11:00
These differences can easily be explained by the mechanisms detailed in chapter 9.2. The differences
noted are only around 2% and do not compromise the aim of traffic observation.
9.4. Conclusion
Accounting and traffic performance are two applications which have been designed for different needs.
Comparing the reports from the two applications shows the differences in certain counts. A superficial
comparison of the results from the two applications should not be carried out.

10. DISK QUOTA EXCEEDED: SERVER STOPPING
This chapter describe how to solve disk capacity overflow when the server is stopped cause of disk
quota exceeded.
10.1 Presentation
Permanently, Omnivista 8770 server is controlling disk capacity of the server to prevent any issue
with system disk capacities.
We recommend you to setup your server by respecting the values of disk size according to the
installation guide and the Installation procedure for Omnivista 8770.
By default, the server ensures a correct functioning of applications with the following sizes:
First Threshold Second Threshold

Applications Directory (directory size or (directory size
percent values) percent values)
A4400SaveRestore \8770_ARC\OXEBackup 350 Mb 500 Mb
OxoSaveRestore \8770_ARC\OXO\data 350 Mb 500 Mb
OTSaveRestore \8770_ARC\OTBackup 8Gb 12Gb
NmcSaveRestore \8770_ARC\8770Backup 6Gb 8Gb
OXESoftwareDownload \8770_ARC\dhs3mgr 1,5Gb 2Gb
OxoSW \8770_ARC\OXO\sw 1Gb 1,5Gb
Accounting \8770_ARC\Accounting\tickets 50% 35%
LdapPath \8770\SunONE 30Gb 15Gb
NmcPath \8770 20% 10%
WebClientSessions \8770\Client\sessions 2% 1%
- First threshold: depending on the tracking type, it corresponds to available hard drive
space or archive size. A minor alarm is transmitted when the threshold is reached

- Second threshold: depending on the tracking type, the available hard drive space or the
archive volume value. A major alarm is transmitted when the threshold is reached
As a consequence of low free disk capacity, the threshold 2 is exceeded then you cannot connect
to the 8770 server :
“Unable to connect to the server” in client logging.
OmniVista service manager is stopping all OmniVista services, SQL server and LDAP server, except
itself.
This will happen also at next restart of server PC, until free capacity is recovered or until disk
control is modified (of course if it was overestimated).
10.2 8770 logs
Looking at 8770\log\ NMCsvc_mgr_1.log file you can find this example :
Unable to login to the 8770 application.

There is a pop-up unable to connect to license server' and then the end result is ‘unable to connect to
server’.
In the logs we could see the following:
[12/9/2015 9:43:00 AM] 1368 svc_mgr: Warning: maximum disk limit reached for Accounting
[12/9/2015 9:43:00 AM] 1368 svc_mgr: Warning: intermediate disk limit reached for DatabaseSettings
[12/9/2015 9:43:00 AM] 1368 svc_mgr: Warning: intermediate disk limit reached for LdapPath
[12/9/2015 9:43:00 AM] 1368 svc_mgr: Warning: maximum disk limit reached for NmcPath
[12/9/2015 9:44:30 AM] 1368 svc_mgr: Warning: maximum disk limit reached for DatabaseSettings
[12/9/2015 9:44:30 AM] 1368 svc_mgr: Warning: maximum disk limit reached for LdapPath
[12/9/2015 9:44:30 AM] 1368 svc_mgr: Error: Not enough diskspace : LDAP [THRESHOLD2] - SQLA
[THRESHOLD2]
[12/9/2015 9:44:30 AM] 1368 svc_mgr: NMC service : svc-mgr will be stopped to prevent data crash
[12/9/2015 9:45:13 AM] 1240 svc_mgr: NMC service : DirectoryServer7-1 will be stopped to prevent
data crash
[12/9/2015 9:45:23 AM] 1240 svc_mgr: Error: _wsystem on DirectoryServer7-1 error code: 0 (errno:2)
[12/9/2015 9:45:23 AM] 1240 svc_mgr: NMC service : MySQL8770 will be stopped to prevent data
crash
[12/9/2015 9:45:26 AM] 1240 svc_mgr: Error: _wsystem on MySQL8770 error code: 0 (errno:2)
[12/9/2015 9:45:26 AM] 1240 svc_mgr: bye, bye!When inserting a warning and/or note, please use
the following warning and note tables:
10.3 Check current control
To detect current control of disk capacity:

- Stop "NMC service manager".
- Start only "Oracle Directory Server Enterprise Edition" service.
- Launch 8770\bin\DirManag.exe
- Connect to ldap server with this setting:
Hostname =Localhost
Login = Adminnmc
- Locate both entry

NMC > OmniVista 8770 > servers > ServerName > NmcArchive > LdapPath
NMC > OmniVista 8770 > servers > ServerName > NMCArchive SaveRestore
- For both entry check the following attributes.

Threholds Ldap values
Patch To get the drive letter
Check "disk", means check of free disk capacity
Threshold1 If this threshold is exceeded, an alarm is sent
Threshold2 If this threshold is exceeded, OmniVista 8770 is blocked
10.4 Solution
If OmniVista 8770 is blocked due to exceeding of disk threshold, stop all services except "
Oracle Directory Server Enterprise Edition " and apply on the three following solutions.

10.4.1. Clear unnecessary files
Remove all unnecessary files under the drives used by NmcDatabase and LdapPath.
Restart the server.
10.4.2. Decrease disk control
Reduce the value of threshold 1 and 2 as show in paragraph 3 above

Ctrol S to save the changes
Restart the Server
Warning Threshold values must be modified carefully. Contact Technical support for further information
or advises about those values.
10.4.3. Move 8770 files to another drive
It may happen OmniVista 8770 is installed on "C:" drive with current capacity reduced. Taking into
account you have already Windows operating system, cache file of Windows, 8770 binaries and
database; you can be out of free space. Decreasing control will only lead to a major crash of the
OmniVista 8770 database service will not be able to find any space for starting, reindex operation
and finally get corrupted.
As alternative, you can move SQL database files or the 8770 Archive folders to another location and
recover some free space.
Notes Make a 8770 backup using command line in DOS windows: 8770backup.bat save
10.4.4. Moving SQL Server database
SQL SQL database is the major file in terms of capacity. If you need to move it to another
location, follow carefully the steps below:
1. Create the new folder d:\8770\data

2. Move the folder “data” from c:\8770\data to d:\8770\data

3. Launch 8770\bin\DirManag.exe
4. Connect to ldap server with this setting:
Hostname =Localhost
Login = Adminnmc
5. Select entry :
NMC > OmniVista 8770 > servers > ServerName > NmcDatabase > DatabaseSettings
6. Change path from c:\8770\data to d:\8770\data. Same modification for
“rebuildtempdirectory”.

7. Ctrl + s to save the changes
8. Register the new path for backup and update Edit the restoreContext.ini file under c:\8770 :
replace szDataBase=c:\8770\Data by szDataBase=d:\8770\DataReplace

9. Modify the starting MariaDb settings ( C:\Program Files (x86)\MariaDB 5.5\data ) , edit the
my.ini file
10. Modify all references to C:\8770\data by D:\8770\data as below:

11. Restart the server.
10.4.5. Moving backup and temp files
The second main files concern backup and temp files located in 87780_ARC folder. If you need to
move it to another location :
Copy the Archive folders:

1. Create D:\8770_ARC
2. Move the folders under C:\8770_ARC to D:\8770_ARC, to get:
3. For folder D:\8770_ARC\OXO\data, check the sharing is kept : still = OXO-Databases

4. Restart the server PC.
5. Register the new archive path in 8770 system directory by starting the OmniVista 8770 Client.
6. Launch Network -> Maintenance application.
7. Select menu Preferences > Maintenance > Configuration
8. Change the directory in all the tabs: OXEBackup, OT backup, OXE configuration : From
C:\8770_ARC to D:\8770_ARC
9. Launch Setup -> Maintenance application

10. Select menu Preferences > Maintenance > Configuration

11. Change the directory in all the tabs Backup/restore and temporary files : From C:\8770_ARC
to D:\8770_ARC
12. Register the new path for backup and update

13. Edit 8770\RestoreContext.ini file
14. Replace 8770ArcPath=D:\8770_ARC by 8770ArcPath=d:\8770_ARC

11. REPORT
This chapter contains a summary of information which is useful for configuration about report.
11.1 Export format
Four formats are possible :
11.1.1 TXT Report
This is txt file using Tab as column as separator.

It is a rough export of the data extracted by the report generation. We do not take into account the
modification of data presentation in the designer (formula, chart, graph, data masking)
Note There are always 40 columns in the report, so each line will include additional Tab character if less than
40 fields selected in the Requester.
11.1.2 PDF Report

Font family and style can be specified for the PDF export as shown below

Example :
“Trebuchet MS” font
“Tahoma” font
11.1.3 EXCEL Report
We take into account part of the modification of data presentation in the designer:
data masking, order of cell, result of formula.
Note Formula definitions and charts are lost. All cells are exported as text only: you cannot update excel file by
adding a formula.

11.2 Scheduled export
11.2.1 Options
11.2.2 Scheduled Export as file to a printer
- The printer selected must be defined as default printer

- Appropriate Windows rights must be given to “ExecdExc” as shown below

11.2.3 Scheduled Export as file (network drive)
- Network drive must be mounted

- Appropriate Windows rights must be given to “ExecdExc” (see paragraph “schedule Export as
file to printer”)
- Appropriate Windows rights must be given to “SaveRestore” as shown below

It’s possible to export a report on the network drive but not via the scheduler as shown below
- If we try to export the report which is already generated, there is no issue to save on the
mapped network drive.
- If we schedule a report, I could see only the local hard disks to select the location to save
the report.
-
Solution :
1) Create a scheduled export on the local drive

2) Then replace the path (“filename” field) by the UNC path of the network drive (“scheddef”
table)

Replaced by \\172.27.132.239\ccd\temp\DetailledReport.
The system will add some escape character (“\”) to give this result
\\\172.27.132.239\\ccd\\temp\\DetailledReport
11.2.4 Scheduled Export as file to an email server
- Configuration of email server as shown below
- Appropriated Windows rights must be given to “ExecdExc” (see paragraph “schedule Export
as file to printer”)
Process :
Schedule report with mail export are generated in 5 steps:

1. Scheduler will access to the database to retrieve filter option and e-mail option.
2. Extractor service generate the report.
3. Export to a temp file under windows temp folder.
4. E-mail of the temp file.
5. Temp file deletion.

11.3 Configuring
11.3.1 Configuration report size limits
You should not generate a detailed report on the full database. Trying such action requires CPU
time, RAM memory space and ability to handle huge file. This is not only OmniVista 8770 limitations
but also linked to your PC performance and IT environment.
For instance:
− Export a large PDF files will take a huge memory and time.
− Viewing a huge html file could be rejected by the HTML browser.
− Your e-mail server may reject report > 10 Mb.
− Test to print a report may result in printing thousand of not useful page.
We have set default limitation value to generate useful report that can
be generated quickly and take few disk capacity. There will be a message “The report has been
truncated to the requested size” if your request are beyond the limitation.
Number of line can be defined as shown below
These parameters are presents directly on the application too :

11.3.2 Date Options
The date format used by the application depends on the language – country selected by the client.
These rules are the official rule applied by java application.
Examples of date:
French (FR) Day/Month/Year Hour:Minute (i.e.: 16/11/06 22:03)
English (EN_GB) Day/Month/Year Hour:Minute (i.e.: 16/11/06 22:03)
American (EN_US) Month/Day/Year Hour:Minute AM/PM (i.e.: 11/16/06 10:03 PM)
11.3.3 Scheduled export as email
There is no indication about the email address used in the scheduled export as email.
To be able to identify this kind of task, add a comment in the description as shown below

11.3.4 Export parameter
A parameter exists to optimize the resources during the generation of a large report.
In the generation options, the item Check memory for large exported reports is proposed.
Another limitation exists for the Extractor service, a field for the number of simultaneous Thread is
added, the initialisation value is 8 (maximum value), the optimum value is 4 and the minimum is 2.
11.4 Purge
The purge is generated automatically with the daily & weekly jobs
Main parameters :

Warning The data from the detailed Traffic Analysis will be purged by default after 45 days while the
same data cumulated in daily tables will be purged after 94 days.
As a consequence, a report for last month (example) based on detailed data can be incomplete
while the one based on cumulated data will be complete.

All purge parameters are located in Database Setting (DO NOT CHANGE THESE VALUES
WITHOUT AGREEMENT OF ALE TECHNICAL SUPPORT)
11.5 Limitation
11.5.1 Data comparison

You cannot compare data between following application:
− Accounting and Performance,
− Performance and CCD/CCS statistics.
All these applications have their own data source and field definition:
− Accounting data are based on PCX CRD (communication record detail),
− Performance data are based on PCX statistic counter,
− CCD statistic are based on counter generated by CCD application.
11.5.2 Filter limitation

When defining a report filter, this filter is added to the report SQL query. This global query is limited
in size, around 1024 characters. The query string is not available. When you add filter and query
may exceed this size the button add new filter will be disabled.
Workaround: If you need to perform a report on a list of 20 subscribers:

− First define an attribute common to all these subscribers.
− Then perform a report on this attribute.
11.5.3 Scheduled export

Do not export several reports at the same time.

11.6 Troubleshooting
If problem occurs, check extractor logs :

- NmcExtractor_X.log
- NmcExacdexc_X.log

12. SNMP
This chapter describes the investigations to carry on in the cases about Opentouch alarms. Last
chapter helps to investigate around SNMP proxy and traps sending to hypervisor.
12.1. Opentouch and 8770 configuration
12.1.1 Opentouch
It is In Opentouch configuration, Eco system / IT server / <Server SNMP declared >
12.1.2 Omnivista
In configuration settings of Opentouch (connectivity)

12.2. Checking and test
12.2.1 Check the configuration file
As soon as the connectivity settings are set, the config file

\8770\data\config\netsnmp\snmptrapd.conf is created and updated with the following entries :
createUser adminsnmp498 SHA "superuser" AES "superuser"

authUser log,execute,net adminsnmp
authCommunity log,execute,net public

12.2.2 Check the SNMP services
From 4.0, the SNMP service is provided by the 8770. Make sure it is well started :
For the others version, SNMP is handled by the windows Operating system started by itself, “SNMP
service”
12.2.3 Sending an alarm
The alarm can be sent by 2 ways :

- Stop/start service :
[root@ice1 iceuser]# service snmpd restart

Stopping snmpd: [ OK ]
Starting snmpd: [ OK ]
- Sending snmpinform command under root is the most appropriated test :
Example :
snmpinform -v 3 -u < SNMP account > -l authPriv -a SHA -A <SNMP password> -x AES -X
<SNMP password> <8770 server ip address> 42 coldStart.0

[root@ice1 etc]# snmpinform -v 3 -u adminsnmp498 -l authPriv -a SHA -A superuser -x AES -X superuser
10-10-1-61.labo10.fr 42 coldStart.0
[root@ice1 etc]#
This test validates:

- OV8770 server FQDN resolution by OT
- The SNMP configuration at OV8770 side
Traps located in NMCFaultManager_ICEService_1.log:

[20/08/2015 16:26:14] 5004 FaultManager_ICEService: CAlarmHdlr::parseMsg() start
[20/08/2015 16:26:14] 5004 FaultManager_ICEService: Error: CAlarmHdlr::parseMsg() 1:Bad alarm message:
ice1.labo10.fr UDP: [10.10.1.31]:53649->[0.0.0.0] SNMPv2-SMI::mib-2.1.3.0 = Timeticks: (42) 0:00:00.42
SNMPv2-SMI::snmpModules.1.1.4.1.0 = OID: SNMPv2-SMI::snmpModules.1.1.5.1.0 <EOF>
The error will be the same as in chapter Error cases
12.2.4 Logs
The ams.log is under /logs/omp/ams
2015-08-25 17:03:45,498 INFO [com.genesyslab.PCT.invoker.eventBroker.defaultInvoker] c.a.i.o.a.r.g.MsgServerGtwImpl

[MsgServerGtwImpl.java : 267] message received: 'EventLogMessage' (11101) attributes:
x_entry_text [str] = "Application terminated due to internal condition"
x_log_app_id [int] = 118
x_log_category [int] = 0 [Application]
x_log_message_header [str] = "17:03:45.493 Standard ice1.labo10.fr NetSNMP_1 GCTI-00-05064 "
x_log_time_generated [str] = "2015-08-25T15:03:45Z"
x_log_entry_id [int] = 5064
x_log_usec [int] = 493740
x_log_hostname [str] = "ice1.labo10.fr"
x_log_application_name [str] = "NetSNMP_1"
x_log_priority [int] = 4 [Error]
2015-08-25 17:03:45,502 INFO [LogProcessor] c.a.i.o.a.s.AbstractAms [AbstractAms.java : 128] Received notif: Key: 43-
10385 Notification Time: 1440515025493 HA primary role: true Host: ice1.labo10.fr CName: 43 IName:
SolutionControlServer_1 param: 'OT_1' context:
2015-08-25 17:03:45,503 INFO [LogProcessor] c.a.i.o.a.r.g.MsgServerGtwImpl [MsgServerGtwImpl.java : 325] Log
received: appId: 118 logId: 5064 notifTime: Tue Aug 25 17:03:45 CEST 2015 text: Application terminated due to internal
condition context:

2015-08-25 17:03:45,506 ERROR [LogProcessor] c.a.i.o.a.r.g.LogConverter [LogConverter.java : 158] Unknown mode:
Exiting
2015-08-25 17:03:45,507 ERROR [LogProcessor] c.a.i.o.a.r.g.LogConverter [LogConverter.java : 159] Primary mode is
used
2015-08-25 17:03:45,507 INFO [LogProcessor] c.a.i.o.a.s.AbstractAms [AbstractAms.java : 128] Received notif: Key: 0-
5064 Notification Time: 1440515025493 HA primary role: true Host: ice1.labo10.fr CName: 23 IName: NetSNMP_1
context:
2015-08-25 17:03:45,526 INFO [SnmpNotificationProcessor] c.a.i.o.a.s.Snmp4jV3Session [Snmp4jV3Session.java : 123]
Sending inform 43-10385 to host 10-10-1-60.labo10.fr on port 162
12.2.5 Error cases
The most current errors are:
user name Incoherencies:

2015-08-20 14:19:13,308 INFO [SnmpNotificationProcessor] c.a.i.o.a.s.Snmp4jV3Session
[Snmp4jV3Session.java : 123] Sending inform CRS-20220 to host 10-10-1-61.labo10.fr on port
162
2015-08-20 14:19:13,309 INFO [SnmpNotificationProcessor] c.a.i.o.a.s.Snmp4jAbstractSession
[Snmp4jAbstractSession.java : 75] REPORT: Unknown user name.
Wrong authentication pwd:

2015-04-09 10:48:49,977 INFO [SnmpNotificationProcessor] c.a.i.o.a.s.Snmp4jAbstractSession
[Snmp4jAbstractSession.java : 79] REPORT: Wrong digest.
Wrong encryption pwd:

2015-08-20 14:34:35,101 ERROR [SnmpNotificationProcessor] c.a.i.o.a.s.Snmp4jV3Session
[Snmp4jV3Session.java : 130] Inform request has timed out for host 10-10-1-61.labo10.f
12.2.6 Wireshark traces at Omnivista 8770 side
Use of the wireshark tool is very helpful in snmp traps investigation.

See how to place a profile:

12.2.7 Logs
In /8770/log, NMCFaultManager_ICEService_1.log locate the trapSequenceNumber request
[25/08/2015 17:00:45] 4760 FaultManager_ICEService: CAlarmHdlr::parseMsg() start

[25/08/2015 17:00:45] 4760 FaultManager_ICEService: CAlarmHdlr::setAlarm_Str(trapSequenceNumber, 600796)
[25/08/2015 17:00:45] 4760 FaultManager_ICEService: CAlarmHdlr::setAlarm_Str(alarmIdentifier, 0-5064)
[25/08/2015 17:00:45] 4760 FaultManager_ICEService: CAlarmHdlr::setAlarm_Str(hostName, ice1.labo10.fr)
[25/08/2015 17:00:45] 4760 FaultManager_ICEService: CAlarmHdlr::setAlarm_Str(ipAddress, 10.10.1.31)
[25/08/2015 17:00:45] 4760 FaultManager_ICEService: CAlarmHdlr::setAlarm_Str(source, SNMP)
[25/08/2015 17:00:45] 4760 FaultManager_ICEService: CAlarmHdlr::setAlarm_Str(instance, NetSNMP_1)
[25/08/2015 17:00:45] 4760 FaultManager_ICEService: CAlarmHdlr::setAlarm_Str(eventTime, 2015-8-25,17:3:45.4,+2:0)
[25/08/2015 17:00:45] 4760 FaultManager_ICEService: CAlarmHdlr::setAlarm_Str(eventType, processingErrorAlarm(4))
[25/08/2015 17:00:45] 4760 FaultManager_ICEService: CAlarmHdlr::setAlarm_Str(perceivedSeverity, major(4))
[25/08/2015 17:00:45] 4760 FaultManager_ICEService: CAlarmHdlr::setAlarm_Str(probableCause, softwareError(545))
[25/08/2015 17:00:45] 4760 FaultManager_ICEService: CAlarmHdlr::setAlarm_Str(additionalText, Application terminated
due to internal condition)
[25/08/2015 17:00:45] 4760 FaultManager_ICEService: CAlarmHdlr::setAlarm_Str(context, Service=INFRASTRUCTURE)
[25/08/2015 17:00:45] 4760 FaultManager_ICEService: CAlarmHdlr::getService() Service = INFRASTRUCTURE
[25/08/2015 17:00:45] 4760 FaultManager_ICEService: CAlarmHdlr::setAlarm_Str(reSent, false(2))
[25/08/2015 17:00:45] 4760 FaultManager_ICEService: CAlarmHdlr::setAlarm_Str(isPrimary, true(1))
[25/08/2015 17:00:45] 4760 FaultManager_ICEService: CAlarmHdlr::parseMsg() finished
In the NMCFaultManager_1.log, locate the “ICE INCIDENT from” string :
[25/08/2015 17:00:45] 1396 FaultManager: ICE INCIDENT from ice1 issued 2015-08-25 17:03:45 :
MO=\Network::1_mon_lab\Subnetwork::mon_lab\Node::ice1\PhysicalServer::ice1.labo10.fr\Component::SNMP\Instance::
NetSNMP_1 OH=\7::'1_mon_lab'\8::'mon_lab'\999::'ice1'\99::'ice1.labo10.fr'\1099::'SNMP'\10099::'NetSNMP_1'\ #600796
active OSI[EvType=10,Sev=2,ProbCause=46] Component[0, Status=] AddInfo[12 0 #0-5064 1 ice1 2 ICEAlarm]
12.2.8 Display in the Alarm application
The incidents is seen as below :

12.3. SNMP Proxy investigation
12.3.1 Enabling of Agent snmp logs
As To enable extended logs in SNMP Agent logs, tracelevel must be filled in registry tool :
Start panel -> Run -> registry
12.3.2 Wireshark traces
In 8770 server, use of wireshark is very helpful, adding “snmp” as filter.

13. LICENSE
13.1. Overview
This chapter contains general information related to license issue.

An 8770 license:
• is specific for your PBX network,
• is sized according to the user capacity of that network, number of client PCs,
• describes the available OmniVista 8770 modules,
• is permanent or temporary with an exact date of end of validity (example: 31/12/2019).
This license is based on 2 locking possibilities:
- When running, OmniVista 8770 server will connect to this PCX to launch a hardware check, this
enable license validation.
- Server locking: Mac address, ProductID and UUID are required, along with either IP address or
Hostname.
To install a second OmniVista 8770 server (backup server, modules split on different servers), a new
license should be generated on another attachment PCX.
Warning The permanent control of licenses by the server can generate information messages as well as alarms
during the launching of a client customer.
It is very important to take into account this information and if necessary to bring the corrective measures.
If these recommendations are not respected, the system will operate in restricted mode.
The fitter of the system must sensitize the final administrator on this crucial point for the continuity of
OmniVista 8770 service.
This file is generated from Business Partner Web Site (BPWS) taking into account:
- the historic of the site: new installation or addition,
- the license requirements.
This file is named XXYYYAAe.sw8770, when it is provided by Actis.

When installing the OmniVista 8770 server:
− the installation program requires a file with *.sw8770 extension,
− then this file is copied in the \8770\etc sub-directory and renamed nmc.license.
The upgrades of licenses are carried out on the Omnivista 8770 server by replacing this file.

13.2. Content of the license file
13.2.1 Omnivista Version key
It is the version for 8770 license key.
release R1.0 R1.1 R1.2 R1.3 R2.0 R2.5 R2.6 R2.6.7 R3.0 R3.1 R3.2 R4.0 R4.1
OV8770
License version 1 2 3 4 5 6 7 7 8 9 10 11 12
Note The key is tested at the time of starting of licenses server. Only the N-1 license has to be
supported in the N release. For example, during 1.0 to 1.2 upgrade the license should be
upgraded.
the license file based on Server Locks will not be backward compatible at all since server lock section
is enhanced. The customer/BP must use the new license file. The N-1 compatibility still applicable for
the licenses based on 8770 Handle.
13.2.2 Redundancy, signature, ValidityDays and ExpirationDate keys
The Redundancy key specifies that redundancy is enabled. Otherwise this line is not included
in the file.
When it is enabled there are 2 instances specified Mac address, ProductID, UUID and IP
address or hostname.
The Signature key is calculated from all character’s present in the license.
ValidityDays and ExpirationDate are optional to give a trial period to use the 8770 Server.
13.2.3 Keys based on server-locking
When the license 8770 is locked based on system identifiers, the following values are
requested:
1. HostName key: the server name on which the license file is installed. It should be FQDN
( for example : Server8770.Ale.com)
2. IP Address key: IP address of the server where the 8770 is running. If redundancy is
enabled. The second one must be provided
3. MacAddress key: MAC address of the server. IF redundancy enabled. The second
instance has to be provided.
4. UUID key: This is the Microsoft Windows UUID of the server. To get this UUID run the
command as follows :
C:\users\Administrator\wmic
Then

wmic:root\cli>csproduct get uuid
As result:
UUID
81C94A96-3A50-CB11-AD26-AB25E8520541
5. ProductID key: This is the Microsoft Windows Product Id. It is obtained by wmic
command as above. The tape os get serialnumber of the server. To get this ProductID run
the command
C:\users\Administrator\wmic
Then
wmic:root\cli>os get serialnumber
As result :
SerialNumber
00376-30818-92942-AA051
13.2.4 Keys based PCx Management
Management key equal to 1 permit to manage OXO, or OXE and ICE.

Alize key is based on the OXO CpuId.
OXE and ICE : key is based on the OmniPcx Enterprise (Handle4760 key in OXE). This value
can be found via its spadmin tool,
• under telnet, launch spadmin
• select the option 2 Display active File
• note the value of Handle4760
13.2.5 Modules
See the following software locks, visible in 8770 help :

Module Description
OmniPCX Office Declaration of OXO
OmniPCX Enterprise and Declaration of OXE and Opentouch
Opentouch
Directory System part and management of administrator accounts/ Company
directory
Audit Use of Audit application
Alarms Internal alarms of server
ALUIPdevices Maximum nulber of ALE SIP devices supported by 8770 ( not OXO )
ThirdPartySIPDevices Third party devices supported by 8770. SIP extensions excluded
UnifiedUserManagement Number of users manageable in Users application:
OXE users: classical counting, excluding virtual extensions as well as
SIP devices
OT users (only OT entry) : 1 User (virtual extenuation created on
OXE not counted)
Standard users (OXE user + OT properties) : Counted as 2 users, 1
OXE user + 1 OT user
ICS Users (OXE User + ICS properties) : Counted as 2 users, 1 OXE
user + 1 ICS user
OXO users: not counted for Users
ExternalDirectorySynchro Synchronization with AD and MSAD plugin

SNMPProxy Support for SNMP proxy capability for all alarms in 8770 (OXE, OXO,
OT
and internal alarms) from an external hypervisor
Scheduler Lists of scheduled jobs
Maintenance Save and restore
Report Report on alarms, accounting, traffic observation, VoIP
Configuration Graphic Interface of configuration
Alarms Alarms of PCX
Topology Topology of PCX network and associated alarms
Accounting Accounting
AccountingMonitoring Monitoring of accounting, traffic and VoIP
PastTimePerformance Traffic observation
Performance
8770Clients Max number of clients allowed to connect to the server
OpenAPI Allow the use of OpenAPI module
RTUAuditor Allow use of RTUAuditor tool which produces KPI reports
OXOVoIPTickets IP tickets of OXO users
Ticket Collector Make available the accounting tickets and IP for third application
Security Secured SSH connectivity between 8770 server and OmniPCX
Enterprise, external authentication. Not more mandatory from 4.1
MSC Give access to multicompanies features
OmniPcx Enterprise:
The number of users is always the same for all the authorized applications. Devices are counted as
users. The most important value is taken into account.
For example, if 8770 is to manage 5000 users for Configuration, 500 for Performance and 6000
devices, then the value entered is 6000 for all.
OXO:
List of interfaces/terminals which will be counted
− Reflexes terminals.
− All UA accesses dedicated to a specific terminal (UA 2G, UA3G, IP Touch terminals, terminal
adaptor, TA, etc.).
− Mobile terminals.
− All DECT accesses dedicated to a specific terminal including GAP terminals (Mobile 100 Reflexes,
Mobile 200 Reflexes, etc.).
− IP terminals including IP PIMPhony users (PC Multimedia).
− IP terminal (First/IP, Easy/IP, Premium/IP, Advanced/IP, IP Touch 4018/IP, 4028/IP, IP Touch
4038/IP, IP Touch 4068/IP, etc.).
− Analog accesses.
− ISDN terminals.
− S0 subdevice (4094).

List of interfaces/terminals which will be not counted
− UA accesses not dedicated to a specific terminal.
− IP accesses not dedicated to a specific terminal.
− DECT accesses.
− All the virtual sets (included Nomadic).
− Integrated modem V34.
− Integrated modem V24.
− Voice Mail Unit.
− Internet Access.
− Remote Access ISDN
13.3. Checking the license
13.3.1 Restriced mode
When an alarm of license reaches the critical state, the server passes in restricted mode. The client can
connect in restricted mode. Only the configuration application and the scheduler are accessible.
13.3.2 Presence of the file
If the nmc.license file is not found on the server, the nmclicserver service cannot enable the license.
In Windows Explorer:
- go to the 8770\etc directory,
- right click to display the properties of the license file,
- check the name and the extension of the nmc.license file. The extension must be .license
and not .license.txt.
13.3.3 Presence of attachment PCX
The checking stages are:

− At the beginning, the server will identify which PCX is the attachment PCX and will mark the
Declaration node (license control) information on the level of the PCX declaration.
− Thereafter, every 24 hours, the server checks on the attachment PCX the 8770identifier. It must be
the same both sides.
− In the event of repeated failure of check, the server generates alarms of increasing gravities and
ends up blocking the client accesses. More precisely:

At the end of 8 days A warning alarm
At the end of 16 A major alarm
days
At the end of 24 A critical alarm
days
At the end of 32 The client passes in restricted mode. The following message is displayed
days during the client connection:
− If the check becomes again positive, the client application goes back in normal mode and the day
meter without key check passes by again to zero.
With the Help\About menu, you can check the name of the attachment PCX as well as its identifier.
These stages are stored in the 8770\log\nmclicserver_X.log file.
[16/09/2003 05:32:16] 1104 LicServer: There is not associated PBX.

[17/09/2003 05:32:49] 1104 LicServer: Trying to find the associated PBX...
[17/09/2003 05:32:49] 1104 LicServer: Checking key of PBX
'SubnetworkNodeNumber=1101, SubnetworkNumber=11, NetworkNumber=10, o=nmc'...
[17/09/2003 05:32:50] 1104 LicServer: It is the associated PBX!
[18/09/2003 05:34:12] 1104 LicServer: Checking key of PBX
'SubnetworkNodeNumber=1101, SubnetworkNumber=11, NetworkNumber=10, o=nmc'...
[18/09/2003 05:34:12] 1104 LicServer: PBX key is right!
...
[22/12/2003 11:56:36] 540 LicServer: WARNING
Checking time for last PBX key/ control: first threshold (8 days) crossed!
Days for last control: 8
13.4. Global synchronization
To count the number of users compared to that allows the license, the 8770 server uses the global
synchronization of all the PCX networks declared in the configuration application. The synchronization
must be done on the first level ( directory root ) in configuration application.
Warning The global synchronization that must not be confused with a complete synchronization.
When the global synchronization has not been carried out for more than 31 days, the client cannot be
used anymore.

1 You can launch synchronization within 8770 client (restricted mode Open the scheduler.
2 Reboot the server then check the Daily and Weekly are still scheduled. Check the report of PCS
synchronization tasks.
Sometimes the weekly and Daily jobs are not more available in Scheduler. You can restore those jobs:
1 Open the scheduler.
2 Delete the entries Weekly and Daily.
3 Open the system directory.
4 In the tree, right click import.
5 Select the directory 8770\data\scheduler on the server.
6 Import the Dailyjob.ldif and WeeklyJob.ldif files.
7 Reboot the server.
13.5. Number of users

The checking stages are:
− the server checks if the number of users corresponds to the limits of the license.
− This check is carried out:
• after synchronization,
• on start of service of license,
• every 24 hours after the last check.
− If the number is bypassed, the server generates alarms of increasing gravities and ended up by
blocking the client accesses. More precisely:
Beyond 80 % A warning alarm

Beyond 90 % A major alarm
Beyond 99 % A critical alarm
On 110% The client application passes in restricted mode. The following message is
displayed during the client connection:

− If the license is up to date, the client application will be able to be again connected in normal mode
to the server.
These stages are stored in the 8770\log\nmclicserver_X.log file.
11/10/2003 01:55:42] 3308 LicServer: Synchronization of LDAP server with PBX(s)

is finished.
[11/10/2003 01:55:54] 2620 LicServer: Procent of max subscriber: 125/250 = 50%
...
[12/10/2003 01:47:00] 1280 LicServer: Program starting
[12/10/2003 01:47:00] 1280 LicServer: time for last synchronization of LDAP
server with all networks: 1440 minutes (1 days)
[12/10/2003 01:47:00] 1280 LicServer: time for last PBX key control: 733 minutes
(0 days)
[12/10/2003 01:47:00] 1696 LicServer: Program running
[12/10/2003 01:48:00] 1696 LicServer: Procent of max subscriber: 125/250 = 50%
13.6. Use of the same license on two Omnivista 8770 servers
As of OmniVista 8770, the server checks the unicity of the license. It detects the possible use of a same
license on another server having the same attachment PCX.
The presence of two servers using the same license, with the same attachment PCX is acceptable during
a temporary period limited to 31 days.
For instance, if you need to install the OmniVista 8770 server on a new server, you can decide to keep
the old server and the new one running then after if the new one is fully operational, you remove the
old one.
If you need permanently to keep several servers 8770, you should place different order for each 8770
and get different license file.

If after 31 days, there are still 2 servers using the same license, an alarm on license failure will be sent
with increasing gravity. If you ignore all these warnings, and finally reach the exceeded gravity of license
failure, the system will turn into restricted mode. You will have to solve the issue by providing separate
license or closing the additional server.
More precisely:
At the end of 31 days A warning alarm

At the end of 51 days A major alarm
At the end of 71 days A critical alarm
At the end of 91 days An exceeded state, client go in restricted mode. In each stage, a
message is displayed when opening a client. It is important to solve
the conflict before turning into the restricted mode
Here are 2 examples of messages displayed when connecting the client:
Warning The return in normal mode will be effective only after a delay of 5 days of functioning
without conflict.
Associated logs
[28/10/2007 11:24:36] 5992 LicServer: License file check starting...
[28/10/2007 11:24:39] 5992 LicServer: Warning: Found a license with the same
8770OfferNumber on server : 155.132.33.195
[28/10/2007 11:24:40] 5992 LicServer: Error: License file(s) with same
4760OfferNumber is/are still used by other server(s).
[28/10/2007 11:24:40] 5992 LicServer: License file check is done
[28/10/2007 11:24:40] 5992 LicServer: Multi-utilization duration : 40 days, 91
allowed (status=warning)

Protection of control mechanism of license unicity
Any obstruction of control mechanism or any attempt to corrupt data or file used by the license control
will be registered as "Unexpected event". These events are counted and information messages are
displayed when connecting the client. The corresponding alarms are generated. It is important to solve
the issue before turning into restricted mode after 32 events.
More precisely:
10 events Warning
15 events Major
20 events Critical
32 events Bypass
Here are 2 examples of messages displayed when opening the client:
CAUTION
The "Unexpected events" are erased only 40 days after their creation. Supposing that an event is
generated once a day (at the time of the license control) and that the counter is to 32 at the moment or
the problem is solved, the decrease will begin only 8 days later, date on which the first event will be
erased because dating more than 40 days. The system will stay in mode restricted as long as the counter
will indicate more than 31 events (8 days in this example).
Example of a particular unexpected event
The mechanism of license unicity control must write that data on the attachment PCX.
A /usr4/tmp/ov4760 directory is created with FTP account defined in OmniVista 8770 configuration
for the PCX in question (user and password Ftp).

The rights allocated to this directory and sub-directory uc are the following:
drwxr-xr-x 3 mtcl tel 4096 Sep 17 16:51 ov4760

In this example, only the creative account has the right of writing in this directory.
If in the configuration, the Ftp user has been changed for this PCX, OmniVista 8770 will not be able to
write any more in the ov4760 directory.
Each daily attempt will fail and will be counted as "unexpected event".
If the directory was created by error by mtcl account, it should be removed (ov4760 of PCX). It will be
created again by the adfexc default account after changing the management OmniVista 8770 side.
Associated logs
[9/20/2007 3:30:21 PM] 6268 LicServer: License file check starting...
[9/20/2007 3:30:24 PM] 6268 LicServer: Error: Unexpected events :
PCXConnect::putFile: Sending file c:\8770\data\temp\\4760_lock_ocppbx4.ocp-ec.com
failed : 553 4760_lock_ocppbx4.ocp-ec.com: Permission denied on server.
(Overwrite)
[9/20/2007 3:30:24 PM] 6268 LicServer: License file check is done
[9/20/2007 3:30:24 PM] 6268 LicServer: Error: Unable to check prevent file
[9/20/2007 3:30:24 PM] 6268 LicServer: Multi-utilization duration : 0 days, 91
allowed (status=ok)
[9/20/2007 3:30:24 PM] 6268 LicServer: License file multi-utilization :
unexpected events count : 26/31 (status=critical)
On first check after removing the ov4760 directory we have :

[9/20/2007 3:32:13 PM] 4692 LicServer: Error: Unexpected events : 8770 server is
supposed to be registered while it is not !
[9/20/2007 3:32:13 PM] 4692 LicServer: License file check is done
[9/20/2007 3:32:13 PM] 4692 LicServer: Multi-utilization duration : 0 days, 91
allowed (status=ok)
[9/20/2007 3:32:13 PM] 4692 LicServer: License file multi-utilization :
unexpected events count : 27/31 (status=critical)
On the following check, we no more must have errors and the counter value no more increases.

13.7. Modifying the licenses
13.7.1 Changing manually the licenses
1 Close the NMC Service Manager service using the manager of OmniVista 8770 service.
2 When all the dependent services are closed, copy the license file of type xxyyyzza.sw8770,
and rename it nmc.license. In Windows Explorer, check this name with right click
\Properties (nmc.licence and not nmc.licence.txt).
3 Move this file under the 8770\etc installation directory.
4 Reboot the PC.
5 Launch the client application.
6 Check that licenses have been updated using the Help\About menu.
13.7.2 Modifying the capacity / Adding a module
There is no tool to change the content of licenses of OmniVista 8770 server. Carry out a manual
change of license file.
13.7.3 Changing the CPU
Depending on the type of attachment PCX, the OmniVista 8770 license can be kept:
− For OmniPCX 4400, the hard keys are saved,
 possibility to keep the existing 8770 license file.
− For OmniPCX Enterprise, the Handle8770 field is saved,
 possibility to keep the existing 8770 license file.
− For OmniPCX Office, the CPU-Id field is changed,
 you should change the 8770 license.
Note To help eLP license search, the field Handle4760 is initiated with the first purchased CPU-Id. after
rehosting an OmniPCX Enterprise CPU, the CPU-Id is modified but the Handle4760 field keeps its
initial value. Hence no need to update an 8770 license after rehosting a CPU.
13.7.4 Migrating the Omnivista 8770 version
When changing the version, the installation program checks the current license and compares the
version id with that required by the new version:
− if the version id is not compatible, the installation program requires to supply a new 8770
license file,

− if the version id is compatible but different,
 the installation program requires anything,
 after the update, reboot the server and wait the end of patch installation. Then you can:
 continue to use the old license,
 supply a new license file; to install this file, you need to carry out a manual copy of license
file,
− if the version id is the same, that is a version of maintenance corresponding to the same commercial
version, therefore the license is preserved.
13.7.5 Changing the 8770 server, hostname or Windows Operating system
When the server or the operating system has to be changed ( Ex : Windows 2012R2 to
Windows2016 ), the ProductId, Mac Address, hostname can be changed.
If the license8770 is based on those keys, a new license must be supplied.
See chapter Keys based on server-locking
13.8. Software locks on OmniPcx Enterprise
The access to data of various PCXs needs to have the corresponding software locks at level of each PCX.
OmniVista 8770 Module Number of OmniPCX Enterprise software locks

Configuration 13 - ECS Engine
50 - Configuration
Accounting 42 - Accounting users
98 - Accounting for local calls (if local accounting)
99 - Accounting for ABC calls(if network accounting)
Directory 49 - Directory
Traffic observation 42 - Accounting users (Do not forget)
39 - Performance
VoIP 42 - Accounting users (Do not forget)
Alarms 47 - Alarms
Secured SSH connection with No specific software lock on OmniPCX Enterprise.
OmniPCX Enterprise Security license on OmniVista
Identification of some issues related to software locks

The steps of configuration access to OmniPCX Entreprise are saved in the
8770\log\NMCCMISD_x.log file.
When the 50 Configuration PCX software lock is missing.
The configuration client returns :

Rejet cmise : Association rompue
The file 8770\log\NMCCMISD_x.log

[09:33:39] 2220 CMISD: Error: The association is not accepted (AARE rejected)
(Pbx : PPP, Connection number : 1655, number of networklink (socket) : 748)
[09:33:39] 2220 CMISD: - Operation : rejected transient
[09:33:39] 2220 CMISD: - Source : acse_service_user
[09:33:39] 2220 CMISD: - Cause : application context name not supported
PCX side, activate the traces, mao +cmisd:

-> cmisd:authenticate control :station =|SRV4760| password =|L__| user = ||
-> cmisd:authenticate control : condition for check ( 47xx )
-> cmisd:authenticate control (47xx:1) status 0 )
-> cmisd:authenticate passed (47xx:1)
-> 47xx conditions and no right
When the PCX 47 Alarms software lock is missing

The file 8770\log\NMCfaultmanager_A4400service_x.log
The EFD was not found -> Trying to create it
A CMISE error occurred
When the PCX PCX 42 Accounting software lock is missing

The file 8770\log\NMCsynchldap_x.log
On operation flush action on accounting
13.9. Example of current issues

- No NMC license for this OmniPCX network :
Cannot connect to the server since the server cannot connect to the attachment PCX too
much time or the identifiers are not the same between 4760 license and PCX
• Solve the problem of ftp connection between 4760 and PCX.
• Installation of a new license associated to an other attachment PCX.
• Delete the previous attachment PCX. The 4760Handle identifier must be the same in
the 8770 license and in OmniPCX Enterprise (spadmin Option 2 command)
• Installation of a new license associated to a new CPU-Id of the attachment OmniPCX Office
- The license file is installed on another server for a long time.

The same license is used on 2 different servers for a long time. These 2 servers have the same
attachment PCX.
Order a 2nd license
Remove one of two servers
CAUTION : The system remains in restricted mode as long as we did not reach 5 days of
functioning without conflict.
- Too many unexpected events during license verification, only restricted access to omnivista
8770
Misfunctioning of control mechanism of license unicity for a long time.
Confirm the writing right of the current FTP user in the /usr4/tmp/ov4760 PCX directory. If it
is not the case, delete this directory then check its re-creation with the correct rights after
restarting the NMC License Server service.
CAUTION: The remains remains in restricted mode as long as the counter value is higher
than 31; see section Use of the same license on two OmniVista 4760 servers.
For others cases, consult the log file to identify the problem.
- CMISD error :
The software lock 47 alarms 47xx is not enabled on the PCX
- Configuration to OmniPCX 4400/Enterprise: Rejet cmise :Association rompue

The 50 Configuration software lock is not opened on the PCX
Require a modification of the PCX license to add it
- Installation of a temporarily license. if a temporarily license was used on a site. It is no more

possible to install another temporarily license. it is necessary to update a temporarily license by
a final license.

Functioning
The software lock 47 alarms 47xx is not enabled on the PCX
Functioning
Configuration to OmniPCX 4400/Enterprise: Rejet cmise :Association rompue
The 50 Configuration software lock is not opened on the PCX
Require a modification of the PCX license to add it
Installation of a temporary license

If a temporary license were used on a site, it is no more possible to install
another temporary license. It is necessary to update a temporary license by a
final license

14. SECURITY ACCESS
This chapter provides elements about the secured access allowing to filter the access to the configuration of
OmniPCX Enterprise. The filtering can be performed by the name of OmniVista 8770 servers (the stations) and
by the logins used to run the omnivista 8770 client (the users).
14.1. Purpose
The secured access allows to filter the access to the configuration of OmniPCX Enterprise. The filtering
can be performed by the name of OmniVista 8770 servers (the stations) and by the logins used to run
the OmniVista 8770 client (the users).
The security is applied on the CMISE connection between the OmniVista 8770 server and the PCX.
Cmise security management brings also a better authentication of the person who makes PCX
modifications using OmniVista 8770. The OmniVista 8770 client "User name" is saved and can be read
at PCX side using maohist tool. Without security access, only the server name is saved.
Example
2006/03/10 15:07:30 Update Users 6 3023 (Srv8770|Nicolas)
This "User name" information is also included in the corresponding events sent to the OmniVista 8770.
But all PCX management actions do not generate an event towards OmniVista 8770. Only those who
modify OmniVista 8770 computed data are concerned, mainly users modification/creation and cost
centers modifications.
Example
No 242261
Notification Id 0
Managed object \Network::Alcatel\SubNetwork::PARIS\Node::N6\Users::3023
Event Type Change of Attribute value
Notification date 03/10/06 03:07:00 PM
Reception date 03/10/06 03:02:25 PM
Information Origin: SRV8770 (Nicolas)
14.2. Object used on OXE side

Under “Security and Access Control”

14.3. Object used on OXE side
In OXE settings enable the secure access for system management and CMISD password ( empty by
default )
14.4. Configuration step by step

To avoid errors and to determine a possible problem, it is advised to follow in the order the stages of
management described below
For the PCX management, use the object “Security and Access Control”.
Step 1 :
- On PCX, manage the stations without password.
Create the stations (8770 servers). The name corresponds to the name of PC on which the OmniVista
8770 server is running.
It is mandatory to enter the name in UPPER case letter.
Do not enter password now. Retain at the moment the relation with the list No. 1 of users.
Example :

- Delete the station " * ". This character allows the connection of any station.
Warning You are not allowed to recreate this character using the client management tools.
To reinit the configuration, read the “security access reinitialisation” section below
- On OmniVista 8770, enable the security without password.

In the system directory, Connectivity tab, tick “Secured access for system
management”.

- List User Access Control (by default)
- Test the connection to PCX in configuration.
Step 2 :
- On PCX , create a list of users No. 2.

- In the Station object, assign this list No. 2 to stations.
- On PCX, create the “users Access Control”.

The name of users corresponds to the login used to run the OmniVista 8770 client.
It is mandatory to enter the name in UPPER case letter.
Assign the user to the list of users No. 2 => List user access Control is updated
Note
when an “users Access Control” is created, the domain by default (“0”) is assigned without
restriction
.

- Test the connection in configuration to PCX.
Step 3 :
- Option of security: creation of a CMISD password.

To strengthen the security, it is possible to control the connection by password.
OmniVista 8770 side, complete the password in the Connectivity tab for corresponding PCX
(Cmisd password).
PCX side, indicate this same password on the corresponding stations.
If the password is changed in OmniVista 8770 side, it can be necessary to launch again the client
and/or to launch again the NMC CMISE server service.
- Test the connection in configuration to PCX.
14.5 Security access reinitialization

Within PCX configuration (via mgr or 8770 configuration) you cannot put back the default security
parameters:
− station = *
− user = *

To recover such value:
1 Start a telnet session on PCX.
2 Put MAO off.
3 Launch multitool SECURITY_ACCESS.
4 Select option 10: Security access reinitialization.
5 Put back MAO on.
14.6 Troubleshooting
14.6.1 Authentication Failure
In case of issue, the following error will be displayed
[1:35:55 PM] > Checking version PCX tssf120...

[1:35:56 PM] > Connected to PCX tssf120.
[1:35:57 PM] > Loading the local object model...
[1:36:01 PM] > Request 0 sent to tssf120.
[1:36:01 PM] > Request 0 completed on tssf120: 0 instance(s) received.
[1:36:01 PM] > Full PCX object model is available.
[1:36:02 PM] > Disconnect from PCX tssf120.
[1:36:03 PM] > CMISE reject: [PCX] Authentication Failure
1) Check the User List assigned to the station (8770)

2) The 8770 user used to make the configuration must belong to this list
3) Check the “user validity” of the user as shown below
14.6.2 Traces OmniPCX Enterprise
mao +cmisd
traced&

This trace is used to view the data of connection sent by the 8770 servers. It gives the result of the
authentication.
After the investigations, stop the trace by:
mao –cmisd
kill -9 for traced& process
Example of completed authentication:
1134132970 -> cmisd:authenticate control :station =|SERVEUR-AP3| password

=|t43gvgst| user = |ADMINNMC|
1134132970 -> cmisd:authenticate control : condition for check ( 47xx )
1134132970 -> cmisd:authenticate control (47xx:1) status 0 )
1134132970 -> cmisd:authenticate passed (47xx:1)
Example of failed authentication:
1134137776 -> cmisd:authenticate control :station =|SERVEUR-AP3| password

=|z34w3iwq| user = |ALAIN|
1134137776 -> cmisd:authenticate control : condition for check ( 47xx )
1134137776 -> cmisd:authenticate control (47xx:1) status 4 )
1134137776 -> cmisd:authenticate failed (47xx:1):4
14.6.3 Traces 8770
This trace can be useful for an additional analysis.

Launch the executable 8770\bin\ntsvcexClient.exe.
File\Open
Registry Search \ service : cmisd
Then OK
Open the tree, click on Debug. display the properties of traceControlBlocks with a right click.
Change the value from 0 to 1.

A log file is generated : 8770/log/NMCViewControl_Blocks.log
Note
After the investigations, return to the value of origin (0).
14.7 OmniPCX Enterprise Domain
14.7.1 Rights & domain
Rights & domain are assigned to the “user Access Control” as shown below

14.7.2 Domain in the object
Domain are assigned to the object (“user”) as shown below

15. INTERWORKING ON A VPN / NAT NETWORK
15.1. Overview
OmniVista 8770 has been designed to work on intranet site where all OmniVista 8770 systems, Clients
and Server, are interconnected on same LAN and use hostname resolution or host file to communicate.
Now some customers would like to extend their intranet on a VPN network to network connection. This
has a major impact on IP address, since such VPN solution comes with Network Address Translation
(NAT).
To operate OmniVista 8770 on a VPN network, you will need:
• a perfect knowledge of customer VPN network architecture
• to change firewall configuration to allow all OmniVista 8770 traffic
• to update OmniVista 8770 client and OmniVista 8770 server host file
• to update one parameter in OmniVista 8770 client batch file runnmc.bat
Restrictions
• Nated address used for VPN needs to be static
• Port address translation (PAT) is not supported
We will work on a real customer topology
OmniVista OmniVista 8770

8770 Client Server
FW1 IPSec Equipment1 IPSec Equipment2
LAN 1 LAN 2
128.213.224.0 10.19.10.0
NAT NAT NAT
VPN Network
Translation of 8770 Client IP address Translation of 8770 Server IP address

Network Client IP address Network Server IP address
LAN1 @Lan1_Client LAN2 @Lan2_Server
VPN Network @VPN_Client VPN Network @VPN_ Server
LAN2 @Lan2_Client LAN1 @VPN_ Server

15.2. IP Flow
LAN1 VPN Network LAN2
Client connects to OmniVista 8770 server services (see Installation manual for the list)
sourceIP @Lan1_Client @VPN_Client @VPN_Client @Lan2_Client
DestinationIP @VPN_Server @VPN _Server @Lan2_Server @Lan2_Server
Server connects to OmniVista 8770 client Notification port (30500-30509)

sourceIP @VPN_Server @VPN _Server @Lan2_Server @Lan2_Server
DestinationIP @Lan1_Client @VPN_Client @VPN_Client @Lan2_Client
15.3. Specific settings
15.3.1. Host file configuration
We will assume there is no DNS service for this VPN connection. Hence you need to edit local host file
for both client and server system (WinNT\Sytem32\driver\etc\hosts).
On server PC, give the resolution of client hostname using its IP address visible on LAN2.
@Lan2_Client CLIENT CLIENT.LABO.FR
On client PC, give the resolution of server hostname using its IP address visible on LAN1.
@VPN_Server SRV8770 SRV8770.ALCATEL.FR
15.3.2. Client modification
Now OmniVista 8770 client and server can communicate using simple protocol: http, ldap, ... But
protocols like CORBA that encapsulate host identification are not NAT compliant.
On OmniVista 8770 server, CORBA is initialized using server hostname. Since we have edited properly
the Client host file, we have no problem: the OmniVista 8770 client will be able to launch CORBA
connection to the server.

On OmniVista 8770 client, CORBA is initialized using local IP address. This will limit OmniVista 8770
usage: OmniVista 8770 server will fails to send notification on client CORBA port 30500 – 30509.
• there is no alarm on client
• you can not launch configuration module
There is a possibility to change client parameter:
1 locate client program: 8770client\bin\runnmc.bat
2 edit this file
3 change ipNumeric yes to ipNumeric no
(there are 2 lines to edit with this parameter)
By this way, the client hostname will be sent to the OmniVista 8770 server. Now server should succeed
to sent notification.
15.3.3. Firewall setting
To operate OmniVista 8770 applications, you need to update firewall rules and allow all OmniVista
8770 IP traffic between client and server:
1 Check “OmniVista 8770 Security Guide” documentation (“Deploying the Omnivista 8770 in a
secure Network Configuration” Chapter)
2 Take care of what will be the IP Address to control: @LAN1, @LAN2 or @VPN
3 Regarding OmniVista 8770 server, allow connection on all OmniVista 8770 services
4 Regarding OmniVista 8770 client, allow connection on CORBA notification port 30500 –30509.
Example
On FW1, you need to allow incoming connection for OmniVista 8770 client:
IP=@LAN1_Client Port = 30500 – 30509

15.4. Specific settings
15.4.1. Alarm error message when port 30500 not available
Description Launch OmniVista 8770 client on the VPN connection

There is " ? " for the alarm statistic information
When you open Alarm application the tree is empty
Log: High exception: ConsultationSeverity AlarmSeverity Request BAD_IDENTIFIER:
8770Client.log null
Srv8770 AlarmManager: ConsultationSeverity thread id: Thread[Thread-
37,6,main]
Srv8770 AlarmManager: AlarmSeverity initialized with id: 391
Srv8770 AlarmManager: Request All Severities...
Srv8770 AlarmManager: OH String Filter:
Srv8770 AlarmManager: OSI Filter:
Srv8770 AlarmManager: Request completed.
Srv8770 AlarmManager: timedout thread id: Thread[AWT-EventQueue-
0,6,main]
Analysis The client does not receive any connection on its Corba port 30500 – 30509:
check firewall setting
15.4.2. Alarm error message when port 30500 not available
Description Launch OmniVista 8770 client on the VPN connection

Start Configuration
Try to configure one PCX
Connection fails
Log: uid=AdminNmc,ou=Administrateurs,ou=Administration,o=%CompanyRoot%,o=di
Status rectoryRoot is connected to server SRV8770:389.
window of 2 new nodes displayed.
configurati 1 new node displayed.
on ComServerApi::ConnectA CORBA.SystemException:
Connection to ComServer impossible
Analysis The client does not receive any connection on its Corba port 30500 – 30509: check
firewall setting
15.5. Firewall
There is a simple way to check firewall setting.
1 On OmniVista 8770 client, find the CORBA port 3050x which is waiting for a connection
(listening state)
2 Start OmniVista 8770 client
3 Launch a DOS window and check the notification port
C:\netstat –a –n
4 On OmniVista 8770 server, check connection to the client notification port

5 Launch a DOS window
C:>telnet CLIENTHOSTNAME 30500
If there is Connect failure error, a firewall has rejected the connection.

16. RTU
16.1. Overview
This chapter provides some steps to check some bad behavior regarding RTU/Kpi’s feature.
As remain, the next figure illustrates a high level view of the RTU architecture :
16.2. Checking steps
In scheduler, make sure the RTU task are well executed and finished properly :
- RTU purge in weekly/daily job

- RTU Scheduled Reports :
-
Otherwise, the system is going to run in restricted mode after 31 days.
- Check the RTU tables are well presents. Connect to RTU database, using dba user :

The rtu files must be located under /8770/data/data/rtu folder :
In the rtu_tx_kpi, the KpiId must be filled.
Consult the table rtu_ma_kpi to get the Kpi signification according to Kpid :

For any cases, if the rtu tables are missing, thanks to contact technical support to get the procedure to create
those tables.
16.3. Known cases
- Error message “Warning : No global RTU snapshot” :

Solution :
The wildfly service is disabled and NMC java service is not running. A restart of the server is needed.
- Some RTU reports doesn't work as scheduled as well as in report application.

Those reports are a copy of predefined report "RTU Consolidated Report" with some modifications by adding filter
at generation ( selection of system ).
A “Report Error” is generated.
Solution :
To solve the issue, it is necessary to rebuild the report "RTU KPI".
In report application, following the steps :
- deletion of the report,
- copy of the initial predefined report ( "RTU Consolidated Report" ),
- paste in account name,
- modify the report as expected : in your case, add the system filter at generation.

17. Manage MyPhone
17.1. Overview
This feature allows display of programmable keys, creation of programmable key and the
update/delete key.
“Manage My Phone” service is running on 8770 Server, and this service is using the Java Web
application on port 8090, ( openJRE of 8770 )
17.2. Configuration
All declared users of the 8770 can log in Manage My Phone and configure his phone set as soon as
Email address field and 8770 password are filled.

If those parameters are not filled, the following error is raised: “Invalid password and/or login”
17.3. How it works

This feature reads the 8770 ldap config directory to check the OXE and users authenticated.
17.4. Logs
The logs can be set in : %NMC_HOME%\selfcare\config\logback.xml
LOG configuration file is specifying under LOG level and log path.
All logs are under / 8770/selfcare.
The most useful log is the /8770/selfcare/logs./selfcare for any case of issue :

18. Web Based Management
18.1 8770 WBM for OXE Configuration : How to clear the OXE MIBs from
browsers
8770 configuration application is introduced in the WBM to support the configuration capabilities.
Before using the OXE configuration Webclient application, do the following steps to clear the old OXE schema
files from the 8770 server and from browser.
Do the below steps only once.
Server side
Delete the files under the folder <8770 Install Dir>\data\config\WBM\OXE
Client side
1) Launch 8770 WBM using the URL https://<8770 server IP or FQDN>:8443/nmclient/ in chrome or
firefox
2) In chrome

a. Launch developer tools by clicking F12 or Navigate and select More tools-> Developer
tools
b. Under Application Tab, select Clear storage and select Clear site data button. Make sure
the IndexedDB checkbox selected.

3) In Firefox
Go to menu Options-> Privacy & Security and select the button Clear Data… under Cookies and
Site Data section

19. Web Based Management Performance
19.1 Overview
A Performance Dashboard is accessible from the WBM client, organized in 5 widgets: Trunks, Devices,
Quality, IP domain, Health.
19.2 License prerequisites

The Performance Dashboard is available with the Performance item in the license.
19.3 Configuration
The OXE nodes observed by this performance polling are declared in the Configuration application, with a new
option: SNMP Performance monitoring.
The SNMP configuration must be consistent on the OmniVista 8770 (hypervisor) and the OXE (agent), checked
during OXE synchronization. OmniVista 8770 works with SNMPv2 and SNMPv3.
Note OXE nodes running an SNMPv1 agent are excluded from the monitoring.

In OXE side :

19.4 The log file
The main logs are written into the file <8770 Install Dir>\log\NMC_RealtimePerformance.log
19.5 The troubleshooting

In alarm application, make sure no incident number 32000 is generated otherwise it means some of the
following parameters don’t matched: SNMP community name, SNMP v3 user, SNMP authentication password.
See chapter 19.3 for further details.
SNMP test :

- snmpget : In order to test the snmp connection and Agent declared in OXE, the snmpget command
returns results value according to OXE MIBs.
As example, snmp get returns the number of set in service (except SIP phones ) :
Here the number of phone in service : 11.

The same test can be performed thanks to software like MIB Browser from iReasoning.
- Analyze can be done with Wireshark tool by filtering “snmp”

- Logs : In log file NMC_RealtimePerformance.log, see the sequences when the performance counters
are well uploaded.
No errors should occurs when the pooling connection and data loading are successfully done from
8770 snmp performance process.

-

20. Authenticated certificate deployment
20.1 Overview
This feature involves the SSL support with a certificate generated by the 8770 PKI(EJBCA) or by the customer
corporate PKI or by an external (third party) certificate authority for https flow in the port 8443 and LDAPS
support by Oracle Directory server in the port mentioned during 8770 server installation.
For complete deployment process, see “TC2599en-Ed02_Authenticated_certificat_deployment”
20.2 tools
The authenticated certificates are deployed via “toolsomnivista” tool
• HTTPS (port 8443) for the WBM client : to avoid the browser warning when launching 8770 WBM Users
or 8770 web directory client
• LDAPS (port 636) for LDAP clients : allow all clients to connect the Directory Server in secure mode
20.3 The log files :

- The current logs to check are the Apache and ldap logs :
As for Oracle, under \8770\SunONE\slapd-8770\logs

As for Apache server, the log is collected from \8770\wildfly\standalone\log
- About all certificate operations via toolsomnivista, the log is “NMCToolsOmniVista_1.log” :
[13/05/2020 18:18:43] 6288 ToolsOmniVista: Authenticated Certificate Deployement is started

[13/05/2020 18:18:43] 6288 ToolsOmniVista: Verifying of server.pem and private.key in AuthCertificate folder
[13/05/2020 18:18:43] 6288 ToolsOmniVista: First time CA deployement started
[13/05/2020 18:18:47] 6288 ToolsOmniVista: Apache: Copying CA files in 8770.
[13/05/2020 18:18:51] 6288 ToolsOmniVista: Apache: Copying Certificates to AuthCertificates folder is
completed.

21. MSAD Plugin
21.1. Known issues

18.1.1 “Internal error” or “licence failure” message
After a new plugin installation on my AD, an error is generated when the plugin is launched :"active
directory client license failure"
Solution :
password of "MSAD8770Admin" has to be changed then MSAD plugin has to be installed on AD again

22. INTERNAL ALARMS LIST
This chapter provides the alarms list useful for understanding some bad working of 8770.
22.1. Presentation
OmniVista 8770 alarm application is based on a predefined list of alarms. When one alarm is
generated, the alarm server looks for its description, and inserts into Sybase database a fully described
alarm with:
• date of notification
• diagnostic id
• severity
• additional text: one line description of the alarm, includes some parameter, {0} , {1}, ... for
parameter 0, 1, ...
• description: detail on the alarm: impact and cause
• information: possible solution
This document will cover OmniVista 8770 internal alarms.
This document has been updated with the last OmniVista 8770 R.4.0 predefined alarms.
For PCX internal alarms please refer to the PCX documentation.
The list of alarms is presented with ascending order for Alarm ID. Each chapter covers a specific range
of alarms dedicated to an OmniVista 8770 service or function.

22.2. Range ID
Range Id Emitter
100-999 Alarms server

2000-2999 Communication server
4000-4999 License server
6000-6999 Service Manager
7000-7999 Scheduler service
10000-10999 SyncLdapPbx service
13000-13999 Loader service (accounting tickets)
15000-15499 Cmised service
15500-15999 GCS services (OXE Configuration)
17000-17999 Loader service (Ptp counters)
18000-18999 Alarms Trigger (module of the Alarm Server)
19000-19999 Ldap Directory Server (plugins modules)
21000-21999 VoIP tickets loader (OXO)
22000-22999 Collector (module of the SyncLdapPbx Server)
23000-23999 SaveRestore Server
24000-24999 External Authentication (module of the Ldap Server)
25000-25999 Security & Password
26000-26999 Audit Server
28000-28999 DeviceManagement server
29000-29999 UnifiedUserManagement server
30000-30999 ICEConfiguration server
31000-31999 RTU Module

22.3. Event
Id EventType
0 Unknown
1 Change of Attribute Value
2 Communication Alarm
3 Environment 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 Change of Relationship
13 Violation of Service or Security Mechanism
14 Change of State

22.4. Cause
Id ProbableCause
0 Unknown
1 Adapter error
2 Application subsystem failure
3 Band with reduced
4 Call establishment error
5 Communications protocol error
6 Communication 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 opened
15 Equiment mal function
16 Excessives vibrations
17 File error
18 Fire Detected
19 Flood detected
20 Framing error
21 Heating or ventilation or cooling system problem
22 Humidity unacceptable
23 I/O 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 exceed

Receive failure
Receiver failure
Remote node&transmission error
Ressource at or nearing capacity
Response time excessive
Retransmission rate excessive
Software error
Software program abnormally terminated
Software program error
Storage capacity problem
Temperature unacceptable
Threshold crossed
Timing problem
Toxic leak detected
Transmit failure
Transmitter failure
Underlying ressource unavailable
Version mismatch
Disk failure
File system call unsuccessful
Information modification detected
Reinitialized
Software environment problem
Transmission error
Unavailable

22.5. Alarm Server
This list concerns alarm relative to NMC Alarm Service (in charge to receive alarms from PCX and
inserting them in 8770 DB).
Event Probable
Id Severity Description
Type Cause
100 2 4 MAJOR The connection to the PCX {0} failed.
The PCX is not reachable or its object model is not available
1 - Verify the PCX state
2 - Verify the domain configuration (security)
3 - Verify if its object model is present on the server machine
101 2 4 MINOR Cannot create the EFD on {0}: no more room left.
Delete all unneeded EFD for the configuration client.
Verify there are no unnecessary EFD on the PCX.
105 2 4 CLEARED The connection to the PCX {0} was successful.
The PCX is now reachable or its object model is now available
110 3 46 MAJOR {0}({1}): No data was found on disk after a successful MIB synchronization
120 11 39 WARNING An alarm list reached {0} alarms.

Alarms over {1} will be lost.
The flow of alarms is too heavy or alarms cannot be stored in
the database; they are being stored in memory.
Verify that the database engine is still running.
125 11 39 CLEARED The number of alarms in the queue fell below {0}.
130 11 7 WARNING An alarm or event has been received from the PCX {0} with a subnet node
number ({1}) not defined.
This problem appears when the PCX definition on the LDAP server is
incorrect.
1. Check if the PCX subnet node number is correct.
2. If the alarm or event comes from a PCX which collects event reports
from another PCX, define a new PCX with this subnet node number
Restart the alarm server.
140 11 46 CRITICAL The number of alarms ({0}) exceeds {1} ({2}%) of the maximum limit {3}.
The oldest alarms will be deleted until the number of alarms falls below the
limit.
200 10 48 MAJOR The MIB version {0} has not been succesfully inserted.
The diagnostic fault database is incomplete; some alarm diagnostics are
missing.
If this alarm remains active after Alarms Server restart, please contact
support personnel.
The database stopped during fault diagnostics insertion and did not restart
afterwards. Insertion in the database has stopped.
You must restart the Alarm Server service.
201 10 48 CLEARED The MIB version {0} inserted successfully. The internal alarm fault
diagnostic database is now correct

22.6. Communication Server
This list concerns alarm relative to NMC Communication Service (in charge of PCX connection).
Event Probable
Type Cause
2000 2 7 MINOR Wrong connection on modem {0} for PCX {1} ({2}).
Verify the PCX configuration is correct per the LDAP connectivity and
modem connection.
2001 2 7 CLEARED Connection established to PCX {0}.
2002 2 7 MINOR Wrong attributes for LAN-to-PCX connectivity {0}.

Check connectivity parameters for PCX with client Directory or
Configuration
on the "Connectivity" tab. Then verify the validity of following fields.
LAN connectivity:
----------------
- Connection type (LAN or blank),

- IP Address.
- Gateway Link : (not empty, corresponding to the ISDN Router Dn
(Check that Router declaration exists and has not been modified).
2003 2 7 CLEARED Correct LAN configuration for PCX {0}.
2004 2 7 MINOR Wrong gateway configuration (IP/X25 or ISDN router) for PCX {0}.
Check connectivity parameters with PCX on 'Connectivity' tab with client
Directory or Configuration. Then verify the validity of following fields.
If IP/X25 connectivity:
- Connection type (IP/X25)

- IP Address on network IP/X25
- Gateway Link IP/X25: DN of PCX acting as gateway
If ISDN Router connectivity:
- Connection type (ISDN Router)

- PCX IP Address on distant VLAN
- Link gateway: DN of ISDN Router
2005 2 7 CLEARED Correct gateway configuration (IP/X25 or ISDN Router) for PCX {0}.

2006 2 7 MINOR Connection problem on PCX {0} Serial PPP ( {1} ).
Check connectivity parameters with PCX on tab 'Connectivity' with client
Directory or Configuration. Then verify the validity of following fields.
Simple PPP connectivity:
- PPP Timeout: 180,

- Phone number,
- PPP account password,
- Authentic CHAP Logon,
- Authentic CHAP password,
- DN Modem pool.
PPP/RMA connectivity:
- PPP Timeout: 180,

- Phone number,
- PPP account password,
- Authentic CHAP Logon,
- Authentic CHAP password,
- RMA Logon,
- RMA password,
- RMA port,
- DN Modem pool.
2007 2 7 CLEARED Parameters for PPP configuration are correctly recorded to PCX {0}.
2009 4 7 WARNING The COM port belongs to two modem pools: {0} and {1}.
Remove the COM port from one modem pool.

2010 10 46 MAJOR Unable to subscribe to LDAP notifications service.
ModemMonitorDll will be unloaded.
Check that LDAP server is correctly started.
2011 10 46 CLEARED Subscription to LDAP notifications successful.
2012 10 46 MAJOR Unable to subscribe to system notifications service.

ModemMonitorDll will be unloaded.
Check ModemMonitorDll's log file.
2013 10 46 CLEARED Subscribe to system notifications successful.
2014 10 46 MAJOR The operating system can't detect a modem behind this COM port.
Check that a modem is correctly declared on this COM port.

2015 10 46 CLEARED The operating system has detected a modem behind this COM port.
2016 2 7 MINOR Multiple IP answer addresses from PCX; the second IP answer address
is {0}.
Possible explanation:
- Slow network (look at with Administrator's network)

- Slow CPU
- Double active CPU on spatial redundancy mode
- Other…
2018 2 10 WARNING From Pbx {0} the Ip address has been changed : active IP address = {1},
unavailable IP address = {2}.
- In spatial redundancy the CPU has been swapped

- New Ip address for pbx corresponding to a new network configuration
- Other...
2020 2 10 WARNING Impossible to connect PCX {0} because there are not enough modem(s)-
channel(s) in pool of modem ( channels available : {1}, number of
aggregation demanded {2}).
Possible resolution:
- Increase the number of COM in modem pool associated to this PCX

- Decrease the number of channel to aggregate
2022 2 10 WARNING Impossible to connect PCX {0} because there are not enough channel(s)
demanded available ( channels available : {1}, number of aggregation
demanded {2}).

- Decrease the number of channels to aggregate
2024 2 10 WARNING PCX {0} connected but all channel(s) demanded are not established
( channels connected : {1}, number of aggregation demanded {2}).

- Decrease the number of channel to aggregate
- If it's a S0 modem with driver ML-PPP don't choose B2channel option
for PCX (on tab connectivity)
2026 2 10 WARNING During a demand of connection to PCX {0} a problem occurs though
COM port {1}.

- Problem establishing communication with remote system

- Problem on channel or modem chosen (power this device down, then
back on)
- Problem on PPP layer, for example if CHAP authentication is
launched, verify that the corresponding field in directory is written
correctly (for PCX, on connectivity tab),
- Other...
2027 2 10 CLEARED The connection to PCX {0} though COM port {1} is established.

22.7. License Manager
This list concerns alarm relative to License control.
Event Probable
Type Cause
4000 11 51 WARNING Number of users has passed {0}% of the license maximum.
It is recommended that you start planning to increase the NMC capacity to

support
a bigger network.
Contact your distributor for more information.
4001 11 51 MAJOR Number of users has passed {0}% of the license maximum.
You should start planning to increase the capacity of NMC to support

a bigger network.
4002 11 51 CRITICAL Number of users has passed {0}% of the license maximum.
The user capacity of the NMC has been exceeded; it is no longer possible
to
start an NMC client.
You must increase the capacity of NMC to support
a bigger network.
4003 11 51 CLEARED The alert {0} has been cleared
4006 11 51 WARNING Problem verifying the PCX hardware key. Reason No. {0}.
There was a problem verifying the PCX hardware key which is used to
check the NMC
license.
Reason:
No. 2: No PCX contains the hardware key defined in the NMC license
file.
No. 3: An FTP error occurred. It is not possible to communicate with the
PCX or the
FTP account (username/password) is wrong.
No. 4: An LDAP error occurred.
No. 6: An error occurred during extraction of the PCX hardware key.
Look in the license logfile for more information.
Note:
The PCX that contains the hardware key specified in the NMC license
file has the
attribute 'License Control Key' set to 1.
The problem should be resolved within {0} days;
otherwise it will not be possible to use the NMC.

4007 11 51 MAJOR Problem verifying the PCX hardware key. Reason No. {0}.
check the NMC
license.
Reason:
file.
PCX or the
Note:
file has the
4008 11 51 CRITICAL Problem verifying the PCX hardware key. Reason No. {0}.
check the NMC
license.
Reason:
file.
PCX or the
Note:
file has the
4009 11 51 CLEARED The PCX hardware key has been verified.
4010 11 51 CRITICAL The internal parameters of the license server are no longer correct.
Look in the the license logfile for more information.
It will no longer be possible to start the NMC client before the PCX
hardware key
is verfied.
Please contact your NMC distributor.

4011 11 51 WARNING LDAP server has not been synchronized with all 4400s for {0} days.
Start 'Scheduler' and check that synchronization of LDAP server with all
4400s is
periodically scheduled.
4012 11 51 MAJOR LDAP server has not been synchronized with all 4400s for {0} days.
4400s is
4013 11 51 CRITICAL LDAP server has not been synchronized with all 4400s for {0} days.
4400s is
4014 11 51 CLEARED LDAP server is being synchronized with all 4400s.
4017 11 9 CRITICAL The license server's internal parameters are no longer correct.
Refer to the license logfile for more information.
It will no longer be possible to start the NMC client before fixing the
problem.
Please contact your NMC distributor.
4018 11 9 CLEARED The license server's internal parameters are now correct.
4019 11 51 WARNING Number of PCX exceeds {0}% of the licensed number.

a bigger network.
4020 11 51 MAJOR Number of PCX exceeds {0}% of the licensed number.

a bigger network.
4021 11 51 CRITICAL Number of PCX exceeds {0}% of the licensed number.

The PCX capacity of the NMC has been exceeded; it is no longer possible
to
start an NMC client.
a bigger network.

4022 11 51 CLEARED Alarm {0} is no longer relevant.
4023 11 51 WARNING Notice: license will expire in {0} days
The license must be updated/

4024 11 51 MAJOR Notice: license will expire in {0} days

4025 11 51 CRITICAL Notice: license will expire in {0} days

4026 11 51 CLEARED License updated
4027 11 51 WARNING The license file is installed on another server; OmniVista 8770 will shut
down in {0} days.
Each server must have its own license file.

4028 11 51 MAJOR The license file is installed on another server; OmniVista 8770 will shut
down in {0} days.

4029 11 51 CRITICAL The license file is installed on another server; OmniVista 8770 will shut
down in {0} days.

4030 11 51 CLEARED End of duplicate license usage
4031 11 51 WARNING Too many unexpected events during license verification: OmniVista 8770
may shut down.
4032 11 51 MAJOR Too many unexpected events during license verification: OmniVista 8770
may shut down.
4033 11 51 CRITICAL Too many unexpected events during license verification: OmniVista 8770
may shut down.
4034 11 51 CLEARED End of alarm: "Too many unexpected events during license verification."
4035 11 51 WARNING RTU snapshot did not happen for {0} days.

4036 11 51 MAJOR RTU snapshot did not happen for {0} days.
Start 'Scheduler' and check that RTU snapshot is periodically scheduled.

4037 11 51 CRITICAL RTU snapshot did not happen for {0} days.
Start 'Scheduler' and check that RTU snapshot is periodically scheduled.

4038 11 51 CLEARED RTU Snapshot is finished successfully.

22.8. Service Manager
The list concerns alarm relative to NMC service Manager (in charge to launch and to monitor 8770
services).
Event Probable
Type Cause
6000 2 0 MINOR LDAP Initialization Failed.
6001 2 0 MINOR Connection to LDAP server on {0} failed.
6002 2 0 CLEARED Connected to LDAP server on {0}:{1}.
6003 2 0 MINOR LDAP server on {0} is not responding.
6100 2 0 MINOR Connection to Service Control Manager on {0} has failed ({1}).
6101 2 0 CLEARED Connected to Service Control Manager on {0}.
6110 2 0 MINOR Stop service request on {0} failed ({1}).
6111 2 0 MINOR Abort of service via NT on {0} has failed ({1}).
6112 2 0 MINOR Abort of service via CORBA on {0} has failed ({1}).
6113 2 0 CLEARED UniStop of service on {0} successful.nstall of service on {0} has failed
({1}).
6120 2 0 MINOR Uninstall of service on {0} has failed ({1}).
6121 2 0 CLEARED Uninstall of service on {0} successful.

6130 2 0 MINOR Install of service on {0} has failed ({1}).
6131 2 0 CLEARED Install of service on {0} successful.
6132 2 0 MINOR Installation of service {0} using Windows account \"{1}\" failed ({2}).
The service is started using the Windows built-in account Local

System;
it will not be able to access shared network, network driver, or printer.
6140 2 0 MINOR Start of service on {0} failed ({1}).
6141 2 0 CLEARED Service {0} is running.
6142 2 0 MINOR Starting service {0} using NT account \"{1}\" failed ({2}).
Service rights are restricted to the PCX system.

6150 2 0 CRITICAL Service {0} is not running normally ({1}).
6151 2 0 CLEARED Service {0} is running normally.
6160 3 49 CLEARED Size of {0} disk or directory (\\\\{4}\\{1}) does not exceed minimum
threshold any more.
6161 3 49 MINOR Less than {2} {3} remain available on {0} drive (\\\\{4}\\{1}).
6162 3 49 MINOR {0} Directory (\\\\{4}\\{1}) occupies more than {2} {3} of entire drive.
6163 3 49 MINOR {0} Directory (\\\\{4}\\{1}) takes more than {2} {3}.
6164 3 49 CLEARED Size of {0} disk or directory (\\\\{4}\\{1}) does not exceed maximum
threshold any more.
6165 3 49 MAJOR Less than {2} {3} remain available on {0} drive (\\\\{4}\\{1}).

6166 3 49 MAJOR {0} Directory (\\\\{4}\\{1}) takes more than {2} {3} of entire drive.
6167 3 49 MAJOR {0} Directory (\\\\{4}\\{1}) takes more than {2} {3}.
6170 3 17 CLEARED Purge of archive {0} ('{2}' on {1}) succeeded.
6171 3 17 WARNING Purge of archive {0} ('{2}' on {1}) failed ({3}).
6200 10 39 WARNING Alarms server appears non-responsive.

22.9. Scheduler
This list concerns alarm relative to scheduled task execution and automatic deletion.
Event Probable
Type Cause
7000 10 2 MAJOR Scheduled task '{0}' failed.
A task executed by the scheduler has definitely failed.
Look at the log file generated for this task execution.
7001 10 2 CLEARED Task '{0}' has been removed.
Scheduler has removed the job per an operator request or because
the job was
too old.
7002 10 2 CLEARED Scheduled task was successful.

A task executed by scheduler finished successfully.
Look at the log file generated for this task execution.

22.10. SyncLdapPbx
This list concerns alarm relative to PCX synchronization
Event Probable
Type Cause
10000 4 9 MINOR The string {0} is not compatible with the PCX character set.
10001 2 9 MAJOR The PCX {0} refused modification of the field {1} with the value {2}
on station {3}.
10002 2 47 CRITICAL Loss of the connection with the directory server

SyncLdapPbx cannot connect with the directory server.
10003 2 47 CLEARED Connection established with the directory server
10004 11 46 MAJOR License Error: {0}.

The license file is invalid.
10005 11 46 CLEARED License file valid
10006 11 46 MAJOR Configuration Error

Invalid parameters for the 4400. Mismatch with the 4400 data.
10007 3 49 MAJOR Synchronization failed (disk full).

Not enough disk space to start the synchronization.
10008 3 49 MAJOR Synchronization failed on PCX {0} (disk full).

Not enough disk space to synchronize this PCX.
10009 4 9 WARNING Update refused by the PCX: the name {0} is too long. The max size
is {1}.
No updates done on either the PCX or on LDAP.
10010 4 9 WARNING Update refused by the PCX: the name {0} is too long. The max size
is {1}.
No updates done either on the PCX or on LDAP.
10011 11 46 MINOR The synchronization has failed for this node.

The synchronization has failed.

10012 11 46 MAJOR The synchronization for this node has failed permanently.
All the requested retries have failed.
10013 11 46 CLEARED The synchronization is successful.
10014 11 7 WARNING The node number has been updated during the synchronization
The node number has been updated according to the value set on
the PCX.
10016 2 0 WARNING Concerning partial load : the parameter

system_parameter/sync_47xx_4400 of this PCX is set to FALSE.
10017 2 7 WARNING Wrong configuration for the synchronization slice number.

All PCXs may not be synchronized.
10018 11 7 WARNING There are no accounting files to download from this call server.
Could not find new accounting files.
10019 11 7 WARNING There's no traffic observation files to download from this call server.
Could not find new traffic observation files.
10020 11 7 WARNING There's no VOIP files to download from this call server.
Could not find new files.
10021 11 7 CLEARED There are new files.
10022 2 7 MAJOR Misconfiguration in PPP settings for urgent alarms

Misconfiguration in PPP settings: cannot update the OmniPCX
Office PPP parameters for sending urgent alarms
10023 11 7 WARNING There are no VoIP files to download from this OmniPCX Office
system
Possible causes:
- The loading of the IP files was requested while the
OmniPCX Office collection process was inactive.
- This synchronization is too soon after the most recent;
OmniPCX Office has not generated new files.
- The OmniPCX Office collection collection process is down.
10024 2 7 MAJOR Misconfiguration in HTTP settings for urgent alarms

Misconfiguration in HTTP settings: cannot update the OmniPCX
Office HTTP parameters for sending urgent alarms.

10025 3 2 MAJOR Error returned from PCX
GCSAdmin: CMISE Error
10026 3 2 MAJOR Error returned from 8770

GCSAdmin: Computing Error
10027 3 2 MINOR Cannot get Software Update Status from the PCX {0}
Possible reasons are:
- Unable reach the PCX
- It is not master DN
10028 3 2 CLEARED Software Update Status retrieved successfully from the PCX {0}
Software update status updated in LDAP successfully
10029 3 2 MINOR RSH execution failed for this call server
10030 3 2 CLEARED Successful RSH execution for this call server
10031 3 2 MINOR Retrieval of log files failed
10040 2 0 CRITICAL Could not connect with OXO; permanent failure on alarm.
Unable to reach OXO. No additional retry will be done. See the log
file for the reason.
10041 0 0 CLEARED Connection with OXO successfully established

22.11. Load accouting
This list concerns alarm relative to Accounting process: loading, cost calculation.
Note
The MAO.DAT is not used by OmniVista 8770, so the alarm relative to MAO.DAT file will never be raised
by OmniVista 8770.
Event Probable
Type Cause
13000 11 51 WARNING {0}: {3} ({4}) {2} ({6}) Threshold ({1}) for {5} exceeded.
Tracking threshold is exceeded.
13001 10 7 MINOR Cost calculation error during record loading from PCX {0}.
Carrier configuration error.
See log file for more details.
13002 11 0 WARNING Manual deletion of the item: {0}.
13011 10 46 MAJOR Record File {0} cannot be opened.

Consequence: The 'TAXxxxxx.DAT' files cannot be processed.
Probable cause: Bad files were generated.
13012 10 46 MINOR Rejected Record File {0} cannot be opened.

The rejected records cannot be saved.
13013 10 46 MAJOR 'TAXxxxxx.DAT' files have been renamed in {0} because of a read
error.
Consequence: The records cannot be loaded.
Probable cause: The content of the files may be damaged.
13014 10 46 MAJOR 'TAXxxxxx.DAT' files could not be renamed in {0}.

Read error of 'TAXxxxxx.DAT' files.
Consequence: Records cannot be loaded.
Probable cause: File content is damaged.
13015 10 46 WARNING Inserted 'TAXxxxxx.DAT' files cannot be renamed in {0}.

Consequence: The 'TAXxxxxx.DAT' files cannot be moved from the
directory.
13016 10 46 WARNING Inserted 'TAXxxxxx.DAT' files cannot be removed from {0}.

Consequence: The 'TAXxxxxx.DAT' files are still in the PCX directory.
13017 10 46 MAJOR 'TAXxxxxx.DAT' file has been rejected in {0} because of a database
error.
Consequence: The 'TAXxxxxx' files were rejected. The records did not
load.
Likely cause: Database insertion error.

13018 10 46 MAJOR 'TAXxxxxx.DAT' files cannot be rejected in {0} because of a database
error.
Consequence: The 'TAXxxxxx.DAT' files cannot be moved into the
rejected directory.
The records were not loaded.
13019 10 46 MAJOR Bad Format in {0}.The records have been rejected in {1}.
Consequence: The records in the file were not loaded.
13020 10 46 MAJOR Bad records in {0}. The records have been rejected in {1}.
Probable cause(s):
1. The line is too long.
2. Bad date format.
3. Bad line content.
13021 10 46 MAJOR {0}: Loader will stop because it cannot access Database.
Verify that Database Engine is launched.
13022 2 49 MAJOR Loader will stop loading in {0} because of insufficient disk space.
13023 10 46 MAJOR {0} : Bad value from CORBA.

No loading process.
13024 10 46 MAJOR MAO File {0} cannot be opened.

Consequence: The files 'MAOxxxx.DAT' cannot be processed.
13025 10 46 MINOR Reject MAO File {0} cannot be opened.

The rejected MAO records cannot be saved.
13026 10 46 MAJOR Files 'MAOxxxx.DAT' have been renamed in {0} because of a read
error.
Consequence: The MAO records cannot be loaded.
Probable cause: The MAO files content appears damaged.
13027 10 46 MAJOR Files 'MAOxxxx.DAT' could not be renamed in {0}.

Read error on 'MAOxxxx.DAT' files.
Consequence: The records cannot be loaded.
Cause probable : The file content is damaged.
13028 10 46 WARNING Inserted Files 'MAOxxxx.DAT' cannot be removed from {0}.

Consequence: The files 'MAOxxxx.DAT' are still in the PCX directory.
13029 10 46 MAJOR Bad Format in {0}. The MAO records have been rejected in {1}.
Consequence: The MAO records in the file are not loaded.

13030 10 46 MAJOR Bad MAO records in {0}. The MAO records have been rejected in {1}.
13031 10 46 MAJOR File {0} cannot be opened.

13032 10 46 MAJOR Read error in {0}.

13033 10 46 MAJOR File {0} is empty.

13034 10 46 MAJOR File {0} not found.

13035 10 46 MAJOR File {0} not found.
13036 10 46 WARNING File {0} not found in mao.lis.

Consequence: The file 'MAOxxxx.DAT' cannot be processed.

22.12. CMISE
This list concerns alarm relative to NMC CMISE service (in charge to send configuration request to
OmniPCX Enterprise).
Event Probable
Type Cause
15000 2 46 MINOR The transmission of a message to an application has failed (PCX: {0}).
Communication problem between Cmisd.exe and Comasync.dll. Or the
network connection to the PCX is down (check connection by pinging the
PCX).
15001 2 46 MAJOR Cannot initialize TCP.
15002 2 46 MAJOR Memory Allocation Error
15003 2 46 MAJOR Cannot read incoming message(s) from an application or a PCX.

Error reading the socket or memory allocation error.
15004 2 46 MAJOR Cannot register new connection.

Error recording new <socket> index in a table.
15005 2 7 MAJOR No remote address for PCX {0}; cannot place outgoing call.
Bad PCX configuration (wrong IP adress; PCX unknown in NMC).
15006 2 46 MAJOR Cannot initialize connections.

Network error or memory allocation error...
15007 2 46 MAJOR Cannot send the data.

Problem formatting the data to send to the PCX.
15010 2 5 WARNING Cannot establish connection with PCX {0}.

A network problem has appeared. Verify that the network link still exists
between the server
and the PCX.
Perform a <ping> operation from server to PCX in order to confirm the
network link.
15011 2 46 MAJOR Network Error.

The <select> operation has caused an incident on a <socket> .
15012 2 5 MINOR Network error after a connection ended.

15014 2 46 MINOR Problem reading a message from the PCX: {0}.
15019 2 5 MINOR Unknown Network Problem.

Verify the network NT configuration.

22.13. GCS
This list concerns alarm relative to NMC GCS configuration service (participate to OmniPCX Enterprise
configuration access).
Event Probable
Type Cause
15500 3 7 MAJOR Database MIB is missing.
A database MIB file is required to synchronize a PCX. Its default location is
$MIBPATH/bare/object.mgr
where $MIBPATH is set by attribute 'mibpath' in LDAP.
Check 'mibpath' attribute for entries GCSAdmin and GCSConfig in LDAP
Server. Verify MIB is present on
disk, or reinstall.
15501 3 7 CLEARED Database MIB has been found.
15502 3 6 MAJOR MIB {0} was not found in directory {1}.

A MIB file object.mgr is missing. Either it has been deleted -- in which
case, restart your configuration client, or
the MIB file location is corrupted. Confirm that the MIB file location is
stored in LDAP as server's attribute 'mibpath'.
15503 3 6 CLEARED MIB file {0} found and OK.
15504 3 0 MAJOR Cannot compile MIB {0}.

Either the MIB compiler is missing or it could not compile MIB. Verify
MIBCompiler program is present in the installation
directory. Check 'NMCMIBCompiler.log' for any error report.
15505 3 0 CLEARED MIB file compiled successfully.
15506 2 6 MAJOR Cannot reach GCS administration server.

GCSAdmin server or network may have a problem. Look at the
'NMCGCS_Admin.log'.
15507 2 6 CLEARED GCS administration server is available once again.
15508 2 6 MAJOR Cannot reach security server.

SecurityServer server or network may have a problem. Review
'NMCSecurityServer.log'.
15509 2 6 CLEARED Security server is available once again.

15510 2 5 MAJOR LDAP Protocol Error.
Check sever log file for precise error diagnosis. You may review the LDAP
error/access file.
15511 2 5 CLEARED Communication with LDAP server re-established.
15512 3 2 MINOR Synchronization on PCX {0} failed.

Check 'NMCGCS_Admin.log' for an exact description of problem.
15513 3 2 CLEARED PCX synchronization successful.
15514 2 5 WARNING CMISE request failed with error code.

A problem with the CMISE layer occurred. Verify if a CMISD alarm
appears to
explain this problem.
If there is no CMISD alarm, open the logfile 'Cmisd.log' to read the
description of this error.
For example if a CMISE connection is interrupted for any reason (a
network problem...), this alarm is triggered.

22.14. Load Past Time Performance
This list concerns alarm relative to Past Time Performance / Traffic data processing.
Event Probable
Type Cause
17000 10 46 MAJOR [{0}]: No INF file found for data file {1}.
Consequence: The file data (half an hour) cannot be loaded.
Possible causes:
1. INF file has not been produced by the PCX (no PMM data file has
been loaded for
the day)
2. The Poller has not given the INF file to the Loader (same as above)
3. The INF file has mistakenly been removed from the directory (bad
user action or
software error)
4. The INF file has been removed because it was old (directory
purge)
17001 10 46 MAJOR [{0}]: Data file {1} cannot be decompressed.

Probable cause: The file content was altered.
17002 10 46 MAJOR [{0}]: File {1} not found.

Description: the loader has seen the file on the disk, but at the point
of loading
it, could not find it.
Consequence: the file data (half an hour) cannot be loaded.
17003 10 46 MAJOR [{0}]: Cannot get file {1} format.

Probable cause: The file content was altered.
17004 10 46 MAJOR [{0}]: Memory allocation error for file {1}.

Probable cause: No memory space available.
17005 10 46 MAJOR [{0}]: Error while copying file {1} from disk to memory.
Consequence: the file data (half an hour) cannot be loaded.
Possible causes:
1. The file content was altered
2. The file header is incorrect
3. The memory space allocation failed
17006 10 46 MAJOR [{0}]: Wrong file {1} content.

Description: Wrong Magic field in file header
Probable cause: File content altered

17007 10 46 MAJOR Database request failed while constructing topology tree.
Consequence: history performance loading is impossible.
Possible causes:
1. Database connection failed
2. Incorrect table format
17008 10 46 MAJOR Installation date unavailable

Possible causes:
1. Database connection failed
2. Incorrect table Chargeable Entity format or table Chargeable Entity
empty
17009 10 46 MINOR Error while fetching company data.

Probable cause: Database connection failed.
17010 10 46 MAJOR Error while constructing memory structures.
17011 10 46 MAJOR Incorrect syntax in PTP API method call: {0}
17012 10 46 CLEARED Clear alarms related to a given PMM file.
17013 10 46 MAJOR Configuration error in ptpParameters field: CumulY contains unknown

object(s): {0}
Consequence: Yearly cumul may not work for all desired objects.
The directory ptp parameters field should be modified.
17014 10 46 MAJOR Invalid values were found in some traffic analysis files.
Data with invalid values were found during load. These values were
replaced by
default values.
Look at the log file (NMCLD_1 or NMCLD_2) to have more
information on these
values.
17015 10 46 MAJOR [{0}]: Instances number between the PMM file {1} and the INF file {2}
do not match.
Consequence: The data for a half an hour cannot be loaded.
Possible causes:
1. The Poller has not given the good INF file to the Loader.
2. The Loader does not select the good INF file for the PMM file.
17016 10 46 MAJOR Configuration error in traffic observation loading parameters: found

unknown object(s): {0}
Consequence: Some desired objects may not be loaded.
Traffic Observation loading parameters should be modified.

17017 10 46 MAJOR [{0}]: This file contains counters lower than 0.
Some data could not be loaded in the database.
17018 11 51 WARNING {0}: {3} ({4}) {2} ({6}) Threshold ({1}) for {5} exceeded.

22.15. Alarm Trigger
This list concerns alarm relative to action launched by Alarm trigger: email.
Event Probable
Type Cause
18000 3 46 MINOR The mailer cannot be initialized. Mail cannot be sent.
The mail server attribute for the NMC object in the LDAP database may
be empty.
Enter this attribute using the IP address or the name of a mail server.
If the port is not 25, you can put it after a colon.
Ex: mailserver:32
18001 3 46 CLEARED The mailer has been successfully initialized.
18002 3 46 MINOR Authentication failure.

Username and password did not match.
Use the correct username and password.
18003 3 46 CLEARED Authentication successful.

22.16. Ldap Directory Server ( plugins module )
This list concerns alarm relative to Directory issue (link creation between Device entry and Directory
person entry). A new alarm 19003 has been added to inform about homonymous directory entry
detected on a different cost center.
Event Probable
Type Cause
19000 11 46 MAJOR Duplicate name on {0}. The directory link for {1} cannot be created.
There are multiple entries with the same name in the company directory.
No link can be created between the system directory entry and a company
directory entry.
The link cannot be added in the system directory entry.

Resolve the duplicate name problem in the company directory.
19001 11 46 MAJOR The entry {0} already exists. No automatic creation for link with {1}.
To establish a link from the system entry, an automatic creation has
been requested. But the calculated identifier already exists in the
company
directory.
19002 11 46 MAJOR The creation of the entry {1} has been rejected with the status {0}.
No automatic creation for link with {2}.
To establish a link from the system entry, an automatic creation has
been requested. But the creation has been rejected in the company
directory.
19003 11 46 MAJOR The entry {0} exists already for different cost center. The directory link for
{1} cannot be created.
The link cannot be added in the system directory. Resolve the issue of
different cost center with the same name.
To establish a link from the system entry, an automatic creation has been
requested. But the calculated identifier already exists for different cost
center in company directory.
19004 11 46 MAJOR The entry {0} exists already for different cost center. The directory link for
{1} cannot be created.
There are multiple entries with the same name in the system directory.
Link cannot be created between the company directory
entry and system directory entry.
The link can't be added in the company directory entry. Resolve the
homonymy problem in the system directory.

22.17. Voice tickets load (OXE/OXO )
This list concerns alarm relative to VOIP ticket processing
Event Probable
Type Cause
21000 10 17 WARNING {0} contains records (tickets) with bad format.
This file cannot be loaded.

21001 10 17 MINOR File {0} cannot be decompressed.

21002 10 17 MINOR File {0}: read error
21003 10 48 MAJOR An internal error occurred while processing the file {0}.
For more information check the log file.
21004 10 46 MINOR Database insertion failed: file {0} cannot be loaded.
A database error occurred during record (ticket) insertion. This file
cannot be loaded.
21005 10 46 MAJOR Job status error
For more information see the log file
Unable to update correctly the job status
21006 10 46 MAJOR PCX not found
PCX not found in table:
Network number: {0}
subnetwork number: {1}
PCX number: {2}
Loader could not find a PCX in table

21007 10 46 MAJOR Could not load: database access failed
21008 10 46 MAJOR An unexpected error has occurred: could not load

20009 11 51 WARNING {0}: {3} ({4}) {2} ({6}) Threshold ({1}) exceeded.

20010 10 7 MAJOR A parameter is not defined the the algorihm {0} and the frmaing {1}
A needed parameter is not defined in the directory.

22.18. Collector module for the SyncLdapPbx Server
This list concerns alarm relative to Accounting file storage by collector option.
Event Probable
Type Cause
22000 4 7 MAJOR Cannot create directory {0}.
Check that access rights are correct.

22001 4 7 MAJOR Cannot browse directory {0}.

22002 4 7 MAJOR Cannot copy file {0}.
22.19. SaveRestore
This list concerns alarm relative to Backup and OmniPCX Enterprise software download.
Event Probable
Type Cause
23000 10 46 MAJOR Save operation failed.
Check the operation log file.

23001 10 46 CLEARED Save operation completed successfully.
23002 10 46 MAJOR Restore operation failed.

23003 10 46 CLEARED Restore operation completed successfully.
23004 10 46 MAJOR Software Download operation failed.

23005 10 46 CLEARED Software Download operation completed successfully.

22.20. Radius
This list concerns alarm relative to use of password checking through a Radius server.
Event Probable
Type Cause
24000 2 5 CRITICAL No response from any RADIUS server!
24001 2 5 CLEARED Communication with one of the RADIUS servers is restored.
24002 2 5 CRITICAL Failed to communicate with RADIUS server {0}.
24003 2 5 CLEARED Communication with one of the RADIUS servers is restored.
24004 2 7 CRITICAL RADIUS server {0} issued a challenge for the user {1}
OmniVista does not support challenges and refuses access to challenged
users.
Contact the RADIUS administrator; RADIUS server must not challenge for
OmniVista users.
24005 2 7 CRITICAL Although OmniVIsta is configured to use RADIUS, No RADIUS server has
been declared.
24006 2 7 CLEARED RADIUS server(s) is/are declared.
24007 2 7 CRITICAL Security license is not in license file; RADIUS could not be used.
24008 2 7 CLEARED License corresponds to the RADIUS configuration

22.21. Password Policy
This list concerns alarm relative to use of password aging and complexity checking.
Event Probable
Type Cause
25000 11 56 MAJOR User account is locked for user ID: {0} with name: {1}
User account specified in the additional information column is locked.

Reset the password.
25001 11 56 MAJOR Log file: {0}
Check the log file described in the additional information column for the
Expired Passwords and reset their passwords.
25002 2 56 MAJOR Administrator {0} has no email Configured.
User account specified in the aditional information has not configured

email id So not able to send forgot password mail.
25003 2 5 MAJOR No email could be sent to Admin {0} because of a SMTP failure.
Not able to send email toadmin as SMTP failure. Check SMTP

configuration.
25004 10 9 CRITICAL Unknow Admin {0} tries to set a password
Unknown admin mentioned in the additional information tries to set a

password.Check Administrator name.

22.22. Audit Server
This list concerns alarms relative to Audit server.
Event Probable
Type Cause
26000 11 46 MINOR The record {0} could not be inserted into the Database.
26001 11 9 MAJOR Cannot open the audit log file {0}
26002 11 9 MINOR Log files may have been overwritten by PBX
26010 2 47 CLEARED Connection established with the directory server
26011 2 47 CRITICAL Loss of connection with the directory server
26012 2 47 CRITICAL Bad value from CORBA

22.23. Device Management Server
This list concerns alarms relative to Device Management server
Event Probable
Type Cause
28001 3 7 CRITICAL Device manager has configuration LDAP problems: {0}
Check DM log files for detailed information. Verify that DM LDAP config
is correct.
28002 6 17 MAJOR File <{0}> does not exist
Check log files for detailed information. Verify that the file is included in
OmniVistaWebService.aar.
28003 10 9 MINOR File format <{0}> is invalid
Check DM log files for detailed information. Verify that file format
included in OmniVistaWebService.aar is correct.
28004 3 7 CLEARED Device manager initialization succeeded
28005 6 17 CLEARED File <{0}> loaded successfully
28051 6 17 MAJOR The schema file <{0}> for OXE device does not exist
Check log files for detailed information. Verify that the file exists.
28052 10 9 MINOR The OXE device schema file <{0}> format is invalid
Check DM log files for detailed information. Verify that the file format is
valid.
28053 6 17 MINOR The schema label file <{0}> for OXE device does not exist
Check DM log files for detailed information. Verify that the label file
exists.
28054 10 9 WARNING <{0}> file format label for OXE device is invalid
28055 6 17 CLEARED The schema file <{0}> for OXE device is good
28056 6 17 CLEARED The schema label file <{0}> for OXE device is good
28061 6 6 MAJOR Retrieval of schema file for OXE MME model name <{0}> was
unsuccessful: {1}

Check log files for detailed information. Verify that GCS/OXE MME
interface is working as expected.
28062 2 6 CRITICAL Initialization of GCS/OXE MME interface <user: {0}, locale: {1}> was
unsuccessful: {2}
28063 2 6 CLEARED Connected to GCS/OXE MME application with <user: {0}, locale: {1}>
28064 6 6 CLEARED Retrieval of schema file for OXE MME model name <{0}> was succesful
28065 10 0 MAJOR device with the same id {0} is already associated with an OXE user
28066 3 0 MAJOR The initialization of connection to {0} failed due to {1},Please check
maintainance login and password.
28067 10 0 CLEARED The connection to {0} is established sucessfully.

22.24. Unified User Management ( UUM )
This list concerns alarms relative to UUM
Event Probable
Type Cause
29000 2 6 CRITICAL UUM server cannot communicate to GCS/OXE MME: <user: {0}, locale:
{1}> with error message: {2}
Check UUM log files for detailed information. Verify that GCS/OXE MME
29001 2 6 CLEARE UUM server connected to GCS/OXE MME successfully (userId<{0}>,
D langCode<{1}>).
29002 6 6 MAJOR Retrieval of schema from GCS/OXE MME on UUM server or model
name <{0}> has a problem: {1}
Check UUM log files for detailed information. Verify that GCE/OXE MME
29003 6 6 MAJOR Retrieval of template from GCS/OXE MME from UUM server for model
name <{0}> has a problem: {1}
Check UUM log files for detailed information. Verify that GCE/OXE MME
29004 6 6 CLEARE UUM server successfully retrieved the schema from GCS/OXE MME for
D model name <{0}>
29005 6 6 CLEARE UUM server successfully retrieved the template from GCS/OXE MME for
D model name <{0}>
29020 2 6 CRITICAL UUM Server cannot communicate to ICS: ICS name: <{0}>, language:
<{1}> with error message: {2}
29021 2 6 CLEARE UUM Server connects to ICS successfully (ICS name<{0}>,

D language<{1>;).
29060 2 6 CRITICAL UUM server cannot connect to the specified OXE (LdapLogin <{0}>) with
error message: {1}
Check UUM log files for detailed information. Verify that OXE is working
as expected.
29061 2 6 CLEARE UUM server connected to OXE successfully (LdapLogin <{0}>)
D

22.25. ICE Configuration ( OpenTouch )
This list concerns alarms relative to OpenTouch
Event Probable
Type Cause
30000 2 7 MAJOR Subscription failed
Event subscription failed
Events from ICE node will not be received
30001 2 7 MAJOR Unsubscription failed
ICE event unsubscription failed
Unnecessary events may be received from ICE Node.
30002 10 2 MAJOR Notification operation {0} fails. Error: {1} Detail: {2}
More details available in NMCICEConfiguration.log file
ICE event update into LDAP failed. Synchronize the ICE node.
30003 10 2 CLEARED Notification operation {0} successful
30004 10 46 WARNING Connection impossible : node not reachable at : {0}
Network failure (or) node in starting mode (or) bad configuration of the
public or private URL
22.26. RTU
This list concerns alarms relative to RTU
Event Probable
Type Cause
31000 10 37 MAJOR Invalid KPI : {0}
Invalid KPI for consecutive 5 days

APPENDIX
23. APPENDIX 1 : SYNOPTIC OF ACCOUNTING OPERATIONS
OmniPCX Enterprise ftp Transfer
account –v
Buffer account save 21 cmd
account compress 22 (SSH) Ports 49152 -
65535
Verrous logiciels :
Masking Accounting users
Tickets local-local
Data (SYN) O
Tickets réseau-local
49152-65535 Ports 49152 - m
Storage filters 65535 ni
V
i
s
ta
Compressed files
accview ftp 8
TAXAxxxx.DAT 7
ACCOUNT.LIS 7
0
OXO ftp
Buffer OXO
1000 tickets
cmd (PASV)
30021 Ports 49152 -

Disk 30000 tickets 65535
Data (SYN)
maximum
Ports 49152 - Ports 49152 -
65535 65535
OmniVista 8770

Omnivista 8770
Insertion Chargeableentity table
Cost Calculation
 Ticket table
Filters
Extractor
Filters Requestor

Designer
Unicity check Cumul
Cost Calculation

Loader 
Data\Loader\Network\Su SQL Tables
bnetworknodenumber EntityDailyCounter
Report
• TAXAxxx.DAT OrgDailyCounter
• ACCOUNT.LIS ProjectDailyCounter
or CarrierDailyCounter Extractor
\Alizenodenumber DirectionDailyCounter
• TAXAxxx.alz CCNDailyCounter
Cumul 
Rejected Monthly Counters
Cumul 
Directory Yearly Counters
PCX \ Data Collection Last
polled accounting file

24. APPENDIX 2 : DESCRIPTION OF OmniPCX Enterprise TICKET
FIELDS
Use in function of type call

Field Description / Value Local & ABC
Outgoing Incoming
network transit
Ticket Version ED5.1 X X X X
Called Number Outgoing call: real called number X - X X
Incoming call: calling number
Charged Number Outgoing call: the internal calling number X X X X
Incoming call: the internal calling number
Charged User Name Depend on the charged number - - X X
Charged Cost Center Depend on the charged number X - X X
Charged Company Not used - - - -
Charged Party Node 100*subnetwork number + node number X X X X
In heterogeneous network this field isn’t filled in if the
protocol does not give it
Sub address Used when ISDN outgoing call otherwise empty - - X X
Calling Number Transferring party number after transfer X - X X
Call Type 0: PublicNetworkOutgoingCall X X X X
1: PublicNetworkOutgoingCallThroughPrivateNetwork
2: PrivateNetworkOutgoingCall
3: LocalNetworkCall
4: PublicNetworkIncomingCall
5: PublicNetworkIncomingCallThroughPrivateNetwork
6: UnspecifiedCall
7: PrivateNetworkOutgoingCallToPublicNetwork
8: PrivateNetworkOutgoingCallToPrivateNetwork
9: PublicNetworkIncomingCallToPrivateNetwork
10: PrivateNetworkIncomingCallToPrivateNetwork
11:
PublicOrPrivateNetworkOutgoingCallThroughPrivateNetw
ork
12:
PublicOrPrivateNetworkIncomingCallThroughPrivateNetwo
rk
13: PrivateNetworkIncomingCall
14: LocalLocalCall
15: LocalTransitCall
Cost Type 0: Unspecified – ABC-F trunkCall - - X -
1: AnalogTrunkCall
2: ISDNCircuitSwitchedCall
3: ISDNPacketCallX25-Bchannel
4: ISDNPacketCallX25-Dchannel
5: X25
6: DigitlNonISDN

Outgoing Incoming
network transit
End Date Time End communication date or communication transfer X X X X
Yyyymmdd hh:mm:ss
Charge Units Meter pulses received from the public network - - - X
Cost Info - - X X
Duration X X X X
Trunk Identity Trunk Identification Number (public trunk or private tie- - - X X
line)
Trunk Group Identity Trunk Group Number - X X X
Trunk Node 100*subnetwork number + node number - X X X
Personal or Business 0: Personal - - X -
Call 1: Business
2: Normal
3: Guest
Access Code Project Account Code, Personal Identifier Number or - - X -
empty
Specific Charge Info 0: SIOPriorityTrunkGroup - - X -
2: PBXGeneratedChargeUnits
3: AnalogWithoutChargeUnits
4: Transcom
5: AccurateDuration
Bearer Capability for 0: Unspecified - - X -
an ISDN call 1: Unrestricted
2: Speech
3: Audio3
4: Audio7
5: Audio15
6: Video
High Level Comp 0: Unspecified - - X -
(type of user in ISDN 1: Telephony
call) 2: Fax Group3
3: Mixed Mode
4: Fax Group4
5: Teletex Char
6: Videotex
7: Telex
8: MHS
9: OSI application
10: Sound
11: SoundVideotex
12: SlowScanVideo
13: Not Standard Application
Data Volume Number of transmitted bytes when ISDN communication - - - -
User To User Volume Number of transmitted bytes or number of mini-messages - - X -
(system option)

Outgoing Incoming
network transit
External Facilities 0: CallingLineIdentificationPresentation - - X -
1: ConnectedLineIdentificationPresentation
2: CallingLineIdentificationRestriction
3: ConnectedLineIdentificationRestriction
4: MaliciousCallIdentification
9: AdviceOfChargeAtSetup
10: AdviceOfChargeDuringCall
11: AdviceOfChargeAtEnd
13: CallWaiting
14: UserToUserSignalling
15: UserUserFacility
21: Mini-messaging
22: SubAddressing
Internal Facilities 5: CallForwardingUnconditional - - X -
6: CallForwardingOnBusy
7: CallForwardingOnNoReply
8: Transfer
23: BasicCall
24: OperatorFacility
25: Substitution
26: PriorityIncomingCall
27: Transit
28: PrivateOverflowToPublic
29: ReroutingPublicToPrivate
30: FaxServer
31: VoiceMail
32: CentralAbbreviatedNumberring
34: IntegratedServiceVPN
35: OverflowVPN
36: ARSService
37: Disa
Call Reference Not used - - - -
Segment Rate 1 Not used - - - -
ComType 0 : no specified - - X
1: Voice
2: Data
3: FacilityActivation
4: FacilityDeactivation
X25 Incoming Flow Not used - - - -
Rate
X25 Outgoing Flow Not used - - - -
Rate
Carrier 0: no carrier or unspecified - - X -
ARS table Number (1 to 10)
Initial Dialled Initial dialed number for incoming call or called number X X X X
Number when ARS service is used

Outgoing Incoming
network transit
Waiting Duration With incoming call : duration before answer (in seconds) - - - X
Effective Call Only with incoming call - - - X
Duration
Redirected Call Only with incoming and ABC network calls : the set who X - - X
Indicator answers isn’t the initial dialed number.
Start Date Time Yyyymmdd hh:mm:ss - - X X
Acting Extension Number of physical charged set. Can be a local number X - X -
Number (substitution case), public number (Disa), trunk group
number (FSxxx, FPxxx, FCxxx) or node number (SNxxx)
Called Number 100*subnetwork number + node number X - - -
Node
Calling Number 100*subnetwork number + node number X - - -
Node
Initial Dialled 100*subnetwork number + node number X X - -
Number Node
Acting Extension 100*subnetwork number + node number X - X -
Number Node Value 99999 if unknown node; Value XXX99 if only subnet
is known
Transit Trunk Group Incoming trunk group number on the transit node - X - -
Identity
Node Time Offset Time difference (in seconds) between 2 nodes; used when - - X X
the additional CDR is generated on the node of the
subscriber; No significant on trunk group node.

25. APPENDIX 3: EXAMPLE OF TRACE OF COST RECALCULATION
[22/09/2006 15:12:38] ----Ticket:

InitialStartDateTime:2006/07/18 15:41:59
StartDateTime:2006/07/18 15:41:59
Duration:3766
NodeTimeOffset:0
ChargeUnits:45
CalledNumber:0248480000
PbxName:N6_Eth
TrunkGroup:6
CallType:0
ComType:1
CostInfo:3330,000000
CarrierCode:4
IsAocAtSetup:0
IsUserToUserSignalling:0
IsCallForwardingUnconditional:0
UserToUserVolume:0
[22/09/2006 15:12:38] ----+Step CostCalculationStartStep
[22/09/2006 15:12:38] -----Step CostCalculationStartStep : OK
[22/09/2006 15:12:38] ----+Step LoadCarrierConfigDataStep
[22/09/2006 15:12:38] ---- +ObjectRq::init
[22/09/2006 15:12:38] ---- +SQLQuery::init(SQLQuery *)
[22/09/2006 15:12:38] ---- +ODBCConnection::createStatement
[22/09/2006 15:12:38] ---- -ODBCConnection::createStatement
[22/09/2006 15:12:38] ---- -SQLQuery::init(SQLQuery *)
[22/09/2006 15:12:38] ---- -ObjectRq::init
[22/09/2006 15:12:38] ----
+CarrierConfigurationOptionRq::selectCarrierConfigurationOption(1)
[22/09/2006 15:12:38] ---- +ObjectRq::assignRequest
[22/09/2006 15:12:38] ---- -ObjectRq::assignRequest
[22/09/2006 15:12:38] ---- +ObjectRq::appendRequest
[22/09/2006 15:12:38] ---- -ObjectRq::appendRequest
[22/09/2006 15:12:38] ---- +ObjectRq::executeRequest
[22/09/2006 15:12:38] ---- +ODBCConnection::commit
[22/09/2006 15:12:38] ---- +ODBCConnection::endTran
[22/09/2006 15:12:38] ---- -ODBCConnection::endTran : 1
[22/09/2006 15:12:38] ---- -ODBCConnection::commit
[22/09/2006 15:12:38] ---- +SQLQuery::execDirect
[22/09/2006 15:12:38] ---- SELECT BooleanValue FROM CarrierConfigurationOption
WHERE OptionId = 1
[22/09/2006 15:12:38] ---- -SQLQuery::execDirect
[22/09/2006 15:12:38] ---- -ObjectRq::executeRequest
[22/09/2006 15:12:38] ---- +ObjectRq::bindRequest
[22/09/2006 15:12:38] ---- -ObjectRq::bindRequest
[22/09/2006 15:12:38] ---- -
CarrierConfigurationOptionRq::selectCarrierConfigurationOption
[22/09/2006 15:12:38] ---- +ObjectRq::nextObject
[22/09/2006 15:12:38] ---- -ObjectRq::nextObject
[22/09/2006 15:12:38] ---- +ObjectRq::nextObject
[22/09/2006 15:12:38] ---- +SQLQuery::closeCursor

[22/09/2006 15:12:38] ---- -SQLQuery::closeCursor
[22/09/2006 15:12:38] ---- +SQLQuery::unbind
[22/09/2006 15:12:38] ---- +SQLQuery::freeStmt
[22/09/2006 15:12:38] ---- -SQLQuery::freeStmt
[22/09/2006 15:12:38] ---- -SQLQuery::unbind
[22/09/2006 15:12:38] ---- -ObjectRq::nextObject
[22/09/2006 15:12:38] ---- +SQLQuery::~SQLQuery
[22/09/2006 15:12:38] ---- +ODBCConnection::commit
[22/09/2006 15:12:38] ---- +ODBCConnection::endTran
[22/09/2006 15:12:38] ---- -ODBCConnection::endTran : 1
[22/09/2006 15:12:38] ---- -ODBCConnection::commit
[22/09/2006 15:12:38] ---- +SQLQuery::closeStatement
[22/09/2006 15:12:38] ---- -SQLQuery::closeStatement
[22/09/2006 15:12:38] ---- -SQLQuery::~SQLQuery
[22/09/2006 15:12:38] -----Step LoadCarrierConfigDataStep : OK
[22/09/2006 15:12:38] ----+Step CalculateActiveCarrierCostBeginStep
[22/09/2006 15:12:38] -----Step CalculateActiveCarrierCostBeginStep : OK
[22/09/2006 15:12:38] ----+Step IsCarrierExistForCallTypeStep
[22/09/2006 15:12:38] -----Step IsCarrierExistForCallTypeStep : YES
[22/09/2006 15:12:38] ----+Step FindFirstCarrierBeginStep
[22/09/2006 15:12:38] -----Step FindFirstCarrierBeginStep : OK
[22/09/2006 15:12:38] ----+Step SearchCarrierTrunkGroupConnectionStep
[22/09/2006 15:12:38] ----Find no carrier
No carrier found in the trunkgroup connection
[22/09/2006 15:12:38] -----Step SearchCarrierTrunkGroupConnectionStep : NO
[22/09/2006 15:12:38] ----+Step FindValidBranchStep
[22/09/2006 15:12:38] -----Step FindValidBranchStep : OK
[22/09/2006 15:12:38] ----+Step IsFirstCarrierFoundStep
[22/09/2006 15:12:38] ----Carrier: Carrier_One
This is the direct carrier
[22/09/2006 15:12:38] -----Step IsFirstCarrierFoundStep : YES
[22/09/2006 15:12:38] ----+Step FindFirstCarrierEndStep
[22/09/2006 15:12:38] -----Step FindFirstCarrierEndStep : OK
[22/09/2006 15:12:38] ----+Step CalculateSecondCarrierCostBeginStep
[22/09/2006 15:12:38] -----Step CalculateSecondCarrierCostBeginStep : OK
[22/09/2006 15:12:38] ----+Step IsCarrierCodeInTicketStep
[22/09/2006 15:12:38] ----Carrier Code = 4
Carrier code > 0 ==>looking for an indirect carrier
[22/09/2006 15:12:38] -----Step IsCarrierCodeInTicketStep : YES
[22/09/2006 15:12:38] ----+Step IsCarrierCodeInConfigStep
[22/09/2006 15:12:38] ----Find carrier code : Indirect4
There is a carrier with this code
[22/09/2006 15:12:38] -----Step IsCarrierCodeInConfigStep : YES
[22/09/2006 15:12:38] ----+Step IsCarrierCodeIndicateASecondCarrierStep
[22/09/2006 15:12:38] ----Carrier code indicate a second carrier: Indirect4
the carrier type is Indirect outgoing
[22/09/2006 15:12:38] -----Step IsCarrierCodeIndicateASecondCarrierStep : YES
[22/09/2006 15:12:38] ----+Step FindCarrierPrefixInCalledNumberStep
[22/09/2006 15:12:38] ----First Carrier Prefix Found = 0
[22/09/2006 15:12:38] -----Step FindCarrierPrefixInCalledNumberStep : OK
[22/09/2006 15:12:38] ----+Step FindValidBranchForSecondCarrierStep
Computing the second carrier cost
[22/09/2006 15:12:38] ----Called Number For Second Carrier = 0248480000

[22/09/2006 15:12:38]
-----Step FindValidBranchForSecondCarrierStep : OK
[22/09/2006 15:12:38]
----+Step IsSecondCarrierDirectionFoundStep
[22/09/2006 15:12:38]
----Best node digit: 8
[22/09/2006 15:12:38]
----Direction found
[22/09/2006 15:12:38]
----Current node digit: 4
[22/09/2006 15:12:38]
----Find direction: Nanterre->Ouest
[22/09/2006 15:12:38]
-----Step IsSecondCarrierDirectionFoundStep : YES
[22/09/2006 15:12:38]
----+Step SearchSecondCarrierCcnStep
[22/09/2006 15:12:38]
----Find ccn: *->024848:Aérospatiale Bourges
The CountryCityName is optional
[22/09/2006 15:12:38] -----Step SearchSecondCarrierCcnStep : OK
[22/09/2006 15:12:38] ----+Step ApplySecondCarrierTariffStep
[22/09/2006 15:12:38] ----Used Tariff: National
[22/09/2006 15:12:38] ----Calculation Mode: Exact Duration
[22/09/2006 15:12:38] ----Type: Voice/Data - Daily
[22/09/2006 15:12:38] ----Cost = 3766,000000
[22/09/2006 15:12:38] ----CostT = 4504,136000
[22/09/2006 15:12:38] -----Step ApplySecondCarrierTariffStep : OK
[22/09/2006 15:12:38] ----+Step CalculateSecondCarrierCostEndStep
[22/09/2006 15:12:38] -----Step CalculateSecondCarrierCostEndStep : OK
Computing the first carrier cost
[22/09/2006 15:12:38] ----+Step CalculateFirstCarrierCostBeginStep

[22/09/2006 15:12:38] -----Step CalculateFirstCarrierCostBeginStep : OK
[22/09/2006 15:12:38] ----+Step FindValidBranchForFirstCarrierStep
[22/09/2006 15:12:38] ----Called Number For First Carrier = 0248480000
[22/09/2006 15:12:38] -----Step FindValidBranchForFirstCarrierStep : OK
[22/09/2006 15:12:38] ----+Step IsFirstCarrierDirectionFoundStep
[22/09/2006 15:12:38] ----Find direction: *->Bourges
[22/09/2006 15:12:38] ----in carrier: Carrier_One
[22/09/2006 15:12:38] -----Step IsFirstCarrierDirectionFoundStep : YES
[22/09/2006 15:12:38] ----+Step SearchFirstCarrierCcnStep
[22/09/2006 15:12:38] ----Find no ccn
[22/09/2006 15:12:38] -----Step SearchFirstCarrierCcnStep : OK
[22/09/2006 15:12:38] ----+Step ApplyFirstCarrierTariffStep
[22/09/2006 15:12:38] ----Tariff: Cout_pabx
[22/09/2006 15:12:38] ----Calculation Mode: AOC
[22/09/2006 15:12:38] ----Cost = 3330,000000
[22/09/2006 15:12:38] ----CostT = 3330,000000
[22/09/2006 15:12:38] -----Step ApplyFirstCarrierTariffStep : OK
[22/09/2006 15:12:38] ----+Step CalculateFirstCarrierCostEndStep
[22/09/2006 15:12:38] -----Step CalculateFirstCarrierCostEndStep : OK
[22/09/2006 15:12:38] ----+Step CalculateFacilityCostBeginStep
[22/09/2006 15:12:38] -----Step CalculateFacilityCostBeginStep : OK
[22/09/2006 15:12:38] ----+Step IsCostInfoUsedForCostStep
[22/09/2006 15:12:38] -----Step IsCostInfoUsedForCostStep : YES
[22/09/2006 15:12:38] ----+Step SetNoFacilityCostStep
[22/09/2006 15:12:38] -----Step SetNoFacilityCostStep : OK
[22/09/2006 15:12:38] ----+Step CalculateFacilityCostEndStep
[22/09/2006 15:12:38] -----Step CalculateFacilityCostEndStep : OK
[22/09/2006 15:12:38] ----+Step AddActiveCostStep
[22/09/2006 15:12:38] -----Step AddActiveCostStep : OK
[22/09/2006 15:12:38] ----+Step CalculateActiveCarrierCostEndStep
[22/09/2006 15:12:38] -----Step CalculateActiveCarrierCostEndStep : OK
[22/09/2006 15:12:38] ----+Step IsCalculateComparisonCarrierCostStep

[22/09/2006 15:12:38] -----Step IsCalculateComparisonCarrierCostStep : YES
[22/09/2006 15:12:38] ----+Step CalculateComparisonCarrierCostBeginStep
[22/09/2006 15:12:38] -----Step CalculateComparisonCarrierCostBeginStep : OK
[22/09/2006 15:12:38] ----+Step SelectFirstOfFirstComparisonCarrierStep
[22/09/2006 15:12:38] -----Step SelectFirstOfFirstComparisonCarrierStep : NO
[22/09/2006 15:12:38] ----+Step CalculateComparisonCarrierCostEndStep
[22/09/2006 15:12:38] -----Step CalculateComparisonCarrierCostEndStep : OK
[22/09/2006 15:12:38] ----+Step CostCalculationEndStep
[22/09/2006 15:12:38] -----Step CostCalculationEndStep : OK
[22/09/2006 15:12:38] 4924 CostRecalculation: Active Costs:
First Carrier Cost:3330,000000
First Carrier:Carrier_One
First Carrier Direction:*->Bourges
First Carrier Ccn:NO CCN
First Carrier Tax:NO TAX
Facility Cost:0,000000
Second Carrier Cost:3766,000000
Second Carrier:Indirect4
Second Carrier Direction:Nanterre->Ouest
Second Carrier Ccn:*->024848:Aérospatiale Bourges
Second Carrier Tax:TVA
[22/09/2006 15:12:38] 4924 CostRecalculation: -ComputeCost::calculateCost
[22/09/2006 15:12:38] 4924 CostRecalculation:
+CostProfileMgr::computeVariableCost
[22/09/2006 15:12:38] ----+CostProfileMgr::internalComputeVariableCost
[22/09/2006 15:12:38] ----Paramètres entrants:
TicketDate : 2006-07-18 15:41:59
EntityId : 30579
This is the extension identity (refer to chargeableEntity table)
TicketCallType: 0
TicketPOB : 2
SumCost : 7096,000000
SumCostT : 7834,136000
[22/09/2006 15:12:38] ---- +CostProfileMgr::selectCostProfile
[22/09/2006 15:12:38] ---- EntityId = 30579
[22/09/2006 15:12:38] ---- +SQLQuery::execute

26. APPENDIX 4: OPERATIONS BLOCK DIAGRAM
OmniPCX Enterprise Transfer
Process obstraf
dbgobs
obsappli
+ O
m
n
Cwwdnnoo.pmm Cwwdxxnn.inf i
V
pmm.lis / pmm2.lis
i
s
t
Internal_tax process ftp F
a
account –v 8
Buffer account save 21 cmd
7
account compress 22 (SSH)
7
Software lock: 0
Storage filters Accounting users
Data (SYN)
Ports 49152-65535
Compressed files
accview
TAXAxxxx.DAT
ACCOUNT.LIS

OmniVista 8770
NMCLD_x.log
Tables SQL Tables SQL Tables SQL Tables SQL
Atg30mn Atgdaily Atgmonthly Atgyearly

Att30mn Attdaily Attmonthly Attyearly
Load in base Cumul Cumul Cumul
Sub30mn Subdaily Submonthly Subyearly
Trg30mn Trgdaily Trgmonthly Trgyearly
Bst30mn Bstdaily Bstmonthly Bstyearly
Dct30mn Dctdaily Dctmonthly Dctyearly
Hds30mn Hdsdaily Hdsmonthly Hdsyearly
Apm30mn Apmdaily Apmmonthly Apmyearly
Extraction and
data process of
incoming public
Trace of cumul: NMCCumulPtp_x.log
accounting
tickets
Extractor Service
(NMCExtractor_x.log
Loader
Data\Loader\Network\Sub Generation of reports

networknodenumber
• TAXAxxx.DAT
• ACCOUNT.LIS
• Cwwdnnnn.pmm
• Cwwdxxnn.inf
• pmm.lis/pmm2.lis
Rejected
System Directory
PCX\Data Collection
Last polled file

27. APPENDIX 5: DESCRIPTION OF SQL TABLES
Attendant Group tables (Atg30mn, Daily, Monthly, Yearly)

Attendant tables (Att30mn, Daily, Monthly, Yearly)

Trunk Group tables (Atg30mn, Daily, Monthly, Yearly)
Set tables (Sub30mn, Daily, Monthly, Yearly)

DECT parameter tables (Dct30mn, Daily, Monthly, Yearly)
DECT handset tables (Hds30mn, Daily, Monthly, Yearly)
ADPCM DECT tables (Apm30mn, Daily, Monthly, Yearly)
DECT base station tables

28. APPENDIX 6: WEBRTC GATEWAY – TRAFFIC OBSERVATION
❑ The analyze of communications going through the WebRTC gateway can be done on
▪ The duration of the communications,
▪ The number of communications,
▪ A period of the day.
OmniPCX Enterprise generates Call Detail Record (CDR) for each communication.
CDRs are stored on the OXE and can be retrieved on the Omnivista 8770 to create the reports wanted
by the administrator.
From the 8770, at the report creation, it’s needed to select the right fields
A first filter must be applied on the TrunkNode and TrunkgroupNumber fields to display the
concerned CDRs only.
• It’s the trunkgroup connecting the WebRTC Gateway to the OXE

Any communications between the OXE and the WebRTC gateway are initiated by the OXE, whatever
the initiator: a Rainbow client or a device on the OXE.
• So, there are only outgoing CDRs on the OXE to the Sip trunk connecting the WebRTC gateway.
• 3PCC implementation for every call launch from a Rainbow client.
CDRs produced for each call between the PBX and the WebRTC Gateway have a specific value in the
fields “Initial Dialled Number” and Called Number” fields.
• It’s a system internal number permitting to identify users in both worlds: OXE and Rainbow.
• This number identifier is unuseful for both end users or administrators.
• Consequently, it’s not possible to identify who is the caller and who is the called
• The extension field permits to identify the owner of the Rainbow client when it is implied in a
communication.
If the two parties of the communication use the Rainbow client, two CDRs are generated.
From the Report Application create a dedicated detail report definition to extract tickets on
the communications between the PBX and the WebRTC gateway

From the Report Application create a dedicated detail report definition to extract tickets on
the communications between the PBX and the WebRTC gateway
When the wanted fields are selected, the report can be generated and visualized.

Submitting a Service Request
Please connect to our eService Request application.
Before submitting a Service Request, please be sure:

− The application has been certified via the AAPP if a third party application is involved.
− You have read the release notes that list new features, system requirements, restrictions, and more,
and are available in the Technical Documentation Library.
− You have read through the related troubleshooting guides and technical bulletins available in the
Technical Documentation Library.
− You have read through the self-service information on commonly asked support questions and known
issues and workarounds available in the Technical Knowledge Center.
- END OF DOCUMENT -


TG0095en-Ed03 OmniVista 8770 Troubleshooting Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TG0095en-Ed03 OmniVista 8770 Troubleshooting Guide

Uploaded by

Copyright:

Available Formats

Troubleshooting Guide OmniVista 8770

TGOO95 ed.03 Release 3 and above

OmniVista 8770 Troubleshooting Guide

3.1. Principle ..................................................................................................................................... 12

4. FAILURE ANALYSIS ........................................................................................................................... 20

4.1. Analysis by stage ........................................................................................................................ 21

OmniVista 8770 - Release 3 and above

OmniVista 8770 - Release 3 and above

9. TRAFFIC PERFORMANCE COMPARISON .............................................................................................. 89

OmniVista 8770 - Release 3 and above

12. SNMP .......................................................................................................................................... 116

13.1. Overview .............................................................................................................................. 124

OmniVista 8770 - Release 3 and above

14. SECURITY ACCESS ....................................................................................................................... 141

15. INTERWORKING ON A VPN / NAT NETWORK ................................................................................ 151

16. RTU ............................................................................................................................................ 156

OmniVista 8770 - Release 3 and above

19.1 Overview .............................................................................................................................. 166

20.1 Overview .............................................................................................................................. 172

21. MSAD Plugin ................................................................................................................................ 173

21.1. Known issues ........................................................................................................................ 173

22. INTERNAL ALARMS LIST .............................................................................................................. 174

OmniVista 8770 - Release 3 and above

25. APPENDIX 3: EXAMPLE OF TRACE OF COST RECALCULATION ........................................................ 223

28. APPENDIX 6: WEBRTC GATEWAY – TRAFFIC OBSERVATION .......................................................... 233

OmniVista 8770 - Release 3 and above

1.2. Escalade to Technical Support :

• The impacted main module,

OmniVista 8770 - Release 3 and above

1.3. Issues linked to PC, Server, IT environment and application:

OmniVista 8770 is installed on a Windows system which, by architecture, supports

OmniVista 8770 - Release 3 and above

2.1. Complying with the installation prerequisites

2.2. Storing the installation data

2.3. Initial management and backup

2.4. Checking the installation

2.5. Saving the OmniVista 8770 elements

OmniVista 8770 - Release 3 and above

3.2. OmniVista 8770 server services

3.2.1. OmniVista 8770 Service Manager tool

Or in Control Panel\System and Security\Administrative Tools, the Services tool :

OmniVista 8770 - Release 3 and above

3.2.2. List of services

LDAP server • Oracle Directory Server Control Center

OmniVista 8770 - Release 3 and above

3.2.3. Dependency and control of the services

OmniVista 8770 - Release 3 and above

Rank1 Rank2 Rank3 Rank4 Rank5

If the ComServer service has not started:

3.3. Launch 8770 client and access to the applications

Complete these checks:

OmniVista 8770 - Release 3 and above

3.4. Status of the scheduled tasks

3.5. Server operation

OmniVista 8770 - Release 3 and above

3.5.5. Directory (OmniPCX Enterprise/Entreprise)

3.5.7. Traffic analysis (OmniPCX Enterprise/Enterprise)

OmniVista 8770 - Release 3 and above

• Check the status of the daily and weekly scheduled tasks:

3.5.9. Export, Print the reports

OmniVista 8770 - Release 3 and above

3.6. Check the license

OmniVista 8770 - Release 3 and above

OmniVista 8770 - Release 3 and above