System Expert PDF

Alcatel OmniPCX Enterprise
PARTICIPANT'S GUIDE
System Expert
REF. ENTPTE403US
This document has no contractual value and may
be changed or withdrawn at any time by Alcatel Issue 01
This product includes software. Its use may be subject to legislation concerning computer technology,
databases and civil liberties (in case of France see the law N° 7817 dated 6 january1978).
Alcatel OmniPCX Enterprise R7.0 - Core
Technical Training offer
Learning Solutions Catalog 2006 All rights reserved © 2006, Alcatel

Legend
Page 2
represents training courses involved in ACSE certification

I=xh C=xd V=xd
Course name
COURSE REFERENCE
represents training courses involved in ACFE certification

I=xh C=xd V=xd
Course name
COURSE REFERENCE
I=xh C=xd V=xd
Course name
COURSE REFERENCE represents training courses involved in AQFP certification
represents training courses that are not involved in
I=xh C=xd V=xd
Course name
COURSE REFERENCE
certification program
I = x h stands for Individual learning, in hours

C = x d stands for Classroom learning, in days
V = x d stands for Virtual learning, in days

Alcatel OmniPCX Enterprise R7.0
Newcomers
Page 3
SYSTEM EXPERT:
•Software loading & update C=4d
•CPU Duplication
•Alarms System Expert
•Maintenance & troubleshooting I= 6 h C=3d
SYSTEM NETWORKING: ENTPTE403
•Network architecture CCD Basic
•Hybrid links OTCCTE451
•Centralized services I= 7 h C=5d C or V = 3 d
•VPN
EXTERNAL SERVICES: System Networking External Services
•ARS, DISA, DID translation
ENTPTE402 ENTPTE408 or ENTPWB408
•Multi-entity
SYSTEM CONFIGURATION:
•Advanced services configuration
•Voice guides
•IP Touch & IP Phones I=12 h C = 3 d V or C = 5 d
•Level 2 maintenance
•Remote Maintenance Access System Configuration
ENTPTE401 or ENTPWB401 C=2d
VOICE SERVICES:
•4645 enhanced services
•Conferences Voice Services
ENTPTE406
SYSTEM INSTALLATION:
• OmniPCX Enterprise architecture
I= 6 h C=2d I= 2 h IP TOUCH PHONE FACILITIES:
• Hardware installation and cabling
•Every day use of phone
• Users basic management System Installation IP Touch Phone Facilities facilities on Alcatel 8 & 9
• System working check
ENTPTE400 CLIEU76 series

Associated Solutions
Page 4
OMNIMESSAGE 4635 EXPERT: GET AUTONOMY

• System parameters
• FAX Server C=3d C=5d ACSE
• Automated attendant OmniMessage 4635
• OPS, Incidents, Traffic analysis 4635 Advanced OmniMessage 4635 Expert R5.x
OMNIMESSAGE 4635 ADVANCED: 4635TE310 4635TE312
• Software loading
• Mailbox configuration & languages
management
MOBILITY EXPERT:
C=2d
• Radio coverage tools ACSE DECT
Mobility Expert
• DECT Engineering rules
• Radio coverage test AP00TE085
STARTER & ACCOUNTING:
•4760 client and server setup in simplified
mode
I = 13 h C=5d
•Put the accounting into service ACSE Accounting
Starter & Accounting
•Carrier cost configuration & codebook
4760TE800
HOTEL / HEALTHCARE: RUN BUSINESS

• Guest and room management modes
• Accounting C=3d
• Hotel services
ACFE
• AHL Hotel / HealthCare Hotel / Healthcare
• Suites ENTPTE409
I= 12 h C = 3 d V or C = 5 d
System Configuration
ENTPTE401 or ENTPWB401
Prerequisite

V-Lab Offer
Page 5
v-Lab
Audience
Alcatel OmniPCX Enterprise •Media-Gateway setup Engineers in charge of the installation
Architecture V = 0.5 d •Signaling back-up configuration
ENTPTAVA02 •Software downloading & the maintenance of stand alone
solutions
v-Lab
Audience
Alcatel OmniPCX Enterprise •Audit/Broadcast configuration Engineers in charge of the design,
Networking V = 0.5 d setup
ENTPTAVA03 •VPN overflow management installation & the maintenance of
•Hybrid link over IP configuration complex network solutions

TAP-Lab offer
Page 6
c-Lab
•Networking Audience
Alcatel OmniPCX Enterprise •VPN Overflow
Engineers in charge of the design,
TAP-Lab R7.x C=3d •Hybrid links
ENTPTA0A05 •ARS, DID and NPD installation & the maintenance of
•Voice Guides complex solutions

Certification offer
Page 7
c-learning
MCQ (60 Questions)+ c-lab
ACSE Core R7.x C: 1 Day
ENTPTC0C8
MCQ
MCQ (30 Questions)
ACFE Core R7.x I: 45 Min
ENTPTC2C6
MCQ
MCQ (20 Questions)
AQFP Core R7.x I: 30 Min
ENTPTC1C6

Page 8
www.alcatel.com

System Expert
ACSE Core level
REFERENCE ENTPTE403US DELIVERY LANGUAGE English (course material in English)
DURATION METHOD
Virtual self-paced training on the computer
4 days Traditional classroom or practical sessions with tutorials (TAP LAB)
Tutored virtual training sessions accessible via an internet connection
MAXIMUM NUMBER OF PARTICIPANTS 12
PUBLIC
System Installers
Technicians and Engineers in charge of the configuration and the maintenance of an Alcatel OmniPCX Enterprise in
complex configurations
OBJECTIVES
At the end of the course, the participant will be able to:

• Load a software version on any kind of CPU
• Update a software version
• Configure system Alarms
• Configure a duplicated CPU configuration
• Ensure the 3rd level of maintenance using traces and scripts
PREREQUISITES
• To have attended Alcatel OmniPCX Enterprise System Networking training course (Ref.: ENTPTE402US)
System Expert
ACSE Core level
PROGRAM DESCRIPTION
Describe the principles of the software loading

Load a full software version on any type of CPU in mono-version mode
Load a full software version on any type of CPU in multi-version mode
Update a software version via static and dynamic patches
Describe the principles of the CPU duplication
Configure a CPU duplicated configuration
Perform the database cloning
Describe and configure the speed dialing by range
Describe and configure the alarm retrievals
• Alarm sets
• External alarms
• CPU alarms
• RMA alarms
Describe, configure and maintain the Media Gateway signaling back-up feature
Describe the principles and parameters of traces
Launch traces on any kind of applications and services
Describe and create simple scripts
Describe software locks details
Describe the Kernel debugger
Retrieve the Crashdump files
Describe and activate the aging password service
Describe the principles of schedulable patch loading from Alcatel OmniVista 4760
Alcatel University Alcatel OmniPCX Enterprise
System Expert TOC.doc
DOCUMENTATION CHANGES
ISSUE DATE ISSUE DATE
01 03/06
Alcatel OmniPCX Enterprise System Expert
File reference: ENTPTE403US
GENERAL SUMMARY
CORE CURRICULUM AND CATALOG PROGRAM DESCRIPTION
1. CS Software loading
ENTP0442P02TEUS.................................................................................................................5
ENTP0442C01TEUS ..............................................................................................................45
ENTP0442C02TEUS ..............................................................................................................51
ENTP0442C03TEUS ..............................................................................................................55
ENTP0442H02TEUS ..............................................................................................................63
2. Multi-Version loading
ENTP0442P03TEUS...............................................................................................................67
ENTP0442C04TEUS ..............................................................................................................77
ENTP0442C05TEUS ..............................................................................................................87
ENTP0442H03TEUS ..............................................................................................................95
3. Schedulable patch downloading from OmniVista 4760

ENTP0442P04TEUS...............................................................................................................99
4. e-CS Duplication
ENTP0438P01TEUS.............................................................................................................105
ENTP0438C02TEUS ............................................................................................................121
ENTP0438C04TEUS ............................................................................................................125
ENTP0438C05TEUS ............................................................................................................129
ENTP0438C06TEUS ............................................................................................................135
ENTP0438H01TEUS ............................................................................................................141
Issue 01 REF. ENTPTE403US 0.1

© Copyright Alcatel Business Systems 2006
Transmission or copying of this document is not permitted without prior written authorization.
The wording "Document Alcatel Business Systems" must appear on all authorized reproduction.
1
Alcatel OmniPCX Enterprise Alcatel University
TOC.doc System Expert
5. Speed Dialing by range

ENTP0408P02TEUS.............................................................................................................145
ENTP0408C03TEUS ............................................................................................................151
ENTP0408H02TEUS ............................................................................................................157
6. Alarms Retrieval
ENTP0422P01TEUS.............................................................................................................161
ENTP0422C01TEUS ............................................................................................................167
ENTP0422C02TEUS ............................................................................................................169
ENTP0422H01TEUS ............................................................................................................173
7. IP Media Gateway Signaling Backup

ENTP0467P01TEUS.............................................................................................................177
ENTP0467C01TEUS ............................................................................................................199
ENTP0467M01TEUS............................................................................................................209
ENTP0467H01TEUS ............................................................................................................219
8. Traces
ENTP0533P01TEUS.............................................................................................................223
ENTP0533P02TEUS.............................................................................................................239
ENTP0533M01TEUS............................................................................................................247
ENTP0533H01TEUS ............................................................................................................263
9. Creation of simple scripts

ENTP0542P01TEUS.............................................................................................................267
ENTP0542H01TEUS ............................................................................................................287
ENTP0542A01TEUS ............................................................................................................289
10. Software locks

ENTP0412P12TEUS.............................................................................................................297
11. Kernel Debugger & Crash dump

ENTP0543P01TEUS.............................................................................................................323
ENTP0543H01TEUS ............................................................................................................333
ENTP0543A01TEUS ............................................................................................................335
12. Security: Aging Passwords

ENTP0531P01TEUS.............................................................................................................347
ENTP0531C01TEUS ............................................................................................................351
ENTP0531H01TEUS ............................................................................................................355
0.2 REF. ENTPTE403US Issue 01

2
System Expert TOC.doc
FEEDBACK SHEET
In order to improve the quality of the documentation, please report any errors found by returning
this sheet to the address below.
SECTION CHAPTER PAGE DESCRIPTION OF THE ERROR
Alcatel University
8 Rue de Kervézennec
CS 82802
29228 BREST CEDEX 2 - FRANCE
FAX: (33) 2 98 14 36 36
Please return this sheet to:
DATE:
Issue 01 REF. ENTPTE403US 0.3

3
TOC.doc System Expert
0.4 REF. ENTPTE403US Issue 01

4
CS software loading

Transmission or copying of this document is not permitted without prior written authorization. 1
OBJECTIVES:
◆ To describe the OmniPCX Enterprise loading tool PC Installer
◆ To describe the software loading principles
◆ To describe the different loading cases
◆ To describe the procedure depending on the type of CPU
◆ To describe a complete software loading procedure
◆ To describe a version updating with a patch
Alcatel OmniPCX Enterprise – CS software loading

Ref. ENTP0442P02TEUS Issue 01
5
CS software loading
Table of contents
Loading tool OmniPCX Enterprise PC Installer
Software loading generalities
Loading tool interface
Complete release loading (Linux +call handling)
➨ Principles
➨ IPRS CPU type (Alize type)
➨ 4400 CPU type (IPCS)
➨ Appliance server type (IPAS)
➨ Common part to all type the CPUs
Release or patch loading


6
CS software loading
PC Installer - Loading tool
The OmniPCX Enterprise PC Installer ensures:
➨ The loading of all software type
▼ Linux operating system
▼ Telephone software
▼ Correcting patch (for Linux and/or telephone)
▼ Specific soft for GA / GD
➨ The loading of all CPU type
▼ IP Rack Server => CPU-CS
▼ IP Appliance Server => IBM server
▼ IP Crystal Server => CPU5 / CPU6 / CPU7


7
CS software loading
Compatible with Windows 98 SE, NT4 SP6, 2000 and XP
Uses Unix environment and PERL scripts
➨ The application is independent from the operating system
▼ cygwin provides a Unix environment that allows the loading tool to

use the des DHCP/TFTP and FTP servers
▼ PERL is a programming language handled by several OS
The user must be logged as «Local Administrator» to get

the rights to install the software on the PC
PC installer software is delivered in each OmniPCX

Enterprise release

Cygwin: Linux environment into Windows Microsoft system. It is made up of a DLL (cygwin1.dll) and a set of tools to recover the main
Linux functions into windows.
This environment is under GPL license(General Public License).This license allow the users to take the source file in condition that if
modifications are made into the source files the modified soft must be distributed to public.
The purpose of Cygwin environment is to implement DHCP, TFTP and FTP servers in systems that originally don’t provide such files
(Windows 98, NT4 Workstation, 2000 Pro and XP Pro or Home for example).
PERL: Practical Extension and Report Language

Programming language based on scripts (These scripts are interpreted when the system is executing them).
A PERL interpreter exists in every Operating System .
The PC Installer install file (called Setup.exe) is located in /Dhs3mgr/versionname/pcmao/boot_res/pcinstall.

8
CS software loading
Tool software architecture
Main Perl Script Bootnet2.pl
Perl interpreter Wperl.exe
CYGWIN.DLL
Unix emulation providing
DHCP, TFTP and FTP servers
DHCP TFTP FTP Call
Server
Windows sytem
W98, NT4, W2k et XP
PC is connected to CS by IP
Company LAN
or direct cable

The FTP login is done with anonymous login

9
CS software loading
Generalities
The software loading is done over IP
➨ Depending on the type of loading, IP connection can be

direct to the PC or via the company’s LAN
➨ In some cases a V24 link is necessary
Call
Server
V24 link
Ethernet link

A V24link can be used to set up the loading parameters (9600 8N1)

For a complete loading (Linux + telephonic version (call handling)+ patch), it is recommended to have a direct Ethernet link
between CS and PC server

10
CS software loading
Generalities
Main element of software release:
➨ A release is made up of:
▼ A Linux OS release
▼ A release of « facilities » (swinst)
▼ A release of the telephone binaries
▼ A static patch (optional)
▼ A dynamic patch (optional)
➨ Naming of a software release

F2.500.6i
i: Dynamic patch
F: Product line
identification
2: Option in the line 500:Soft version # 6: Static patch #

The Linux software is located in the directory /DHS3mgr/« Version name »/pcmao/bootp/linux/« N° version »
swinst environment is located in /DHS3mgr/« Version name »/pkglinux/facil
The telephone application (call handling) is located in /DHS3mgr/« Version name »/
The static patch is located in /DHS3mgr/« Patch name »/
The dynamic patch is located in/DHS3mgr/« Dynamic patch name »/
The F2.500.6i release name stands for:

•Product line: F (OmniPCX Enterprise Release 5x)
•Option in product line: 2 (Release 6.1 Lx)
•Software release: 500 (Basic telephonic application version without patch)
•Static patch: 6 (correcting patch to be installed with telephone application stopped)
•Dynamic patch: i (it is the dynamic correcting patch index to be installed on patch2 , the telephone application doesn’t have to
be stopped)
This release is split in 3 directories in DHS3mgr:

•The directory f2500 contains the version f2500
•The directory f25006 contains the static patch 6 of version f2500
•The directory f25006i contains the dynamic patch i to install on patch 6 of version f2500

11
CS software loading
Generalities
Different types of loading
➨ Call Handling or Patch

▼ Complete version or
patch installation
➨ Linux on inactive partition

▼ Linux Installation in the
second disk part
➨ Linux + Call Handling

▼ Automatic complete loading
➨ GD/GA Binary
▼ To reload GD or GA binaries

Depending on the type of installation, the PC installer will start the following servers:
Telephonic application or Patch
FTP server
Linux on inactive partition
FTP server
Linux + Call handling
GD/GA binaries

12
CS software loading
Generalities
Different types of Call Server
➨ IP Rack Server CPU-CS

▼ Bootp request at starting up
▼ V24 optional for a complete loading
▼ Named Alize in the interface
➨ IP Crystal Server CPU 5/6/7

▼ bootp request at starting up
▼ V24 mandatory for a complete loading
▼ Named A4400 in the interface
➨ IP Appliance Server Server IBM

▼ PXE request at starting up
▼ V24 optional for a complete loading
▼ Named Appliance Server in the
interface

Depending on Call Server type , the starting up request for a complete loading (Linux + Telephone) varies:
BOOTP protocol for the CPU-CS and the CPU 5/6
PXE protocol for the CPU-AS
BOOTP: Bootstrap Protocol

Old protocol used to start a system without any basic configuration.
PXE: Pre-Boot eXecution Environment
Developed by Intel . Now it is a standard.
Those 2 protocols allow to start a system without configuration (no hard drive for example).
They are used to download IP parameters from server and after the Operating system.
Depending on the needs the operating system will be installed on hard drive or in memory.

13
CS software loading
Generalities
Call server automatic loading:
➨ 2 cases:
▼ The CS hard disk is empty
✦ Automatic start up in «Standard Installation » mode for Alize Call server

(IPRS) and IPAS (Appliance Server)
✦ Manual start up on IPCS (CPU 5/6/7)

V24 link mandatory
▼ The CPU disk is already loaded
✦ Manual starting up on IPCS, IPRS et IPAS

V24 mandatory for IPCS and IPRS
Screen/keyboard mandatory for IPAS
✦ Hard drive invalidation to force automatic start up

For the IPRS and IPAS

For CPU-CS (IPRS, called Alize in the loading tool interface), the bios release is at least:8.17.
This BIOS release allows to start manually the CS (via console port) without disabling the hard disk .

14
CS software loading
Generalities
CPU’s starting up phases
➨ Bios starting up Possible interruption
▼ System auto-test
➨ Bootloader starting up Possible invalidation
▼ GRUB loader starting up
➨ Linux starting up Possible invalidation
▼ Linux starting up on hard disk active partition .
➨ Telephonic application starting up
▼ Automatic starting up if autostart is set in swinst
▼ Manual starting up under mtcl with command RUNTEL

Depending on CPU type, the bios access procedure varies:

For an Appliance Server, it is essential to plug a screen and a keyboard on the server (press F1 key while booting).
For the CPU-CS and the CPU 5/6/7, access to the bios can be only done by V24.
GRUB: (GRand Unified Bootloader) is the boot loader used by the OXE.
It allows the system to start on hard drive (on a specific partition if necessary) or from the network.
It is possible to use a small shell directly under GRUB control.

15
CS software loading
Main interface

menus:
Commands:
To leave the application
Preferences:
•To select the language
•To select the disk (where is located the OXE release to be downloaded)
This release must be in /DHS3mgr folder (it can be on the CD-Rom).
Tools:
To consult the different loading log files and DHCP server configuration.
Installation type:
Allow to select the application working mode
Call handling or Patch
installation of a telephone binaries or patch on CS (Linux + telephone)
Linux on inactive partition
Linux installation on the second hard disk partition .This Linux part can be used in case of software upgrading.
Linux + Call handling
Linux software and telephone application complete installation
GD/GA binaries
GD or GA software downloading .

16
CS software loading
Loading configuration
Choice of DHCP server mode

Depending on CPU type
List of versions
in /DHS3mgr
List of countries
Auto/manual installation
or disk maintenance
If company network, you must

write the MAC Address
in the field at the bottom
List of ethernet boards found in your system

Call server type:

Alize: BOOTP and startup.txt file
A4400: BOOTP and no configuration file
For this type, the next 3 steps are disabled
Appliance Server: PXE and pxeloader file
Call handling version:
List of releases present in:/DHS3mgr on the selected drive drive in Configuration menu
Country:
The country list is built up from the selected version
Installation type:
Standard: for an automatic loading
Linux reloading: Linux reloading without disk formatting nor telephone application replacement
Linux into memory: loading Linux into memory for further maintenance operations
Network type:
Direct cable: the server replies to all DHCP requests.
Customer network: the server only replies to requests coming from the Call Server.The CS MAC address must be entered in
the field Ethernet address of the window.
Network interface:
Select the Ethernet interface in the list built for the PC.
IP address:
By default the system does + 1 to the default address.But it is possible to change the address to be used.
Address Ethernet:
Unused in direct cable, to be entered with MAC address in client network mode
Validate:
Starts up the different servers (temporized stop in case of non receip of CS requests)
Modify:
Stops the server and comes back into configuration mode of the application.

17
CS software loading
Information windows during loading
Complete
release
loading
MAC address of client BOOTP/DHCP
IP address given by DHCP server FTP client IP address
Hostname given by DHCP
Directory used for loading Directory used for loading
File name being transferred File name asked to the the server
Update of a version or patch
Downloading progress window

The color shows the server used

In case of a complete release loading, the progressing window at the bottom shows the files percentage (or replies percentage) sent
to the call server depending on the used server (DHCP, TFTP, FTP and FTP data).
In case of patch loading, the progression is visible under swinst.

18
CS software loading
Complete release loading - Principles
Principles of automatic software loading
BOOTP request or DHCP (PXE)
config IP and boot file name delivery
Files list downloading
Files transfer (including Linux RAM)
DHCP request
Call IP setting up delivery
Server
Automated installation of linux via FTP
Files transfer (linux, tools and swinst)
Version and patches downloading
Requested files delivery
End of installation , call server reboot
Ethernet link

Depending on the call server type, the initial request can be BOOTP (IPRS and IPCS) or DHCP (IPAS).
The server delivers the necessary IP configuration to continue and a file containing a list of files to be downloaded with TFTP
IPRS: startup.txt
IPAS: pxeloader
IPCS: none (the file name containing the Linux RAM is known from the CPU)
The call server downloads with TFTP the whole files enumerated in the boot file (or already known in case of CPU 5/6)
Once Linux RAM is downloaded , this one is copied into memory.The system really starts up under Linux in an automatic procedure.
•Complete IP configuration request to the PC server via DHCP
•Hard drive formatting and system files creation
•Complete kernel and essential packages downloading
•Swinst downloading and starting up
•As no telephonic application is present, swinst immediately starts the automatic installation procedure
•Downloading of release and patches files pointed in PC Installer or during the boot of CPU 5/67
•Creation of a default IP configuration (10.253.253.1) for the CPU
•Reboot of the system
Installation is finished

19
CS software loading
Complete release loading - Principles
Loading tool configuration
Select CPU type (Alize/A4400/Appliance server)
Select the complete version to be installed

(Version + Static patch + Dynamic patch)
Select the country (here us for United-States)
Select Standard
Select connection type
Change the network board (if necessary)
Modify the IP address given to the e-CS (if necessary)
Enter CPU MAC address (Company network mode)
Validate to start the servers

If the call handling releases are not visible in the list it means that there is no DHS3mgr directory or no release on the pointed drive.
The name of the directory must not contain special character (For instance f2.5006.i must be renamed into f25006i).
• In Call Server type, select the type of IP Server to load (Alize, A4400 or Appliance Server).
• If A4400 type is selected, the Call handling version, Country and Installation type are disabled
• In Call handling version, select version or patch (It is possible to automatically install version , static and dynamic patch)
• In Country, select the country for installation
• In Installation type, select Standard
• In Network type, select direct or company network
• In Network interface, select the Ethernet interface to be used
• In IP address , it is possible to change the customer IP address (default PC IP address + 1).
• In Ethernet address, enter CPU MAC address only if the selected network is Company network
A DHCP server is activated for a release installation (when the window “installation parameters » is validated) and stopped every time
parameters are modified in the window or when this window is closed.
Closing the OmniPCX Enterprise PC Installer interface stops the 3 servers: TFTP, FTP et DHCP.
DHCP stops automatically after a timer if any request.
To start it again without modifications , you can click on Return button and after on Apply button .

20
CS software loading
Complete release loading - CPU type Alize (IPRS)
Different cases of starting up
➨ Hard drive is empty
▼ The loading begins automatically
➨ Release already installed, the hard drive can be disabled
▼ If Linux is started, log with root account and type:

grubboot ETHER then reboot the call server
▼ Otherwise, interrupt the system in GRUB with c and type:

Press enter to boot the default OS [0], 'c' for a command-line,
or give an another entry number
grubboot ETHER then reboot
▼ At the reboot, the system recovers the case of an empty disk

ON
The« DIL switches » on the CPU-CS must be configured to value 1
OFF
1234
The command grubboot ETHER forbids the system to start from the disk by disabling the disk for the GRUB.
While rebooting , as the disk is considered unavailable , the system starts automatically a loading procedure from the IP network.
The disk data are useless after having typed grubboot ETHER command.
(In case of error,please refers to technical communication TC0536 customer’s data recover on faulty or disabled disk)

21
CS software loading
Complete release loading - CPU type Alize (IPRS))
Different cases of starting up (continued)
➨ Force boot on network in the bios
#Alize BIOS Monitor

*** BIOS Version 3EH30227DRAA bios100/008.017 ***
*** Generated on Jun/13/2003 at 09:25 ***
....................... Hardware autotest .......................
value of DIL switch 01
YOU CAN strike Ctrl B to enter in BIOS monitor during several seconds from NOW
!
Ctrl B
hit [Ctrl I] for BIOS monitor! Ctrl I
Password?:

For the CPU-CS (IPRS, called Alize in the loading tool), the bios must be at a minimum version of 8.17 to allow a manual starting up
via the port console without having to disable the hard drive.
The delay at YOU CAN strike Ctrl B to enter in BIOS monitor is very short.
Since bios 8.17, an empty password (type return) allow to access a small menu to start the CPU on Ethernet.

22
CS software loading
Different cases of starting up (continued)
➨ Force boot on network in the bios
Alize BIOS Monitor

*** BIOS Version 3EH30227DRAA bios100/008.017 ***
*** Generated on Jun/13/2003 at 09:25 ***
Monitor Light Menu

01 - Load From Hdisk #0
02 - Load From Ethernet Starting up on network (BOOTP)
03 - Load From Flash NAND program
04 - Load From Flash NAND program and Bootp
05 - Load From Hdisk #0 and Bootp
06 - Display MAC address Useful in « company network »mode
07 - Display PCMS id
08 - Display System informations
09 - Full Options menu Password protected access (reserved R&D)
10 - Reset System

For the CPU-CS (IPRS, called Alize in the loading tool), the bios must be at a minimum version of 8.17 to allow a manual starting up
via the port console without having to disable the hard drive.

23
CS software loading
CPU starting up on the network
➨ BOOTP request to obtain IP settings
▼ The PC server replies and send information and file name to be

downloaded (startup.txt)
➨ Download with TFTP of startup.txt
▼ It contains the name , the size and type of files to download
➨ Downloading of files vmlinux.bin and initrd.img
➨ Starting a minimum linux provided by initrd.img
➨ DHCP request to obtain a full IP configuration
➨ Launching of the automatic installation procedure

Example of startup.txt file:
/bootp/linux/18.0_18.1/alize/vmlinux.bin;1267568;BIN;1048576;1048576
/bootp/linux/18.0_18.1/alize/initrd.img;3855709;RAMDISK;4194304;0
ramdisk_size=3855709,root=/dev/ramdisk,console=ttyS0,panic=5;60;CL;0;0
boot;0;BOOT;0;1048576
This file shows the path to the files used for loading, the file type , its size and the position in memory .
vmlinux.bin:
binaries of a minimum Linux allowing to start the installation procedure on the hard drive.
initrd.img:
Ensures the creation of a virtual disk in RAM to charge a minimum Linux in memory and start the system.
The RamDisk is setup to start an automated Linux installation procedure via FTP.

24
CS software loading
Complete release loading - CPU of type 4400 (IPCS)
*** BIOS Version 3BA_24095_AAAB_02 ***

*** Generated on col000018455 on May/13/2003 at 14:45 ***
*** CPU6 Step 2 version 3BA 23197: 0.1 ***
*** ELAN SC520 @ 100MHz ***
...........
> System Times
CLK Time: Sun Feb 15 06:16:28 2004
----- Auto Boot in 5 s -----

System starting up can be interrupted by hitting the return key within 5seconds.
In case of CPU7, use Ctrl-B / Ctrl-I to interrupt the boot (same as CPU-CS).

25
CS software loading
CPU starting up on the network (continued)
Monitor Main Menu:
1 - Display Test Results

2 - Flash Programming
3 - Boot 3
4 - CMOS Management
5 - Data & Time
6 - Trap Test
7 - NMI Test
8 - FPU Test
9 - Command Interpreter
10 - Exit application
CPU6 A> 3


26
CS software loading
Boot Menu:
1 - Booting From Floppy #0

2 - Booting From Floppy #1
3 - Booting From Hard Disk #0
4 - Booting From Hard Disk #1
5 - Booting From Ethernet Network 5
6 - Default Boot Sequence
CPU6 A> 5
The boot on network differs from CPU-CS to remain

compatible with the OmniPCX Enterprise versions loading
procedure

A CPU 5/6/7 board can be loaded with Chorus (OmniPCX 4400) or Linux (OmniPCX Enterprise).
So the loading procedure is very similar to the one used for 4400 loading.

27
CS software loading
ACT4400 specific INSTALLATION data input:

=========================================
Standard installation (y/n, default is y)?:
TEL version ?: f25006i.us
Phase 1: address determination and bootfile selection

=====================================================
NB: All parameters below are optionnal.
Default internet Address: *** Unknown ***

