You are on page 1of 8





Presentation

1.1

Call Log Information in the Open Telephony Server Service


The "local call metering" application retrieves call log tickets via the Open Telephony Server
service.

1.2

The Open Telephony Server service can save up to 200 tickets in a buffer

Local call log tickets are deleted when they are sent to the "local call metering" application

Unsuccessful calls (busy, unanswered call, etc.) are not logged in the Open Telephony
Server service

One local call in conversation generates one ticket

Local Call Metering Application Structure


The "local call metering" application consists of the following blocks:

Figure 1.1: Local Call Metering Application structure


-

The Configuration application is a user-friendly interface used to configure the local


metering file

The Call Log Driver retrieves all call log events from the Alcatel-Lucent OmniPCX Office
Communication Server and presents these log events in an orderly manner

The Metering Driver stores the local call log tickets in the output file (TicketCollector.xml)

 
     
 

1-1

Chapter

1.2.1



The TicketCollector.xml is the output file for tickets on the PC

Debug/Log is a global log text file, where all traces are stored

Log File
The global log file, located in the "Local call metering" application installation directory,
contains the following information:

1.2.2

"Local call metering" interface information

Alcatel-Lucent OmniPCX Office Communication Server information

Warning/Error information

XML File
When installing the "Local call metering" application, the Open Telephony Server interface
must be active.
When the "local call metering" application is running, call log information (metering tickets) is
extracted via the Open Telephony Server. These metering tickets are stored in an XML local
file, located in the application installation directory (by default) and named "TicketCollector.xml"
(by default).
The maximum number of tickets stored in the XML file can be changed by modifying the
configuration file.
The call log information includes:
-

Call date, call start time and call end time

Initial number: initial called party in case of transfer, pick-up, or other similar operation

Caller number

Called number and name (if available)

Note:
When the tickets number limit is reached, the "TicketCollector" file is emptied and its content is copied on
the local directory to an archive file as: TicketCollector_yyyymmdd_hhmmss.xml:
where "yyyymmdd" is the archive date and "hhmmss" is the archive time.

Installation

2.1

Installing the "Local Call Metering" Application


Prerequisite: Before installing the "local call metering" application, the user must have
administrator privileges on the local PC.
There are two ways to install the "local call metering" application:

1-2

Interactive (graphic) mode installation - installs the application using the InstallShield
Wizard running on a client PC.

Silent mode installation - allows you to run the installation program in the background
without interactive input. This method is based on a specific command line parameters.

 
     
 



If installing the "local call metering" application on a system that already includes a "local call
metering" application, the installation program acknowledges the existing application and
offers a "Modify" mode, and a "Remove" mode, so as to remove the old application and all
associated files before the new application is installed.
The "local call metering" application includes a configuration application and a "local call
metering" service.
Interactive installation
From the CD-ROM/DVD or from the download page of the WEB site:
To install the "local call metering" application using the InstallShield Wizard:
1. Install the application by running the setup.exe file located in the installation directory
2. Follow the Wizard's instructions to complete application installation
3. Restart the system in order to load the "local call metering" application as a Windows
startup service
It appears in the Windows "Services" list with an automatic (default value) Startup
Type.
Note 1:
The InstallShield also installs an application configuration program on the PC. A shortcut to the
configuration application is available from the PC desktop.

Silent installation
You can use the command line or "silent" mode to install the "local call metering" application in
the background with no need for user interaction.
To install the "local call metering" application in silent mode:
1. Run the following command: setup.exe /S /v"/qn INSTALLDIR=product_folder
USERNAME="username""
Where:
The product_folder is the user target folder
The user name must be entered within quotation marks.
Note 2:
The setup.exe file extracted from ZIP file "lcma_7.0.0_X.X.X_XX_Alcatel.zip.
Caution:
Do not add any space character between the option and its parameter:
Example:

setup.exe /S /v"/qn INSTALLDIR=c:\PCXTools USERNAME="Tom"": The


command is correct.

setup.exe /S /v "/qn INSTALLDIR=c:\PCXTools USERNAME="Tom"": The


command is not correct.

2. Restart the system in order to load the "local call metering" application as a Windows
startup service
It appears in the Windows "Services" list with an automatic (default value) Startup
Type.
Upon completion of installation
The "local call metering" application and its associated configuration application are installed

 
     
 

1-3

Chapter



on the PC.
Note 3:
The files included in the installation directory are the following:

metering local.exe: "local call metering" application configuration files

metering service.exe: "local call metering" service files

LCMA. conf: configuration files (once the application has been run)

TicketCollector. xml: output files (once the application has been run)

The "local call metering" application is installed and running.


You can now configure the "local call metering" application with the "local call metering"
application configuration program.
Note 4:
In case of a PC crash while the "local call metering" application is running, the application restarts
automatically.

2.2

Uninstalling the "Local Call Metering" Application


