AudioCodes Mediant 3000, TP-8410, TP-6310 User Manual

Download

Page 1

Mediant™ 3000

VoIP Digital Media Gateway

MGCP & MEGACO Protocols

User's Manual

Mediant 3000 with TP-6310 & TP-8410

Version 6.6

December 2015

Document # LTRT-95211

Page 2

Page 3

User's Manual Contents

1 Introduction ......................................................................................................... 9

1.1 General Features ................................................................................................. 11

1.2 High Availability .................................................................................................... 13

1.2.1 Mediant 3000 HA System with TP-6310 ..................................................................13

1.2.2 Mediant 3000 HA System with TP-8410 ..................................................................14

1.2.3 Private IP Address and System (Global) IP Address(es) ........................................15

1.2.3.1 Private (Local) IP Address........................................................................15

1.2.3.2 System (Global) IP Address .....................................................................15

1.3 Functional Block Diagram - TP-6310 .................................................................... 16

1.4 Functional Block Diagram - TP-8410 .................................................................... 17

2 Software Package.............................................................................................. 19

2.1 Installing the Software Package ........................................................................... 19

2.1.1 Installing/Unzipping When Using a Windows™ Operating System ........................19

2.2 Software Directory Contents & Structure .............................................................. 20

3 Getting Started .................................................................................................. 21

3.1 Assigning the Device IP Address .......................................................................... 21

3.1.1 Assigning an IP Address Using HTTP .....................................................................21

3.1.2 Assigning an IP Addr ess Using Boot P ....................................................................22

3.2 Assigning the IP Addresses for High Availability Mode ......................................... 23

4 System Initialization Process ........................................................................... 25

4.1 Boot Firmware & Operational Firmware ................................................................ 25

4.2 Startup Process .................................................................................................... 26

4.3 Configuration Parameters and Files ..................................................................... 28

4.3.1 Initialization (ini) File ................................................................................................28

4.3.1.1 Parameter Value Structure .......................................................................29

4.3.1.2 Tables of Parameter Value Structure .......................................................31

4.3.1.3 Binary Configuration File Download .........................................................33

4.3.2 Auxiliary Files ...........................................................................................................33

4.3.2.1 Downloading Auxiliary Files via TFTP During the Blade Startup .............34

4.3.3 Automatic Update Facility ........................................................................................34

4.4 Backup Copies of ini and Auxiliary Files ............................................................... 37

4.5 Upgrading Device Software .................................................................................. 38

4.6 Software Upgrade Key ......................................................................................... 38

4.7 High Availability .................................................................................................... 39

4.7.1 Initializing the Mediant 3000 System .......................................................................39

4.7.2 Device Initialization Process ....................................................................................39

4.7.3 Special System Specific Behavior ...........................................................................39

4.7.3.1 Rebooting the Blade .................................................................................39

4.7.3.2 High Availability and Syslog .....................................................................40

4.7.4 Actions upon Detecting Blade Failure .....................................................................40

4.7.4.1 Failure in the Active Blade........................................................................40

4.7.4.2 Failure in the Redundant Blade ................................................................40

4.7.5 Hitless Software Upgrade ........................................................................................40

5 Configuration Using the Web Interface ........................................................... 43

5.1 Limiting the Web Interface to Read-Only Mode .................................................... 43

5.2 Disabling the Web Interface .................................................................................. 44

Version 6.6 3 Mediant 3000 with TP-6310 & TP-8410

Page 4

Mediant 3000 with TP-6310 & TP-8410

5.2.1 Encr ypted HTTP Transport (HTTPS - SSL) ............................................................44

5.2.2 Limiting Web Access to a Predefined List of Client IP Addresses ..........................44

5.2.3 Managing Web Server Access Using a RADIUS Server .........................................44

5.3 Initial Device Configuration using the Web Interface ............................................. 44

5.4 Accessing the Web Interface ................................................................................ 45

5.5 Using Internet Explorer to Access the Web Interface ............................................ 46

5.6 Getting Acquainted with the Web Interface ........................................................... 47

5.6.1 Toolbar .....................................................................................................................48

5.6.2 Navigation Tree .......................................................................................................49

5.6.2.1 Displaying Navigation Tree in Basic and Full View ..................................49

5.6.2.2 Showing / Hiding the Navigation Pane .....................................................50

5.6.3 Working with Configuration Pages ..........................................................................51

5.6.3.1 Accessing Pages ......................................................................................51

5.6.3.2 Viewing Parameters .................................................................................52

5.6.3.3 Displaying Basic and Advanced Parameters ...........................................52

5.6.3.4 Showing / Hiding Parameter Groups ........................................................53

5.6.3.5 Modifying Parameter Values ....................................................................54

5.6.4 Saving Configuration Changes ................................................................................55

5.6.5 Searching for Configuration Parameters .................................................................55

5.6.6 Working with Scenarios ...........................................................................................56

5.6.6.1 Creating a Scenario ..................................................................................57

5.6.6.2 Editing a Scenario ....................................................................................60

5.6.6.3 Saving a Scenario to a PC .......................................................................61

5.6.6.4 Loading a Scenario to the Device ............................................................62

5.6.6.5 Exiting Scenario Mode .............................................................................62

5.6.6.6 Deleting a Scenario ..................................................................................62

5.6.7 Creating a Login Welcome Message .......................................................................63

5.6.8 Getting Help .............................................................................................................64

5.6.9 Logging Off the Web Interface .................................................................................65

5.7 Using the Home Page .......................................................................................... 66

5.7.1 TP-6310 ...................................................................................................................66

5.7.2 TP-8410 ...................................................................................................................69

5.7.3 Viewing the Active Alarms Table .............................................................................70

5.7.4 Viewing Ethernet Port Information ...........................................................................71

5.7.5 High Availability Configuration .................................................................................72

5.7.5.1 Manual Switch Over / Redundant Board Reset .......................................73

5.8 Configuration ........................................................................................................ 74

5.8.1 System .....................................................................................................................74

5.8.1.1 Application Settings ..................................................................................74

5.8.1.2 Syslog Settings .........................................................................................76

5.8.1.3 Regional Settings .....................................................................................76

5.8.1.4 Certificates ...............................................................................................77

5.8.1.5 Management ............................................................................................78

5.8.2 VoIP .........................................................................................................................91

5.8.2.1 Network ....................................................................................................91

5.8.2.2 TDM & Timing ........................................................................................102

5.8.2.3 Security Settings ....................................................................................108

5.8.2.4 PSTN ......................................................................................................113

5.8.2.5 Media ......................................................................................................122

5.8.2.6 Call Control .............................................................................................136

5.8.2.7 V5.2 Configuration (For TP-8410 Only) .................................................141

5.9 Maintenance ....................................................................................................... 142

5.9.1 Maintenance ..........................................................................................................142

5.9.1.1 Maintenance Actions ..............................................................................142

5.9.1.2 High Availability Maintenance ................................................................145

5.9.2 Software Update ....................................................................................................146

5.9.2.1 Load Auxiliary Files ................................................................................147

User's Manual 4 Document #: LTRT-95211

Page 5

User's Manual Contents

5.9.2.2 Software Upgrade Key ...........................................................................148

5.9.2.3 Software Upgrade Wizard ......................................................................151

5.9.2.4 Configuration File ...................................................................................157

5.10 Status and Diagnostic Menu ............................................................................... 161

5.10.1 System Status ........................................................................................................161

5.10.1.1 Message Log ..........................................................................................161

5.10.1.2 Device Information .................................................................................162

5.10.1.3 Ethernet Port Information .......................................................................163

5.10.1.4 Carrier-Grade Alarms .............................................................................163

5.10.2 Performance Monitoring ........................................................................................165

5.10.2.1 Viewing Trunk Utilization ........................................................................165

5.10.2.2 Viewing MOS per Media Realm .............................................................166

5.10.3 VoIP Status ............................................................................................................168

5.10.3.1 Viewing Trunk and Channel Status ........................................................168

5.10.3.2 Viewing NFAS Groups and D-Channel Status .......................................169

5.10.3.3 Active IP Interfaces ................................................................................170

5.10.3.4 Performance Statistics ...........................................................................171

5.10.3.5 Timing Module Information .....................................................................171

5.10.4 Components Status ...............................................................................................172

5.11 Device High Availability Mode ............................................................................ 173

6 Troubleshooting .............................................................................................. 175

6.1 TP-6310 Self-Test .............................................................................................. 175

6.2 TP-8410 Self-Test .............................................................................................. 176

7 Technical Specifications ................................................................................ 177

7.1 Mediant 3000 with TP-6310/TP-8410 Technical Specification ............................ 177

8 List of Abbreviations ....................................................................................... 183

9 Index ................................................................................................................. 187

Version 6.6 5 Mediant 3000 with TP-6310 & TP-8410

Page 6

Mediant 3000 with TP-6310 & TP-8410

This page is intentionally left blank.

User's Manual 6 Document #: LTRT-95211

Page 7

User's Manual Notices

as software files can be viewed by registered customers at



Notice

This document describes the Au dioCod es Med iant 30 00 MGCP & MEG ACO m edia gate way, housed with TP-8410 SIP blade(s) or TP-6310 blade(s).

Information contained in t his document is believed to be ac curate and reliable at the tim e of printing. However, du e to ongoing product im provements and revis ions, AudioCodes canno t guarantee accuracy of printed material after the Date Published nor can it accept responsibility for error s or omissions. U pdates to this d ocum ent and other docum ents as well

http://www.audiocodes.com/downloads.

This document is subject to change without notice.

Date Published: December 13, 2015

Trademarks

AudioCodes, AC, HD VoIP, HD VoIP Soun ds Better , I Pmedia, Mediant, MediaPack , What’s Inside Matters, OSN, SmartTAP, VMAS, VoIPerfect, VoIPerfectHD, Your Gateway To VoIP, 3GX, VocaNOM and CloudBond 365 are trademarks or registered trademarks of AudioCodes Limited All other products or trademarks are property of their respective owners. Product specifications are subject to change without notic e.

WEEE EU Directive

Pursuant to the W EEE EU Directive, electronic and el ectrical waste must not be disposed of with unsorted waste. Please contact your local recycling authority for disposal of this product.

Customer Support

Customer technical s upport and s ervices are provided by Au dioCodes or b y an authori zed AudioCodes Service Partner. For more information on how to buy technical support for AudioCodes products and for contact information, please visit our Web site at www.audiocodes.com/support.

Documentation Feedback

AudioCodes continually strives to produce high quality documentation. If you have any comments (suggestions or errors) regarding this document, please fill out the mentation Feedback form on our Web site at http://www.audiocodes.com/downloads

User's Manual 8 Document #: LTRT-95211

Page 9

User's Manual 1. Introduction



1 Introduction

The Mediant 3000 is a VoIP gateway, offering integrated voice gateway functionality capable of delivering 2016 simultaneous calls, the Mediant 3000 supports all necessary functions for voice and fax streaming over IP networks.

Supporting up to 2016 voice channels with up to 63 E1 / 84 T1 trunks and with variou s PSTN interfaces, the Mediant 3000 addresses mid-density applications deployed in IP networks. The Mediant 3000 supports a wide variety of VoIP and cellular vocoders, standards-compliant signaling and call control.

There are two types of VoP communication blades supported by the Mediant 3000:

Based on TP-6310 blades - The Mediant 3000 with TP-6310 blades incorporates 1+1

Protected OC-3/STM-1 PSTN or three T3 PSTN telephony interfaces, either directly to the PSTN or to an enterprise PBX.

Based on TP-8410 blades – The Mediant 3000 with TP-8410 blades incorporates up

to 63 E1 or 84 T1 PSTN interfaces and it also allows the user to have different and dedicated physical Ethernet ports for each network type (Media, OAMP and Control).

The Mediant 3000 supports a broad selection of voice processing related algorithms, including:

G.711, G.723.1, G.729A and multiple UMTS, GSM and CDMA Vocoders G.168-2000 compliant echo cancellation T.38 real-time Fax over IP A wide selection of In-band and Out-of-band tone detection and generation Signaling protocol support including ISDN PRI

The Mediant 3000 is available in the following operating modes:

Simplex Mode (one VoP communication blade and one SA/M3K Synchronization and

Alarm blade). In this mode there is an optional integrated CPU (iCPU) for 3rd party applications.

High Availability 1+1 Mode (two VoP communication blades, two RTM and two

SA/M3K Synchronization and Alarm blades - one is active and the other is in standby mode).

For High Availabilit y, the Mediant 3000's har dware design cont ains redundant m odules for every part in the system, including redundant network connectivity, comprehensive switchover processing and backup data storage and access, as well as applicable loadsharing schemes.

To achieve high-availability, the software itself resides on redundant components and monitors system components to detect a hardware failure, as well as handling the switchover procedures to overcome a possible failure. In addition, components are hotswappable so that they can be replaced while the system is fully operational with no disruption to service.

The Mediant 3000 contains:

Up to two VoP communication blades RTM (Rear Transition Module) blades: In a Simplex configuration, up to two RTM blades for a TP-8410 based system, or a

single RTM for a TP-6310 based system.

In 1+1 system configuration, two RTM blades. Up to two SA/M3K S ync hro ni zat ion and Alarm blades Two Po wer Entr y Modu les ( PEM/D C/3 K) Two Power Supplies (PS/DC/3K)

Version 6.6 9 Mediant 3000 with TP-6310 & TP-8410

Page 10

Mediant 3000 with TP-6310 & TP-8410

These components function in either an Active / Standby redundant or load-sharing configuration to prov id e f ul l cont inuo us per f ormance coverage an d are id ea l b ui ld ing bl oc k s for deploying high-density, high availability Voice over Packet systems.

For more details on the High Availability 1+1 system, refer to 'The High Availability 1+1 System' on page 13.

User's Manual 10 Document #: LTRT-95211

Page 11

User's Manual 1. Introduction



1.1 General Features

The Mediant 3000 has the following features:

Up to 2016 voice/ f ax/ data independent multiple LBR channels PSTN interfaces:

• Up to 63 E1 / 84 T1 interfaces (with TP-8410)

• 1 + 1 Protected STM-1/OC-3 interface (with TP-6310)

• Three T3 interfaces (with TP-6310)

Packet interface:

• Dual GbE link ports (for redundancy)

• Four Fast links for multiple IP configurations (with TP-8410)

VoP and Voice Processing capabilities:

• Superior, high quality VoIP calls and FoIP transmissions

• Packet telephony standard compliant

• Vocoder configuration options include:

♦ AMR, AMR WB, EVRC, EVRC-B, G.711 A/u-law PCM, G.722, G.723.1,

G.726 ADPCM, G.727 ADPCM, G.729 A B, G.729.1 (up to 12 kbps), G.729.1 (up to 32 kbps), G.729E, GSM-EFR, GSM-FR, iLBC, MS GSM & EG.711

• Independent vocoder selection per channel

• VoIP packet streaming (RTP/ RTCP) per RFC 3550/2551

• RTP stream multiple destination connection

• IP to IP Mediation capabilities

• IP to IP Transcoding (G.711 to and from LBR, to GSM Vocoders, to UMTS

vocoders and to CDMA vocoders)

• Real-time Fax over IP/T.38 with superior performance (round trip delay of up to 9

sec)

• Automatic Fax Bypass modes

• DTMF Detection and Generation according to TIA 464B

• DTMF Relay according RFC 2833

• Tone detection and generation (MF, DTMF, RFC 2833)

• Extensive media processing functions

• G.168-2000 compliant Echo Cancelation with a 32, 64 or 128 msec tail

• Silence Suppression supporting VAD (Voice Activity Detection) and CNG

(Comfort Noise Generation)

“TDM- Switching” – for transferring TDM streams between timeslots Call Control and Signaling support:

• Call Control: MGCP (RFC 3435), MEGACO (H.248) standard control protocols

• PSTN Signaling: CAS, ISDN, PRI, (and V5 for TP-8410)

• MF-R1, MFC-R2 and Call Progress Tone detection and generation

Version 6.6 11 Mediant 3000 with TP-6310 & TP-8410

Page 12

Mediant 3000 with TP-6310 & TP-8410



Management Interfaces:

• SNMPv2, Web interface, EMS (Optional), SNMPv3

Mediant 3000 Platform capabilities:

• Flexible deployment and multiple density options

• Redundant Active / Standby configuration

• Load-sharing power supply configuration with separate power sources

• Carrier Grade Alarm System

• NEBS Level 3 compliant

User's Manual 12 Document #: LTRT-95211

Page 13

User's Manual 1. Introduction



RTM With Full

Interfaces

6310 Active

Blade

SA Active

Card

6310

Redundant

Blade

Redundant

Card

Slot1 Slot2 Slot3 Slot4

Internal Network Connection

Rear

Side

Lower

Side

Front

Side

Upper

Side

2xGbEDS3/SDH

RTM With

Ethernet

Interfaces

2xGbE

1.2 High Availability

The High Availability architecture of the Mediant 3000 provides the following functionality:

Redundant Active / Standby configuration Support for both TP-6310 & TP-8410 blades One or many global System IP addresses Private IP address for each blade for maintenance and fallback. Upgrading software without disrupting current calls (Hitless Software Upgrade)

1.2.1 Mediant 3000 HA System with TP-6310

The system includes t wo TP-6310 blades. One of the blades is the act ive (working) blade and the other blade is the redundant (standb y) blade.

The figure below illustrates the general architecture of the Mediant 3000 with 1+1 High Availability.

Figure 1: Mediant 3000 with TP-6310 System HA 1+1 Architecture

If both TP-6310 blad es are installed at the time the system is powered up, the TP-6310 blade in Slot 1 always initi ally assumes the Active functionalit y and the TP-6310 blade in Slot 3 always initia lly assumes the Redundant f unctionality. If only one blad e is installed, (no matter which slot it is occ upying) it al ways ass um es the Activ e funct ionalit y. If at a lat er time, a second TP-6310 blade is added, this second TP-6310 blade assumes the redundant functionality.

There is one internal Ethernet link between the Active and Redundant blades, which is used for the management of the high availability feature. This link is automatically and internally configured and is used by both of the blades.

Slots 2 and 4 in the front are occupied with the SA/M3K blades. One SA/M3K blade assumes the Active f unctionality, while the other SA/M3K blade assumes the Redundant functionality, according to each blade state.