New Internet Address:
Name of default BOOTP/TFTP server: *** Unknown ***

Name of a new BOOTP/TFTP server:
Default loaded file:

New loaded file: %33.0
BOOTP request in progress ..............

Standard installation (y/n, default is y)?

The standard installation corresponds to Linux installation , formatting and version and patches installation (as for CPU-CS).
TEL version?
The name to be entered must be like: Version name.country
Here the version is f25006i and the country is USA (us)
New Internet Address and Name of a new BOOTP/TFTP server:

It is possible to define the IP address and the name of the BOOTP server for a company network installation.
Type « return » to ignore.
New loaded file:

It is the name of the folder containing the linux.ram file to be loaded.
The character « % » must be put in front of the name to make a difference with a chorus.ram file loading (OmniPCX 4400).
The folder is located in /DHS3mgr/« Release »/pcmao/boot_res/linux/

28
CS software loading - Complete release loading
CPU of type 4400 (IPCS)
➨ BOOTP requests to obtain the IP configuration
▼ The PC server replies and send the information and the file
name to be downloaded (linux.ram)
➨ Downloading with TFTP of linux.ram
➨ Starting up of Linux minimum provided by linux.ram
➨ DHCP request to obtain the full IP configuration
➨ Launching of the automated installation procedure

linux.ram:
Minimum Linux kernel that allows the TCP network configuration and that contains the main installation utilities.
It is configured for starting an automated installation via ftp.

29
CPU type Appliance Server (IPAS)
Different cases of starting up
➨ The hard disk is empty
▼ The complete release loading starts automatically
➨ Release is already installed, the disk can be disabled
▼ If Linux is started, log with root account and type:

grubboot ETHER then reboot the call server
▼ Otherwise, interrupt the system in GRUB with c and type:

Press enter to boot the default OS [0], 'c' for a command-line,
or give an another entry number
grubboot ETHER then reboot
▼ At the reboot, the system recovers the case of an empty disk

The command grubboot ETHER forbids the system to start from the disk by disabling the disk for GRUB.
While rebooting , as the disk is considered unavailable , the system starts automatically a loading procedure from the IP network.
The disk data are useless after having typed grubboot ETHER command.
(In case of error,please refers to the technical communication TC0536 customer’s data recover on faulty or disabled disk)

30
Different starting up cases (continued)
➨ Force the boot on the network in the bios
▼ Connect a screen and a keyboard on the Appliance Server
▼ Connect the network on ETH1port
▼ Interrupt the server starting up by pushing F1
▼ Force starting up on boot PXE
✦ Depending on the bios version, les menus can vary
✦ In case of change in server starting up order, do not forget to reconfigure

it in a proper way after !


31
➨ PXE request to obtain IP configuration
▼ The PC server replies and send information and the name of the file
to download (pxeloader)
➨ Downloading with TFTP of pxeloader file
▼ The server switches inputs/outputs on the V24 port
➨ Downloading of linux.ram
➨ Starting up of the minimum Linux provided by linux.ram
➨ DHCP to obtain the full IP configuration
➨ Launching of the automatic installation procedure

linux.ram:
Minimum Linux kernel that allows the TCP network configuration and that contains the main installation utilities.
It is configured for starting an automated installation via ftp.

32
Common part to all CPUs
Once the Linux kernel is in memory, the Linux

installation on the disk begins
➨ Loading with FTP with account anonymous
Welcome to Alcatel e-Mediate installation
+-----------------------------+ Loading +-----------------------------------+

| |
| Loading second stage ramdisk... |
| |
+---------------------------------------------------------------------------+
<Tab>/<Alt-Tab> between elements | <Space> selects | <F12> next screen
➨ Automatic installation of the swinst package


33
Automated version installation by swinst
➨ Creation of the accounts and the directories
*** Creation of user mtcl

*** Creation of user adfexc
*** Creation of the missing main directories
*** Creation of the missing swinst directories
A daily backup will be executed on cpu disk

at 5 hour 45 min
WARNING: no delivery has been installed
The path of the delivery is /dhs3mgr/f2500
The previous version will be erased before the new installation

to avoid for some old files to remain on your CPU.
end of remove procedure

swinst allows the installation of release and patch .

It executes:
• The users accounts creation
• The necessary tree diagram creation for a good working of the telephonic application
• The configuration of an automatic database backup on the disk
• The release installation
• The patches installation
• The Linux updating upgrades are included in the patches
• A default IP configuration IP
• The system reboot

34
Automatic release installation with swinst
➨ Call handling (Telephonic application) binaries
….
DHS3bin/oneshot/mtcl/getpilconf_test
DHS3bin/oneshot/mtcl/qconf
DHS3bin/oneshot/mtcl/btracer.config
DHS3bin/oneshot/mtcl/trcterm
DHS3bin/oneshot/mtcl/debug_csta
DHS3bin/oneshot/mtcl/getpilconf
DHS3bin/oneshot/mtcl/getpilconf_sun
DHS3bin/oneshot/mtcl/pilot
DHS3bin/oneshot/mtcl/pilot_sun
DHS3bin/oneshot/mtcl/pilot2
DHS3bin/oneshot/mtcl/pilot2_sun
DHS3bin/oneshot/mtcl/pilot2a
DHS3bin/oneshot/mtcl/pilot2a_sun
DHS3bin/oneshot/mtcl/lis
DHS3bin/oneshot/mtcl/lisX25
DHS3bin/oneshot/mtcl/trt2
….


35
Automatic release installation with swinst
➨ End of binaries loading
(c) Alcatel e-Mediate / Linux (C) 1999 Red Hat Software
+----------+ Reboot +----------+

| |
| |
| Do you want reboot the CPU |
| +-----+ +----+ |
| | Yes | | No | |
| +-----+ +----+ |
| |
+------------------------------+
<Tab>/<Alt-Tab> between elements | <Space> selects | <F12> next screen
➨ If no action from the operator, the reboot is automatic


36
Set up IP configuration
➨ use netadmin
Restore customer database or create an empty database
➨ use swinst
Install licenses files in /usr4/BACKUP/OPS

➨ transfer the files with FTP or 4760i
➨ install with swinst utility
Reboot the system

➨ command shutdown –r now


37
CS software loading
Release or Patch loading - Principles
Release or Patch loading
Loading configuration in swinst
Call Files request (version/patch) via FTP
Server
Files transfer (common part)
Files transfer (depending on the country)
End of version or patch loading

V24 link
Ethernet link

The software version or patch manual loading is done via swinst.

Connection to the system for the control can be by V24 or via Telnet.
Several cases:
Complete version loading(the previous version will be deleted except in « multi-partitions »)
A version does not have a correcting patch
Static patch loading
This kind of patch contains correcting files that requires the call handling (telephonic application) to be stopped before
loading.
Dynamic patch loading
This kind of patch contains correcting files that does not need the stopping of the telephonic application.
For a version or a patch, the loading is done in 2 steps (maximum)

step 1: the files common to all OmniPCX Enterprise installations.
step 2: the files specific to the country

38
CS software loading
Software release replacement is possible via

swinst menus
➨ Previous version will be automatically deleted
➨ The call handling (telephone) must be stopped
Version updating with patch is done the same way

➨ Depending on the patch, telephone must stop or not
▼ Static patch: the system must stop
▼ Dynamic patch: stopping the system is not necessary

A manual version updating allows to keep intact customer’s data .

The version deletion does not affect the customer’s data , the tickets or the voice guides.
On the other end, a standard installation formats the disk. So it is necessary to save the database before.
It is also possible to load a software version on the second part of the disk.
This method offers the maximum security because the 2 versions are completely independent.

39
CS software loading
Setting up loading tool
Select the drive where is located

the version to be installed

The FTP server is activated for a version or patch installation.

Closing the OmniPCX Enterprise PC Installer application stops the FTP server.
Just indicate in Preferences the drive where is located the version or patch to install.
It is possible to enter directly the name of the drive in swinst.

40
CS software loading
Release or Patch loading - Configuration in swinst
Patch loading with swinst
ALCATEL BUSINESS SYSTEMS

FACILITIES Expert menu Installation FACILITIES 2.18.0
1 Packages installation
2 Deliveries installation 2
3 Cloning & duplicate operations
4 Backup & restore operations
5 OPS configuration
6 System management
7 Database tools
8 Software identity display
9 Remote download
Q Go back to previous menu
Your choice [1..9, Q]? 2
This menu allows to install a new version or a patch (static

or dynamic)

Expert menu is accessible by selecting 2 in the main menu of swinst.

41
CS software loading
Release or Patch loading - Configuration in swinst
Patch loading with swinst (continued)
ALCATEL BUSINESS SYSTEMS

Delivery menu Installation FACILITIES 2.18.0
1 Install delivery from server 1

2 About last install deliveries operations
Your choice [1..2, Q]? 1
Enter the name of the server -> 10.253.253.10
The installation of the binaries will modify the current installed version
Please, confirm the installation of a new version (y/n, default y):
Enter the full path of the delivery on the server
example for Unix server: /twdhs3/dhs3ref/dhs3ref_d2/E2.403/LIVRAISON

for Windows server: /dhs3mgr/E2403
-> /dhs3mgr/f25006k
Confirm the full path /dhs3mgr/f25006k (y/n, default y):
The path of the delivery is /dhs3mgr/f25006k

Enter the name of the server:

It is possible to indicate a name (if it is declared in /etc/hosts file with netadmin) or an IP address.
The server name or address are kept in memory for the next loading.
Enter the full path of the delivery on the server:

Enter the path to access the telephonic application (call handling) binaries or patch.
This path can refer to a drive letter to bypass the PC Installer tool configuration
In Windows environment the case is not important (case of PC Installer).

42
CS software loading
Version or Patch loading - Configuration in swinst
Patch loading with swinst (continued)
Do you wish to secure the installation (y/n): n

Transfer for pkg part in preparation
facil/swinst-2.18.0-4alc.i386.rpm
End of remote copy for pkg part files
LINUX 33.0 is already installed

*** Creation of the missing swinst directories
Transfer for comm part in preparation

Remote copy for comm part files is in progress ...
DHS3bin/descript/dyn_id
DHS3bin/descript/dynlinux.list
.......... Files downloading ..........
etc/pam.d/gcsconfig
End of remote copy for comm part files
Setting permissions on files ...
End of post installation

End of operation!
Press return

Do you wish to secure the installation (y/n):

It is possible to create a backup of all the files contained in a patch before they are being replaced.
At the end of installation swinst proposes to delete the backup or to keep it. By keeping it , it will be possible to come later back to
the previous patch in case of dysfunction of the new one (new entry in swinst menu in this case).
At any time it is possible to verify the loadings done by swinst by consulting About last install deliveries operations.

43

44
4400 CPU Type loading (IPCS)
PROCEDURE
OBJECTIVE
- To learn how to load a full release on a 4400 CPU Type (IPCS)
REFERENCES
- Technical Communication TC0631
- System Documentation CD-ROM: R6.x Custom System Documentation/Technical
Documentation/System/Call Server
OVERVIEW
Standard installation of a 4400 CPU Type consists in automatically loading a basic version (basic
release) or basic version + static patch or basic version + static patch + dynamic patch to the Call
Server hard drive. Standard installation is performed in several steps:
1. Create a directory on the PC server called dhs3mgr.this directory will contain a basic version,
a static patch and dynamic patch Ex:
1. The Call Server must perform a network boot on the installation server PC on which the
ENTERPRISE PC INSTALLER application is running.
2. The installation server PC provides the Call Server with an IP address via DHCP.
3. The installation server PC provides the "linux.ram".
4. The installation server PC provides the Linux OS, swinst packages, and telephone application
binaries via FTP.
5. The Call Server restarts automatically when installation is complete.
Issue 01 REF. ENTP0442C01TEUS.doc C.1

45
PROCEDURE
1. PC Installer configuration
To install the PC Installer, Run the executable file in the following directory. For more
explications consult the technical communication TC0631.
1.1 Drive selection

PC Installer
Path Preferences/Drive
Parameters D: (example, choose the drive where the release is)
The folder name where the release is must be dhs3mgr
1.2 Full installation selection

PC Installer
Path Installation type
Parameters Linux + Call handling
Note: After the installation type selection, a new window is opened
C.2 REF. ENTP0442C01TEUS.doc Issue 01

46
1.3 Call server type selection

PC Installer (second window)
Path Call Server type
Parameters A4400
Call Handling version, country code and installation type will be attributed later in the lab.
1.4 Connection type selection
Path Network type
Parameters Direct cable
It is better to use a direct connection with the CPU to load it.
In case of connection through the company network, the Ethernet address (MAC address) of
the CPU must be set in the Ethernet address field.
1.5 PC Installer parameters validation

Action Click on Apply button

47
2. CPU Reset and boot on Ethernet
2.1 Restart the CPU

On CPU using terminal
Path mtcl
Parameters Shutdown –r now
2.2 Enter in the bios menu

Path When displaying the message: « Auto Boot in 5 s »
Action Return
2.3 In the bios menu, choose “boot” option

Path Monitor Main Menu
Parameters 3 - Boot
2.4 Select “Boot on Ethernet”

Path Boot Menu:
Parameters 5 - Booting From Ethernet Network

48
2.5 Answer to the questions

Parameters ACT4400 specific INSTALLATION data input:
=========================================
Standard installation (y/n, default is y) ?:y
Phase 1: address determination and boot file selection
=========================================
NB: All parameters below are optional.
Default internet Address: *** Unknown ***
New Internet Address:
Name of default BOOTP/TFTP server: *** Unknown ***
Name of a new BOOTP/TFTP server:
Default loaded file:
Language (e.g. for U.S. )
Full release (patch included)

Verify the folder in
dhs3mgr/release name (example: f2500)
Tape % for linux /pcmao/boot_res/bootp/linux
Note: At the end of loading, the CPU restarts automatically. ” PC Installer” windows can be then
closed. Now, the following actions must be done on the CPU:
CPU IP configuration using “netadmin” command
Data base restoration or empty data base creation
Soft licenses files restoration

49

50
Software version loading on IPRS
PROCEDURE
OBJECTIVE
- To learn how to load a full release on a IPRS (Alize type)
REFERENCE
- Technical communication TC0631
- System Documentation CD: R6.x Custom System Documentation/Technical
OVERVIEW
Standard installation of a IPRS Call server (Alize type) consists in automatically loading a basic
version (basic release) or basic version + static patch or basic version + static patch + dynamic
patch to the Call Server hard drive. Standard installation is performed in several steps:
a) Create a directory on the PC server called dhs3mgr.this directory will contain a basic version,
a static patch and dynamic patch Ex:
b) The Call Server must perform a network boot on the installation server PC on which the
ENTERPRISE PC INSTALLER application is running.
c) The installation server PC provides the Call Server with an IP address via DHCP.
d) The installation server PC provides the "linux.ram" or the "pxeloader" for an Appliance Server
via TFTP.

51
e) The installation server PC provides the Linux OS, swinst packages, and telephone application
binaries via FTP.
f) The Call Server restarts automatically when installation is complete.

Note: RECOMMENDATION before the Upgrade:
Before upgrading an existing installation, SAVE the Alcatel OmniPCX database on the Call
Server hard disk and transfer the database backup file to the PC.
PROCEDURE
1. PC Installer configuration
To install the PC Installer, Run the executable file in the following directory. For more
explications consult the technical communication TC0631
1.1 Drive selection

PC Installer
Path Preferences/Drive
Parameters D: (example, choose the drive where the release is)
The folder name where the release is must be dhs3mgr
1.2 Full installation selection

PC Installer
Path Installation type
Parameters Linux + Call handling
Note: After the installation type selection, a new window is opened

52
1.3 Call server type selection

Path Call Server type
Parameters Alize
1.4 Release to install selection

Path Call handling version
Parameters f25006i (e.g.)
Give the full release (including the last patch)
1.5 Country selection

Path Country
Parameters us (example for U.S.)
1.6 Connection type selection

Path Network type
Parameters Direct cable
It is better to use a direct connection with the CPU to load it.
In case of connection through the company network, the Ethernet address (MAC address) of
the CPU must be set in the Ethernet address field.
1.7 PC Installer parameters validation

Action Click on Apply button

53
2. CPU Reset and boot on Ethernet
2.1 CPU-CS or Appliance Server With an empty hard disk

On the call server
Action Switch on the power of the e-CS board
If the hard disk is empty, the loading starts automatically.
If the hard disk contains a call handling software see 2.1
2.2 With a hard disk containing the call handling software

On the call server
Login root
Command grubboot ETHER
Result Disk have to be reinstalled after reboot.
The system will automatically reboot after confirmation.
Do you want to continue (y/n, default y):
Entry Y
Note: At the end of loading, the CPU restarts automatically. ” PC Installer” windows can be then
closed.Now, the following actions must be done on the CPU:
CPU IP configuration using “netadmin” command
Data base restoration or empty data base creation
Soft licenses files restoration

54
Upgrade using Static and Dynamic patches
PROCEDURE
OBJECTIVE
- To learn how to perform a software version upgrade using static and dynamic patches
REFERENCE
OVERVIEW
The installation of a patch is carried out with the OmniPCX Enterprise PC Installer and swinst
software on the OmniPCX Enterprise .
For the telephone application, there are two types of patches: (Example in R6.1)
• Static patch. (f25006)
• Dynamic patch. (f25006i)
Telephone patches are delivered as a cpiofile file (Unix compressed file) located in the directory
\dhs3mgr\<version>\dhs3linux
example: \dhs3mgr\e1604\dhs3linux\comm\cpiofile.
Most binaries are located in the comm directory.
For country-specific binaries, the cpiofile file is at the same level of the tree structure but in a
directory named according to the international standard.
example: es for Spain, ch for Switzerland, etc.

55
PROCEDURE
1. Open OmniPCX Enterprise PC Installer

On the PC
Action Double-click on the icon of the OmniPCX Enterprise PC Installer on the desktop
Select In the menu Preferences, select the drive that contains the patch.
In the field Installation type, select the type of installation to "Call handling or
patch only".
Remark:
a FTP server are run during all the installation of the patch and are stopped
only when the window OmniPCX Enterprise PC Installer is closed.

56
2. Static telephone patches

A static patch can easily be distinguished from a full version by the presence of two text files,
for_comp and patch, located in the CD-ROM tree structure in:
<CD-ROM root>\dhs3mgr\<patch name>\installlinux\
The file for_comp is used when installing a full version in standard mode (see the procedure ”Load
a software version - Standard installation of a complete version’’). For a static patch, this file
contains the name of the full version associated with the patch.
The file patch gives the patch version.
e.g.: for the static patch f2.500.6 with a CD-Rom drive mapped on D:, there will be the file
D:\dhs3mgr\f25006\installlinux\for_comp containing the string ‘’ f2500’’
D:\dhs3mgr\f25006\installlinux\patch containing the string ‘’patch_f2.500.6’’.
Static patch name is usually the name of the full version followed by the patch number.
Each new static patch includes all corrections made in previous patches.
2.1 Install a static patch

On the call server
Login swinst
Select Easy menu
Stop the telephone
Remark:
These patches are new telephone application files containing corrections or
upgrades. They can only be installed with the phone shut down or when
installation is on the inactive partition
They are installed after a full version has been installed. They cannot run if the
standard telephone version is not installed.
Result Please confirm to stop the telephone (y/n, default y):
Entry y
Result The system reboots:
INIT: Sending processes the TERM signal Jan 12
Stopping alzled: /etc/rc.d/rc(1): Stopping alzled:
[ OK ]
Stopping role: /etc/rc.d/rc(1): Stopping role:
[ OK ]
Shutting down TEL services
Login swinst
Select Expert menu
Deliveries installation

57
Install delivery from server

Result Enter the name of the server ->
Entry (e.g.) 10.1.1.10

Remark:
Use the IP address of the PC from which you want to install the patch
Result The installation of the binaries will modify the current installed
versionPlease, confirm the installation of a new version (y/n, default
y):
Entry y
Result Enter the full path of the delivery on the server
Entry -> (e.g) /dhs3mgr/f25006
Result confirm the full path d:/dhs3mgr/ f25006 (y/n, default y):
Entry y
Result The path of the delivery is d:/dhs3mgr/ f25006
NOTES: if the answer is YES ,a binaries backup will be done in case of
trouble.
Entry n ( backup is not mandatory for the lab )
Result --> Searching for symbolic link '/DHS3bin/nmc/log' on target
'/DHS3dyn/tmp' ...
WARNING: symbolic link '/DHS3bin/nmc/log' already exists.
Set chown 'mtcl:tel' on '/DHS3bin/nmc/log' ...
<-- Symbolic link '/DHS3bin/nmc/log' successfully created.
@@@@@ End of post_inst at Mon Apr 15 09:42:00 CEST 2002
In order to run the linux packages
In order to run the emulation layer
YOU HAVE TO REBOOT THE SYSTEM
End of operation!
Press return
Action Press RETURN
In the swinst menu, go back to easy menu
Start the telephone
Remark:
Some patches require a complete reboot. This is the case when a new version
of Linux is installed for example. When the installation (via swinst) is complete,
a system message is displayed requesting the user to reboot the machine.

58
2.2 Check the version installed on the hard disk

On the call server
Login mtcl
Command siteid
Result Customer's name : ALCATEL ;
Customer's address: Kergaradec ;
Customer's town : Brest ;
Customer's country: FRANCE ;
Customer's install number: ;
CPU type : CPU80
Linux version : 33.3
Delivery software version: f2.500;
Patch version : 6 ;
MAO software version : F2.500;
Software Version Name : R6.1 ;
System Country : US ( 5);
Node number : 1 ;
Network number : 1 ;
Alarm relay state: ACTIVE

59
3. Dynamic telephone patches

These patches are new telephone application files containing corrections or upgrades. They can be
installed on the active or inactive partition with the phone running without disturbing phone
operation. 1
After a dynamic patch has been installed, it is immediately installed in CPU memory. The customer
then has the corrected version available without having to reboot the machine.
This installation is performed using the memloader tool. For each process patched in memory, a
2176 incident indicating the operation is emitted.
Dynamic patches are installed after static patch installation. They cannot run if the standard
telephone version and corresponding static patch are not installed.
Dynamic patch name always ends with one or two letters. The first dynamic patch for a version ends
with the letter "a", the next with the letter "b" and so on till the end of the alphabet. If further patches
are necessary after the letter "z", they are named "aa", “ab”, etc.
3.1 Install a dynamic patch

On the call server
Login swinst
Select Expert menu
Entry (e.g.) 10.1.1.10

Remark:
Use the IP address of the PC from which you want to install the patch
y):
Entry y
Entry -> (e.g.) /dhs3mgr/f25006i
Result confirm the full path d:/dhs3mgr/ f25006i (y/n, default y):
Entry y
Result The path of the delivery is d:/dhs3mgr/ f25006i

60
Entry n
Result Check linux version
linux/dhs3mod-1.10a_30-15alc.i386.rpm
linux/netadmin-4.4.17-20alc.i386.rpm
RPMS/lx_version-4.4-4alc.i386.rpm
--> Searching for symbolic link '/DHS3bin/nmc/log' on target
'/DHS3dyn/tmp' ...
3.2 Check the loading of the dynamic patch

On the call server
Login mtcl
Command incvisu | grep 2176
Result 02/03/04 11:56:40 001001I|--/--/-/---|=2:2176=Patch dynamique installe
pour TEL

61

62
Software loading on Call Server
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to download a Call server with the Alcatel OmniPCX Enterprise software
MANAGEMENT
1. Ask to the trainer an empty hard disk and install it on board in the place of the initial hard
disk.
2. Check wiring (IP and V24) between your PC and OmniPCX Enterprise.
3. Check that the version of Alcatel OmniPCX Enterprise is located in the repertory “/DHS3mgr”
on your PC.
4. Install the software of CPU loading (OmniPCX Enterprise PC Installer) on your PC. The way of
the setup.exe is: \dhs3mgr\f2500\pcmao\boot_res\pcinstall (for example).
5. Carry out the loading of the version on your CS as indicated in the procedure.
6. As soon as the TP is finished, give the initial hard disk and start again the CS.
Issue 01 REF. ENTP0442H02TEUS.doc HO.1

63
Software loading on Crystal CPU
HO.2 REF. ENTP0442H02TEUS.doc Issue 01

64
Alcatel University NOTES
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
Alcatel University – https://www.businesspartner.alcatel.com
65
NOTES Alcatel University
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
66
Alcatel OmniPCX Enterprise Overview
Multi version loading

OBJECTIVE:
◆ To make a multi version loading
Alcatel OmniPCX Enterprise – Multi version loading

67
Overview
Multi-version loading allows two versions to be

simultaneously installed on the same hard disk.
➨ Different Releases
➨ Different Releases including correction of patch
Its main advantage is that a 2nd version can be set up on

the Call Server without stopping the telephone application.
Once the 2nd version is installed, you simply restart the

Call Server on it.
Should a problem arise, it is possible to switch back to the

old version which is still present.


68
Overview
There are two cases of Multi-version loading
➨ Copy of the complete first version and loading of a software

patch for update
▼ Possible when the basic version stays the same
➨ Complete loading of a new version and copy of the data

(telephone database and Linux data) from the old one.
▼ To be used for a different version of Linux
▼ The OPS files may have to be changed as well

Multi-version loading is advantageous for a patch, because everything can be prepared remotely.
A complete copy of the 1st version can be made: chorus, binaries and database, and then download the patch to the inactive 2nd
version. On the given date, you simply go on site to validate the switching. It can be validated remotely, but it is preferable to be on
site should problems arise.
This procedure allows you not to go to the customer’s site with another Call Server which has been preloaded at the agency
(requiring that you have a Call Server whose edition is identical or compatible if the Call Server is doubled, or that you have the
customer’s exact version in your agency,...)

69
Structure of the hard disk
The directory structure for the hard disk
/root2_d /
Second release First release
on the disk on the disk
/var2 /var
/usr5 /usr2
/usr6 /usr3
/usr7 /usr4
Common part

During the initial release Installation,hard disk is automatically partitioned (automatically format).
Others specific partitions are common for both versions :

/dev/hda1 (linked with /dev/grub)
Partition used by the boot GRUB
/dev/hda2 (linked with /dev/bios)
Partition used for the CPU’s bios update
/dev/hda16 (linked with /dev/vmu)
Partition used for the 4645 voice mail system
/dev/hda17 (linked with /dev/crashdump)
Partition used to save the memory in case of CPU crash

70
Structure of the hard disk
The directory structure for the hard disk
➨ Disk partition with the ACTIVE version

▼ / Active linux operating system
▼ /usr2 (linked with /DHS3bin) Active OXE version
▼ /usr3 (linked with /DHS3data) Active Data Base
▼ /var Logs and active variable data
Common part
▼ /usr4 (linked with /DHS3dyn) Dynamic accounting data
▼ /usr7 (linked with /DHS3ext) System voice guides
➨ Disk partition with the INACTIVE version

▼ /root2_d (linked with /root2) Inactive linux operating system
▼ /usr5 (linked with /DHS3bin2) Inactive OXE version
▼ /usr6 (linked with /DHS3data2) Inactive Data Base
▼ /var2 Logs and inactive variable data

DHS3xxx directories are links to others directories in the disk. They are used in installation scripts,the inactive partition is generally
mounted in the /dev/null directory.
ver2cho visible command allow to mount partitions in home directory.
(1)xa000000> ver2cho visible ; df -v
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/hda5 495876 84823 385452 18% /
/dev/hda7 1007960 234172 722584 24% /usr2
/dev/hda8 1007960 97124 859632 10% /usr3
/dev/hda9 4276616 536836 3522536 13% /usr4
/dev/hda15 2015984 51400 1862176 3% /usr7
/dev/hda6 396623 4292 371845 1% /var
/dev/hda11 495876 84812 385463 18% /root2_d
/dev/hda12 396623 2341 373796 1% /var2
/dev/hda13 1007960 234544 722212 25% /usr5
/dev/hda14 1007960 97096 859660 10% /usr6
/dev/hda13 1007960 234544 722212 25% /root2_d/usr2
/dev/hda14 1007960 97096 859660 10% /root2_d/usr3
/dev/hda9 4276616 536836 3522536 13% /root2_d/usr4
/dev/hda15 2015984 51400 1862176 3% /root2_d/usr7
/dev/hda12 396623 2341 373796 1% /root2_d/var
Ver2cho hidden command is used to mask Inactive partitions.

(1)xa000000> ver2cho hidden ; df -v
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/hda5 495876 84823 385452 18% /
/dev/hda7 1007960 234172 722584 24% /usr2
/dev/hda8 1007960 97124 859632 10% /usr3
/dev/hda9 4276616 536836 3522536 13% /usr4
/dev/hda15 2015984 51400 1862176 3% /usr7
/dev/hda6 396623 4292 371845 1% /var

71
Multi version loading - Overview
First possibility - Copy followed by patch loading
Initial state: The active part of the disk only is loaded
➨ Example of versions on the disk:
Active partition Inactive partition

linux : 33.0 linux : -----
swinst : 2.25.0 swinst : -----
binaires : F2.500.0 binaires : -----
1) Total duplication of the active to the inactive partition
➨ State of versions on the disk:

