AASTQA

Telephony System Installation

Chapter 2 - Telephony System Installation 2

2.1 Objectives 2

2.2 Glossary 2

2.3 General Overview 3

2.4 Installation Prerequisites 3

2.5 Network Connectivity 3

2.6 Telephony System Installation Process Overview 4

2.7 Installation with Recovery DVD 5

2.8 Installation with Media Kit DVD 8

2.9 Setup for network communication 10

2.10 Additional configurations 18

2.11 Start MX-ONE Telephony system configuration and installation 18

2.12 Exercise: Telephony System Installation 26

LZU 103 1013 Rev B

Page 1 of 26

A4STQA

Telephony System Installation

Chapter 2 - Telephony System Installation

2.1 Objectives

The objectives for chapter 2 are:

o Describe the different approaches to install and start a Telephony System

o Describe the installation with recovery DVD

o Describe the installation with Media Kit DVD

o Complete Telephony System configuration

o Describe the software installation

o Describe Telephony System configuration files.

o Complete Telephony System installationSetup communication with media gateways

2.2 Glossary

Acronym Definition
CPI Customer/partner library
ESU Embedded Server Unit
ICT Installation and Configuration Tool
LSU-E LIM Switch Unit - Ethernet
EMG Enterprise Media Gateway(a type of media gateway)
MGU Media Gateway Unit (a type of media gateway)
RTP Real Time Protocol
SLES SuSE Linux Enterprise Server
SSH Secure Shell
TOM Time Division Multiplexing
TS Telephony System Conventions

o Commands or parameters in the text of the document are quoted in quotation marks, " ..... /1. When using the commands and parameters on the command line, the quotation marks are omitted.

o Commands are shown in Courier 12pt bold. The command prompt is not bold.

LZU 103 1013 Rev B

Page 2 of 26

Telephony System Installation

2.3 General Overview

The Aastra MX-ONE Telephony System can comprise one or several servers. Before MX-ONE 4.0 we used to talk about LIMs and a LIM used to be a server plus a media gateway, were server and media gateway could be of different types. Server could be "Standard (HP)" or "ESU (Embedded Server Unit)" (with or without fan) while media gateway could be the EMG or the LSU-E. With MX-ONE 4 a new type of media gateway is introduced - the MGU (Media Gateway Unit).

With the introduction of MX-ONE 4.0 a "LIM" is now a server which is capable of handling up to fifteen media gateways.

Each server is assigned a server number. During software installation server 1 is used to copy the installation files and to distribute the configuration data to all other servers. Two configuration files on server 1 ("jetcjeri_ts.conf" and "jetcjsystem_conf.xml") control the installation. Installation files are created by ICT.

2.4 Installation Prerequisites

Before proceeding with the software installation:

o Make sure all hardware meets the minimum requirements and is properly installed and all cables are firmly connected

o Check whether all necessary information regarding the network infrastructure (IP addresses, subnet masks, default gateway, hostnames, domainname ... ) is available

o Have the necessary hardware available (external DVD reader, USB hub, floppy or USB stick ... )

o Prepare the software (SLES 10 SP3 DVD, Recovery DVD, Media Kit DVD)

2.5 Network Connectivity

Depending whether redundancy is used or not the involved systems are connected to one or two networks.

2.5.1

No redundancy

When redundancy is not used one LAN is used for the MX-ONE Telephony System. The media gateways of type LSU-E and EMG use different LAN ports for control (signaling) and media. Thus they have direct links (used for signaling) to their controlling Telephony Servers. As the direct links are unique per server the same network addresses can be used for this link in each server.

On the media gateway of type MGU both control (signaling) and media is accessed on both of the LAN ports. To each port two addresses can be assigned (one for being used for control and one for media).

LZU 103 1013 Rev B

Page 3 of 26

Telephony System Installation

In a non-redundant network only one of the two LAN ports of the MGU is used.

Figure 1: Connectivity without redundancy

2.5.2

Redundancy

When redundancy is used all the IP addresses have to be unique. The previously direct link between the media gateway of type LSU-E or EMG is now established over one of the networks.

The media gateways of type EMG need to be connected with both LAN ports to one of the networks since they use different LAN ports for control and media. They should be alternated to use either network.

The media gateways of type LSU-E can be connected in parallel, that is, all their level 2 switches can be connected to one LAN. Media is handled by the IPLU boards.

Figure 2: Connectivity with redundancy

2.6 Telephony System Installation Process Overview

To perform a successful installation it is necessary to prepare all servers with the installation files, a proper network configuration. The installation can be started from server 1.

Aastra MX-ONE Telephony System installation consists of 5 steps.

o Step 1: Installation of Linux OS on the servers

o Step 2: Use command "sh /rnedla/ .... /MX-ONE_install_verx.x.bin tk" to prepared MX-ONE Telephony system installation on all servers

o Step 3: Reboot and continue with system configuration

o Step 4: Setup for network communication (network configuration)

LZU 103 1013 Rev B

Page 4 of 26

Telephony System Installation

Step 5: Use command "ts_startup" on server 1 to start up MX-ONE Telephony system configuration and installation

There are two different approaches to go through these 5 steps:

o Installation with Recovery DVD

o Installation with Media Kit DVD

2.7 Installation with Recovery DVD

"Recovery DVD" is a SLES 10 with SP3 installation DVD with three additional files. Two of them are located in the folder /MXOne (the MXONE_installxxx.bin and a script that installs the *.bin) and the other one is in the root of the DVD (autoinst.xml).

The following screenshots show an installation with Recovery DVD.