On the rear of the chas sis, a RTM-6310 is located i n slot num ber 2. Its PSTN connections and GbE interface are always con nected to the Ac tive TP-6310 bla de in the f ront in slot 1. The RTM-6310/Redund ant is located in slot 3 and su pplies the GbE interfac es to the TP6310 blade in the front in slot 3.

Version 6.6 13 Mediant 3000 with TP-6310 & TP-8410

Page 14

Mediant 3000 with TP-6310 & TP-8410

Rear

Side

Lower

Side

Front

Side

8410/RTM

Trunks 1-42

8410/RTM

Trunks 43-84

TP-8410

Blade

Default:

Active

Slot 1 Slot 2 Slot 3 Slot 4

Active Segment

Upper

Side

1+1 GBE

42 E1/T1

PSTN

SA/3K

Blade

Default:

Active

TP-8410

Blade

Default:

StandBy

SA/3K

Blade

Default:

StandBy

1+1 GBE

42 E1/T1

PSTN

Redundant Segment

PEM-3

Port A

PEM-3

Port B

PS-3

Power

Supply

PS-3

Power Supply

48VDC

Source A

48VDC

Source B

Power Supplies

Shared Bus

2 Main

FE Links

BITS/ SETS

Contact

Closures

2 StandBy

FE Links

BITS/ SETS

Contact

Closures

Used by

the Active

TP-8410

Used by

the Active

TP-8410

Two GbE links can b e connected to each blad e through eac h RTM-63 10. At leas t one link per blade must be connected, but two are recommended for LAN redundancy. After system initialization is complete, network access is available only to the Active blade. The Redundant GbE links have no network access.

1.2.2 Mediant 3000 HA System with TP-8410

The HA (High Availability) system includes two TP-8410 blades, two RTM-8410s (Rear Transition Modules) and two SA/M3K Synchronization and Alarm blades

One of each of the blades is the active (working) blade and the other blade is the redundant (standby) blade, as illustrated below:

Figure 2: Mediant 3000 with TP-8410 System HA 1+1 Architecture

If both TP-8410 blad es are installed at the time the s ys tem is powered up, the TP-8410 blade in Slot 1 alwa ys initially provides the Active function ality and the TP-8410 blade in Slot 3 always initiall y provides the Redundan t functionality. If only one blade is insta lled, (no matter which slot it is o ccupying) i t alwa ys provides the Active f unction ality. If at a later

User's Manual 14 Document #: LTRT-95211

Page 15

User's Manual 1. Introduction

time, a second TP-8410 blade is added, this second TP-8410 blade provides the redundant functionality.

There is one interna l Ether net (ET H) link bet ween the Acti ve and Redund ant bl ades , which is used for the m anagement of the High Ava ilability feature. This link is automaticall y and internally configured and is used by both of the blades.

Slots 2 and 4 in the front are occupied with the SA/M3K blades. One SA/M3K blade provides the Active functionality, while the other SA/M3K blade provides the Redundant functionality, according to each blade's state.

On the rear of the chas sis, an RTM-8410 is located in slot # 2. This RTM is connec ted to trunks 1-42. Its PSTN connec tions and ETH interface are always connect ed to the Active TP-8410 blade in the front in slot # 1. The second RTM-8410 is located in slot # 4. This 2nd RTM is connected to tru nks 43-84. Trunks c onnec ted t o this RT M ar e direc te d to t he Ac t iv e blade. ETH interfaces are directed to the TP-8410 blade in the front in slot # 3.

Two GbE links can be connec ted to each bl ade through eac h RTM-8410. At least one link per blade must be connected, but two are recommended for LAN redundancy. After system initialization is complete, network access is available only to the Acti ve blade. The Redundant GbE links have no network access.

Each blade has its own local IP address (ac quired via BootP/D HCP) used for loading t he software by TFTP. In or der for the system to be set to HA, the s ystem address must be configured via the interface table.

1.2.3 Private IP Address and Sy stem (Global) IP Add ress(es)

Each blade on HA systems, has a single Private (Local) IP address and one or more System (Global) IP Addresses.

Please refer to 'Ass igning the Dev ice IP Address ' on page 21 to configure th e Private and System IP Addresses.

1.2.3.1 Private (Local) IP Address

This is a single IP address ( and subnet) per blade that is acquired via BootP/D HCP and used for loading the software by TFTP.

1.2.3.2 System (Global) IP Address

The Global IP address(es) of the HA system are the IP Address(es) that ar e used by the Active blade for Media, O AMP and Contr ol. These IP Addr ess(es) are c onfigured us ing an interface table.

Note: In HA s ystems, the local IP ad dresses (one of each bla de) are rare ly used (on ly

when a major failure occurs). It is necessary to configure these addresses to be valid IP addresses on the net work with full access to the Syslog server, s o in case of a m ajor failure, the blades will be able to report to the Syslog server. Moreover, it is recommended that th ese private IP addresses will be on same subnet as the OAM P system IP address.

Version 6.6 15 Mediant 3000 with TP-6310 & TP-8410

Page 16

Mediant 3000 with TP-6310 & TP-8410

SDRAM

Flash

Time Slot

Assigner

H.110 Bus

Interface

PCM Highway

Framers

MPC8260 Parallel Bus

Copper

Network

Processor

PCI Bus

Utopia

Bridge

STM-1 / OC-3

Transceiver

SDRAM

SRAM

Utopia Bus

PCM Highway

H.110 TSI

Up to

21 AC491

DSPs on

Module

HPI

0 to 8

AC491

DSPs on

Baseboard

CPU

Controller

MPC8280

H.100 Bus

MPC8260 Parallel Bus

Ethernet

Phy

Fiber Optic

2x Copper OR

2 x Fiber Optic

RJ-45 Copper

10/100/1000

or Optical GbE

1.3 Functional Block Diagram - TP-6310

The figure below illustrates the functionality of the blade.

Figure 3: 6310 Functional Block Diagram

User's Manual 16 Document #: LTRT-95211

Page 17

User's Manual 1. Introduction

SDRAM

Flash

Time Slot

Assigner

PCM Highway

Framers

MPC8260

Parallel

Bus

PSTN

Network

Processor

C-5e

PCI Bus

Utopia Bridge

SDRAM

SRAM

Utopia Bus

PCM Highway

Up to

21 AC 491

DSPs on

Module

HPI

1 to 4

AC491

DSPs on

Baseboard

CPU Controller MPC8280

MPC8260

Parallel

Bus

Ethernet

Switch

RJ-45 Copper

10/100/ 1000

or Optical GbE

Storage Unit

RJ-45 Copper

10/100

RJ-45 Copper

10/100

H.110

Bus

H.110

2 x Copper OR 2 x Fiber Optic

4 x 10/100 Base Tx

1.4 Functional Block Diagram - TP-8410

The figure below illustrates the functionality of the blade.

Figure 4: TP-8410 Functional Block Diagram

Version 6.6 17 Mediant 3000 with TP-6310 & TP-8410

Page 18

Mediant 3000 with TP-6310 & TP-8410

This page is intentionally left blank.

User's Manual 18 Document #: LTRT-95211

Page 19

User's Manual 2. Software Package



2 Software Package

After installing and powering up the device, you are ready to install the utilities that are included in the software package. This software package must be installed on the host PC/machine to be used to manage the d evice. The sof tware package can b e downloaded by registered users from the AudioCodes Web site at 'www.audiocodes.com/support'.

To become a registered user, follow the instructions on the Web site.

 To get started:

1. To install the software package refer to 'Installing the Software Package' on page 19.

2. Check the software package contents (refer to ''Software Directory Contents &

Structure'' on page 20.)

2.1 Installing the Software Package

3. Perform ''Getting Started'' on page 21.

The software package is available on the AudioCodes' FTP Web site.

Customers using a Windows™ operating system may choose to install the package

via the installation wizard, or choose to unzip the software package from the supplied zip file (refer to "Installing/Unzipping When Using a Windows™ Operating System" below).

2.1.1 Installing/Unzipping When Using a Windows™ Operating System

 To install the package:

1. Double-click on the setup.exe executable file.

2. Follow on-page instructions.

 To unzip when using a Windows™ Operating System:

1. Using a tool like WinZip™, open the zip file.

2. Click the ‘Extract’ button; the ‘Extract’ page opens.

3. Nav igate to the directory that you require to b e the root directory for the installation

and click the ‘Extract’ button; the files are extracted to the location you specified.

Version 6.6 19 Mediant 3000 with TP-6310 & TP-8410

Page 20

Mediant 3000 with TP-6310 & TP-8410

2.2 Software Directory Contents & Structure

Software Package Contents

Contents Directory Description

Auxiliary Files .\Auxiliary_Files\MIB_Files Various MIB files, e.g., SNMP MIB files: ACL.my,

RTP.my, ds1.my, MIB_2.m y, V2_MI B. my.

.\Auxiliary_Files\Sample_ Call_Progress_Files

.\Auxiliary_Files\Sample_

Contains examples of Call Progress Tones configuration files.

Contains examples of CAS protocol files.

CAS_Protocol_Files .\Auxiliary_Files\Sample_

Ini_Files

Contains examples of configuration (ini) files. Users can utilize these sample files as a baseline

for creating customized configuration files.

Firmware .\Firmware Contains cmp files, loaded to the device when

changing the version of the software. When the device is supplied to customers, it is already configured with pre-installed firmware.

Utilities AudioCodes’ utilities pro vid e you with us er-friendly interfaces that enhance

device usability and smooth your transition to the new VoIP infrastructure. .\Utilities\DConvert Contains the TrunkPack Downloadable

Construction Utilit y. Use the utilit y to build Call Progress Tones, Voice Prompts, and CAS files.

.\Utilities\PSTN_TRACE_ UTILITY

.\Utilities\Wireshark Plugins

This utility is designed to convert Wireshark log files containing the PSTN trace to text format.

Contains the plugins for the Wireshark network diagnostic tool. The plugin registers itself to handle a dissection of AudioCodes' proprietary protocol.

Documentation All relevant product documentation

Note: All the demo programs described above are for reference only. Flawless

operation and stability of these applications cannot be guaranteed.

User's Manual 20 Document #: LTRT-95211

Page 21

User's Manual 3. Getting Started



3 Getting Started

The Mediant 3000 is supp li ed with app lic at io n sof t ware alr e ady resident in its flas h memory

3.1 Assigning the Device IP Address

(with factory default parameters). The Mediant 3000 is also supplied with a Web interface. For detailed inform ation on how to fully configure the gateway refer to 'Device Ini tialization

& Configuration Files' on page 25 and 'Configuration Using the Web Interface' on page 43. The Mediant 3000 HA c an be c onf ig ured vi a EM S (r ef er to LT RT-9480x EMS Conf igur ati on

Guide) or the Web interface (refer to 'Configuration Using the Web Interface' on page 43).

To assign an IP address to the Mediant 3000 use one of the following methods:

HTTP using a Web browser (refer to ''Assigning an IP Address Using HTTP'' on page

21).

BootP (refer to ''Assigning an IP Address Using BootP'' on page 22). DHCP (refer to 'Using BootP/DHCP').

The default device IP Addresses are shown below. Default Networking Parameters

Default IP address: 10.1.10.10 Default subnet mask is 255.255.0.0 Default gateway IP address is 0.0.0.0

3.1.1 Assigning an IP Address Using HTTP

 To assign an IP address using HTTP:

1. Connect your PC to the device. Either connec t the network interfac e on your PC to a

port on a network hub / switch (using an RJ-45 Ethernet c able), or use an Ethernet cross-over cable to directly connect the network interface on your PC to the RJ-45 jack on the device.

2. Chan ge your PC’s IP addres s and subnet m ask to corr espond with the d evice fac tory

default IP address and subnet mask, shown in the table above. For details on changing the IP address and subnet mask of your PC, refer to Windows™ Online Help (Start>Help and Support).

3. Acc es s the Web interface (refer to the W eb interface chapter in the Product Ref er enc e

Manual).

4. Click Reset and click OK in the prompt. The device applies the cha nges and res tarts.

This takes approximately 1 minute to complete. When the device has finished restarting, the Ready and LAN LEDs on the front view are lit green.

Tip: Record and retain th e IP address and subnet mask you assign the device.

Do the same when definin g a new username or password. If the Web interface is unavailable (for example, if you’ve lost your username and password), use a BootP/TFTP configuration utility to access the device, “reflash” the load and reset the password.

5. Disconnect your PC from the device or from the hub / switch (depending on the

connection method you used in step 1 above).

Version 6.6 21 Mediant 3000 with TP-6310 & TP-8410

Page 22

Mediant 3000 with TP-6310 & TP-8410

6. Reconnect the device and your PC (if necessary) to the LAN.

7. Restore your PC’s IP address & subnet mask to what they originally were. If

necessary, restart your PC and re-access the device via the Web interface with its new assigned IP address.

3.1.2 Assigning an IP Address Using BootP

Notes:

• The BootP procedure should be performed using any standard c ompatible BootP

server.

• For Mediant 3000 HA, in order to get the BootP reset request from the blade,

perform a double reset on the system, as described in 'Private IP Address and System (Global) IP Address' on page 15.

Tip: You can also use BootP to load the auxiliary files to the device (refer to

'Using BootP/DHCP').

 To assign an IP address using BootP:

1. Obtain and install a BootP server application on your PC.

2. Add the client configuration for the device.

3. Res et the g atew ay ph ysicall y causing it to us e Boot P. T he devic e changes its networ k

parameters to the values provided by BootP.

User's Manual 22 Document #: LTRT-95211

Page 23

User's Manual 3. Getting Started

3.2 Assigning the IP Addresses for High Availability Mode

The private IP addr ess is assigned to the Active and Redundant blades (for m aintenance) by using the BootP/DHCP.

 To assign Private IP addresses to the Mediant 3000 blades:

1. Start your BootP/DHCP Server application.

2. Add a client configuration f or the Mediant 3000 that you wish to initialize and ins ert a

local (private) IP address for each of the two Mediant 3000 blades.

Note: Do not load a cm p or an ini file usin g a BootP/DHC P Server appl ication.

This action will erase the previous configuration that was stored to the flash memory of the Mediant 3000 device.

3. Power down the Mediant 3000.

4. Power up the Mediant 3000 system for 30 seconds.

5. Power down the Mediant 3000.

6. Power up the Mediant 3000 system within 15 seconds.

7. Us ing a BootP/DHCP S erver app lication, verif y that both bla des in Sl ots 1 and 3 have

received their local IP addresses.

Note: A repeat power down and power up cycle, as described above, is necessary. By default the redundant and active blades are set to load the IP addresses from the flash memory and do not automatically send a BootP request.

 To assign an IP address via the CLI:

In the event that a BootP or DHCP server is not available in the network, the following method can be used to assign local (private) IP addresses to the Mediant 3000 blades.

1. Connect the blade’s RS-232 port to either COM1 or COM2 communication port on

your PC using the serial cable supplied with the Mediant 3000.

2. Use a serial communication application (e.g., HyperTerminalTM) with the following

communications port settings:

• Baud Rate: 115,200 bps

• Data Bits: 8

• Parity: None

• Stop Bits: 1

• Flow Control: None

3. The CLI prompt appears.

4. At the prompt, type conf, and then press <Enter>; the configuration folder is

accessed.

5. Type scp ip <new private ip address> <netmask> <default gw>

(‘scp’ command stands for SetConfigParam) and then press <Enter>.

Version 6.6 23 Mediant 3000 with TP-6310 & TP-8410

Page 24

Mediant 3000 with TP-6310 & TP-8410

6. T he new ip address is immediately being used (unles s the blade is the active blade

and it already uses the network IF table – global addresses).

7. Type sar.

(save and reset) for saving and restarting with configured address.

Note: The gcp ip comm and can be used to see a cur rent configured private

address.

This private address are used for maintenance purposes and also used as a fallback in case of major system problem which prevents the system from working in HA mode.

In order for the s ystem to be set to HA, the s ystem's IP address(es ) must be configured. The configured system address configuration is per f ormed via the Interface Table us ing th e EMS (Refer to LTRT-9480x EMS Configuration Guide) or Web interface (refer to Network on page 91). The configured system addresses should differ from private addresses. Managing the system is done by connecting to the Active blade private address (the Redundant blade management is blocked). If you don’t know which of the two private addresses belongs to the active blade, try both. Only one will answer to the EMS/Web connection attempt.

Note: HA will not be enabled until the system address has been configured.

User's Manual 24 Document #: LTRT-95211

Page 25

User's Manual 4. System Initialization Process



4 System Initialization P rocess

This section describes the Initialization Procedures and Configuration Options for the Mediant 3000 System. It includes:

Startup Process (see below) Configuration Parameters and Files (refer to 'Configuration Parameters and Files' on

28)

page

BootP/DHCP (refer to Using BootP/DHCP) Software Upgrade

4.1 Boot Firmware & Operational Firmware

High Availability Aspects

The device runs two distinct software programs: Boot firmware and operational firmware.

Boot firmware - Boot firmware (also known as flash software) resides in the device's

non-volatile memory. When the device is reset, Boot firmware is initialized and the operational software is loaded into the SDRAM from a TFTP server or integral nonvolatile memory. Boot firmware is also responsible for obtaining the device's IP parameters and ini file name (used to obtain the device's configuration parameters) via integral BootP or DHCP clients. The Boot firmware version can be viewed on the Web Interface. The last step the Boot firmware performs is to invoke the operational firmware.

cmp Operational firmware file - The device is supplied with a cmp file pre-installed on

its flash memory. Therefore, this file is not included on the supplied CD. However, if you are an AudioCodes registered customer, you can obtain the latest cmp version files (as well as documentation and other software listed in the table above) from AudioCodes Web site at 'www.audiocodes.com/support' (customer registration is performed online at this Web site). If you are not a direct customer of AudioCodes, please contact the AudioCodes' Distributor and Reseller from whom this product was purchased.

For more information on BootP/DHCP, refer to the Product Reference Manual.

Note: The ini, MIB and Utility files are available on the CD supplied with the device.

Version 6.6 25 Mediant 3000 with TP-6310 & TP-8410

Page 26

Mediant 3000 with TP-6310 & TP-8410