linux : 33.0 linux : 33.0
swinst : 2.25.0 swinst : 2.25.0
binaires : F2.500.0 binaires : F2.500.0

WARNING:
The following pages correspond to an example of one release. It must be adapted to the release you have in the first partition as
well as the patch you have to download to update the 2nd version

72
First possibility - Copy followed by patch loading
2) Loading of the patch in the inactive partition

swinst : 2.25.0 swinst : 2.25.0
3) Versions switch

swinst : 2.25.0 swinst : 2.25.0


73
Second possibility - Complete loading
Initial state: The active part of the disk only is loaded

linux : 16.0 linux : -----
binaires : E2.404.0 binaires : -----
1) Loading of linux in the inactive partition
➨ State of versions on the disk after loading:

binaires : E2.404.0 binaires : -----

WARNING:
The following pages correspond to an example of one release. It must be adapted to the new release you have to download on
the 2nd partition

74
2) Loading of the complete version in the inactive partition

swinst : 2.17.0 swinst : 2.25.0
binaires : E2.404.0 binaires : F2.500.0
3) Loading of a binary patch in the inactive partition

swinst : 2.17.0 swinst : 2.25.0
binaires : E2.404.0 binaires : F2.500.5

Notes:
In this example we could as well download the dynamic patch f25006i. ( 3rd step )

75
4) Copy of the Linux data and the database from the

active partitions to the inactive ones
5) Reboot of the CPU on the inactive partitions
➨ State of versions on the disk after switch:

swinst : 2.25.0 swinst : 2.17.0
binaires : F2.500.6 binaires : E2.404.0
6) Installation of the new OPS files (if required)
7) Reboot the Call Server (if required)

In case of trouble ,it is possible to go back to previous release switching again to the initial partition.
Remark:
During the switch ,boards can receive new binaries from new release.If you decide to go back with the initial release ,another
downloading will be done if necessary.

76
Multi version loading /Static and Dynamic patches
PROCEDURE
Multi version loading/Static and Dynamic patches
OBJECTIVE
- To learn how to perform a static and dynamic patches using the multi version loading.
REFERENCE
Documentation/System/Call Server/ using the multi-partition
OVERVIEW
Initial hard disk configuration :release R6.1
Basic version f2500 and static patch f25006 already Installed on active partition.
Objective of this lab:
a) Duplicate Linux and binaries from active partition to inactive partition.
b) Install dynamic patch on the inactive partition.
c) Check that multi version has been done properly then switch the version.

77
Static and Dynamic patches
PROCEDURE
1. Duplicate the active version partitions to the inactive version ones
1.1 Check the version already install on the active partition

Sur le call server
Login mtcl
Command siteid
Result Customer's name : ALCATEL ;
Customer's address : Kergaradec ;
Customer's town : Brest ;
Customer's country : FRANCE ;
Customer's install number : ;
CPU type : CPU80
Linux version : 33.3
Delivery software version : f2.500 ;
Patch version : 6 ;
MAO software version : F2.500 ;
Software Version Name : R6.1 ;
System Country : FRA ( 5);
Node number : 1 ;
Network number : 1 ;
Alarm relay state : ACTIVE

78
2. Duplicate the active version partitions to the inactive version ones
2.1 Access to the swinst expert menu

path On the PC
Login: swinst
Chose Expert menu
Action Select the following options:
Select Cloning & duplicate operations
Partitions duplication
2.2 Select data to duplicate

Action ALCATEL BUSINESS SYSTEMS
Partitions duplication operation menu Installation FACILITIES
2.25.0
1 Duplicate Linux, packages and Linux data
2 Duplicate Linux data
3 Duplicate delivery
4 Duplicate database
5 Duplicate all
6 About last duplicate operation
Your choice [1..6, Q] ? 5
2.3 Confirm the partitions duplication

Action Confirm the duplication of all (y/n, default y): y

79
3. Check that every steps is done properly during the duplication
3.1 Linux partition duplication

On the call server
Result Duplicating Linux and packages
Clean the second Linux version. Confirm (y/n, default is y):y
Second version cleaned
setup-2.1.9-22mdk_3alc
filesystem-2.0.6-2mdk_1alc
ld.so-1.9.11-4mdk_2alc
glibc-2.1.3-16mdk_3alc
…
Please wait, working ….
3.2 Network settings duplication

On the call server
Result Duplicating the network configuration
Duplicate the network configuration in the second Linux version.
Confirm (y/n, default is y):
Please wait, working ...
The network configuration is duplicated
3.3 Swinst duplication

On the call server
Result Transfer for pkg part in preparation
End of duplication for pkg part files

80
3.4 Binaries files duplication

On the call server
Result checking Linux version
LINUX 33.3 is already installed
Running mkusers ...
/rootbis/DHS3bin/lib/librt-2.1.2.so
/rootbis/DHS3bin/lib/libutil-2.1.2.so
/rootbis/DHS3bin/downbin/bnvintgd
/rootbis/DHS3bin/downbin/bnvintof
/rootbis/DHS3bin/downbin/bnvintofs
3.5 Database duplication

On the call server
Result Stop the mao process…
Building list of files….
Deleting the old files on unactive version….
/rootbis/DHS3data/mao/SUBSPNM.idx
/rootbis/DHS3data/mao/SUFFDATEM.dat
/rootbis/DHS3data/mao/SUFFDATEM.idx
/rootbis/DHS3data/mao/SUPERVM.dat
/rootbis/DHS3data/mao/SUPERVM.idx
/rootbis/DHS3data/mao/SYSOPTM.dat
/rootbis/DHS3data/mao/SYSOPTM.idx
……
8763 blocks
4. Quit swinst
Action Select Q to go back to the previous menu in order to exit

81
5. Check the use rate of the partitions of the hard disk, and their link to the
logical names
5.1 Make visible the partitions of the inactive version

On the call server
Path Under the terminal
Login:mtcl
Password:mtcl
Action (1)xa001001> ver2cho visible
(1)xa001001> df -v
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/hda5 495876 85631 384644 19% /
/dev/hda7 1007960 268368 688388 29% /usr2
/dev/hda8 1007960 161252 795504 17% /usr3
/dev/hda9 4276616 39456 4019916 1% /usr4
/dev/hda15 2015984 41508 1872068 3% /usr7
/dev/hda6 396623 4049 372088 2% /var
/dev/hda11 495876 86234 384041 19% /root2_d
/dev/hda12 396623 3010 373127 1% /var2
/dev/hda13 1007960 268336 688420 29% /usr5
/dev/hda14 1007960 161128 795628 17% /usr6
/dev/hda13 1007960 268336 688420 29% /root2_d/usr2
/dev/hda14 1007960 161128 795628 17% /root2_d/usr3
/dev/hda9 4276616 39456 4019916 1% /root2_d/usr4
/dev/hda15 2015984 41508 1872068 3% /root2_d/usr7
/dev/hda12 396623 3010 373127 1% /root2_d/var
(1)xa001001>
Notes:
Comparing both partitions, we can see that are totally identical.
Dynamic patch has just to be install now.

82
6. Run the OmniPCX Enterprise PC Installer application on the PC and select the
loading option Make visible the partitions of the inactive version
On the PC server
Action Run the program: OmniPCX Enterprise PC Installer
And select drive where the patch is available.
Action
6.1 Install a dynamic patch on the inactive partition

On the call server
Login swinst
Select Expert menu
Result Press 1 for the unactive version and Enter the name of the server ->
Entry (e.g.) 10.1.1.10

Remark :
Use the IP address of the PC from which you want to install the patch. We
could used the PC host name if it has been managed on netadmin menu.
y):
Entry y

83

Entry -> (e.g.) /dhs3mgr/f25006i
Result confirm the full path d:/dhs3mgr/ f25006i (y/n, default y):
Entry y
Result The path of the delivery is d:/dhs3mgr/ f25006i
'/DHS3dyn/tmp' ...
WARNING : symbolic link '/DHS3bin/nmc/log' already exists.
6.2 Switch the versions

On the call server
Login swinst
select Expert menu
Cloning & Duplicate operation
Switch on unactive version
'/DHS3dyn/tmp' ...
WARNING : symbolic link '/DHS3bin/nmc/log' already exists.
Result Please confirm switching on the unactive version (y/n, default y):

84
entry y
Result Autostart is set on unactive version
Do you want to switch back to the previous version if system resets
(y/n, default n):
entry n
Result In order to complete the installation of the swinst package
you have to connect as swinst user after the switching
Do a version switch. Confirm (y/n, default y):
entry y
Notes: After this confirmation the system will restart automatically
It will be mandatory to enter the country code during the first connection to the
swinst menu.
6.3 Check the versions installed in the active partitions

On the call server
Login swinst
select Expert menu
Software Identity display
Application software identity
Result Press 0 for the active version, 1 for the unactive one or q to quit
Entry 0
Result Application software identity
R6.1-f2.500-6-i-fr-c80s1
Business identification: R6.1
Release:
DELIVERY f2.500
Patch identification: 6
Dynamic patch identification: i
Country: fr
Cpu: c80s1

85

86
Release Installation using the multi partition
PROCEDURE
OBJECTIVE
- To learn how to Install a new version using the multi-partition solution.
REFERENCE
Documentation/System/Call Server/ using the multi-partition
OVERVIEW
Initial hard disk configuration:In this example we could imagine tow different release ex:
R5.1.1 on active partition: Basic version E2502, static patch E25022 and dynamic patch
E25022G already installed on active partition.
Objective of this lab:

Install a new release ex R6.1 (f2500 ,f25006,f25006i). In that case (when basic version are
different) it will be necessary to process in the following way:
a) Download separately the Linux on inactive partition.
b) Download the basic version and different patches in the inactive partition.
c) Duplicate and translate database from active to inactive partition in order to switch finally
on the new release.

87
Release Installation using multi partition
PROCEDURE
1. DOWNLOAD THE LINUX ON THE INACTIVE VERSION
1.1 Run the OmniPCX Enterprise PC Installer application on the PC and select the
loading option
On the PC server
Action Run the program: OmniPCX Enterprise PC Installer
And select drive where the Linux directory is available. Then select Linux on
inactive partition
Action

88
1.2 Select the Linux version to load on inactive partition

On the call server
Login swinst
Select Expert menu
Packages installation
Install Linux on unactive version from server
Entry (e.g.) 10.1.1.10

Remark:
Use the IP address of the PC from which you want to install the patch. We
could used the PC host name if it has been managed on netadmin menu.
Result Enter directory of linux on 10.1.1.10 (default /bootp/linux) ->
Enter the name of the linux version (eg:11.0)
Entry ->33.0
Result Clean the second linux version. confirm (y/n, default is y):
Entry y
Result You will erase the actual bootp server if you respond yes to this
question has this cpu to be a bootp server for major installation
(y/n, def is y):
Entry y
Result Clean the /bootp/linux actual content. confirm (y/n, default is y):
Entry y
Notes: To know the Linux version it could be useful to consult the following
way in the dhs3mgr directory on the PC server

89
2. Installation of the new release R6.1
2.1 Basic version installation on the inactive partition

On the call server
Login swinst
select Expert menu
Result Press 0 for the active version Press 1 for the unactive version
entry 1
entry (for example) 10.1.1.10

y):
entry y
entry -> (e.g.) /dhs3mgr/f2500
Result confirm the full path /dhs3mgr/f25006i (y/n, default y):
entry y
Result The path of the delivery is /dhs3mgr/f2500
entry n
'/DHS3dyn/tmp' ...

90
Notes:
Patches Installation (static and dynamic)
The process to download patches is exactly the same than downloading
Basic version. The only parameter which will change will be the way in
dhs3mgr directory.
For the Static patch:under swinst menu select
/dhs3mgr/f25006
For the dynamic patch:
/dhs3mgr/f25006i
2.2 Duplicate database from active to inactive partition

On the call server
Login swinst
select Expert menu
Cloning & duplicate operations
Partitions duplication
Duplicate database
Result Confirm the duplication of the database confirm (y/n, default is y):
entry y
Notes: in case of migration, the system could will ask you to translate the
database before to duplicate it. If it ‘s happen entry YES to translate the
database .

91
2.3 Switch the versions

On the call server
Login swinst
select Expert menu
Switch on unactive version
'/DHS3dyn/tmp' ...
Result Please confirm switching on the unactive version (y/n, default y):
entry y
Result Autostart is set on unactive version
Do you want to switch back to the previous version if system resets
(y/n, default n):
entry n
Result In order to complete the installation of the swinst package
you have to connect as swinst user after the switching
Do a version switch. Confirm (y/n, default y):
entry y
Notes: After this confirmation the system will restart automatically
It will be mandatory to enter the country code during the first connection to the
swinst menu.

92
2.4 Check the versions installed in the active partitions

On the call server
Login swinst
select Expert menu
Cloning & Duplicate operation
Software Identity display
Application software identity
Result Press 0 for the active version, 1 for the unactive one or q to quit
Entry 0
Result Application software identity
R6.1-f2.500-6-i-fr-c80s1
Business identification: R6.1
Release:
DELIVERY f2.500
Patch identification: 6
Dynamic patch identification: i
Country: fr
CPU: c80s1

93

94
Software Loading/multi-version
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to perform a software upgrade with a static and dynamic patch using multi version
MANAGEMENT
Initial hard disk configuration:release R6.1
Basic version f2500 and static patch f25006 already Installed on active partition.
1. Check by swinst the active and inactive versions installed on the hard disk
2. Check by the ‘df –v’ command the used space in the active and inactive part of the hard disk.
3. Make a complete copy from the active to the inactive part of the hard disk.
4. Check the differences on the hard disk by swinst and the ‘df –v’ command.
5. Load a dynamic patch in the inactive part of the hard disk
6. Check the versions by swinst again.
7. Make a version switch and check that everything’s alright as the CPU starts up.

95
Software Loading/multi-version

96
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
97
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
98
Patch downloading from 4760

OBJECTIVE:
◆ To describe the principles of scheduled patch downloading from Alcatel OmniVista 4760
Alcatel OmniPCX Enterprise – Patch downloading from 4760

99
Objectives
Allow the remote automatic loading of patches on several

systems
➨ Control of compatibilities between patches and versions
➨ Schedule of the operations
▼ Patch downloading on one “distributor” system
▼ Patch downloading on several systems of the network
▼ Automatic switching at a predefined date and time
✦ Possibility to come back in case of problem
➨ History of operations

The remote loading of version or patch exist since release 2.1 of the Alcatel OmniPCX 4400.
This service allows to set one system to act as Distributor and to broadcast the version or patch to the other systems of a network
(systems acting as clients).
Available since R4.0 of the Alcatel OmniVista 4760.

100
Connections and facilities
The 4760 server must be connected to the ‘distributor”

PCX
➨ Connection via Ethernet
➨ Connection via PPP and an IRAD board in the OXE
Transfer in SFTP / SSH mode if necessary
For the moment, only the automatic installation of patch is

possible on the systems
➨ No full version loading
➨ No remote OPS installation

The IRAD board allows the connection over several B channels at the same time. This boards is seen as a T2 board in the Alcatel
OmniPCX Enterprise (Common hardware).
The connection between the OmniVista 4760 server and the Alcatel OmniPCX Enterprise can be realized via SFTP / SSH or FTP /
Telnet.
The automatic installation of patch allows the automatic loading and switching of the PCXs.
This kind of operations cannot be used for a full version loading (databases translation, new OPS installation, etc.).

101
Example
Configuration of a loading for an Alcatel OmniPCX

Enterprise


102
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
103
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
104
e-CS duplication

OBJECTIVE:
◆ To describe the e-CS duplication principle
Alcatel OmniPCX Enterprise – e-CS duplication

105
e-CS duplication
Summary
Introduction
Switch over mechanism
Topology
Media gateway backup link
Duplication and ABC-F network
Restrictions


106
e-CS duplication
Introduction
Principle: duplication of the e-CS software platform
➨ Main call server
➨ Standby call server
Purpose: provide continuous service in the unlikely event of

one of the call servers failing

With the OmniPCX Enterprise, it is also possible to duplicate the E-CS, in this case operating on a specific and dedicated CPU,for
providing continuous service in the unlikely event of one of the CPU failing. Providing a CPU standby function is often required in
contact center serving emergency or 24hr/7 days a week services (without interruption), supporting both cases of failure and
maintenance operation.

107
e-CS duplication
Introduction
Services: if the Main call server fails, the system switches

on the standby one (which becomes Main):
➨ Calls already established are maintained
➨ Calls being connected during switch-over are lost
➨ Both server databases are duplicated and coherently

maintained
▼ Management modifications
▼ Accounting tickets
Solution: IP link between both e-CS


108
e-CS duplication
Introduction
Main e-CS in service
Main e-CS Standby e-CS
IP Signaling
Network
IP-MG

Even though the system hardware architecture allows both main and standby servers to operate in the same Media-gateway chassis, it
is recommended for reasons of eventual power supply unit failure, to insert the CPUs into independent chassis.
As soon as the main E-CS is operational and reachable, it controls the Media Gateways and the IP terminals.

109
e-CS duplication
Introduction
Loss of Main e-CS
XMain e-CS Standby e-CS ⇒ Main e-CS
IP Signaling
Network
IP-MG

If Main E-CS falls down or is unreachable, Media gateways and IP terminals are managed by the Standby E-CS (which becomes the
"Main").

110
e-CS duplication
Introduction
Implementation using:
➨ An IP Link which performs the signalling between both Call

servers. It handles:
▼ The "keep alive" messages exchange between the two e-CS
▼ The duplication data exchange
➨ A reference Media Gateway

▼ This one is used when the call servers can not exchange the "keep-
alive" messages ( IP network problem )

The solution used for the duplication is an IP Link process which manage all the Data Link (DL) with all IP devices managed by the
Main call server and with the standby call server.
Keep alive: This message allows to maintain "active" the link between both call servers.

111
e-CS duplication
Call server initialisation:
➨ In the Mao is declared:

▼ The "Call Server Role":
✦ Primary
✦ Secondary
▼ The Reference Media Gateway
➨ To determine its role, each call server tries to establish a

connection with the other one (CONNECT message)
➨ If it succeeds, a negotiation occurs to decide the exact role

of each one according to the MAO parameter
➨ Defence: If the "Call server role" is not correctly defined, the

e-CS with the highest IP address starts in Main role

The "call server role" is used in case of simultaneous start-up of both e-CS.
Initialisation:
e-CS A state e-CS B state result for e-CS A result for e-CS B
Unspecify (primary) Unspecified (secondary) becomes main becomes standby
Unspecify (primary) Unspecify (primary) negociation * negociation *
Unspecified (secondary) Unspecified (secondary) negociation * negociation *
Main Unspecified (primary or secondary) stay main becomes standby
* see Defence mechanism
Procedure used to determine the role of both Call Server:

☞ During initialization step, the Call server (A), in state UNSPECIFY, indicates to the other e-CS (B) its availability with a CONNECT
message, that contains the information primary / secondary
☞ The Call Server B, on receiving the CONNECT message, will use the following algorithm:
•If B is already Main: B remains Main and the other one, A, becomes Stand-By
•Otherwise:
- If A is set up as primary and B as secondary Call Server: A becomes Main and B Stand-By
- If A is set up as secondary and B as primary Call Server: B becomes Main and A Stand-By
☞ B sends then a CONNECT_ACK message, that indicates A which role it should take.
Defence mechanism:
If the above algorithm is not enough to determine the role of each e-CS (incoherent management for example), then the Call Server
which will become Main is the one with the highest IP address.

112
e-CS duplication
Switch over:
➨ Once roles have been determined:

▼ there is a "Keep Alive" messages exchange between Main and
Standby
➨ If the Main e-CS falls down or has an IP link process

problem:
▼ The Standby e-CS becomes Main
▼ All IP devices reconnect to the new Main e-CS
▼ The established communications are maintained
➨ If the IP network is down between both e-CS

▼ There are two main Call Server (Double Main Mode) on the network
✦ a Real Main Call Server
✦ a Pseudo Main Call Server
▼ The "Reference Media Gateway" is used in this case to determine the
Real Main on which will be activated the MAO (management)

Once roles have been determined, the Main call server generates "Keep Alive" messages and the Standby call server answers those
"Keep Alive" messages.
If Main e-CS falls down or has an IP link process problem, the other call server becomes Main and a message is sent to all IP devices
to reconnect to the other call server keeping though all the established communications
The call server which has an IP link problem must reboot.
When the two call servers are not "seeing" each other, they both try to connect to the reference e-MG, the one which succeeds
becomes the Real Main and the other one becomes the Pseudo Main (MAO not activated).
The reference e-MG shall be as close as possible from one e-CS (same switch).
If no reference Media Gateway has been declared, the Call Server with the highest IP address becomes the "Real Main".

113
e-CS duplication
Double Main Mode
Real Main Pseudo Main
Reference Node 1
IP-MG
Node 1 '
IP-MG
IP-MG

If the IP network is down between both e-CS, the standby call server doesn't receive any "keep alive" messages, it switches over and
reconnects to all IP devices it has access to.
The Main server declares losing the Standby call server and deletes all Data Link with IP devices which are on the other part of the
node.
In this scenario, the node is divided into two parts which runs independently.
Link between e-CS and reference e-MG:

It is a classical e-CS /e-MG signalling link (managed by IP Link Process) but with a specific UDP port.
Each e-MG is listening on this port, but only the reference e-MG will receive messages from the e-CS.

114
e-CS duplication
Call server link "wake up":
➨ After a call server shutdown
▼ It restarts as in initialisation mode (restarts as Stand-by if there is

already a Main e-CS)
➨ After an IP network problem
▼ The Pseudo Main Call Server reboots
▼ IP devices which were connected to the Pseudo Main reboot and

reconnect to the Real Main
✦ The established communications are released
▼ A database duplication has to be launched to synchronise the call

servers


115
e-CS duplication
Topology
Recommended:
➨ Both call servers on the same LAN switch

➨ Call servers on two different LAN switches with inter-switch
Link backup
Not recommended:
➨ Call servers connected through an IP WAN
➨ Both e-CS in the same Media Gateway
▼ All installation must be switched off for maintenance
E-CS A
E-CS B

Call servers connected through a WAN is not authorised for call server backup because a high viability level cannot be provided.

116
e-CS duplication
Media Gateway signalling link backup
It is possible to have a signalling link backup through the

public network between the e-CS and a Media Gateway
A media gateway can not be connected with two e-CS at

the same time
➨ The second connection is refused
In Double Main mode:

➨ The backup signalling is only available with the "Real Main"
e-CS

We prohibit that a same media gateway has two links with two different call servers. If one media gateway has already a link with
another call server, the second connection will be refused.

117
e-CS duplication
Duplication and ABC-
ABC-F Network
The two sides of the network are not synchronised
Real Main Pseudo Main

(MAO ON) (MAO OFF)
Node 1
E-CS Node 1 ' E-CS
Node 2 Modification Node 3

files exchange No database
No modification
files exchange update
➨ When the IP network problem is solved:

▼ A copy of the Main e-CS database has to be made on the Standby
▼ The modification files are exchanged automatically to resynchronise the
network

In ABC-F networks, when the database of one node is modified (new user creation for example), modification files are exchanged
between the nodes to keep the coherency within the network.
In Double Main mode, as the MAO is stopped on the Pseudo Main, it is not possible to create modification files on this e-CS and thus
update the database. A mastercopy (Main e-CS database copy on Standby e-CS) has to be launched.
In the example above, if a modification is made on node 2, the modification file is broadcast to the Real Main of node 1, but doesn't
reach node 1 pseudo main and node 3.
Same thing, if modifications are made on node 3, there is no update of node 1 and node 2.
This scenario creates a de-synchronisation of the database on each side of the network.
The modification files which are not broadcast are kept on the nodes until the IP network comes up and then exchanged by the nodes
to resynchronise the ABC-F network.
=> No data are lost in Double Main configuration (except the modification files created when the stack is full).

118
e-CS duplication
Restrictions
Both e-CS must be on the same platform type
Under specifics conditions, it’s now possible in R6.1 to

place Both call servers in different IP sub-networks.This
new feature is called “Spatial Redundancy”
Services not provided in Double Main mode:
➨ Accounting (tickets generated on the Pseudo Main can not

be reported on the other call server)
➨ Traffic observation (same thing)
➨ One part of the network has no Voice Mail

“Spatial Redundancy”:this new feature will be seen later with more details in the curriculum training.“ IP Advanced :ENTP374US”.

119

120
Duplication System without Spatial redundancy

(CPU CS A)

OBJECTIVE:
◆ To describe the configuration of the CPU A in case of duplicated configuration without spatial redundancy
Alcatel OmniPCX Enterprise – Duplication System without Spatial redundancy (CPU CSA)
Ref. ENTP0438C02TEUS Issue 01
121
Full IP configuration of CS
Management of CPU A
Full IP configuration
➨ netadmin
Warning: for a specific setup please use menu mode (netadmin -m)
Do you want to erase the existing setup? y
X25 private network number? 1
Unique site number? 1
Warning: the node name must be unique.

Enter node name? node001001
Do you want to activate internal name resolver (y/n default is 'n')? n
Enter local CPU position (a or b) for duplicated configuration

or n for single CPU (default is 'n')? a

Node name: by default it is “node” + network N° + node N°

this parameter is used only in case of configuration with spatial redundancy
Internal name resolver: allows to start the DNS service on the CS.
Answer yes only in case of configuration with spatial redundancy
122
Management of CPU A (cont.)
Ethernet interface setup

============
CPU name? xa001001
CPU address? 10.1.1.1
Name used when the CPU role is MAIN? xma001001
Address used when the CPU role is MAIN? 10.1.1.3
CPU redundancy setup

============
Twin CPU name? xb001001
Twin CPU's address? 10.1.1.2
Network mask? 255.255.0.0

The setup has been correctly achieved.
Security
====
Do you want to enhance security (y/n, default is y)? n

Both CPU use the same name for main role function because they are within the same LAN and use the same main IP address.
123
Management of CPU A (cont.)
➨ 3.Local Ethernet interface

➨ 3.2. 'Update'
CPU name (default is xa001001)?
CPU address (default is 10.1.1.1)?
Network mask (default is 255.255.255.192)? 255.255.0.0
➨ 8.Routing setup
➨ 8.1 Default router setup
➨ 8.1.2 Add/Update
Default router name? router
The name you gave isn't in our hosts database. Do you want to add it
and so give the corresponding address? y
Default router address? 10.1.1.100

Until the release F2.500 you don’t see the question for managing Network mask so the default one is applied.
You have to manage it at the end of the full configuration.
Same for router management. You have to declare it after the full IP configuration.
124
Duplication System without Spatial redundancy

(CPU CS B)

OBJECTIVE:
◆ To describe the configuration of the CPU B in case of duplicated configuration without spatial redundancy
OmniPCX Enterprise – Spatial redundancy

125
Management of CPU B
Full IP configuration
➨ netadmin
Warning: for a specific setup please use menu mode (netadmin -m)
Do you want to erase the existing setup? y
X25 private network number? 1
Unique site number? 1
Warning: the node name must be unique.

Enter node name? node001001
Do you want to activate internal name resolver (y/n default is 'n')? n
Enter local CPU position (a or b) for duplicated configuration

or n for single CPU (default is 'n')? b

Node name: by default it is “node” + network N° + node N°

this parameter is used only in case of configuration with spatial redundancy
Internal name resolver: allows to start the DNS service on the CS.
Answer yes only in case of configuration with spatial redundancy

126
Management of CPU B (cont.)

============
CPU name? xb001001
CPU address? 10.1.1.2

============
Twin CPU name? xa001001
Twin CPU's address? 10.1.1.1
Network mask? 255.255.0.0

The setup has been correctly achieved.
Security
====
Do you want to enhance security (y/n, default is y)? n

Both CPU use the same name for main role function because they are within the same LAN and use the same main IP address.

127
Management of CPU B (cont.)
➨ 3.Local Ethernet interface

➨ 3.2. 'Update'
CPU name (default is xb001001)?
CPU address (default is 10.1.1.2)?
Network mask (default is 255.255.255.192)? 255.255.0.0
➨ 8.Routing setup
➨ 8.1 Default router setup
➨ 8.1.2 Add/Update
Default router name? router
The name you gave isn't in our hosts database. Do you want to add it
and so give the corresponding address? y
Default router address? 10.1.1.100

Until the release F2.500 you don’t see the question for managing Network mask so the default one is applied.
You have to manage it at the end of the full configuration.
Same for router management. You have to declare it after the full IP configuration.

128
Setup duplicated Call Server
PROCEDURE
OBJECTIVE
- To learn how to setup Call Server duplication
REFERENCE
- System Documentation CD-ROM: R6.X Custom System Documentation/Technical
documentation/system /call server/call server duplication
OVERVIEW
The "Call Server Duplication" service is used to improve the PCX's operational safety. Two Call
Servers coexist in the same PCX. One of them is active, it is said to fulfill the "Main" role. The other is
on hold, it is said to fulfill the "Stand-by" role. When the first one has failed, the second one replaces
it. The calls in progress are maintained, the calls currently being set up are interrupted.