Screens hot 3: Boot from Recovery DVD, select "Installation"

Booting from Recovery DVD and selecting "Installation" in the boot menu initializes an Aastra customized, script controlled, un-attended installation of SLES 10 SP3.

LZU 103 1013 Rev B

Page 5 of 26

Telephony System Installation

Screenshot 4: Script controlled installation (autoinst.xml)

The file /autoinst.xml contain all the information that is needed during installation (partitioning, packets to install, root password and so on) so no interaction is required.

LZU 103 1013 Rev B

Page 6 of 26

Telephony System Installation

Additionally the autoinst.xml contains the information that a script is executed at the end of the SLES 10 SP3 installation. This script performs a "turnkey installation" .

At the end of the installation you can log on to Linux and reboot the system.

Screenshot 5: Log on and reboot the system

After reboot, the system welcomes you with the following screen:

Screenshot 6: Welcome to Aastra MX-ONE Telephony System

The Installation with Recovery DVD has performed the steps 1, 2 and 3 of the 5-step-installation and we are now about to start with step 4.

MX-ONeM servers, delivered by Aastra, come preinstalled with "Installation with Recovery DVD" and the DVD comes with the server.

LZU 103 1013 Rev B

Page 7 of 26

Telephony System Installation

2.8 Installation with Media Kit DVD

Prerequisite for the Media Kit installation is an Aastra customized installation of SLES 10 SP3 which can be done with the help of the autoyast configuration file (profile) autoinst.xml.

The following screenshots show a Media Kit Installation:

Screenshot 7: Start Media Kit Installation by executing the MX-ONE_installxxx.bin tk

The file MX-ONE_installxxx.bin consists of a shell script and a tar.gz archive separated by a separator line. Executing the file means that the shell script is started.

Purpose of the shell script is to unpack the tar.gz archive and copy its content to appropriate directories on the server.

Screenshot 8: Unpacking files, please wait ...

After the files are unpacked a menu offers the choice between "Software Installation" and "Turnkey Installation". These options can be given directly

LZU 103 1013 Rev B

Page 8 of 26

Telephony System Installation

when executing the MX-ONE_installxxx.bin file with option "tk" (Turnkey Installation).

At the end of the Media Kit Installation you will see the following screen:

Screenshot 9: Installation with Media Kit Installation complete, reboot the system

After reboot, the system welcomes you with the following screen:

Screenshot 9: Welcome to Aastra MX-ONE Telephony System

The Media Kit Installation has performed the steps 2 and 3 of the 5-stepinstallation (step 1 needs to be done manually) and we are now about to start with step 4.

Installation with Recovery DVD and Installation Media Kit Installation end with step 3 of the 5-step-installation-process and both continue with step 4. The only difference is the installation of the Linux OS. Installation with Recovery

LZU 103 1013 Rev B

Page 9 of 26

Telephony System Installation

DVD includes the installation of Linux OS while this is not included in Media Kit Installation.

2.9 Setup for network communication

Step 4 which is in common for Installation with Recovery DVD and Media Kit Installation is to configure the server for network communication. This is done by configuring IP addresses and subnet masks for each of the two network interfaces as well as default gateway, hostname and domain name.

The following screenshots show the configuration:

Screenshot 101: Welcome to Aastra MX-ONE Telephony System

If you select "No" in the above screen the system will shutdown and halt

Screenshot 112: Shutdown and halt of the system if "No" was selected

LZU 103 1013 Rev B

Page 10 of 26

.A4ST~A

Telephony System Installation

Choosing "Yes" in the "Welcome"-screen prompt you for distinguishing between server 1 or any other server.

Screenshot 123: Select "Yes" or "No"

This question is necessary because on server 1 two additional things are done:

o Creation of the file /sbin/ts_startup. This file is later used to start the "Main Installation" from server 1. The file /sbin/ts_startup starts the command /home/eri_sn_admin/install_sw/ts_conf_install with special parameters to start installation

o Prompting for USB storage device or floppy disk with config files "eri_ts.conf" and "system_conf.xml" in the root of the media

Screenshot 134: On server 1 prompt for configuration files

If you answer the above question with "Yes" you will see the following screen:

LZU 103 1013 Rev B

Page 11 of 26

Telephony System Installation

Screenshot 145: On server 1 insert media with configuration files (in the root of the media)

Now insert the floppy disk or plug the USB storage device. The media must contain two files "eri_ts.conf" and "system_conf.xml" in the root of the media. This procedure will not look in subdirectories on your media. The purpose of this procedure is to copy the two files from the media to directory jetc on your server (server 1).

In case the media is detected and the files are copied successfully you will see the following screen for a short moment:

Screenshot 15: On server 1, do not remove media

In case the media is not detected or there are no appropriate files in the root of the media the following message is displayed:

LZU 103 1013 Rev B

Page 12 of 26

A4STQA

Telephony System Installation

Screenshot 16: On server 1, no media detected

You can continue to try to read the files from a media by selecting "Yes" or select "No" to proceed to the prompt for IP address of ethO.

Even if you have already existing configuration files (eri_ts.conf and system_conf.xml) you should answer the question

Screenshot18: On server 1 prompt for configuration files

with "No". You can mount the media later and copy the configuration files to the directory jetc.

In any case (configuration files copied from a media or not), the next step is to insert the IP address of ethO:

Insert IP address for ethO.

LZU 103 1013 Rev B

Page 13 of 26

Telephony System Installation

Screenshot19: IP address ethO Insert subnet mask for ethO.

Screenshot 17: Subnet mask ethO

