101.2.2 As 5300 Install and Config Method For Audiocodes M3K PRI GW

Avaya Aura AS 5300
101.2.2 AS 5300 Install and Config Method for

Audiocodes M3K PRI GW
Product Release:
Version:
Document Release:
Issue Date:
Security Classification:
AS 5300 3.0
Version 1.6
Approved
May 02, 2012
Avaya Confidential
Copyright 2012 Avaya

All rights reserved.
AVAYA CONFIDENTIAL: The information contained in this document is the property of Avaya. Except as
specifically authorized in writing by Avaya, the holder of this document shall keep the information contained
herein confidential and shall protect same in whole or in part from disclosure and dissemination to third parties
and use same for evaluation, operation, and maintenance purposes only.
101.2.2 AS 5300 Install and Config Method for Audiocodes M3K PRI GW
Version 1.6
Table of Contents
General Introduction ............................................................................................... 11
Reference: Documentation ..................................................................................... 12
Required Software Tools ........................................................................................ 13
Customer Supplied Materials / Information........................................................... 14
Customer Supplied Network Information .............................................................. 15
1
Installation and Configuration..........................................................................17

1.1
1.2
Introduction........................................................................................................... 17
How to Save Configuration or Board.INI File ........................................................ 18
1.2.1
1.2.2
1.3
1.4
Physical Installation of the Mediant 3000 Gateway ............................................... 20

Assign IP Address and New Install Mediant 3000 HA ........................................... 20
1.4.1
1.4.2
1.4.3
1.5
1.6
1.7
1.8
1.9
1.10
1.11
1.12
1.13
Via Web Interface ................................................................................................ 18

Via SSH Interface ................................................................................................ 18
Assign Private IP Address Using BootP ............................................................... 21

Using HTTP to Assigning GW Global IP Address and Upgrade Firmware ............ 25
Using HTTP to Upload Initial Default Configuration to M3K GW .......................... 27
Generate Certificate Signing Request (CSR) for the GW ...................................... 29

Install CA Issued Certificates on the GW .............................................................. 30
Install Call Progress Tone (CPT) File on the GW .................................................. 31
Setup RSA public key for PuTTY SSH access to GW ........................................... 32
Configure SNMPv3 Secure Communication ......................................................... 36
Adding a New File to the EMS Software Manager ................................................ 38
Adding the GW to EMS ........................................................................................ 39
Use GW with HTTPS Enabled on Hardened EMS ................................................ 41
Upgrade/Downgrade the GW Firmware Using EMS ............................................. 42
1.13.1 Upgrade of GW Firmware from 5.8 to 6.2............................................................. 42
1.13.2 Downgrade of GW Firmware from 6.2 and 5.8 ..................................................... 47
1.13.3 Major Upgrade/Downgrade of GW Firmware between 5.4 and 6.2 ....................... 47
1.14 Configure DS1 Trunks for TP-8410 Board ............................................................ 48

1.14.1 Frame: VoIP -> PSTN -> DS1 Trunks Trunk SIP Frame .................................... 48
1.14.1.1 Tab: General Settings ........................................................................... 48
1.14.1.2 Tab: ISDN Settings ............................................................................... 49
1.14.1.3 Tab: SIP Settings.................................................................................. 51
1.15 Configure the Sonet/SDH Trunk for TP-6310 Boards ........................................... 52

1.15.1 Frame: VoIP -> PSTN -> Trunk............................................................................ 52
1.15.2 Frame: Fiber Group ............................................................................................. 53
1.15.3 Frame: VoIP -> PSTN -> Trunks .......................................................................... 55
1.15.3.1 Tab: General Settings ........................................................................... 56
1.15.3.2 Tab: ISDN Settings ............................................................................... 57
1.15.3.3 Tab: SIP Settings.................................................................................. 60
1.16 Configure NFAS Primary, Backup, NFAS Trunks .............................................. 61

1.17 Removing NFAS Group ........................................................................................ 65
May 02, 2012
2011 Avaya Inc.

Avaya proprietary use pursuant to company instructions
Version 1.6
1.18 Configuring GW Parameters................................................................................. 66

1.18.1 Frame: System -> System Setting ....................................................................... 67
1.18.1.1 Tab: Application Settings ...................................................................... 67
1.18.2 Frame: System -> Management........................................................................... 68
1.18.2.1 Tab: CLI Terminals Provisioning ........................................................... 68
1.18.3 Frame: VoIP > Network ....................................................................................... 69
1.18.3.1 Tab: QoS Settings ................................................................................ 69
1.18.4 Frame: System -> System Setting ....................................................................... 70
1.18.4.1 Tab: Security Settings........................................................................... 70
1.18.5 Frame: VoIP -> Media ......................................................................................... 72
1.18.5.1 Tab: SRTP Settings .............................................................................. 72
1.18.6 Frame: VoIP -> TDM -> TDM Frame.................................................................... 73
1.18.6.1 Tab: System Timing .............................................................................. 73
1.18.7 Frame: VoIP -> Media -> Media Frame ................................................................ 74
1.18.7.1 Tab: Bypass Settings ............................................................................ 74
1.18.7.2 Tab: Fax Settings ................................................................................. 75
1.18.7.3 Tab: Modem Settings............................................................................ 76
1.18.7.4 Tab: RTP Settings ................................................................................ 77
1.18.8 Frame: VoIP -> SIP ->SIP Protocol Definition ...................................................... 79
1.18.8.1 Tab: General Info.................................................................................. 79
1.18.8.2 Tab: Proxy Server................................................................................. 80
1.18.8.3 Tab: Registration .................................................................................. 82
1.18.8.4 Tab: Coders.......................................................................................... 83
1.18.8.5 Tab: Sup Services ................................................................................ 84
1.18.8.6 Tab: Authentication & Security .............................................................. 85
1.18.9 Frame: VoIP ->SIP -> SIP Endpoints ................................................................... 86
1.18.9.1 Tab: Phones ......................................................................................... 86
1.18.10 Frame: VoIP -> SIP -> SIP Routing...................................................................... 87
1.18.10.1 Tab: Routing Modes ............................................................................. 87
1.18.10.2 Tab: IP to Hunt ..................................................................................... 88
1.18.11 Frame: VoIP -> SIP -> SIP Manipulations ............................................................ 89
1.18.11.1 Tab: Definitions..................................................................................... 89
1.18.11.2 Tab: Destination Telecom to IP ............................................................. 90
1.18.12 Frame: VoIP ->SIP -> SIP Advanced Configuration ............................................. 91
1.18.12.1 Tab: General Features 1 (Part 1 of 2).................................................... 91
1.18.12.6 Tab: Transport Info ............................................................................... 96
1.18.12.7 Tab: Tones and Progress ..................................................................... 97
1.18.12.8 Tab: Debug .......................................................................................... 98
1.18.12.9 Tab: MLPP (Part 1 of 2) ........................................................................ 99
1.18.12.10 Tab: MLPP (Part 2 of 2)................................................................. 100
1.18.12.11 Tab: SIP to ISDN Cause Mapping (for Hybrid Routing) .................. 101
Configure Multiple Network / VLAN Address ................................................ 102

2.1.1
2.1.2
2.1.3
2.1.4
May 02, 2012
Prerequisites ..................................................................................................... 102

VLAN Network Information ................................................................................ 102
2.1.2.1 Initial IP Addresses ............................................................................. 102
2.1.2.2 Syslog Server ..................................................................................... 102
2.1.2.3 Verifying the Active Blade ................................................................... 103
Configuring Static Routes .................................................................................. 104
Configuring Multiple VLAN Interfaces................................................................. 105
2011 Avaya Inc.
2.1.5
2.1.6
Prerequisite Steps .............................................................................................. 110
4.1.2
4.1.1.1 VoIP -> Security > Tab: Firewall Settings .......................................... 111
4.1.1.2 System -> Management > Tab: CLI Terminals Provisioning .............. 112
4.1.1.3 System -> Management > Tab: Access Settings ............................... 113
4.1.1.4 System -> System Setting > Tab: Security Settings ........................... 114
4.1.1.5 System -> Management > Tab: Access Addresses ........................... 115
Disabling RS-232 Serial Port ............................................................................. 116
Appendix-A Configuring GW in AS 5300 ....................................................... 117

5.1
5.2
5.3
5.4
5.5
Adding GW to the AS 5300 Element Manager Console ...................................... 117

Creating Service Node for the GW in AS 5300 Provisioning Manager ................ 120
Creating Logical Entity for the GW ...................................................................... 121
Translation from AS5300 to M3K GW ................................................................. 123
Troubleshooting Configuration ............................................................................ 124
5.5.1
Prerequisites ..................................................................................................... 108

IPv6 Address Assignment for Media .................................................................. 108
Configure IPv6 for Media ................................................................................... 109
GW Security Hardening .................................................................................. 110

4.1
Modify GW IP in AS 5300 with GW VLAN Media & Control IP ............................ 106

Switching Back to Single Network Interface ....................................................... 107
Configure IPv6 Address.................................................................................. 108

3.1.1
3.1.2
3.1.3
Version 1.6
AS5300 Translation Tool ................................................................................... 124
Appendix-B Trouble Shoot and Recover GW ............................................... 125

6.1
Using BootP to Install New Firmware to M3K ..................................................... 125
May 02, 2012
2011 Avaya Inc.

Version 1.6
List of Tables
Table 1-1: GW Default Networking Parameters ................................................................................. 20
Table 1-2: SNMPv3 MG Configuration .............................................................................................. 37
Table 1-3: SNMPv3 GW Configuration .............................................................................................. 40
Table 1-4: GW Firmware ................................................................................................................... 46
Table 1-5: Trunk SIP Frame -> Tab: General Settings ....................................................................... 48
Table 1-6: Trunk SIP Frame -> Tab: ISDN Settings ........................................................................... 50
Table 1-7: Trunk SIP Frame -> Tab: SIP Settings .............................................................................. 51
Table 1-8: Transmission Setting Frame -> Tab: General Info ............................................................ 52
Table 1-9: Frame: Fiber Group -> Sonet/SDH Table Entry - Tab: Sonet/SDH General Info ................ 54
Table 1-10: Trunk SIP Frame -> Tab: General Settings .................................................................... 56
Table 1-11: Trunk SIP Frame -> Tab: ISDN Settings ......................................................................... 59
Table 1-12: Trunk SIP Frame ->Tab: SIP Settings ............................................................................. 60
Table 1-13: Trunk SIP Frame -> Tab: ISDN Settings ......................................................................... 62
Table 1-14: Frame: Trunk Status - Tab: ISDN Settings ...................................................................... 63
Table 1-15: Frame: Trunk Status - Tab: ISDN Settings ...................................................................... 64
Table 1-16: Frame: System - > System Setting -> Tab: Application Settings ...................................... 67
Table 1-17: Frame: System - > Management -> CLI Terminals Provisioning ...................................... 68
Table 1-18: Frame: General Config -> Network -> Tab: QoS Settings ................................................ 69
Table 1-19: Frame: System > System Setting -> Tab: Security Settings............................................. 70
Table 1-20: Frame: VoIP- > Media -> Media Frame -> Tab: SRTP Settings ....................................... 72
Table 1-21: Frame: VoIP -> TDM -> TDM Frame -> Tab: System Timing ........................................... 73
Table 1-22: Frame: VoIP - > Media -> Media Frame -> Tab: Bypass Settings .................................... 74
Table 1-23: Frame: VoIP -> Media -> Media Frame -> Tab: Fax Settings........................................... 75
Table 1-24: Frame: VoIP -> Media -> Media Frame -> Tab: Modem Settings..................................... 76
Table 1-25: Frame: VoIP - > Media -> Media Frame -> Tab: RTP Settings. ....................................... 77
Table 1-26: Frame: VoIP - > Media -> Media Frame -> Tab: RTP Settings. ....................................... 78
Table 1-27: Frame: VoIP -> SIP -> SIP Protocol Definition -> Tab: General Info ................................ 79
Table 1-28: Frame: VoIP -> SIP -> SIP Protocol Definitions -> Tab: Proxy Server.............................. 80
Table 1-29: Frame: VoIP -> SIP -> SIP Protocol Definitions - Tab: Registration ................................. 82
Table 1-30: Frame: VoIP -> SIP -> SIP Protocol Definitions - Tab: Coders Group 0 ........................... 83
Table 1-31: Frame: VoIP ->SIP -> SIP Protocol Definitions -> Tab: Sup Services .............................. 84
Table 1-32: Frame: SIP > Protocol Definitions Tab: Authentication & Security ................................ 85
Table 1-33: Frame: VoIP -> SIP -> SIP Endpoints - Tab: Phones ...................................................... 86
Table 1-34: Frame: VoIP -> SIP - > SIP Routing - Tab: Routing Modes ............................................. 87
Table 1-35: Frame: VoIP -> SIP -> SIP Routing - Tab: IP to Hunt ...................................................... 88
Table 1-36: Frame: VoIP -> SIP -> SIP Manipulations - Tab: Definitions ............................................ 89
Table 1-37: Frame: VoIP -> SIP -> SIP Manipulations -> Tab: Destination Telecom to IP .................. 90
Table 1-38: Frame: VoIP -> SIP -> SIP Advanced Configuration -> Tab: General Features 1............. 91
Table 1-43: Frame: VoIP -> SIP -> SIP Advanced Configuration -> Tab: Transport Info ..................... 96
Table 1-44: Frame: VoIP -> SIP -> SIP Advanced Configuration -> Tab: Tone And Progress............. 97
Table 1-45: Frame: VoIP -> SIP -> SIP Advanced Configuration -> Tab: Debug ................................ 98
Table 1-46: Frame: VoIP -> SIP -> SIP Advanced Configuration -> Tab: MLPP ................................. 99
Table 1-47: Frame: VoIP -> SIP -> SIP Advanced Configuration -> Tab: MLPP ............................... 100
Table 1-48: Frame: VoIP ->SIP -> SIP Advanced Configuration -> Tab: SIP to ISDN Cause Mapping101
Table 2-1: VLAN Example IP Addresses ......................................................................................... 105
Table 4-1: Frame: VoIP -> Security > Tab: Firewall Settings .......................................................... 111
Table 4-2: Frame: System -> Management > Tab: CLI Terminals Provisioning .............................. 112
May 02, 2012
2011 Avaya Inc.

Version 1.6
Table 4-3: Frame: System -> Management > Tab: Access Settings ............................................... 113
Table 4-4: Frame: System -> System Setting -> Tab: Security Settings ........................................... 114
Table 4-5: Frame: General Config > Info & Security Tab: Web Access Addresses ........................... 115
May 02, 2012
2011 Avaya Inc.