Download firmware via

TFTP

BootP/DHCP

reply contains ini file

name?

Download

configuration

files via TFTP

Run operational

software

Reset command from Web interface,

or SNMP

Response to

BootP x times

Response to

DHCP x times

BootP

Response

Update network

parameters from

BootP/DHCP reply

DHCP

Response

Yes

BootP/DHCP

reply contains

Firmware

file name?

Yes

Reset board via Power Reset

Is device in HA

Mode?

Yes

4.2 Startup Process

For more information on BootP/DHCP, refer to the Product Ref erenc e Man ua l.

Figure 5: Startup Process Diagram

User's Manual 26 Document #: LTRT-95211

Page 27

User's Manual 4. System Initialization Proces s

Notes:

• The default time duration between BootP/DHCP requests is set to 1 second.

This can be changed by the BootPDelay ini file parameter. Also, the default number of requests is 3 and can be changed by the BootPRetries ini file parameter. Both parameters can also be set using the Command Line Switches in the BootP reply packet.

• The ini file configuration parameters are stored in non-volatile memory after

the file is loaded. When a parameter is missing from the ini file, a default value is assigned to this parameter and stored in non-volatile memory (thereby overriding any previous value set for that parameter). Refer to Using BootP/DHCP below.

Version 6.6 27 Mediant 3000 with TP-6310 & TP-8410

Page 28

Mediant 3000 with TP-6310 & TP-8410



4.3 Configuration Parameters and Files

The device's configuration is stored in two file groups.

The Initialization file - an initialization (ini) text file containing configuration parameters

of the device.

The Auxiliary files - dat files containing the raw data used for various tasks such as

Call Progress Tones, Voice Prompts, logo image, etc.

These files contain factory-pre-configured parameter defaults when supplied with the device and are store d i n th e de vice's non-volatile mem ory. T he de vice is s tar te d up in it ially with this default configuration. Subsequently, these files can be modified and reloaded using either of the following methods:

BootP/TFTP during the startup process (refer to 'Using BootP/DHCP'). Web Interface (refer to 'Configuration Using the Web Interface' on page 43). Automatic Update facility (refer to 'Automatic Update Facility' on page 34).

The modified auxiliar y files are burned into the n on-volatile memory so that the modif ied configuration is utilized with subsequent resets. T he configuration file is al ways stored on the non-volatile memory. There is no need to repeatedly reload the modified files after reset.

Notes:

• Users who configure the device with the Web interface do not require ini files

to be downloaded and have no need to utilize a TFTP server.

• SNMP users configure the device via SNMP. Therefore a very small ini file is

required which contains the IP address for the SNMP traps.

4.3.1 Initialization (ini) File

The ini file name must not include hyphens or spaces. Use underscores instead. The ini file can contain a num ber of par ameters . The ini file st ructure s uppor ts the f ollowing

parameter value constructs:

Parameter = Value (refer to 'Parameter = Value Constructs'). The lists of parameters

are provided in the ini File Parameters chapter of the Product Reference Manual.

Tables of Parameter Value (refer to ''Table of Parameter Value Constructs'' on page

31).

The example below shows a sample of the general structure of the ini file for both the Parameter = Value and Tables of Parameter Value Constructs.

[Sub Section Name] Parameter_Name = Parameter_Value Parameter_Name = Parameter_Value . ..

; REMARK

[Sub Section Name] ...

User's Manual 28 Document #: LTRT-95211

Page 29

User's Manual 4. System Initialization Process



; Tables Format Rules: [Table_Name] ; Fields declaration Format Index_Name_1 ... Index_Name_N = Param_Name_1 ...

Param_Name_M ; Table's Lines (repeat for each line) Table_Name Index_1_val ... Index_N_val = Param_Val_1 ...

Param_Val_M [\Table_Name]

4.3.1.1 Paramet er Val ue St r uct u re

The following are the rules in the ini File structure for individual ini file parameters (Parameter = Value):

Lines beginning with a semi-colon ';' (as the first character) are ignored. A carriage-return/line-feed must be the final character of each line. The number of spaces before and after "=" is not relevant. If there is a syntax error in the parameter name, the value is ignored. Syntax errors in the parameter value field can cause unexpected errors (because

parameters may be set to the incorrect values).

Sub-section names are optional. String parameters, representing file names, for example,

CallProgressTonesFileName, must be placed between two inverted commas ('…').

The parameter name is NOT case sensitive; the parameter value is usually case

sensitive.

Numeric parameter values should be entered only in decimal format. The ini file should be ended with one or more empty lines.

ini File Examples

The example below shows a sample ini file for MGCP.

[TDM BUS configuration] ; 1=aLaw 3=ulaw PCMLawSelect = 1 BaseUDPPort = 4000 [Trunk Configuration] ;E1_trans_31 ProtocolType = 5 ; USER_TERMINATION_SIDE TerminationSide = 0 ; EXTENDED_SUPER_FRAME FramingMethod = 0 ;HDB3 LineCode = 2 [MGCP] EndpointName = 'ACgw' CallAgentIP = 10.1.2.34 [Channel Params] DJBufferMinDelay = 75 RTPRedundancyDepth = 1

Version 6.6 29 Mediant 3000 with TP-6310 & TP-8410

Page 30

Mediant 3000 with TP-6310 & TP-8410

[Files] CallProgressTonesFilename = 'CPUSA.dat' VoicePromptsFilename = 'tpdemo_723.dat' CasFilename = 'E_M_WinkTable.dat'

The example below shows a sample ini file for MEGACO. [MEGACO]

; List of Call agents, separated by ','. ; The default is the loading computer. PROVISIONEDCALLAGENTS = 10.2.1.254 ; List of ports for the above Call Agents, separated by ','. The

default is 2944. PROVISIONEDCALLAGENTSPORTS = 2944

; The next 2 fields are the termination names patterns. ; The first is the pattern for the physical termination, and the ; second is the pattern for the RTP termination. The '*' stands