Insert IP address of the default gateway for ethO

LZU 103 1013 Rev B

Page 14 of 26

Telephony System Installation

Screenshot 181: Default gateway Insert IP address of the ethl

Screenshot 192: IP address ethl Insert subnet mask for ethl.

LZU 103 1013 Rev B

Page 15 of 26

A4.STQA

Telephony System Installation

Screenshot 203: Subnet mask eth 1

Insert hostname.

Screenshot 214: Hostname

This is case sensitive! (Not case sensitive for DNS but case sensitive for the installation process, that is, the hostname has to be typed in the same case later in leT).

Insert domain name for this server.

LZU 103 1013 Rev B

Page 16 of 26

Telephony System Installation

Screenshot 225: Domain name Summary

Screenshot 23: Summary

LZU 103 1013 Rev B

Page 17 of 26

Telephony System Installation

Screenshot 24: Network configuration complete

Now you can log on to server 1 and continue the installation (Step 5).

2.10 Additional configurations

One of the opportunities where you can log on to the system during the previous installation steps should be used to configure things like

o keyboard layout

o time zone

o date and time

If it was not already done, now is the moment to do it (on server 1 switch to another console, log on and use "yast", on other servers simply log on and use "yast").

2.11 Start MX-ONE Telephony system configuration and installation

liml:~ # ts_startup

The file /sbin/ts jstartup starts the command /home/eri_sn_admin/install_sw/ts_conf_install with special parameters to start installation.

Screenshot 28: leT is up

Now you can connect to ICT. If you use a remote machine connect to http://192.168. 100.10/ICT where "192.168.100.10" is to be replaced by the IP address of your server 1. If no other machine is easily available you may want to connect by using another terminal. Configure the terminal with "sax2" (only if default configuration of 1024x768 specified in the xml file is not

LZU 103 1013 Rev B

Page 18 of 26

A4ST~A

Telephony System Installation

suitable for you), change to runlevel 5 with "init 5", log on, start a browser and connect to http://192.168.100.10:8080/ICT.

ICT is a web based application to create or modify the configuration files for the installation. These plain text files are "eri_ts.conf" and "system_conf.xml" and both are located in directory jetc.

When you connect to ICT, it reads these two files (by default there is an "eri_ts.conf" containing some default values but there is no "system_conf.xml") and shows the content of this files.

In ICT you can modify the configuration and finally save this configuration. The result is that the two configuration files are created (or overwritten if they already exist).

_?_t.~_nq.~_~", .. ",.. L:±I

Manager Provisioning _:.tl

Screenshot29: ICT, tab "General"

Enter general information. Help is available by clicking "?".

(D U~eHTIPS

(f) Web Server Port

(1) Certificate,

(j)Uplcad Security File

d)SeC!lrityFile (1) POI:;sword

(.1) Email Adoress

,?!) oeserv Code Point for Medi<l

Ci) rnns erv Code Point for Cal! Control (f::' NTP server

Screenshot 250: ICT, tab "General"

LZU 103 1013 Rev B

Page 19 of 26

AASTQA

Telephony System Installation

Screenshot 26: ICT, tab "LIM", click "Add"

(1) LIM Number

\l) Server Host Name

® Use Redundant Net~c1k i:!) server type

Screenshot 32: ICT, LIM configuration

Insert configuration data of your LIMs.

LZU 103 1013 Rev B

Page 20 of 26

Telephony System Installation

Screenshot 33: ICT, 2 LIMs configured

This is the summary view of the configured LIMs.

Screenshot34: ICT, configuration files written successfully

This screen indicates that the files /etc/eri js.conf and /etc/system_conf.xml were successfully written.

Screenshot35: ICT, tab "Cluster" (Redundancy configuration)

The tab "Cluster" is used to configure a system with Redundancy. Servers can only be members of a cluster if during configuration of the appropriate server the checkbox "Use Redundant Network" was activated (refer to chapter "Redundancy" for more information).

LZU 103 1013 Rev B

Page 21 of 26

Telephony System Installation

Screenshot36: leT, tab "Import/Export"

The tab "Import/Export" makes it easy to copy the files /etc/eri j.s.conf and /etc/system_conf.xml between your server 1 and the machine where your browser is running on. Of course you can mount a media on your server 1 as well to import or export the configuration files.

Now that the configuration files are created the "main installation" (system installation) can be started. To do this, return back to ttyl of server 1 where you still should see the following screen:

Screenshot37: leT is up

As instructed, press enter key. This will start the installation of the system.

LZU 103 1013 Rev B

Page 22 of 26

Telephony System Installation

Screenshot38: System Installation Starts

Screenshot 39: System Installation progress

On the screen the screen the progress of the system installation is displayed. In case the installation runs successfully you should see a screen similar to this after a while:

LZU 103 1013 Rev B

Page 23 of 26

Telephony System Installation

Screenshot 27: The installation has finished successfully!

In case that the installation failed for some reason the screen will look similar to this:

Screenshot 28: The multi server installation failed.

The installation program prints on the screen what was the problem during installation and why the installation failed. Additionally there are instructions how to restart the installation after the problem was corrected.

After correcting the indicated problem (preferably from a different terminal) come back to ttyl, log of, log on as eri_sn_admin and perform the task as instructed.

The following screenshot displays the procedure:

LZU 103 1013 Rev B

Page 24 of 26

Telephony System Installation

Screenshot 42: The multi server installation failed.

The System Installation starts again "Getting LIM data

"

LZU 103 1013 Rev B

Page 25 of 26