Version 1.6
List of Figures
Figure 1-1: ACSyslog Setup Syslog for collecting logs ....................................................................... 21
Figure 1-2: BootP Preferences with Private IP Addresses.................................................................. 22
Figure 1-3 BootP Client Configuration with Private IP Addresses ....................................................... 23
Figure 1-4: Multiple Interface Table page........................................................................................... 25
Figure 1-5: Install Server and Trusted Root Cert and Private Key ...................................................... 30
Figure 1-6: Install Call Progress Tone File ......................................................................................... 31
Figure 1-7: PuTTY Key Generator ..................................................................................................... 32
Figure 1-8: PuTTY Configuration ....................................................................................................... 34
Figure 1-9: Add Files to EMS Software Manager ............................................................................... 38
Figure 1-10: Right click Globe to Add a Region ................................................................................. 39
Figure 1-11: Right click on Region to Add MG ................................................................................... 39
Figure 1-12 Enable HTTPS on EMS .................................................................................................. 41
Figure 1-13: Select the correct firmware from Software Upgrade File Manager list ............................. 45
Figure 2-1: Diagnostics Screen ....................................................................................................... 103
Figure 2-2: Color-Coding Showing Active and Redundant Blades .................................................... 104
Figure 2-3: Multiple Interface Table VLAN Settings.......................................................................... 105
Figure 6-1: BootP Client Preferences .............................................................................................. 126
Figure 6-2: BootP Client Configuration ............................................................................................ 127
May 02, 2012
2011 Avaya Inc.

Version 1.6
Setup Notes
Installation Site Name:
May 02, 2012
2011 Avaya Inc.

10
Version 1.6
General Introduction
This deployment guide describes the procedures for commissioning and securing the Audiocodes
Mediant 3000 (M3K) Gateway for use with Avaya Aura Application Server 5300 Solution.
Before starting the GW installation and commissioning procedures make sure you have performed or
obtained the items listed below that are described in next few pages:
Audiocodes EMS has been Installed, Configured, and Hardened
All Referenced documents are available, see next page for list of documents.
Obtain Required Software Tools
Customer Supplied Materials
Customer Network Information
This document has following major sections. These must be followed in the order they are
documented.
Installation and Configuration
Configure Multiple Network VLAN Interfaces
Configure IPv6 Addresses
GW Security Hardening
After completing each section following two steps should be performed.
Save the gateway configuration file (BOARD.INI file)

If possible, perform a basic call between the gateway and AS 5300 11xx IP Desk phone.
May 02, 2012
2011 Avaya Inc.

11
Version 1.6
Reference: Documentation
Listed below are the Audiocodes supplied documents that are referenced in this document.
Document #
Manual Name
LTRT-81911
MGCP-MEGACO Release Notes
LTRT-94709
Mediant 3000 SIP-MGCP-MEGACO Installation Manual
LTRT-89711
Mediant 3000 SIP User's Manual
LTRT-94013
Element Management System (EMS) Product Description
LTRT-91018
Element Management System (EMS) Users Manual
LTRT-94130
Element Management System (EMS) Server IOM Manual
Notes:
May 02, 2012
Contact AS 5300 support if you dont have full access to the Referenced
document listed above.
Throughout this manual and unless otherwise specified, the term device or
gateway or GW refers to the Audiocodes Mediant 3000 PRI Gateway.
2011 Avaya Inc.

12
Version 1.6
Required Software Tools

Before starting the installation procedure, ensure the following software tools are available:
M3K GW load file to be installed (.cmp file)
M3K GW Call Progress Tone file (.dat file)

ACSyslog.exe tool installed on the PC used for configuration
BootP M3K address configuration tool installed on the PC used for configuration
Putty telnet tool installed on the PC used for configuration

PuttyGen key generator installed on the PC used for configuration
Wireshark packet capturing tool installed on the PC used for configuration
May 02, 2012
2011 Avaya Inc.

13
Version 1.6
Customer Supplied Materials / Information

The following describes the equipments that must be prepared on site by the Customer before the
Mediant 3000 can be commissioned:
L2/L3 Switch or Routers with 1Gbps ports (4 are required for High Availability)
Audiocodes Element Management System (EMS) server
NTP Server for the Network Time Protocol
PC Terminal Console (EMS Client) to configure the M3K Gateway (Note: Installation laptop
may also be used)
Mediant 3000 (M3K) chassis installed in a 19" Telco rack
Screws and Washers to install M3K in the Telco rack (if not installed in Avaya provided
ARTS frame)
ESD wrist strap and banana plug or alligator clip
Phillips screw driver
Successful installation and configuration of the M3K is also dependent on customer supplied network
information. This network information must be available at the start of this method. Depending on the
customer application, there could be numerous M3K Gateways.
Customer Supplied Network Information on the next page lists the information required for
configuring a single M3K Gateway. Make copies of this section and complete with the required
information for each M3K Gateway.
May 02, 2012
2011 Avaya Inc.

14
Version 1.6
Customer Supplied Network Information

Parameter
Value
EMS IP Address
Comment
IP address of the Primary EMS if more than one EMS
installed.
NTP Server IP Address
Syslog Server IP Address
Required for TLS configuration

Required during installation, this can be the IP Address
of the Laptop/PC used to configure M3K
M3K Gateway TP Board Settings

M3K Global IP Address
(OAM network)
Public IP for reaching the M3K from AS 5300
Slot 1 private IP Address

(OAM network)
Private IP of Slot 1
Slot 3 private IP Address

(OAM network)
Private IP of Slot 3
Subnet Mask Prefix

(OAM network)
e.g. /24 = 255.255.255.0 , /16 = 255.255.0.0
Default Gateway IP
Address
Default GW Router IP
M3K Gateway VLAN IP Addresses

M3K Media&Control
IP Address
GW Media&Control IP address when VLAN configured
OAMP (VLAN ID)/

Network IP/ Prefix
e.g., (4013) / 192.168.20.0 / 24
Media&Contro (VLAN ID)/

Network IP/Prefix
e.g., (4012) / 192.168.30.0 / 24
M3K Gateway IPv6 Settings

Media IPv6 IP Address
Media IPv6 Netmask
Prefix
Media IPv6 Default GW
Address
May 02, 2012
e.g., 2001:19A8:A00:200::5
e.g., 64
e.g., 2001:19A8:A00:200::1
2011 Avaya Inc.

15
Version 1.6
M3K Gateway General Settings

EMS MG Region
For display only the folder name in EMS is containing

all M3K gateways. If none given use M3K PRI
Gateways as the region name
EMS MG Name
For display only, the symbolic name is given to this

M3K. If none given use AC M3K Gw-1
SNMPv3 Security Name
For display only, a name chosen for SNMPv3 security.

If none given use AudiocodesM3K
SNMPv3 Auth Key
This is a secret authentication key password used in

SNMPv3. Customer must provide an alphanumeric
authkey. If none given temporarily use RAPtor1234
SNMPv3 Privacy Key
This is a secret privacy key password used in

SNMPv3. Set to the same value as Auth key. If none
provided temporarily use RAPtor1234
QoS Settings Diff Serv

Network Service Class Diff
Serv
48
48 (default) Replace with Customer provided value if

necessary. Used for ICMP, ARP
Premium Service Class

Media Diff Serv
46

necessary. Used for RTP/SRTP Media traffic
Network Service Class Diff

Control Serv
40

necessary. Used for Call Control/SIP traffic
Gold Network Service

Class Diff Serv
26

necessary. Used for streaming traffic
Bronze Service Class Diff

Serv
10

necessary. Used for OAMP (Web/SNMP
Qos Settings VLAN Priority

Network Service Class
Priority (VLAN)

necessary.

Media Priority (VLAN)

necessary.
Gold Service Class Priority

(VLAN)

necessary.
Bronze Service Class

Priority (VLAN)

necessary.

Control Priority (VLAN)

necessary.
Qos Settings MLPP Precedence Calls

Diff Serv
40
40 (default) Used for MLPP Call SIP Control
RTP for Routine
46
46 (default) Used for media Routine
RTP for Priority
45
45 (default) Used for media Priority
RTP for Immediate
43
43 (default) Used for media Immediate
RTP for Flash
42
42 (default) Used for media Flash
RTP for Flash-Override
41
41 (default) Used for media Flash Override
RTP for Flash-OverrideOverride
41
May 02, 2012
41 (default) Used for media Flash Override-Override
2011 Avaya Inc.

16
Installation and Configuration
1.1
Introduction
Version 1.6
This document provides Avaya recommendation for the Element Management System (EMS)
parameter values for configuring AudioCodes' Mediant 3000 PRI gateway to properly Interop with
Avaya Aura AS 5300 Solution. The parameters are organized in this document according to the
features being provisioned.
Mediant 3000, housing contains one (simplex mode) or two (HA mode) of the following blade types:
TP-6310 compactPCI (cPCI) blade, providing up to three T3 or 1+1 STM-1/OC-3
interfaces, and two Gigabit Ethernet interfaces
TP-8410 cPCI blade, providing up to 63 E1/84 T1 interfaces and two Gigabit Ethernet
interfaces
In Simplex mode only one card is present and there is no active and standby capability. In HA mode
two cards are present where the GW provides active and standby capability. In HA mode if active
card goes down, the standby card takes over the GW functionality.
The M3K GW provides a built-in webserver for web accessing of the device for initial device setup. It
is recommended to use Audiocodes EMS server/client for routine configuration tasks to ensure the
consistency of the configuration, auxiliary, and cmp files used in the network. The Web access should
only be used for initial configuration and be disabled after the gateway has been properly configured
and running properly. But, never disable the built-in webserver itself.
It is assumed the person configuring the GW is familiar with EMS. Refer to EMS Users Manual to
get familiar with EMS Sec-3, Sec-4, Sec-5, and Sec-6.
Throughout this manual a parameter depicts the parameter as it appears in the EMS. For a
description of the EMS parameters refer to Mediant 3000 SIP User's Manual.
To Interop properly with AS 5300 only set the values shown in each section as specified. All
other parameters can remain set with the default values shown.
Note: Please consult with Avaya before changing any parameters that are not specified in
this document since the GW may not function properly with AS 5300. Configure only
the parameters documented in this document.
Always Click on Apply on EMS windows to configure parameter values. Save only
saves value on the EMS database, but not on the GW.
Always Reset the GW with Burn option selected after configuring or changing any
parameter.
May 02, 2012
2011 Avaya Inc.

17
1.2
Version 1.6
How to Save Configuration or Board.INI File

Follow one of the two ways below to save the Board.ini file. Keep incremental files when saving the
configuration. For example, name the file as Board1.ini, Board2.ini, etc.
Always, save the Board.ini file before starting any complex configuration or when all configurations
are complete and the device is operating properly.
1.2.1
Via Web Interface

a) Http to the MP/GW and login using user/password as Admin/Admin
b) In the middle click Device Actions and select Save Configuration File
c) Click the Save INI File button to save the Board.ini file in the local PC, name it Board1.ini,
Board2.ini, etc.
1.2.2
Via SSH Interface

a) SSH to the GW and login using the Username = Admin and Password = Admin for brand new
GW or the passphrase for public key for secure access
b) Start logging screen output of the SSH client being used (e.g., putty)
c) Type conf at the prompt
d) Type cf view and press return until all pages are done (see below example)
e) Type exit to logout from the SSH
f) Now save off the SSH client logfile and rename it Board1.ini, Board2.ini, etc.
login as: Admin
Admin@135.60.86.184's password:
SIP/ SECurity/ PStn/ DebugRecording/ MGmt/ ControlProtocol/ CONFiguration/ IPNetworking/ TPApp/ BSP/
PING SHow
conf
AutoUPDate SaveAndReset RestoreAllDefaults RestoreFactorySettings SetConfigParamDefault
GetConfigParam GetParameterDescription CHangeUserName CHangePassWord ConfigFile
SetConfigParam
cf view ration>cf view

;**************
;** Ini File **
;**************
;Board: TP 8410 HA
;Serial Number: 1104234
;Slot Number: 1
;Software Version: 6.20A.055.001
;DSP Software Version: 491096AE3 => 620.18
;Board IP Address: 135.60.86.184
;Board Subnet Mask: 255.255.255.224
;Board Default Gateway: 135.60.86.161
;Private IP Address: 135.60.86.181
;Redundant Private IP Address: 135.60.86.183
;Ram size: 512M Flash size: 32M
;Num of DSP Cores: 126 Num DSP Channels: 504
;Profile: NORTEL-IMS
May 02, 2012
2011 Avaya Inc.

18
Version 1.6
;Key features:;Board Type: TrunkPack 8410 ;Security: IPSEC MediaEncryption StrongEncryption EncryptControlProtocol
;E1Trunks=8 ;T1Trunks=8 ;PSTN Protocols: IUA=84 ;Coders: G723 G729 NETCODER GSM-FR G727 ;IP Media: VXML
VoicePromptAnnounc(H248.9) CALEA ;Channel Type: RTP ATM PCI DspCh=504 ;M3K HA ;Control Protocols: MGCP
MEGACO H323 SIP ;Default features:;Coders: G711 G726;
-- More --
May 02, 2012
2011 Avaya Inc.

19
1.3
Version 1.6
Physical Installation of the Mediant 3000 Gateway

Please follow the Mediant 3000 SIP-MGCP-MEGACO Installation Manual Section - 2 and Section
3 for the physical description and installation procedure for the gateway. After completing physical
installation of the GW follow the procedure described in this document for assigning the IP address.
1.4
Assign IP Address and New Install Mediant 3000 HA

The Mediant 3000 HA houses two TP-6310 or TP-8410 blades (Active and Redundant).These two
blades each have a private IP address (different from one another) for maintenance and initial
configuration. BootP will be used to configure these private IP addresses. In addition to these private
IP addresses, the device has a "global" IP address used by the Active blade for communicating with
the IP network and to the AS 5300 proxy. This global IP address is configured with Web or EMS
management tools and is a valid IP address that is different than the two private IP addresses of the
blades, but has to be in the same subnet. Customer network should provide all three of these IP
addresses.
To assign the private IP addresses and the global IP to the GW use the following methods:
1. Assign the private IP addresses using BootP and upgrade the firmware
2. Use HTTP to assign the Global IP address
The default networking parameters for the GW are show in Table 1-1.
Table 1-1: GW Default Networking Parameters
Parameter
Private IP Addresses
Subnet Mask
Default Gateway IP Address
Default Value
Blade in Slot 1: 10.1.10.10

Blade in Slot 3: 10.1.10.11
255.255.0.0
0.0.0.0
Note: On existing working gateway, when using Bootp application never re-ip and send a
new firmware load at the same time. Separate the steps, i.e. re-ip the box first and
then upgrade the firmware load with new IP.
May 02, 2012
2011 Avaya Inc.