for ; a number. PHYSTERMNAMEPATTERN = gws*c* LOGICALRTPTERMPATTERN = gwRTP/* ; This parameter activates MEGACO. If omitted, MGCP will be active MGCONTROLPROTOCOLTYPE = 2

; The following disables the keep-alive mechanism if set to 0, ; else it is enabled. Note that the recommended KeepAlive method

is ; the use of the inactivity timer package - 'it'. KEEPALIVEENABLED = 1 ; ; This parameter defines the profile used, and it is a bitmask MGCPCOMPATIBILITYPROFILE = 2

Note: Before loading an i ni file to the device, m ake sure that the ext ension of the ini

file saved on your PC is correc t: Verify that the c heckbox Hide ex tension f or known f ile types (My Computer>Tools >Folder Options>View) is unchec ked. Then, verify that the ini file name extension is xxx.ini and NOT erroneously xxx.ini.ini or xxx~.ini.

The lists of individual ini file parameters are provided in ini File Parameters.

User's Manual 30 Document #: LTRT-95211

Page 31

User's Manual 4. System Initialization Process



4.3.1.2 Tables of Parameter Value Structure

Tables group the r elated parameters of a given ent ity. Tables are composed of rows and columns. The colum ns represent parameters types, while each row represent s an entity. The parameters in e ach row are called the line attr ibutes. Rows in tables ma y represent (for example) a trunk, list of timers for a given application, etc.

For a list of supported t ables please refer to the ini File Table P arameters section in the Product Reference Manual.

4.3.1.2.1 Table Structure Rules

Tables are composed of four elements:

Table-Title - The Table's string name in square brackets. Format Line - This line specifies the table's fields by their string names. The first word MUST be "FORMAT" (in capital letters), followed by indices field

names, and after '=' sign, all data fields names should be listed.

• Items must be separated by ',' sign.

• The Format Line must end with ';' sign.

Version 6.6 31 Mediant 3000 with TP-6310 & TP-8410

Page 32

Mediant 3000 with TP-6310 & TP-8410



Data Line( s) - The actual values for parameters are specified in each Data line. The

values are interpreted according to the format line. The first word must be the table's string name.

• Items must be separated by a comma (',' sign).

• A Data line must end with a semicolon (';' sign).

• Indices (in both the Format line and the Data lines) must all appear in order, as

determined by the table's specific documentation. The Index field must NOT be omitted. Each row in a table must be unique. For this reason, each table defines one or more Index fields. The combination of the Index fields determines the 'linetag'. Each line-tag may appear only once. In the example provided in the table above, Table Structure Example', there is only one index field. This is the simplest way to mark rows.

• Data fields in the Format line may use a sub-set of all of the configurable fields in

a table only. In this case, all other fields are assigned with the pr e-defined default value for each configured line.

• The order of the Data fields in the Format line is not significant (unlike the Index-

fields). Field values in Data lines are interpreted according to the order specified in the Format line.

• Specifying '$$' in the Data line causes the pre-defined default value assigned to

the field for the given line.

• The order of Data lines is insignificant.

• Data lines must match the Format line, i.e. must contain exactly the same number

of Indices and Data fields and should be in exactly the same order.

• A line in a table is identified by its table-name and its indices. Each such line may

appear only once in the ini file.

End-of-Table-Mark: Marks the end of a table. Same as Table title, but the string name

is preceded by '\'. Below is an example of the table structure in an ini file.

; Table: Items Table. ; Fields: Item_Name, Item_Serial_Number, Item_Color, Item_weight. ; NOTE: Item_Color is not specified. It will be given default

value. [Items_Table] ; Fields declaration Format Item_Index = Item_Name, Item_Serial_Number, Item_weight; Items_Table 0 = Computer, 678678, 6; Items_Table 6 = Computer-page, 127979, 9; Items_Table 2 = Computer-pad, 111111, $$; [\Items_Table]

4.3.1.2.2 Tables in the Uploaded ini File

Tables are grouped according to the applications they configure. When uploading the i ni file, the polic y is to include only tab les that belong to ap plications,

which have been configured. (Dynamic tables of other applications are empty, but static tables are not.) The trigger for upload ing tables is further docum ented in the applications'

User's Manual 32 Document #: LTRT-95211

specific sectio ns.

Page 33

User's Manual 4. System Initialization Process

4.3.1.3 Binary Configuration File Download

The ini file contains sens itive inform ation require d for appropr iate func tioning of the de vice. The ini file is uplo ade d to th e de vic e or d o wnlo ade d f r om the gateway using T FTP or HTTP protocols. These protocols are unsecured (and thus vulnerable to a potential hacker). Conversely, if the ini file is encoded, the ini file would be significantly less vulnerable to

4.3.1.3.1 Encoding Mechanism

outside harm.

The ini file to be loaded and retrieved is available with or without encoding. When an encoded ini file is downloaded to the device, it is retrieved as encoded from the device. When a decoded file is downloaded to the device, it is retrieved as decoded from the device.

In order to create an encod ed in i f ile, t he user must first create an ini file an d the n app l y th e DConvert utility to it in order to encode it.

In order to decode an encoded ini f ile retrieved from the device, the us er must retrieve an encoded ini file from the device using the Web server (refer to "Downloading Auxiliary Files" below) and then use the DConvert utility in order to decode it.

(Refer to the Utilities chap ter in the Product Refer ence Manual for detailed ins tructions on ini file encoding and decoding.)

Downloading the in i f i le w it h or wit hout encoding ma y be per f ormed by utilizing either TFTP or HTTP.

4.3.2 Auxiliary F iles

The auxiliary files are *.dat files containing ra w data used for a certai n task such as Call Progress Tones, Voice Prompts, logo image, etc. The *.dat files are created using the DConvert utility (refer to the Utilities chapter in the Product Reference Manual), which converts auxiliary source files into dat files. Some sample auxiliary source files are available in the software pac kage under: .\Auxiliary_Files\.dat files. These *.dat files ar e downloaded to the device using TFTP (see below) or HTTP via the Software Upgrade Wizard (refer to 'Upgrading Device Software' on page 38.) This section describes the various types of auxiliary files.

Note: The auxiliary source files use the same ini file extension type as the ini

configuration file, how ever, the func tionalit y is different. Whenever the ter m, "ini fil e" is used, it refers to the configuration file and NOT to the auxiliary files.

Version 6.6 33 Mediant 3000 with TP-6310 & TP-8410

Page 34

Mediant 3000 with TP-6310 & TP-8410



4.3.2.1 Downloading Auxiliary Files via TFTP During the Blade Startup

Note: This is not applicable in HA mode.

Each auxiliary file has a corresponding ini file parameter in the form of [AuxiliaryFileType]FileName. This parameter takes the name of the auxiliary file to be downloaded to the device. I f the ini file does no t conta in a par am eter f or a specif ic auxiliar y file type, the device uses the last auxiliary file that was stored on the non-vol a tile memory.

The following list contains t he ini file param eters f or the differ ent types of auxiliar y files that can be downloaded to the device:

CoderTblFileName – The name (and path) of the file containing the coder table . This

file should be constructed using the “TrunkPack Conversion Utility” supplied as part of the software package on the CD accompanying the device.

VoicePromptsFileName - The name (and path) of the file containing the voice

prompts. This file should be constructed using the “TrunkPack Conversion Utility” supplied as part of the software package on the CD accompanying the device. The Voice Prompt buffer size in the blade is 10 Mbytes.

The Voice Prompt buffer size is also controlled by the software upgrade key. For more

information contact an AudioCodes representative.

CallProgressTonesFilename - The name (and path) of the file containing the Call

Progress and User-Defined Tones definition.

PrerecordedTonesFileName - The name (and path) of the file containing the

Prerecorded Tones. This file should be constructed using the "TrunkPack Conversion Utility" supplied as part of the software package on the CD accompanying the device.

DialPlanFileName - The name (and path) of the file containing dial-plan configuration

for CAS protocols. This file should be constructed using the "TrunkPack Conversion Utility" supplied as part of the software package on the CD accompanying the device.

CASFileName_0…CASFileName_7 (or CASFileName) - The names (and path

names) of the files containing the CAS protocol configuration. It is possible to use 1 to 8 files. The CASFileName name is still supported and can be used instead of the enumerated names when using only one CAS protocol file.

CASTablesNum - Indicates how many CAS protocol configuration files are loaded. Its

range is 1-8. It should match the number of "CASFileName_X" fields.

CASTableIndex_TrunkNum (TrunkNum should be an integer) - This field is a CAS

protocol file index. It indicates the CAS protocol file to use in a specific Trunk. The index value corresponds to the number in the field “CASFileName_X”.

4.3.3 Automatic Update Facility

The device is capable of automatically downloading updates to the ini file, auxiliary files and firmware image. An y standard W eb server, FTP server or NFS s erver ma y be used to host these files.

The Automatic Update processing is performed:

Upon device start-up (after the device is operational) At a configurable time of day, e.g., 18:00 (disabled by default) At fixed intervals, e.g., every 60 minutes (disabled by default) If Secure Startup is enabled (refer to Secure Startup), upon start-up but befor e the

User's Manual 34 Document #: LTRT-95211

Page 35

User's Manual 4. System Initialization Process



device is operational.

The Automatic Update process is entirel y controlled by conf iguration param eters in the ini file. During the Automatic Update process, the device contacts the external server and requests the latest version of a given set of URLs. An additional benefit of using HTTP (Web) servers is that c onf iguratio n ini fi les would be downlo aded o nl y if they wer e m odif ied since the last update.

The following is an example of an ini file activating the Automatic Update Facility.

# DNS is required for specifying domain names in URLs DnsPriServerIP = 10.1.1.11

# Load extra configuration ini file using HTTP INIFILEURL = 'http://webserver.corp.com/AudioCodes/inifile.ini' # Load call progress tones using HTTPS CPTFILEURL = 'https://10.31.2.17/usa_tones.dat' # Load voice prompts, using user "root" and password "wheel" VPFILEURL = 'ftps://root:wheel@ftpserver.corp.com/vp.dat'

# Update every day at 03:00 AM AutoUpdatePredefinedTime = '03:00'

Notes on Configuration URLs:

Additional URLs may be specified, as described in the System ini File Parameters in

the Product Reference Manual.

Updates to non-ini files are performed only once. To update a previously-loaded

binary file, you must update the ini file containing the URL for the file.

To provide differential configuration for each of the devices in a network, add the string

"<MAC>" to the URL. This mnemonic is replaced with the hardware (MAC) address of the device.

Version 6.6 35 Mediant 3000 with TP-6310 & TP-8410

Page 36

Mediant 3000 with TP-6310 & TP-8410



initializing the

To update the firmware image using the Automatic Update facility, use the

CMPFILEURL parameter to point to the image file. As a precaution (in order to protect the device from an accidental update), you must also set AUTOUPDATECMPFILE to

URLs may be as long as 255 characters.

Note: For the following p aram et ers, the URLs are res et to their def au lt value o n

successful Autoupdate. Subsequent Autoupdates without reparameters are not supported.

• CptFileUrl

• PrtFileUrl

• FXSCoeffFileUrl

• FXOCoeffFileUrl

• CasFileUrl

• DialPlanFileUrl

• TLSPkeyFileUrl

• TLSCertFileUrl

• TLSRootFileUrl

• WebLogoFileUrl

• V5PortConfigurationFileURL

 To utilize Automatic Updates for deploying the device with minimum manual

configuration:

1. Set up a Web server (in this example it is http://www.corp.com/) where all the

configuration files are to be stored.

2. O n each device, pr e-configure the following setting: (DHCP/DNS are assumed)

INIFILEURL = 'http://www.corp.com/master_configuration.ini'

Create a file named master_configuration.ini, with the following text:

# Common configuration for all devices # -----------------------------------CptFileURL = 'http://www.corp.com/call_progress.dat' # Check for updates every 60 minutes AutoUpdateFrequency = 60

# Additional configuration per device # ----------------------------------# Each device will load a file named after its MAC address, # e.g. config_00908F033512.ini IniFileTemplateURL = 'http://www.corp.com/config_<MAC>.ini'

# Reset the device after configuration has been updated. # The device will reset after all files were processed. RESETNOW = 1

User's Manual 36 Document #: LTRT-95211

Page 37

User's Manual 4. System Initialization Process

3. You c an modif y the master_conf iguration.ini fil e (or any of the config_ <MAC>. ini files )

at any time. The de vice queries for the latest vers ion every 60 minutes, and ap plies the new settings immediately.

4. For additional security, usage of HTT PS and FTPS protocols is recomm ended. The

device supports HTTPS (RFC 2818) and FTPS using the AUTH TLS method (RFC

4217) for the Automatic Update facility.

5. To download configuration files from an NFS server, the file system parameters

should be defined in the configuration ini file. The following is an example of a configuration ini file for downloading files from NFS servers using NFS version 2:

# Define NFS servers for Automatic Update [ NFSServers ] FORMAT NFSServers_Index = NFSServers_HostOrIP,

NFSServers_RootPath, NFSServers_NfsVersion; NFSServers 1 = 10.31.2.10, /usr/share, 2 ; NFSServers 2 = 192.168.100.7, /d/shared, 2 ; [ \NFSServers ]

CptFileUrl = 'file://10.31.2.10/usr/share/public/usa_tones.dat' VpFileUrl =

'file://192.168.100.7/d/shared/audiocodes/voiceprompt.dat'

If you implement the Automatic Update mechanism, the device must not be configured using the Web interf ace. If you configure p arameters in th e Web interf ace and save ( burn) the new settings to t he device's flash m emory, the In iFileURL param eter (definin g the URL to the ini file for Autom atic Updates) is automatically set to 0 (i.e., A utomatic Updates is disabled).

The Web interface provides a safeguard for the Automatic Update mechanism. If the IniFileURL parameter is defined with a URL value (i.e., Automatic Updates is enabled), then by default, the ' Burn To FLA SH' fie ld under th e Reset Co nfigurat ion group in the W eb interface's 'Maintenanc e Act ions' page is autom atic ally set to "No". T herefor e, this preve nts an unintended burn-to-flash when resetting the device.

However, if configuration settings in the Web Interface were burnt to flash, you can reinstate the Automatic Upda te mec hanism, b y loading to the dev ice, the ini fil e that includes the correct IniFileURL parameter setting, using the Web interface or BootP.

4.4 Backup Copies of ini and Auxiliary Files

Be sure to separate ly store a cop y of the ini file and all auxili ary files, as well as a note of

Version 6.6 37 Mediant 3000 with TP-6310 & TP-8410

the software version for use should a device require replacement.

Page 38

Mediant 3000 with TP-6310 & TP-8410

4.5 Upgrading Device Software

To upgrade the device's software (firmware), loa d the upgraded firm ware cmp file into the device (and optionally burn it into integral non-volatile memory) using:

1. Web interface - For a complete description of this option refer to Software Upgrade

Wizard.

2. Boot P/TFT P Server - Use the -fb BootP c ommand line switch. T he device downl oads

the specified firmware name via TFTP and also “burns” the firmware on the nonvolatile memory.

Note: Upgrading the device's f irmware requires reloading the ini f ile and re-burning

the configuration files. A S oftware Upgrade Key ma y be required (refer to 'Software Upgrade Wizard').

4.6 Software Upgrade Key

The Software Upgrade Key is a string stored in the device's non-volatile flash memory, defining the features and capabilities allowed by the specific license purchased by the customer. Customers specify the features and capabilities they require at the time they order the device. The device only allows users to utilize those features allowed by the integral Software Upgrade Ke y.

The device is supplied a lready pre-configured with a Sof tware Upgrade Key according to the customer's order. Us ers can verify which featur es are allowed by the licens e using the Web interface GUI. (Refer to ''Software Upgrade Key'' on page 148).

Note: The Software Upgrade Key is an encrypted key provided by AudioCodes only.

User's Manual 38 Document #: LTRT-95211

Page 39

User's Manual 4. System Initialization Process



4.7 High Availability

4.7.1 Initializing the Mediant 3000 System

For the system to be set up f or High Availabilit y, the following installati on phases must be carried out:

Hardware configuration setup as described in the Mediant 3000 and IPmedia 3000

SIP-MEGACO-MGCP Installation Manual. The system can be set up initially with only one blade and one SA/M3K blade, however, High Availability mode is only functional with a second blade and SA/M3K blade is added.

The feature key includes the high availability feature and is installed on both of the

blades. Refer to 'Software Upgrade Key - Web Server' on page Availability feature was specified at the time the system was purchased, then it is already included on both of the blades).

The Global IP Address is set using the Networking IF table blade parameter (burned

to flash or received by the ini file, or set by SNMP – in which case the blade must be re-booted for the change to take effect) in the active blade to a valid IP address that is different than the local IP address of the blades, but with the same subnet. Refer to 'Assigning the IP Addresses for High Availab il ity Mode' on page

System was loaded from flash (when loading from BootP/TFTP, on first configuration

setup the High Availability mode is disabled).

148. (If the High

23.

4.7.2 Device In itia liza tion Proc ess

Each blade is initialized as Active or Redundant according to its placement in the

chassis and the status of the SDH interface.

An Active blade is identified by a green light in ACT led on the blade front panel. Synchronization between active and redundant blades can take several minutes in

which the active blade forwards to the redundant blade, all its current configuration data, including files such as voice prompt, call progress tone and even its software (cmp file). If necessary, a second boot of the redundant blade is issued in order to apply the new configuration .

After the synchronization has ended, the redundant blade is identified by a blinking

yellow light in ACT led.

The redundant blade is disconnected from the external network and has an internal

connection with the active blade only. This means that the user does not interact directly with the redundant blade.

4.7.3 Special System Speci fic Behavior

4.7.3.1 Rebooting the Blade

Both blades are set to load from Flash, even after power-off /power-on reset. The system needs to load from BootP/TFTP in the following cases:

when the private IP addresses need to be set (at the first configuration or if they need

to be changed)

when the system cannot be loaded from Flash (bad configuration, etc.)

If the system needs to be loaded from BootP/TFTP, a double hard ware reset is needed. After the first reset, wait approx imately 20 seconds and then perform a second hardware reset.

Version 6.6 39 Mediant 3000 with TP-6310 & TP-8410

Page 40

Mediant 3000 with TP-6310 & TP-8410

4.7.3.2 High Availability and Syslog

All High Availabil ity main operations and events are printed to the Syslog with the prefix: "M3K_HA".

All S yslog mess ages and events of the redundant blade ar e printed to the Syslog by the active blade with the appropriate message prefix.

4.7.4 Actions upon Detecting Blade Failure

4.7.4.1 Failure in the Active Blade

In the event that an Active blade fails, the Redundant (Stan dby) blade issues a switch-over operation. As part of this switch-over operation, the failed blade is reset and the initially Redundant (Standb y) blade becom es the Active blade in Simplex mode, until a redundant blade is detected.

If the failure in the active blade is f ixed after reset, it is initialized as the redundant blad e and the Device system returns to High Availability mode.

4.7.4.2 Failure in the Redundant Blade

In the event that a Redundant bl ade fails, the Acti ve blade resets the redund ant blade and switches to Simplex mode until the redundant blade is returned to functional operation.

If the failure in the redundant blade is fixed after reset, it is initialized as the redundant blade again and the Device system returns to High Availability mode.

4.7.5 Hitless Software Upgrade

The Mediant 3000 HA system allows you to upgrade the sof tware (SW) ver sion (i.e., cmp file) running on the device, without disrupting current calls. This non-effecting traffic upgrade feature is referred to as Hitless Software Upgrade.

The Hitless Software Upgrade process is as follows: The user loads a new softwar e version file to the device using the EMS/W eb. The file is

received by the Active blade, which then forwards it to the Redundant blade. The Redundant blade 'bur ns' the file to its f lash memor y, and then resets (loadin g the new

software file saved in the flash memory). The Redundant blade perf orms a switchover from the Active blade (runni ng the previous

software version). This switc hover pr oc ess inc ludes tr anslat ion of all requ ir ed d ata bas e an d blade states. After switc ho v er , exis tin g c alls c ontinue as normal. The Redundan t b lad e no w becomes active and from this stage, the system operates with the new SW version.

The previously Active blad e burns the new software version file to its flash m emory, and then resets in Redundant mode.

Both blades now operate with the new software version and a switchback is issued to return the system to its original state. The previously Active blade now becomes active, and the previously Redundant blade resets once more to return to redundant state.

User's Manual 40 Document #: LTRT-95211

Page 41

User's Manual 4. System Initialization Process

Figure 6: Hitless Software Upgrade

Version 6.6 41 Mediant 3000 with TP-6310 & TP-8410

Page 42

Mediant 3000 with TP-6310 & TP-8410

This page is intentionally left blank.

User's Manual 42 Document #: LTRT-95211

Page 43

User's Manual 5. Configuration Using the Web Interface



5 Configuration Using the Web Interface

The device contains a Web interface to be used for configuration and for run-time monitoring. The W eb interface enables users equipped w ith any standard W eb-browsing application such as Micros oft™ Internet Explorer™ (Version 6.0 and higher ) or Firefox™ (Versions 5 through 9.0) to:

Provision devices (refer to 'Configuration' on page 74). Verify configuration changes in the Status pages (refer to ''Status and Diagnostic

Menu'' on page on page 47.

Load the CMP file (refer to 'Software Upgrade Wizard' on page 151). Load the ini, CAS, Voice Prompt, CPT, Prerecorded Tones, Dial Plan, Coder Table,

and AMD Sensitivity Files (refer to 'Load Auxiliary Files' on page

Note: Although the W eb Interface's recommended res olutions are 1024 x 768 and

1280 x 1024 pixels, AudioCodes supports other advanced resolutions.

161) or Toolbar (refer to 'Getting Acquainted with the Web Interface'

147).

5.1 Limiting the Web Interface to Read-Only Mode

Initially, the Web interface displays the default parameters that are pre-installed in the device. These param eters can be modified using the W eb interface, either by modifying parameters on the various pages or by loading a text configuration ini file to the device.

Administrators can lim it the Web interf ace to read-onl y mode by changing the value of the DisableWebConfig ini file parameter. The read-only mode feature can be used as a security measure. This security level provides protection against unauthorized access (such as Internet hacker attacks), particularly important to users without a firewall.

 To limit the Web Server to read-only mode:

Set the ini file parameter DisableWebConfig to 1 (Default = 0, i.e. read-write mode)

and send the modified ini file to the device. All Web pages are presented in read-only mode. The ability to modify configuration data is disabled. In addition, users do NOT have access to any "File Loading", "Regional Settings","Web User Accounts", "Maintenance Actions" and "Configuration File" pages.

Notes:

• 'Read Only' policy can also be employed by setting DisableWebConfig to 0,

setting the secondary account to User_Monitor access level and distributing the Main and Secondary accounts' user name password pairs according to the organization's security policy.

• When DisableWebConfig is set to 1, all users are demoted to ‘Read Only’

privileges regardless of their access level.

Version 6.6 43 Mediant 3000 with TP-6310 & TP-8410

Page 44

Mediant 3000 with TP-6310 & TP-8410



5.2 Disabling the Web Interface

5.2.1 Encrypted HTTP Transport (HTTPS - SSL)

Data transport between the Web server and the Web client may be conducted over a secured SSL link that encrypts the HTTP layer. The Web server may be configured to accept communicat ions onl y on a sec ured l ink (HTT PS) or both o n a sec ured l ink (HTT PS) and a non-secured link (HTTP). For further details refer to the Security chapter in the

5.2.2 Limiting Web Access to a Predefined List of C lient IP Addresses

5.2.3 Managing Web Serv er Access Us ing a RADIUS Server

Product Reference Manual.

When client IP address es are known in advance, adminis trators can define a list of up to 10 client IP addresses that ar e to be accepted by the Web server. An y client that does not bear an IP address in the pre-defined list is unable to connect to the Web server. For further details refer to the Security chapter in the Product Reference Manual.

Users are given the option to manage the web server's password-username pairs via a RADIUS server. For furthe r details refer to the Securit y chapter in the Product Ref erence Manual.

5.3 Initial Device Configuration using the Web Interface

When configuring a device for the first time using the Web interf ace, change the PC's IP address and Subnet Mas k to correspond with the dev ice's factory default IP add ress and Subnet Mask shown be lo w. F or details on changing th e IP addres s a nd Sub net Mas k, refer to the Help information provided by the Operating System used.

Default IP Address: 10.1.10.10 Default Subnet Mask: 255.255.0.0

User's Manual 44 Document #: LTRT-95211

Page 45

User's Manual 5. Configuration Using the Web Interface

script is disabled, a

5.4 Accessing the Web Interface

 To access the Web interface:

1. Open any standard Web-browser application, such as Micros oft™ Internet Explor er™

(Ver. 6.0 and higher) or Firefox™ (Ver. 2.5 and higher).

Note: The browser must be Java-script enabled. If java-

message box with notification of this is displayed.

2. Specify the IP address of the device in th e bro wser 's URL f ield (e. g., h ttp:// 10.1.229.17

or https://10.1.229.17 for an SSL secure link). The browser's Password page appears. The default user-name and password are both "Admin" (case-sensitive).

Figure 7: Enter Network Password Screen

Version 6.6 45 Mediant 3000 with TP-6310 & TP-8410

Page 46

Mediant 3000 with TP-6310 & TP-8410

5.5 Using Internet Explorer to Access the Web Interface

Internet Explorer's security settings may block access to the Gateway's Web browser if they're configured incorrectly. If this happens, the following message appears:

Unauthorized Correct authorizatio n is r equired for this ar ea. E ither your bro wser does not perf orm

authorization or your authorization has failed. RomPager server.

 To troubleshoot blocked access to Internet Explorer:

1. Delete all cookies from the T em porar y Internet files f older. If this does no t clear u p the

problem, the security settings may need to be altered. (Continue to Step 2).

2. In Internet Explorer, from the Tools menu, select Internet Options. The Internet

Options dialog box appears.

3. Sel ect the Security tab, an d the n, at th e bottom of the dialo g b ox , c lick Custom Level.

The Security Settings dialog box appears.

4. Scr oll d o wn unti l the L ogo n optio ns are dis p layed and change the setting to Prom pt for

user name and Password. Click OK.

5. Select the Advanced tab.

6. Scr oll down until the HTTP 1.1 Settings are displayed and verify that the Us e HTTP

1.1 option is checked.

7. Restart the browser. This fixes any issues related to domain use logon policy.

User's Manual 46 Document #: LTRT-95211

Page 47

User's Manual 5. Configuration Using the Web Interface



5.6 Getting Acquainted with the Web Interface

The figure below displays the general layout of the GUI of the Web interface:

Figure 8: Areas of the Web GUI

The Web GUI is composed of the following main areas:

Title Bar: Displays the corporate logo and device name. For replacing the logo with

another image or text, refer to Replacing the Corporate Logo. For customizing the device name, refer to Customizing the Product Name.

Toolbar: Provides frequently required command buttons for configuration (refer to

'Toolbar' below).

Navigation Pane: Consists of the following areas:

• Navigation bar: Provides tabs for accessing the configuration menus (refer to

'Navigation Tree' below), creating a Scenario (refer to 'Working with Scenario' on page 56), and searching ini file parameters that have corresponding Web interface parameters (refer to 'Searching for Configuration Parameters' on page 55 below).

• Navigation tree: Displays the elements pertaining to the tab selected on the

Navigation bar (tree-like structure of the configuration menus, Scenario Steps, or Search engine).

Work pane: Displays configuration pages where all configuration is performed (refer to

'Working with Configuration Pages' on page

51).

Version 6.6 47 Mediant 3000 with TP-6310 & TP-8410

Page 48

Mediant 3000 with TP-6310 & TP-8410

5.6.1 Toolbar

The toolbar provides command buttons for quick-and-eas y access to frequently required commands. The toolbar buttons are described in the table below:

Description of Toolbar Buttons

Icon Button Name Description

Submit Applies parameter settings to the device (refer to 'Saving Configuration

Burn Saves parameter settings to flash memory (refer to 'Saving Configuration

-- Device Actions

Changes' on page 55). Note: This icon is grayed out when not applicable to the currently opened page.

Changes' on page 55). Opens a drop-down menu list with frequently needed commands:

Load Configuration File: Opens the 'Configuration File' page for loading an ini file (refer to 'Restoring and Backing Up the device Configuration').

Save Configuration File: Opens the 'Configuration File' page for saving the ini file to a PC (refer to 'Restoring and Backing Up the device Configuration').

Reset: Opens the 'Maintenance Actions' page for resetting the device (refer to 'Maintenance' on page 142).

Restore Defaults: Opens the 'Configuration File' page for restoring the parameters default values (refer to Restoring Networking Parameters to their Default Values).

Software Upgrade Wizard: Opens the 'Software Upgrade Wizard' page for upgrading the device's software (refer to Software Upgrade Wizard).

Switch Over: Opens the “High Availability Maintenance” page for switching between Active and Redundant Boards (refer to 'High Availability Maintenance' on page 145).

Reset Redundant: Opens the "High Availability Maintenance" page for resetting the Redundant Board (refer to 'High Availability Maintenance' on page 145).

Home Opens the Home page (refer to Using the Home Page).

Help Opens the Online Help topic of the currently opened configuration page in

the Work pane (refer to 'Getting Help' on page 64).

Log off Logs off a session with the Web interface (refer to 'Logging Off the Web

Interface' on page 65).

Note: If you modif y parameters that only take effec t after a device reset, after you

click the Submit button, t h e too lbar d is plays the word "Reset" (in re d c ol or ). This is a reminder for you to later save (' burn') your settings to flash memory and reset the device.

User's Manual 48 Document #: LTRT-95211

Page 49

User's Manual 5. Configuration Using the Web Interface



5.6.2 Navigation Tree

The Navigation tree, loc ated in the Navig ation pane, displa ys the menus ( pertaining to the tab selected on the Navigation bar) used for accessing the configuration pages. The Navigation tree displays a tree-like structure of menus. You can easily drill-down to the required page item level to open its corresponding page in the Work pane.

The terminology used throughout this manual for referr ing to the hierarchical structure of the tree is as follows:

menu: first level (highest level) submenu: second level - contained within a menu. page item: last level (lowest level in a menu) - contained within a menu or submenu.

Figure 9: Terminology for Navigation Tree Levels

 To view menus in the Navigation tree:

On the Navigation bar, select the required tab (Configuration, Maintenance, or Status

& Diagnostics).

 To navigate to a page:

8. Navigate to the required page item, by performing the following:

• Drilling-down using the plus signs to expand the menus and submenus

• Drilling-up using the minus signs to collapse the menus and submenus

9. Select the required page item; the page opens in the Work pane.

5.6.2.1 Displaying Navigation Tree in Basic and Full View

You can view an expanded or reduced Navigation tree display regarding the number of listed menus and submenus. This is relevant when using the configuration tabs (Configuration, Maintenance and Status & Diagnostics) on the Navigation bar.

The Navigation tree menu can be displayed in one of two views:

Basic - Displays only commonly used menus Full - Displays all the menus pertaining to a configuration tab

The advantage of the Basic view is that it prevents "cluttering" the Navigation tree with menus that may not be required. Therefore, a Basic view allows you to easily locate required menus.

Version 6.6 49 Mediant 3000 with TP-6310 & TP-8410

Page 50

Mediant 3000 with TP-6310 & TP-8410

 To toggle between Full and Basic view:

Select the Basic optio n (located below the N aviga tion bar) to displa y a reduced menu tree; select the Full option to display all the menus. By default, the Basic option is selected.

Figure 10: Navigation Tree in Basic and Full View

Note: When in Scenar io mode (refer to 'Working with Sc enarios' on page 56), the

Navigation tree is displayed in 'Full' view (i.e., all menus are displayed in the Navigation tree).

5.6.2.2 Showing / Hiding the Navigation Pane

The Navigation pane can be hi dden to provide more space for elements displayed in the Work pane. This is especially useful when the Work pane displays a page with a table that's wider than the W ork pane and to view the all the colum ns, you need to use scroll bars. The arrow button located just below the Naviga tion bar is used to hide an d show the Navigation pane.

To hide the Navig ation pane: click the left-pointin g arrow ; the pane is hid den and the button is replaced by the right-pointing arrow button.

To show the Naviga tion pane: c lick the ri ght-p ointing arr ow ; the pane is displayed and the button is replaced by the left-pointing arrow button.

User's Manual 50 Document #: LTRT-95211

Page 51

User's Manual 5. Configuration Using the Web Interface

Figure 11: Showing and Hiding Navigation Pane

5.6.3 Working with Configuration Pages

The configuration pages contain the parameters for configuring the device. The configuration pages are displayed in the Work pane, which is located to the right of the Navigation pane.

5.6.3.1 Accessing Pages

The configuration pages ar e accessed b y clicking the required pag e item in the Navigat ion tree.

 To open a configuration page in the Work pane:

1. On the Navigation bar, click the required ta b (Configuration, Mainte nance, and Status

& Diagnostics); the menu options of the selected tab appear in the Navigation tree.

2. In the Navigation tree, drill-down to the required page item; the page opens in the

Work pane.

Version 6.6 51 Mediant 3000 with TP-6310 & TP-8410

Page 52

Mediant 3000 with TP-6310 & TP-8410



You can also access previously opened pages, by clicking your Web browser's Back button until you have reached the r equired page. T his is useful if you want to view pag es in which you have performed configurations in the current Web session.

Notes:

• You can also access certain pages from the Device Actions button located on the

toolbar (refer to 'Getting Acquainted with the Web Interface' on page 47).

• To view all the menus in the Navigation tree, ensure that the Navigation tree is in

'Full' view (refer to 'Getting Acquainted with the Web Interface' on page 47).

• To get Online Help for the currently opened page, refer to 'Getting Help' on page

64.

• Certain pages may not be accessible or may only be read-only if your Web user

account's access level is low (refer to 'Web User Accounts' on pag e 78). If a page is read-only, 'Read-Only Mode' is displayed at the bottom of the page.

5.6.3.2 Viewing Parameters

For convenience, some pages allow you to view a reduced or expanded display of parameters. A reduced d isplay allows you to easily identif y required parameters, enab ling you to quickly configure your device.

The Web Interface provides you with two methods for handling the display of page parameters:

Display of "Basic" and "Advanced" param eter s Display of parameter groups

Note: Certain pages may only be read-onl y if your Web user account's acc ess level

is low (refer to Conf iguring the Web Us er Accounts). If a pag e is read-only, 'ReadOnly Mode' is displayed at the bottom of the page.

5.6.3.3 Displaying Basic and Advanced Parameters

Some pages provide you with a n Advanced Parameter List / Basic Param eter List toggle button that allows you to show or hide advanced param eters (in addition to displaying the basic parameters). T his button is located on the top-right corner of the page and has two states:

Advanced Parameter List button with down-pointing arrow: click this button to display

all parameters.

Basic Parameter List button with up-pointing arrow: click this button to show only

common (basic) parameters.

User's Manual 52 Document #: LTRT-95211

Page 53

User's Manual 5. Configuration Using the Web Interface

The figure below shows an example of a page displa ying basic parameter s only, and then showing advanced parameters as well, using the Advanced Parameter List button.

Figure 12: Basic and Advanced Parameters

For ease of identification, the basic parameters are displayed with a darker blue color background than the advanced parameters.

Notes:

• When the Navigation tree is in 'Full' mode, configuration pages display all their

parameters (i.e., the 'Advanced Parameter List' view is displayed).

• If a screen contains only basic parameters, the Basic Parameter List button will

not be shown.

5.6.3.4 Showing / Hiding Parameter Groups

Some pages provide groups of parameters, which can be hidden or shown. To toggle between hiding and showing a group, simply click the group name button that appears above each group. The button appears with a down-pointing or up-pointing arrow, indicating that it can be collapsed or expanded when clicked, respectively.

Version 6.6 53 Mediant 3000 with TP-6310 & TP-8410

Page 54

Mediant 3000 with TP-6310 & TP-8410

Figure 13: Expanding and Collap sing Parameter Groups

5.6.3.5 Modifying Parameter Values

When you enter param eter values on a configuration page, the Edit s ymbol appears t o the right of these value fields. This feature is especially useful when modifying many parameters in a conf igur at i on p age in th at i t h elps to remind you of the parameters that you have currently modified (before applying the changes, i.e., clicking the Submit button).

Figure 14: Modifying Parameter Values

Once you apply your param eter changes by clicking the Submit button, th e Edit symbols disappear.

User's Manual 54 Document #: LTRT-95211

Page 55

User's Manual 5. Configuration Using the Web Interface

If you enter an invalid parameter value and then click Submit, a message box appears notifying you of the invalid value. In addition, the parameter value reverts back to its previous value and is highlighted in red, as shown in the figure below:

Figure 15: Value Reverts to Previous Valid Value

5.6.4 Saving Configuration Changes

To apply configurati on changes to the device's volatile m emory (RAM), click the Submit

button, which is located on the page in which you are working. Modifications to parameters with on-the-fly capabilities are immediately applied to the device; other parameters are applied only after a device reset.

However, parameter s saved to the volat ile memor y revert to their previous settings after a hardware or soft ware reset (or if the device is po wered down). Therefore, to en sure that parameter changes (wheth er on-the-f ly or not) are ret ained, you ne ed to save ('b urn') them to the device's non-volat ile memory (i.e., flas h). To save parameter c hanges to flash, refer to Saving Configuration.

Note: Parameters preceded by the lightn ing sign are not c hangeable on-the-fly

and require a device reset.

5.6.5 Searching for Configuration Parameters

The Web interface provides a search engine that allows you to search any ini file parameter that is configurable by the Web interface (i.e., has a corresponding Web parameter). You can searc h for a specific parameter (e.g., " EnableIPSec") or a sub-string of that parameter (e.g., "se c "). I f you search for a sub-string, all parameters that contain the searched sub-string in their names are listed.

 To search for ini file parameters configurable in the Web interface:

1. On the Navigation bar, click the Search tab; the Search engine appears in the

Navigation pane.

2. In the 'S earch' field, enter the parameter nam e or sub-string of the parameter name

that you want to search. If you have performed a previous search for such a

parameter, instead of entering the required string, you can use the 'Search History'

drop-down list to select the string (saved from a previous search).

3. Click Search; a list of located parameters based on your search appears in the

Navigation pane. Each searched result displays the following:

• Link (in green) to its location (page) in the Web interface

• Brief description of the parameter

Version 6.6 55 Mediant 3000 with TP-6310 & TP-8410

Page 56

Mediant 3000 with TP-6310 & TP-8410

4. In the s earched list, click the required param eter (link in green) to open the page in

which the parameter appears; the relevant page opens in the Work pane and the

searched parameter is highlighted for easy identification, as shown in the figure below:

Note: If the search ed parameter is not located, t he "No Matches Found For This

String" message is displayed.

Figure 16: Searched Result Screen

5.6.6 Working with Scenarios

The Web interface allows you to create your own "menu" with up to 20 pages selected from the menus in the Na vigation tree (i.e., pertaining to the C onfiguration, Maintenance, and Status & Diagnostics tabs). The "menu" is a set of configuration pages grouped into a logical entity referred to as a Scenari o. Each page in the Scenar io is referred to as a Step. For each Step, you can se lect up to 25 param eters in the page that you want available in the Scenario. Theref ore, the Scenario f eature is usef ul in that it allo ws you quick -and-easy access to commonly used c onfiguration parameters specific to your network environment . When you login to the Web interface, your Scenario is displayed in the Navigation tree, thereby, facilitating your configuration.

Instead of creating a Scenario, you can also load an existing Scenario from a PC to th e device (refer to 'Loading a Scenario to the Device' on page 62).

User's Manual 56 Document #: LTRT-95211

Page 57

User's Manual 5. Configuration Using the Web Interface

5.6.6.1 Creating a Scenario

The Web interface al lows you to create one Sc enari o with up to 2 0 conf igurat ion pages, as described in the procedure below:

 To create a Scenario:

1. On the Navigation bar, cl ick the Scenarios tab; a message box appears, r equesting

you to confirm creation of a Scenario:

Figure 17: Scenario Confirm Message Box

Note: If a Scenario already exists, the Scenario Loading message box appears.

2. Click OK; the Scenario mode ap pears in the Navigation tr ee as well as the menus of

the Configuration tab.

Note: If a Scenario already exists and you wish to create a new one, click the

Create Scenario button, and then click OK in the subsequent message box.

3. In the 'Scenario Name' field, enter an arbitrary name for the Scenario.

4. On the Navigation bar, click the Configuration or Maintenance tab to display their

respective menus in the Navigation tree.

5. In th e Navigation tree, selec t the r eq uire d p age item for the Step , an d th en in the page

itself, select the requ ired parameters by selecting the check boxes corresponding to

the parameters.

6. In the 'Step Name' field, enter a name for the Step.

7. Click Next located at the bottom of the page; the Step is add ed to the Scenario and

appears in the Scenario Step list:

Version 6.6 57 Mediant 3000 with TP-6310 & TP-8410

Page 58

Mediant 3000 with TP-6310 & TP-8410

Figure 18: Creating a Scenario

8. Repeat steps 5 through 8 to add additional Steps (i.e., pages).

9. W hen you have added all the require d Steps for your Scenario, clic k Save & Finish

located at the bottom of the Navigation tree; a mes sage box appears informing you

that the Scenario has been successfully created.

10. Click OK; the Scenario mode has ended an d the menu tree of the Co nfiguration tab

appears in the Navigation tree. Once you have created the Scenario, you can access it at any time by following the

procedure below:

User's Manual 58 Document #: LTRT-95211

Page 59

User's Manual 5. Configuration Using the Web Interface



 To access the Scenario:

On the Navigation bar, select the Scenario tab; the Scenario appears in the Navigation

tree, as shown in the example figure below:

Figure 19: Scenario Example

When you select a Scenari o Step, the corresponding page is displayed in the Wor k pane. The available parameters are indicated by a dark-blue background; the unavailable parameters are indicated by a gray or light-blue background.

To navigate between Scenario Steps, you can perform one of the following:

In the Navigation tree, click the required Scenario Step. In an opened Scenario Step, use the following navigation buttons:

• Next: opens the next Step listed in the Scenario.

• Previous: opens the previous Step listed in the Scenario.

Notes:

• Up to 20 Steps can be added to a Scenario, where each Step can contain up to

25 parameters.

• If you reset the device while in Scenario mode, after the device resets you are

returned once again to the Scenario mode.

• When in Scenario mode, the Navigation tree is in 'Full' display (i.e., all menus are

displayed in the Navigation tree) and the configuration pages are in 'Advanced Parameter List' display (i.e., all parameters are shown in the pages). This ensures accessibility to all parameters when creating a Scenario. For a description on the Navigation tree views, refer to Navigation Tree.

• If you previously created a Scenario and you click the Create Scenario button,

the previous Scenario is deleted and replaced with the one you are creating.

Version 6.6 59 Mediant 3000 with TP-6310 & TP-8410

Page 60

Mediant 3000 with TP-6310 & TP-8410

5.6.6.2 Editing a Scenario

You can modify a Scenario anytime by adding or removing Steps (i.e., pages) or parameters, and changing the Scenario name and the Steps' names.

 To edit a Scenario:

On the Navigation bar , clic k the Scenarios t ab; a m essage box appe ars, r eques ting you to confirm Scenario loading.

Figure 20: Scenario Loading Message Box

1. Click OK; the Scenario appears with its Steps in the Navigation tree.

2. Click the Edit Scenario button located at the bottom of the Navigation pane; the

'Scenario Name' and 'Step Name' fields appear.

3. You can perform the following operations:

• Add Steps:

a. On the Navigation bar, select the required tab (i.e., Configuration or

Maintenance); the tab's menu appears in the Navigation tree.

b. In the Navigation tree, navigate to the required page item; the corresponding

page opens in the Work pane.

c. In the page, select the required parameter(s) by marking the corresponding

check box(es).

d. Click Next.

• Add or Remove Parameters:

a. In the Navigation tree, select the required Step; the corresponding page

opens in the Work pane.

b. To add parameters, select the check boxes corresponding to the required

parameters; to remove parameters, clear the check boxes corresponding to the parameters that you want removed.

c. Click Next. A message box appears informing you that the Scenario step

has been successfully modified.

d. Click OK.

• Edit the Step Name:

a. In the Navigation tree, select the required Step. b. In the 'Add Step name' field, modify the Step name. c. In the page, click Next.

• Edit the Scenario Name:

a. In the 'Scenario Name' field, edit the Scenario name. b. In the displayed page, click Next.

• Remove a Step:

a. In the Navigation tree, select the required Step; the corresponding pag e

opens in the Work pane.

b. In the page, clear all the check boxes corresponding to the parameters. c. Click Next. d. After clicking Next, a message box appears notifying you of the change.

Click OK.

User's Manual 60 Document #: LTRT-95211

Page 61

User's Manual 5. Configuration Using the Web Interface

4. Click Save & Finish; a message box appears informing you that the Scenario has

been successfully modified. The Scenario mode is exited and the menus of the Configuration tab appear in the Navigation tree.

Note: To delete a Scenario, you can either load an em pty dat file (refer to 'Loading

a Scenario to the Device' o n page 62) or load an ini f ile with the ScenarioF ileName value set to a file that has no content.

5.6.6.3 Saving a Scenario to a PC

You can save a Scenari o to a PC (as a dat file) . This is es peciall y useful when you require more than one Scenario to represent different environment setups (e.g., where one includes PBX interoperabi lity and another not). Once you create a Scenar io and save it to your PC, you can then keep on saving modifications to it under different Scenario file names. When you requir e a specific network environm ent setup, you can simply load the suitable Scenario fil e from your PC (refer to 'Loading a Scenario to th e Device' on page

62).

 To save a Scenario to a PC:

1. On the Navigation bar, cl ic k the Scenarios tab; th e Sc enari o a ppe ar s in th e Navigation

tree.

2. Click the Get/S end Scenar io File butt on (located at the bottom of the Navigation tree);

the 'Scenario File' page appears, as shown below:

Figure 21: Scenario File Page

3. Click Get Scenario File.

Version 6.6 61 Mediant 3000 with TP-6310 & TP-8410

Page 62

Mediant 3000 with TP-6310 & TP-8410

5.6.6.4 Loading a Scenario to the Device

Instead of creating a Scenar io, you can loa d a Scena rio file (data f ile) from your PC to the device.

 To load a Scenario to the device:

1. On the Navigation bar, cl ic k the Scenarios tab; th e Sc enari o a ppe ar s in th e Navigation

tree.

2. Click the Get/S end Scenar io File button (located at the bottom of the Navigat ion tree);

the 'Scenario File' page appears (refer to 'Saving a Scenario to a PC' on page 61).

3. Click the Browse button, and then navigate to the Scenario file stored on your PC.

4. Click the Send File button.

Notes:

• The loaded Scenario replaces any existing Scenario.

• Instead of using the Web Interface, you can load an ini file to the device with the

ScenarioFileName ini file parameter.

5.6.6.5 Exiting Scenario Mode

When you want to close t he Scenario mode after using it for de vice configuration, follow the procedure below:

 To close the Scenario mode:

1. Simply click any tab (besides the Scenarios tab) on the Navigation bar, or click the

Cancel Scenarios butt on located at th e bottom of the Navigatio n tree; a m essage box appears, requesting you to confirm exiting Scenario mode, as shown below.

Figure 22: Confirmation Message fo r Exiting Scenario Mode

2. Click OK to exit.

5.6.6.6 Deletin g a Scen ari o

You can delete the Sce nario by using the De lete Scenario File butt on, as described i n the procedure below:

 To delete the Scenario:

1. On the Navigation bar, click the Sc enarios tab; a message box appears, reque sting

you to con firm:

Figure 23: Scenario Loading Message Box

2. Click OK; the Scenario mode appears in the Navigation tree.

User's Manual 62 Document #: LTRT-95211

Page 63

User's Manual 5. Configuration Using the Web Interface

Note: Each index represents a line of text in the Welcome message box.

3. Click the Delet e Scen ario F ile button; a message box appears request ing conf irmat ion

for deletion.

Figure 24: Message Box for Confirming Scenario Deletion

4. Click OK; the Scenario is deleted and the Scenar io m ode closes.

5.6.7 Creating a Login Welcome Message

You can create a Welcome message box (alert message) that appears after each successful login to the device's Web interface. The WelcomeMessage ini file parameter table allows you to create the W elcome message. Up to 20 lines of character strings c an be defined for the m ess age. If this parameter is not co nfigured, no W elcome m essage box is displayed after login.

An example of a Welcome message is shown in the figure below:

Figure 25: User-Defined Web Welcome Message after Login

ini File Parameter for Welcome Login Message

Parameter Description

WelcomeMessage Defines the Welcome message that appears after a successful login to

the Web interface. The format for this ini file parameter table is as follows: [WelcomeMessage] FORMAT WelcomeMessage_Index = WelcomeMessage_Text; WelcomeMessage 1 = "..." ; WelcomeMessage 2 = "..." ; WelcomeMessage 3 = "..." ; [\WelcomeMessage]

For Example: [WelcomeMessage ] FORMAT WelcomeMessage_Index = WelcomeMessage_Text; WelcomeMessage 1 = "**********************************" ; WelcomeMessage 2 = "********* This is a Welcome message ***" ; WelcomeMessage 3 = "**********************************" ; [\WelcomeMessage]

Version 6.6 63 Mediant 3000 with TP-6310 & TP-8410

Page 64

ini File Parameter for Welcome Login Message

Up to 20 indices can be defined.

Parameter Description

5.6.8 Getting Help

The Web interface provides you with context-sensitive Online Help. The Online Help provides you with brief descriptions of most of the param eters you'll need to successfully configure the device. T he Onli ne He lp pr o vides d es cr iptio ns of par ameters pertaining to the currently opened page.

 To view the Help topic for a currently opened page:

1. Using the Navigation tree, open the required page for which you want Help.

2. On the toolbar, click the Help button; the Help topic pertaining to the opened

page appears, as shown below:

Mediant 3000 with TP-6310 & TP-8410

Figure 26: Help Topic for Current Page

3. T o view a description of a parameter, click the plus sign to expand the par ameter.

To collapse the description, click the minus sign.

4. T o c los e the Help to pic, c lic k the c lose button l oc ate d on the to p-right corner of the

Help topic window or click the HELP button.

Note: Instead of click ing the Help button for each page you open , you can open it

once for a page, and the n s imply leave it open. Each t i me you open a different pa ge, the Help topic pertaining to that page is automatically displayed.

User's Manual 64 Document #: LTRT-95211

Page 65

User's Manual 5. Configuration Using the Web Interface

5.6.9 Logging Off the Web Interface

You can log off the Web interface and re-access it with a different user account. For detailed information on the Web User Accounts, refer to User Accounts.

 To log off the Web Interface:

1. On the toolbar, click the Log Off button; the 'Log Off ' confirmation message box

appears:

Figure 27: Log Off Confirmation Box

2. Click OK; the Web session is logged off . T he "W eb page f or the s essio n is logg ed of f"

message box appears, with a "Log In" button.

3. To log on again, simply click any page item in the navigation tree, and then in the

'Enter Network Password' dialog box, enter your user name and password.

Version 6.6 65 Mediant 3000 with TP-6310 & TP-8410

Page 66

Mediant 3000 with TP-6310 & TP-8410

The following 'Home' page is applicable to the 6310/3000 devices using

Simplex configuration (without High Availability). Refer to 'High Availability

5.7 Using the Home Page

The Home icon, located o n the toolbar, opens the 'Home' page. This page pr ovides you with a graphical display of the device's front panel. This page allows you to monitor the functioning of the device by its c olor-coded icons. The 'Hom e' page also displays general information in the 'General Information' pane such as the device's IP address, firmware version and the High Availability status.

Using a High Avail ability configuration, the ‘General Information’ pane dis plays additional information showing the High Availability status and the Active Board Slot Number. In MEGACO It also includes information about the status of the connection to the call agent.

5.7.1 TP-6310

 To access the Home page:

1. On the toolbar, click the Home icon; the 'Home' page is displayed:

Note:

Configuration' on page 72 for more information.

Figure 28: 6310/3000 Home Page using Simplex Configuration

6310/3000 Home Page Descriptions

Item# / Label Description

1 Fan Tray unit displaying operating status of fans:

(green): normal operation (red): fan failure or fan missing

You can also view current alarms, by clicking anywhere in this area (refer to 'Viewing the Active Alarms Table' on page 70).

2 System unit displaying chassis severity alarm LEDs:

(green): no alarm - normal functioning. (red): Critical, Shelf, and / or System alarm raised ( orange): Major and / or Minor alarm raised

User's Manual 66 Document #: LTRT-95211

Page 67

User's Manual 5. Configuration Using the Web Interface

6310/3000 Home Page Descriptions

Item# / Label Description

3 SA/M3K Alarms and Status blade's FAIL LED:

(gray): Normal functioning. (red): Blade failure.

4 SA/M3K Alarms and Status blade's ACT LED:

(gray): Single blade. (green): Active blade.

(orange): Standby blade.

5 6310 blade's FAIL LED:

(gray): Normal functioning. (red): Blade failure.

6 6310 blade's ACT LED:

(gray): Single blade. (green): Active blade.

(orange): Standby blade.

7 & 8

9 PSTN LEDs grouped in pairs, each displaying a PSTN Link LED (left LED) with a

Dual Ethernet port status LEDs (Eth 1 and Eth 2):

(gray): No link. (green): Active Ethernet link. (yellow): Redundant link. (Not applicable to IPM)

You can also view detailed information (in the 'Ethernet Port Information' page) of an Ethernet port, by clicking the LED icon (refer to 'Viewing Ethernet Port Information' on page 71).

PSTN Alarm LED (right LED). The PSTN Link LED indicates the status of the PSTN link, while the PSTN Alarm LED indicates the traffic loss alarm type associated with the PSTN link.

PSTN Link LED:

(gray): No link. (green): Active link (for optical STM1/OC3 interface) or “DS3 Synchronized” (for

DS3 interface).

(yellow): Standby link. (red): PSTN alarm.

PSTN Alarm LED:

(gray): No alarm (for optical STM1/OC3 interface) or “No Near-end Alarm” (for

DS3 interface).

(red): PSTN alarm exists.

(orange): D-channel alarm (ISDN only) (dark orange): NFAS alarm (ISDN only)

You can also view and modify PSTN link settings, by clicking the PSTN Settings Transmission Settings menu option in the Web Interface (refer to Viewing and Modifying PSTN Settings).

Version 6.6 67 Mediant 3000 with TP-6310 & TP-8410

Page 68

Mediant 3000 with TP-6310 & TP-8410

6310/3000 Home Page Descriptions

Item# / Label Description

10 Power status (PWR LED) of the blade:

(green): Power received by blade. (red): No power received by blade.

11 Slot status of installed blade in the chassis (SWAP Ready LED).

12 & 13 Power supply units (PS/DC/3K modules) LED (Power Supply Number 1 & 2 LED):

(green): Normal functioning. (red): Power failure.

User's Manual 68 Document #: LTRT-95211

Page 69

User's Manual 5. Configuration Using the Web Interface



Simplex configuration (without High Availability). Refer to 'High Availability

1 2

3 4

5 6

10 11 12

5.7.2 TP-8410

 To access the Home page, take this step:

On the toolbar, click the Home icon; the 'Home' page is displayed:

Note: The following 'H ome' page is applicable to th e 8410/3000 devices using t he

Configuration' on page 72 for more information.

Figure 29: TP-8410 Home Page

Mediant 3000/TP-8410 Home Page Descriptions

Item# / Label Description

1 Fan Tray unit displaying operating status of fans:

(green): normal operation (red): fan failure or fan missing

You can also view current alarms, by clicking anywhere in this area (refer to 'Viewing the Active Alarms Table' on page 70).

2 System unit displaying chassis severity alarm LEDs:

(green): no alarm - normal functioning. (red): Critical, Shelf, and / or System alarm raised ( orange): Major and / or Minor alarm raised

3 SA/M3K Alarms and Status blade's FAIL LED:

(gray): Normal functioning. (red): Blade failure.

Version 6.6 69 Mediant 3000 with TP-6310 & TP-8410

Page 70

Mediant 3000 with TP-6310 & TP-8410



Mediant 3000/TP-8410 Home Page Descriptions

Item# / Label Description

4 SA/M3K Alarms and Status blade's ACT LED:

(gray): Single blade. (green): Active blade.

(orange): Standby blade.

5 8410 blade's FAIL LED:

(gray): Normal functioning. (red): Blade failure.

6 8410 blade's ACT LED:

(gray): Single blade. (green): Active blade.

(orange): Standby blade.

10 Power status (PWR LED) of the blade:

(green): Power received by blade. (red): No power received by blade.

11 Slot status of installed blade in the chassis (SWAP Ready LED).

12 & 13 Power supply units (PS/DC/3K modules) LED (Power Supply Number 1 & 2 LED):

(green): Normal functioning. (red): Power failure

5.7.3 Viewing the Active Alarms Table

The 'Home' page allows you to view a list of currently active alarms. These alarms are displayed in the 'Active Alarms' page. In addition, the color of the 'Alarms' area in the 'Home' page indicates the highest alarm severity currently listed in the 'Active Alarms' page.

 To view the list of alarms:

On the 'Home' page, click the Alarm s area, next to the Fan Tra y unit (labeled as item #2 in the figures in Using the 'Home' page above); the 'Active Alarms' page appears:

Figure 30: Viewing Active Alarms

For each alarm, the following is displayed:

Severity: severity level of the alarm:

• Critical: alarm displayed in red

• Major: alarm displayed in orange

• Minor: alarm displayed in yellow

Source: unit from which the alarm was raised Description: brief explanation of the alarm Date: date and time that the alarm was generated

User's Manual 70 Document #: LTRT-95211

Page 71

User's Manual 5. Configuration Using the Web Interface



5.7.3.1.1 Viewing Alarm History

The Alarms History page displays a list of alarms that have been raised and traps that have been cleared.

 To view the list of history alarms:

Open the Alarms History page (Status & Diagnostics tab > System Status menu >

Carrier-Grade Alarms > Alarms History).

Figure 31: Viewing Alarm History

For each alarm, the following information is provided: Severity: severity level of the alarm:

• Critical (red)

• Major (range)

• Minor (y ellow)

• Cleared (green)

Source: unit from which the alarm was raised Description: brief explanation of the alarm Date: date and time that the alarm was generated

You can view the next 20 alarms (if exist), by clicking the Go to page button.

 To delete all the alarms in the table:

2. Click the Delete History Table button; a confirmation message box appears.

3. Click OK to confirm.

5.7.4 Viewing Ethernet Port Information

 To view Ethernet port settings via the Home page:

1. Click the 'Home' page icon.

2. Click the Ethernet port for which you want to view port settings; the 'Ethernet Port

Information' page opens:

Figure 32: Ethernet Port Information

Version 6.6 71 Mediant 3000 with TP-6310 & TP-8410

Page 72

Mediant 3000 with TP-6310 & TP-8410

5.7.5 High Availability Configuration

Once the Mediant 3000 setup is using High Availabi lity, additional inf ormation and o ptions will be available via the Web interface. A sample Mediant 3000 Home Page with High Availability is shown below.

Figure 33: Mediant 3000 with TP-6310 Home Page using High Availability Setup

Figure 34: Mediant 3000 with TP-8410 Home Page using High Availability Setup

Refer to the Hom e Page f igur e in 'Us ing t he Hom e Pa ge - Mediant 3000/T P-6310' on page 66 for a full led reference.

The active board is indicated both by “Active Board Slot Number” in the “General Information” pane and by appearing shaded in dark er color. The “Hi gh Availability” status shows whenever the system is High Availability ready, synchronizing or in case of an error, the error reason.

User's Manual 72 Document #: LTRT-95211

Page 73

User's Manual 5. Configuration Using the Web Interface



5.7.5.1 Manual Switch Over / Redundant Board Reset

A High Availability system has two additional options:

Manually switching over between the active and redundant board Manually resetting the redundant board

These options are avail able on the High Availabilit y Maintenance Home Page accessible otherwise by selecting “S witch Over” or “Reset Redundant” via the Device Actions, or, by navigating through Maintenance - High Availability Maintenance. Selecting either option requires an additional confirmation.

Figure 35: Mediant 3000 - High Availability Maintenance

Note: Selecting either opti on will result in no High Availabilit y for a period of

time.

Version 6.6 73 Mediant 3000 with TP-6310 & TP-8410

Page 74

Mediant 3000 with TP-6310 & TP-8410



5.8 Configuration

5.8.1 System

5.8.1.1 Application Settings

Application Settings inc lude the following features: NT P, Da ylight S av in g T im e, STUN, NFS and DHCP Settings.

In this option, the following can be configured:

NTP Server Day Light Sa ving T im e STUN Settings NFS Servers Settings Enable the DHCP client

 To configure the Application Settin g s:

1. Open the Application Settings page (Configuration tab > System menu >

Application Settings).

Figure 36: Application Settings

2. To configure this page, refer to the System Parameters sub-section in the Product

Reference Manual.

3. Af ter conf igur in g/modifying the parameter f ields, c lic k the Submit button. The changes

are entered into the system and the page is refreshed.

 To configure the NFS Settings:

Network File System (NFS) enables the device to access a remote server's shared files and directories and to hand le them as if they're locate d locall y. The device can use NF S to load cmp, ini, and auxiliary files through the Automatic Update mechanism (refer to the Product Reference Manual).

You can configure up to 16 different NFS file systems. As a file system, the NFS is independent of m achine types, operati ng systems and network architec tures. Note that an NFS file server can share multiple file systems. There must be a separate row for each remote file system shared by the NFS file server that needs to be accessed by the device.

User's Manual 74 Document #: LTRT-95211

Page 75

User's Manual 5. Configuration Using the Web Interface

 To add remote NFS file systems:

1. Open the Application Settings page (Configuration tab > System menu >

Application Settings).

Under the 'NFS Settings' group, click the NFS Table button; the NFS Table page appears.

2. Click the Add button; the Add Record dialog box appears:

Figure 37: Add Record Dialog Box - NFS

3. Configure the NFS parameters according to the table below.

4. Click the Submit button; the remote NFS file system is immediately applied, which

can be verified by the ap pearance of the 'NF S mount was successf ul' message in the Syslog server.

5. To save the changes to flash memory, see 'Saving Configuration' on page 145.

Notes:

• To avoid terminating current calls, a row must not be deleted or modified while

the device is currently accessing files on that remote NFS file system.

• The combination of 'Host Or IP' and 'Root Path' must be unique for each row in

the table. For example, the table must include only one row with a Host/IP of

192.168.1.1 and Root Path of /audio.

• The NFS table can also be configured using the table ini file parameter

NFSServers (refer to the 'NFS Parameters' in the Product Reference Manual).

Version 6.6 75 Mediant 3000 with TP-6310 & TP-8410

Page 76

Mediant 3000 with TP-6310 & TP-8410



5.8.1.2 Syslog Settings

The procedure below describes how to configure Syslog.

 To configure Syslog:

1. Open the Syslog Settings page (Configuration tab > System menu > Syslog

Settings).

Figure 38: Syslog Settings

2. Enable the Syslog feature by setting the 'Enable Syslog' to Enable.

3. Define the Syslog server using the 'Syslog Server IP Address' and 'Syslog Server Port'

parameters.

4. Configure the debug level using the 'Debug Level' parameter.

5. Under the 'Activity Types to Report ...' group, select the activities to report.

6. Click Submit to apply your changes.

5.8.1.3 Regional Settings

The Regional Settings page allows setting the system date and time.

 To access the Regional Settings page:

Open the Regional Settings page (Configuration tab > System menu > Regional

Settings).

Figure 39: Regional Settings

User's Manual 76 Document #: LTRT-95211

Page 77

User's Manual 5. Configuration Using the Web Interface

 To set the date and time:

1. Enter the date and/or tim e using the YYYY, MM, and DD field for Year, Month and

Day and HH, MM, and SS fields for Hour, Minutes and Seconds.

2. Click Submit. The date and time is set on the device, accordingly.

Note: When the NTP feature is enabled (the NTP server is defined in the

Application Settings page) , the date and time are in Read O n l y m ode as th e y are s et by the NTP server.

5.8.1.4 Certificates

This page allows managing the security certificates loaded on the device. The device is shipped with a working certificate conf iguration. Use this page onl y as needed. For f urther information, refer to the Security chapter in the Product Reference Manual.

5.8.1.4.1 TLS Server Certificate Expiry Check

The device can per iodical ly check the va lidat ion dat e of the instal led TLS server cer tificate . This periodic check interval is user-defined. In addition, within a user-defined number of days before the installed TLS server certificate expires, the device can be configured to send the SNMP trap, acCertificateExpiryNotifiaction to notify of the impending certificate expiration.

 To configure TLS certificate expiry checks and notification:

1. Open the Certificates page.

2. In the 'TLS Expiry Check Start' f ield, ent er the number of days before the insta lled TLS

server certificate is to expire at which the device m ust send a trap to notify of this.

Figure 40: TLS Expiry Settings

3. In the 'TLS Expiry Check Period' field, enter the periodical interval (in days) for

checking the TLS server certificate expiry date. By default, the device checks the certificate every 7 days.

4. Click the Submit TLS Expiry Settings butto n.

Version 6.6 77 Mediant 3000 with TP-6310 & TP-8410

Page 78

Mediant 3000 with TP-6310 & TP-8410



Note: There must be at least one Security

5.8.1.5 Management

Management - Contains a drop-down list with the following options:

Web User Accounts - Refer to 'Web User Accounts' on page 78 Web Security Settings - Refer to 'Web Security Settings' on page 85 Telnet/S SH Set tin gs - Refer to 'Telnet/SSH Sett ings' on page 86 Web & Telnet Access List - Refer to 'Web & Telnet Access List' on page 86 RADIUS Settings - Refer to 'RADIUS Settings' on pag e 87 SNMP - Refer to 'SNMP' on page 88

• SNMP Community Settings - Refer to 'SNMP Community Settings' on page 88

• SNMP Trap Destinations - Refer to 'SNMP Trap Destinations' on page 89

• SNMP Trusted Managers - Refer to 'SNMP Trusted Managers' on page 89

5.8.1.5.1 Web User Accounts

• SNMP V3 Users - Refer to 'SNMP V3 Users' on page 90

You can create up to 10 Web user accounts for the device. Up to five Web users can simultaneously be logged in to the device's Web interface. Web user accounts prevent unauthorized access to the Web interf ace, enabling login acces s only to users wi th correct credentials (i.e., username and password). Each Web user account is composed of the following attributes:

Username and password: Credentials that enable authorized login access to the Web

interface.

Access level (user type): Access privileges specifying what the user can view in the

Web interface and its read/write privileges. The table below describes the different types of Web user account access levels:

User Access

Level

Master

Security

Administrator

Monitor

No Access

Access Levels of Web User Accounts

Numeric

Representation*

220

200

100

Privileges

Read / write privileges for all pages. Can create all user types, including additional Master users and Security Administrators. It can delete all users except the last Security Administrator.

Read / write privileges for all pages. It can create all user types and is the only one that can create the first Master user.

Administrator.

Read / write privileges for all pages except securityrelated pages, which are read-only.

No access to security-related and file-lo adi ng pag es; read-only access to other pages.

No access to any page. Note: This access level is not applicable when using

advanced Web user account configuration in the Web Users table.

User's Manual 78 Document #: LTRT-95211

Page 79

User's Manual 5. Configuration Using the Web Interface

User Access

Level

* The numeric representation of the access level is used only to define accounts in a RADIUS server (the access level ranges from 1 to 255).

By default, the device is pre-configured with the following two Web user accounts:

User Access Level Username

Security Administrator Admin Admin Monitor User User

After you log in to the Web interface, the username is displayed on the toolbar. If the Web session is idl e (i.e., no actions are performed) for more than five m inutes, the

Web session expires and you ar e once again requested to login with your username and password. Users can be banned for a period of time upon a user-defined number of unsuccessful login attempts. Login information (such as how many login attempts were made and the last successful login time) can be presented to the user.

Numeric

Representation*

Pre-configured Web User Accounts

(Case-Sensitive)

Privileges

Password

(Case-Sensitive)

 To prevent user access after a specific number of failed logins:

1. From the 'Deny Access On Fail Count' drop-down list, select the number of failed

logins after which the us er is prevented access to the devic e for a user-defined tim e (see next step).

2. In the 'D eny Authentication Timer' field, enter the i nterval (in seconds) that the user

needs to wait before a new login attem pt fr om the sam e IP address can be do ne aft er reaching the number of failed login attempts (defined in the previous step).

Notes:

• For security reasons, it's recommended that you change the default username

and password.

• The Security Administrator user can change all attributes of all Web user

accounts. Web users with access levels other than Security Administrator can change only their password and username.

• To restore the two Web user accounts to default settings (usernames and

passwords), set the ini file parameter ResetWebPassword to 1.

• To log in to the Web interface with a different Web user, click the Log off button

and then login with a different username and password.

• You can set the entire Web interface to read-only (regardless of Web user

access levels), by using the ini file parameter DisableWebConfig (refer to the 'Web and Telnet Parameters' in the Product Reference Manual).

• You can define additional Web user accounts using a RADIUS server (refer to

the 'Configuring RADIUS Settings' in the Product Reference Manual).

Version 6.6 79 Mediant 3000 with TP-6310 & TP-8410

Page 80

Mediant 3000 with TP-6310 & TP-8410

5.8.1.5.2 Basic User Accounts Configuration

This section describ es basic Web user account configuration. This is relevant only if the two default, pre-configured Web user accounts - Security Administrator ("Admin") and Monitor ("User") - are sufficient for your management scheme.

For the Security Administr ator, you can change only the username and pas sword; not its access level. For th e Monitor user, you can change us ername and password as well as access level (Administrator, Monitor, or No Access).

Notes:

• The access level of the Security Administrator cannot be modified.

• The access level of the second user account can be modified only by the

Security Administrator.

• The username and password can be a string of up to 19 characters. When you

• Up to two users can be logged in to the Web interface at the same time, and they

can be of the same user.

 To configure the two pre-configured Web user accounts:

1. Open the Web Us er Accounts page (Configuration tab > System menu > Web User

Accounts). If you are logged in as Security Administrator, both W eb user accounts

are displayed (as sho wn below). If you are logged i n with the second user account, only the details of this user account are displayed.

Figure 41: Web User Accounts Screen - Security Administrator Level

2. To change the username of an account: a. In the 'User Name' field, enter the new user name.

b. Click Change User Name; if you are currently logged in to the Web interface with

this account, the 'Web Login' dialog box appears.

c. Log in with your ne w user n ame.

User's Manual 80 Document #: LTRT-95211

Page 81

User's Manual 5. Configuration Using the Web Interface



3. To change the password of an account: a. In the 'Current Password' field, enter the current password.

b. In the 'New Password' and 'Confirm New Password' fields, enter the new

password.

c. Click Change Password; if you are currently logged in to the Web interface with

this account, the 'Web Login' dialog box appears.

4. To change the access level of the optional, second account: a. Under the Account Data for User: User group, from the 'Access Level' drop-down

list, select a new access level user.

b. Click Change Access Level; the new access level is applied immediately.

5.8.1.5.3 Advanced User Accounts Configuration

This section descr ibes advanced Web user account c onfiguration. This is relevant if you need the following management scheme:

Enhanced security settings per Web user (e.g., limit session duration)

More than two Web user accounts (up to 10 Web user accounts)

Master users

This advanced W eb user configuration is done in the W eb Users table, which is initially accessed from the Web User Accounts page (see procedure below). Once this table is accessed, subsequent ac cess immediatel y opens the W eb Users table instead of the W eb User Accounts page.

Notes:

• Only the Security Administrator user can initially access the Web Users table.

• Only Security Administrator and Master users can add, edit, or delete users.

• Admin users have read-only privileges in the Web Users table. Monitor users

have no access to this page.

• If you delete a user who is currently in an active Web session, the user is

immediately logged off by the device.

• All users can change their own passwords. This is done in the WEB Security

Settings page (see 'Web Security Settings' on page 85).

• To remove the Web Users table and revert to the Web User Accounts page with

the pre-configured, default Web user accounts, set the ResetWebPassword ini file parameter to 1. This also deletes all other Web users.

• Once the Web Users table is accessed, Monitor users and Admin users can only

change their passwords in the Web Security Settings page (see 'Web Security Settings' on page 85). The new password must have at least four different characters than the previous password. (The Security Administrator users and Master users can change their passwords in the Web Users table and in the Web Security Settings page.)

Version 6.6 81 Mediant 3000 with TP-6310 & TP-8410

Page 82

Mediant 3000 with TP-6310 & TP-8410

 To add Web user accounts with advanced settings:

1. Open the Web Users Table page:

• Upon initial access:

a. Open the Web User Accounts page (Configuration tab > System menu >

Web User Accounts).

b. Under the Web Users Table group, click the Create Table button.

• Subsequent access: Configuration tab > System menu > Web User Accounts.

The Web Users table appears, listing the two default, pre-configured Web use accounts - Security Administrator ("Admin") and Monitor ("User"):

Figure 42: Web Users Table Page

2. Click Add; the following dialog box is displayed:

Figure 43: Web Users Table - Add Record Dialog Box

3. Add a user as required. For a description of the parameters, see the table below.

4. Click Submit.

Parameter Description

Web: Username

Web User Parameters Description

Defines the Web user's username. The valid value is a string of up to 40 alphanumeric characters,

including the period ".", underscore "_", and hyphen "-" signs.

User's Manual 82 Document #: LTRT-95211

Page 83

User's Manual 5. Configuration Using the Web Interface

This state is automatically set for users

set by the 'Deny Access on Fail Count' parameter (see

eout configured by

efined

number of days, set by the 'User Inactivity Timer' (see can only log in to the Web interface if their status is

changed (to New or Valid) by a System Administrator or

Web User Parameters Description

Parameter Description

Web: Password

Web: Status

Defines the Web user's password. The valid value is a string of 8 to 40 ASCII characters, which must

include the following:

 At least eight characters  At least two letters that are upper case (e.g., "AA")  At least two letters that are lower case (e.g., "aa")  At least two numbers  At least two signs (e.g., the dollar "$" sign)  No spaces in the string  At least four characters different to the previous password

Defines the status of the Web user.

 New = (Default) User is required to change its password on the

next login. When the user logs in to the Web interface, the user is immediately prompted to change the current password.

 Valid = User can log in to the Web interface as normal.

Failed Access = that exceed a user-def ined num ber of failed login at tempts ,

'Configuring Web Sec urity Sett ings' on p age ). Thes e users can log in only after a user-defined tim the 'Block Duration' param eter (see below) or if their status is changed (to New or Valid) b y a System Administrator or Master.

Old Account = This state is automatically set for user s that have not accessed the Web interface for a user-d

'Configuring Web Sec urity Sett ings' on p age ). Thes e users

Master.

Notes:

 The Old Account status is applicable only to Admin and Monitor

users; System Administrator and Master users can be inactive indefinitely.

 For security, it is recommended to set the status of a newly added

Web: Password Age

user to New in order to enforce password change.

Defines the duration (in days) of the validity of the password. When this duration elapses, the user is prompted to change the password; otherwise, access to the Web interface is blocked.

The valid value is 0 to 10000, where 0 means that the password is always valid. The default is 90.

Web: Session Limit

Defines the maximum number of Web interface sessions allowed for the user. In other words, this allows the same user account to log in to the device from different sources (i.e., IP addresses).

The valid value is 0 to 5. The default is 2. Note: Up to 5 users can be logged in to the Web interface at any

given.

Version 6.6 83 Mediant 3000 with TP-6310 & TP-8410

Page 84

Mediant 3000 with TP-6310 & TP-8410

Web User Parameters Description

Parameter Description

Web: Session Timeout

Web: Block Duration

Web: User Level

Defines the duration (in minutes) of Web inactivity of a logged-in user, after which the user is automatically logged off the Web interface.

The valid value is 0 to 100000. The default is according to the settings of the 'Session Timeout' global parameter (see 'Web Security Settings' on page 85).

Defines the duration (in seconds) for which the user is blocked when the user exceeds a user-defined number of failed login attempts. This is configured by the 'Deny Access On Fail Count' parameter (see 'Web Security Settings' on page 85).

The valid value is 0 to 100000, where 0 means that the user can do as many login failures without getting blocked. The default is according to the settings of the 'Deny Authentication Timer' parameter ((see 'Web Security Settings' on page 85).

Note: The 'Deny Authentication Timer' parameter relates to failed Web logins from specific IP addresses.

Defines the user's access level.

 Monitor = (Default) Read-only user. This user can only view Web

pages and access to security-related pages is denied.

 Admin = Read/write privileges for all pages, except security-related

pages including the Web Users table where this user has only read-only privileges.

 SecAdmin = Read/write privileges for all pages. This user is the

Security Administrator.

 Master-User = Read/write privileges for all pages. This user also

functions as a security administrator.

Notes:

 At least one Security Administrator must exist. The last remaining

Security Administrator cannot be deleted.

 The first Master user can be added only by a Security

Administrator user.

 Additional Master users can be added, edited and d elet ed on ly by

Master users.

 If only one Master user exists, it can be deleted only by itself.  Master users can add, edit, and delete Security Administrators (but

cannot delete the last Security Adminis trator ).

 Only Security Administrator and Master users can add, edit, and

delete Admin and Monitor users.

User's Manual 84 Document #: LTRT-95211

Page 85

User's Manual 5. Configuration Using the Web Interface

5.8.1.5.4 Web Security Settings

The Web Security Settings page is used to define a secure Web acc ess communication method. For a description of these parameters, see 'Web and Telnet Param eters' in the Product Reference Manual

 To define Web access security:

1. Open the WEB Security Settings page (Configuration tab > System menu >

Management submenu > WEB Security Settings).

Figure 44: Web Security Settings

2. Configure the parameters as required.

3. Click Submit to apply your changes.

4. To save the changes to flash memory, see 'Saving Configuration' on page 145.

5.8.1.5.5 Web Login Authentication using Smart Cards

You can enable Web login authentication using certificates from a third-party, Common Access Card (CAC) with user identification. When a user attempts to access the device through the Web browser (HTTPS), the device retrieves the Web user’s login username (and other inform at ion, if r equire d) f rom the CAC. The user attem pt ing to ac c es s the device is only required to provide the login password. Typicall y, a TLS connection is establishe d between the CAC and t he dev ice’s W eb inter fac e, and a R ADIUS s erver is im plem ented to authenticate the p assword with the username. T herefore, this feature implements a t wofactor authenticatio n - what the user has (i.e., the ph ysical card) and what the user k nows (i.e., the login password).

This feature is enabled using the EnableMgmtTwoFactorAuthentication parameter.

Note: For specific integration requirements for implementing a third-party smart

card for Web login authentication, contact your AudioCodes representative.

 To log in to the Web interface using CAC:

1. Insert the Common Access Card into the card reader.

2. Access the device using the following URL: https://<host name or IP address>; the

device prompts for a username and password.

3. Enter t he password only. As some br owsers require that the username be provi ded,

Version 6.6 85 Mediant 3000 with TP-6310 & TP-8410

it’s recommended to enter the username with an arbitrary value.

Page 86

Mediant 3000 with TP-6310 & TP-8410

5.8.1.5.6 Telnet/SSH Settings

 To enable Telnet:

1. Open the Telnet/SSH Settings page (Configuration tab > System menu >

Management > Telnet/SSH Settings).

Figure 45: Telnet/SSH Settings

2. To configure this page, refer to the Secure Telnet sub-section in the Product

Reference Manual.

3. Af ter conf igur in g/modifying the parameter f ields, c lick the Submit button. The changes

are entered into the system and the page is refreshed.

5.8.1.5.7 Web & Telnet Access List

 To configure the Web & Telnet Access List:

1. Open the Web & Telnet Access List page (Configuration tab > System menu >

Management > Web & Telnet Access List).

Figure 46: Web & Telnet Access List

2. T o add a new author ized IP address , in the Add a ne w Authorized I P Address f ield at

the bottom portion of the page, enter the required IP address and click Add New Entry.

User's Manual 86 Document #: LTRT-95211

Page 87

User's Manual 5. Configuration Using the Web Interface

3. To delete an authorized IP address, in the upper portion of the page, click a

checkmark into the checkbox of the required IP address row (checkmarks in more than one row is permissible) and click Delete Selected Addresses.

Notes:

• When all authorized IP addresses are deleted, this security feature becomes

disabled (all IP addresses are allowed to connect).

• When adding the first authorized IP address, you should add your own terminal's

IP address, in order to be able to connect to the Web interface. If entered incorrectly, reset the device to restore configuration from non-volatile memory and regain web access.

5.8.1.5.8 RADIUS Settings

 To configure the RADIUS Settings:

1. Open the RADIUS Settings pag e ( Configuration tab > System menu > Management

> RADIUS Settings).

Figure 47: RADIUS Settings

2. To configure this page, refer to the Radius Support sub-section in the Product

Reference Manual.

3. Af ter conf igur in g/modifying the parameter f ields, c lick the Submit button. The changes

are entered into the system and the page is refreshed.

Version 6.6 87 Mediant 3000 with TP-6310 & TP-8410

Page 88

Mediant 3000 with TP-6310 & TP-8410

5.8.1.5.9 SNMP

The following describes SNMP settings.

5.8.1.5.9.1 SNMP Community String

A SNMP Communit y String is a basic form of SNMP security. It desc ribes the association between an SNMP ser ver a nd cl ients T his s trin g is lik e a pas s word that controls the client's access to the server.

 To configure the SNMP Community Stri n g :

1. Open the SNMP Community String page (Configuration tab > System menu >

Management submenu > SNMP submenu > SNMP Community String).

Figure 48: SNMP Community Settings

2. T o add a Community Strin g, enter a name in the Co mmunity String fie ld in the "Read

Only" or "Read/W r ite" sect ion, ( de pen di ng o n th e ne ed ed Ac c ess Le ve l) an d then click the Submit button, to apply the settings.

Note: Up to five "Read Only" or "Read/Write" Community Strings are permitted.

3. T o delete a C om munity String, select the De let e chec k -box of the Community String to

be deleted and then click the Submit button, to apply the settings.

4. T o configure t his page, r efer to the SNMP I nterface D etails sub-section in the Product

Reference Manual.

5. Af ter conf igur in g/modifying the parameter f ields, c lick the Submit button. The changes

are entered into the system and the page is refreshed.

User's Manual 88 Document #: LTRT-95211

Page 89

User's Manual 5. Configuration Using the Web Interface

5.8.1.5.9.2 SNMP Trap Destinations

 To configure the SNMP Trap Destinations:

1. Open the SNMP Trap Destinations page (Configuration tab > System menu >

Management submenu > SNMP > SNMP Trap Destinations).

Figure 49: SNMP Trap Destinations

2. T o configure this page, refer to the Multiple SNM P Trap Destinations sub-section in

the Product Reference Manual.

3. Af ter conf igur in g/modifying the parameter f ields, c lick the Submit button. The changes

are entered into the system and the page is refreshed.

5.8.1.5.9.3 SNMP Trusted Managers

 To configure the SNMP Trusted Managers:

1. Open the SNMP Trusted Managers page (Configuration tab > System menu >

Management submenu > SNMP > SNMP Trusted Managers).

Figure 50: SNMP Trusted Managers

2. To configure this page, refer to the SNMP parameters sub-section in the Product

Reference Manual.

3. Af ter conf igur in g/modifying the parameter f ields, c lick the Submit button. The changes

are entered into the system and the page is refreshed.

Version 6.6 89 Mediant 3000 with TP-6310 & TP-8410

Page 90

Mediant 3000 with TP-6310 & TP-8410

5.8.1.5.9.4 SNMP V3 Users

 To configure the SNMP V3 Users:

1. Open the SNMP v3 Users page (Configuration tab > System menu > Management

> SNMP > SNMP V3 Users).

2. Click Add; the following dialog box appears:

3. T o configure this page, refer to the SNMP v3 USM Users sub-section in the Product

Reference Manual.

4. Af ter conf igur in g/modifying the parameter f ields, c lick the Submit button. The changes

are entered into the system and the page is refreshed.

Figure 51: SNMP V3 Users

User's Manual 90 Document #: LTRT-95211

Page 91

User's Manual 5. Configuration Using the Web Interface



5.8.2 VoIP

The following describes VoIP settings.

5.8.2.1 Network

Network - Contains a drop-down list with the following opti ons:

IP Settings - Refer to ''IP Settings'' on page 91 IP Routing Table - Refer to ''Routing Table'' on page 98 QoS Settings - Refer to 'QoS Settings' on page 99 SCTP Settings - Refer to ''SCTP Settings'' on page 100

5.8.2.1.1 IP Settings

Network Settings - Refer to Network Settings on page 100

Log on to the Web Interface. From the navigation tree on the left, open the IP Settings page (Configuration tab > VoIP menu > Network > IP Settings). The Multiple Interfac e Table page is displayed.

Figure 52: Multiple Interface Table - TP-6310

At this point, you can add rows to the table, edit ex isting rows and rem ove rows. In this page you can also change the VLAN Mode value and choose the ‘Native’ VLAN ID.

For TP-8410, you can select the value for Network Physical Separation.

Figure 53: Multiple Interface Table - TP-8410

Version 6.6 91 Mediant 3000 with TP-6310 & TP-8410

Page 92

Mediant 3000 with TP-6310 & TP-8410

At this point, you can add rows to the table, edit ex isting rows and remove rows. In this page you can also change the VLAN Mode va lue, choose the ‘Nati ve’ VLAN ID and se lect the value for Network Physical Separation.

Note: For Mediant 30 00 HA, the default IP Settings pag e is the Multiple Interface

Table. If the system was loaded without an Interf ace Table configuration in the ini file, the following message is displayed.

“For the system to operate in High Availability mode, ensure that at least one IP address has been defined."

 To configure the IP Settings:

1. Open the IP Settings page (Configuration tab > VoIP menu > Network > IP

Settings).

2. Follow the guidelines in the Product Reference Manual when configuring/modifying

the IP Settings, in the IP Settings page.

3. After configuring/modifying the parameter fields, click DONE. This will validate your

configuration.

4. For configuration guidelines, refer to the MGCP/MEGACO Product Reference Manual.

5.8.2.1.1.1 Multiple Interface Table

 To configure the Multiple Interface Table:

1. Click on the Multiple Interfac e Table link in the IP Settings page above; the following

message appears:

Figure 54: Multiple Interface Table Message

2. Confirm moving the configuration to the Multiple Interface Table, when clicking OK.

The following table appears:

Figure 55: Multiple Interface Table

User's Manual 92 Document #: LTRT-95211

Page 93

User's Manual 5. Configuration Using the Web Interface

You may now add, edit or delete an existing row using the Interface Table.

Note: It is highly recommended to click on Done after changing the Networking

configuration. This will tr igg er a va li dat ion pr oces s whi c h ensur es the co nfiguration is complete and valid.

5.8.2.1.1.2 Adding a New Interface Table Row

 To add a new Interface Table row:

1. To add a new Interface Table row , enter a row number in the field s hown below and

click the Add Index button.

Figure 56: Interface Table - Add Ro w

2. Enter the appropriate values in the available fields and click Apply.

3. Click Done for validation.

Note: When adding more than one network interface, VLANS must be enabled.

Please refer to the Product Reference Manual for more information and guidelines.

Version 6.6 93 Mediant 3000 with TP-6310 & TP-8410

Page 94

Mediant 3000 with TP-6310 & TP-8410

5.8.2.1.1.3 Editing an Interface Table Row

 To edit an existing Interface Table row:

1. Select the line to be edited by clicking the radio button on the appropriate row.

Figure 57: Interface Table - Edit Row

2. Click on the Edit button and make the necessary changes; click Apply.

3. Click Done for validation.

5.8.2.1.1.4 Deleting an Interface Table Row

 To delete an existing Interface Table row:

1. Open the IP Settings page (Configuration tab > VoIP m enu > Networ k submenu > I P

Settings).

2. Click on the radio button next to the ro w you wish to remove, and then click on the

Delete button. The table row is removed.

3. Click Done. The new configuration will be avai lable after sav ing the configur ation and

restarting the module.

4. Refer to the Interface Table Configuration Guidelines sub-section in the Product

Reference Manual to ensure a successful Interface Table configuration.

5.8.2.1.1.5 Changing VLAN Mode and ‘Native’ VLAN ID

The Interface Table web page allows the user to change the VLAN Mode (enable or disable VLANs), as well as to change the value of the ‘Native’ VLAN ID.

When configuring more than one network interface, VLANS must be enabled. In order to change one of thes e param et ers, ope n the Netw ork Settings->IP Settings page.

The VLAN Mode and ‘Native’ VLAN ID parameters are displayed below the Interface Table.

Note that any change of these parameter values will only be applied after burning the configuration and booting from Flash (not using a BOOTP/DHCP server).

Refer to the Interface Table Configuration Summary and Guidelines section in the MGCP/MEGACO Product Reference Manual, to ensure a successful configuration.

User's Manual 94 Document #: LTRT-95211

Page 95

User's Manual 5. Configuration Using the Web Interface

GBE

RTM

Redundant

RJ45/SFP

##2

##1

MEDIA

8410

Redundant

PEM #1

[

A -

Bottom]

GBE

GBEETHETH

RTM

Active

RJ45/SFP

PEM #2

[

B -

Top]

MEDIA

TP-

8410

Active

OAMCONTROL

RJ45RJ45

5.8.2.1.1.6 Using Network Physical Separation - TP-8410 Only

A Mediant 3000 with TP-8410 blades allows the user to have different physical port for each network type (Media, OAMP and Control). This feature eliminates the need for a VLAN aware switch in order to separat e the different traf fic of each networ k. The Mediant 3000 is basicall y implementing VLANs architec ture inside the syst em. This also means that user VLANs are not supported with th is feature. This section provides information on how to enable or disable this mode of operation.

Figure 58: Network Physical Separation in Mediant 3000 + TP-8410 Block Diagram

Each TP-8410 (Activ e and Redundant) blade has its own dedicated and redundant GbE (Gigabit Ethernet) port for Media traffic. This interface is directly available via the RTM module. The four Ethernet por ts are available via the PEM, but they are share d by the two blades. The active blade is connected to these ports.

Changing the mode of operation, with network physical separation or without, is done by setting the following parameter:

EnableNetworkPhysicalSeparation = 1

Note: Physical Network Separation is currently supported only for three interface

configurations. Users must configure an interface for each traff ic type (i.e., OAMP, Control and Media).

5.8.2.1.1.7 Switching into/out of Multiple IP’s and Network Physical Separation configuration.

When the Mediant 300 0 operates with multip le IP’s, it uses a sing le ph ysical Ether net port, located on its RT M, to connect to the networks. By using VLANs and an exter nal VLAN aware switch, the user c an s eparate th e diff erent traff ic types and co nnect each of them to

Version 6.6 95 Mediant 3000 with TP-6310 & TP-8410

their dedicated networ k . Moving into a Net w ork Physical Separation m ode means you have a dedicated Ethernet port f or each traffic type (Media, Control & OAMP). This al so means that after the blade is set to work in this mode, its OAMP traffic (which includes BootP/TFTP traff ic) will be sent/received to/fr om the dedicated port (on the PEM). This is not the port used in multiple IP’s & VLANs without network physical separation.

Page 96

Mediant 3000 with TP-6310 & TP-8410

5.8.2.1.1.8 Configuring System to Separate Physical Interfaces Scheme using *.ini file

 To prepare the Mediant 3000 to work with Multiple Interfaces and network

physical interfaces separation:

1. Prepare an ini file with your parameters and make sure that the

EnableNetworkPhysicalSeparation ini file parameter has been added and is set to "1".

2. Insert a single blade into the system. Each blade should be configured separately.

There is no importance to the order.

3. Make sure that your Ethernet cable is connected to the RTM of the inserted blade.

4. Us e Boot P/TFT P to loa d th e ini f ile you pre pared in th e firs t step t o the blade (Mu ltiple

Interfaces and physica l interfaces separation are availabl e when booting from flash), or use the Web interface to set the configuration.

5. Verify that the following message is sent to the Syslog: "Updating Flash to work in

Network Separation Mode in the next Boot".

6. Repeat steps 3 to 5 for the second blade.

7. Ins ert both blades into the system and connect a separate Ethernet cables for each

network. Remember that your OAMP applications are now available at the PEM module. Power up the system.

8. Verify that the following message is sent to the Syslog from each blade: "Board Is

Working in Network Separation Mode".

 To prepare the Mediant 3000 to work with Multiple Interfaces and without

Network Physical Interfaces Separation:

1. Prepare an ini file with your parameters and make sure that the ini file parameter

“EnableNetworkPhysicalSeparation” is added and set to 0.

2. Insert a single blade into the system. Each blade should be configured separately,

while the other blade is not inserted into the M3K. There is no importance to the order.

3. Make sure your Ethernet cable is connected to the PEM.

4. Us e Boo tP/T F T P to load th e IN I f ile you prepared in the firs t st ep to the b la de (Mu lti ple

Interfaces and VLANs are available when booting from flash), or use the Web interface to set the configuration.

5. Verify that the following mess age is s ent to the S ys log: "Upda ting F lash to work in Non

Network Separation Mode in the next Boot".

6. Repeat steps 4 to 5 with the second blade.

7. Ins ert both blades into the s ystem and connect two separ ate Ethernet cables, one for

each RTM. Remember that your OAMP applications are now available at the RTM module, as well as your Media and Call Control applications. Power up the system.

5.8.2.1.1.9 How to Switch to Multiple IP’s with Network Physical Separation

 To prepare the Mediant 3000 to work in Multiple IP’s Network with network

physical separation:

1. Log on to the Web Interface. From the naviga tion tr ee on th e lef t, click on the Net work

Settings - IP Settings link. The IP Settings page is displayed.

2. Configure exactly three interfaces, one for each traffic type, using the Multiple

Interface table. (Refer to 'IP Settings' on page 91 for more information.)

User's Manual 96 Document #: LTRT-95211

Page 97

User's Manual 5. Configuration Using the Web Interface

Figure 59: Configuring Three Interfaces

3. Set th e Network Physical Sep aration field to Enable. You will be prompted to change

the OAMP Ethernet cable to the PEM module.

Figure 60: Enable Network Physical Separation

4. Click on OK and t hen on the Do ne button to s et the ne w configurati on. A new pr ompt

will ask you to restart the system in order for the new configurations to take place.

5. Reset the blade using the Reset function on the Maintenance web page.

6. Change the OAMP Ethernet cable to the PEM’s relevant OAMP ports. Connect the

other Ethernet network ports to the system.

5.8.2.1.1.10 How to Switch out of Multiple IP’s with Network Physical Separation

 To prepare the Mediant 3000 to w ork in Multiple IP’s Network without network

physical separation:

1. Log on to the Web Interface. From the naviga tion tr ee on th e lef t, click on the Net work

Settings - IP Settings link. The IP Settings page is displayed.

2. Set the Network Physical Separation field to Disable.

3. Conf igure your new multiple interf aces using th e Multiple Inter face T able. (Refer to ' IP

Settings' on page 91 for more information.)

4. Clic k on OK and then on t he Done button to s et the ne w configuration. A new prom pt

will ask you to restart the system in order for the new configurations to take place.

Version 6.6 97 Mediant 3000 with TP-6310 & TP-8410

Page 98

Mediant 3000 with TP-6310 & TP-8410

Figure 61: Network Physical Separation Disabled

5. Reset the blade using the Reset function on the Maintenance web page.

6. Chan ge the OAMP Ether net cable to the RT M's relevant OAMP ports . Disconnec t the

other Ethernet network ports from the system.

5.8.2.1.2 IP Routing Table

The IP Routing Table page allows you to define up to 30 static IP routing rules for the device. These rules can be associated with a network interface (defined in the Multiple Interface table) and therefore, the routing dec ision is bas ed on the sour ce subnet/VL AN. If not associated with an IP interface, the static IP rule is based on destination IP addres s. Traffic destined to the subnet specified in the routing rule is re-directed to the defined gateway, reachable through the specified interface. Before sending an IP packet, the device searches this table for an entry that matches the requested destination host/network. If such an en tr y is found, t he de vice se nds the pac ket to t he indicat ed rou ter. If no explicit entry is found, the packet is sent to the default gateway.

 To configure static IP routing:

1. Open the IP Routing Table page (Configuration tab > VoIP menu > Network > IP

Routing Table).

Figure 62: IP Routing Table Pa g e

2. In the Add a new table entry table, add a new static routing rule according to the

parameters described in the table below.

3. Click Add New Entry; the new routing rule is added to the IP routing table.

User's Manual 98 Document #: LTRT-95211

Page 99

User's Manual 5. Configuration Using the Web Interface

4. To delete a routing rule from the table, select the 'Delete Row' check box

corresponding to the required routing rule, and then click Delete Selected Entries.

Notes:

• You can delete only inactive routing rules.

• The IP Routing table can also be configured using the table ini file parameter,

StaticRouteTable.

5.8.2.1.3 QoS Settings

This page allows the user t o configur e values f or the p riority fie ld of the VLAN tag, and th e DiffServ field of the I P He a der . Ref er to Q o S Parameters in the Product R ef er enc e Ma nua l, for more information.

In order to access this page, set the configuration mode on the Navigation Pane to Full.

 To configure the QoS Settings:

1. Open the QoS Settings page (Configuration tab > VoIP menu > Network > QoS

Settings).

Figure 63: QoS Settings

2. T o c onf igur e this page , r ef er to the Inf r astr uc ture ini F il e Parameters sub-sec tion in the

Product Reference Manual.

3. Af ter conf igur in g/modifying the parameter f ields, c lick the Submit button. The changes

are entered into the s ystem and the page is refreshed. Changes made to Class of Service parameters take effect immediately.

Version 6.6 99 Mediant 3000 with TP-6310 & TP-8410

Page 100

Mediant 3000 with TP-6310 & TP-8410

You can also configure this feature using the ini file parameter

5.8.2.1.4 SCTP Settings

 To configure the SCTP Settings:

1. Open the SCTP Settings page (Co nfigurat ion tab > V oIP menu > N etwork submenu >

SCTP Settings.

2. Use the appropriate tables in the Product Reference Manual as a reference when

configuring/modifying the SCTP Settings, in the SCTP Settings page.

3. Af ter conf igur in g/modifying the parameter f ields, c lick the Submit button. The changes

5.8.2.1.5 Network Settings

are entered into the system and the page is refreshed.

Figure 64: SCTP Settings

You can configure the device's handling of ICMP Redirect messages. These messages can either be rejected (ignored) or permitted.

Note:

DisableICMPRedirects (see 'Routing Parameters' in the Product Reference Manual.

 To configure the handling of ICMP Redirect messages:

1. Open the Network Settings page (Configuration tab > VoIP menu > Network

submenu > Network Settings).

Figure 65: Disabling ICMP R edirect in Network Settings Page

2. From the 'Disable ICMP Redirects' drop-down list, select the required option.

3. Click Submit to apply your changes.

User's Manual 100 Document #: LTRT-95211

AudioCodes Mediant 3000, TP-8410, TP-6310 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Table of Contents

User's Manual Notices

Trademarks

WEEE EU Directive

Customer Support

Related Documentation

Documentation Feedback

1 Introduction

1.1 General Features

1.2 High Availability

1.2.1 Mediant 3000 HA System with TP-6310

1.2.2 Mediant 3000 HA System with TP-8410

1.2.3 Private IP Address and Sy stem (Global) IP Add ress(es)

1.2.3.1 Private (Local) IP Address

1.2.3.2 System (Global) IP Address

1.3 Functional Block Diagram - TP-6310

1.4 Functional Block Diagram - TP-8410

2 Software Package

2.1 Installing the Software Package

2.1.1 Installing/Unzipping When Using a Windows™ Operating System

2.2 Software Directory Contents & Structure

3 Getting Started

3.1 Assigning the Device IP Address

3.1.1 Assigning an IP Address Using HTTP

3.1.2 Assigning an IP Address Using BootP

3.2 Assigning the IP Addresses for High Availability Mode

4 System Initialization P rocess

4.1 Boot Firmware & Operational Firmware

4.2 Startup Process

4.3 Configuration Parameters and Files

4.3.1 Initialization (ini) File

4.3.1.1 Paramet er Val ue St r uct u re

4.3.1.2.1 Table Structure Rules

4.3.1.2.2 Tables in the Uploaded ini File

4.3.2 Auxiliary F iles

4.3.3 Automatic Update Facility

4.4 Backup Copies of ini and Auxiliary Files

4.5 Upgrading Device Software

4.6 Software Upgrade Key

4.7 High Availability

4.7.1 Initializing the Mediant 3000 System

4.7.2 Device In itia liza tion Proc ess

4.7.3 Special System Speci fic Behavior

4.7.3.1 Rebooting the Blade

4.7.3.2 High Availability and Syslog

4.7.4 Actions upon Detecting Blade Failure

4.7.4.1 Failure in the Active Blade

4.7.4.2 Failure in the Redundant Blade

4.7.5 Hitless Software Upgrade

5 Configuration Using the Web Interface

5.1 Limiting the Web Interface to Read-Only Mode

5.2 Disabling the Web Interface

5.2.1 Encrypted HTTP Transport (HTTPS - SSL)

5.2.2 Limiting Web Access to a Predefined List of C lient IP Addresses

5.2.3 Managing Web Serv er Access Us ing a RADIUS Server

5.3 Initial Device Configuration using the Web Interface

5.4 Accessing the Web Interface

5.5 Using Internet Explorer to Access the Web Interface

5.6 Getting Acquainted with the Web Interface

5.6.1 Toolbar

5.6.2 Navigation Tree

5.6.2.1 Displaying Navigation Tree in Basic and Full View

5.6.2.2 Showing / Hiding the Navigation Pane

5.6.3 Working with Configuration Pages

5.6.3.1 Accessing Pages

5.6.3.2 Viewing Parameters

5.6.3.3 Displaying Basic and Advanced Parameters

5.6.3.4 Showing / Hiding Parameter Groups

5.6.3.5 Modifying Parameter Values

5.6.4 Saving Configuration Changes

5.6.5 Searching for Configuration Parameters

5.6.6 Working with Scenarios

5.6.6.1 Creating a Scenario

5.6.6.2 Editing a Scenario

5.6.6.3 Saving a Scenario to a PC

5.6.6.4 Loading a Scenario to the Device