c o :;:; I1J

I1J ....... Vl C

......

E

Q) ....... Vl >(J)

>C o .c D.. Q)

Q) I-

c
0
.I-J
CO
CO
.I-J
Vl
C
1--1
E
OJ
.I-J
Vl
>-
(J)
>-
C
0
...c
0...
OJ
OJ
I-
OJ
Vl
~ U
!....
OJ
i ><
W
N
T-i
.
N -
.-
ra
.,
Q)
C
.......
"C
C
ra
E
E
0
u
0
'<:j"
L.U
Z
0
I
X
::;E
4-
0
C
0
P
ro
-
-
ro
.,_,
Vl
C
C ._
0 c
., ro
V E
::J
J.. I....
., 0
III 4-
I....
C Q)
t-I 0.. \.D N

"o

\.D N Q) OJ I1J 0...

co > Q)

0::: ('I') ,....,

a ,....,

('I') a ,....,

::J N ....J

Media Gateway Setup

Chapter 3 - Media Gateway Setup 2

3.1 Objectives 2

3.2 Glossary 2

3.3 General 4

3.4 Setup Process 4

3.5 Enterprise Media Gateway and Media Gateway Classic 5

3.6 Media Gateway Unit 11

3.7 Assigning a Media Gateway to a Server 19

3.8 RTP Resources 23

3.9 System Preparation 25

3.10 Update/Read Hardware 25

3.11 Exercise: title 27

LZU 103 1013 Rev B

Page 1 of 26

Media Gateway Setup

Chapter 3 - Media Gateway Setup 3.1 Objectives

The objectives for chapter 4 are:

o Describe the setup procedure

o Setup Enterprise Media Gateway, EMG

o Setup Media Gateway Classic, MG-C

o Setup Media Gateway Unit, MGU 3.2 Glossary

Acronym Definition
ALEX Active Library Explorer
ESU Embedded Server Unit
LIM Line Interface Module
LSU-E LIM Switch Unit - Ethernet
EMG Enterprise Media Gateway (a type of media gateway)
MG-C Media Gateway Classic (a type of media gateway)
MGU Media Gateway Unit (a type of media gateway)
NFS Network File System
RTP Real Time Protocol
SLES SuSE Linux Enterprise Server
SM Server Media Gateway (ESU and Media Gateway in one
chassis)
SM-H Server Media Gateway Hybrid (ESU and MGU in a 3U chassis)
SSH Secure Shell
TDM Time Division Multiplexing
TS Telephony System Conventions

o Commands or parameters in the text of the document are quoted in quotation marks, " ..... ". When using the commands and parameters on the command line, the quotation marks are omitted.

o Commands are shown in Courier 12pt bold. The command prompt is not bold.

o The phrase "Telephony Server" is used to refer to any server (HP DL360, ESU or other) that is used in a LIM as part of the MX-ONeM Telephony System installation.

LZU 103 1013 Rev B

Page 2 of 26

Media Gateway Setup

3.3 General

Before starting with the setup of the media gateways we need to distinguish between the different types, modes and connections.

There are three different types of media gateways:

o Enterprise Media Gateway (EMG)

o Media Gateway Classic (IPLU)

o Media Gateway Unit (MGU)

All media gateways have a "boot mode" were the operating system (Linux) is not running and a "Linux mode".

A connection towards all three types of media gateways can be established via a serial connection (control over boot mode and Linux mode or via network connection with protocol SSH (control over Linux mode only).

The Media Gateway Unit supports additionally connections via USB (control over Linux mode only).

On EMG and Media Gateway Classic some important communication parameters (boot mode IP addresses, NFS server) can be set only in boot mode.

Media Gateway Classic can, however, from version 1.4_5, R3A set these parameters in application mode too.

The Media Gateway Unit gives read and write access to these parameters in Linux mode.)

Previously (before MX-ONE 4) the type of the media gateway and the IP address of ethO of the media gateway, was specified during installation process (in ICT respectively the created configuration files). It was not possible to change the type of media gateway after installation. Additionally a Telephony Server could control only one media gateway.

In MX-ONE 4 the media gateway is assigned to a Telephony Server in Manager Telephony System (System - Hardware - Media Gateway) or by command (media_gateway_config) and the new Media Gateway Unit supports up to 15 MGUs or MG-C being assigned to one Telephony Server.

3.4 Setu p Process

The setup process consists basically of two steps:

o set communication parameters (ip adresses, nfs server)

o assign a media gateway to a Telephony Server

IP addresses (and other communication parameters) are necessary to send control and media communication over the network. Additional communication parameters like NFS servers may be necessary to boot from an NTS exported root file system.

LZU 103 1013 Rev B

Page 3 of 26

AAST~A

Media Gateway Setup

To give a Telephony Server the information that it is able to control one EMG or up to fifteen Media Gateway Unit or Media Gateway Classic media gateways.

The following sections describe the setup of the three different media gateway types. Since EMG and Media Gateway Classic have more in common than differences, their setup is described in one section, while the setup of the Media Gateway Unit is in a separate section.

3.5 Enterprise Media Gateway and Media Gateway Classic

The EMG, but not the Media Gateway Classic, needs to have an NFS server in order to start in Linux mode since it does not have a local file system. The flash memory on this media gateway contains just a basic Linux kernel and some files needed by this kernel to start the boot process. The NFS server serves a "Monte Vista Linux" to the media gateway as as.

To boot the NFS exported root file system, communication parameters (IP address, NFS server ... ) need to be set. This can be done only in boot mode. To communicate with one of these media gateways in boot mode, a serial connection is required.