You can uninstall the "local call metering" application at any time using one of the following
methods:

2.3

Use the MS Windows Add/Remove Programs feature and select the "local call metering"
application.

Use the Uninstall "local call metering" application shortcut located on the desktop or in
the Programs folder.

Launch the installation program via setup.exe and select the Remove checkbox.

Updating the "Local Call Metering" Application


You can update the "local call metering" application at any time using one of the following
methods:
-

Launch the installation program via setup.exe and select the Modify checkbox.

Uninstall the "local call metering" application and install the new "local call metering"
application.

Configuration

3.1

Configuring the "Local Call Metering" Application


This is used to:
-

Configure the Alcatel-Lucent OmniPCX Office Communication Server name/address

Configure the password

Start/stop the application

Once the "local call metering" application is installed and running, you can launch the "local

1-4

 
     
 



call metering" application configuration program to set various driver parameter values.
"Local call metering" application configuration parameters are stored in the LCMA.conf file
located in the "Local call metering" application installation directory.
This file contains all "Local call metering" application parameters which are set with default
values when the "Local call metering" application is first installed. The file can be edited to
update certain parameters that are not configured by the "Local call metering" application
configuration program.
To configure an installed and running "local call metering" application:
1. Run the "local call metering" application configuration program by clicking on the desktop
shortcut or by selecting the "local call metering" application configuration program located
in the "local call metering" application installation folder.
The "local call metering" application configuration window is displayed with information
about the application version and the installation mode.

Figure 3.2: Configuring the "Local Call Metering" application

Click Save to save the Alcatel-Lucent OmniPCX Office Communication Server Host
Name address and the Admin password to the LCMA.conf configuration file.
Click Default to set all fields to their default values.
Click Autodetect to detect automatically the Alcatel-Lucent OmniPCX Office
Communication Server host name address.
Note 1:
If the Autodetect feature fails, the field can also be filled in manually.

 
     
 

1-5

Chapter



Click TestConnection to test the Alcatel-Lucent OmniPCX Office Communication


Server Host Name address, the Admin password and the application version.
Click Start /Stop to start or stop the "local call metering" service.
Note 2:
The current application status is indicated by a green or red icon.

The Call Log Update Timer is a timer mechanism to read in time the call log from the
Alcatel-Lucent OmniPCX Office Communication Server.
The number of Open Telephony Server logs is limited to 200 in the Alcatel-Lucent
OmniPCX Office Communication Server. The "CALLLOG_UPDATE_TIMER"
parameter must be managed according to the number of users and traffic in order to
avoid any loss of logs.

2. Once you have verified that all fields contain the desired values, click OK to save the
values to the LCMA.conf configuration file and quit the "local call metering" application
configuration program.

3.2

"LCMA.conf" Configuration File


The LCMA.conf configuration file can be customized by editing specific fields. Fields that can
be edited include:

1-6

Alcatel-Lucent OmniPCX Office Communication Server parameters:


OXO_PASSWORD: Alcatel-Lucent OmniPCX Office Communication Server
administrator password.
OXO_LOG_LEVEL: Alcatel-Lucent OmniPCX Office Communication Server log level
(up to 4).
OXO_TIMEOUT: "Local call metering" application inactivity connection time limit (in
second) (default value: 30s).
OXO_IP_HOSTNAME: Alcatel-Lucent OmniPCX Office Communication Server host
name identifier (IP address or host name identifier).

Proxy parameters:
The "local call metering" application can connect to the Alcatel-Lucent OmniPCX Office
Communication Server via a proxy server.
PROXY_IP_HOST_NAME: Hostname or proxy server IP address.
PROXY_PORT_NUMBER: Proxy server port number.
PROXY_USER_NAME: User name used to login to the proxy server.
PROXY_USER_PASSWORD: User password.
LCMA_NETWORK_LOG_LEVEL: Log level (up to 4): network status trace level
between the "local Call Metering" application and the Alcatel-Lucent OmniPCX Office
Communication Server.

Metering parameters:
METERING_COLLECTOR_DIR: Tickets collector file directory name.
METERING_COLLECTOR_FILE: Tickets collector file name (by default:
TicketCollector (without extension)).
METERING_COLLECTOR_MAX_TICKET: Metering tickets maximum number stored
in the TicketCollector file (by default: 2000).

Call log parameters:


CALLLOG_UPDATE_TIMER: Duration to send read call log request to the

 
     
 



Alcatel-Lucent OmniPCX Office Communication Server.


CALLLOG_LOG_LEVEL: CALLLOG Log level (up to 4 levels).

Global parameters:
GLOBAL_LOG_FILE: Global Log file name (by default: LOG.txt).
GLOBAL_LOG_LEVEL: Global information trace level.
LOG_FILES_MAX_SIZE: Log file maximum size (in bytes) (by default: 1 000 000).

 
     
 

1-7

Chapter

1-8



 
     
 

You might also like