20
1.4.1
Version 1.6
Assign Private IP Address Using BootP

Its recommended NOT to send the initial default configuration ini file using
BootP; this can lead to accidentally wiping out the existing configuration in
the GW. Upload the ini file to the GW using the web interface.
To assign private IP, follow these steps:

1.
Make sure Bootp is installed on the PC used for configuring the M3K.
2.
Make sure ACSyslog.exe is installed on the PC used for configuring the M3K
3.
Connect both laptop and M3K GW(primary interface port from the back of each card) to ports of an
Ethernet hub or non-tagged ports of the Ethernet switch as follows:
4.
5.
6.
Use a standard Ethernet cable to connect the network interface on your PC to a port on a network hub.
Use a two standard Ethernet cable to connect primary interface (GbE-1) from both cards on the back
of the GW to two other ports on the same hub/switch. Hub is preferred since all packets from GW can
be sniffed with Wireshark tool
For temporary use, change your laptop IP address to an IP address different from the two GW private IPs
but in the same network as the GW IP address. Change PCs subnet mask to GW subnet mask.
On the laptop, run the ACSyslog.exe application used for configuring the GW. Click
Options -> Settings and setup the Log File, Logging Method, and Text Alignment fields as shown in
figure below, then click Ok to save.
Now click the disk icon under File menu to start collecting syslog trace. The file created for collecting
trace will be shown at the bottom status bar of the ACSyslog application. After address assignment is
complete, remember to click this icon to stop collecting syslog trace.
Figure 1-1: ACSyslog Setup Syslog for collecting logs
May 02, 2012
2011 Avaya Inc.

21
Version 1.6
7.
Use a Phillips screw driver and loosen the two screws next to the two latches on each side of Slot 1 and
Slot 3 cards on the front side of GW (the bottom card is counted as Slot 1)
8.
Unseat both cards from Slot 1 and Slot 3. When unseating each card press on the red latch to unlock and
simultaneously turn outward the black latch firmly from both sides. Unseat just enough to disconnect it.
Never take the card out completely from its slot.
9.
On the PC, run the BootP application (supplied with the software package).
Figure 1-2: BootP Preferences with Private IP Addresses
10. Go to BootP application and select from menu Edit -> Preferences (see figure above)
i. Select check box ARP Manipulations Enabled, set Reply Type to Broadcast and ARP Type to
Dynamic
ii. Select check box Enabled under TFTP Server
iii. Make sure On Interface shows the IP address temporarily assigned to the LAN port of the PC/Laptop
connected to the Hub/Switch. Note: If a different IP is shown, temporarily disable the Wireless network
on the PC/Laptop.
iv. On the Directory field click the >> next to it and select the C:\BootPFiles folder.
v. Set Boot File Mask to *.cmp
vi. Set INI File Mask to *.ini
vii. Set Timeout field to 50
viii. Set Maximum Retransmissions to 29
ix. Click OK to save Preferences.
May 02, 2012
2011 Avaya Inc.

22
Version 1.6
11. Login to the M3K via Web by http://10.1.10.10, then click Configuration button on the left and select
System -> Syslog Settings. Set the Syslog Server IP Address to your laptop IP address and set
Enable Syslog = Enable.
12. From the BootP App Services menu, choose Clients; click the Edit Clients icon
Configuration screen is displayed. Refer to figure below as a reference.
; the Client
Figure 1-3 BootP Client Configuration with Private IP Addresses
13. Click the Add New Client icon
; a client with blank parameters is displayed
14. In the Client MAC field, enter the MAC address of the M3K Slot 1 gateway. The MAC address is printed
on Slot 1 card on the front.
15. Verify that the check box to the right of the Client MAC field is selected. This enables the particular client
in the BootP tool (if the client is disabled, no replies are sent to BootP requests).
16. In the Client Name field, enter a descriptive name for this client so that it's easier to remember which
gateway the record refers to. For example, this name could refer to the location of the M3K gateway. e.g.,
M3K-slot1-Lackland
17. In the IP field, enter the customer provided Slot 1 private IP address of that gateway. Use the normal
dotted decimal format.
18. In the Subnet field, enter the customer provided Subnet mask for that gateway slot. Use the normal
dotted decimal format.
19. In the Gateway field, enter the customer provided Default GW IP address.
20. In the TFTP Server IP make sure your PCs IP is displayed. Note: If its PC is a laptop with Wireless
network, temporarily disable it, so only IP configured for LAN connection to the Hub/Switch is displayed.
May 02, 2012
2011 Avaya Inc.

23
Version 1.6
21. Click Apply to save this entry to the list of clients.

22. Now for the Slot 3 card, create another entry based on the Slot 1 entry, by just changing the Client MAC,
Client Name, and IP field, then Click Apply to save a new entry for the Slot 3 card.
23. Click on each entry one at a time and verify that the data of all fields are entered correctly.
24. Click OK; the Client Configuration screen closes. Keep the BootP application running.
25. Start Wireshark program and start capturing packets to see whats occurring on the network.
26. Now reseat the Slot 1 card (you should hear a click when fully reseated) and it should send a BootP
request to the network and the PC running BootP sends the new private IP address to this card.
27. To confirm new IP address was assigned successfully, check the Wireshark captures to verify Slot 1 card
is using the new IP address.
28. If IP assign fails via BootP method (using firmware load 5.8 or 6.2), then do the following alternate method
to assign IP address, otherwise if bootp method was successful then skip this step and go to the next step.
Follow this alternate method for assigning IP address and upgrading firmware:
Use Putty to SSH to the M3K default IP (for new install) or existing private IP of Slot-1 with
user/password as Admin/Admin to access the CLI interface.
At the prompt CLI prompt type conf
Type gcp ip to list the current global IP and private IP of this card.
Type the exact scp command below to set the private IP address. Add space to separate each item.
scp ip <ip-address><space> <net mask><space> < default gw>
e.g., scp ip 10.13.77.7 255.255.0.0 10.13.0.1
sar to Save and Reset this card
29. Now un-seat the Slot 1 card.

30. Re-seat the Slot 3 card and repeat the same process of assigning and verifying the Slot 3 private IP
address.
31. Un-seat the Slot 3 card.
32. Now the private IP assignment is complete.
33. Close Bootp after finish
May 02, 2012
2011 Avaya Inc.

24
1.4.2
Version 1.6
Using HTTP to Assigning GW Global IP Address and Upgrade Firmware

Make sure the private IP address of each card have been successfully
assigned.
To Assign Global IP address using HTTP and Upgrade Firmware, follow these steps:
1.
If you are continuing from previous section, then skip this first step. Otherwise, disconnect the GW from
the network and reconnect the GW (primary interface from the back each card) and the PC used to
configure the GW to a Netgear hub/switch as follows:
2.
Use a standard Ethernet cable to connect the network interface on your PC to a port on a network
hub. Use a two standard Ethernet cable to connect primary interface (GbE-1) from both cards on
the back of the GW to two other ports on the same hub/switch. Hub is preferred since all packets
from GW can be sniffed with Wireshark tool.
3.
For temporary use, change your PCs IP address to an IP address different from the two GW private IPs in
the same network as the GW IP address. Change PCs subnet mask to GW subnet mask, and Default GW
IP to the same Default GW IP used by GW.
Access the GW Embedded Web Server of Slot 1
4.
HTTP to web interface with the private IP address that you assigned to the card in Slot 1
5.
Go to Configuration -> VoIP -> Network -> IP Settings page. See Figure 4 as reference. Enter 1 and
click the Add button and define the parameters below.
Note: If interface line already exists, then modify the parms as below.
Application type = OAMP + Media + Control
Interface Mode = IPv4 Manual
IP Address = GW global IP address in dotted decimal format
Prefix Length = In Prefix format
Gateway = Default GW IP
VLAN ID = 1 ( if network is already VLAN configured then set VLAN ID to the same network configured
VLAN ID and scroll down in the this Webpage and set VLAN mode = 1, then reset with burn option )
Interface Name = O+M+C
Figure 1-4: Multiple Interface Table page
May 02, 2012
2011 Avaya Inc.

25
Version 1.6
6.
Now save the configuration and Reset the device by going to Maintenance (or Management) ->
Maintenance -> Maintenance Actions. Ensure that Burn To Flash is set to Yes, and then click Reset.
7.
If you were unable to reset, then http with new global IP and then reset the GW with burn option set to yes.
8.
After M3K resets to verify that the GW went to HA mode successfully, this time access the GW with global
IP address i.e., http://global-IP-Address and login with Admin/Admin as user/password.
9.
Then Click Device Actions -> Save Configuration File and then Save to save a copy of the BOARD.INI
file.
10. Upgrade the firmware via Web by doing http://Slot-1-Private-IP (Slot-3 IP when doing slot 3) with Login
user/pwd as Admin/Admin. Click Maintenance (or Management) button, then under Software Update
click the Software Upgrade Wizard. Follow the prompt to enter the firmware file (e.g.,
TP8410_SIP_F6.20A.055.001.cmp) in your PC, then click Next to all other screens, then click Reset on
the last screen. Allow 3-4 minutes for the GW to reset.
11. For fresh installation of a GW, perform the steps to upload the initial default configuration INI file to the
M3K as stated in next section.
May 02, 2012
2011 Avaya Inc.

26
1.4.3
Version 1.6
Using HTTP to Upload Initial Default Configuration to M3K GW

Use this procedure for a fresh installation of a GW only. For either
Upgrading or Downgrading a GW skip this step.
To upload initial default configuration INI file to M3K, follow these steps:
1.
This step is for a fresh installation of a GW only. For either Upgrading or Downgrading a GW skip
this step. With Windows Notepad create a file called M3K-Parms.ini with only following lines, except
change the 47.102.228.135 IP address for SyslogServerIP parameter to your PCs IP address. Place this
M3K-Parms.ini in Windows Desktop folder.
SetDefaultOnIniFileProcess = 0
syslog PC address
SyslogServerIP = xxx.xxx.xxx.xxx
EnableSyslog = 1
SSHServerEnable = 1
DisableRS232 = 0
ActivityListToLog = 'afl', 'dr', 'fb', 'swu', 'ard', 'naa', 'spc', 'll'
DenyAuthenticationTimer = 60
EnableTPNCPSecurity = 1
AuthorizedTPNCPServers=1.1.1.1
WebAuthMode = 0
TelnetServerEnable = 0
WEBPasswordControlViaSNMP = 1
FORMAT WelcomeMessage_Index = WelcomeMessage_Text;
WelcomeMessage 0 = ****-------------------------------****;
WelcomeMessage 1 = **;
WelcomeMessage 2 = "** I have read & consent to terms";
WelcomeMessage 3 = "**
in IS user agreement.";
WelcomeMessage 4 = **;
WelcomeMessage 5 = ****-------------------------------****;
2.
This step is for a fresh installation of a GW only. (When Upgrading or Downgrading a GW skip this
step). Once, the GW is back up, verify you can login to this Slot 1 via web by doing http://Slot-1-Private-IP
(Slot-3 IP when doing slot 3) with Login user/pwd as Admin/Admin. Verify the firmware load version
displayed matches to the load upgraded. Now using Maintenance (or Management) -> Software
Upgrade click Load Auxiliary files to load the INI file that was created earlier called M3K-Parms.ini.
3.
Now un-seat the Slot 1 card.
4.
Re-seat the Slot 3 card and repeat the same process of upgrading the Slot 3 firmware to the latest version.
5.
Un-seat the Slot 3 card.
6.
Close the BootP application.
7.
Re-seat the Slot 1 card, then wait 5 min until Slot 1 card is back up and you can login to it via Web.
8.
Now re-seat the Slot 3 card.
9.
Now the GW will reset and will be back up in 5-6 min. If both cards reset properly then System and Shelf
LEDs on very left hand side should be Green.
10. Login via Web to Slot 1 Private address. Then Click Device Actions -> Save Configuration File and
then click Save INI File to save a copy of the BOARD.INI file.
11. Now the private IP assignment and update firmware are complete, tighten the screws next to the latches
May 02, 2012
2011 Avaya Inc.

27
Version 1.6
on both cards.
12. Now reconnect the M3K GW back to the network and the PC back to the network (change the PC IP as
necessary).
May 02, 2012
2011 Avaya Inc.

28
1.5
Version 1.6
Generate Certificate Signing Request (CSR) for the GW

This section describes how to create a Certificate Signing Request (CSR) and certificates for the GW.
Since, private key cannot be extracted from the GW, use the AS 5300 certmgr tool to generate a
custom CSR for the GW as described in the AS 5300 MOP document 105.1.3 AS 5300 Security
Hardening. Then use certmgr again to generate the pkcs12 certificate with the key.
1. Follow the AS 5300 Security Hardening MOP steps in Sec 8 Create Certificate Signing Requests
to generate a custom CSR for the GW.
2. Submit the CSR to CA i.e., DISA PKI group to issue signed certificates.
3. Obtain in pem format signed leaf certificate and CA root and intermediate root certificates from
CA.
4. Again follow AS 5300 Security Hardening MOP steps in Sec 10.1.1 to install the signed cert and
root certs into AS 5300 certificate database.
5. Follow AS 5300 Security Hardening MOP steps in Sec 10.1.2 to generate a gwcert.p12 PKCS12
file (make a note of the pass-phrase used in creating the PKCS12 file).
6. Use the following open SSL commands to extract the key out of the gwcert.p12 PKCS12 file.
$ openssl pkcs12 -nocerts -in gwcert.p12 -out gwkey-with-passphrase.pem
7. Use the following open SSL command to remove the passphrase from GW key.
$ openssl rsa -in gwkey-with-passphrase.pem -out gwkey.pem
8. Rename the signed leaf certificate obtained from CA to gwcer.pem
9. Use a text editor and combine the Intermediate Root cert (listed first) followed by CA root into a
single file. The certs should be separated with begin/end only. There should be no other
information in the file.
e.g., Call this root_combo_ca21_ca2.pem
begin
CA 21 root cert
end
begin
CA 2 root cert
end
10. Keep these three files (gwkey.pem, gwcer.pem, root_combo_ca21_ca2.pem) in a safe place
and proceed to next section to install these files in the GW.
May 02, 2012
2011 Avaya Inc.

29
1.6
Version 1.6
Install CA Issued Certificates on the GW