The EMG has a serial connector at the front but on the Media Gateway Classic there are just pins on the board so a special cable is needed to connect to these pins (in fact it is not a "special" cable but a standard cable that was used years ago to connect the serial interface of a PC to the main board). To access and use the com connector, DSUl must be removed.

To establish a serial connection to one of these media gateways you need a 1: 1 serial cable (and the mentioned cable to connect to the pins on the board if the media gateway is of type Media Gateway Classic) and a terminal program.

On Windows you may want to use HyperTerm since it is generally available (not available in Vista but you can simply copy "hypertrm.exe" and "hypertrm.dll" from XP) or the free available TeraTerm.

On Linux the terminal program kermit is a good choice since it is included in the customized, xml file controlled Linux installation.

All other terminal programs should do the job as well as long as they support the communication parameters:

o baud rate: 9600

o data bits: 8

o parity bits: none

o stop bits: 1

o flow control: none (software and hardware flow control set to "off")

If kermit is used it may be worth to store a file". kermrc" in home directory. The file could contain the commands that would be given to kermit interactively instead.

LZU 103 1013 Rev B

Page 4 of 26

A4ST~A

Media Gateway Setup

set line /dev/ttySO set modem type none set speed 9600

set serial 8n1

set carrier-watch off set flow none

set disconnect on set exit warning off set esc Aq

set ta ke echo on

set transmit prompt 46 (or "10" or "0") connect

Powering on one of the media gateways while having a serial connection to it should result in the following output:

autostart will take place in about 5 seconds.

Hit any key before CR to abort!

1

EGX restart

Login: egxap

Password: legxap

egx >

Screenshot 1: Prompt to start in boot mode and logon

If any key (i. e. "1") is pressed followed by CR (Carriage Return = Enter) the media gateway will start in boot mode.

Log on with the credentials shown in the screenshot (here the password was added later, in a real screenshot the password is not displayed) if media

LZU 103 1013 Rev B

Page 5 of 26

A4STQA

Media Gateway Setup

gateway type is EMG. The credentials to log on to a Media Gateway Classic are username "MDUSER" and password "HELP"

In boot mode various commands are available. The command "help" displays the available commands.

egx > help

login: login <user> [password]

passwd: specify user and password values

rt: Run Test (as console task)

dbg: run test-function as dbg task (keep your console ;)

help: Command Info

h: Command Info

syntax: describe command syntax

quit: quit apn console

wd: watchdog handling

dbsig: set up and send a signal to specified PID

md: memory display

dm: memory display

du: memory display

sm: set or modify memory

mm: set or modify memory

LZU 103 1013 Rev B

Page 6 of 26

Media Gateway Setup

pm:

set or modify memory

mcp:

memory copy

mset:

memory set (fill memory)

msum: generate a memory check-sum

flprog: write memory contents to flashprom

flerase: erase flash Chip or Sectors

rd:

read memory (8 or 16 or 32 Bits memory access)

wr: write memory (8 or 16 or 32 Bits memory access)

ramtest: memory test

dispar: display parameters

rmpar: remove parameter

setpar: set parameter

savepar: save parameters to nonvolatile flash memory

setflm:

set default LM-info table in flash

sload: load one S-records file to ram-memory

loadmod: load a module from flash memory to ram

startmod: start loaded module

savemod:

save module in flash memory

listmod:

LZU 103 1013 Rev B

list defined modules in memory

Page 7 of 26

Media Gateway Setup

delmod: remove module from flash

startlm: start all modules defined in the "load"

parameter

start:

start modules by name

apload: server

down-load an AP loadmodule file from a remote

chkmod: verify checksum for loadmoduls

dupmod: duplicate module-image in flash memory

fpgaload: load FPGA from DP-memory (flash or ram)

ps: process status

restart: restart the system

pbist: load and start the pbist module

lilo: boot a vmlinux image

Screenshot 2: Commands in boot mode

To display the parameters the command "dispar" can be used.

egx > dispar

ROJ rev*

R3B/A

ROJ num*

ROJ 208 0031/1

ROJ ser*

T013963246

ethO mac*

OO:13:5E:OB:FD:EE

LZU 103 1013 Rev B

Page 8 of 26

A4STQA

Media Gateway Setup

eth1 mac* 00:13:5E:OB:FD:EF

BFJ num* BFJ 901 05/1

BFJ rev* P2A

BFJ ser* T01D124659

ethO ip 192.168.100.15/24

eth1 ip 192.168.10.165/25

nfs server 192.168.100.10

Screenshot 3: Boot pa ra meters

With the command "setpar" some of the parameters (those without a *) can be modified to meet the requirements of the network infrastructure respectively the local installation.

Changes made with "setpar" will be lost during restart of the system until they are not saved to the flash. This can be done with the command "savepar".

egx > setpar ethO_ip 192.168.1.1/24

egx > setpar eth1_ip 192.168.100.15/24

egx > setpar nfs server 192.168.1.10

egx > savepar

Screenshot 4: Modifying parameters

Finally the system is rebooted by powering it off and on or with the help of the command "restart".

egx > restart

Screenshot 5: restart

LZU 103 1013 Rev B

Page 9 of 26

AAST~A

Media Gateway Setup

The EMGs are powered up after the Telephony System has started successfully. The status of the EMGs is checked via the front LEOs:

D Top green LED indicates connectivity to the Ethernet LAN.

D Bottom red LED indicates alarms in the EMG. The red LED is on while the

EMG is booting.