129
PROCEDURE
1. Check Software lock with spadmin command

On the call server
Login mtcl
Command spadmin
Result ooo Reading string-file /DHS3bin/oneshot/mtcl/objects.US0 ...
ooo Reading string-file /DHS3bin/oneshot/mtcl/spadmin.dct ...
Display current counters ........................... 1
Display active file ................................ 2
Check active file coherency ........................ 3
Install a new file ................................. 4
Read the system CPUID .............................. 5
CPU-Ids management ................................. 6
Display active and new file ........................ 7
Display OPS limits ................................. 8
Display ACK code ................................... 9
Exit ............................................... 0
choice:
Entry 2
Result File version = 0
OXE version = 0110
Soft Key = 423b496e72a18eef3567
Cpu Id 0 = 0000BAD5
177-SIP users = 9999 (0)
178-4645 Voice mail engin = 1
179-4645 users = 400 (0)
181-OmniPCX Enterprise (1 = 1
182-4645 networking = 1
183-4645 additionnal lang = 5
184-Integrated gatekeeper = 9999
185-SIP Gateway = 9999
186-E-CS redundancy = 1
Remark:
186-E-CS redundancy = 1 (duplication = yes)

130
2. Set up IP configuration on e-CS A

On the call server
Login mtcl
Command netadmin
Result Warning: for a specific setup please use menu mode (netadmin -m).
Do you want to erase the existing setup (y/n default is 'n')?
Entry y
Result Do you intend to use IP/X25 on your system (y/n default is 'n')?
Entry n
Result Warning: the node name must be unique.
Enter node name (default is node000000) ?
Entry Node001001
Result Do you want to activate internal name resolver (y/n default is 'n') ?
Entry n
Result Enter local CPU position (a or b) for duplicated configuration
or n for single CPU (default is 'n')?
Entry a
Result Ethernet interface setup
========================
Entry xa001001
Result CPU address (default is 10.253.253.1)?
Entry 10.1.1.1
Result Network mask (default is 255.255.255.192)?
Entry 255.255.0.0
Result Name used when the CPU role is MAIN (default is xma000000) ?
Entry xma001001
Result The name you gave isn't in our hosts database. Do you want to add it
and so
give the corresponding address (y/n default is 'n') ?
Entry y
Result Address used when the CPU role is MAIN ?
Entry 10.1.1.3
Result CPU redundancy setup
====================
Twin CPU name (default is xb000000)?
Entry xb001001

131
Result Twin CPU's address (default is 10.253.253.2)?
Entry 10.1.1.2
Entry 255.255.0.0
Result Name used when the CPU role is MAIN (default is xma000000) ?
Entry xma001001
Entry 10.1.1.3
Result Default router setup
====================
Do you use an external gateway as default router (y/n default is n)?
Entry n
Result Security
========
Do you want to enhance security (y/n, default is y)?
Entry n
3. Set up IP configuration on e-CS B

On the call server
Login mtcl
Command netadmin
Result Warning: for a specific setup please use menu mode (netadmin -m).
Do you want to erase the existing setup (y/n default is 'n')?
Entry y
Result Do you intend to use IP/X25 on your system (y/n default is 'n')?
Entry n
Result Warning: the node name must be unique.
Enter node name (default is node001001) ?
Entry Press return
Result Do you want to activate internal name resolver (y/n default is 'n') ?
Entry n
Result Enter local CPU position (a or b) for duplicated configuration
or n for single CPU (default is 'n')?
Entry b

132
Result Ethernet interface setup

========================
Entry xb001001
Result CPU address (default is 10.253.253.1)?
Entry 10.1.1.2
Entry 255.255.0.0
Result Name used when the CPU role is MAIN (default is xmb000000) ?
Entry xma001001
Result The name you gave isn't in our hosts database. Do you want to add it
and so
give the corresponding address (y/n default is 'n') ?
Entry y
Entry 10.1.1.3
Result CPU redundancy setup
====================
Twin CPU name (default is xb000000)?
Entry xa001001
Result Twin CPU's address (default is 10.253.253.2)?
Entry 10.1.1.1
Entry 255.255.0.0
Result Name used when the CPU role is MAIN (default is xmb000000) ?
Entry xma001001
Result 10.1.1.3
Result Default router setup
====================
Do you use an external gateway as default router (y/n default is n)?
Entry n
Result Security
========
Do you want to enhance security (y/n, default is y)?
Entry n

133
4. Reference IP-MG declaration

On mgr
Select Shelf
Entry Shelf address: (for example: 1) (take the GD nearest the CS)
Reference: true
Action Press CTRL+v two times to validate the creation
Press CTRL+c as many time as needed to come back on main menu
Remark:
When the two call servers are not "seeing" each other, they both try to connect
to the reference e-MG, the one which succeeds becomes the Real Main and
the other one becomes the Pseudo Main (MAO not activated).
The reference e-MG shall be as close as possible from one e-CS (same switch).
If no reference Media Gateway has been declared, the Call Server with the
highest IP address becomes the "Real Main".
5. Call server role declaration on mao

On mgr
Select IP
Entry Preferred CS @IP (redundancy): (for example: 10.1.1.1)
Action Press CTRL+v two times to validate the creation
Press CTRL+c as many time as needed to come back on main menu
Remark:
Preferred CS @IP
Used In case of simultaneous start-up of both e-CS, the one whose IP address
is defined here will start as main.

134
Database cloning
PROCEDURE
Database cloning
OBJECTIVE
- To learn how to perform a database cloning
REFERENCE
- System Documentation CD-ROM: R.6.X System Documentation-> Functional documentation->
system services->call server duplication->management
OVERVIEW
The "Call Server Duplication" service is used to improve the PCX's operational safety. Two Call
Servers coexist in the same PCX. One of them is active, it is said to fulfill the "Main" role. The other is
on hold, it is said to fulfill the "Stand-by" role. When the first one has failed, the second one replaces
it. The calls in progress are maintained, the calls currently being set up are interrupted.
Issue 01 REF. ENTP0438C06TEUS.doc W.1

135
Database cloning
PROCEDURE
1. Maintenance
1.1 Check IP configuration on call server A

On the call server
Login mtcl
Command netadmin –m
Select 2. 'Show current configuration'
Result Your system hasn't any site number.
Private IP addressing space: no
Restricted internet accesses: no
Accept ICMP redirect: yes
Low dynamic ports range configuration : 10000 - 10499
There is no VLan configuration. No frame will be 802.1q-tagged.
node name : node001001
internal name resolver activated : no
========================
Netmask : 255.255.0.0
===============================================================
| Machine type| Local interface | Name | Address
===============================================================
| local | Ethernet | xa001001 | 10.1.1.1
| local main | Ethernet | xma001001 | 10.1.1.3
|==============================================================
====================
Netmask : 255.255.0.0
===============================================================
| Machine type | Local interface | Name | Address
===============================================================
| local | Ethernet | xb001001 | 10.1.1.2
===============================================================
Action Press ENTER
Press 0 to exit from netadmin menu
W.2 REF. ENTP0438C06TEUS.doc Issue 01

136
Database cloning
1.2 Check IP configuration on call server B

On the call server
Login mtcl
Command netadmin –m
Select 2. 'Show current configuration'
Result Your system hasn't any site number.
Private IP addressing space: no
Restricted internet accesses: no
Accept ICMP redirect: yes
Low dynamic ports range configuration : 10000 - 10499
There is no VLan configuration. No frame will be 802.1q-tagged.
node name : node001001
internal name resolver activated : no
========================
Netmask : 255.255.0.0
===============================================================
| Machine type| Local interface | Name | Address
===============================================================
| local | Ethernet | xb001001 | 10.1.1.2
|==============================================================
====================
Netmask : 255.255.0.0
===============================================================
| Machine type | Local interface | Name | Address
===============================================================
| local | Ethernet | xa001001 | 10.1.1.1
===============================================================
Action Press ENTER
Press 0 to leave netadmin menu

137
Database cloning
1.3 Validate autostart on call server B (standby)

On the call server
Login mtcl
Command swinst
Select 2 Expert menu
6 system management
2 autostart management
1 set autostart
Action Press ENTER
Press Q as many times as needed to leave swinst menu
1.4 Stop the telephone application on call server B (standby)

On the call server
Login mtcl
Command swinst
Select 1 Easy menu
7 stop the telephone
Entry Please confirm to stop the telephone: y

138
Database cloning
1.5 Copy the main call server database on to the standby one(call server B)
On the call server
Remark:
you must be logged on the call server where you want to copy the database. In
this case call server B which is the stand by call server
Login mtcl
Command swinst
Select 2 Expert menu
3 cloning & duplicate operations
1 CPU cloning
3 cloning database
Entry BACKUP DATA from 10.1.1.3 on LOCAL CPU mastercopy utility 1.0
Ethernet link is used for copy
Do you wish to copy the DATABASE AND ACCOUNTING (y/n): y
Do you wish to copy the VOICE GUIDES (y/n): n
Do you wish to copy the TRAFFIC HISTORY (y/n): n
Do you wish to copy the ACD CONFIGURATION AND STATISTIC FILES (y/n): n
Do you wish to copy the LINUX DATA (y/n, default n): n
Do you wish to START THE TELEPHONIC APPLICATION
at the end of the operation (y/n, default y): y
AT THE END OF THE OPERATION, THE TELEPHONIC
APPLICATION WILL BE STARTED AUTOMATICALLY
Continue the mastercopy (y/n)? y
Remark:
Be patient!

139
Database cloning
1.6 Check the good working of the duplication

On the call server
Remark:
You log on call server A
Login mtcl
Command Role -b
Result MAIN stand-by CPU state: ACTIVE
Remark:
Call server A is main and call server B is active in Stand by mode
Check the switching between call server A and call server B
Before using the next command, you can realize some calls in order to check
the transparency
Command bascul
Entry This command will cause a fast CPU switch-over.
The CPU is running in Main Role. If you perform a CPU switch-over,
this CPU will be shutdown.
Are you sure you want to perform a CPU switch-over (y/n)? y
Remark:
Call server A is in shutdown mode, call server B is main.
After call server reset, try the following command
Command Role -b
Result ACTIVE stand-by CPU state: MAIN
Remark:
Call server B is main and call server A is active in Stand by mode

140
e-CS Duplication
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to put into operation the call server duplication
MANAGEMENT
1. Start your second call server and manage both e-CS IP addressing.
2. Manage the reference e-MGD and the “call server role” on the first call server.
3. Perform a database cloning and start the telephone application on the second e-CS.
4. Through the maintenance commands, verify the state and role of each call server.
Test the “role addressing” feature.
5. Establish several calls and perform a call server switch over, what happens?
6. Disconnect the main e-CS from the IP network and use the different maintenance commands
to see the role of each e-CS and the devices connected to those e-CS.
7. Reconnect the e-CS , which one is rebooting?

141
e-CS Duplication

142
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
143
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
144
Speed dialing by range

OBJECTIVE:
◆ To describe the speed dialing numbers by range
Alcatel OmniPCX Enterprise – Speed dialing by range

145
Principles
Speed dialing by range allow to:

➨ Define for a same call prefix:
▼ Different numbers according to the calling set entity
▼ Different speed dialing numbers between nodes in network
➨ Define several call numbers for a same speed dialing

number
➨ Restrict access to some ranges according to the phone

feature class of service
➨ Modify automatically the out dialing numbering

▼ Use of overflow speed dialing n° and Timed overflow range N°
➨ Identify automatically calling number

Same as direct speed dialing numbers, this speed dialing numbers can be:
• barred
• Dialed by name
• Used to identify the calling (displayed name, type of call in VIP / Normal / Local)
• Used for automatic DISA substitution
• Used in ISDN Filtering key in Executive / Assistant set

146
Principles
Two types of speed dialing ranges in the system
➨ 1 range of direct speed dialing numbers
▼ This range can’t overlap the other ranges
➨ 400 range of speed dialing numbers by range
▼ The ranges can overlap the others
One user can only use 32 speed dialing ranges
➨ Use of a specific prefix Speed Dialing Area N°
▼ This prefix is followed by an index of speed dialing number in the

range
➨ The link between ranges is defined in the entity of the user

Reminder:
•Direct speed dialing numbers are common objects inside an ABC network.
•To each direct speed dialing prefix corresponds only one call prefix in the translator.
Ranges Overlapping allows to call the same number using two different prefixes. A same number can be used in different ways.
For easy to use reasons, this configuration must be reserved for specific needs.
The maximum size of the table of speed dialing numbers is 15 000 numbers.
The default size of the table is 4 000.

147
Example
Common ranges for all the entities

40 : Speed dialing prefix Phone feature COS . 0 Link Entity 1
Range 0 Speed Rights Prefix Real range of Direct Speed
41 : Speed dialing prefix
Dialing range of use Range spd dlg prefix dialing range
0 1 0 0
Range 1
1 1 1 1
42 : Speed dialing prefix 2 0 2 2
1st index: 0
Range 2 Length: 3000
3 0 3 3
… … … …
29 1 29 29
Range N° 0
30 1 30 30
31 1 31 31 1st index: 3000
Length: 100
Number Function Access Real Relative Real Number N° of digits: 2
dialed related Rights range Index Index sent
Range N° 1
40 99 Spd rg.0 YES 0 99 3099 00298143322
41 12 Spd rg.1 YES 1 12 3112 00155667000 1st index: 3100
42 38 Spd rg.2 NO 2 38 3238 00605040302 Length: 100
N° of digits: 2
Range N° 2
0298143322
1st index: 3200
ISDN
Set 31000 Length: 100
Entity 1
Phone feature COS0
N° of digits: 2
0155667000

In this example, the table of speed dialing number is build with 3000 direct speed dialing numbers.
Modify the size of ranges in a system it’s a sensitive operation, so it’s better to do it well at first.
Numbering Analysis:
1. Set 31000 dials number 4099
• The translator determines with prefix 40 that the call concerns range index 0, the number of significant digits is determined by
management of the range (here 2 digits). So, the translator is waiting for 2 supplementary digits to determine the location of
the speed dialing number in the range.
• The phone feature COS authorizes access to range 0.
• Entity set do the link between range 0 and the real range 0 in the table of speed dialing numbers.
• The end of the number determines the index of the speed dialing number in the range, here 99.
• The range 0 begins at real index 3000, the last index is then 3099.
• This speed dialing number contains the digits to dial, that correspond to the public number 0 0298143322.
2. Set 31000 dials number 4112
• The call concerns range index 1 (prefix 41).
• The phone feature COS authorizes access to range 1 and entity points to the real range 1.
• Index is 12, range begins at 1100, the number is found in index 3112 of the table.
3. Le Set 31000 dials number 4238
• The call concerns range index 2 (prefix 42).
• This range is forbidden in the phone feature COS, the call is not authorized.
• If the call was authorized, the number found would be index 3238.

148
Example
Different ranges according to the entity

40 : Speed dialing prefix Link Entity 1 Link Entity 2
Range 0 Prefix Real range of Prefix Real range of Direct Speed
Range spd dlg prefix Range spd dlg prefix dialing range
0 0 0 32
1 1 1 33
2 2 2 34
1st index: 0
3 3 3 35 Length: 3000
… … … …
29 29 29 61
Range N° 0
30 30 30 62
31 31 31 63 1st index: 3000
Length : 10
Number Function Access Real Relative Real Number N° of digits: 1
dialed related Rights range Index Index sent
Set 31000
Entity 1
0298143322
40 0 Spd rg.0 YES 0 0 3000 00298143322
Range N° 32
Set 32000
Entity 2 1st index : 3200
0605040302 Length : 10
40 0 Spd rg.0 YES 32 0 3200 00605040302 N° of digits : 1

Set 31000 is in entity 1, set 32000 in entity 2. The management of the speed dialing ranges is different for the two entities.
(from 0 to 31 for entity 1, from 32 to 63 pour for entity 2).
Numbering Analysis:
1.Set 31000 dials number 400
management of the range (here 1 digit). So, the translator is waiting for 1 supplementary digit to determine the location of
• The phone feature COS authorizes access to range 0. Entity 1 of the set do the link between range 0 and the real range 0 in
the table of speed dialing numbers.
• The end of the number determines the index of the speed dialing number in the range, here 0. The range 0 begins at real
index 3000, the last index is then 3000 (corresponds to public number 0 0298143322).
2.Set 32000 dials number 400
management of the range (here 1 digit). So, the translator is waiting for 1 supplementary digit to determine the location of
• The phone feature COS authorizes access to range 0. Entity 2 of the set do the link between range 0 and the real range 32
in the table of speed dialing numbers.
• The end of the number determines the index of the speed dialing number in the range, here 0. The range 0 begins at real
index 3200, the last index is then 3200 (corresponds to public number 0 0605040302).
This configuration allows for example to do a list of speed dialing number to call companies with users changing according to the
entity of the calling.
Example : Speed dialing number 400 = Company Smith
entity 1 is coming to attendant, entity 2 to sales, entity 3 to executive, etc…
Real ranges accessible by the same logical range (given by the prefix) must have the same number of waiting digits.

149
Example
Different ranges according to the node of the ABC network

40 : Speed dialing prefix 41 : Speed dialing prefix
Range 0 Range 1
Direct Speed 40 01 Number dialed 40 01 Direct Speed

dialing range Spd rg.0 Function related Spd rg.0 dialing range
1st index : 0 1 Relative Index 1 1st index : 0

Length : 3000 Length : 3000
3001 Real Index 3001
Range N° 0 0 0298143322 Number sent 0 0298143322 Range N° 0
1st index : 3000 1st index : 3000
Length : 100 41 12 Number dialed 41 12 Length : 100
N° of digits: 2 N° of digits: 2
Type : Network Spd rg.1 Function related Spd rg.1 Type : Network
12 Relative Index 12
Range N° 1 Range N° 1
1st index : 3100 3112 Real Index 3112 1st index : 3100
Length : 100 31018 Number sent 0 112 Length : 100
N° of digits : 2 N° of digits : 2
Type : Local Type : Local
Set 31000 Set 32000

ABC link
Node 2
Node 1

Set 31000 is on node 1, set 32000 on node 2.

The management of the speed dialing ranges is different for the two nodes. This range is locale on each node, this allows to have
different contents according to the node. The size and the position is broadcast in the network to maintain the coherency of the
network.
Numbering Analysis:
1.Sets dial number 4001
• The translator determines with prefix 40 that the call concerns range index 0. Following digits determine index of the speed
dialing number in the range.
• The type of range is Network, the content is the same in the nodes after audit and broadcast.
• The range 0 begins at real index 3000, the last index is then 3001 (corresponds to public number 0 0298143322).
2.Sets dial number 4112
The translator determines with prefix 41 that the call concerns range index 1. Following digits determine index of the speed dialing
number in the range.
• The type of range is Local, content is different in the nodes .
• The range 1 begins at real index 3100, the last index is then 3112.
• On node 1, it corresponds to internal number 31018.
• On node 2, it corresponds to public number 0 112.
This configuration is useful for emergency calls in network. If emergency exist on site, the speed dialing number will be forwarded to
local numbers. But, if there is no local emergency, it’s possible to forward to public numbers emergency.

150
Direct speed dialing management
PROCEDURE
OBJECTIVE
- To learn how to manage speed dialing by range
OVERVIEW
Create speed dialing ranges
Create several speed dialing numbers by range using mgr tool
Use speed dial by range overflow

151
PROCEDURE
1. Modify the Speed dialing numbers by range N°0

Application mgr
Path Speed dialing / Spd Dl Numbers by Range /
Action Review/Modify
Range Number 0
Action CTRL-V
Index for 1st speed dial number 1000
Length for speed dialing numbers 100
Number of Digits 2
Used in network + Local Node
Action CTRL-V
Note: Number of Digits: Number of digits to be dialled by the user (1, 2, or 3 digits). This number
must be coherent with the length of the range: - length of range x 10: 1 digit enough, -
length of range x 100: 2 digits enough, - length of range x 1000: 3 digits necessary.
Used in Network The choice is made in the menu:
- Network: the definition of the range is global on the network. The contained in this
range are the same for all the nodes.
- Local: the definition of the range is local to this node. The abbreviated numbers
contained in this range are locally defined to the node. The content of the network
ranges is automatically transmitted onto all the nodes (creation, modification, deletion).
The characteristics of the local ranges are transmitted onto all the nodes (index of 1st
abbreviated number, length...) to avoid the same range being local on one node and
network on another.

152
2. Modify the Speed dialing numbers by range N°1

Application mgr
Path Speed dialing / Spd Dl Numbers by Range /
Action Review/Modify
Range Number 1
Action CTRL-V
Index for 1st speed dial number 1100
Length for speed dialing numbers 10
Number of Digits 1
Used in network + Local Node
Action CTRL-V

153
3. Create a speed dialing Number by range with overflow

Application mgr
Path Speed dialing / Spd Dl Numbers by Range / Speed
Dialing Number
Action Create
Range Number 1
Speed Dialing No. 0
Call Number #0120201032000
Directory name Lopez
Directory First Name Jennifer
Call Restrictions – Barring + False
Overflow Range No. 0
Call Type + Normal
Timed Overflow Range No. -1
Can be Called/Dialed By Name + YES
Displayed Name
External DISA Dir.No.
Action CTRL-V
Overflow Spd Dl No. 0
Phone book Name (Dial by name)
Phone book First Name
Action CTRL-V
Note: Overflow Range No.: Is used to specify the overflow number to be called if the trunk group
used by the call number configured above is not available. Enter the number of the range in
which the overflow number is declared. -1 (no number) is the default value.
Note: Overflow Spd Dl No.: This parameter is only accessible if the Overflow Range No.
attribute is completed. Enter the number of the order of the overflow number in the overflow
range.
Note: In this example, if the T2 is busy, when you use this speed dial number, there is an overflow
to range 0 and speed dial n° 0 (but GSM number outgoing with T0).

154
4. Create a speed dialing Number by range

Application mgr
Path Speed dialing / Spd Dl Numbers by Range / Speed
Dialing Number
Action Create
Range Number 0
Speed Dialing No. 0
Call Number #0100675936700
Directory name Lopez
Directory First Name Jennifer
Call Restrictions – Barring + False
Overflow Range No. -1
Call Type + Normal
Timed Overflow Range No. -1
Can be Called/Dialed By Name + NO
Displayed Name
External DISA Dir.No.
Action CTRL-V
5. Manage the entity speed dialing Numbers Range

Application mgr
Path Entities / Entity Spd Dial Numbers Range
Action Review / Modify
Entity Number 1
Speed Dialing Area 0 0
Action CTRL-V
Note: Overflow Range No.: Is used to specify the overflow number to be called if the trunk group
used by the call number configured above is not available. Enter the number of the range in
which the overflow number is declared. -1 (no number) is the default value.

155
Note: Overflow Spd Dl No.: This parameter is only accessible if the Overflow Range No.
attribute is completed. Enter the number of the order of the overflow number in the overflow
range.
6. Create speed dialling area prefixes

Application mgr
Path Translator / Prefix Plan
Action Create
Number 2
Prefix Meaning + Speed Dialing Area
Action CTRL-V
Prefix Information 0
Action CTRL-V
Path Translator / Prefix Plan
Action Create
Number 6
Prefix Meaning + Speed Dialing Area
Action CTRL-V
Prefix Information 1
Action CTRL-V
7. Authorize the access to speed dial ranges

Application mgr
Path Classes of Service / Phone Features COS
Phone Features COS 0
Speed Dialing Area
Area 0 1
Area 1 1
Area 31 1
Action CTRL-V

156
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to set the abbreviated numbers by range.
MANAGEMENT
1. Manage the abbreviated number range 0 that uses the system indexes 1000 to 1099
Manage the outside number “#0x202yy3z000” in the abbreviated number 0 contained in it.
2. Manage the abbreviated number range 1 that uses the system indexes 1100 to 1109
Manage the outside number “#0x202yy3z001” in the abbreviated number 0 contained in it.
3. Manage the entity speed dialing Numbers Range
4. Create speed dialling area prefixes:.
5. Authorize the access to dial speed ranges.

157

158
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
159
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
160
Alarms retrieval

OBJECTIVES:
◆ To describe the different type of alarms
◆ To describe the different solution to retrieve alarms
Alcatel OmniPCX Enterprise – Alarm retrieval

161
Alarms retrieval
topology
Example remote system

maintenance
terminal
External
Alarm
Alarm
center
ISDN
Computing
Alarm
RMA set
call
CPU
External Alarm
Alarm
RMA incident
ABC Link
ACT 0 ACT 0 system
Power supply LAN

ACT 1
Node 2 Node 1
Alarm
set

In this example:
• Two type of alarms sources are used:(message system and dry contact)
• Tree different type of signaling are used:(alarm set, contact alarm and remote call through ISDN)
Different cases can appear:
• if we lost the power supply on node 2 a external alarm is generated by a dry contact.
Automatically incident system will be transmitted through alarm sets on node 2 and 1.
• In case of computing trouble a external alarm can be generate as well by a physical contact in order to transmit trough ABC
link incident system to the alarm center.
•In case of media-gateway trouble the RMA or e-RMA feature can be used to contact a remote maintenance center through external
link.

162
Alarms retrieval
Alarm generation
Different type of alarm generation:
➨ External alarm connected to a analog equipment
➨ Alarm set
➨ CPU alarm relay
➨ Report system messages to an RMA system.

The alarm relay can be present on different board such as INT,RT2,LIOB,GD.

Each system message can be associated with an RMA operation or ringing of an alarm station.
Four RMA actions are available (0 to 3).

163
Alarm retrieval
External alarms
The OXE allows a user to be notified of an external event
➨ The “external alarm” feature allows to use a sensor (fire,

temperature, intrusion, etc.), generating a dry contact, to be
connected to a Z interface
➨ This analog Set is associated to a routing table allowing to define

the severity level of the message. A range of system messages
indexes is reserved for this feature
➨ When the contact opens or closes (depending on its

configuration), a system message is emitted
➨ Dry contacts can be present on remote site

▼ peripheral ACT shelf: IP,INTOF, RT2
▼ ABC-F sub-Network using incident centralization

(1) A range of system messages indexes is reserved for this feature and offers four levels of severity(1)
(2) This range is split as followed:

- 1101 to 1124, severity level: warning
- 1125 to 1149, severity level: minor
- 1150 to 1174, severity level: major
- 1175 to 1200, severity level: critical
In fact, two system messages are emitted:
- The event: faulty status (incident 11xx followed by the MCDU of the external alarm)
Á 17/05/04 11:16:37 001006M|05/01/0/064|=2:1150= External Alarm: **ALARM Sensor1
- And the comeback to the “default status” (incident 1099 followed by the MCDU of the external alarm)
Á 17/05/04 11:16:39 001006M|05/01/0/064|=5:1099=End of External Alarm: ** ALARM Sensor1

164
Alarm retrieval
Alarm set
Alarm set configuration

➨ alarm sets are used to inform the system administrator or
any other designated person, that one or more particular
incidents have occurred
To create an alarm set, you must comply with the following

procedure:
➨ Create an analog or UA type of set in the usual way
➨ Assign the system message(s) and Table Id in the “Incident
Filter” object
➨ Declare the predefined set as an alarm set

To display incidents (for example, on a 4035 set)

When an alarm occurs the set is rung (ringing cadence is managed by tone 64) and the LED flashes. On off-hook, the display shows
the number of the corresponding table:
Several actions can be performed:

End: on hook without acknowledging, the LED continues to flash,
Scroll: view incident data:
Cancel: acknowledge the alarm.

Note: if the set is not off hooked, it stops ringing when timer n° 25 elapses but the LED continues to flash. To view and acknowledge
the alarm, the set feature prefix of the Alarm Consultation set must be dialed.

165
Alarm retrieval
Cpu alarm relay and RMA action
CPU Alarm relay
➨ The CPU alarm relay is used to indicate that a problem has

occurred. Several incident numbers can be allocated to relay
activation and several other numbers to its deactivation.
➨ alarm action parameter: (None, Alarm set or Alarm Up)
RMA Action
➨ A RMA action can be as well associated to a incident filter

➨ RMA action parameter:
(None, Action 0, Action 1, Action 2, Action 3)

Example:
•The incident 2826 / Link_status_down (indicating that a link is cut off), to trigger the relay.
•The incident 2827 / Link_status_up (associated "cleared" incident, indicating that the link has been reestablished), to deactivate the
relay.
The alarm relay can also be manually activated or deactivated using the alarmrel command.

166
External Alarms configuration
PROCEDURE
External Alarms configuration
OBJECTIVE
- To learn how to manage External Alarms
REFERENCE
- System Documentation CD-ROM: R6.XCustom system documentation/Technical
documentation/maintenance/system services/management of system messages
OVERVIEW
External alarms using incidents management allow to centralize information generated by a dry
contact connected to a analog interface.
Incident system management is not describe in this procedure. For more explications Consult the
system documentation if necessary.
In this example, we will used a 3n021 SET associated to the phone Feature COS 1. The
modification of the set state will generate two incidents: one for the faulty status (incident 1190)
and another one for correct status (incident 1099) with a critical severity.
In addition to these incidents, the system message should indicate the notion “Sensor N°1”.

167
External Alarms Configuration
PROCEDURE
1. Analog set creation used as dry contact

Application mgr
Path /Users/
Action Create
Directory number 3n021
Name Sensor
Surname N°1
Set type analog
Phone Feature COS 1
Routing table 90
Action CTRL-V
Ext. Alarm Equipment Alarm On Opened Loop
Action CTRL-V
2. Management of phone Features COS

Application mgr
Path /Classes of service/phone features COS
phone features COS 1
Action CTRL-V
Routing Mode At Off-hook External Alarm
Action CTRL-V
3. Check under mtcl account the messages reception

Application Incivisu - t
Action Check the faulty and correct status reception
Off-hook 1:1190=External alarm : ** Sensor N°1
On-hook 5:1099=End of external alarm : ** Sensor N°1

168
Alarm Sets configuration
PROCEDURE
OBJECTIVE
- To learn how to manage an Alarm Sets
REFERENCE
- System Documentation CD-ROM: R6.XCustom system documentation/Technical
documentation/maintenance/system services/management of system messages
OVERVIEW
A alarm set (4035 set type) will be used to inform the system administrator that a particular incident
system have occurred (ex:2042 = loss of board coupler).
In this example, we will used a 3n000 SET, the table ID N°1and and a Alarm Consultation prefix
available in the numbering plan (example ## or 571).

169
Alarm Sets Configuration
PROCEDURE
1. Matching Alarm number and table number

Application mgr
Path /Applications/Incident manager/Incident Filter
Review / Modify Review / Modify
Incident number 2042
Action CTRL-V
Table ID 1
Action CTRL-V
2. Declaring the alarm set

Application mgr
Path /System/alarm set
Action Creation
Table ID 1
Alarm Set Dir.No 3n000
Action CTRL-V
3. Declaring Alarm Consultation prefix

Application mgr
path /translator/Prefix Plan
Action Creation
Number 571
Prefix Meaning Set Feature
Set Feature Alarm consultation

170
4. Check the right to used the Alarm consultation Prefix

Application mgr
path /translator/Prefix Plan
Action Review/modify
Phone Features COS 0
Action CTRL-V
( In Set Features parameters )
Alarm consultation 1
Action CTRL-V

171
Alarm Sets Configuration

172
Alarm set and external alarms
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to manage an alarm set and an external alarm
MANAGEMENT
1. Create a filter in the incident so that the loss of a coupler generate an alarm and rings the
extension 3n000 (UA phone)
2. Reset a coupler on the system, and verify that is rings the alarm set you defined
3. Create an external alarm extension number 3n021, when an alarm occurs, this should ring
the extension 3n100 as well, for alarm and end of alarm.
To test this, connect an analog phone to the Z circuit.

173
Alarm set and external alarms

174
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
175
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
176
IP Media Gateway signaling backup

OBJECTIVE:
◆ To describe the IP Media Gateway signaling backup
Alcatel OmniPCX Enterprise – IP MG Signaling Backup

177
Summary
Overview
Signaling backup establishment and release
IP Media gateway local calls
Inter IP Media Gateway calls
External calls
With IP phones
In duplicated configuration
Restrictions
With Crystal CPU


178
Overview
Link between CPU-CS and IP Media Gateway handled by

IP network
IP Media
IP server
Gateway
➨ IP Link Process Call Handling Rack Manager
IP Link IP Link Process
UDP&IP UDP&IP
Data Link (DL)
➨ Data Link (DL)

Signaling Link
IP Media
IP Gateway
Network Rack Manager
IP Link Process
UDP&IP
Signaling flow between the Call server and IP MG

IP Link Process : On the call server, the Call Handling emits and receives signaling messages. Those messages are handled by the IP
Link Process. On the Media Gateway there is also an IP Link Process that receives signaling from Data Links and sends them to the
rack.
Data Link :It is an object within the IP Link Process. It translates standard signaling messages to IP packets that are send to the Call
Server. And conversely, it transforms IP signaling datagrams from Call Server to regular messages.
Rack Manager : It is a software process on the Media Gateway that routes regular messages toward interface card drivers.

179
Overview
Purpose
➨ Rescue the signaling link between IP server and IP Media

Gateway in case of IP network breakdown
Implementation
➨ IP Signaling Link Backup (IPSLB)
▼ Mechanism establishing temporary connection to replace the regular

IP link
▼ Communication channel open through the public network
▼ Use of GD internal modem (DSP1)
▼ Can not be used for the voice transport

The IP Signaling Link Backup concerns only signaling between Call Server and Media Gateways.
It does not take into account communications between Call Server and any other kind of IP devices such as IP-Phones.
Be careful, IP Signaling Backup does not create an alternative link for the voice to be transported.

180
Overview
IPSLB principle
"Rescuer" CPU-GD
DSP1: GD internal
modem
IP Network
Public Analog or ISDN IP Server
Operator boards
Broken IP
Signaling Link
Signaling Link
Backup

An auxiliary Media gateway (rescuer) , in service and visible from the call server is used as a relay between the lost Media Gateway
and the Call Server.
Between the lost Media Gateway and its rescuer, a signaling channel over the public network is established and a new Data Link over
IP is created between the rescuer and the Call Server.
All IP packets which transport signaling between the Call Server and the Media Gateway are redirected onto the new backup link.

181
GD internal modem
This modem is located in the DSP1 of each GD
It is compatible with V8, V34 and V42 protocols
Restrictions
➨ Each IP Media Gateway can only use its local modem
➨ Only one connection at a time

V8: Signaling protocol which allows the determination of each side modem capabilities (auto-negotiation).
V34 :Synchronous or asynchronous full duplex transmission (28800b/s).
V42 : Error control protocol

182
Signaling backup establishment
On call server side

➨ The IP Signaling Link (with IP MG) is down
▼ The IP MG is considered out by the IP server after a certain timer
✦ The stations and interface boards are not accessible (frozen)
✦ Expansion racks are lost
▼ After a timeout (20s by default), the Call server launches the IPSLB
process
✦ Look for "free modem access" to the public network
✦ Call of the lost IP MG
✦ Trunk used by the backup is marked busy
Unusable for external calls
▼ As soon as the backup is established, all IP MG interface boards are

reset
✦ The established communications of the main rack are released
➨ If the backup is not established or if the regular IP link does

not come back
▼ The complete IP MG is lost (reset of GD)

Free modem access : a modem not used by any other application and located on a Media Gateway with a free access to the PSTN
The call of the lost Media gateway will only be performed from an authorised Media gateway ( boolean "eMG Rescue" in
management )
There are 3 backup establishment attempts. If no link comes up (neither backup nor regular IP link), the IP-MGD resets after 20
minutes.

183
Signaling backup establishment
On IP Media Gateway side
➨ The GD also detects that the IP Signaling Link is down

▼ It expects to receive an incoming call on a free trunk or free access
➨ Both digital and analog lines can be used for the signaling
backup
▼ On ISDN access, a dedicated DID number is needed to connect the
call to the local internal modem
✦ Number specified in management and transmitted to the GD at
initialization
▼ On analog lines, any incoming call is accepted and connected to the

local modem

During the transition time, any incoming call is considered by the Media Gateway.
Analog trunk incoming calls are systematically considered as IP Signaling Backup calls.
Digital trunk incoming calls are discriminated, only the one whose DID number corresponds to an IPSLB establishment will be
accepted.

184
Signaling backup release
When IP network comes back to normal
➨ The IP signaling link is re-established
➨ If this one is persistent

▼ The Signaling Backup is released
✦ Telephone line and modem used by IPSLB are released
▼ The Call Handling is informed that IP MG has returned to a normal

state
➨ The transition is transparent for the users, no reset of the

GD
▼ The established communications are maintained


185
IP Media Gateway local calls
Calls within IP Media Gateway are still possible
IP Server Public
Operator
Backup
signaling
IP
Broken IP
Signaling Link
Voice


186
Inter IP Media Gateway calls
Communications with rescued IP-MG are forbidden
Public
IP Server Operator Backup
Signaling
Signaling IP network
core Shadow IP
Link network
IP MG2
gap IP MG1
Voice flow
Impossible
Forbidden
call
call

Be careful : The signaling backup establishment needs another Media Gateway (reachable by the call server) with e free modem
access. This one has not been drawn upon (backup signaling link directly on call server) but it is mandatory, see slide 10.
If the IP network is split into two separate networks, Media gateways can either be located on the same "IP network part" as the call
server (IP network core on the drawing) or separated from the call server by the "IP gap" (shadow IP network).
When this happens, it is impossible to determine if media gateways can see each other (because of IP protocol routing complexity).
As a result, all communications between two end-users of different Media Gateways are forbidden as soon as the active signaling is
the backup one. Nevertheless, an end-user can still establish the communication by performing a regular external call through
PSTN/ISDN.
In the above example, the IP link between IP MG1 and the call server is broken, so the IPSLB is established Same thing for IP MG2.
But the call server doesn't know if IP MG1 and IP MG2 can reach each other through IP (there is maybe also a gap between IP MG1
and IP MG2), so communications between those two Media Gateways are forbidden.

187
External calls
Same principle
Possible
External call
Backup
Signaling Public
IP Server Operator
IP IP
gap
① Impossible
② External call

Be careful : The signaling backup establishment needs another Media Gateway (reachable by the call server) with e free modem
① : If two Media Gateways are not located on the same part of the "gap", the voice channel can not be established , so the external
call is impossible.
This problem should not occur if there are outgoing trunks on each part of the gap ( the best case is accesses on each Media
gateway) because the Call Handling will select a trunk in the same unbroken IP sub-network.
② : As the inter Media Gateways call are forbidden, it is impossible for a end-user located on a rescued IP-MG to use a trunk on
another Media Gateway for an external call.
Note: the rules are the same for incoming calls, the called set and the trunk group have to be located on the same Media Gateway.
The trunk group should not be segregated with many interfaces located on different Media Gateways. It is the same for the signaling
backup establishment, if the trunk group is segregated, the public network will decide itself on which Media Gateway to route the call.

188
IPSLB and IP-
IP-Phones
The IP-Phones can be associated to a IP Media Gateway
➨ In this case, IP-Phones signaling is encapsulated in GD

signaling link
Use of IP domains
➨ It is possible to secure an IP domain through IPSLB of the IP-

MG
▼ The IP-Phones belonging to an IP domain and attached to a IP Media
Gateway with IPSLB are also rescued
✦ Same behavior as a normal set (UA,Z)

If an IP-Phone is inside an IP domain and the Media Gateway it is attached to use an IP Signaling Link Backup, this IP phone reacts
exactly like a non IP phone of that particular Media gateway (UA phone or Z phone).
This is to say that, Media Gateway internal communications are possible; external communication abilities depends of trunk
availability; and inter Media Gateway communications are forbidden.
Note : IPSLB can not create a backup link directly to a single IP phone.

189
IPSLB and IP-
IP-Phones
The IP Phones attached to an IP MG with IPSLB are rescued

(IP domain management)
Backup Public
Call Server
Signaling Operator
Unreachable IP
phone
Call Server
IP domain
Backup
Signaling for IP
Phone
IP Domain
Reachable IP with IPSLB
phone
IP Domain
Broken IP link without IPSLB
Reachable IP
phone

Be careful : The signaling backup establishment needs another Media Gateway (reachable by the call server) with a free modem
To avoid some routing problems when IP Signaling Link Backup is working, it is strongly recommended that each "rescuable" Media
Gateway have particular IP domain.

190
IPSLB and duplicated configuration
When the IP network is down between the two CPU-CS
➨ Both CPU-CS are active (Main)
IP Signaling Link Backup won't be established on a IP

Media gateway which is already exchanging signaling
IPSLB not
established
IP Server
Main
X Public
Operator
IP Server
Standby
IP network IP network Main
IP Signaling
Link

Be careful : The signaling backup establishment needs another Media Gateway (reachable by the call server) with a free modem
The IP Signaling Link Backup establishment is slower that call server duplication mechanism.
Thus, when the call server's call arrives on the Media Gateway, if this Media Gateway already has a new IP signaling link then the
Media Gateway refuses a backup link.

191
Restrictions
IPSLB is not able to secure Remote ACT over IP (INTIPB)
The external access used to establish the backup has to be

located on the main rack of the IP Media Gateway
In the case of ISDN access, the media gateway has to be

synchronized on this access.
➨ The priority of maximum synchronization for an IPMG is
200
▼ Creation of one synchronization domain
Because IP LINK with the call server is broken down,the
CPU-GD has to conserve its IP address in case of backup
➨ IP address attributed has to be in static mode


192
With Crystal CPU
Signaling Backup on configuration with Crystal CPU

(CPU7, CPU6s2, CPU5s3)
➨ Signaling link with IP devices (IP-Phones, ACT MG) handled

by physical INTIPA boards
▼ Does not offer backup service
➨ IPLINK activation for backup purpose
▼ IP MG, and IP-Touch are linked to IP Link by default
▼ Other IP devices are linked to INTIPA (physical one)
➨ No ACT MG signaling link backup

The system does not need IPLink in normal operation since IO1 (or IO2) and INTIPA boards are present. On the other hand, as we
know, INTIPA board does not offer the backup service, it is only available in the IP Link. Therefore, it is necessary to activate the IP
Link even if INTIPA boards are present.
Only rescuer Media Gateways need to be tied to IP Link in order to use it to set up a backup link with the rescued Media Gateway
when necessary, they are forced to be tied to the IP Link,while other Media Gateways and remote ACT are tied to INTIPA boards.

193
With Crystal CPU
Signaling link with call server on CPU5/6/7
Main Rack
IPLink
Call Server
Rescuer
Media Gateway
INTIPA INTIPA
Act-MG
IP Network INTIPB
Rescuable
Media Gateway Media Gateway

A Media Gateway can be linked to an INTIP A (system configuration)

A Media Gateway defined as « Rescuer » will be tied to the IP Link started on CPU5/6/7 and not to the physical INTIPA.

194
With Crystal CPU
Backup signaling flow with Call Server on CPU5/6/7
Main Rack
IPLink
Call Server
Rescuer
Media Gateway
INTIPA INTIPA
Act-MG
Public INTIPB
Operator IP Network
Rescuable
Media Gateway Media Gateway

When the signaling link breaks down for a given rescuable Media Gateway, the similar process as with Aspen type CPU (CPU-CS) is
applied to establish a backup link.

195
Signaling backup process with Crystal CPU (1/2)
Signaling link loss
➨ In case of IP signaling link loss, after « UDP lost » timer, call

handling tries to switch to another INTIPA
Switching to another INTIPA

➨ If unsuccessful, the MGD is set out of service by CH
➨ After MAO timeout, CH launches the backup link process
Backup link establishment
➨ CH finds a free modem on rescuer IP MG and establishes the

backup through PSTN
➨ At this step the rescued GD is tied to IPLINK as for the signaling

backup with CPU-CS and Appliance Server

The CPU shares the signaling traffic between the INTIPA boards

196
Signaling backup process with Crystal CPU (2/2)
IP network recovery
➨ During backup mode, the IP network is sensed (Delay

between TFTP request in MAO)
➨ Once IP network is recovered, the «signaling link switch

process» is launched
Signaling link switching from IPLINK to INTIPA
➨ INTIPA board search (depending of IP Domain, signaling

load of the board)
▼ If no board is found, the rescued GD stays on IPLINK
▼ If a board is available, the GD connects to this one


197
Defense with Crystal CPU
Case of INTIPA failure for a rescuable GD
➨ The IP network is still active
▼ If the call server can still “reach” this GD(1)
✦ The backup process is not started
✦ The CH connects directly the GD to the CPU IPLINK process
➨ The IP network is out of order too
▼ The Call Server can not “reach” this GD (via any INTIPA board(2))
✦ backup process is started
➨ A message is send (0423)

Le Call Server tries to find an active Physical INTIPA board. In the opposite case, it will use its own virtual INTIPA board to establish
the signaling with the
CPU-GD
Physical or fictive INTIP board

198
IP MG signaling backup
PROCEDURE
OBJECTIVE
- To learn how to manage IP MG signaling backup
REFERENCE
- System Documentation CD-ROM: R6.1Custom system documentation/system services/signaling
link backup
OVERVIEW
Initial state of the system: 2 IP MG must be managed.
MG 1 will be rescueable and MG 2 rescued

199
PROCEDURE
1. Management of the rescueable IP MG

Application mgr
Path /Shelf/ Board
Shelf address 1
Board Address: 0
EMG rescue + Yes
Action CTRL-V
Note: The modem of the GD 1 is now in the pool of backup modem
2. Management of the rescued IP MG

Application mgr
Path /Shelf/Board /Signaling link backup
Shelf address 2
Board Address: 0
Action CTRL-V
Backup call number #0n202CL13n000
Backup address
Shelf 2
Board 4
Terminal 0
Signaling link type + T0
Number of expected digits 10
Action CTRL-V
Note: Backup call number: n : System N°, CL : Classroom N°. * The backup call N° may be any
DID number (this public DID number can be used by a set or not).
Note: Backup address: * You must specify thanks to the backup address on which physical access
the call of signaling backup will come in for the T0 remote access: 2-4-0

200
3. Management of access priority of ISDN accesses

Application mgr
Path /Shelf/ Board / Digital access
Shelf address 1
Board Address: 2
T0/T2 Access No. 0
Action CTRL-V
Synchronization priority 200
Action CTRL-V
Shelf address 2
Board Address: 4
T0/T2 Access No. 0
Action CTRL-V
Synchronization priority 200
Action CTRL-V
Note: The GD must be synchronized on the public access

201
4. Management of backup of IP Phones

Association of signaling backup of IP Phones with the rescuable GD. When the remote GD will
be rescued IP phones will stay in service because they will be driven by the GD instead of the
virtual INTIPA.
Application mgr
Path /IP/ IP domain
Action Create
IP domain number 1
Intra domain coding algorithm + Default
Extra domain coding algorithm + Default
Domain max voice connection -1
IP quality of service 0
Contact number:
Action CTRL-V
Voice Services broadcast + YES
Domain type + IP
Action CTRL-V
Note: This IP domain is required for association of IP phones on the rescueable GD.
Path /IP/IP Domain / IP domain address
Action Create
IP domain number 1
IP Address low 10.CL.n.30
IP Address high 10.CL.n.39
IP NetMask: 255.255.255.0
Action CTRL-V
IP domain number 1
IP Address low 10.CL.n.40
IP Address high 10.CL.n.44
IP NetMask: 255.255.255.0
Action CTRL-V
Note: IP addresses of remote GD and IP phones are allocated to IP domain 1. IP Phones and
remote GD belong to this domain.

202
Path /IP/IP Parameters

IP Phone signaling on eMGD + True
Action CTRL-V
Note: IP Phones are associated to the GD for signalling
5. In case of CPU crystal

Application mgr
Path /System / Other System Param./ System Parameters
GD linked with a real INTIPA board + False
Action CTRL-V
Path /System / Other System Param./ System Parameters
IPTouch IP on real INTIPA board + False
Action CTRL-V
Note: GD linked with a real INTIPA board: This attribute is used to return to a configuration where
the GD boards are linked with a real INTIPA board (as in the older versions). NO (default
value): the GD boards are linked with a fictitious INTIPA board(IP_LINK). YES: the GD
boards are linked with a real INTIPA board.
Note: IP Touch IP on real INTIPA board: IP-Touch IP set connected to a real INTIPA board. With
this attribute, it is no longer possible to connect an IP-Touch IP to a board in an ACT4400
other than a CPU. NO (default value): the IP-TOUCH IPs are connected to the fictitious
INTIPA board (IP_LINK) or GD/GA if the set has the appropriate rights. YES: the IP-TOUCH
IPs are connected to a real INTIPA board or an LIOx orGD/GA depending on their rights
(as for a standard Ipp).

203
6. On IP Phones
Indicate GD IP address as TFTP server in the static IP configuration of IP phones.
When the GD is connected trough IP it sends in lanpbx.cfg file the CS IP address otherwise in case of
connected backup link it sends his own IP address
7. Reset the IP Media Cateway

Application Under mtcl
Action Command : < rstcpl 2 0 >
Note: The GD must be reset so as to take into account modifications caused to the management
of the backup and IP domain
8. Check that all boards are in service

Action Command : < config 1 >
Action Command : < config 2 >

204
9. Check the IP domain

Action Command : < domstat >
Action Command : < Display one Domain Devices :7 >
Action Command: < Enter Domain Id:1 >
-------------IP couplers defined in domain 1 IP_REMOTE-------------
+--------+--------+-------+-----------------------+-----------------+
| Type | Cr/Cpl | Neqt | Mac Address | Ip Address |
+--------+--------+-------+-----------------------+-----------------+
| GD| 2/ 0 | 5194 | Unused | 10.42.1.40 |
+--------+--------+-------+-----------------------+-----------------+
----------------------IP Terminals in domain 1 IP_REMOTE --------------------
+--------+--------------+--------------------+-+-----+---------------+----+
| QMCDU | Name | Mac Address | |Neqt | Ip Address |Type|
+--------+--------------+--------------------+-+-----+---------------+----+
|36000 |IP1 |00:80:9f:3b:08:e5:00|V|01151| 10.42.1.30 | V1 |
+--------+--------------+--------------------+-+-----+---------------+----+
In the single column
V: means the channel is valid
-: means the channel is not valid
Note: The remote GD and IP Phones belong to the same domain .
9.1 Check signaling link for IP phones in case of CPU crystal

Action Command: < ippstat >
Action Command: < Display all IP Phones connected on a board : 12 >
Action Command: < Cristal Number : 2 >
Action Command: < Coupler Number : 0 >
coupler GD cr 2, cpl 0, Ghost Eqt 5194
+--------+--------------+--------------------+-+-----+---------------+----+
| QMCDU | Name | Mac Address | |Neqt | Ip Address |Type|
+--------+--------------+--------------------+-+-----+---------------+----+
|36000 |IP1 |00:80:9f:3b:08:e5:00|S|01151| 10.42.1.30 | V1 |
+--------+--------------+--------------------+-+-----+---------------+----+
In the single column
S: means sig. channel is supported by this board for these Ip phones
V: means voice channel is supported by this board for these Ip phones
B: means both channel is supported by this board for these Ip phones
Note: The remote IP Phone is linked to the remote GD for signaling.

205
10. Simulation of cut between remote and local LAN network

Disconnect the link between local IP network and the remote GD. It will take few minutes for
backup link setting.
Action Command: < config 2 >
+-------------------------------------------------------------------+
| Cr | cpl| cpl type | hw type | cpl state | coupler ID |
|----|----|------------|-----------|--------------|-----------------|
| 2 | 0 | GD |---------- | IN SERVICE | NO PCMS CODE |
| 2 | 1 | UAI 4 |---------- | IN SERVICE | NO PCMS CODE |
| 2 | 2 | PRA T2 |---------- | IN SERVICE | NO PCMS CODE |
| 2 | 3 | SLI 4 (Z) |---------- | IN SERVICE | NO PCMS CODE |
| 2 | 4 | MIX 2/4/4 |---------- | IN SERVICE | NO PCMS CODE |
+-------------------------------------------------------------------+
--- Inter Crystal Topology ---
+--------------------------------------------------------------------------+
| CR | CPL Type Role Free/Tot Role Type CPL | CR |
|--------------------------------------------------------------------------|
| 02 | 00 - MGD (MAIN ) --- RESCUE --- ( INT_A) INTIPA - 01 | 19 |
|--------------------------------------------------------------------------|
Note: Check that the GD is rescued (rescue)

Action Command : < incvisu –t 10 >
Check incidents corresponding to backup link activation:
02/00/-/---|=3: 0419=Trying to establish to back up signaling link02/00/-/---|=3
:0417=The Media Gateway is rescued by the Media Gateway (6)

206
11. Re-establishment of the link between the 2 LAN networks

The network links is back. It will take 1’ to release the backup link.
Action Command: < config 2 >
+-------------------------------------------------------------------+
| Cr | cpl| cpl type | hw type | cpl state | coupler ID |
|----|----|------------|-----------|--------------|-----------------|
| 2 | 0 | GD |---------- | IN SERVICE | NO PCMS CODE |
| 2 | 1 | UAI 4 |---------- | IN SERVICE | NO PCMS CODE |
| 2 | 2 | PRA T2 |---------- | IN SERVICE | NO PCMS CODE |
| 2 | 3 | SLI 4 (Z) |---------- | IN SERVICE | NO PCMS CODE |
| 2 | 4 | MIX 2/4/4 |---------- | IN SERVICE | NO PCMS CODE |
+-------------------------------------------------------------------+
+--------------------------------------------------------------------------+
|--------------------------------------------------------------------------|
| 02 | 00 - MGD (MAIN ) --- 8/8 --- ( INT_A) INTIPA - 01 | 19 |
|--------------------------------------------------------------------------|
Note: Check that the GD is not rescued

Action Command : < incvisu –t 10 >
Check incidents corresponding to backup link release:
02/00/-/---|=5:0418=The signaling link over IP is recovered

207

208
IP Media Gateway Signaling Backup

OBJECTIVE:
◆ To maintain the IP Media Gateway Signaling Backup
Alcatel OmniPCX Enterprise – IP Media Gateway Signaling Backup

Ref. ENTP0467M01TEUS Issue 01
209
bckdebug command
bckdebug command
(101)node1> bckdebug
----------------------------------------------------
CALL SERVER : Config tool for back up signaling link
----------------------------------------------------
Display the signaling link back-up information : 1
Display the information about neqt x : 2
List all used fictitious z : 3
List timers for back-up DL : 4
Display gd_loss for MG : 5
Modify timers for back-up DL : 6
Check management consistency : 7
Activate back up calls : 8
----------------------------------------------------
Quit this tool : 0
Enter your choice :


210
bckdebug command
Menu 1: Display the signaling link back-up information

INFORMATION FOR BACK UP LINK ON eMGD (2 0)
neqt_phant_cpl = 30159
********************************************
current status :SIG_BACKUP_ENABLE
this MG can be rescued :SIG_BACKUP_ENABLE
==> 0 attempt(s) of 3
********************************************
neqt of the calling fictitious z : -1
PROBLEM : can not access to information about neqt -1
********************************************
associated modem nulog : 5868
calls_attempts : 3
delay_between_calls : 120
delay_between_TFTP_req : 60
delay_for_resurection : 60
sig_type : 2
Back up call number : [1..30] = 0 0 2 0 2 0 3 1 0 0 0
Back up access on CPL_MIX : (2, 1, 0, 255)
********************************************
********************************************
=> Management consistency OK
********************************************

In this example, MG n°2 will be the rescued by MG n°1

211
bckdebug command
Before establishing the backup

Menu 3: List all used fictitious z
fictitious z (19, 4, 0) nulog = 7840 neqt = 850 associated to (1, 0)

fictitious z (19, 4, 1) nulog = 7841 neqt = 851 associated to (2, 0)
Menu 2: Display the information about neqt x
Enter the neqt : 851

INFORMATION ABOUT Z_MG NEQT 851 IN POSITION (19, 4, 1) :
********************************************
associated_cr : 2
associated_cpl : 0
associated_pos : 254
associated_ts : 126
emgd_neqt : -1
modem_state : MODEM_AVAILABLE (1)
ip_mode : 0
modem_use : BackupUse (2)
********************************************

Modem state: status of the modem. This can be:

•MODEM_AVAILABLE: idle state
•MODEM_OUT_DIALING: dialing
•MODEM_WAITING _FOR _INCOMING_CALL: in reception mode
•MODEM_CONNECTED: connected
•MODEM_DISABLE: out of service

212
bckdebug command
During back-up establishment

********************************************
associated_cr : 1
associated_cpl : 0
associated_ts : 126
emgd_neqt : -1
modem_state : MODEM_OUT_DIALING (3)
ip_mode : 0
********************************************
********************************************
associated_cr : 2
associated_cpl : 0
associated_ts : 126
emgd_neqt : -1
modem_state : MODEM_WAITING_FOR_INCOMING_CALL (4)
ip_mode : 0
********************************************

In this example, internal modem of rescuer GD (ACT 1) is dialing and calling internal modem of rescued GD (ACT 2)

213
bckdebug command
Once the link is established

********************************************
associated_cr : 1
associated_cpl : 0
associated_ts : 126
emgd_neqt : 30159
modem_state : MODEM_CONNECTED (2)
ip_mode : 0
********************************************


214
config command
config command
(5)xa000005> config 2
+-------------------------------------------------------------------------+
| Cr | cpl | cpl type | coupler state | coupler ID |
|----|-----|--------------|--------------------------|--------------------|
| 2 | 0 | MGD | IN SERVICE| NO OPS FILE |
| 2 | 1 | MIX244 | IN SERVICE| NO OPS FILE |
+-------------------------------------------------------------------------+
+-------------------------------------------------------------------------+
|-------------------------------------------------------------------------|
| 02 | 00 - MGD (MAIN ) --- RESCUE --- ( INT_A) INTIPA - 01 | 19 |
|-------------------------------------------------------------------------|


215
Timers
302 (TEMPO_MG_BCK)
➨ Timeout used by the call handler to know whether or not the
backup link has to be established immediately after the loss
of a Media Gateway
▼ 0: IPSLB never activated on the whole system
▼ 1: IPSLB activated as soon as the CH detects the loss of a MG
▼ other value: delays the beginning of IPSLB establishment after a MG
loss
➨ Default value: 5 s
305 (TEMPO_MG_REBOOT)
➨ A MG reboots after this time if it is impossible to start either
in IP mode or in rescue mode
➨ Default value: 20 minutes (should not be modified)


216
System Messages
System Messages
(5)xa000005>
000005M|01/00/-/---|=3:0419=Trying to establish the back up signaling link
000005M|01/00/-/---|=3:0417=The Media Gateway is rescued by the Media Gateway (6)
000005M|01/00/-/---|=5:0418=The signaling link over IP is recovered
000005M|01/00/-/---|=3:0420=Back up signaling link establishment failed(8)


217

218
Media Gateway Backup Link Management
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to manage the Media Gateway backup link signaling
MANAGEMENT
1. Declare the media gateway 1 as “rescuer”.
2. Manage the T2 synchronization priority (200) in both media gateways.
3. Declare the backup signaling in Media Gateway 3.
4. Disconnect GD 3 from IP network and verify establishment of the signaling backup.
5. Establish a call between extension 3x600 and extension 3x601.
6. Use the maintenance commands.
7. Reconnect the IP Link.

219
Media Gateway Backup Link Management

220
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
221
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
222
Trace tools

OBJECTIVES:
◆ To describe the trace tools for level 3 and application
◆ To describe the procedure to set up and stop a trace on "level 3" and "application"
Alcatel OmniPCX Enterprise Overview – Trace tools

223
Traces
Summary
Level 3 trace tools
➨ tuner
➨ trc
➨ mtracer
Level 3 trace procedure
Application trace tools

➨ actdbg
Application trace procedure


224
Traces
Traces on "Level 3"
➨ Use debug tools integrated in Alcatel OmniPCX Enterprise
Traces mechanism via "monitel"
➨ Traces are provided by "monitel" actor
➨ A dedicated buffer is used for the traces (500 max)
➨ 3 tools are available
▼ A configuration tool exists (tuner) (1)

▼ A tool is used to filter the equipment (trc) (2)
▼ The display is made by a dedicated server (mtracer) (3)

These trace tools are accessible under mtcl or mtch
(1) tuner Allows to manage the trace tool and select the message direction
(2) trc Allows filter management on the accesses to trace
(3) mtracer Message interpreter

225
Traces
Diagram
ACTOR ACTOR
monitel TEL
trc
Sending IPC
the signaling
to monitel
Thread execution
Messages
01011001 to handle
information deposit Execution of the
between monitel necessary code
circuit and TEL using
by a thread
and reply through
Reading of IPC port IPC ports an IPC port
by a thread and
demi-com assignment
mtracer
IPC
output buffer tuner actdbg


226
Traces
The "tuner" tool
The tuner tool allows to
➨ Configure internal filter around "monitel" actor
➨ Use monitel traces
➨ Use the debug functions


227
Traces
The "tuner" tool
Common options of tuner tool (1)
➨ Parameter Meaning
✦ km Stop the process mtracer

✦ -a Disable all the traces options
✦ clear-traces Empty all the traces in the buffer
✦ cpu Messages from CPU to coupler
✦ cpl Messages from coupler to CPU
✦ +at Active supplementary application traces
(linked to actdbg use)
✦ ...

(1) Regarding the system release, some options are not available with this wording (example: old releases)
Á To display the list of all the parameters available with tuner tool, you have juste to type tuner without any option
For example
tuner km Á tuner kill-matracer
tuner -a Á tuner all=off
tuner cpu Á tuner cpu-cpl
tuner cpl Á tuner cpl-cpu
…
Different options can be used in the same command line (with the same condition on or off)
tuner cpu cpl hybrid=on

228
Traces
The "trc
"trc"" tool
The trc tool
➨ When the "messages from CPU to coupler and from coupler

to CPU" option is set, "mtracer" provides (via "monitel") a lot
of information corresponding to the "level 3" (on all
accesses providing this type of service)
➨ If the traffic is high, the trace messages are heavy. The

reading and the understanding of the interesting messages
can become difficult
➨ The trc(1) tool is used to filter some accesses, to reduce the

flow of the information (around "monitel")

(1) The tool "trc" allows to apply one or several filters on accesses (physical [T2,T0], virtual [in case of compression] or hybrid [hybrid
links]), 8 at the maximum

229
Traces
The "trc
"trc"" tool
The command trc

➨ Parameter Abbreviation Meaning
init i Suppress all the filters

cr C Crystal number
cpl c Board number
us u US shelf
term t Equipment number
del D Suppress a filter (0, ..., 7)(1)
list-config lc displays the table of filters
➨ Example of filter on a T2 trunk group, shelf 0, board 2,

access 0
Á trc C 0 c 2 t 0

(1) The filter index is shown in the table of filters already set-up (given by the command trc lc)
To display the list of all the parameters, you have to type Á trc

230
Traces
"mtracer"
mtracer" process
The "mtracer" process is the server of traces for monitel
"mtracer" displays, and interprets (if needed), the trace

messages put into a buffer by "monitel" actor
➨ Main options
-a interpreted output tracing

-A interpreted hexadecimal output tracing
-a «number» interpreted output tracing, where the number is in a
message
-A «number» interpreted hexadecimal output tracing, where the
number is in a message

To have the list of all the parameters, you have to type Á mtracer -?
mtracer started ...

usage: mtracer
[-e] all tuner flags turn off and erase any pending message
[-n] without symbolic name (if cpu is not enough powerful)
[-N] numeric value everywhere
[-d] becomes a daemon process
[-1 trace-output-filename] [-2 extended-trace-output-filename].
[-s trace-files-size] [-f trace-files-number (< 100)]
[-a number_for_filtrer] [-A number_for_filter]
[-b number_for_filtrer] [-B number_for_filter]
...

231
ISDN Traces
"Level 3" trace procedure
How to start a "level 3" trace
➨ Stop mtracer tool

▼ tuner km
➨ Manage the wished filters on accesses

▼ trc i Á erase the previous parameters
▼ trc C ‘ cristal N°’ c ‘coupler N°’ t ‘ access N°’ (e.g. trc C 0 c 5) (1)
➨ Initialize tuner parameters:

▼ tuner all=off Á reset the previous flags
▼ tuner clear-traces Á empty the buffer of traces
▼ tuner cpu cpl Á trace in the both directions
➨ Start the trace interpreter (2)

▼ mtracer -a or mtracer -a ZABPQMCDU

It is necessary to stop mtracer process to obtain interpreted traces because this tool is started by default at the application start-up
(1) The filtering tool "trc" allows to configure 8 different filters
(2) If the trace is started using:

mtracer -a, the result of the trace corresponds to all the calls on the filtered accesses
mtracer -a ZABPQMCDU, (where ZAPBPQMCDU matches to a called or calling number)
the result of the trace corresponds only to the filtered number,
even if there are several calls on the different accesses

232
ISDN Traces
"Level 3" trace procedure
How to stop the trace
➨ Stop the tracer (1)

▼ press on delete key to stop the task
➨ Erase tuner tool parameters

▼ tuner all=off
▼ tuner clear-traces
➨ Erase trc tool filters

▼ trc i
➨ Restart mtracer process

▼ dhs3_init -R MTRACER (2)

(1) A trace can be started as background task by command mtracer -a & ( This way is not recommended for ISDN traces ) .
In this case we have to stop it by command kill-9 PID (Process Identification of the mtracer)
All the started traces use CPU time , and can cause slow down the system in certain cases
It is important to initialize correctly the trace tools to avoid running problems consequently .
(2) The mtacer process is started at the application starts up , it is necessary to restart as done by default .
To do that, dhs3_init process has to be used

233
Traces
Application traces
The tool actdbg
➨ Used to give supplementary information about options

selected during the use of an (or several) application(s)
This tool can used as a debug function
(activated by "tuner +at")(1)
➨ Several options (2)
✦ 4635: 4635 voice mail

✦ abca: blf+fms+voice mail+sbc
✦ acdv2: trace on CCd
✦ affope: displays on OP console
✦ ars: ars
✦ csta: call center
✦ cbn: call by name
✦ cnx: connections
✦ ...

(1) A trace using a filter on an application can provide a lot of information, if need, it is possible to trace the application(s) only for
one user. The equipment number of the set has to be used to set up this type of trace (details in the following page)
(2) To display the complete list of available options, type actdbg (without any option). In addition of the list of the options, the status
(on /off) of the different option is shown

234
Traces
How to start an application trace
▼ tuner km Á Stop "mtracer"

▼ tuner all=off Á reset the previous flags
▼ tuner clear-traces Á empty the buffer of traces
▼ tuner +at Á Active the application trace
▼ actdbg npd=on Á Example of filter(1)
▼ mtracer -a Á Start the trace
It is possible to filter an (or several) application(s) for a

specific set
➨ In the line corresponding to the application trace activation,

add the equipment number of the set
▼ tuner +at,5 Á here "5" corresponds to the set neqt

(1) It is possible to active several filters (on application) in the same trace (warning, this type of trace provides a lot of information)

235
Traces
How to stop an application trace(1)
➨ Stop the tracer

▼ press on ctrl c key to stop the task
▼ tuner all=off
▼ actdbg all=off
➨ Restart mtracer tool as before

▼ dhs3_init -R MTRACER

(1) It is possible to mix "level 3" (with different filters on "monitel" and with "trc") and "application" trace. Warning, this type of trace
provides an heavy flow of information
Á In this case, in the procedure to stop the trace, do not forget to disable the filters on accesses ( trc i )

236
Traces
Option
Traces Redirected in a file
➨ Using redirection when launching mtracer

▼ mtracer –a > /tmpd/my_trace
Trace launched in background
➨ Gives the possibility to keep the console port

available
▼ mtracer –a > /tmpd/my_trace &


237
Traces
Option
Turning traces automatically redirected into files
➨ Possibility to activate the trace in background

▼ Store the trace in a file
▼ When file reaches predefined limit, it will be closed
and a new one is opened
▼ When maximum predefined number of files
reached, the older is automatically erased
➨ Example
▼ mtracer –d –1 /tmpd/traces –s 100000 –f 5 &
▼ mtracer is run in turning traces in 5 files, each
maximum 1 GB. The files are called "traces-00" up to
"traces-04".


238
ISDN traces

OBJECTIVE:
◆ To describe the ISDN traces
Alcatel OmniPCX Enterprise – ISDN traces

239
ISDN Traces
Call principle
Principle of ISDN call setting up
➨ Outgoing call Incoming call

▼ Block mode Block mode
▼ Overlapping mode --
➨ Call proceeding
➨ Connect (optional)
➨ Disconnect (optional)
➨ Release

In case of one call to the network , 2 modes are possible

•Block mode: in case of professional trunk group seize ( or ARS seize )
•Overlapping mode: in case of professional trunk group seize without sub-address ( or ARS seize )
There is one information in the called system parameters: Overlap seizure , by default this parameter is not managed .
When this parameter is validated the number of level 3 message to public exchange is reduced ( we don’t use one information
message per dialed digit but only one information message for the whole number ) . This type of dialing is overlap dialing because
the called number is not send in the set up message .
Calls coming from the public network will be always in block mode.
The OmniPCX Enterprise is able to treat the incoming calls in overlapping mode.

240
ISDN Traces
Steps of establishment
Call set up in block mode
➨ The called number is sent in the SETUP message
▼ Send SETUP message with SENDING COMPLETE information

✦ The complete number is present in this message
✦ The call reference is indicated on 1,2 or 3 bytes ( CALL REF )
▼ Send information element in this message (EI)

✦ Call type (BEARER_CAPABILITY): 80 90 a3 = TEL
✦ CALLING_NUMBER
✦ CALLED_NUMBER
➨ The call reference is used by the system to link the messages

exchanged for one specific call
▼ The 80h value is added to the first call reference byte when the
message come from the distant
✦ Local: Call Ref = 3b 0c Remote: Call Ref = bb 0c

In VN4, using a T0 the CALL REF will be coded with 1 byte and 2 bytes for a T2, and respectively 2 or 3 bytes in ETSI.
_____________________________________________________________________________
| (257398:143320) 90: Send_IO1 (link-nbr=2, sapi=0, tei=0) :
| long : 63 desti : 0 source : 15 cryst : 0 cpl : 2 us : 8 term : 0 type a5
| tei : 0 <<<< message send : SETUP [05] Call ref : 01 c1
| SENDING COMPLETE
|______________________________________________________________________________
|
| EI:[04] BEARER_CAPABILITY (l=3) :80 90 a3
| EI:[18] CHANNEL (l=3) : a9 83 82 -> T2 : B channel 2 exclusive
| EI:[6c] CALLING_NUMBER (l=12) : -> 21 81 Num : 298143010
| EI:[70] CALLED_NUMBER (l=11) : -> 80 Num : 0155667000
| EI:[7d] HLC (l=2) :91 81
| EI:[7e] USER_USER (l=1) : 04
|______________________________________________________________________________
Type BC = 88 90 for Unrestricted Digital Information (DATA)

241
ISDN Traces
Outgoing call set up with overlap dialing
➨ The called number is sent in one or many information

messages (IE)
▼ Send SETUP message
▼ Send information element in this message (EI)

✦ CALLING NUMBER
▼ Reception of acknowledge message from network SETUP ACK
▼ Send one or many information elements (EI)

✦ These messages contain one or many digits of the called number (send
according to the dialing rhythm
✦ If the number format known in the translator
The last message contains the SENDING COMPLETE information
✦ If the number format is undefined in the translator
The reception of call proceeding message from network indicates the end of
dialing

_____________________________________________________________________________
| tei : 0 <<<< message send : SETUP [05] Call ref : 64 d1
|______________________________________________________________________________
| [9e] Non-locking shift. codeset : 6
| EI:[24] MOD_FNCT_USAGER (l=1) :80
| EI:[6c] CALLING_NUMBER (l=10) : -> a1 Num : 298143010
| EI:[7d] HLC (l=2) :91 81
| EI:[7e] USER_USER (l=1) : 04
|______________________________________________________________________________
_____________________________________________________________________________
| (375826780:001112) Physical-Event :
| tei : 0 >>>> message received : SETUP ACK [0d] Call ref : e4 d1
|______________________________________________________________________________
|______________________________________________________________________________
_____________________________________________________________________________
| tei : 0 <<<< message send : INFORMATION [7b] Call ref : 64 d1
|______________________________________________________________________________
|______________________________________________________________________________

242
ISDN Traces
Call reception from public network
➨ This call is always in block mode
▼ Reception of a set up message SETUP with SENDING COMPLETE
➨ Reception of information elements in this message (EI)

✦ B channel number to use
The public network has B Channel choice
Type 88 90 for Unrestricted Digital Information (DATA)
✦ Caller number (CALLING_NUMBER)
Provided by distant
✦ Installation number (CALLING_NUMBER)
Provided by public network
✦ DDI called number (CALLED_NUMBER)
4 digits in VN4, 9 in ETSI

_____________________________________________________________________________
| (375826047:001002) Physical-Event :
| tei : 0 >>>> message received : SETUP [05] Call ref : 3b 0d
| SENDING COMPLETE
|______________________________________________________________________________
|
| EI:[18] CHANNEL (l=3) : a9 83 8e -> T2 : B channel 14 exclusive
| EI:[1e] PROGRESS_ID (l=2) :85 83
| EI:[6c] CALLING_NUMBER (l=5) : -> a1 Num : 298143012
|______________________________________________________________________________

243
ISDN Traces
Call proceeding (sent or received)
➨ This information contains 2 messages
▼ CALL PROC: Call proceeding

✦ On one outgoing call in overlap mode , if the system ignores the send
number format, this message finishes the dialing
▼ ALERT: The called user is ringing
User connection
➨ Send and receive connection messages
▼ CONNECT: User connected
▼ CONNECT ACK: Connection acknowledged by public network

CONNECT and CONNECT ACK are optional.
_____________________________________________________________________________
| tei : 0 <<<< message send : CALL PROC (02) Call ref : bb 0d
|______________________________________________________________________________
|
|______________________________________________________________________________
_____________________________________________________________________________
| tei : 0 <<<< message send : ALERT (01) Call ref : bb 0d
|______________________________________________________________________________
_____________________________________________________________________________
| tei : 0 <<<< message send : CONNECT (07) Call ref : bb 0d
|______________________________________________________________________________
_____________________________________________________________________________
| (375826125:001022) Physical-Event :
| tei : 0 >>>> message received : CONNECT ACK (0f) Call ref : 3b 0d
|______________________________________________________________________________

244
ISDN Traces
Disconnection of communication
➨ Disconnection information transmission
▼ DISCONNECT: Send by the terminal which releases the call

✦ Provide the release cause in the information element
Communication release
➨ Transmission of release messages
▼ RELEASE: Call release
▼ RELEASE COMP: Call release from end to end

DISCONNECT will depend of the presence of a CONNECT message.
_____________________________________________________________________________
| (375827088:001207) Physical-Event :
| tei : 0 >>>> message received : DISCONNECT [45] Call ref : 3b 0d
|______________________________________________________________________________
|
| EI:[08] CAUSE (l=2) :87 90
|______________________________________________________________________________
_____________________________________________________________________________
| tei : 0 <<<< message send : RELEASE [4d] Call ref : bb 0d
|______________________________________________________________________________
|
| EI:[08] CAUSE (l=2) :87 90
|______________________________________________________________________________
_____________________________________________________________________________
| (375827092:001212) Physical-Event :
| tei : 0 >>>> message received : REL COMP [5a] Call ref : 3b 0d
|______________________________________________________________________________

245
ISDN Trace
Trace tools
The Alcatel OmniPCX Enterprise possesses integrated

script to realize third level traces of ISDN protocol: t3
It’s possible to indicate ISDN access to trace
➨ Use the command with the following parameters:
▼ C ‘cristal number’ c ‘coupler number’
▼ To obtain a trace on T2 located in the Shelf 0, board 5:

t3 C 0 c 5
Stop the trace with “Ctrl-C”
To suppress tuner parameters and restart the tracer
➨ tuner clear-traces ; trc init ; dhs3_init -R MTRACER

The “t3" can not allow to set up a trace on a specific number.

On a T2 access, 30 calls can be simultaneously set up, the result of a t3 trace. corresponds to the messages of those 30 calls.
Checking the result corresponding to a specific call can be difficult.
If needed, use the following procedure
tuner km Á Stop the mtracer tool
tuner clear-traces Á Empty the buffer of traces
tuner cpu cpl Á Show messages from CPU to coupler, and from coupler to CPU
trc i Á Initialization of the accesses filters
(Optional ) trc C 0 c 5 t 0 Á Set up a filter on the Shelf "0", board "5", access "0"
mtracer -a ZABPQMCDU Á Active the trace on the corresponding "calling" or "called number"
(must be complete number)
To stop the trace, the following steps have to be followed

Press on “Ctrl-C" Á Stop the mtracer tool in trace mode
tuner clear-traces Á Empty the buffer of traces
trc i Á Initialization of the accesses filters
dhs3_init -R MTRACER Á Restart the mtracer tool in standard mode

246
Application Traces

OBJECTIVE:
◆ To set-up application traces in stand-alone
Alcatel OmniPCX Enterprise – Application Traces

247
Traces
Examples
Main option of traces

➨ ARS
➨ VPN
➨ VoIP
➨ Hybrid
➨ ISDN
➨ Users / Terminal


248
Traces
ARS
ARS Trace
➨ Start-up the trace
▼ Stop mtracer process
✦ tuner km
▼ Deactivate the filters and empty the buffer

✦ tuner all=off
✦ tuner clear-traces
✦ trc i
▼ Activate trace on application

✦ tuner +at
✦ actdbg ars=on
▼ Start-up the traces server

✦ mtracer -a or
✦ mtracer -a &


249
Traces
ARS
Example of ARS trace
Calling 0298232000
ARS route 1 = T0 delete 5 add 02980 cout 5
ARS route 2 = T2 sans changement de num. cout 10
le T0 est libre
(831627:180798) ARS->is here idx_remp = 1 idx_emis = 0 idx_fin = 0

(831627:180799) ETRALI ARS nulosub=65535 forwarded_neqph=-1 expldisa=0
(831627:180800) ARS call allowed
(831627:180801) ARS: Enter ini_ars premchif est mis a TRUE
(831627:180802) ARS : ars_demarnum_ok fintrad 1, findiscri 1, overlap 1, opt_b3
1, idx_fin 11
(831627:180803) ars_demarnum_ok-->result=0
*
*
*
1, idx_fin 11
(831627:180821) ars_demarnum_ok-->result=1
(831627:180822) ARS : Enter ars_demarnum with forwarded_neqph = -1, nummcdu = -1


250
Traces
ARS
Example of ARS trace (follow-up)
(831627:180823) ARS : testars processing route list 0 idx_ars 0, zone 1

(831627:180824) ars_sauv_numcomp j = 1 digit = 10
(831627:180835) ars_sauv_numcomp idx_remp = 11 idx_emis = 2, idx_fin = 11
(831627:180836) ars_sauv_numcomp idx_remp_numdialed = 11
(831627:180837) ARS demar_rln idx_remp = 11 idx_emis = 2 idx_fin = 11
(831627:180838) ARS : rln process route list 0
(831627:180839) rln_process : ptdemi->arsdata.rln : 0
(831627:180840) rln_process bw: ptdemi->arsdata.failcode : -2
(831627:180843) rln_process aw: ptdemi->arsdata.idx_ars : 1
(831627:180844) rln_process aw: poorRoute : 0
(831627:180845) rln_process : dtyterm != JONCT cos : 8
(831627:180846) ARS : rln_process - user cost = 8, failcode = -2
(831627:180847) ARS : stopping points on primary routes = 0, wait point enable = 1
(831627:180848) ARS : Route: 1, tg = 10, stop_limit = 5 wait_limit = 5


251
Traces
VPN
VPN Trace
✦ tuner km

✦ tuner all=off
✦ trc i
▼ Activate trace on application

✦ tuner +at
✦ actdbg vpn=on

✦ mtracer -a or
✦ mtracer -a &


252
Traces
VoIP
VoIPTraces
✦ tuner km

✦ tuner all=off
✦ trc I
▼ Set the option

✦ tuner cpu-cpl=on (to get the trace over the IP trunk group)
✦ tuner cpl-cpu=on (to get the trace over the IP trunk group)
✦ trc C x c y (to filter the access of the IP trunk group)
✦ tuner +at
✦ actdbg voip=on

✦ mtracer -a or
✦ mtracer -a &


253
Traces
Hybrid link
Hybrid links Trace

✦ tuner km

✦ tuner all=off
✦ trc i
✦ tuner hybrid=on
▼ Activate trace on application and set the optin

✦ tuner +at
✦ actdbg hybr=on

✦ mtracer -a or
✦ mtracer -a &


254
Network Architecture
ABC-
ABC-F Traces
Example of ABC traces on hybrid links (1):

➨ tuner hybrid=on, actdbg hybr=off
_____________________________________________________________________________
| tei : 0 <<<< message send : SETUP [05] Call ref : 00 04
| SENDING COMPLETE
|______________________________________________________________________________
|
| EI:[1c] FACILITY (l=98)
| Service discriminator [91] : supplementary service
| [aa] NFE (l=6):
| [80] Source Entity : (l=1) : End_PTNX
| [82] Destination Entity (l=1) : End_PTNX
| [a1] INVOKE (l=16):
| Invoke Ident. : 2ee0 (12000)
| OP: ECMA RO_CALLING_NAME (0)
| [80] Name presentation allowed (l=4) : 'DUPONT Jean'
| [a1] INVOKE (l=69):
| Invoke Ident. : 0001 (1)
| OP: ALCATEL RO_CLASSMARKS (1)
| [30] Sequence (l=56) :
| [80] Feature identifier (l=5) : 06 44 6a 1f 04
| [82] Cug (l=1) : 00
| [83] Trunk call priority (l=1) : 00
| [ab] Sequence of Project data (l=41) :
| [30] Sequence (l=15) :


255
Network Architecture
ABC-
ABC-F Traces
Example of ABC traces on hybrid links (2):
| OP : CLASSMARKS_SUPPLEMENTARY_INFO_1 (7000)
| [30] Sequence (l=9) :
| [83] Current entity (l=1) : 02
| [84] Initial kind of call (l=1) : 11
| [85] Context specific (l=1) : 02
| [30] Sequence (l=22) :
| OP : VMS SERVER ACCESS (7005)
| [30] Sequence (l=16) :
| [80] Language (l=1) : 01
| [81] type of set (l=1) : 03
| [84] Feature identifier 2 (l=5) : 00 c0 00 00 00
| [86] Priority of call (l=1) : 00
| EI:[1c] FACILITY (l=27)
| Service discriminator [91] : supplementary service
| [aa] NFE (l=6):
| [80] Source Entity : (l=1) : End_PTNX
| [82] Destination Entity (l=1) : End_PTNX
| [ab] Interpretation_APDU (l=1): DISCARD (0)
| [a1] INVOKE (l=13):
| Invoke Ident. : 1b6f (7023)
| OP: ALCATEL Unknown : 1b6f (7023)
| EI:[7d] HLC (l=2) :91 81
| [95] Locking shift. codeset : 5
| EI:[32] PARTY_CATEGORY (l=1) : -> EXTENSION (1)
|______________________________________________________________________________


256
Traces
ISDN
ISDN Traces
✦ tuner km

✦ tuner all=off
✦ trc i
▼ Set the option
✦ tuner cpu-cpl=on
✦ tuner cpl-cpu=on
✦ trc C x c y (to filter the access of the ISDN trunk group)
✦ mtracer -a or
✦ mtracer -a &

This corresponds to the t3 trace

257
Traces
User / Terminal
Traces on terminals (follow-up)

✦ tuner km
✦ tuner all=off
✦ trc i
▼ Set the option
✦ tuner xtrace=on,neqt (equipment number of the terminal)
✦ tuner +at,neqt (equipment number of the terminal)
✦ mtracer -a or
✦ mtracer -a &


258
Traces
User / Terminal
Traces with trcterm script
➨ This script enables to trace one or several terminals
➨ The terminals can be specified by their directory number, or

by their equipment number
➨ These traces can be redirected to a file

▼ be careful to the available disk space
➨ The trcterm command, without any option, gives the

different available syntaxes


259
Traces
User / Terminal
Traces with trcterm script (follow-up)
use: trcterm <selected-equipment> [help|h]

<selected-equipment> :
all
first clear and turn OFF all traces then turn ON traces
for all equipment's of the system
neqt|n <neqt_number>
dir|d <directory_number>
first clear and turn OFF all traces then turn ON traces
for given equipment
+neqt|+n <neqt_number>
+dir|+d <directory_number>
turn ON traces for given equipment WITHOUT turning OFF
previous traces
-neqt|-n <neqt_number>
-dir|-d <directory_number>
turn OFF traces for given equipment WITHOUT turning OFF
previous traces
stop
turn OFF all traces and kill mtracer
help|h : print this usage
example: trcterm neqt 306

trcterm +d 77712
trcterm -n 306
trcterm all


260
Traces
UA sets
Specific traces on UA sets
➨ Enables to have information about messages exchanged

between UA sets and Enterprise
➨ Then, the process mtracer is used
▼ tuner km
▼ tuner all=off
▼ tuner cpu cpl
▼ mtracer -u or mtracer -u &


261

262
Traces
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to launch traces and interpret the messages in the traces
MANAGEMENT
1. Set up an ISDN T2 link if it is not yet done on your system

1.1 Trunk group id will be n2 for the T2, see with instructor for the external dial plan.
1.2 Select the t3 trace, store the trace in a file named ISDN_Trace, under /usr4/tmp
1.3 Without using t3, but using tuner, validate the options to get the same trace
1.4 Validate a trace on a selected number with mtracer –a ABPQMCDU
1.5 Send the ISDN trace result through a text file
1.6 Get the text file on your PC via FTP
1.7 identify the different elements :
- Call Ref calling and called
- Call type
- Calling and called number
- Call proceeding
- User connection
- Disconnect
- Communication release

263
Traces

264
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
265
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
266
Creating simple script

OBJECTIVE:
◆ To be able to create simples scripts using the bash shell
Alcatel OmniPCX Enterprise – Creating simple script

267
Creating simple scripts
Overview
A script is a group of commands recorded in a text file.
➨ Using the shell as a programming language
➨ Using system commands
This file has to have proper executed rights to be used as

an ordinary command
➨ The command called chmod allow to Modify file rights in

order to execute it
➨ Different commands describe in the scripts will be used with
the normal rights of the account

The shell bash is the user interface by default in the OmniPCX Enterprise
To modify a file rights in order to execute it, you have to used the x right for the account using the following command:
Chmod u+x scriptname

268
Overview
Commentaries in Shell
➨ Comments are there to facilitate the understanding of the

script (if any further modification would be needed)
➨ A commentary line always begins with the

sign #
➨ The contents of this line, up to the line feed, are not

interpreted by the shell
➨ External commands to the shell

▼ Example:ls, ps, awk
➨ Internal commands to the shell
▼ Test functions, control loopback

At the beginning of the script we will find the line #!/bin/bash allowing to specify the interpreter used in the program.

269
Overview
The command echo
➨ Used to inform user of script’s progress or to request to

enter a command
➨ Used to build up a menu
(101)xa001001> cat script1

echo " Good Morning"
echo "This is the date of the day:"
date
(101)xa001001>
(101)xa001001> script1
Good Morning
This is the date of the day:
Fri Jun 10 14:49:49 CEST 2005
(101)xa001001>


270
Overview
The command echo
➨ To improve the text presentation, -e option allow to used the

following codes
✦ \n new line
✦ \t tabulation writing
✦ \c leave the cursor at the currant place
(101)xa001001 > echo -e "\nwelcom\n\tthis i a new line with

tabulation\n\t\tthis one with 2 tabulations\nand the cursor
will stay at the end of the line\c"
Welcom
this is a new line with tabulation
and this one with 2 tabulations
And the cursor willstay at the end of the line(101)xa001001 >


271
Overview
Variables
➨ The operation consists in assigning contents to a variable
Usually these will be character strings
Different types of variables include:

➨ System variables (predefined variables)
➨ User-defined variables
➨ Specifics variables
In the shell,concerning variables,there is no differences

between numbers and characters strings

Allocation example:
Newspaper=“/usr4/tmp/DHS3-init.log”
Echo Newspaper will be displayed Newspaper
Echo $Newspaper will be displayed usr4/tmp/DHS3-init.log

272
Overview
Main system variables:
➨ PS1
▼ contains the standard prompt text which the
shell displays on the screen as a key-in prompt
➨ PS2
▼ displayed by the shell when a keyed-in line is not
compliant with expected key-in
➨ HOME
▼ contains the absolute access path for the current
directory
➨ PATH
▼ contains the list of directories, separated from
each other by colons. These are the directories
explored in searching for an external command

System variables describe the home work of the user.it can be displays using env and set commands.
system variables example:

PWD=/DHS3data/mao Curent Répertoire
HOSTNAME=xa001001 system name
PS1=(101)xa001001> standard Prompt
USER=mtcl user name
LOGNAME=mtcl login name
SHELL=/bin/bash command interpreter
OSTYPE=linux-gnu operating system name
HOME=/DHS3bin/mtcl Personal user directory
TERM=vt100 emulation type used for terminal
PATH=.:/DHS3bin/oneshot/mtcl:/usr/bin/rsh2ssh:/usr/local/bin:/bin:/usr
/bin:/usr/netadm/bin:/DHS3bin/com:/DHS3bin/tel:/DHS3bin/servers:/DHS3b
in/downbin:/DHS3bin/oneshot/mtcl:/DHS3bin/incid:/DHS3bin/fab:/DHS3bin/
x25:/sbin:/usr/sbin

273
Overview
User-defined Variable
➨ These variables are used to store data
➨ Variable content can be modify in the script

(101)xa001001 > cat essai2
Date="/bin/date"
echo -e"Good morning\nthe date of the day is:«
$DATE
echo « this the content of the variable DATE: $DATE"
(101)xa001001 >
(101)xa001001 >essai2
Good morning
the date of the day is:
Fri jun 10 14:49:49 CEST 2005
This is the content of the variable DATE: /bin/date
(101)xa001001 >

In that case the variable DATE is equal to /bin/date. The variable can be substituted to the content of the variable Using the $
character.
Example:
Var1=Black
Echo “ the color of the Var1 is $Var1“ = the color of Var1 is Black
Echo ‘ the color of the Var1 is $Var1’ = the color of Var1 is $Var1

274
Overview
Specifics variables:
➨ These variables are directly supervised by the system

and can not be modified
▼ Only accessible in read only
➨ $:process number (PID) of active shell

▼ contains the absolute access path for the current
directory
➨ !:process number (PID) in case of process in background

▼ Used to check if a process run properly in background

In case of two script which run simultaneously .It can be useful to used the $ variable in order to write in two different temporally
files.
Example:
Tempfile=/tmpd/Temp.$$
For one script it will be /tmpd/Temp.1234 and for the second script it will be /tmpd/Temp.1304
(1234 and 1304 being process numbers)

275
Overview
Deleting user variables
➨ Can be done by the command:unset
▼ unset variablename
Exportation command
➨ The variables are only defined in the shell where they were
created
➨ With the command export, this variable is copied into all

new shells created.

Example with the export command:
(101)xa001001> echo $$ Allow to display the process number (pid)

564
(101)xa001001> Var1= "original shell" Overview of the var1 variable
(101)xa001001> Var2="Secondary variable" Overview of the var2 variable
(101)xa001001> export Var1 The Var1 variable is exported
(101)xa001001> bash Another shell is running
(101)xa001001> echo $$ display the new process number (pid)
15611
(101)xa001001> echo $Var1 Content of these two variables are diplayed
Original shell Var1 is available in this new shell
(101)xa001001> echo $Var2
Var2 is unknown (empty string)
(101)xa001001> Var1="Secondary shell" Redefinition of the variable Var1
(101)xa001001> Var2="New shell" Redefinition of the variable Var2
(101)xa001001> echo $Var1 Content of these two variables
Secondary shell Var1 is modify in this shell
(101)xa001001> echo $Var2
New shell Var2 is defined
(101)xa001001> exit Exit of the secondary shell (back to the original
exit shell )
(101)xa001001> echo $$
564 Display of the process number from the courant
(101)xa001001> echo $Var1 shell
Original shell Display of the two variables content
(101)xa001001> echo $Var2 Var1 doesn’t change
Secondary variable
(101)xa001001> Var2 doesn’t change

276
Overview
The command test allow to check a variety of conditions:
➨ test of two character strings

▼ test “$var” = string (equal)
▼ if test “$var1” != string (not equal)
➨ digital tests
▼ if test < integer1 > -gt < integer2 > (>)
-ge < integer2 > (>=)
-eq < integer2 > (=)
-ne < integer2 > (different)
-le < integer2 > (<=)
-lt < integer2 > (<)

To make a test on a character string,it is necessary to put variable name between quotation mark.
Example:
Test –z $variable =an error will be present if the variable is empty
Test –z “$Variable” =no error,if the variable is empty,we will test an empty string between quotation mark.

277
Overview
Other possibilities of the command test
➨ test also allows an access path’s characteristics to be tested
▼ if test -f <path> true if <path> is an ordinary file

-d <path> true if <path> is a directory
-r <path> true if <path> is read authorized
-w <path> true if <path> is write authorize
-x <path> true if <path> is execute authorized
➨ The various test forms can be interlinked using other options
▼ !: logical negation of test

▼ -a: Logic link «AND» of both tests
▼ -o: Logic link «Or» of both tests

Example utilisation of the dans .profile file of mtcl:
if [ "$CYGWIN" = "" -a -f $HOME/.kshrc -a -r $HOME/.kshrc ]; then

ENV=$HOME/.kshrc # set ENV if there is an rc file
export ENV
fi
The test is about the CYGWIN variable and about the existence of /usr2/mtcl/.kshrc file ($HOME is equal to /usr2/mtcl for the
mtcl account).The first test check that the CYGWIN variable is empty (=""),then we add two others tests on the .kshrc file using (-f)
and (-r) option.
If all tests correspond ,we validate the ENV variable with /usr2/mtcl/.kshrc and we export this variable to use it in several
programs .

278
Overview
The instruction while and for enables a command

sequence to be executed as long as a condition is true
➨ while condition
➨ Do
➨ list of shell commands
➨ done
(106)xa001006> cat script3
#As long as you don’t stop by ctrl-C
while true
Do
#You can’t use directly config it’s an alias,
#You must used but tool config
tool config 1
sleep 5
done
(106)xa001006>


279
Overview
The instruction if allow to execute a command if a

condition is true and another one in the other case
➨ Syntax:
if condition
then
list of shell commands if condition is true
else
list of shell commands if condition is true
fi

Example with if:
(101)xa001001> if test –f $HOME/.profile The test will be true if .profile file is an

ordinary file)
> then
PS2 prompt(>) is displayed because the command
> echo ".profile file exist" Is not finished for the shell
> else
> echo ".profile file is not present"
> fi
.profile file exist
(101)xa001001>
The instruction if can be also written by using && et || option
(101)xa001001> [ –f $HOME/.profile ] && echo "Le fichier existe" || echo "Le fichier est absent"
Le fichier existe
(101)xa001001>

280
Overview
Conditional execution
➨ The case instruction allow to choose several possibilities and
execute the appropriated command
➨ A default command can be proposed if not any tests doesn’t
correspond
➨ Syntax:
case Variable to test in
choice 1)
list of commands if the test correspond ;;
choice 2)
list of commands if the test correspond ;;
*)
list of commands if not any test correspond ;;
esac