Upload the certs and key from previous step into the EMS using EMS Software Manager for safe
storage. Do not use EMS to install the certificates into the GW. The actual certs and key will be
loaded via Web. The cert files and keys should have .pem extension.
Trusted Root Cert This is the root certificate file (e.g., root_combo_ca21_ca2.pem)
Server Cert This is the GW certificate file (e.g., gwcer.pem)
Private Key This is the key file for the GW certificate (e.g., gwkey.pem)
Before uploading server certificate and the key file. Use open SSL command to ensure you have the
correct key file that will work with the server cert. Output from both lines below should match.
$ openssl x509 -noout -modulus -in gwcer.pem | openssl md5
$ openssl rsa -noout -modulus -in gwkey.pem | openssl md5
Upload the CA provided certs and the key using the Web Interface. All cert
files and keys must be in .pem format. Before installing, edit the .pem
Server cert file and ensure it only has one Begin Certificate and End
Certificate marker, i.e., multiple certs in one .pem file for Server cert is
not supported. Trusted Root cert can have multiple certs in one .pem file
Follow the steps below to load the certificates and key using WEB interface:
1.
To securely install the cert and private key, ensure GW and PC are disconnected from the main
network and locally connected to a private LAN using a Netgear Hub/Switch.
2.
Login via Web to Global IP Address and click Full radio button, then navigate to Configuration
-> System -> Certificates.
3.
On the right Browse to your local PC to the CA provided Server cert and click Send File.
4.
On the right Browse to your local PC to the CA provided Trusted Root cert and click Send File
5.
On the right Browse to your local PC to the CA provided Private Key and click Send File
6.
Using the WEB interface Save Board.ini file, then reset the GW (with the Burn to Flash option
enabled). Wait 5-6 min. then ensure you can Login to the GW via Web to Global IP.
Figure 1-5: Install Server and Trusted Root Cert and Private Key
May 02, 2012
2011 Avaya Inc.

30
1.7
Version 1.6
Install Call Progress Tone (CPT) File on the GW

Upload the CPT file into the EMS using EMS Software Manager for safe storage. Do not use EMS to
install the CPT file. The CPT file will be loaded via Web.
CPT file usa_tones_12_noheld.dat
Upload the Call Progress Tone file using the Web Interface. CPT file has
.dat extension.
Follow the steps below to load the CPT file using the WEB interface:
1.
To securely install the CPT file, ensure GW and PC are disconnected from the main network and locally
connected to a private LAN using a Netgear Hub/Switch.
2.
Login via Web to Global IP address and click Full radio button, then navigate to Management ->
Software Update -> Load Auxiliary Files.
3.
On the right scroll down until you see Call Progress Tones file field.
4.
Click Browse to your local PC to the CPT file called usa_tones_12_noheld.dat
5.
Click Load File. The web page should indicate file loaded successfully.
6.
Using the WEB interface Save the Board.ini file then reset the GW (with the Burn to Flash option
enabled). Wait for 5-6 min. then ensure you can Login via Web to Global IP address.
Figure 1-6: Install Call Progress Tone File
May 02, 2012
2011 Avaya Inc.

31
1.8
Version 1.6
Setup RSA public key for PuTTY SSH access to GW
To configure RSA public keys for Windows (using PuTTY SSHsoftware), take these steps:
1.
Run the file puttygen.exe (if you dont have it, search Google to get a copy) the PuTTY Key
Generator program starts, displaying the main window.
2.
Under Key on the menu bar, select the option SSH-2 RSA
3.
Under Parameters group, in the field 'Number of bits in a generated key', enter "1024 bits
4.
Under the Actions group, perform the following:

a. Click Generate button and move the mouse around the screen to have key generated until it
finished.
b. Enter a Private Key Passphrase (if none given by Customer use RAPtor4321) in Key
passphrase field.
c. Re-enter the same Private Key Passphrase in Confirm passphrase field
5.
Under the 'Actions' group, save the new private key to a file (*.ppk) on your PC, by clicking Save
private key.
6.
Under the 'Key' group, select and COPY the displayed public key encoded text between "ssh-rsa"
and "rsakey-.", as shown in the example below:
Figure 1-7: PuTTY Key Generator
May 02, 2012
2011 Avaya Inc.

32
7.
Version 1.6
Create a standalone INI file called SSH-Enable.ini containing the following 4 lines. The first line
(SetDefaultOnIniFileProcess = 0) will prevent the loss of any existing configuration. For
SSHAdminKey the value below is shown from the example above. Replace it with your generated
publc key (copied from previous step).
SSHAdminKey =
AAAAB3NzaC1yc2EAAAABJQAAAIB7DAJQNe3rTUnJ5r2kYV+Vh9eaqNyfyYJ/8JDPuPUbiJqDa4/w/hFs9o
5su8WxxFJz6bo3BwZDNwnZvORIMpTnC4uPWCEe9xnitxAceTXBtx5w6VNQuDBswYG8iqGJbrNx4dvvofe
sRNpQknBW0OZ8X16wCSXCeyR7oUO8339B2w==
SSHServerEnable=1
TelnetServerEnable = 0
Note: The key above due to word wrap is shown in multiple lines. In the SSH-Enable.ini file the key
should be specified in a single line. Splitting the key into multiple lines will cause error.
See the partial Notepad screenshot below how the above key specified in a single line.
8.
Save the above content and close the SSH-Enable.ini file.
9. Login to the GW via WEB to the Global IP address of the GW

10. Go to Device Actions -> Load Configuration File
11. Click Browse to locate SSH-Enable.ini file
12. Click Send INI File to upload the file and Reset the GW with burn option enabled. Allow 5-6 minutes
for the GW to reset and switch to HA. When you Log back via Web ensure on the home page High
Availability status is Operational.
13. Run the file PuTTY.exe; the PuTTY Configuration program starts.
14. In the 'Category' expand Connection, then SSH, and then select Auth; the 'Options controlling
SSH authentication' pane appears.
May 02, 2012
2011 Avaya Inc.

33
Version 1.6
Figure 1-8: PuTTY Configuration
15. Under the 'Authentication parameters' group, click Browse and then locate the private key file that
you created and saved in Step 5.
16. Connect to the GW with SSH
a. At the Login prompt, enter the user name Admin.
b. At the Passphrase prompt, enter the Key Passphrase created at Step 4.
c. As an example, when you login to the GW using Putty, you should see the following
interaction:
May 02, 2012
2011 Avaya Inc.

34
Version 1.6
login as: Admin

****-------------------------------****
**
** I have read & consent to terms
** in IS user agreement.
**
****-------------------------------****
Authenticating with public key "rsa-key-20050804"
Passphrase for key "rsa-key-20050804":
SIP/ SECurity/ MGmt/ DebugRecording/ ControlProtocol/ CONFiguration/

IPNetworking/ TPApp/ BSP/
PING SHow
/>
d. If you can login with SSH using the Public Key, then proceed to the next step. If you are unable
to login, rerun the private and public key generation steps from Step 1.
17. Now we will configure the GW to always require entering the passphrase for SSH login. Create a INI
file (text file called SSHRequirekey.ini) containing the following lines and load the INI file into the
GW by loging to the GW via Web and going to Device Actions -> Load Configuration File
SSHRequirePublicKey = 1
18. Using the WEB interface reset the GW (with the Burn to Flash option enabled). Wait for 5-6 min. to
allow the GW to completely re-initialize.
19. Now verify you can SSH to the gateway and you can access the GW using the passphrase.
20. Login to the GW via Web and Save a copy of the Board.ini file.
May 02, 2012
2011 Avaya Inc.

35
1.9
Version 1.6
Configure SNMPv3 Secure Communication

This section describes how to configure the GW to support SNMPv3 communications with the EMS. It
is important to remember the Authentication and Privacy keys created at Step 4, below. These keys
will be used when the GW is added to the EMSConfigure SNMPv3 parameters on the GW
1.
Login via Web to the Global IP Address of the GW.
2.
In the WEB interface, open the 'Management Settings' page (Configuration -> System -> Management
-> SNMP -> SNMP V3 Users)
3.
To add an SNMP v3 user, in the 'Add Index' field, enter 0, and then click Add button. A new row
appears.
4.
Configure SNMPv3 parameters as shown in the table in the next page.
5.
Click Apply
May 02, 2012
2011 Avaya Inc.

36
Version 1.6
Table 1-2: SNMPv3 MG Configuration

Step
Parameter Name
AS 5300 Recommended Value
User Name
Enter a User name AudiocodesM3K
Authentication Protocol
Select from dropdown SHA-1 as the Authentication Protocol.
Privacy Protocol
Select from dropdown AES-128 as the Privacy Protocol.
Authentication Key
Enter the Authentication Key passphrase from Customer provided

information. If none given, enter RAPtor1234.
Note: Do not enter encoded hex
Privacy Key
Enter the Privacy Key identical to Authentication Key.
Group
Read-write
Note: Write down the Authentication and Privacy key entered:

Authentication Key:
Privacy Key:
Note: Make sure you record in a safe place the Authentication Key and Privacy Key that has
been entered. These keys will be needed to connect to the GW as described in the
next section. Without these keys you will not be able to setup secure communication
between EMS and the GW.
May 02, 2012
2011 Avaya Inc.

37
1.10
Version 1.6
Adding a New File to the EMS Software Manager
The GW firmware (.cmp file) is available in a DvD .iso image that can be downloaded from
https://support.avaya.com/css/appmanager/css/support/Downloads/P0626#wlp_Downloads_Page
EMS Client has been installed on the PC used for configuration.

To add new files to the EMS Software Manager:
1. Run EMS Client application on the PC and login to the EMS server.
2. In EMS, go to Tools -> Software Manager; click the Add File icon (indicated with a plus sign in the
upper left corner of the Software Manager screen) or open the Actions menu and choose the option Add
File; the Add Files screen (shown in the figure below) opens.
3. Click the icon of a folder located adjacent to the CMP to be added, and in the dialog box that opens,
navigate to the file (saved in your PC); click OK.
4. Set Select Product to MEDIANT 3000 8410 or MEDIANT 3000 6310 based on blade type
5. Set Select Protocol to SIP.
6. Click OK to complete adding file to EMS Software Manager
Figure 1-9: Add Files to EMS Software Manager
May 02, 2012
2011 Avaya Inc.

38
1.11
Version 1.6
Adding the GW to EMS

Before proceeding ensure that EMS Server has been fully
installed and hardened.
EMS Client has been installed on the PC used for configuration.
Ensure that the EMS certs have been installed on the EMS Client
and on the EMS Server to securely configure the GW.
1.
Run EMS Client application on the PC and login to the EMS server.
2.
In the MG Tree, right click on the Globe and select Add Region
Figure 1-10: Right click Globe to Add a Region
3.
Give a descriptive Region Name and Description.
4.
Right click on the Region Name created in the previous step and click Add MG
Figure 1-11: Right click on Region to Add MG
May 02, 2012
2011 Avaya Inc.

39
Version 1.6
5.
Enter the MG Name, IP Address, which is the Global IP address of the M3K, and a Description.
6.
On the window that appears above, select SNMPv3 radio button and set the SNMPv3 parameters to the
exact values that were set in previous section (see table below)
7.
Click OK to add the M3K to EMS. If successful, EMS will connect to the GW and create an entry under the
Region and display a large graphics on the Status pane of EMS representing the M3K GW. The dark
shaded card labeled either 6310 or 8410 represents the active card and the light blue shaded card is the
standby card.
8.
Once communication with the GW is restored, Reset the GW with Burn option selected.
Table 1-3: SNMPv3 GW Configuration

Step
Parameter Name
Security Name
Enter the same User name entered for this GW.
Security Protocol
Select the authentication protocol that was entered for this GW.
Authentication Key
Enter the Authentication Key that was entered for this GW.
Privacy Protocol
Enter the Privacy Protocol that was entered for this GW.
Privacy Key
Enter the Privacy Key that was entered for this GW.
May 02, 2012
2011 Avaya Inc.

40
1.12
Version 1.6
Use GW with HTTPS Enabled on Hardened EMS

Once EMS is hardened, the EMS <-> MG communications must be done via HTTPS.
Right -click on MG-> Details of the GW on EMS and select the HTTPS Enabled checkbox.
Figure 1-12 Enable HTTPS on EMS
Note: If HTTPS Enabled is not selected on hardened EMS, then any software upgrade of GW
firmware will fail.
May 02, 2012
2011 Avaya Inc.

41
1.13
Version 1.6
Upgrade/Downgrade the GW Firmware Using EMS

if a new firmware load is received, upgrade the firmware
following the steps in this section.
If DoD certificate has been installed on the EMS Server, then
ensure it has been installed on the EMS Client PC, otherwise
Upgrade will fail.
Always Click on Apply on EMS windows to configure parameter values.
Save only saves value on the EMS database, but not on the GW.
1.13.1 Upgrade of GW Firmware from 5.8 to 6.2

The following section describe how to upgrade an existing AS 5300 2.0 M3K GW from 5.8 firmware load to AS
5300 3.0 M3K GW 6.2 firmware load. Do not follow this procedure for fresh installation and configuration
of AS 5300 3.0 M3K GW with 6.2 firmware load. For fresh installation of M3K, start at the beginning of this
document.
Also, follow the procedure described in this section for minor upgrade/downgrade the GW firmware between
6.2.x to 6.2.y versions
1.
From EMS, load the latest GW load (.cmp file) via EMS Tools -> Software Manager (see details in
section 1.10 Adding a New File to the EMS Software Manager)
2.
Using SSH, save a copy of the Board.ini file before performing the upgrade by following section 1.2.2 of
this document.
3.
From EMS, enable Telnet and SSH

i. For 5.8 GW, navigate in EMS to Network Frame -> Applications Tab; set Server Enable to enable
and SSH Server Enable to enable. Click Apply then Save.
May 02, 2012
2011 Avaya Inc.

42
Version 1.6
ii. For 6.2 GW, navigate in EMS to System->Management->CLI Terminal Frame; set the Server Enable
to Enable Secured and SSH Server Enable to Enable. Click Apply then Save.
4.
Enable the RS-232 serial port in M3K using SSH
Use Putty to SSH to the M3K GW as the admin user
At the CLI prompt type conf
At the prompt type the exact scp command below to enable the serial port
scp DisableRS232 0
sar to Save and Reset this card
May 02, 2012
2011 Avaya Inc.

43
5.
Version 1.6
Enable syslog in EMS

i.
For 5.8 GW, navigate in EMS to Info & Security Frame -> Diagnostic tab; set the Syslog
enable to Enable and enter IP of the syslog server. Click Apply then Save.
ii.
For 6.2 GW, navigate in EMS to System -> System Setting in Configuration pane ->
Diagnostics; set Syslog enable to Enable and enter the IP of the syslog server. Click Apply then
Save.
6.
On PC, start running the ACSyslog.exe tool on the syslog server and start capturing syslog to a file.
7.
From the EMS, select the GW and click Software Upgrade to upgrade GW firmware.
Note: If HTTPS Enabled is not selected on hardened EMS, then any

software upgrade of M3K GW firmware will fail.
May 02, 2012
2011 Avaya Inc.