Alternatively, view the alarms related to the EMGs from anyone of the Telephony Servers with "alarm_list".

Before and during the boot of the EMGs, an alarm, with severity 3, is present for each EMG. The alarm description is "No contact with media gateway". When the EMGs are fully booted, the alarm list updates. The alarm moves to severity 0 at the bottom of the alarm list.

The status of the LSU-Es, and connection to DSUs is checked with the command "Is_config_info". The status should be "OK".

There is no alarm to indicate if the connection between the LSU-E and any one of the DSUs is faulty. The best indication of a faulty connection is in the "Is_config_info" print. The print will not necessarily show a faulty board or cable, but will indicate if a DSU has not been detected.

To finish the configuration of the media gateway the media gateway needs to be assigned to a server.

Since this task is identical for all types of media gateways this will be covered after the setup of the Media Gateway Unit.

3.6 Media Gateway Unit

Different from the other media gateways the Media Gateway Unit has a local file system which means that it does not need an NFS server to start in Linux mode. The flash memory contains the entire Linux operating system (Wind River Linux 1.4).

Running in Linux mode, a connection to the MGU can be established via SSH (assumed the ethO ip address is known). All communication parameters can be set in boot mode and in Linux mode.

Alternatively the connection to the MGU can be a serial connection There is a group of 10 pins next to LAN 1 on MGU board (pin 1 is next to LAN 1) and the same cable/adapter is used than for Media Gateway Classic). Connection to USB port at the front of the MGU (using an RC323-USB cable) is also possible. With a serial connection boot mode and Linux mode can be controlled while the other two connections (SSH and USB) give only control over Linux mode. The parameters for the serial connection (and USB connection) are as they are for the other two media gateways.

Having a serial connection to the MGU and restarting the MGU should create the following output:

LZU 103 1013 Rev B

Page 10 of 26

Media Gateway Setup

autostart will take place in about 3 seconds.

Hit any key before CR to abort!

1

MGW restart

Login: admin

Password: admin

MGW >

Screenshot 6: MGU in boot mode

Logon with the credentials shown in the screenshot. Again, on a real screenshot the password would not be displayed.

As on the other media gateways, the command "help" displays the available commands in boot mode:

MGW > help

login: login <user> [password]

passwd: specify user and password values

rt: Run Test (as console task)

dbg: run test-function as dbg task (keep your console ;)

help: Command Info

h: Command Info

LZU 103 1013 Rev B

Page 11 of 26

Media Gateway Setup

syntax: describe command syntax

quit: quit apn console

wd: watchdog handling

dbsig: set up and send a signal to specified PIO

md: memory display

dm: memory display

du: memory display

sm: set or modify memory

mm: set or modify memory

pm: set or modify memory

mcp: memory copy

mset:

memory set (fill memory)

msum: generate a memory check-sum

flprog: write memory contents to flashprom

flerase: erase flash Chip or Sectors

rd:

read memory (8 or 16 or 32 Bits memory access)

wr: write memory (8 or 16 or 32 Bits memory access)

ramtest: memory test

dispar: display parameters LZU 103 1013 Rev B

Page 12 of 26

Media Gateway Setup

rmpar: remove parameter

setpar: set parameter

savepar: save parameters to nonvolatile flash memory

setflm:

set default LM-info table in flash

sload: load one S-records file to ram-memory

loadmod: load a module from flash memory to ram

startmod: start loaded module

savemod:

save module in flash memory

listmod: list defined modules in memory

delmod: remove module from flash

startlm: start all modules defined in the "load"

parameter

start:

start modules by name

apload: server

down-load an AP loadmodule file from a remote

chkmod:

verify checksum for loadmoduls

dupmod:

duplicate module-image in flash memory

fpgaload: load FPGA from DP-memory (flash or ram)

ps: process status

restart: restart the system

LZU 103 1013 Rev B

Page 13 of 26

pbist:

lilo:

Screenshot 7: help

Media Gateway Setup

load and start the pbist module

boot a vmlinux image

sig exec commands

Similar to the process on the other two media gateways the command "dispar" can be used to display the communication parameters.

MGW > dispar

ROF rev*

ROF num*

ROF ser*

ethO mac*

eth1 mac*

eth2 mac*

eth3 mac*

ethO ip

eth1 ip

eth2 ip

eth3 ip

def route

LZU 103 1013 Rev B

R2A

ROF 137 6304/1

T01E591932

00:lE:DF:63:D1:EA

00:lE:DF:63:D1:EB

OO:lE:DF:63:D1:EC

OO:lE:DF:63:D1:ED

192.168.1.15/24

192.168.2.15/24

192.168.1.16/24

192.168.2.16/24

192.168.1. 254

Page 14 of 26

AASTQA

Media Gateway Setup

def route1

192.168.2.254

lilo arg noatime

root=/dev/mtdblock1 rw rootfstype=yaffs2

autoupdate

no

Ian active

LANO

Ian primary

LANO

phyO_mode

AUTO

phy1_mode

AUTO

dispar returns ok;

MGW >

Screenshot 8: Communication parameters of MGU

Modification of the parameters in boot mode is done in the same was as it is done on the other two media gateways ("setpar", "savepar").

Since the Media Gateway Unit has a locally installed Linux as (in flash memory), which is different from the other two media gateways, it comes up in linux mode without an NFS exported root filesystem.

Having a connection (serial, USB or SSH) to the Media Gateway Unit and the Media Gateway Unit completed the start of the Linux as, the screen should look like this:

localhost login: root

Password: root

Wind River Linux glibc std (cgl) 1.4

