Alcatel - Comm Server

This is the html version of the file
ftp://mail02.spread.com.br/Alcatel%20Convidado/OXE/R9.1_OXE/09011b0280f30c82-
1258471723222/cdrom/content/pdf/ID09011b0280f30d53.pdf.
Google automatically generates html versions of documents as we crawl the web.
Page 1
Alcatel-Lucent OmniPCX Enterprise

Communication Server
Crystal Hardware Media Gateway
Page 2
Legal notice:
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of
Alcatel-Lucent. All other trademarks are the property of their respective
owners.
The information presented is subject to change without notice.
Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.
Copyright 2009 Alcatel-Lucent. All rights reserved.
The CE mark indicates that this product conforms to the following Council
Directives:
- 89/336/CEE (concerning electro-magnetic compatibility)
- 73/23/CEE (concerning electrical safety)
- 1999/5/CE (R&TTE)
Page 3
Chapter 1
Overview
1.1
Overview .................................................................................................... 1.1
Chapter 2
Architecture
2.1
Configuration 1 ....................................................................................... 2.1
2.2
Configuration 2 ....................................................................................... 2.1
2.3
Configuration 3 ....................................................................................... 2.2
2.4
Restriction ................................................................................................ 2.4
Chapter 3
Commissioning
3.1
Overview .................................................................................................... 3.1
3.2
Principle ..................................................................................................... 3.1
3.3
Declaring the INT-IP A Board ............................................................. 3.1
3.4
Declaring the ACT Media Gateway .................................................. 3.1
Table of
contents
0-1
Page 4
3.4.1
Declaring the Crystal Shelf of the ACT Media Gateway ........................... 3.1
3.4.2
Declaring the INT-IP B (or IOIP) Board ...................................................... 3.2
3.4.3
Entering the Ethernet (MAC) Address of the INT-IP B (or IOIP) Board ... 3.3
3.4.4
Declaring another Board ............................................................................. 3.3
3.5
Installing and Connecting INT-IP B (or IOIP) Board to the ACT
Media Gateway ........................................................................................ 3.3
3.6
Installing and Connecting INT-IP3 Board to the ACT Media
Gateway ..................................................................................................... 3.4
3.7
Starting the ACT Media Gateway ...................................................... 3.5
3.7.1
INT-IP B (or IOIP) Board Static Initialization Process .............................. 3.5
3.7.2
INT-IP B (or IOIP) Board Dynamic Initialization Process ......................... 3.6
3.7.3
INT-IP3 B Board Static Initialization Process ............................................ 3.7
3.8
Configuring the Address of the Passive Communication Server
in the INTIP board .................................................................................. 3.8
Chapter 4
Maintenance
4.1
Connecting to a Media Gateway ....................................................... 4.1
4.2
Error Codes .............................................................................................. 4.1
4.3
Board Boot Traces ................................................................................. 4.1
0-2
Page 5
1 Main Call Server in a duplicated Call Server configuration
1.1
Overview
This document describes how to commission an ACT Media Gateway connected via IP.
Connection via IP is specific in that the link between the ACT Media Gateway and Call Server
cannot be set up immediately. A preliminary phase, involving acquisition of IP parameters by
the ACT Media Gateway controller board and a binary download from the Call Server 1, must
be performed.
An ACT Media Gateway on IP is controlled by an INT-IP B or IOIP board installed in a CPU
slot. This board may be duplicated. The INT-IP B or IOIP board only provides a link with the
Call Server or main Crystal shelf. It does not act as an H.323 gateway and does not handle
IP-Phone signaling.
Chapter
1
Overview
dm09011b0280122f8d.xml - Ed.05 - January 2009 - Overview
1-1
Page 6
Chapter
1
Overview
1-2
dm09011b0280122f8d.xml - Ed.05 - January 2009 - Overview
Page 7
On the basis of the three standard topologies described in the module Topology - Overview,
this section describes three basic types of configuration.
2.1
Configuration 1
The main area is composed of an OmniPCX Media Gateway (S and L racks): there may be an
auxiliary ACT Media Gateway in the main area and remote ACT Media Gateways over IP.
Connection to the Call Server is via IP.
Figure 2.1: Configuration 1
2.2
Configuration 2
Main area with a main Crystal shelf hosting the Call Server on a CPU board: there may be
remote ACT Media Gateways over IP. The inter ACT link is established between the CPU and
the INT-IPB board. The INT-IPA board provides ressource for VOIP communication.
___change-begin___
Chapter
2
Architecture
dm09011b0280122fad.xml - Ed.05 - December 2009 - Architecture
2-1
Page 8
___change-end___
2.3
Configuration 3
Main area with an ACT Media Gateway and Call Server on Appliance Server. In this case, the
main Crystal shelf is connected to the Call Server via the IP network. There may also be
remote ACT Media Gateways over IP.
Chapter
2
Architecture
2-2
Page 9
Note 1:
With this latter configuration, an INTOF or RT2 connection behind the main ACT Media Gateway may be
used.
If there is a peripheral Crystal shelf on INTOF, 2 signaling modes can be used: TS16 mode or N64 mode.
Architecture
2-3
Page 10
Note 2:
The INT-IP3 board cannot be used as an IOIP board.
2.4
Restriction
On an ACT Media Gateway, the INT-IPB main and the INT-IPB standby must be of the same
board generation: two INT-IP3 boards or two INT-IP from older generation.
Chapter
2
Architecture
2-4
Page 11
3.1
Overview
The commissioning procedure is almost identical, irrespective of system architecture. The only
difference is with configuration 3 (see the module Crystal Hardware Media Gateway -
Architecture Configuration 3): if an INTOF connection with 4*64 kbps signaling is used, you
must declare an IOIP board instead of the INT-IP B board.
Note:
The INT-IP3 board cannot be used as an IOIP board.
3.2
Principle
To put an ACT Media Gateway into service:
1. If required (see configuration 2 above), declare an INT-IP A board in the main Crystal
shelf.
2. Declare the ACT Media Gateway on the Call Server using the PCX configuration tool.
3. Install and connect INT-IP B (or IOIP) board in the ACT Media Gateway.
4. Start-up the ACT Media Gateway.
3.3
Declaring the INT-IP A Board
In configuration 2, at least one INT-IP A board must be declared in the main Crystal shelf. This
board provides compression resources.
3.4
Declaring the ACT Media Gateway
Declare the following:
1. The Crystal shelf of the ACT Media Gateway (this is always declared as a peripheral
shelf).
2. An INT-IP B (or IOIP) board in CPU position.
3. The Ethernet (MAC) address of the INT-IP B (or IOIP) board.
4. At least another board in the Crystal shelf (required for commissioning).
3.4.1
Declaring the Crystal Shelf of the ACT Media Gateway
1. Select Shelf
2. Review/modify the following attributes:
Chapter
3
Commissioning
dm09011b0280001cb0.xml - Ed.06 - December 2009 - Commissioning
3-1
Page 12
Shelf Address
Enter Crystal shelf number.
Note:
Numbers 0, 18 and 19 are reserved.
Shelf Type
Select Crystal shelf type from the menu: ACT-14 Interfaces or
ACT-28 Interfaces.
Name of rack
Enter a name for the Crystal shelf.
ACT Type
Select Peripheral ACT Shelf.
Remark:
In configuration 3, the Crystal shelf in the main area is also declared as a
peripheral ACT shelf. In management, the Call Server is considered to
be the main Crystal shelf (No. 0).
3. Confirm your entries
3.4.2
Declaring the INT-IP B (or IOIP) Board
1. Select Shelf > Board
Shelf Address
Board Address
Enter the slot number of the board in the Crystal shelf.
This board must be in a CPU slot. The options are:
Slot 1 in a 4-slot Crystal shelf (Voice Hub) or in a
9-slot Crystal shelf (WM1)
Slot 6 in a 14-slot Crystal shelf
Interface Type
Select INTIPB, INTIP3B or IOIP (if the signaling mode
used is IO2).
INTIP Daughterboard
Specify the type and number of daughterboards in-
stalled on the board, the options are:
None: no daughterboard.
GIP6x1: one GIP6 daughterboard.
GIP6x2: two GIP6 daughterboards.
1 GIP4-4: one GIP4-4 daughterboard (as of R6.0).
2 GIP4-4: two GIP4-4 daughterboards (as of R6.0).
1 GIP6A: one GIP6A daughterboard.
1 GIP4-1: one GIP4-1 daughterboard (as of R6.0).
2 GIP6A: two GIP6A daughterboards.
2 GIP4-1: two GIP4-1 daughterboards (as of R6.0).
ARMADA: if the mother board is an INT-IP3 board