44
8.
Version 1.6
Choose the correct firmware load from the list provided.

Figure 1-13: Select the correct firmware from Software Upgrade File Manager list
9.
On the Popup that appears after firmware load is selected, select System Reset Upgrade. Never select
HitlessUpgrade option (see figure below).
10. After Reset when GW is back on line, right click on the GW graphics, then select Configuration ->
Upload then click Yes to the pop-up window with Question on Upload configuration from unit to
database will detach all profiles and master profile. This will force the EMS to sync up with all GW
parameters (see figures below).
May 02, 2012
2011 Avaya Inc.

45
Version 1.6
11. After GW Reset, use EMS to disable Telnet Access and enable SSH Require Key if using RSA public key
for Putty SSH access to GW.
Navigate in EMS to System->Management->CLI Terminal Frame; set the Server Enable to Disable,
SSH Server Enable to Enable and SSH Require Public Key to Enable. Click Apply then Save.
12. From EMS, disable syslog by navigating to System -> System Setting in Configuration pane ->
Diagnostics; set Syslog enable to Disable. Click Apply then Save.
13. Save a new copy of the Board.ini file via SSH interface by following section 1.2.2 of this document.
Table 1-4: GW Firmware

GW Firmware Filename
AS 5300 Recommendation
TP8410_SIP_F6.20A.055.001.cmp
Use this or later version for M3K with 8410 cards
TP6310_SIP_F6.20A.055.001.cmp
Use this or later version for M3K with 6310 cards
May 02, 2012
2011 Avaya Inc.

46
Version 1.6
1.13.2 Downgrade of GW Firmware from 6.2 and 5.8

The following section describe how to downgrade an existing AS 5300 3.0 M3K GW from 6.2 firmware load to AS
5300 2.0 M3K GW 5.8 firmware load. Downgrading the GW firmware from 6.2 to 5.8 is very similar to Upgrading
the M3K.
1.
Save a copy of the Board.INI file via SSH interface by following section 1.2.2 of this document. Name it
Board-6.2-Original.ini
2.
In section 1.13.1, perform steps 3 thru 7.
3.
In section 1.13.1 in step 8, use the 5.8 firmware load TP8410_SIP_F5.80A.045.cmp (PRI interface M3K)
or TP6310_SIP_F5.80A.045.cmp (optical interface M3K).
4.
Complete Step 9 thru 13 in section 1.13.1.
5.
Now if this is not a permanent rollback to 5.8, then EMS can still remain in 6.2. Otherwise, if EMS needs to
be rollback to 5.8, then follow LTRT-94118_EMS_Server_IOM_Manual_v5_8.pdf to install 5.8 EMS.
6.
Now the downgrade of M3K is complete.
1.13.3 Major Upgrade/Downgrade of GW Firmware between 5.4 and 6.2

Upgrading the GW firmware from 5.4 directly to 6.2 is not supported, its recommended to upgrade the GW
sequentially from firmware 5.4 to 5.8 first, than from 5.8 than to 6.2. For upgrading GW firmware from 5.4 to
5.8, please refer to the AS 5300 R2.0 MOP 101.2.2 AS 5300 Install and Config Method for Audiocodes M3K
PRI GW and Audiocodes EMS User Manual for details on the upgrade procedure from 5.4 to 5.8. After
successfully upgrading to firmware 5.8; then follow the procedure specified in section 1.13.1 Upgrading of GW
Firmware from 5.8 to 6.2.
Downgrading the GW firmware from 6.2 directly to 5.4 is not supported, its recommended to downgrade
sequentially from firmware 6.2 to 5.8 first, then to 5.8 than to 5.4. For downgrading firmware from 6.2 to 5.8,
follow the procedure specified in section 1.13.2 Downgrading of GW Firmware from 6.2 to 5.8. After
successfully downgrading to firmware 5.8, then refer to the AS 5300 R2.0 MOP 101.2.2 AS 5300 Install and
Config Method for Audiocodes M3K PRI GW and Audiocodes EMS User Manual for details on the downgrade
procedure from 5.8 to 5.4.
May 02, 2012
2011 Avaya Inc.

47
1.14
Version 1.6
Configure DS1 Trunks for TP-8410 Board
1.14.1 Frame: VoIP -> PSTN -> DS1 Trunks Trunk SIP Frame
Trunk parameters cannot be configured without locking the trunk.
Select the Trunk row to be configured. Right click on the selected Trunk row, and then select
Maintenance -> Lock to lock the trunk. Once the trunk is locked select the Trunk SIP Frame in
Configuration pane to configure its parameters.
1.14.1.1 Tab: General Settings

Navigate to Trunk SIP Frame -> Tab: General Settings.
Table 1-5: Trunk SIP Frame -> Tab: General Settings

Step
Parameter Name
Protocol Type
T1_NI2ISDN
Clock Master
acCLOCK_MASTER_OFF
Framing Method
T1_FRAMING_ESF_CRC6
Line Code
acB8ZS
Trace Level
acNO_TRACE ( set acFULL_ISDN_TRACE to debug callp issues)
May 02, 2012
2011 Avaya Inc.

48
Version 1.6
1.14.1.2 Tab: ISDN Settings

Navigate to Trunk SIP Frame -> Tab: ISDN Settings.
May 02, 2012
2011 Avaya Inc.

49
Version 1.6
Table 1-6: Trunk SIP Frame -> Tab: ISDN Settings

Step
Parameter Name
Termination Side
acUESR_TERMINATION_SIDE
Q931 Layer Response Behavior
0x0
Incoming Calls Behavior
0x00
Outgoing Calls Behavior
1024
General CC Behavior
0x40
Use T1 PRI
Checked (Note: This results in General CC

Behavior = 0x40)
IUA Interface ID
-1
D-Channel Configuration
PRIMARY
ISDN NFAS Interface ID
255
10
Group Number
11
Duplicate Q931 Buff Mode
May 02, 2012
2011 Avaya Inc.

50
Version 1.6
1.14.1.3 Tab: SIP Settings

Navigate to Trunk SIP Frame -> Tab: SIP Settings.
Table 1-7: Trunk SIP Frame -> Tab: SIP Settings

Step
Parameter Name
Progress Indicator to ISDN
NotSet
Play Ring Back Tone To Tel
PreferIp
Local ISDN RB Source
gateway
Note: Nothing to set in tab Line Settings and the tab CAS Settings.
May 02, 2012
2011 Avaya Inc.

51
1.15
Version 1.6
Configure the Sonet/SDH Trunk for TP-6310 Boards
1.15.1 Frame: VoIP -> PSTN -> Trunk

In Configuration pane Navigate to Transmission Settings -> Tab: General Info
Table 1-8: Transmission Setting Frame -> Tab: General Info

Step
1
Parameter Name
Transmission Type
May 02, 2012

opticalSonetSdh
2011 Avaya Inc.

52
Version 1.6
1.15.2 Frame: Fiber Group

Navigate to Frame Fiber Group and the Sonet/SDH table is displayed as follows:
Double-click an entry in the Sonet/SDH table or select the entry and click Properties; the Sonet/SDH
Parameters Provisioning screen is displayed.
May 02, 2012
2011 Avaya Inc.

53
Version 1.6
Table 1-9: Frame: Fiber Group -> Sonet/SDH Table Entry - Tab: Sonet/SDH General Info
Step
Parameter Name
Medium Type
sonet
Medium Line Coding
NRZ
Medium Line Type
Short Single Mode
Medium Circuit Identifier
Leave it blank
Fiber Group Mapping Type
asynchronousVT15andDS1
Fiber Group KLM Numbering Scheme
Numbering_Scheme_MLK
Fiber Group APS Revert Mode
Unidirectional
Fiber Group APS Revert Mode
NonRevertive
Fiber Group APS Wait To Restore Time
May 02, 2012
2011 Avaya Inc.

54
Version 1.6
1.15.3 Frame: VoIP -> PSTN -> Trunks

Navigate to Frame: VoIP -> PSTN -> Trunks
Trunk parameters cannot be configured without locking the trunk.
Select the Trunk row to be configured. Right click on the selected Trunk row, and then select
Maintenance -> Lock to lock the trunk.
Once the trunk is locked select the Trunk SIP Frame in Configuration pane to configure its parameters.
May 02, 2012
2011 Avaya Inc.

55
Version 1.6
1.15.3.1 Tab: General Settings

Navigate to Trunk SIP Frame -> Tab: General Settings.
Table 1-10: Trunk SIP Frame -> Tab: General Settings

Step
Parameter Name
Protocol Type
T1_NI2ISDN
Clock Master
acCLOCK_MASTER_OFF
Framing Method
T1_FRAMING_ESF_CRC6
Line Code
acB8ZS
Trace Level
acNO_TRACE ( set acFULL_ISDN_TRACE to debug callp issues)
Dial Plan Name
Leave it blank
Auto Clock Priority
May 02, 2012
2011 Avaya Inc.

56
Version 1.6
1.15.3.2 Tab: ISDN Settings

Navigate to Trunk SIP Frame -> Tab: ISDN Settings.
May 02, 2012
2011 Avaya Inc.

57
May 02, 2012
2011 Avaya Inc.

Version 1.6
58
Version 1.6

Step
Parameter Name
Termination Side
acUESR_TERMINATION_SIDE
Q931 Layer Response Behavior
0x200
Explicit Interface ID
Checked (Note: Causes Q931 Response Behavior = 0x200)
Incoming Calls Behavior
0x00
Outgoing Calls Behavior
0x1024
General CC Behavior
0x40
Use T1 PRI
Checked (Note: This results in General CC Behavior = 0x40)
IUA Interface ID
-1
acDCH_CONFIG_SUMMARY
10
0 (Basically, Trunk #1 is coinfigured as Primary D channel)
11
Group Number
12
May 02, 2012
2011 Avaya Inc.

59
Version 1.6
1.15.3.3 Tab: SIP Settings

Navigate to Trunk SIP Frame -> Tab: SIP Settings.
Table 1-12: Trunk SIP Frame ->Tab: SIP Settings

Step
Parameter Name
Progress Indicator to ISDN
NotSet
PreferIp
Local ISDN RB Source
gateway
Note: Nothing to set for Tab Line Settings and CAS Settings.
May 02, 2012
2011 Avaya Inc.

60
1.16
Version 1.6
Configure NFAS Primary, Backup, NFAS Trunks

When NFAS trunks are configured, the Primary, Backup, and NFAS trunks must be configured and
unlocked in a particular order, otherwise configuration error will occur.
1) Lock each trunk and set the Trunk Protocol to NONE
2) Configure the Backup trunk in the group first then, unlock the Backup trunk.
3) Next, Configure the Primary trunk in the group and unlock it.
4) Finally, configure all the remaining trunks as NFAS trunk and unlock it.
This NFAS configuration example as shown above, is configured in the

following order (the order is important):
- Trunk#2 ( 1st Trunk ID) with NFAS Interface ID = 1 is setup as BACKUP
- Trunk#1 ( 0th Trunk ID) with NFAS Interface ID = 0 is setup as PRIMARY
- Trunk#3-#10 with incremental NFAS Interface ID are setup as NFAS
trunks
May 02, 2012
2011 Avaya Inc.