Last login: Thu Jan 1 01:03:28 +0100 1970 on console.

LZU 103 1013 Rev B Page 15 of 26

Media Gateway Setup

root@localhost:/root>

Screenshot 9: MGU in linux mode

Logon with the credentials shown in the screenshot (password would not be displayed on real screenshot).

In linux mode the command "nvparams" is used to display and modify the communication parameters.

root@localhost:/root> nvparams -dispar all

DISP *ROF rev

R2A

DISP *ROF num

ROF 137 6304/1

DISP *ROF ser

T01E591932

DISP *ethO mac

00:lE:DF:63:D1:EA

DISP *eth1 mac

00:lE:DF:63:D1:EB

DISP *eth2 mac

00:lE:DF:63:D1:EC

DISP *eth3 mac

00:lE:DF:63:D1:ED

DISP ethO ip 192.168.100.25/24

DISP eth1 ip 192.168.200.25/24

DISP eth2 ip 192.168.100.26/24

DISP eth3 ip 192.168.200.26/24

DISP def route 192.168.100.254

DISP def route1 192.168.200.254

LZU 103 1013 Rev B

Page 16 of 26

Media Gateway Setup

DISP lila arg noatime

root=/dev/mtdblock1 rw rootfstype=yaffs2

DISP autoupdate no

DISP Ian active LANO

DISP lan_primary LANO

DISP phyO_mode AUTO

DISP phy1_mode AUTO

root@localhost:/root>

Screenshot 10: Communication parameters of MGU

root@localhost:/root> nvparams -setpar ethO_ip 192.168.100.15/24

SET

eth1 ip

192.168.100.15/24

SAVE

root@localhost:/root>

Screenshot 11: Modifying communication parameters of MGU in linux mode

As the screenshot shows, the changes are saved automatically to the flash (no need for "savepar")

Finally a reboot is required to activate the changes.

root@localhost:/root> init 6

On the MGU there is a package with name "mgw-x.y.z-1.ppc.rpm" installed, where x, y and z indicate the version number of the package. Whenever there is a new version available, this package should be upgraded. This can be done using a web server to offer the package and running the command "upgrade"

LZU 103 1013 Rev B

Page 17 of 26

A4ST~A

Media Gateway Setup

on the MGU or by copying the package to the MGU and install it with command "rpm".

3.7 Assigning a Media Gateway to a Server

Now, after the configuration of the media gateways it is necessary to assign every media gateway to a server. This can be done in Manager TS or by command.

3.7.1

Assign Media Gateway to TS with Manager TS

To assign a media gateway to a server with Manager TS, connect to Manager TS Chttp://ip_address or http://ip_address:8080 if browser is running on LIM1) and log on with the account created during system installation.

Screenshot 12: Log on to Manager TS

Navigate to "System" - "Hardware" - "Media Gateway" and click "Add"

LZU 103 1013 Rev B

Page 18 of 26

Media Gateway Setup

Screenshot 13: Add Media Gateway

To present only the valid opportunities Manager TS checks the configuration of the system to find out what you can configure (other options will be greyed out). If there is i. e. already an EMG assigned to a server, it will not be possible to add a MGU.

MGU AddNUmbterolMGUis):F3 Q;' MGWType: ('" EMG