(as of R9.1)
For more information on daughterboards, see the mod-
ule INT-IP - GIP 6 daughter board - GIP 6 Daughter
Board and module INT-IP - GIP 4 daughter board - GIP
4 Daughter Board.
If an IOIP board is used, a daughterboard cannot be in-
stalled (no compressor on IOIP boards).
Board IP Version
IP Default
Chapter
3
Commissioning
3-2
Page 13
Note:
When the board has been created, an additional attribute is displayed in view/modify:
No. of Compressors for IP Devices
Enter the number of compressors that can be used. The value
entered is used to calculate the maximum number of PCX
compressors for the "G729A Server" and "469 G723.1 Server"
135 locks.
According to hardware configuration, the table below details the number of available VOIP channels.
Profile
Additional ARMADA
VOIP Channels
INT-IP3B
Main/Standby
0
30
1
60 (30+30)
3.4.3
Entering the Ethernet (MAC) Address of the INT-IP B (or IOIP) Board
Once the INT-IP B board has been declared, its MAC address must be entered in its Ethernet
parameters. IP parameters are not completed at this stage, they are completed at board
initialization.
1. Select Shelf > Board > Ethernet Parameters
Shelf Address
Board Address
Enter the slot number of the board in the Crystal
shelf.
Interface Type
INTIPB or IOIP (if 4*64 kbps signaling on INTOF is
used).
Board Ethernet Address
Enter the board Ethernet MAC address. This inform-
ation is included in the label attached to the board.
3.4.4
Declaring another Board
1. Select Shelf > Board
Shelf Address
Board Address
Enter the slot number of the board in the Crystal shelf.
Interface Type
Select a board from the menu list.
3.5
Installing and Connecting INT-IP B (or IOIP) Board to the ACT
Media Gateway
Commissioning
3-3
Page 14
Note:
This section is not relevant for INT-IP3 boards.
The following procedure is applicable for both the INT-IP B and IOIP boards. The IOIP board is
(physically) an INT-IP2 board with no compressors (declaring the INT-IP2 board as an IOIP board in
management gives it this functionality).
1. On the INT-IP B board, specify Crystal shelf number with the "crystal number" switches.
There are 8 switches each corresponding to a bit (pay attention to LSB and MSB).
2. In the Crystal shelf, install the INT-IP B board in the CPU slot as follows:
Slot 1 in a 4-slot Crystal shelf (Voice Hub) or in a 9-slot Crystal shelf (WM1)
3. Connect the adapter to the INT-IP B board as follows:
For 9-slot (WM1), 14-slot or 28-slot Crystal shelf: connect the 10/100 base T connector
(ref 3BA 23243 AA) to the back panel of the INT-IP B board. For more information: see
module INT-IP - External connections INT-IP board in CPU mode.
For 4-slot Crystal shelf (Voice Hub): connect the 9-port module (VH PATCH PANEL
INT-IP MODULE/ref 3BA 23244 AA) to the patch panel. For more information: see
module Patch Panel - INT-IP module - INT-IP module INT-IP or INT-IP2 Board Used
in CPU Mode (INT-IP B).
4. Connect the adapter to the LAN with a straight RJ45 cable.
5. Install another board in the shelf (there must be at least one other board declared and in
service in the shelf for the INT-IP B board to initialize).
3.6
Installing and Connecting INT-IP3 Board to the ACT Media
Gateway
1. Install the INT-IP3 board in the CPU main slot or standby.
Note:
The Voice Hub is not supported with INT-IP3.
2. Connect the 10/100/1000 base T (3BA23278AA) connector as shown in module INT-IP3 -
External connections
3. Connect the adapter to the LAN with a straight RJ45 cable.
Chapter
3
Commissioning
3-4
Page 15
3.7
Starting the ACT Media Gateway
The Media Gateway start-up corresponds to INT-IP B board initialization. There are two
possible initialization processes:
- Static initialization: IP parameters are manually configured on the INT-IP B board. Static
initialization must be used if there is no DHCP server. It is also recommended for reasons
of reliability so that ACT Media Gateway operation is not dependent on DHCP server
availability. See INT-IP B (or IOIP) Board Static Initialization Process .
- Dynamic initialization (factory-fitted default process): IP parameters are automatically sent
by a DHCP server to the INT-IP B board. See INT-IP B (or IOIP) Board Dynamic
Initialization Process .
Note 1:
The two board initialization processes are common to the INT-IP B and IOIP boards.
Note 2:
For INT-IP3, only static initialization is allowed due to security constraints.
3.7.1
INT-IP B (or IOIP) Board Static Initialization Process
Note:
For INT-IP3 static initialization, see: INT-IP3 B Board Static Initialization Process .
3.7.1.1
Overview
1. The administrator configures the board IP parameters from a console connected directly to
the front panel of the INT-IP B board. The IP parameters to configure are:
The INT-IP B board IP address
The IP subnetwork mask
The router address
The TFTP server 1 IP address
The TFTP server 2 IP address
Note:
In a duplicated Call Server configuration, the addresses to enter in the TFTP server 1 and 2
fields are the main IP addresses of the Call Servers as follows:
When the two Call Servers are on the same IP subnetwork, the same main IP address can
be used for the two Call Servers. This one must only be entered on the TFTP server 1 field.
When the two Call Servers are on different IP subnetworks, the two Call Servers main IP ad-
dresses must be entered on the TFTP server 1 and TFTP server 2 fields.
2. The INT-IP B board downloads the lanpbx.cfg file from the TFTP server, this file
contains the list of Call Server IP addresses in the PCX network. For information on
lanpbx.cfg generation, see the module lanpbxbuild - Operation (if the file does not exist
on the PCX, it is created automatically).
3. The INT-IP B board sends a TFTP request towards the Call Servers IP addresses declared
in the lanpbx.cfg file.
4. The INT-IP B board downloads the binaries from the main Call Server.
5. The INT-IP B board sends a new TFTP request towards the two Call Servers main IP
Commissioning
3-5
Page 16
addresses.
6. The INT-IP B board downloads the startintip file from the main Call Server.
3.7.1.2
Starting the Static Initialization Process
To configure the board in static, access the board's main menu by connecting a console to the
front panel of the board:
1. Connect the V24 cable to the board:
INT-IP board: reference 3BA 28112, see the module INT-IP - External connections
Description of the cable for the INT-IP board.
INT-IP 2 board: reference 3EH75003AA, see the module INT-IP - External connections
Description of the cable for the INT-IP2 board.
2. Configure the console as follows:
9600 bps
8 N1
Flow control XON/XOFF