61
Version 1.6
In a NFAS trunk group, first the Backup Trunk (that is Trunk #2) is
configured and unlocked.

Step
Parameter Name
BACKUP
1 (Trunk #2 is setup as backup)
Group Number
Now go to General Settings and set the Protocol Type = T1 NI2ISDN
May 02, 2012
2011 Avaya Inc.

62
Version 1.6
Next the Primary trunk in the Trunk group is configured and unlocked.
Table 1-14: Frame: Trunk Status - Tab: ISDN Settings

Step
Parameter Name
PRIMARY
0 (Trunk #1 is setup as primary)
Group Number
May 02, 2012
2011 Avaya Inc.

63
Version 1.6
Finally, the remaining trunks (in this case Trunk#3-#10) are configured as
NFAS trunks and unlocked one at a time.
Table 1-15: Frame: Trunk Status - Tab: ISDN Settings

Step
Parameter Name
NFAS
2 (Trunk #3 is setup as NFAS)
Group Number
May 02, 2012
2011 Avaya Inc.

64
1.17
Version 1.6
Removing NFAS Group

Once NFAS trunks are configured, a user cannot re-configure the NFAS group. To re-configure or
completely remove NFAS group, do the following in the order listed below:
1. Lock all NFAS trunks, change their Protocol type to NONE and then unlock them.
2. Lock the Backup trunk if it exists. Change its Protocol type to NONE and then unlock it.
3. Lock the Primary trunk, change its Protocol type to NONE and then unlock it.
May 02, 2012
2011 Avaya Inc.

65
1.18
Version 1.6
Configuring GW Parameters
Each subsequent section contains where possible a EMS GUI screen shot of the TopFrame ->Frame
-> Tab -> Parameters (values on the right) followed by a table with steps to set the parameters for AS
5300.
In each section navigate to the Frame specified and configure only the parameters specified. All other
parameters can remain set with the default values. As each parameter is configured check the box
in each step to ensure the step has been completed.
On each configuration window on EMS always click Apply to

save the parameter value in the GW and EMS. Do not click the
Save button.
Note:
1. After configuring all parameter values described in this document, always reset
the GW (with Burn option selected on the reset prompt). This will ensure all
parameter settings are saved in the non-volatile memory.
2. After configuring all parameters save a copy of the Board.INI file that contains the
GW configuration.
May 02, 2012
2011 Avaya Inc.

66
Version 1.6
1.18.1 Frame: System -> System Setting

1.18.1.1 Tab: Application Settings
Navigate to Frame: System - > System Setting in Configuration pane -> Tab: Application Settings
Table 1-16: Frame: System - > System Setting -> Tab: Application Settings
Step
Parameter Name
Server IP Address
NTP Server IP Address from customer
Utc Offset
-21600 is U.S. central
May 02, 2012
2011 Avaya Inc.

67
Version 1.6
1.18.2 Frame: System -> Management

1.18.2.1 Tab: CLI Terminals Provisioning
Navigate to Frame: System - > Management -> CLI Terminals Provisioning in Configuration pane -> Tab: CLI
Terminals Provisioning
Table 1-17: Frame: System - > Management -> CLI Terminals Provisioning
Step
Parameter Name
Server Enable
Disable (to disable Telnet Access)
SSH Server Enable
Enable
May 02, 2012
2011 Avaya Inc.

68
Version 1.6
1.18.3 Frame: VoIP > Network

1.18.3.1 Tab: QoS Settings
Navigate to Frame: VoIP -> Network -> Network Frame in Configuration pane -> Tab: QoS Settings.
Table 1-18: Frame: General Config -> Network -> Tab: QoS Settings
Step
Parameter Name
Network Service Class Diff Serv
48
Premium Service Class Media Diff Serv
46
Premium Service Class Control Diff Serv
40
Gold Service Class Diff Serv
26
Bronze Service Class Diff Serv
10
Network Service Class Priority (VLAN)
Premium Service Class Media Priority (VLAN)
Gold Service Class Priority (VLAN)
Bronze Service Class Priority (VLAN)
May 02, 2012
2011 Avaya Inc.

69
Step
10
Parameter Name
Version 1.6
Premium Service Class Control Priority (VLAN)
1.18.4 Frame: System -> System Setting

1.18.4.1 Tab: Security Settings
Navigate to Frame: System > System Setting -> Tab: Security Settings
Table 1-19: Frame: System > System Setting -> Tab: Security Settings
Step
Parameter Name
TLS Version
TLS 1.0 Only
TLS FIPS 140 Mode
Enable
HTTPS Cipher String
EDH-RSA-DES-CBC3-SHA:DHE-RSA-AES128SHA:AES128-SHA:AES256-SHA:DES-CBC3-SHA
OCSP Enable
Enable if Customer Network has OCSP server
May 02, 2012
2011 Avaya Inc.

70
Step
Parameter Name
Version 1.6
OCSP Server IP
Enter the IP address of the OCSP server
OCSP Secondary Server IP
If available configure IP of Secondary OCSP
OCSP Server Port
Set to the port OCSP server receives requests
OCSP Default Response
Allow Peer Certificate
Require Strict Certification
Disable
May 02, 2012
2011 Avaya Inc.

71
Version 1.6
1.18.5 Frame: VoIP -> Media

1.18.5.1 Tab: SRTP Settings
Navigate to Frame: VoIP- > Media -> Media Frame in Configuration pane -> Tab: SRTP Settings
Table 1-20: Frame: VoIP- > Media -> Media Frame -> Tab: SRTP Settings
Step
Parameter Name
Enable Media Security
Enable
Packet MKI Size
May 02, 2012
2011 Avaya Inc.

72
1.18.6
Version 1.6
Frame: VoIP -> TDM -> TDM Frame
1.18.6.1 Tab: System Timing

Navigate to Frame: VoIP -> TDM -> TDM Frame -> Tab: System Timing
Table 1-21: Frame: VoIP -> TDM -> TDM Frame -> Tab: System Timing
Step
Parameter Name
TDM Bus Clock Source
Network
TDM Bus Fall Back Clock
Network
TDM Bus Local Reference
0 (zero based number - refers to 1st Trunk. If 1st Trunk is

not active, pick the next active Trunk)
May 02, 2012
2011 Avaya Inc.

73
Version 1.6
1.18.7 Frame: VoIP -> Media -> Media Frame

1.18.7.1 Tab: Bypass Settings
Navigate to Frame: VoIP - > Media -> Media Frame -> Tab: Bypass Settings.
Table 1-22: Frame: VoIP - > Media -> Media Frame -> Tab: Bypass Settings
Step
Parameter Name
Coder Type
G711Mulaw
Dynamic Jitter Buffer Min. Delay
150
Fax Bypass Payload Type
102
Modem Bypass Payload Type
103
May 02, 2012
2011 Avaya Inc.

74
Version 1.6
1.18.7.2 Tab: Fax Settings

Navigate to Frame: VoIP -> Media -> Media Frame -> Tab: Fax Settings.
Table 1-23: Frame: VoIP -> Media -> Media Frame -> Tab: Fax Settings
Step
1
Parameter Name
Transport Mode
May 02, 2012

Disable
2011 Avaya Inc.

75
Version 1.6
1.18.7.3 Tab: Modem Settings

Navigate to Frame: VoIP -> Media -> Media Frame -> Tab: Modem Settings.
Table 1-24: Frame: VoIP -> Media -> Media Frame -> Tab: Modem Settings
Step
Parameter Name
V21 Transport
Disable
V22 Transport
Disable
V23 Transport
Disable
V32 Transport
Disable
Bell Transport type
Disable
V34 Transport
Disable
V150.1 Allocation Profile
Leave this parameter to its default value
SSE Payload Type Rx
98
SSE Redundancy Depth
May 02, 2012
2011 Avaya Inc.

76
Version 1.6
1.18.7.4 Tab: RTP Settings

Navigate to Frame: VoIP - > Media -> Media Frame -> Tab: RTP Settings.
Table 1-25: Frame: VoIP - > Media -> Media Frame -> Tab: RTP Settings.
Step
1
Parameter Name
Base UDP Port
May 02, 2012

6000
2011 Avaya Inc.

77
Version 1.6
Table 1-26: Frame: VoIP - > Media -> Media Frame -> Tab: RTP Settings.
Step
1
Parameter Name
Broken Connection Event Timeout
May 02, 2012

3000
2011 Avaya Inc.

78
Version 1.6
1.18.8 Frame: VoIP -> SIP ->SIP Protocol Definition

1.18.8.1 Tab: General Info
Navigate to Frame: VoIP -> SIP -> SIP Protocol Definition -> Tab: General Info
Table 1-27: Frame: VoIP -> SIP -> SIP Protocol Definition -> Tab: General Info
Step
Parameter Name
Gateway Name
AS5300 subscribers domain name
Sip Session Expires
1800
Enable Early Media
Yes
Fax Used
NoFax
Session Expires Method
Update
Minimal Session Refresh Value
90
Use SIP URI For Diversion Header
Sip
Forking Handling Mode
Parallel
May 02, 2012
2011 Avaya Inc.

79
Version 1.6
1.18.8.2 Tab: Proxy Server

Navigate to Frame: VoIP -> SIP -> SIP Protocol Definitions -> Tab: Proxy Server.
Table 1-28: Frame: VoIP -> SIP -> SIP Protocol Definitions -> Tab: Proxy Server
Step
Parameter Name
Proxy Used
Yes
Proxy Name
AS5300 subscribers domain name
Enable Proxy Keep Alive
Disable
May 02, 2012
2011 Avaya Inc.

80
Step
Parameter Name
Version 1.6
Always Use Proxy
No
Proxy IP
If no rows present, click + to add a row and click Proxy IP

field and enter the proxy IP Address, for AS 5300 LSC
enter the master SESM Service IP or in case of MFSS
AS 5300 enter the SS SESM Service IP address.
May 02, 2012
2011 Avaya Inc.

81
Version 1.6
1.18.8.3 Tab: Registration

Navigate to Frame: VoIP -> SIP -> SIP Protocol Definitions - Tab: Registration
Table 1-29: Frame: VoIP -> SIP -> SIP Protocol Definitions - Tab: Registration
Step
1
Parameter Name
Is Register Needed
May 02, 2012

No
2011 Avaya Inc.

82
Version 1.6
1.18.8.4 Tab: Coders

Navigate to Frame: VoIP -> SIP -> SIP Protocol Definitions - Tab: Coders Group 0
Table 1-30: Frame: VoIP -> SIP -> SIP Protocol Definitions - Tab: Coders Group 0
Step
Parameter Name
Index - 0
g711Ulaw64k / 20 / 64 / 0
Index - 1
g711Alaw64k / 20 / 64 / 8
Index - 2
g711Ulaw64k_VBD/ 20 / 64 / 110
Index - 3
V1501mr/ 255 / 255 / 114
Index - 4
g729 / 20 / 8 / 18
Note:
After adding a Codec, if Status is shown Locked, then right-click on the row and select
unlock rows to unlock it.
May 02, 2012
2011 Avaya Inc.

83
Version 1.6
1.18.8.5 Tab: Sup Services

Navigate to Frame: VoIP ->SIP -> SIP Protocol Definitions -> Tab: Sup Services
Table 1-31: Frame: VoIP ->SIP -> SIP Protocol Definitions -> Tab: Sup Services
Step
Parameter Name
Enable Hold
Yes
Hold Format
connextionIP
Enable Transfer
Yes
Logical Prefix For Transferred Call
May 02, 2012
2011 Avaya Inc.

84
Version 1.6
1.18.8.6 Tab: Authentication & Security

Navigate to Frame: VoIP -> SIP -> SIP Protocol Definitions -> Tab: Authentication & Security
Table 1-32: Frame: SIP > Protocol Definitions Tab: Authentication & Security
Step
Parameter Name
SIPS Require Client Certificate
Enable ( Enables Mutual Authentication, make sure Server &

Trusted Root certificates have been downloaded into the
gateway before enabling this parm)
Media Security Behavior
Mandatory
TLS Handshake Interval
60
Peer Host Name Verification Mode
Disable
Verify Server Certificate
Enable
SRTP Offered Suites (crypto)
AES-CM-128-HMAC-SHA1 32 and AES-CM-128-HMAC-SHA1 80
May 02, 2012
2011 Avaya Inc.

85
Version 1.6
1.18.9 Frame: VoIP ->SIP -> SIP Endpoints

1.18.9.1 Tab: Phones
Navigate to Frame: VoIP -> SIP -> SIP Endpoints - Tab: Phones
Table 1-33: Frame: VoIP -> SIP -> SIP Endpoints - Tab: Phones
Step
Parameter Name
Starting Channel
Last Channel
24
Trunk/Hunt Group ID
Logical grouping of a set of trunks, start at 1,

then 2, and so on, to keep unique ID for each
trunk.
Trunk ID
0 for the 1st physical trunk (zero based

numbering for physical trunks)
Last Trunk ID
Zero based number. Same as Trunk ID if each

trunk is separate. If multiple trunks are
combined then enter highest trunk number.
E.g., To combine 3 physical trunks starting at
the first and ending at the last as a group, enter
Trunk ID = 0 and Last Trunk ID = 2
May 02, 2012
2011 Avaya Inc.

86
Version 1.6
1.18.10 Frame: VoIP -> SIP -> SIP Routing

1.18.10.1
Tab: Routing Modes
Navigate to Frame: VoIP -> SIP - > SIP Routing - Tab: Routing Modes
Table 1-34: Frame: VoIP -> SIP - > SIP Routing - Tab: Routing Modes
Step
Parameter Name
TEL To IP Routing Mode
RouteBeforeMap
IP to TEL Routing Mode
RouteBeforeMap
May 02, 2012
2011 Avaya Inc.

87
1.18.10.2
Version 1.6
Tab: IP to Hunt
Navigate to Frame: VoIP -> SIP -> SIP Routing - Tab: IP to Hunt
Table 1-35: Frame: VoIP -> SIP -> SIP Routing - Tab: IP to Hunt
Step
1
Parameter Name
Destination Phone Prefix

<AS 5300 MLPP Domain> / <norteltrkgrp parm value from the
GW logical entity configured in AS 5300>; consult AS 5300
configuration before setting this parameter (see Appendix-A)
e.g., uc.mil/tg_pvt_01
For Hotline Calls add two rows as follows (see figure above):
<AS 5300 MLPP Domain> / hotline
<AS 5300 MLPP Domain> / hotline-ccdata
e.g., uc.mil/hotline
uc.mil/hotline-ccdata
Trunk Hunt Group ID
Is the Trunk Group ID that should be used in SIP > Endpoints

when this Destination Phone Prefix matches.
Source Phone Prefix
Leave it blank
Address
Leave it blank
Source IP Group ID
-1
Destination Host Prefix
Leave it blank
Source Host Prefix
Leave it blank
Profile ID
May 02, 2012
2011 Avaya Inc.

88
Version 1.6
1.18.11 Frame: VoIP -> SIP -> SIP Manipulations

1.18.11.1
Tab: Definitions
Navigate to Frame: VoIP -> SIP -> SIP Manipulations - Tab: Definitions
Table 1-36: Frame: VoIP -> SIP -> SIP Manipulations - Tab: Definitions
Step
Parameter Name
Remove Prefix
Yes
Add Trunk Group ID As Prefix
Yes
May 02, 2012
2011 Avaya Inc.

89
1.18.11.2
Version 1.6
Tab: Destination Telecom to IP
Navigate to Frame: VoIP -> SIP -> SIP Manipulations -> Tab: Destination Telecom to IP
Table 1-37: Frame: VoIP -> SIP -> SIP Manipulations -> Tab: Destination Telecom to IP
Step
Parameter Name
Destination Prefix
Stripped Digits From Left
Prefix To Add
Leave it blank
Number of Digits to Leave
255
Source Prefix
Stripped Digits From Right
Suffix To Add
Leave it blank
Is Presentation Restricted
255
Source IP Address
10
Source Trunk Group ID
-1
11
Source IP Group ID
-1
May 02, 2012
2011 Avaya Inc.

90
Version 1.6
1.18.12 Frame: VoIP ->SIP -> SIP Advanced Configuration

1.18.12.1
Tab: General Features 1 (Part 1 of 2)
Navigate to Frame: VoIP -> SIP -> SIP Advanced Configuration -> Tab: General Features 1
Table 1-38: Frame: VoIP -> SIP -> SIP Advanced Configuration -> Tab: General Features 1
Step
Parameter Name
Secure Call From IP
No
SIP 183 Behavior
Disable
Use SIP TGRP
NortelHotline
User Agent Display Info
Audiocodes or audiocodesIPv6 for IPv6
May 02, 2012
2011 Avaya Inc.

91
1.18.12.2
Version 1.6
Step
Parameter Name
Enable TCP Connection Reuse
Enable
Enable Reason Header
Enable
Application Profile
4444
May 02, 2012
2011 Avaya Inc.

92
1.18.12.3
Version 1.6
Step
Parameter Name
Prack Mode
Supported
X Channel Header
Enable
Default Release Cause
Disconnect Calls on Broken Connection
Enable
May 02, 2012
2011 Avaya Inc.

93
1.18.12.4
Version 1.6
Step
Parameter Name
IP Alert Timeout
180
PSTN Alert Timeout
180
Reliable Connection Persistent Mode
Enable
May 02, 2012
2011 Avaya Inc.

94
1.18.12.5
Version 1.6
Step
1
Parameter Name
Enable Rekey After 181
May 02, 2012

Enable
2011 Avaya Inc.

95
1.18.12.6
Version 1.6
Tab: Transport Info
Navigate to Frame: VoIP -> SIP -> SIP Advanced Configuration -> Tab: Transport Info
Table 1-43: Frame: VoIP -> SIP -> SIP Advanced Configuration -> Tab: Transport Info
Step
Parameter Name
Transport Type
tls
Destination Port
5061
Local SIP Port
5060
TCP Local SIP Port
5060
TLS Local SIP Port
5061
May 02, 2012
2011 Avaya Inc.

96
1.18.12.7
Version 1.6
Tab: Tones and Progress
Navigate to Frame: VoIP -> SIP -> SIP Advanced Configuration -> Tab: Tone And Progress
Table 1-44: Frame: VoIP -> SIP -> SIP Advanced Configuration -> Tab: Tone And Progress
Step
1
Parameter Name
May 02, 2012

PreferIp
2011 Avaya Inc.

97
1.18.12.8
Version 1.6
Tab: Debug
Navigate to Frame: VoIP -> SIP -> SIP Advanced Configuration -> Tab: Debug
Table 1-45: Frame: VoIP -> SIP -> SIP Advanced Configuration -> Tab: Debug
Step
1
Parameter Name
Debug Level
May 02, 2012

logLevel5
2011 Avaya Inc.

98
1.18.12.9
Version 1.6
Tab: MLPP (Part 1 of 2)
Navigate to Frame: VoIP -> SIP -> SIP Advanced Configuration -> Tab: MLPP
Table 1-46: Frame: VoIP -> SIP -> SIP Advanced Configuration -> Tab: MLPP
Step
Parameter Name
Call Priority Mode
MLPP
Default Name Space
DSN
Diff Serv
40
Preemption Tone Duration
0 (GW does not apply any Preemption tone)
Default Service Domain
000000 (this value is used for Precedence domain in IP

side in outgoing INVITE if Precedence IE is missing in
MLPP call from ISDN side)
Normalized Service Domain
000000 (this value is used to override Precedence domain

value coming in from ISDN side and used for Precedence
domain in IP side in outgoing INVITE)
May 02, 2012
2011 Avaya Inc.

99
1.18.12.10
Version 1.6
Tab: MLPP (Part 2 of 2)
Navigate to Frame: VoIP -> SIP -> SIP Advanced Configuration -> Tab: MLPP
Table 1-47: Frame: VoIP -> SIP -> SIP Advanced Configuration -> Tab: MLPP
Step
Parameter Name
RTP DSCP for MLPP Routine
46
RTP DSCP for MLPP Priority
45
RTP DSCP for MLPP Immediate
43
RTP DSCP for MLPP Flash
42
RTP DSCP for MLPP Flash-Override
41
RTP DSCP for MLPP Flash-OverrideOverride
41
E911 MLPP Behavior
standardMode
May 02, 2012
2011 Avaya Inc.

100
1.18.12.11
Version 1.6
Tab: SIP to ISDN Cause Mapping (for Hybrid Routing)
Navigate to Frame: VoIP ->SIP -> SIP Advanced Configuration -> Tab: SIP to ISDN Cause Mapping
Click + to Add the two rows with SIP Response and Q850 Cause values as shown. These mapping are required
for AS 5300 Hybrid Routing feature.
Table 1-48: Frame: VoIP ->SIP -> SIP Advanced Configuration -> Tab: SIP to ISDN Cause Mapping
Step
Parameter Name
Row 1 SIP Response / Q850 Cause
404 / 1
Row 1 SIP Response / Q850 Cause
410 / 1
May 02, 2012
2011 Avaya Inc.

101
Version 1.6
Configure Multiple Network / VLAN Address
2.1.1
Prerequisites
This section describes actions that you should perform before configuring Mediant 3000 HA Systems
for operating in a VLAN environment. If Customer Network Information does not contain VLAN
information, then skip this section..
Before start use SSH to save a copy of the BOARD.INI file with current GW configuration in a
safe place.
Make sure ACSyslog server is running and capturing data during VLAN setup.
Make sure customer network is VLAN enabled before configuring the VLAN parameters of
the GW. Otherwise, the GW may not function properly
2.1.2
VLAN Network Information

If Customer Network Information does not contain VLAN information, then
skip this section. Make sure customer network is VLAN enabled before
configuring the VLAN parameters of the GW. Otherwise, the GW may not
function properly.
VLAN IP addresses must be entered correctly with extreme

care.
VLAN setup in this section is shown with a color coded example set of IP addresses. During
deployment replace these IP Addresses with Customer Network IP addresses.
2.1.2.1
Initial IP Addresses
The local active (slot 1) and redundant (slot 3) blade IP addresses as well as the Mediant 3000
Global (OAM) IP address must be valid addresses residing on the OAM subnet according to
the IP addressing scheme. When planning an installation with multiple IP addresses, its a minimum
requirement to assign a private IP address for each of the blades and a Global (OAM) IP address.
Note: Ensure that the existing local and Global (OAM) IP addresses are in the OAM subnet.
If not, reassign the private IP addresses and the Global (OAM) IP address of the
Mediant 3000.
2.1.2.2
Syslog Server
It is recommended to run the Syslog server during the VLAN configuration process to identify any
potential issues during the device reset. The PC running the Syslog server should reside in the same
OAM subnet as the Mediant 3000. If required, temporarily connect a laptop to the upstream router
from the Mediant 3000. If Syslog server is not in same OAM subnet, then add a static route to the
Syslog server subnet.
May 02, 2012
2011 Avaya Inc.

102
Version 1.6
To configure the Syslog, do the following:

1.
In the MG Tree, select the required device.
2.
On the Navigation pane, select System, and then click System Setting in Configuration pane; the
Parameters List frame appears.
3.
Select the Diagnostics tab; the 'Diagnostics' screen appears.
4.
Configure Syslog server Ip Address to syslog server
5.
Set Syslog enable to Enable to start sending syslog to the syslog server.
Figure 2-1: Diagnostics Screen
2.1.2.3
Verifying the Active Blade

Before configuring a VLAN environment, verify the following:
The Active blade in Slot 1 has been assigned a Global (OAM) IP address. It should be displayed
in black as shown below (not grey). The redundant blade in Slot 3 is connected. It should be
displayed in blue.
If Slot 3 is shown active (i.e., black), then perform a switchover (i.e. Right Click on 8410 text
then select Maintenance -> Switch over from the popup menu.
May 02, 2012
2011 Avaya Inc.

103
Version 1.6
Figure 2-2: Color-Coding Showing Active and Redundant Blades
2.1.3
Configuring Static Routes

In 6.2 EMS, it is no longer needed to add manually static routes. The GW should route the following
via OAM subnet. After configuring VLAN verify all items below are reachable from the GW:
EMS server IP Address
May 02, 2012
Syslog server subnet (if on a different subnet)

PC used for configuration if in a different network than EMS server subnet.
NTP server network (if in a different subnet)

SNMP trap destinations, going to other servers (i.e. not just EMS)
2011 Avaya Inc.

104
2.1.4
Version 1.6
Configuring Multiple VLAN Interfaces

The procedure below describes how to configure multiple VLANs (OAM and MediaControl) using the
example IP addresses listed in the Table below. Refer to the M3K screen shot below how the IPs are
configured for multiple VLAN.
Table 2-1: VLAN Example IP Addresses

Example Parameter
Example IP Address
MP OAM IP Address
200.20.9.230
MP OAM Net mask Address
/24
MP OAM Default GW IP Address
200.20.9.1
OAM VLAN ID
133
MP SIP Media and Control IP Address
200.20.10.239
MP SIP Media and Control Net mask IP Address
/24
Customer Network IP Addr
MP SIP Media and Control Default GW IP Address 200.20.10.1

SIP VLAN ID
132
Figure 2-3: Multiple Interface Table VLAN Settings
May 02, 2012
2011 Avaya Inc.

105
Version 1.6
To configure multiple VLAN interfaces:

6.
Before configuring VLAN make sure you have saved off a copy of the INI file and complete the
Prerequisite steps in Section in 2.1.1
7.
Login via the Web interface to the M3K to configure VLAN.
8.
Navigate to VoIP->Network->IP Settings
9.
Select the IP Settings; the Multiple Interface Table window appears on the right.
10. Click the 0th Index radio button, then click EDIT button to modify OAM interface
11. Modify the OAM interface parameters to correspond to the values below:
Application Type: OAM (select from the dropdown)
IP Address:
200.20.9.230 (OAM IP of the in the example)
Prefix Length:
24 (Corresponds with the NET MASK of 255.255.255.0)
Gateway:
200.20.9.1 (OAM default GW in this example)
VLAN ID:
133 (Varies by network)
Interface Name: oam (name this interface)

12. Click Apply.
13. Enter 1 next to Add Index, and then click the Add Index button to add a second row for the Media and
Control interface.
14. Modify the MEDIA + CONTROL interface parameters to correspond to the values below:
Application Type: Media&Control
IP Address:
200.20.10.239 (Media & Control IP Address in this example)
Prefix Length:
24 (in this example)
Gateway:
200.20.10.1 ( media/control default GW in this example)
VLAN ID:
132 (in this example Varies by network)
Interface Name: mediactl (name this interface)

15. Double check and ensure all the IP, Default GW IP and VLAN ID are entered correctly.
16. Click Apply
17. Set the ' VLAN Mode' to Enable
18. Set the 'Native VLAN ID' to 1 (by default) [ see Warning Note below ]
19. Click Done
20. Reset the GW with burn option selected.
21. After GW has been reset, request to change the Ethernet switch port connected to this GW to tag
both OAM and Media/Signal packets sent to this GW.
Note: The 'Native VLAN ID' is default to 1. If VLAN ID 1 is used for OAM or
MediaAndControl VLAN, make sure to use a different number for Native VALN ID.
For example, 50.
2.1.5
Modify GW IP in AS 5300 with GW VLAN Media & Control IP
After VLAN Media & Control IP has been configured, be sure to go back to AS 5300 Element Manager Console
and replace the GW IP address with the Media & Control IP that has been configured on the GW.
May 02, 2012
2011 Avaya Inc.

106
2.1.6
Version 1.6
Switching Back to Single Network Interface

The procedure below describes how to configure your network back to a single network interface
environment, after you have already configured a VLAN environment. For example, whenever you
move the Mediant 3000 device to another subnet, you must initially switch back to a single network
interface configuration before reassigning the IP addresses.
To switch back to a single network interface configuration:

1.
In the MG Tree, select the device that you want to configure.
2.
Ensure that the Active blade (displayed in black) in Slot 1 has the Global (OAM) IP before starting the
VLAN configuration.
3.
Double-click the Active blade.
4.
On the Navigation panel, select VoIP -> Network, and then click Network frame in Configuration pane;
the 'Network Parameters Provisioning' screen is displayed.
Select the IP Interface Settings tab; the 'IP Interface Settings' screen appears.
5.
6.
Change the 'VLAN Mode' field to 0 to disable the VLAN settings. The 'Native VLAN' should be set to the
default value (1).
7.
Delete all the rows in the Interface Table.
8.
Click Apply and close the window.
9.
Click the Reset button to reset the device (ensure that the Burn Configuration into Flash Memory
option is selected).
10. Close the 'Results Table' window; the device is reset in non-VLAN mode.
11. Right-click the Active blade, and then from the shortcut menu, choose Configuration and then click
Upload.
12. Click Done; the device now operates in its default (non-VLAN) mode.
Note: If in case you cannot access the GW via EMS, Web, or SSH after enabling VLAN, you
can use serial connection to the GW and set VLANMODE to 0, to disable the VLAN.
May 02, 2012
2011 Avaya Inc.

107
Configure IPv6 Address
3.1.1
Prerequisites
Version 1.6
This section configures IPv6 IP address and associated config parameter on the GW. If Customer
Network Information does not contain IPv6 information, then skip this section.
Before start save a copy of the BOARD.INI file with current GW configuration in a safe place.
Make sure ACSyslog server is running and capturing data during IPv6 address setup.
3.1.2
Make sure customer network supports IPv6 enabled before configuring the IPv6 address and
parameters of the GW. Otherwise, the GW may not function properly
IPv6 Address Assignment for Media

On EMS perform the following steps only to assign IPv6 address for media. The OAM and Control
will continue to use IPv4 address.
1.
Navigate to VoIP -> Network -> Network Frame in Configuration pane, IP Interface Settings (see above
figure)
2.
Click on the + to add a row.
3.
Enter Application Types = media
4.
Enter Interface Mode = IPv6Manual
5.
Enter IP Address = IPv6 IP address from the Customer Network information,
6.
Prefix will automatically get data filled with 64
7.
Enter Default GW Address = IPv6 default GW from the Customer Network Information
8.
Enter VLAN ID = 0
9.
Enter the Interface Name = M, then click Tab to stop entering data on this field.
10. Click Apply to configure the address.
May 02, 2012
2011 Avaya Inc.

108
3.1.3
Version 1.6
Configure IPv6 for Media
1. Navigate to Voip -> SIP -> SIP Protocol Definitions -> General Info
2. Scroll down and under the IPv6 set the Media IP Version Preference field to preferIPv6
3. Click Apply to save the setting.
4. Reset the GW with Burn Option selected. Wait 5-6 minutes for the GW to completely re-initialize.
5. Use SSH interface to login and save a copy of the Board.INI file.
May 02, 2012
2011 Avaya Inc.

109
Version 1.6
GW Security Hardening
Follow the steps in this section with extreme care to harden the GW.
4.1
Prerequisite Steps
Before proceeding with hardening steps perform the following steps:
1.
Save a copy of the Board.INI file via SSH interface by following section 1.2 of this document.
2.
Make sure ACSyslog is running and start capturing before hardening steps are started
May 02, 2012
2011 Avaya Inc.

110
4.1.1.1
Version 1.6
VoIP -> Security > Tab: Firewall Settings
Navigate to VoIP -> Security > Security Frame ->Tab: Firewall Settings
Add following rows to the Firewall table as specified below to block any traffic arriving to these ports.
Table 4-1: Frame: VoIP -> Security > Tab: Firewall Settings
Source IP Netmask
Start
Port
End
Port
Protocol
Packet
Size
Byte
Rate
Byte
Burst
Allow
Type
Match
Count
0.0.0.0
0.0.0.0
5060
5060
Any
Block
0.0.0.0
0.0.0.0
80
80
Any
Block
0.0.0.0
0.0.0.0
443
443
Any
Block
0.0.0.0
0.0.0.0
2424
2424
Any
Block
0.0.0.0
11.3.9.1
80
80
Any
Allow
0.0.0.0
11.3.9.2
80
80
Any
Allow
May 02, 2012
2011 Avaya Inc.

111
4.1.1.2
Version 1.6
System -> Management > Tab: CLI Terminals Provisioning
Navigate to System -> Management > CLI Terminals Frame -> Tab: CLI Terminals Provisioning
Table 4-2: Frame: System -> Management > Tab: CLI Terminals Provisioning
Step
1
Parameter Name
Server Enable
May 02, 2012

Disable (disables Telnet access to the GW)
2011 Avaya Inc.

112
4.1.1.3
Version 1.6
System -> Management > Tab: Access Settings
Navigate to System -> Management > Web Frame -> Tab: Access Settings
Table 4-3: Frame: System -> Management > Tab: Access Settings
Step
Parameter Name
Disable WEB Config
Disable (DisableWebConfig - to make Web access read-only no

changes can be made via Web
HTTPS Only
Enable (HTTPSOnly - so HTTPS will be used for WEB access i.e.,

https://M3K-Global-IP-Addrs) SEE Warning Note below for https to
work properly.
WEB Deny Authentication Timer
60 (DenyAuthenticationTimer - after 60 sec auto logout SSH session -)
Note: In the Internet Explorer make sure under Tools -> Internet Options Advanced
Tab in Security section the parms are set as follows: Use SSL 2.0 = un-checked, Use SSL
3.0 = checked, and Use TLS 1.0 = checked.
May 02, 2012
2011 Avaya Inc.

113
4.1.1.4
Version 1.6
System -> System Setting > Tab: Security Settings
Navigate to System -> System Setting -> Tab: Security Settings
Table 4-4: Frame: System -> System Setting -> Tab: Security Settings
Step
Parameter Name
HTTPS Require Client Certificate
Enable (HTTPSRequireClientCertificate - once enabled

requires client certificate for HTTPS connection)
SEE Warning note below regarding certificate import.
AUPD Verify Certificates
Enable (AUPDVerifyCertificates for secure download of .cmp

file from EMS to GW)
Note: In the Internet Explorer (IE) make sure under Tools -> Internet Options
Advanced Tab in Security section the parms are set as follows: Use SSL 2.0 = unchecked, Use SSL 3.0 = checked, and Use TLS 1.0 = checked. Also under Tools ->
Internet Options Content, click Certificates and Import the Server Certificate into the
IE that is signed by the same CA to access the GW. Now when you access via https the IE
will prompt you to select the certificate to be used for communicating to the GW.
May 02, 2012
2011 Avaya Inc.

114
4.1.1.5
Version 1.6
System -> Management > Tab: Access Addresses
Navigate to System -> Management -> Web Frame > Tab: Access Addresses
Restrict SSH access (or WEB access if allowed via Firewall) to the GW only from the listed IP addresses.
Table 4-5: Frame: General Config > Info & Security Tab: Web Access Addresses
Step
Parameter Name
0 Index - IP
IP Address of the primary EMS
1 Index - IP
IP Address of the backup EMS
2 Index IP
Customer designated PC from where Web and SSH will

be allowed by the GW.
May 02, 2012
2011 Avaya Inc.

115
4.1.2
Version 1.6
Disabling RS-232 Serial Port

After the GW has been properly deployed, configured and verified everything is working correctly. If
possible, perform a basic call between the GW and AS 5300 11xx IP Desk phone.
As the last step, its recommended to reset the RS-232 serial port to disable in the GW.
Use Putty to SSH to the GW as the admin user

Type cmdshell to enter to command shell
At the CLI prompt type conf
At the prompt type the exact scp command below to disable the serial port
scp DisableRS232 1
sar to Save and Reset the GW
login as: Admin

Welcome to AudioCodes CLI
Admin@135.60.69.200's password:
Last login: Wed Dec 07 2011 at 12:20:50
Mediant 800>
Mediant 800> cmdshell
SIP/ SECurity/ PStn/ DebugRecording/ MGmt/ ControlProtocol/ CONFiguration/ IPNetworking/ TPApp/
BSP/
SHow
/>conf
conf
AutoUPDate SaveAndReset RestoreAllDefaults RestoreFactorySettings SetConfigParamDefault
SetConfigParam GetConfigParam GetParameterDescription CHangeUserName CHangePassWord
/CONFiguration>scp DisableRS232
May 02, 2012
2011 Avaya Inc.

116
Version 1.6
Appendix-A Configuring GW in AS 5300
This Appendix provides method for configuring a GW in AS 5300.
5.1
Adding GW to the AS 5300 Element Manager Console
1.
Login to AS 5300 Element Manager Console
2.
Under Network Data and Mtc -> Addresses name the GW ACGWAddr and enter the GW OAM IP
Address
Note: Once VLAN is configured change this address to GWs MediaCtl IP address.
3.
Add the GW under External Nodes with Name = ACGWND and Address = ACGWAddr
May 02, 2012
2011 Avaya Inc.

117
4.
Version 1.6
Add the GW under Informational Element as follows:

Shortname = ACGW
LongName = ACGW
Trusted = checked
ExemptionDoSProtection = un-checked
Port = 0
Type = Gateway
Node = select ACGW
Enable SIP UDP Port = unchecked
Enable SIP TCP Port = unchecked
Enable SIP TLS Port = checked
May 02, 2012
2011 Avaya Inc.

118
5.
Version 1.6
Add SIP Profile for Audiocodes GW:
May 02, 2012
2011 Avaya Inc.

119
5.2
Version 1.6
Creating Service Node for the GW in AS 5300 Provisioning

Manager
1.
Navigate to Service Node from Translations menu in AS 5300 Provisioning Manager
2.
Add a Service Node with GW Node Name
3.
For Address Name select the ACGWIE from the dropdown.
4.
Select Node type = audiocodes. This will ensure M3K GW uses audiocodes SIP Profile defined in AS
5300 Element Manager Console. Set this parm to audiocodesIPv6 if this GW will be provisioned with
IPv6.
5.
Check Is trusted and leave other boxes un-checked.
6.
After admin saves successful, click Domain and add the AS5300 domain(s) to service node.
May 02, 2012
2011 Avaya Inc.

120
5.3
Version 1.6
Creating Logical Entity for the GW
1.
Navigate to Logical Entity from Translations menu in AS 5300 Provisioning Manager
2.
Add a Logical Entity for the GW with logical entitiy name and parameters as figure below:
3.
Provide a name for the route e.g., rte1_acgw_pvt_01
4.
Select the GW node from Node dropdown
5.
Select Trunk Group from Parms and click Add, then provide a name for the Trunk group (e.g., tg_03)
6.
Select Facility Domain from Parms and click Add, then provide a name for the Facility domain, which is
the domain name (e.g., uc.mil)
7.
First save the Route.
8.
Then Save the le created.
May 02, 2012
2011 Avaya Inc.

121
9.
Version 1.6
Assign domain to the Logical Entity created for the GW
May 02, 2012
2011 Avaya Inc.

122
5.4
Version 1.6
Translation from AS5300 to M3K GW
1.
Based on the dial plan create Telephony routes for DSN and PSTN numbers
2.
Under Telephony Route create a Routelist called M3K_Routlist for the GW with Class of Service
= 2-LongDistance.
May 02, 2012
2011 Avaya Inc.

123
5.5
Troubleshooting Configuration
5.5.1
AS5300 Translation Tool
Version 1.6
In AS5300 PROV, there is a translation tool can be used to verify configuration.

Under Translations -> Translation Tool.
May 02, 2012
2011 Avaya Inc.

124
Version 1.6
Appendix-B Trouble Shoot and Recover GW
6.1
Using BootP to Install New Firmware to M3K

If HTTP access to the device fails, use BootP as alternate method to install
new Firmware. Procedure below assumes the M3K has completed re-ip
procedure.
When using Bootp application never re-ip and send a new firmware load at
the same time. Separate the steps, i.e. re-ip the box first and then upgrade
the firmware load with new IP.
To install New Firmware to M3K using BootP, follow these steps:
1.
Make sure Bootp and ACSyslog.exe are installed on the PC used for configuring the M3K.
2.
Make sure the M3K GW IP has been changed, change your PC IP to an IP in the same subnet as the new
IP assigned to the M3K GW (along with netmask and default GW IP).
Login to the M3K via Web by http://<new IP address of the M3K>, then click Configuration button on the
left and select System -> Syslog Settings. Set the Syslog Server IP Address to your laptop IP address
and set Enable Syslog = Enable.
3.
4.
On the PC, run the ACSyslog.exe application used for configuring the GW. Click
Options -> Settings and setup the Log File, Logging Method, and Text Alignment fields, then click Ok
to save.
5.
Now click the disk icon under File menu to start collecting syslog trace. The file created for collecting
trace will be shown at the bottom status bar of the ACSyslog application.
6.
Use a Phillips screw driver and loosen the two screws next to the two latches on each side of Slot 1 and
Slot 3 cards on the front side of GW (the bottom card is counted as Slot 1)
7.
Unseat both cards from Slot 1 and Slot 3. When unseating each card press on the red latch to unlock and
simultaneously turn outward the black latch firmly from both sides. Unseat just enough to disconnect it.
Never take the card out completely from its slot.
On the PC, run the BootP application (supplied with the software package).
8.
May 02, 2012
2011 Avaya Inc.

125
Version 1.6
Figure 6-1: BootP Client Preferences
9.
With Explorer create a folder under C:\ in installation PC called BootPFiles.
10. Put the GW load file e.g. TP8410_SIP_F6.20A.055.001.cmp to C:\BootPFiles folder.

11. Go to BootP application and select from menu Edit -> Preferences (see figure above)
i.
Select check box ARP Manipulations Enabled, set Reply Type to Broadcast and ARP
Type to Dynamic
ii.
Select check box Enabled under TFTP Server
iii.
Make sure On Interface shows the IP address temporarily assigned to the LAN port of the
PC/Laptop connected to the Hub/Switch. Note: If a different IP is shown, temporarily disable
the Wireless network on the PC/Laptop.
iv.
On the Directory field click the >> next to it and select the C:\BootPFiles folder.
v.
Set Boot File Mask to *.cmp
vi.
Set INI File Mask to *.ini
vii.
Set Timeout field to 50
viii.
Set Maximum Retransmissions to 29
ix.
Click OK to save Preferences.
12. From the BootP App Services menu, choose Clients; click the Edit Clients icon
; the Client
Configuration screen is displayed. Refer to Error! Reference source not found. figure below as a
reference.
May 02, 2012
2011 Avaya Inc.

126
Version 1.6
Figure 6-2: BootP Client Configuration
13. In the Boot File field enter the GW firmware file name and make sure to add a space and add -fb to
flash and burn the firmware. E.g., TP8410_SIP_F6.20A.055.001.cmp fb
14. Click Apply to save this entry to the list of clients.
15. Click on each entry one at a time and verify that the data of all fields are entered correctly.
16. Click OK; the Client Configuration screen closes. Keep the BootP application running.
17. Now reseat the Slot 1 card (you should hear a click when fully reseated) and it should send a BootP
request to the network and the PC running BootP sends the new private IP address to this card and starts
downloading the firmware. In the BootP application, verify that Status shows 0%, then 10% etc. until
100% OK status to indicate download is complete. Then the Slot 1 card will reset automatically. This step
will take 5-6 min. for upgrading the firmware. Watch the Syslog for reset process to complete.
18. This step is for a fresh installation of a GW only. (When Upgrading or Downgrading a GW skip this
step). Follow procedure in section 1.4.3 Using Web interface to Upload Initial Default Configuration to
M3K GW.
19. Now un-seat the Slot 1 card.
20. Re-seat the Slot 3 card and repeat the same process of upgrading the Slot 3 firmware to the latest version.
21. Un-seat the Slot 3 card.
22. Close the BootP application.
23. Re-seat the Slot 1 card, then wait 5 min until Slot 1 card is back up and you can login to it via Web.
24. Now re-seat the Slot 3 card.
25. Now the GW will reset and will be back up in 5-6 min. If both cards reset properly then System and Shelf
LEDs on very left hand side should be Green.
May 02, 2012
2011 Avaya Inc.

127
Version 1.6
26. Login via Web to Slot 1 Private address. Then Click Device Actions -> Save Configuration File and
then click Save INI File to save a copy of the BOARD.INI file.
27. Now the firmware upgrade is complete, tighten the screws next to the latches on both cards.
28. Reconnect the customer network cables to the back of the M3K GW Ethernet ports.
May 02, 2012
2011 Avaya Inc.

128
101.2.2 AS 5300 Install and Config Method for

Audiocodes M3K PRI GW
Version 1.6

101.2.2 As 5300 Install and Config Method For Audiocodes M3K PRI GW

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

101.2.2 As 5300 Install and Config Method For Audiocodes M3K PRI GW

Загружено:

Авторское право:

Доступные форматы

Avaya Aura AS 5300

101.2.2 AS 5300 Install and Config Method for

Copyright 2012 Avaya

Installation and Configuration..........................................................................17

Physical Installation of the Mediant 3000 Gateway ............................................... 20

Via Web Interface ................................................................................................ 18

Assign Private IP Address Using BootP ............................................................... 21

Generate Certificate Signing Request (CSR) for the GW ...................................... 29

1.14 Configure DS1 Trunks for TP-8410 Board ............................................................ 48

1.15 Configure the Sonet/SDH Trunk for TP-6310 Boards ........................................... 52

1.16 Configure NFAS Primary, Backup, NFAS Trunks .............................................. 61

2011 Avaya Inc.

1.18 Configuring GW Parameters................................................................................. 66

Configure Multiple Network / VLAN Address ................................................ 102

Prerequisites ..................................................................................................... 102

Prerequisite Steps .............................................................................................. 110

Appendix-A Configuring GW in AS 5300 ....................................................... 117

Adding GW to the AS 5300 Element Manager Console ...................................... 117

Prerequisites ..................................................................................................... 108

GW Security Hardening .................................................................................. 110

Modify GW IP in AS 5300 with GW VLAN Media & Control IP ............................ 106

Configure IPv6 Address.................................................................................. 108

AS5300 Translation Tool ................................................................................... 124

Appendix-B Trouble Shoot and Recover GW ............................................... 125

Using BootP to Install New Firmware to M3K ..................................................... 125

May 02, 2012

2011 Avaya Inc.

2011 Avaya Inc.

May 02, 2012

2011 Avaya Inc.

May 02, 2012

2011 Avaya Inc.

May 02, 2012

2011 Avaya Inc.

Save the gateway configuration file (BOARD.INI file)

May 02, 2012

2011 Avaya Inc.

MGCP-MEGACO Release Notes

Mediant 3000 SIP-MGCP-MEGACO Installation Manual

Mediant 3000 SIP User's Manual

Element Management System (EMS) Product Description

Element Management System (EMS) Users Manual

Element Management System (EMS) Server IOM Manual

May 02, 2012

2011 Avaya Inc.

Required Software Tools

M3K GW load file to be installed (.cmp file)

M3K GW Call Progress Tone file (.dat file)

Putty telnet tool installed on the PC used for configuration

May 02, 2012

2011 Avaya Inc.

Customer Supplied Materials / Information

May 02, 2012

2011 Avaya Inc.

Customer Supplied Network Information

NTP Server IP Address

Syslog Server IP Address

Required for TLS configuration

M3K Gateway TP Board Settings

Public IP for reaching the M3K from AS 5300

Slot 1 private IP Address

Slot 3 private IP Address

Subnet Mask Prefix