Example with the case option:
(101)xa001001> Choice="2" The Choice is eqaul to 2.

(101)xa001001> case $Choice in
the PS2 prompt(>) is displayed because the
> 1) command is not finish by the shell
> echo « the choice 1" ;;
> 2)
> *)
> echo « other choice" ;;
> esac
Le choix 2 The command case is checked for 2)
(101)xa001001> Choice="6" The Choice is eqaul to 6.

(101)xa001001> case $Choice in
> 1)
> 2)
> echo "Le choix 2" ;;
> *)
> echo « other choice" ;;
> esac No more possibilities correspond, this is the
Other choice default command *) which is used.
(101)xa001001>

281
Overview
Interactive dialogue instruction
➨ The Read command wait a value and store it in variable
echo –e "\tYour choice ? \c "

read Answers
▼ It is possible to validate several instructions at the same time
Result capture of a shell command

➨ The command has to used back quotes (`=Alt-Gr 7 on AZERTY
Keyboard)
PROCESS=`ps –edf | grep remad`

[ -z "$PROCESS" ] && echo " inactif Telephon "

Example:.profile file of the swinst menu
echo " 1 Packages installation" read: reads a message sent by user

echo " 2 Deliveries installation" case: makes a choice between several alternatives
echo " 3 Cloning operations"
esac: end of structure
echo " Q Go back to previous menu"
echo " Your choice [1..4, Q] ? "
read Reply
echo
case $Reply in
1 )
installpkg_menu ;;
2 )
delivery_menu ;;
3 )
cloning_menu ;;
Q )
echo "bye bye" ; exit 0 ;;
* )
echo "Wrong Choice" ;;
esac

282
Overview
It is possible to transmit parameters to a script
➨ The instruction $0 contains the script name
➨ The instruction $* contains all parameters received
➨ The instruction $# contains the number of parameters

received
➨ The instruction $1 to $n contains the respective parameters

[ $# -gt 0 ] && echo " there are some parameters "


283
Overview
A script can contain some functions
➨ They can be used to create specifics menus
➨ They are used in the script as common shell commands
➨ A function can receive some parameters and send back a

code in order to be tested (0= true,1=False)
Exist_Param ()
{
[ $# -gt 0 ] && BackCode=0 || BackCode=1
return $BackCode
}

Example of function in a script:
(101)xa001001 > more script

Function_1 ()
{
echo " you want the function 1 "
}
Function_2 ()
{
echo " you want the function 2 "
}
#
while true ; do
echo " Principal menu"
echo " 1 Function 1"
echo " 2 Function 2"
read Reply
case $Reply in
1 ) Function_1 ;;
2 ) Function_2 ;;
* ) echo "incorrect choice" ;;
esac
done

284
Overview
Contain of the /usr2/oneshot/mtcl/whereis script

if test $1
then
echo "scanning alias of mtcl ..."
if (grep $1 /DHS3bin/mtcl/.kshrc)
then
:
fi
echo "scanning directories ..."

echo ""
find / -name $1 -print 2>/dev/null
else
echo "usage: whereis <file to find>"
fi

The whereis script allow to look ing for a command on the disk.:
Explications:
1. if test $1 we check that a parameter is present
2. If (grep $1 /DHS3bin/mtcl/.kshrc) the grep command will go back TRUE if it find something in the alias file
(.kshrc)and will displays the result.
3. Then:
4. Display of information and find command the command find the file asked with $1 will display the result
5. If there isn’t parameters (else) we display the script syntaxe

285
Overview
Part of the /usr2/oneshot/mtcl/t3 script

echo "--> Cleaning mtracer..."
if ( ps -edf | grep mtracer > /dev/null )
then
/DHS3bin/oneshot/mtcl/tuner kill-mtracer
fi
/DHS3bin/oneshot/mtcl/tuner clear-traces
/DHS3bin/oneshot/mtcl/tuner cpu-cpl=on cpl-cpu=on
echo "--> Positionning t3 filters..."
trc init > /dev/null
if [ "${CR_NBR}" = "" ] && [ "${CPL_NBR}" = "" ]
then
# (filters Position)
elif [ "${CR_NBR}" != "" ] && [ "${CPL_NBR}" = "" ]
then
# (filters position)
elif [ "${CR_NBR}" = "" ] && [ "${CPL_NBR}" != "" ]
then
else
fi

The t3 script can be quite complicated.

Explication of this part.
1. Information display with the echo command
2. Search of the mtracer process
3. Buffer traces is clear
4. All filters are deleted in trc (trc init)
5. We test then the contain of CR_NBR (crystral n°) et CPL _NBR (N°coupler) using if instructions
• If the crystal N° is empty (=“”) and the coupler N° is empty
• If the crystal N° is not empty (!=“”) and the coupler N° is empty
• If the crytal N° is empty and the coupler N° is not empty
• Then (crytal and coupler N° none empty)
• Etc….

286
Creation of simple scripts
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to create of simple scripts
MANAGEMENT
1. Modify the menu of the following file (REF: ENTP0542A01TEUS, ask to the trainer) in order to
add the possibility to realize a trace over IP (ACTDBG voip=on). After the modification done,
download by FTP connection this file in ASCII mode under mtcl and finally modify the file
rights to execute it.
2. Depending and the remaining time create a script called Config in /usr2/mtcl (be careful to
the case sensitive used for the characters).
2.1. This script will display the result of the config command with a shelf number (recall: the
config command is an alias of the tool configcommand).
2.2. The firs parameter will be the shelf number.
2.3. The secondary will be the number of time (facultative) where the config command is
displayed.

287
Creation of simple script
Correction
1. Add an entry in the menu with the function VOIP_TRACES for example.
copy the SIP_TRACES function for example and rename by VOIP_TRACES and change
$ACTDBG sip=on by $ACTDBG voip=on in the new function.
2. Script allowing to display a shelf configuration

#!/bin/bash
# Test of the number of parameters
case $# in
0)
#name of the script without the access path
NomScript=`basename $0`
echo -e "\nScript d'affichage en boucle de la configuration d'une alveole\n"
echo -e "Le numero de l'alveole est obligatoire (0 - 90)"
echo -e "Syntaxe : $NomScript Num_Alveole Nb_Repetition"
echo -e "Exemple : $NomScript 0 5 \t==> Affichera 5 fois l'alvéole 0.\n"
# We leave the script with back code indicated an error
exit 1
;;
1)
# only one parameter ,the shelf number
ACT="$1"
# We initialize one time in $NBR
NBR=1
;;
2)
# the parameter 1 is the shelf number
ACT="$1"
# the parameter 2 is the number of repetition witch will be memorize in $NBR
NBR="$2"
;;
esac
# Counter Initialization
i=0
# instruction while the counter is smaller than the limit
while [ $i -lt $NBR ] ; do
# screen is cleaned
clear
# The config command is an alias of the real "tool config" command
tool config $ACT
# Break of 5 seconds in order to read
sleep 5
# Counter incrementation
let i+=1
done
# The script is finished when (counter =limit)

288
!
" # # $ #
% &
' ( # ) * $
%# + , &$
-- .
# % +! &
/ 0011$ #
!
" !
"
# ! ! " $ !
# $ (
2 ( / $ #
!
" !
"
# ! # # $ !
)
%&'! $%
!
%( )*+ + ! & $ '(
/ .
$+, ! $ )
) $
# . 3 #
$ $ & * $ &
, . 3 ,
- .$ + + $ , - ./
- .$ + 0 % ))) +
4 . 3 5 6$ #
) 8 # % # 9 ) * &
# *" ' /0
1
+ ( % 97 #&
3 9)
. 3 % 6 &
- .$ + + +
2
!
+ + /0
1
4 % 9 : 7;2 &
,#'$+, ! "1# 203
) ! ! . # , )
' :$ " < :
289
. 3 . . 4
. %&' !
. * $ & *45
; ! +
%* /0
1
,#'$+, ! "1# 203

- .$ + " 0 6 "1# "+
. 3 .
. %&' !
. * $ & *45
.%( )*+ + " " * $ & *45
2
) % 96 ( &
, +# /0
1
; 96 $. ( # $ . .
5 44 - .$ - .$ + 5
: # '=
- .$ $$ 7 +
$
1#
) '= $ . $ . #
- .$ ' 8 9 5 .,#'$+, * $ &
) '= $ . '=
- .$ : $ $$ 7 +
$ &# %
: 1";
' $ . '=
$+, ! "# # 1#
'= $ . .
- .$ 1 % 7 +
$
1##
' '=$ . ,
$+, ! "# # 1# : 1";
'= $ .
$+, ! "# # 1# : 1"; 1##
( # #
. #
%+ . # . # 92 <7;2 &
.$+, 5 .,#'$+, * $ &
) .
# ' /0
1
- .$ + ; < - = > ? +
$
.
6575 5#5 0
. $*$ $ % &
- .$ @ 8 % "1# 203 %< $ 9 7 +
290
$ ,#'$+,
3 A203
, # $ .
,#'$+, ! "1# 203
# 3 .
3
,#'$+, ! $ % 3 A203
B0
. . #
,#'$+, ! "1# 203
"
- .$ 3 A203 7
4 #
- CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC ** .,#'$+,
- .$ + $ ** .,#'$+,
- CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC ** .,#'$+,
2
. #
& %* (#+ /0
1
- .$ + + 0 + + " % . +
. . : :'
.
$
2
8 6
+ % * /0
1
+ +
# '
, +#
- .$ + ; < - 0 ;@ % 8< @9? +
$ 6
. 6
7565#5 0
- .$ 0 ;@ % 7 + $ 4 8
B 0
4 8 !
# *" '
." @ % 5 .,#'$+, * $ &
2
8 >
(7& +%* /0
1
+ +
# '
, +# A & <% $ . $$ )))
. -68 9!
.
. %&' -68 !
# *" '
)
291
." 5 .,#'$+, * $ &
2
8 ?
: * /0
1
+ +
# '
, +# 0 ;@ .
, +# .
.
. %&' ; !
# *" '
." 5 .,#'$+, * $ &
2
8 0
%* /0
1
+ +
# '
.
. %&' 9!
# *" '
." 5 .,#'$+, * $ &
2
8 @
+ * /0
1
+ +
# '
.
. %&' !
# *" '
." 5 .,#'$+, * $ &
2
8 A
* /0
1
+ +
# '
.
. %&' !
# *" '
." 5 .,#'$+, * $ &
2
8 B
#" +# * /0
1
+ +
# '
.
. %&' !
# *" '
." 5 .,#'$+, * $ &
2
% . + &
. $+,
292
- .$ + ; < - $ & 8 "1# 203 9 = > ? +
$
.
6575 5#5 0
" # . . % + &
. $+,
B0
- .$ - % $$ $ "1# 203
; ! 3
4 ( 3
$ #
'"C : ) % ( $ $ D 3 +E +6@&
, @;( "1# , ) <
8
4 . 2 :
F . $
, ( G/ F/ H
2 : %/: ;&$
( I . %9: & 5
JI $ . . . (
( $ . '"C : ) 3
- .1,## =! 2 $
- .$ + + + + BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
- .$ + + B 81 ! & <9 B
- .$ + + BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
- .$ + + + + 5) 0 ;@
- .$ + + + ) D<% $
- .$ + + + ') E @
- .$ + + + F) @ ;
- .$ + + + G) 0
- .$ + + + H) 1"
- .$ + + + I) #
- .$ + + + + J) J
- .$ + + + =5 I J>7 +
$ 6
. 6
0
+ % *
0
(7& +%*
)0
: *
0
%*
0
+ *
>0
*
?0
#" +# *
@5A0
,## !
B0
- .$ + + K + + " % . +
$
293
$
>
294
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
295
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
296
License and OPS files

OBJECTIVES:
◆ To describe the principle of e-licensing
◆ To describe the role of the different OPS files
Alcatel OmniPCX Enterprise – License and OPS files

297
Licenses and OPS files
Overview
The system of licenses allows to
➨ Supply a unique installation medium independently from the

applications bought by each customer
➨ Avoid the risks of fraudulent use of the software
➨ Define a commercial politics fitted to:
▼ The customer needs
▼ The market constraints
It is based on two distinct elements
➨ The license file
➨ The software locks controlled by the Call Server

OPS: Order Preparating System

298
Definitions
The Call Server features and applications are controlled by

hardware/software keys
Each system is uniquely identified
➨ This reference is stored:
▼ In the PROM for each CPU board (CPU-Id)
✦ It is the case for the CPU-CS, the Appliance Servers and the new boards
CPU5/6
▼ In an hardware PAL-key plugged on the CPU5 or CPU6 boards
✦ This hardware key was used before in the software protection system of
the OmniPCX 4400
✦ It is still compatible in case of a migration to OmniPCX Enterprise

PROM: Programmable Read Only Memory

PAL: Programmable Array Logic
If the system is duplicated, there are whether 2 CPU-Id, whether 2 hard key numbers in the license file.

299
Definitions
The system identifier (CPU-Id) is encrypted in the license

file and supply the software key
System ID
CPU ID or
License file Software key
hardware key
The software keys are ordered through eCom and/or the

software Actis or ExpressQuote
➨ Hardware and software can be ordered separately

eCom: Alcatel Internet server dedicated to receive orders for licenses and hardware
ACTIS: Alcatel Configuration Tool for International Sales
Configuration and costing software used to calculate complex offers for OmniPCX Office, OmniPCX 4400 and OmniPCX
Enterprise
ExpressQuote: Quick costing tool for OmniPCX Office and OmniPCX Enterprise (up to IPMG 250)
Available in 3 versions:
A paper version
An electronic offline version
An electronic online version (Website)
The license file contains the listing of the software locks open in the Call Server software, the listing of the CPU identifiers (CPU-Id),
miscellaneous technical information and a software key.
This key is generated from information contained in the file and from a secrete key.
It is impossible to modify the licenses in this file because the software key wouldn’t correspond anymore.

300
Order principle
Offers generated Three

by Actis possibilities
Final
configuration
or
by ExpressQuote Extranet
e-com
or
Final customer
quotation
Direct license Alcatel

Business Partner
order
Web site
Listing of items


301
e-Licensing Portal
Marketing
information page
Important
Messages
Licensing services
Software keys
Easy access to management tool
E-Licensing

The e-Licensing portal is accessible on the Alcatel Business Partners website (https://www.businesspartner.alcatel.com)
The following operations are available through this website:
Order licenses by lot
Moving the licenses to another site
Management of the keys
CPU-Id registration
Reaffecting CPU-Id
FAQ

302
Main locks
Licenses related to the sets
➨ « Engine » licenses possible
▼ 80,150, 250, 500 and over 500 users
➨ « Client » licenses (UA, Z, IP phones, mobiles , etc.)
▼ by packages of 10
➨ Auxiliaries licenses (IP trunk, compression, conferences)
▼ piece by piece
➨ DECT licenses
▼ based on the users number and not the stations number

Licenses concerning the users are based on client-server model (server & clients)
The engine license represents the capacity of the system and the client license represents the users
(UA, Z, IP phones, SIP phones, etc.)

303
Main locks
Licenses related to applications
➨ OmniVista 4760
➨ OmniMessage 4635, 4645
➨ Notification server
➨ Hotel / Hospital
➨ Network features
License related to the duplication of the CPU
➨ Duplication license
➨ Identification of the CPU-Id concerned by the duplication


304
Main locks
Applications Call handling Clients Embedded
Phone-Book Analog sets Mobile UA Fixed UA Tier-IP AlcatelIP Voice Mail

LDAP Client (DECT) sets
- Contact Center
LDAP 4645
- OTUC
- OmniVista 4760
“n” x 10 “n” x 10 “n” x 10 “n” x 10 “n” x 10 “n” x 10 “n” = CS engine
- Notification server
E- Call Server
- Ubiquity e-CS P1 (80)
e-CS P4 (500) Alcatel 4645
e-CS P2 (150)
“Engines” e-CS P4 (+500)
Engine
e-CS P3 (250)
Corporate Networking APIs Media services

Management Proxy
•Accounting •API CSTA •A4635 •Attendant

•Management •API TSAPI •Security •VoIP Gateway (compression)
•Performances •API TAPI •VPS •Internal Accounting
•Alarms •API AHL •Automated attendant •Selective Routing (ARS / LCR)
•STAP (Phonebook) •Conference up to N •DECT Mobility
•Traps SNMP •Msg Recording •VPIM network
•ABC network management •Multilanguage Hotel •Portal
•ABCA & Infocenter


305
OPS files used
The number of OPS files depends on the costing tool

➨ Using e-Com
▼ Only one file
➨ Using Actis / ExpressQuote
▼ At least 4 files (5 with OmniVista 4760)
An offer generated by Actis is identified by an offer_id
➨ Example: au00403a
▼ au Initials of the ACTIS operator

▼ 004 Identification number of the customer for the BP
▼ 03 Major number of the offer made to the customer
▼ a Minor number of the offer made to the customer

An offer_id is generated by Actis for each new offer.

In case of an evolution or a migration, the OPS files are used to establish the base of the new offer. The offer_id don’t change.

306
OPS files used
Role of the different files
➨ offer_id.swk
▼ Contains the listing of the customer licenses and the software key
▼ This necessary file is the only one generated by the e-Com server
➨ offer_id.hw
▼ Contains the hardware description for the system
➨ offer_id.sw4760
▼ Optional file, this is the OmniVista 4760 license file
➨ offer_id.zip
▼ Archive used by Actis for addition and/or migration
➨ hardware.mao
▼ Copy of the file Offer_Id.hw for des compatibility reasons

For a system configured using e-Com, no file but offer_id.swk is necessary.

For compatibility reasons, this file will be copied in the Call Server database and renamed as software.mao
For a system configured using Actis / ExpressQuote, the files 1,2,4 and 5 are always there.
The file offer_id.sw4760 is only there if there’s an OmniVista4760 server attached to the OmniPCX.
The file offer_id.zip contains an electronic version of the whole technical folder and the different licenses.
This file is absolutely necessary to manage addition/migration using Actis / ExpressQuote.
The files offer_id.hw and hardware.mao are identical. The file hardware.mao is always present for compatibility reasons with
older versions of OmniPCX 4400.
The file hardware .mao is used by the Call Server to automatically configure the different IP Media Gateway and to fit the memory
for pour some applications.
The file offer_id.hw is used by Actis to handle evolutions.

307
Licencses and OPS files
OPS files used
The file offer_id.swk
➨ This file contains:
▼ The version of DLL used for coding this file
▼ The software key
▼ The date and time of generation of this file
▼ Le “handle 4760” witch allow to link this file with a 4760 license
▼ The identifier of the CPU (both CPU-ID in case of duplication)
▼ The version number of the software used to make the offer (OPS
version)
▼ The listing of the sold features

The file offer_id.swk is an ASCII file.
The software key is created from information stored in this file and encrypted with a secrete key.
The Call Server software allows to decipher the software key and then check the integrity of this file.
On site ,it’s possible to find until 3 CPU-Id in a license file;2 for CPU in duplication configuration and eventually another one for a
embedded voice mail system 4645.(AS or CPU-CS)
The meaning of the different parameters is given by swinst or directly by the command spadmin.

308
OPS files used
The file offer_id.swk
3031313000188be44e39618f9591af720028000400280012003a0014004e0028007621e900122
004012014185500143132333435364142002800010020383637323232583535303034374221e9
E0201000101999900020199990003020001999900040199990005019999000601000100070200
01999900080100010009019999001001000100110100010012010001001301999900140100010
01501000100160100010017010001001801000100190199990020019999002101999900220100
01002301999900240199990025019999002601999900270199990028020000000000290100030
03001000100310100010032010000003301000000340100000035019999003601999900370199
99003801000100390199990040019999004101000100420199990043019999004401999900450
19999004601999900470199990048019999004901999900500199990051019999005201000200
53010030005401003200550100040056010064005701006400580100640059010064006001006
40061010170006201000500630100640064010064006501006400660100640067010001006801
99990069019999007001999900710199990072019999007301000100740100010075010001007
60110000077019999007801000100790100010080010001008101000100820199990083019999
.................................................................
90844019999084501999908460199990847019999084801999908490199990850019999085101
99990852019999085301999908540199990855019999085601999908570199990858019999085
90199990860019999086101999908620199990863019999086401999908650199990866019999

Each software lock is encoded (just after the OPS version number, E0201 at the beginning of the line 3 in this example) following this
scheme:
Lock number (4 bytes) + Number of parameters for this lock (2 bytes) + Lock value (4 bytes)
Example: 0001019999
Lock number: 0001
Parameters number: 01
Lock value: 9999
Example: 00030200019999
Lock number: 0003
Parameters number: 02
Parameter 1 value: 0001
Parameter 2 value: 9999

309
OPS files used
The file offer_id.hw / hardware.mao
➨ This file contains the hardware description of the system
➨ It describes for each Media Gateway the listing and the type
of shelf used
➨ It describes for each shelf the type and the position of the
boards
➨ This file is not protected by a key
➨ It is also used for:
▼ Startup and locking the applications
▼ Initialization of the memory necessary for the applications

These are two ASCII files.

They can be modified by the technician on the site to solve troubles.
Some system limitations are directly modifiable in this file. Other limitations depending from the software version are taken into
account by the file config.mao.
In case of overflow of these limitations in the file hardware.mao, the system will consider the limitations defined in the file
config.mao.
This file may be modified through the command cfgUpdate (mtcl account).

310
OPS files used
The file offer_id.hw / hardware.mao
PRODUCT OXE
OPS E0201 FRTRFR02901A
OPS_MAO 02.00 OPS_OXE_Release 6.1
MAO_OPS 01.00 MAO_OXE_Release 6.1
VERS_4400 f1.600 VERS_OPS_4400 2.0.2
PARA_MAO 1 12500
PARA_MAO 2 512
PARA_MAO 3 512
PARA_MAO 4 512
PARA_MAO 5 0
PARA_MAO 6 1
PARA_MAO 7 2
PARA_MAO 8 1
.............
PARA_MAO 22 3
PARA_MAO 23 36582

Important Parameters in the file:

Product concerned (4400/OXE)
Version of the OPS used to generate the file and number of the complete offer in ACTIS
Version of the PABX that will receive these OPS files
Listing of parameters associated to the applications (PARA_MAO)
Hardware configuration (not displayed here)
Role of the different parameters MAO (Management Assisté par Ordinateur = Assisted Management by Computer):
PARA_MAO 1 Memory size for the Call Handling PARA_MAO 13 Number of Hotel consoles
PARA_MAO 2 Total subscribers number PARA_MAO 14 Number of ACD V1 supervisors
PARA_MAO 3 Total trunks number PARA_MAO 15 Number of multi-site CCS
PARA_MAO 4 Half-coms number PARA_MAO 16 Number of display languages for UA sets
PARA_MAO 5 Network / Stand-Alone PARA_MAO 17 Number of S0 buses
PARA_MAO 6 Simultaneous accesses to BLF PARA_MAO 18 Number of virtual sets
PARA_MAO 7 Phonebook size (x 2000) PARA_MAO 19 Number of shelves
PARA_MAO 8 Number of 4059 application PARA_MAO 20 ACR Function (Advanced Call Routing)
PARA_MAO 9 Unused PARA_MAO 21 Recording sets via CSTA (NICE)
PARA_MAO 10 4635 Voice Mail PARA_MAO 22 Add-On Conferences
PARA_MAO 11 4630 Voice Mail (unused) PARA_MAO 23 memory size calculated
PARA_MAO 12 4855 Fax Server

311
OPS files used
The file offer_id.sw4760
➨ This file is optional
➨ It contains the listing of the applications authorized for the

OmniVista 4760 server
➨ It is associated to the customer’s OmniPCX by the

“handle 4760” declared in the license file
▼ A license file is only valid for one customer
➨ It defines the limitations for the applications
➨ It is protected by a software key that grants the integrity of

this file.

Le “handle 4760” is a value with 8 octets allowing to leave the 4760 license independent to the CPU-Id .
Incase of CPU modification, a new file has to be generated for the OXE,and thanks to this « handle »any intervention will be
necessary.

312
OPS files used
The file offer_id.sw4760
[A4400]
Management = 1
Lock1 = 0223
[4760]
Version = 4
Signature = Gesda1Pmjbj54WWYXsxaw==WebynRjq1rwewoBKzndWuw==
[Modules]
Configuration = 5000
Alarms = 5000
Topology = 1
Accounting = 0
AccountingMonitoring = 0
PastTimePerformance = 0
Directory = 0
NmcClients = 10
Subscribers = 5000

This file is sort by section

In this example, the management of the OmniPCX 4400 and OXE is allowed, the file is linked to the hardware key number 223.
The file version is 4 (Release 2.1 for the OmniVista 4760)
The 4760 server applications are allowed if the associated value is greater than 1, and limited to this value if necessary (ex:
Configuration authorized but limited to 5000 subscribers).

313
OPS files used
The file config.mao
➨ This file doesn’t belong to the OPS files
➨ It is created by the system at the first startup
▼ If this file is deleted, it will be recreated at the next startup
➨ It contains the maximum limitations of the system
▼ The limitations depend on the software version installed
➨ It is possible to modify on site if necessary
▼ Command: cfgUpdate

These limitations won’t be overflowed.

If these parameters are modified, the new values will be take into account at the next reset of the system.
This file is mandatory, it is created with default values by the system.
The modification of this file allows to resize the memory allocated to the telephonic application depending on the customer’s needs.

314
Software protection
Control of the licenses
➨ In normal working mode, the Call Server checks every 4

hours the coherency of the protection elements
➨ It checks the coherency of the management data comparing

to the features bought by the customer
▼ In case of incoherency, the system switch to a degraded mode
➨ It checks that the CPU-Id matches the data in the licenses

file
▼ In case of incoherency, the system first considers that it is an
maintenance operation
▼ After 30 days, the system switch to degraded mode

The coherency can be checked using the command spadmin.

Menu 1 (Display current counters), look at the state of the « Panic Flag »(0 = OK, 1 = NOK).

315
Licenses OPS files
Software protection
Risks in case of fraud
➨ Legal Risks
▼ The software replication or the unlocking of features without

authorization is an illegal operation.
▼ Offenders will be liable to prosecution.
➨ Functional Risks
▼ When the Call Server software detects an incoherency between the

different keys or with the features, it switches to the degraded mode
and triggers some actions

System behavior in degraded mode:
action 1 (as soon as detected)

•display a warning to the attendant (acknowledge mandatory) as soon as she’s free.
•erase the terminal screen and display the incident message
•the incident is stored in the incidents file
•continuous ring on the alarm set
•some management commands are locked and just give the error: “Software protection error"
action 2 (4 hours later):
•display the message « Please call your administrator » on every set with screen
action 3 (8 hours later):
•Loop back on actions 1 et 2

316
Replacement of a CPU board
If a CPU board is replaced, the software key stored on the

Call Server is not valid anymore.
➨ The CPU_Id of this new board is different
The system can still work for 30 days
➨ After these 30 days, the system will switch to the degraded

mode
A new key has to be load on the system to recover a

normal working mode
This key can be downloaded through the e-Com server


317
Replacement of a CPU board
Replacement modes of a CPU board
➨ Case 1
▼ The technician registers the CPU change before the Hardware

Support received the defective CPU board
✦ Standard Service
➨ Case 2
▼ The technician registers the CPU change after the Hardware Support
received the defective CPU board
✦ Standard Service
➨ Case 3
▼ The Hardware Support registers the CPU board change and

reception
✦ Plug and Play Service

Operating modes depending on the case:
Case 1:
The technician replaces the defective CPU board by the new one and registers the exchange on the e-Com website
The technician sends the defective CPU board to the Hardware Support
The Hardware Support receives the defective CPU board and register the reception on the eLP (e-Licensing Product) website
The technician downloads the keys from the e-Com website and installs it on the customer’s system
Case 2:
The technician sends the defective CPU board to the Hardware Support. At reception, the Hardware Support registers it on the
eLP website
The technician receives a new CPU board and install it on the customer’s system
The technician gives the two CPU numbers on the e-Com website and downloads the licenses. Then, he installs the licenses on
the customer’s system.
Case 3:
Everything is done by the Hardware Support: registration of the change (through eLP) at the reception of the defective board and
license management for the customer
The working mode depends on the support contract of the customer.

318
Move licences
Licenses Moving between two systems
➨ The « Move » of license allow to use specific licenses

available (or became available) from a system to another
one
➨ This operation is possible:
▼ Only between two systems of the same customer
▼ Only concerning specifics licenses
✦ Licenses per user type (UA, Z, SIP, IP, etc…)
✦ Features Licenses (call by name, DECT mobility, CCd Agent)
✦ Compression Resources (G729)
✦ SoftPhone licenses

Licenses available (it could be change according to the next release):
Designation N° de license Role
10 UA fixed users 173 UA set numbers
10 analog users 174 Z set numbers
10 UA Mobile users 175 DECT set numbers
10 IP users 176 e-Reflexes set numbers
10 SIP users 177 SIP set numbers
10 OmniCellular client 308 Remote Extension set numbers
10 Phonebook users 2 Call by name numbers
Roaming DECT 90 DECT set numbers with mobility
DECT encryption 127 DECT set numbers with encryption
G729A client software 197 Numbers of G729 compressors
CCD 5 agents 76 CCD agent numbers
ECC My SoftPhone 129 WEB 4980 user numbers
ECC 4980 option 117 4980 user numbers

319
Move licences
Transfer example of SIP set between two sites

1 Register the new license file with the value decrease via the eLP server
2 Delete elements concerned in MAO on the A site
3 Install the new license file with the value decreased Server
eLP
4 Pick up the ACK code on A site
5 Register the new license file via eLP with the ACK code
6 Restore the new license file on B site
7 Make the management in MAO on the B site
ACK
Site A Site B

In case of Move licenses for users, it is important to check if the Engine size is correct to add users in the remote site (license n° 13).
The ACK code can be found via the spadmin tool or swinst.

320
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
321
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
322
Debugger

OBJECTIVE:
◆ To access to debugger and run a dumpsave
Alcatel OmniPCX Enterprise – Debugger

323
Kernel debugger
Overview
Kernel debugger (kdbg) is a program enabling:
➨ Retrieval of information on crashed sites
➨ Analysis will be performed by R&D

▼ dump of memory in a partition of the hard disk
➨ Restart of the CPU without using the CPU’s ON/OFF

button when the system has crashed
(access to console no longer possible, with or without
telephone)


324
Kernel debugger
Overview
Kernel Debugger entry can be invoked by:
➨ Automatic procedure when a serious error is detected on a

program
▼ Dump of memory
▼ Reboot of CPU
➨ Access by user when system has crashed

(access to console no longer possible, with or without
telephone)
▼ User access on console port only


325
Kernel debugger
Overview
User access on the console port

➨ Ctrl g and Ctrl o: all applications stopped
…
(6)xa000000>
Entering kdb (0xc0208000) due to Keyboard Entry
kdb>
➨ Read information, dump memory to disk, at the end of the

dump, restart the CPU
…
kdb>
kdb>ps
kdb>lsmod
kdb>ed
Dumping to device 0x311 [ide0(3,17)] ...
Writing dump header ...
Writing 32768 dump pages ............
…
Dump complete.
kdb> reboot
…


326
Kernel debugger
Overview
Warning
➨ In the case of maintained telephone operations

or of a site which need not restart immediately you must
imperatively contact Product support, who will effect the
entry in the Kernel debugger if required
➨ In the case of a duplicated site (the Stand-By becomes Main

upon entry in Kernel), you must keep the crashed CPU in
kernel and contact product support


327
Crashdump
Overview
Retrieves information on system crashes
In the case of an operating system crash, this tool

recopies the entire contents of the CPU memory into the
dedicated partition
The contents of this partition must then be copied as a file

in the directory /tmpd with dumpsave command
➨ This content can then be analyzed by R&D

The size of the file recopied in the directory /tmpd will correspond to the size of the CPU memory
examples: 128 Mb for the CPU-CS

328
Crashdump
Overview
To check whether the crashdump disk partition contains information

about the CPU crash
➨ When you login mtcl, if a crashdump has been stored, the
information returned will be the date and time of the crash
…
standard installation last performed: 04-May-2004 14:23:53
There is a crash dump on /dev/crashdump, date: 2004/05/05 10:37:41
# The role of the CPU is MAIN

…
➨ In the mtcl account, type the following command:

(101)xa001001> dumpsave –c
(101)xa001001>
➨ if no crashdump has been stored, the information returned will be

”it is not a dump file”


329
Crashdump
Overview
Options of the dumpsave command
(101)xa001001> dumpsave ?
Move the last crash dump to a regular file
Usage: dumpsave [option] [crash_dump_file]
Options:
-c display the date of the crash dump (if any)
-h display the crash dump header
-m display loaded modules at crash time
-a create a whole crash environment
-z compress archive (use with -a)
-o file specify the output file (default: stdout)
-r write the content of dump file (in binary) to the output file
-t tell if a valid dump exists in the dump file
(success means yes, failure means no)
-w remove the dump information from dump file
Default values:
crash_dump_file: /dev/crashdump
(101)xa001001>


330
Crashdump
What you have to do

➨ Dump the memory in the file named crash, under /tmpd
➨ You should then compress this file
(101)xa001001> dumpsave –r –o /tmpd/crash

….
(101)xa001001> gzip -9 /tmpd/crash
….
Or even better (from R5.1)

➨ Memory dump as well as other info such as incidents, …
▼ the output directory named “crash_date_time” is automatically
compressed compressed
(101)xa001001> dumpsave –a -z
…
(101)xa001001> l crash*
-rw-rw-r-- 1 mtcl tel 38037494 May 5 15:49 crash_20040505_103741.tgz
(101)xa001001>


331
Crashdump
Then get the file by ftp

Do not forget to remove this file from the disk after you
retrieved it
…
(101)xa001001>
(101)xa001001> cd /tmpd
(101)xa001001> l crash*
-rw-rw-r-- 1 mtcl tel 38037494 May 5 15:49 crash_20040505_103741.tgz
(101)xa001001>rm crash*
(101)xa001001>
Remove the message you get at mtcl root

[root@xa000001 /root]# dumpsave -w
…
[root@xa000001 /root]#


332
Crash dump retreival
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to generate a crash dump and retrieve the information
MANAGEMENT
1. Generate a Crash Dump by entering the kernel debugger.
2. Restart the CPU as well as the telephone application.
3. Check that the crash dump partition contains the crash (login mtcl).
4. launch the retrieval of the crash dump as well as the extra information using automated
backup and compression method.
4.1 From the telnet connection, use the command top to observe the most consuming
processes. What do you observe?
4.2 Use the ps –edf command to check it as well.
5. Use ftp to get the corresponding file on the management PC.
6. Please do not forget to delete the file on the PCX hard disk, and erase the message displayed
at mtcl login.

333
Crash dump retreival

334
TECHNICAL COMMUNICATION No. TC0500 Ed. 01
OmniPCX 4400/Enterprise Nb of pages : 9 Date : 07-11-2003
URGENT
NOT URGENT TEMPORARY PERMANENT
SUBJECT : EASY USE OF KERNEL DEBUGGER UNDER CHORUS AND LINUX
The purpose of this technical communication is to described how to enter manually into the debugger
and run the crashdump in case of CPU blocking.
1
335
336
OmniPCX 4400/Enterprise
EASY USE OF KERNEL DEBUGGER UNDER
CHORUS AND LINUX
CONTENTS
1. PURPOSE .....................................................................................3
2. USE .............................................................................................3
3. SYNTAXES ...................................................................................4
3.1. Access to kernel debugger........................................................................ 4
3.2. Chorus syntaxes........................................................................................ 4
3.3. Linux syntaxes........................................................................................... 5
4. AFTER THE CRASHDUMP .............................................................6
Ed. 01 / 07-11-2003 1 TC0500

337
CHORUS AND LINUX
TC0500 2 Ed. 01 / 07-11-2003

338
CHORUS AND LINUX
1. PURPOSE
In situations of CPU blocking (any type of Alcatel CPU board and Appliance Server), a single reboot
of the machine is not sufficient to investigate and to understand why the CPU crashed.
Indeed, it is completely possible that the mechanism of storage and system messages display is itself
blocked. So, when rebooting no information will be available and the diagnosis will be very difficult.
The types of blocking are:
− No longer dialog on the machine (v24/ Ethernet) and no longer telephone but the system has
not restarted.
or
− No longer dialog on the machine (v24/ Ethernet) but the telephone application functions yet.
Under Chorus and Linux, a system debugger has been embedded. It is accessible most of the time
even in these blocking situations. This debugger is used to analyze the RAM and also to generate a
dump of this RAM: this dump consists of taking the complete CPU RAM and putting it in a dedicated
part of the disk. After the reboot, these information can be saved as a file of the disk and supplied to
Support and R&D teams for analysis. This file is called crashdump. In some cases of CPU crash,
this feature is activated automatically: in that case, the crashdump generation and the reboot are
automatic.
The debugger ("kernel debugger") can be launched only on the console port (/dev/console) even
if the v24 ports are blocked.
Note
If the hard disk is in a critical status, it is likely you cannot generate manually or automatically this
crashdump.
The purpose of this technical communication is to described how to enter manually into the
debugger and run the crashdump in case of CPU blocking.
2. USE
When logging mtcl, an information is supplied if there is a crashdump.
Example
Note
A crashdump does not take more disk space. Indeed, during the formatting, this space disk is
systematically reserved.
In the situations of CPU blocking, you need to generate manually this dump when there is no more
access to the machine (no longer v24, no longer IP).
Note
Capture anything it happens from the access to the debugger up to completed reboot.
Ed. 01 / 07-11-2003 3 TC0500

339
CHORUS AND LINUX
3. SYNTAXES
3.1. Access to kernel debugger

Two ways are available to access to kernel debugger :
1 the first one stops completely the telephone (but without automatic reboot): the reboot of the Call
Server or CPU board takes place when quitting the debugger,
2 the second one puts the system in halt: the telephone will probably operate when quitting the
debugger (without warranty). If a crashdump is generated then a reboot is automatically
performed when quitting.
The way to access to the debugger is carried out as follows:
− Press the keys Ctrl g then Ctrl o to access to the first mode.
− Press the keys Ctrl g then Ctrl p to access to the second mode. This mode is better for the
crashdump.
In some circumstances of crash, only the 1st mode can be used. Specify the way to access to the
debugger when you describe the default.
From this step, use either the Chorus or Linux syntaxes.
3.2. Chorus syntaxes

− A message is displayed:
** Entry in the debugger requested, eip = 0xff8d6055

** Press <return> within 30 seconds to enter into the kernel debugger.
** Press <r> or do nothing to reboot.
=>
− Press the key Enter within 30 seconds (otherwise reboot) to display the debugger kdbg>
prompt.
--- Enter Debugger

--- Thread 53 Actor a0000 5 (DM) Int Level 0
ff8d6055 DM:putcbp+12f99 popl %ebp
kdbg>
− Some commands are available. The most important ones are:

• ?
Display of the help.
• L
Equivalent to the command limitsinfo. List some maximal data (maximum, current data
and maximum reached during the life of the machine).
TC0500 4 Ed. 01 / 07-11-2003

340
CHORUS AND LINUX
• u uL et ul:
Data of Chorus processes.
• Ee
Submenu of information on Ethernet (I for the statistics IP, x to quit).
• ED
This command generates the crashdump.
Example
If telephone is running, telephone won't be available from now until next

reboot
Sysdump request from kdbg
dumping 32768 pages on dev 13
..........................................................................
......................................................
32768 pages written on dumpdev
0 bad ptbls
0 bad pages
kdbg>
• ZZ
This command is to be launched after ED so that the machine reboots.
• c
Exit of the debugger. If the access was carried out with Ctrl g then Ctrl p and there was
no required crashdump then there is a return to the previous status. There is no warranty of
stability of the system at this moment.
− An other sequence of keys managed by Chorus is available:
• Ctrl g then Ctrl c
This sequence is to be applied when a Unix process launched in foreground does not "return
any more the hand". Then you return to the login (and not into the shell).
3.3. Linux syntaxes

− After the access sequence, press the key Enter to display the prompt kdb. There is no 30
seconds time-out before the reboot like with Chorus.
− Commands:
• ps
List of processes. The display is in paginated mode. Press the key Enter for the next pages.
• lsmod
List of loaded modules.
• ed
Generation of the crashdump.
• reboot
Reboot of the board. To be launched after the command ed.
Ed. 01 / 07-11-2003 5 TC0500

341
CHORUS AND LINUX
• go
Equivalent to the command c of the Chorus kdbg.
Note
Some commands supplied above are given for information purpose: the crashdump itself is
sufficient. On client installation, the Technical Support and R&D recommendations are to access only
to the debugger in order to generate the crasdump and to reboot the Call Server or CPU board via
the associated debugger command (ZZ or reboot). This method is to be applied to get reliable
information.
4. AFTER THE CRASHDUMP

To save the crashdump as a file, follow the procedure below.
When a crashdump is present on the disk, the following message is displayed when you log on the
system:
There is a dump on /dev/dsk/crashdump from <date>, <time>
Use the following command to extract the crashdump:
a4400> dumpsave –r –o /tmpd/mycrash (where "mycrash" is the name you give to the
extracted file).
From Release 5.0 Ux, the size of the file is 128 MB.
Use the following command to compress the file on the system :
a4400> gzip /tmpd/mycrash (where "mycrash" is the name of the file).
For not having the message of crash during the login, enter the dumpsave -w command. In any
case, the /dev/crashdump file must be deleted; it is not the crashdump but a file of "device" type.
This command deletes the display but not the crashdump. This latter is located in a inaccessible disk
partition and systematically present (128 MB). When installing a blank disk, there is no data in this
partition. During a crash, the CPU memory transfers its data into it but the size of the partition does
not change.
From Release 5.1, new options have been added to the dumpsave command:
− -a
This option checks if there is a crashdump and creates a directory under /tmpd.
This directory is named as follows:
crash_<year><day><month>_<hh><mn><sec> (the time corresponds to the date of the
crash)
Example
crash_20031607_130000
The directory corresponds to a system crash generated on the 16th of July 2003 at 13H.
In this directory, the following information are added:
• the crash file already compressed,
TC0500 6 Ed. 01 / 07-11-2003

342
CHORUS AND LINUX
• text files of incvisu commands (included this 3 latest),

• the same thing for excvisu,
• the 4 files of "DHS3-INIT"
these files are those taken when launching the command. They do not correspond to the
ones when the crash happens (if there are too many reboots after the crashdump, no
incident file will not correspond to the crash).
• -z
This option is to be added after the "-a" option. The result is the same as previously but instead
of creating the directory, there will be only one compressed file containing the tree structure and
all files of the "-a" option. This file has the same name as the directory.
This command can be launched under mtcl or root. Launched under root, it can only be
launched again under root since there is no rights to erase the directory file under mtcl.
To erase the file or the directory, enter the command (under root or mtcl depending on the
being part) :
rm -r -f crash_xxxxx
The dump –a –z command is especially interesting and is to be used systematically from
Releases 5.1.
Add the compressed file to the observation sheet.
Ed. 01 / 07-11-2003 7 TC0500

343
CHORUS AND LINUX
TC0500 8 Ed. 01 / 07-11-2003

344
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
345
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
346
Security: Aging passwords

OBJECTIVE:
◆ To describe the “aging password” facility
Alcatel OmniPCX Enterprise – Security: Aging passwords

347
System accounts passwords
Problematic and solution
Even if some security rules are implemented for the system

accesses, if the accounts passwords are known by a none
trusted person, sooner or later your system can be hacked
➨ To secure the system access, one of the security principle is

to frequently change the “users” passwords
➨ In addition to the other security facilities, the “aging

passwords” facility allows to force the administrator to
change the password of all accounts
▼ A period of validity is configured while activating the aging password
facility
✦ As soon as the end of this period is reached, at the first next login (even if
it is 10 days after the end of the period), the administrator is requested to
change the passwords


348
System accounts passwords
System installation
After the system loading, at the first login, the technician is

asked to secure the system. In fact, that corresponds to a
phase of default system passwords modification
▼ Do you want to secure passwords (Y/N/L for later, default Y)?
✦ If the answer is “L” the question will be asked again at the next login
✦ If the answer is “Y”, the technician accesses directly to the “aging

passwords” configuration menu
✦ If the answer is “N” the question is not asked again

To validate this function later it is necessary to use “swinst” (refer to the
configuration module)
After the passwords modification, it is possible to activate

the “aging password” facility (optional)


349

350

OBJECTIVE:
◆ To activate the Aging password facility

351
Aging password
Activation
To activate the “aging password” facility, the modification

of all the accounts passwords has to be activated first
➨ “swinst”
▼ 2 Expert menu
▼ 6 System management
▼ 5 User's accounts management
▼ 2 Change account aging passwords
Result on the screen:
Current aging password status:

[root] - Not activated
[swinst] - Not activated
[mtcl] - Not activated
[adfexc] - Not activated

Aging passwords: if this option is validated then the passwords must be changed when the delay is expired.
For adfexc you have to select the option “Change 'adfexc' password” in the “user’s accounts management in swinst

352
Aging password
Activation
Aging password activation for “mtcl” account for a

duration of 11 days:
Enter a username: mtcl
How many days do you want to keep validate passwords (10<X<366, 0 for no aging) ? 11
Done Aging password
Press return
configuration
Result on the screen:

Current aging password status:
[root] - Not activated
[swinst] - Not activated
[mtcl] - 11 days / last change 0 days ago, 11 days left
[adfexc] - Not activated
Next connection to “mtcl” account the password has to be

changed


353

354
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to activate the “aging passwords” security facility
MANAGEMENT
1. Force the modification of all the accounts passwords at the next “login”
2. Password modifications :
2.1. Log in as “root” and modify all the passwords
- root: Entp374@
- swinst: 0531@uS
- mtcl: 1A2d3f
- adfexc: h01@teUS
2.2. Activate the aging passwords. The periodicity has to be 21 days
2.3. Modify the date (add one month to the current date)
3. Return to the default configuration (only desirable for the following labs)
3.1. Log in as “root”. The systems ask you if you want to secure the system (“aging
functioning”). Change again the passwords.
- root: Entp0531
- swinst: TEus@531
- mtcl: 0494@teUS
- adfexc: HandsOn1
3.2. Answer “no” to the “aging” activation question !
3.3. To manage back the default system password, use the “passwd” command under “root”
account

355

356
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
357
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
358

System Expert PDF

Uploaded by

Document Information

Original Title

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

System Expert PDF

Uploaded by

Copyright:

Available Formats

Alcatel OmniPCX Enterprise

Technical Training offer

Learning Solutions Catalog 2006 All rights reserved © 2006, Alcatel

represents training courses involved in ACSE certification

represents training courses involved in ACFE certification

I=xh C=xd V=xd

I = x h stands for Individual learning, in hours

Learning Solutions Catalog 2006 All rights reserved © 2006, Alcatel

Learning Solutions Catalog 2006 All rights reserved © 2006, Alcatel

OMNIMESSAGE 4635 EXPERT: GET AUTONOMY

HOTEL / HEALTHCARE: RUN BUSINESS

Learning Solutions Catalog 2006 All rights reserved © 2006, Alcatel

Learning Solutions Catalog 2006 All rights reserved © 2006, Alcatel

Learning Solutions Catalog 2006 All rights reserved © 2006, Alcatel

Learning Solutions Catalog 2006 All rights reserved © 2006, Alcatel

Learning Solutions Catalog 2006 All rights reserved © 2006, Alcatel

REFERENCE ENTPTE403US DELIVERY LANGUAGE English (course material in English)

Virtual self-paced training on the computer

4 days Traditional classroom or practical sessions with tutorials (TAP LAB)

Tutored virtual training sessions accessible via an internet connection

MAXIMUM NUMBER OF PARTICIPANTS 12

At the end of the course, the participant will be able to:

Describe the principles of the software loading

ISSUE DATE ISSUE DATE

Alcatel OmniPCX Enterprise System Expert

File reference: ENTPTE403US

CORE CURRICULUM AND CATALOG PROGRAM DESCRIPTION

3. Schedulable patch downloading from OmniVista 4760

Issue 01 REF. ENTPTE403US 0.1

5. Speed Dialing by range

7. IP Media Gateway Signaling Backup

9. Creation of simple scripts

10. Software locks

11. Kernel Debugger & Crash dump

12. Security: Aging Passwords

0.2 REF. ENTPTE403US Issue 01

SECTION CHAPTER PAGE DESCRIPTION OF THE ERROR

Issue 01 REF. ENTPTE403US 0.3

0.4 REF. ENTPTE403US Issue 01

© Copyright Alcatel Business Systems 2005

◆ To describe the OmniPCX Enterprise loading tool PC Installer

◆ To describe the software loading principles

◆ To describe the different loading cases

◆ To describe the procedure depending on the type of CPU

◆ To describe a complete software loading procedure

◆ To describe a version updating with a patch

Alcatel OmniPCX Enterprise – CS software loading

Loading tool OmniPCX Enterprise PC Installer

Software loading generalities

Loading tool interface

Complete release loading (Linux +call handling)

Release or patch loading

© Copyright Alcatel Business Systems 2005

Alcatel OmniPCX Enterprise – CS software loading

The OmniPCX Enterprise PC Installer ensures:

➨ The loading of all software type

▼ Linux operating system

▼ Correcting patch (for Linux and/or telephone)

▼ Specific soft for GA / GD

➨ The loading of all CPU type

▼ IP Rack Server => CPU-CS

▼ IP Appliance Server => IBM server

▼ IP Crystal Server => CPU5 / CPU6 / CPU7