3. When the message Hit ENTER key to suspend coupler boot processis
displayed, press Enter to display the main menu:
IP configuration Menu
Available commands :
view : display current IP configuration
chmode : change IP Configuration Mode (Static/dynamic)
chip : change Static IP Parameters
- chqual : Change default quality Parameters
save : saved modified configuration
reset : reset coupler
Use? or ? <cmd> to get help on Command
Config:
4. Enter chmode, then 1 to change the initialization mode to Static mode.
5. Enter chip and configure the following IP parameters:
The INT-IP B board IP address,
The IP subnetwork mask,
The router IP address,
The TFTP server 1 IP address,
The TFTP server 2 IP address.
6. Enter save to save the parameters.
7. Enter reset to re-initialize the board.
8. To check initialization status, enter the command: Config <Shelf No.>
3.7.2
INT-IP B (or IOIP) Board Dynamic Initialization Process
3.7.2.1
Overview
1. At board start-up, the INT-IP B board sends a request to the DHCP server which returns
the following IP parameters:
The INT-IP B board IP address,
The IP subnetwork mask,
Chapter
3
Commissioning
3-6
Page 17
The router address,
The TFTP server address.
2. The INT-IP B board downloads the lanpbx.cfg file from the TFTP server, this file contains
the list of Call Server IP addresses in the PCX network. For information on lanpbx.cfg
generation, see the module lanpbxbuild - Operation (if the file does not exist on the PCX, it
is created automatically).
3. The INT-IP B board sends a TFTP request towards the Call Servers IP addresses declared
in the lanpbx.cfg file.
4. The INT-IP B board downloads the binaries from the main Call Server.
5. The INT-IP B board sends a new TFTP request towards the two Call Servers main IP
addresses.
6. The INT-IP B board downloads the startintip file from the main Call Server.
3.7.2.2
Starting the Dynamic Initialization Process
Requirements:
- Before starting initialization, you must program on the DHCP server a static address
(Ethernet (MAC) address - IP address correspondence) for the INT-IP B board. The ad-
vantage of static addressing is that the DHCP server always assigns the same IP address
to the INT-IP B board at subsequent start-ups. For more information: see module DHCP
server - Configuration procedure.
- If the DHCP server is internal to the Call Server, no address of TFTP server must be
entered in DHCP server configuration. The DHCP server provides the appropriate IP ad-
dress of the Call Server. In a duplicated Call Server configuration where the two Call
Servers are on different IP subnetworks, a DHCP relay must be activated on the IP sub-
network where the INT-IP B board is located.
- If the DHCP server is external, the TFTP server address must be entered in DHCP server
configuration. In a duplicated Call Server configuration where the two Call Servers are on
different IP subnetworks, the TFTP server must also be external.
The INT-IP B board initialization starts as soon as the board is installed in the ACT Media
Gateway.
Note:
If board initialization process has been changed previously and the board is set to static, it must be
switched back to dynamic using the IP configuration menu. This menu is accessible by connecting
a console to the front panel of the INT-IP B board. For more information: see Starting the Static Initializ-
ation Process .
3.7.3
INT-IP3 B Board Static Initialization Process
The administrator configures the INT-IP3 B board IP parameters from a console using the
mgconfig command.
1. Connect a console as shown in: module INT-IP3 - External connections Connecting a
Console for Static Configuration
2. Open a root session (by default the password is empty)
3. Enter the mgconfig command
The IP parameters to enter are:
Commissioning
3-7
Page 18
The INT-IP3 B board IP address
The IP subnetwork mask
The router address
The CS role address
The CS redundancy role address
Note:
In a duplicated Call Server configuration:
When the two Call Servers are in the same IP subnetwork, the same main IP address can
be used for the two Call Servers. This address must only be entered once in the CS role ad-
dress field.
When the two Call Servers are on different IP subnetworks, the duplicated Call Server main
IP address must be entered in the CS redundancy role address field.
4. Exit the mgconfig tool and exit the session
After configuration, the INT-IP3 B:
1. Sends a TFTP request towards the main IP addresses of the two Call Servers configured
previously
2. Downloads the binaries from the main Call Server
3. Sends a new TFTP request towards the main IP addresses of the two Call Servers
configured previously
4. Downloads the startemg file from the main Call Server
3.8
Configuring the Address of the Passive Communication Server
in the INTIP board
If the ACT Media Gateway is rescued by a Passive Communication Server, the Passive
Communication Server address must be configured in the INT-IP board. To configure the
address of the Passive Communication Server in the INTIP board, see module Passive
Communication Server (PCS) - Configuration procedure Configuring the Address of the
Passive Communication Server in the INTIP boards.
Chapter
3
Commissioning
3-8
Page 19
4.1
Connecting to a Media Gateway
telnet sessions are not available on INT-IP boards. To access an INT-IP board, use the the
console port in front of the INT-IP board.
4.2
Error Codes
In case of error, LEDs located on the front panel are lit up. For more information, see:
- INT-IP and INT-IP2: module INT-IP - Hardware configuration
- INT-IP3: module INT-IP3 - Hardware configuration
4.3
Board Boot Traces
Board boot can be traced on a console connected to the board front panel with a cable as
described in module Crystal Hardware Media Gateway - Commissioning INT-IP B (or IOIP)
Board Static Initialization Process. The trace gives information on binary download, binary
version, IP parameters, Call Server address, etc.
Example:
In this example, the address assigned by the DHCP server is 172.231.47.19.
Chapter
4
Maintenance
dm09011b0280122fb3.xml - Ed.06 - December 2009 - Maintenance
4-1
Page 20
------------------------------------------------------------------------------
Logical Board : INTIP B Main - Crystal 2 (Dynamic IP Configuration using
DHCP)
Physical Board : Revision 1 = AB (MPC8260 40MHz)
MuP : Version 0081 Revision 0101
Boot/download version : intip _04.03.0_03Dec01_11h29
Application version : intip _04.07.1_09Jan02_08h56
------------------------------------------------------------------------------
---> Hit ENTER key to suspend coupler boot process <--- INTIP:
5 sec left before starting coupler
Starting Coupler
00000004-000007E4: ConfigIP : Discovering our IP Parameters using DHCP
request
00000005-000007E4: DHCP : My Ethernet Address is 00:80:9F:04:9C:0E
00000006-000007E4: DHCP : Send DHCP_DISCOVER (Broadcast)
00000007-00000BCD: DHCP : Switch to state INIT_STATE
00000008-00000F6D: DHCP : Send DHCP_DISCOVER (Broadcast)
00000009-00000F6E: DHCP : Receive DHCP_OFFER from 172.231. 47. 1
0000000A-00000F6E: DHCP : This DHCP_OFFER comes from Alcatel 4400 DHCP
Server
0000000B-00000F6E: DHCP : DHCP_OFFER contain @IP 172.231. 47. 19 @TFTP
172.231. 47. 3
0000000C-00000F6E: DHCP : Switch to state REQUESTING_STATE
0000000D-00000F6E: DHCP : Send DHCP_REQUEST[0] [ServerId 172.231. 47. 3
ReqIP 172.231. 47. 19] (Broadcasts)
0000000E-00000F89: DHCP : Receive DHCP_ACK from 172.231. 47. 1
0000000F-00000F89: DHCP : Switch to state BOUND_STATE
00000010-00000F89: DHCP : Board IP Addr : 172.231. 47. 19
00000011-00000F89: DHCP : Subnet Mask : 255.255.255. 0
00000012-00000F89: DHCP : Router IP Addr: 172.231. 47.254
00000013-00000F89: DHCP : DHCP IP Addr : 172.231. 47. 3
00000014-00000F89: DHCP : TFTP IP Addr : 172.231. 47. 3
00000015-00000F89: DHCP : LEASE TIME : 86400 seconds
00000016-00000F89: DHCP : Start Timer [43200 , 75600 , 86400]
00000017-00000F89: ConfigIP : IP Parameters comes from DHCP server 172.231.
47. 3
00000018-00000F89: ConfigIP : IP Address : 172.231. 47. 19
00000019-00000F89: ConfigIP : IP Subnet Mask : 255.255.255. 0
0000001A-00000F89: ConfigIP : IP Default Router : 172.231. 47.254 ping fd =
2
0000001B-00000F8C: Reset of Released Call Counters
0000001C-00000F8C: LANPBX : Download of the file 'lanpbx.cfg' from server
172.231.47.3
Chapter
4
Maintenance
4-2
dm09011b0280122fb3.xml - Ed.06 - December 2009 - Maintenance

Alcatel - Comm Server

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

Alcatel - Comm Server

Uploaded by

Copyright:

Available Formats

This is the html version of the file

Alcatel-Lucent OmniPCX Enterprise

GIP6x1: one GIP6 daughterboard.

GIP6x2: two GIP6 daughterboards.

1 GIP4-4: one GIP4-4 daughterboard (as of R6.0).

2 GIP4-4: two GIP4-4 daughterboards (as of R6.0).

1 GIP6A: one GIP6A daughterboard.

1 GIP4-1: one GIP4-1 daughterboard (as of R6.0).

2 GIP6A: two GIP6A daughterboards.

2 GIP4-1: two GIP4-1 daughterboards (as of R6.0).

ARMADA: if the mother board is an INT-IP3 board

Flow control XON/XOFF

You might also like