{~ LSU

Screenshot 14: Select media gateway type

Depending on the type of the media gateway Manager TS will show you appropriate screens to fill in additional data.

LZU 103 1013 Rev B

Page 19 of 26

Media Gateway Setup

(f) MGWA: MGU

rUSE" Redund"lT1C"j

Mecli~ Gateway - Add - Step 2 ! 2

(7.) server 1

I.

192.1613.100.10 1%',168.'.Hl

Screenshot 15: Data for adding MGU

192:lm11.10

(:,;] Server 2

IP

(1i MGWA EMG

",CO",_="Pc, Mw~ IP Subnd:Ma~

",1192,168.1,1 !192,16'8.100_25 12.55.255.255,0

1192_168_100.254

Screenshot 16: Data for adding MG

LZU 103 1013 Rev B

Page 20 of 26

Media Gateway Setup

/.1) Server 2

IP

192.168.1.10

ti'MGWA lSU

CamrollP "'!192.168_l.11

Screenshot 17: Data for adding MGC

Screenshot 18: Add operation successful

Manager TS provides an intuitive, easy to use interface for system configuration. What Manager TS basically does is to translate the configuration data that is entered in Manager TS in commands (Linux style and mml commands) and then run this commands in mdsh (MD Shell).

That means that the above configuration can be done with exactly the same result running the commands on the command line directly.

3.7.2

Assign Media Gateway to TS by command

LZU 103 1013 Rev B

Page 21 of 26

A4STQA

Media Gateway Setup

Alternatively to the assignment of a media gateway to a server with Manager TS, this task can be performed from the command line (in mdsh or bash).

The procedure is done with two commands:

D media_gateway _config

D media_gateway _interface

With the command "media_gateway_config" the control over the media gateway is delegated to a server. As parameters (among others) the type of the media gateway and the control ip address of the media gateway need to be given to the command.

The command "media_gateway_interface" is used to configure the media ip address( es) of the media gateway (in case that the media gateway type is LSU (Media Gateway Classic) it can control more than one IPLU).

After the media ip address( es) is/are set, the RTP resources of the appropriate media gateway are available.

3.8 RTP Resou rces

Whenever it is needed to convert IP voice packets to TDM media or TDM media to IP voice an RTP (Real Time Protocol) resource is needed to perform this task.

When the MX-ONeM Version 4 system includes non-IP endpoints, RTP resources are required for any call that involves a non-IP endpoint. All calls between LIMs, where one or both endpoints are non-IP, are allocated an RTP resource in the LIM where the endpoint is located. Consider the calls below:

1. IP extension LIMl to analogue extension LIMl (intra LIM gateway call) - dash line (-----)

2. IP extension LIMl to analogue extension LIM2 (inter LIM gateway call) - dot-dash line (_. _. - )

3. IP extension LIM 1 to digital extension LIM3 (inter LIM gateway call) - solid line (_)

4. IP extension LIMl to IP extension LIM2 (inter LIM non-gateway call) - 2

dot-dash line (_ .. - )

In call 1, a call from an IP extension in LIMl to an analogue extension in the same LIM uses one RTP resource in LIM1.

In call 2, a call from an IP extension in LIMl to an analogue extension in LIM2 uses one RTP resource in LIM2.

LZU 103 1013 Rev B

Page 22 of 26

A4ST~A

Media Gateway Setup

In call 3, a call from an IP extension in LIMl to a digital extension in LIM3 uses one RTP resource, on the IPLU board, in LIM3.

In call 4, a call from IP to IP (LIMl to LIM2) does not use any RTP resources.

RTP Resource Usage

.. RTPresourcesused in LIM where non-IPendpointis located .

.. RTP resources (for all butOperatorAssistant} are

dyna mica lJy aUocatedotrd n d .

switching

Slide 19 RTP Resource Usage

RTP resources are provided by the virtual ELU32 boards in EMG and MGU and IPLU boards in the Media Gateway Classic.

There are 4 ELU32 boards in each of the Media Gateways. Each ELU32 provides 24 RTP resource individuals, a total of 96 per MG.

A Media Gateway Classic with 4 magazines is recommended to have at least 3 IPLU boards. Each IPLU provides 32 RTP resources.

In a Media Gateway all 4 virtual ELU32s use the ethl media IP address of the Media Gateway. Static IP addressing is used.

Once the "media_gateway_interface" command has been executed (directly or from Manager TS), the status of all ELU32s changes to "assigned".

All calls from a non-IP endpoint in a Media Gateway Classic LIM to an extension or route in the same or another LIM require an RTP resource (= channel) on an IPLU board. The calls are gateway (GW) calls. IPLU boards provide the communication channels for:

o Transportation of media between IP extensions or IP routes and non-IP endpoints in the same LIM.

o Transportation of media between non-IP endpoints to extensions/routes in other LIMs.

LZU 103 1013 Rev B

Page 23 of 26

Media Gateway Setup

There are 32 channels per IPLU board, each connected to a time slot in the Media Gateway Classic LIM backplane. There are no channels for signaling or synchronization. The inter LIM signaling is sent directly between the Telephony Servers.

There is no synchronization between the LIMs. The IP network does not support synchronization (IP is an asynchronous protocol).

The IPLUs must be physically installed in the Media Gateway Classic LIMs prior to initiating the boards as RTP resources. The IPLUs can be located in either upper or lower cabinet in anyone of the board positions. If the EMC shield is used, IPLUs must be installed "outside" the EMC.

In Media Gateway Classic, each IPLU board requires a unique static IP address. Each IPLU is configured individually.

If the MX-ONETM system is a pure IP-PBX solution using only IP extensions and IP routes none of the RTP resources are required. All calls, intra and inter LIM, are non-gateway.

3.9 System Preparation

With the servers and Media Gateway running successfully, the Telephony System can be prepared for customer data. The preparation can be completed from a login to any LIM but it is recommended to use LIM 1 (there are some functions that must be completed from LIMl).

Login to LIMl using the mdsh user created after the software installation. If there is no users created it may be done at this point. If Linux user (root or eri_sn_admin) is used for logging it is possible to open mdsh by just typing a command mdsh from command line. mdsh prompt will appear as result. Check that the Telephony System is ready to accept "MDllO-style" data by running any MML command. Set the site identity of the MX-ONETM Telephony System with the Linux-style Aastra proprietary command group "exchange_info". The command t'exchange info"l executed without parameters, returns the site identity and build version for the Telephony System.

3.10 Update/Read Hardware

After the installation of the Telephony System software, the system acts, and can be treated as, a multi-LIM system. Almost all configurations can be done by logging into a single LIM, some configurations need to be initiated from LIM!. Both root and the user created during installation (eri_sn_admin) are available in all LIMs.

The virtual boards in the EMG and Media Gateway Unit and the real boards in the Media Gateway Classic may not automatically be "visible" to the system after Telephony System software installation. The virtual and real board list can be viewed and updated using the "board_" command group. The command "board_list" is used to print boards and the "board_config" (with option "-scan") command to update the board list.

LZU 103 1013 Rev B

Page 24 of 26

A4STQA

LZU 103 1013 Rev B

Media Gateway Setup

Page 25 of 26

QJ
.j..I
.j..I
QJ
g. (J)
U
!...
QJ
! ><
W
T""'I
T""'I
(V) -
.-
ra
...,
OJ
C
.........
"C
C
ra
E
E
0
u
CJ)
l.....
Q)
>
l.....
Q)
CJ)
l.....
:::J
0
>-
0
+-1
CJ)
>-
CO
3:
Q)
+-1
CO
C en
0 co
:p "'0
U Q)
~ E
I-
...,
III "'0
C "'0
1-1 « \D N ..,_

o \D N

Q) 01 ro 0..

« > Q)

0::: (V) ...... o ......

(V) o ......

::l N __j