Page 1
Mediant 2000, Mediant 1000 & TP-1610 H.323
User’s Manual
Version 4.6
Document #: LTRT-69903
Page 2
Notice
This document describes the release of the AudioCodes Mediant 2000 H.323 gateway, digital Mediant
1000 H.323 gateway and TP-1610 H.323 cPCI board.
Information contained in this document is believed to be accurate and reliable at the time of printing.
However, due to ongoing product improvements and revisions, AudioCodes cannot guarantee
accuracy of printed material after the Date Published nor can it accept responsibility for errors or
omissions. Updates to this document and other documents can be viewed by registered Technical
Support customers at www.audiocodes.com under Support / Product Documentation.
© Copyright 2005 AudioCodes Ltd. All rights reserved.
This document is subject to change without notice.
Date Published: Jul-23-2004 Date Printed: Jul-28-2005
Page 3
Mediant Series and TP-1610 H.323 User’s Manual Contents
Version 4.6 3 July 2005
Table of Contents
1 Overview.....................................................................................................................17
1.1 Introduction .....................................................................................................................................17
1.2 Mediant 2000 Overview..................................................................................................................17
1.3 TP-1610 Overview..........................................................................................................................18
1.4 Mediant 1000 Overview..................................................................................................................19
1.5 Mediant 2000 Features...................................................................................................................20
1.5.1 General Features ................................................................................................................20
1.5.2 PSTN-to-H.323 Interworking ...............................................................................................21
1.5.2.1 Supported Interworking Features..................................................................................21
1.5.3 H.323 Compatibility .............................................................................................................22
1.5.3.1 Gatekeeper Features ....................................................................................................22
1.5.3.2 Call Setup Features ......................................................................................................22
1.5.3.3 General H.323 Features ...............................................................................................23
2 Physical Description..................................................................................................25
2.1 Mediant 2000 Physical Description ................................................................................................25
2.1.1 The Mediant 2000 Chassis..................................................................................................26
2.1.1.1 Power Supply ................................................................................................................26
2.1.2 Optional CPU Board............................................................................................................26
2.2 TP-1610 Physical Description.........................................................................................................27
2.2.1 TP-1610 Front Panel LED Indicators ..................................................................................28
2.2.2 Rear Transition Module.......................................................................................................29
2.3 Mediant 1000 Physical Description ................................................................................................30
2.3.1 Mediant 1000 Front Panel...................................................................................................30
2.3.1.1 I/O Modules ...................................................................................................................31
2.3.1.2 CPU Module..................................................................................................................31
2.3.1.2.1 Dry Contact Connector (Labeled I and II) ....................................................................... 31
2.3.1.2.2 Audio IN/OUT ................................................................................................................. 32
2.3.1.2.3 Two 10/100 Base-TX Ethernet Ports (Labeled I and II) .................................................. 32
2.3.1.2.4 RS-232 Port (Labeled I0I0)............................................................................................. 32
2.3.1.2.5 Reset Button (Labeled //)................................................................................................ 32
2.3.1.3 Power Supply Module (Labeled 1 and 2)......................................................................32
2.3.1.4 Fan Tray Module ...........................................................................................................32
2.3.1.4.1 Replacing the Air Filter.................................................................................................... 33
2.3.1.5 Front Panel LEDs..........................................................................................................35
2.3.2 Mediant 1000 Rear Panel....................................................................................................36
2.3.3 Mediant 1000 Modules ........................................................................................................37
2.3.4 Partner Application Platform................................................................................................38
2.3.4.1 Connection Module (CM) ..............................................................................................38
2.3.4.2 iPMX Module.................................................................................................................38
2.3.4.3 HDMX Module...............................................................................................................40
3 Installation..................................................................................................................41
3.1 Installing the Mediant 2000.............................................................................................................41
3.1.1 Unpacking............................................................................................................................41
3.1.2 Package Contents ...............................................................................................................41
3.1.3 Mounting the Mediant 2000.................................................................................................42
3.1.3.1 Mounting the Mediant 2000 on a Desktop ....................................................................42
3.1.3.2 Installing the Mediant 2000 in a 19-inch Rack..............................................................42
3.1.4 Cabling the Mediant 2000 ...................................................................................................44
3.1.4.1 Connecting the E1/T1 Trunk Interfaces ........................................................................45
3.1.4.2 Installing the Ethernet Connection ................................................................................46
3.1.4.3 Connecting the RS-232 Port to Your PC ......................................................................46
3.1.4.4 Connecting the Power Supply.......................................................................................47
3.1.4.4.1 Connecting the AC Power Supply................................................................................... 47
3.1.4.4.2 Connecting the DC Power Supply .................................................................................. 47
3.2 Installing the TP-1610.....................................................................................................................49
3.2.1 Unpacking............................................................................................................................49
3.2.2 Package Contents ...............................................................................................................49
3.2.3 Installing the TP-1610 .........................................................................................................49
Page 4
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 4 Document #: LTRT-69903
3.2.3.1 Inserting Boards............................................................................................................50
3.2.3.2 Removing Boards..........................................................................................................50
3.2.4 Cabling the TP-1610 ...........................................................................................................50
3.3 Installing the Mediant 1000.............................................................................................................51
3.3.1 Unpacking............................................................................................................................51
3.3.2 Package Contents ...............................................................................................................51
3.3.3 Mounting the Mediant 1000.................................................................................................51
3.3.3.1 Mounting the Mediant 1000 on a Desktop ....................................................................51
3.3.3.2 Installing the Mediant 1000 in a 19-inch Rack..............................................................52
3.3.4 Cabling the Mediant 1000 ...................................................................................................53
3.3.4.1 Connecting the Mediant 1000 RS-232 Port to Your PC ...............................................54
3.3.4.2 Setting up a Dry Contact System..................................................................................54
3.3.4.3 Connecting the Audio IN/OUT Cable............................................................................55
4 Getting Started...........................................................................................................57
4.1 Configuration Concepts ..................................................................................................................57
4.2 Assigning the Mediant 2000 IP Address.........................................................................................58
4.2.1 Assigning an IP Address Using HTTP ................................................................................58
4.2.2 Assigning an IP Address Using BootP ................................................................................59
4.3 Configuring the Mediant 2000 Basic Parameters...........................................................................59
5 Web Management ......................................................................................................61
5.1 Computer Requirements.................................................................................................................61
5.2 Protection and Security Mechanisms .............................................................................................61
5.2.1 Dual Access Level Username and Password .....................................................................61
5.2.2 Limiting the Embedded Web Server to Read-Only Mode ...................................................62
5.2.3 Disabling the Embedded Web Server .................................................................................62
5.3 Accessing the Embedded Web Server...........................................................................................62
5.3.1 Using Internet Explorer to Access the Embedded Web Server ..........................................63
5.4 Getting Acquainted with the Web Interface ....................................................................................63
5.4.1 Main Menu Bar ....................................................................................................................64
5.4.2 Saving Changes ..................................................................................................................64
5.4.3 Entering Phone Numbers in Various Tables .......................................................................64
5.5 Protocol Management.....................................................................................................................65
5.5.1 Protocol Definition Parameters............................................................................................65
5.5.1.1 Coders...........................................................................................................................65
5.5.2 Advanced Parameters.........................................................................................................66
5.5.3 Number Manipulation Tables ..............................................................................................66
5.5.3.1 Dialing Plan Notation ....................................................................................................68
5.5.3.2 Numbering Plan and Type of Number ..........................................................................69
5.5.4 Configuring the Routing Tables...........................................................................................70
5.5.4.1 Tel to IP Routing Table .................................................................................................70
5.5.4.2 IP to Trunk Group Routing Table ..................................................................................72
5.5.4.3 Internal DNS Table........................................................................................................74
5.5.4.4 Reasons for Alternative Routing ...................................................................................75
5.5.5 Configuring the Profile Definitions.......................................................................................76
5.5.5.1 Coder Group Settings ...................................................................................................76
5.5.5.2 Tel Profile Settings ........................................................................................................77
5.5.5.3 IP Profile Settings..........................................................................................................78
5.5.6 Configuring the Registration Prefixes Table........................................................................80
5.5.7 Configuring the Trunk Group Table.....................................................................................82
5.5.8 Trunk Group Settings ..........................................................................................................83
5.6 Advanced Configuration .................................................................................................................85
5.6.1 Configuring the Network Settings........................................................................................85
5.6.1.1 Configuring the SNMP Managers Table .......................................................................85
5.6.1.2 Configuring the Web and Telnet Access List ................................................................86
5.6.1.3 Configuring the IP Routing Table..................................................................................86
5.6.1.4 Viewing the Ethernet Port Information ..........................................................................88
5.6.2 Configuring the Channel Settings........................................................................................88
5.6.3 Configuring the Trunk Settings............................................................................................89
5.6.4 Configuring the TDM Bus Settings......................................................................................91
5.6.5 Restoring and Backing Up the Gateway Configuration.......................................................92
5.6.6 Regional Settings ................................................................................................................93
Page 5
Mediant Series and TP-1610 H.323 User’s Manual Contents
Version 4.6 5 July 2005
5.6.7 Changing the Mediant 2000 Username and Password ......................................................94
5.7 Status & Diagnostic ........................................................................................................................95
5.7.1 Gateway Statistics...............................................................................................................95
5.7.1.1 IP Connectivity ..............................................................................................................95
5.7.1.2 Call Counters ................................................................................................................96
5.7.1.3 Call Routing Status .......................................................................................................98
5.7.2 Monitoring the Mediant 2000 Trunks & Channels...............................................................99
5.7.3 Activating the Internal Syslog Viewer................................................................................101
5.7.4 Device Information ............................................................................................................102
5.7.5 Front Panel View (Mediant 1000 Only) .............................................................................103
5.8 Software Update Menu.................................................................................................................104
5.8.1 Software Upgrade Wizard .................................................................................................104
5.8.2 Auxiliary Files ....................................................................................................................108
5.8.3 Updating the Software Upgrade Key.................................................................................109
5.9 Save Configuration .......................................................................................................................110
5.10 Resetting the Mediant 2000..........................................................................................................111
6 ini File Configuration of the Mediant 2000.............................................................113
6.1 Secured ini File .............................................................................................................................113
6.2 Modifying an ini File......................................................................................................................113
6.3 The ini File Content.......................................................................................................................114
6.4 The ini File Structure.....................................................................................................................114
6.4.1 The ini File Structure Rules ...............................................................................................114
6.5 The ini File Examples ...................................................................................................................115
6.6 Networking Parameters ................................................................................................................116
6.7 System Parameters ......................................................................................................................119
6.8 Web and Telnet Parameters.........................................................................................................123
6.9 RADIUS Parameters.....................................................................................................................125
6.10 SNMP Parameters........................................................................................................................126
6.11 H.323 Configuration Parameters ..................................................................................................128
6.12 ISDN and CAS Interworking-Related Parameters........................................................................138
6.13 Number Manipulation and Routing Parameters ...........................................................................142
6.14 E1/T1 Configuration Parameters ..................................................................................................149
6.15 Channel Parameters.....................................................................................................................154
6.16 Configuration Files Parameters ....................................................................................................158
7 Using BootP / DHCP................................................................................................159
7.1 BootP/DHCP Server Parameters .................................................................................................159
7.2 Using DHCP .................................................................................................................................159
7.3 Using BootP..................................................................................................................................160
7.3.1 Upgrading the Mediant 2000.............................................................................................160
7.3.2 Vendor Specific Information Field .....................................................................................161
8 Telephony Capabilities............................................................................................163
8.1 Working with H.450 Supplementary Services ..............................................................................163
8.1.1 Call Hold and Retrieve Features .......................................................................................163
8.1.2 Call Transfer......................................................................................................................163
8.1.3 Call Forward ......................................................................................................................164
8.1.4 Call Waiting .......................................................................................................................164
8.1.5 Name Identification............................................................................................................164
8.2 Configuring the DTMF Transport Types.......................................................................................165
8.2.1 Overview of In-Band DTMF Transport Types ...................................................................165
8.3 Fax & Modem Transport Modes ...................................................................................................166
8.3.1 Fax/Modem Settings .........................................................................................................166
8.3.2 Configuring Fax Relay Mode.............................................................................................166
8.3.3 Configuring Fax/Modem ByPass Mode.............................................................................166
8.3.4 Supporting V.34 Faxes......................................................................................................167
8.3.4.1 Using Bypass Mechanism for V.34 Fax Transmission ...............................................167
8.3.4.2 Using Relay Mode for both T.30 and V.34 Faxes.......................................................167
8.4 Redundant Gatekeeper Implementation.......................................................................................168
8.5 Mediant 2000 Registration with a Gatekeeper .............................................................................168
8.5.1 Registration with Prefixes..................................................................................................168
8.5.2 Registration with H.323-ID ................................................................................................169
Page 6
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 6 Document #: LTRT-69903
8.6 ThroughPacket™..........................................................................................................................169
8.7 Dynamic Jitter Buffer Operation....................................................................................................169
8.8 Configuring the Gateway’s Alternative Routing (based on Connectivity and QoS)......................170
8.8.1 Alternative Routing Mechanism.........................................................................................170
8.8.2 Determining the Availability of Destination IP Addresses .................................................171
8.8.3 PSTN Fallback as a Special Case of Alternative Routing.................................................171
8.8.4 Relevant Parameters.........................................................................................................171
8.9 Call Detail Report..........................................................................................................................172
8.10 Supported RADIUS Attributes ......................................................................................................173
8.10.1 RADIUS Server Messages................................................................................................174
8.11 Trunk to Trunk Routing Example..................................................................................................175
9 Networking Capabilities..........................................................................................177
9.1 Ethernet Interface Configuration...................................................................................................177
9.2 Ethernet Interface Redundancy....................................................................................................177
9.3 NAT (Network Address Translation) Support ...............................................................................178
9.4 Robust Reception of RTP Streams ..............................................................................................178
9.5 Multiple Routers Support ..............................................................................................................179
9.6 Simple Network Time Protocol Support........................................................................................179
10 Advanced PSTN Configuration...............................................................................181
10.1 Mediant 2000 Clock Settings ........................................................................................................181
10.2 ISDN Overlap Dialing....................................................................................................................181
10.3 Using ISDN NFAS ........................................................................................................................182
10.3.1 NFAS Interface ID .............................................................................................................183
10.3.2 Working with DMS-100 Switches ......................................................................................183
10.4 Redirect Number and Calling Name (Display)..............................................................................184
11 Advanced System Capabilities...............................................................................185
11.1 Restoring Networking Parameters to their Initial State.................................................................185
11.2 Establishing a Serial Communications Link with the Mediant 2000 .............................................185
11.3 Automatic Update Mechanism......................................................................................................186
11.4 Startup Process ............................................................................................................................188
11.5 Using Parameter Tables ...............................................................................................................190
11.5.1 Table Indices .....................................................................................................................190
11.5.2 Table Permissions .............................................................................................................191
11.5.3 Dynamic Tables vs. Static Tables .....................................................................................191
11.5.4 Secret Tables ....................................................................................................................191
11.5.5 Using the ini File to Configure Parameter Tables .............................................................192
11.5.5.1 Structure of Parameter Tables in the ini File ..............................................................192
11.6 Customizing the Mediant 2000 Web Interface..............................................................................194
11.6.1 Replacing the Main Corporate Logo .................................................................................194
11.6.1.1 Replacing the Main Corporate Logo with an Image File.............................................194
11.6.1.2 Replacing the Main Corporate Logo with a Text String ..............................................196
11.6.2 Replacing the Background Image File ..............................................................................196
11.6.3 Customizing the Product Name.........................................................................................197
11.6.3.1 Modifying ini File Parameters via the Web AdminPage..............................................198
11.7 Software Upgrade Key..................................................................................................................199
11.7.1 Backing up the Current Software Upgrade Key ................................................................199
11.7.2 Loading the Software Upgrade Key ..................................................................................199
11.7.2.1 Loading the Software Upgrade Key Using the Embedded Web Server.....................200
11.7.2.2 Loading the Software Upgrade Key Using BootP/TFTP.............................................201
11.7.3 Verifying that the Key was Successfully Loaded...............................................................201
11.7.4 Troubleshooting an Unsuccessful Loading of a Key .........................................................201
11.7.5 Abort Procedure ................................................................................................................201
12 Special Applications................................................................................................203
12.1 TDM Tunneling .............................................................................................................................203
12.1.1 Implementation ..................................................................................................................203
12.2 SS7 Tunneling ..............................................................................................................................205
12.2.1 MTP2 Tunneling Technology ............................................................................................206
12.2.2 SS7 Characteristics ...........................................................................................................206
12.2.3 SS7 Parameters ................................................................................................................207
Page 7
Mediant Series and TP-1610 H.323 User’s Manual Contents
Version 4.6 7 July 2005
12.2.4 SS7 Parameter Tables ......................................................................................................208
12.2.4.1 SIGTRAN Interface Groups ........................................................................................208
12.2.4.2 SIGTRAN Interface IDs...............................................................................................209
12.2.4.3 SS7 Signaling Link......................................................................................................210
12.2.5 SS7 MTP2 Tunneling ini File Example..............................................................................212
12.3 Answering Machine Detection (AMD)...........................................................................................216
12.3.1 Operation...........................................................................................................................216
12.3.1.1 Activating the Answering Machine Detection..............................................................216
12.3.1.2 Activation Acknowledgement......................................................................................217
12.3.1.3 Returned Detector’s Results .......................................................................................217
12.3.2 Relevant parameters .........................................................................................................218
13 Security ....................................................................................................................219
13.1 SSL/TLS........................................................................................................................................219
13.1.1 Embedded Web Server Configuration ..............................................................................219
13.1.1.1 Using the Secured Embedded Web Server................................................................219
13.1.2 Secured Telnet ..................................................................................................................220
13.1.3 Server Certificate Replacement ........................................................................................220
13.1.4 Client Certificates ..............................................................................................................221
13.2 RADIUS Login Authentication.......................................................................................................223
13.2.1 Setting Up a RADIUS Server ............................................................................................223
13.2.2 Configuring RADIUS Support............................................................................................224
13.3 Network Port Usage......................................................................................................................225
13.4 Recommended Practices..............................................................................................................226
13.5 Legal Notice..................................................................................................................................226
14 Diagnostics ..............................................................................................................227
14.1 Self-Testing...................................................................................................................................227
14.2 Syslog Support .............................................................................................................................227
14.2.1 Syslog Servers ..................................................................................................................228
14.2.2 Operation...........................................................................................................................228
15 Embedded Command Line Interface......................................................................229
15.1 Accessing the CLI.........................................................................................................................229
15.2 Using the CLI ................................................................................................................................230
15.2.1 Changing the Networking Parameters ..............................................................................231
16 SNMP-Based Management......................................................................................233
16.1 About SNMP .................................................................................................................................233
16.1.1 SNMP Message Standard.................................................................................................233
16.1.2 SNMP MIB Objects ...........................................................................................................234
16.1.3 SNMP Extensibility Feature...............................................................................................234
16.2 Carrier Grade Alarm System ........................................................................................................235
16.2.1 Active Alarm Table ............................................................................................................235
16.2.2 Alarm History .....................................................................................................................235
16.3 Cold Start Trap .............................................................................................................................235
16.4 Third-Party Performance Monitoring Measurements ...................................................................236
16.5 Supported MIBs ............................................................................................................................237
16.6 Traps.............................................................................................................................................238
16.7 SNMP Interface Details ................................................................................................................239
16.7.1 SNMP Community Names ................................................................................................239
16.7.1.1 Configuration of Community Strings via the ini File....................................................240
16.7.1.2 Configuration of Community Strings via SNMP ..........................................................240
16.7.2 Trusted Managers .............................................................................................................241
16.7.2.1 Configuration of Trusted Managers via ini File ...........................................................241
16.7.2.2 Configuration of Trusted Managers via SNMP ...........................................................241
16.7.3 SNMP Ports.......................................................................................................................242
16.7.4 Multiple SNMP Trap Destinations .....................................................................................242
16.7.4.1 Trap Manger Configuration via Host Name ................................................................242
16.7.4.2 Trap Managers Configuration via the ini File..............................................................243
16.7.4.3 Trap Mangers Configuration via SNMP ......................................................................244
16.8 SNMP Manager Backward Compatibility......................................................................................245
16.9 Dual Module Interface...................................................................................................................245
16.10 AudioCodes’ Element Management System................................................................................245
Page 8
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 8 Document #: LTRT-69903
17 Configuration Files ..................................................................................................247
17.1 Configuring the Call Progress Tones............................................................................................247
17.1.1 Format of the Call Progress Tones Section in the ini File.................................................247
17.2 Prerecorded Tones (PRT) File......................................................................................................249
17.2.1 PRT File Format ................................................................................................................249
17.3 Voice Prompts File........................................................................................................................250
17.4 CAS Protocol Configuration Files .................................................................................................251
18 Selected Technical Specifications .........................................................................253
18.1 General Specifications..................................................................................................................253
18.2 Mediant 2000 Specifications.........................................................................................................255
18.3 TP-1610 Specifications.................................................................................................................257
18.4 Mediant 1000 Specifications.........................................................................................................259
Appendix A Supplied H.323 Software Kit....................................................................261
Appendix B The BootP/TFTP Configuration Utility ....................................................263
B.1 When to Use the BootP/TFTP ......................................................................................................263
B.2 An Overview of BootP...................................................................................................................263
B.3 Key Features ................................................................................................................................263
B.4 Specifications................................................................................................................................264
B.5 Installation.....................................................................................................................................264
B.6 Loading the cmp File, Booting the Device....................................................................................264
B.7 BootP/TFTP Application User Interface........................................................................................265
B.8 Function Buttons on the Main Screen ..........................................................................................265
B.9 Log Window ..................................................................................................................................266
B.10 Setting the Preferences ................................................................................................................267
B.10.1 BootP Preferences ............................................................................................................267
B.10.2 TFTP Preferences .............................................................................................................268
B.11 Configuring the BootP Clients.......................................................................................................269
B.11.1 Adding Clients ...................................................................................................................269
B.11.2 Deleting Clients .................................................................................................................270
B.11.3 Editing Client Parameters..................................................................................................270
B.11.4 Testing the Client ..............................................................................................................270
B.11.5 Setting Client Parameters .................................................................................................271
B.11.6 Using Command Line Switches ........................................................................................272
B.12 Managing Client Templates ..........................................................................................................273
Appendix C RTP/RTCP Payload Types and Port Allocation......................................275
C.1 Packet Types Defined in RFC 3551.............................................................................................275
C.2 Defined Payload Types.................................................................................................................275
C.3 Default RTP/RTCP/T.38 Port Allocation.......................................................................................276
Appendix D Accessory Programs and Tools..............................................................277
D.1 TrunkPack Downloadable Conversion Utility................................................................................277
D.1.1 Converting a CPT ini File to a Binary dat File ...................................................................278
D.1.2 Creating a Loadable Voice Prompts File...........................................................................279
D.1.3 Creating a loadable CAS Protocol Table File....................................................................281
D.1.4 Encoding / Decoding an ini File.........................................................................................283
D.1.5 Creating a Loadable Prerecorded Tones File ...................................................................284
D.2 PSTN Trace Utility ........................................................................................................................286
D.2.1 Operation...........................................................................................................................286
Appendix E SNMP Traps...............................................................................................289
E.1 Alarm Traps ..................................................................................................................................289
E.1.1 Component: Board#<n> ....................................................................................................289
E.1.2 Component: AlarmManager#0 ..........................................................................................292
E.1.3 Component: EthernetLink#0..............................................................................................292
E.1.4 Component: SS7#0 ...........................................................................................................293
E.1.5 Log Traps (Notifications) ...................................................................................................294
E.1.6 Other Traps .......................................................................................................................294
E.1.7 Trap Varbinds....................................................................................................................295
Page 9
Mediant Series and TP-1610 H.323 User’s Manual Contents
Version 4.6 9 July 2005
Appendix F Regulatory Information............................................................................297
F.1 Mediant 2000 ................................................................................................................................297
F.2 TP-1610 ........................................................................................................................................299
Page 10
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 10 Document #: LTRT-69903
List of Figures
Figure 1-1: Typical Mediant 2000 Gateway Application...................................................................................20
Figure 2-1: Mediant 2000 Front View...............................................................................................................25
Figure 2-2: Front and Upper View of the TP-1610 cPCI Board........................................................................27
Figure 2-3: Rear Panel with two 50-pin Connectors for 16 Trunks ..................................................................29
Figure 2-4: Rear Panel with 8 RJ-48c Connectors for 8 Trunks ......................................................................29
Figure 2-5: Mediant 1000 Front View & CPU Enlargement..............................................................................30
Figure 2-6: Mediant 1000 Front Layout............................................................................................................31
Figure 2-7: Slightly Extracted Fan Try Unit.......................................................................................................33
Figure 2-8: Fan Try with Filter Extracted..........................................................................................................34
Figure 2-9: Location of Front Panel LEDs........................................................................................................35
Figure 2-10: Mediant 1000 Rear Connectors...................................................................................................36
Figure 2-11: Front View of the CM Module.......................................................................................................38
Figure 2-12: iPMX Module................................................................................................................................39
Figure 2-13: RJ-11 Connector Used for Night Bell...........................................................................................39
Figure 2-14: RJ-11 Connector Used for Paging...............................................................................................39
Figure 2-15: HDMX Module..............................................................................................................................40
Figure 3-1: 19-inch Rack & Desktop Accessories............................................................................................42
Figure 3-2: Mediant 2000 Front View with 19-inch Rack Mount Brackets .......................................................43
Figure 3-3: Mediant 2000 Rear Panel Cabling (16 Trunks, Dual AC Power)...................................................44
Figure 3-4: Mediant 2000 Rear Panel Cabling (8 Trunks, DC Power))............................................................44
Figure 3-5: 50-pin Female Telco Board-Mounted Connector...........................................................................45
Figure 3-6: Pinout of RJ-48c Trunk Connectors...............................................................................................46
Figure 3-7: Pinout of RJ-45 Connectors...........................................................................................................46
Figure 3-8: RS-232 Cable Wiring .....................................................................................................................46
Figure 3-9: DC Terminal Block Screw Connector ............................................................................................47
Figure 3-10: DC Terminal Block Crimp Connector...........................................................................................48
Figure 3-11: Pinout of the RJ-48c Trunk Connectors.......................................................................................53
Figure 3-12: RJ-45 Ethernet Connector Pinout................................................................................................54
Figure 3-13: Supplied RS-232 Cable................................................................................................................54
Figure 3-14: Dry Contact Wires’ Mate ..............................................................................................................54
Figure 3-15: Audio Cable and IN/OUT RCA Connectors.................................................................................55
Figure 4-1: Mediant 2000 Quick Setup Screen ................................................................................................59
Figure 5-1: Embedded Web Server Login Screen ...........................................................................................62
Figure 5-2: Mediant 2000 Web Interface..........................................................................................................63
Figure 5-3: Coders Screen ...............................................................................................................................65
Figure 5-4: Source Phone Number Manipulation Table for TelÆIP Calls........................................................67
Figure 5-5: Tel to IP Routing Table Screen......................................................................................................71
Figure 5-6: IP to Trunk Group Routing Table...................................................................................................73
Figure 5-7: Internal DNS Table Screen............................................................................................................74
Figure 5-8: Reasons for Alternative Routing Screen........................................................................................75
Figure 5-9: Coder Group Settings Screen........................................................................................................76
Figure 5-10: Tel Profile Settings Screen...........................................................................................................77
Figure 5-11: IP Profile Settings Screen ............................................................................................................78
Figure 5-12: Registration Prefixes Table Screen .............................................................................................80
Figure 5-13: Trunk Group Table Screen...........................................................................................................82
Figure 5-14: Trunk Group Settings Screen.......................................................................................................83
Figure 5-15: SNMP Managers Table Screen ...................................................................................................85
Figure 5-16: Web & Telnet Access List Screen................................................................................................86
Figure 5-17: Ethernet Port Information Screen ................................................................................................88
Figure 5-18: E1/T1 Trunk Settings Screen.......................................................................................................89
Figure 5-19: TDM Bus Settings Screen............................................................................................................91
Figure 5-20: Configuration File Screen.............................................................................................................92
Figure 5-21: Regional Settings Screen.............................................................................................................93
Figure 5-22: Change Password Screen ...........................................................................................................94
Figure 5-23: IP Connectivity Screen.................................................................................................................95
Figure 5-24: TelÆIP Call Counters Screen......................................................................................................97
Figure 5-25: Call Routing Status Screen..........................................................................................................98
Figure 5-26: Mediant 2000 Trunk & Channel Status Screen............................................................................99
Figure 5-27: Trunk and Channel Status Color Indicator Keys..........................................................................99
Page 11
Mediant Series and TP-1610 H.323 User’s Manual Contents
Version 4.6 11 July 2005
Figure 5-28: Channel Status Details Screen..................................................................................................100
Figure 5-29: Message Log Screen .................................................................................................................101
Figure 5-30: Device Information Screen.........................................................................................................102
Figure 5-31: Mediant 1000 Front Panel View Screen ....................................................................................103
Figure 5-32: Start Software Upgrade Screen.................................................................................................104
Figure 5-33: Load a cmp File Screen.............................................................................................................105
Figure 5-34: cmp File Successfully Loaded into the Mediant 2000 Notification.............................................105
Figure 5-35: Load an ini File Screen ..............................................................................................................106
Figure 5-36: Load a CPT File Screen.............................................................................................................107
Figure 5-37: FINISH Screen...........................................................................................................................107
Figure 5-38: ‘End Process’ Screen.................................................................................................................108
Figure 5-39: Auxiliary Files Screen.................................................................................................................109
Figure 5-40: Save Configuration Screen........................................................................................................110
Figure 5-41: Reset Screen .............................................................................................................................111
Figure 6-1: ini File Structure ...........................................................................................................................114
Figure 6-2: H.323 ini File Example.................................................................................................................115
Figure 8-1: Accounting Example ....................................................................................................................174
Figure 9-1: NAT Functioning ..........................................................................................................................178
Figure 11-1: RS-232 Status and Error Messages ..........................................................................................186
Figure 11-2: Example of an ini File Activating the Automatic Update Mechanism.........................................187
Figure 11-3: Mediant 2000 Startup Process...................................................................................................189
Figure 11-4: Structure of a Parameter Table in the ini File ............................................................................192
Figure 11-5: User-Customizable Web Interface Title Bar...............................................................................194
Figure 11-6: Customized Web Interface Title Bar ..........................................................................................194
Figure 11-7: Image Download Screen............................................................................................................195
Figure 11-8: INI Parameters Screen...............................................................................................................198
Figure 11-9: Software Upgrade Key Screen ..................................................................................................200
Figure 11-10: Example of a Software Upgrade Key ini File Containing Multiple S/N Lines...........................201
Figure 12-1: ini File Example for TDM Tunneling (Originating Side)..............................................................204
Figure 12-2: ini File Example for TDM Tunneling (Terminating Side)............................................................204
Figure 12-3: M2UA Architecture.....................................................................................................................205
Figure 12-4: M2TN Architecture .....................................................................................................................205
Figure 12-5: Protocol Architecture for MTP2 Tunneling.................................................................................206
Figure 12-6: SS7 MTP2 Tunneling ini File Example - MGC...........................................................................212
Figure 12-7: SS7 MTP2 Tunneling ini File Example - SG..............................................................................214
Figure 12-8: Answering Machine Detection, Basic Call Scenario..................................................................216
Figure 13-1: Example of a Host File...............................................................................................................220
Figure 13-2: Certificate Signing Request Screen...........................................................................................220
Figure 13-3: Example of a Base64-Encoded X.509 Certificate......................................................................221
Figure 13-4: Example of the File clients.conf (FreeRADIUS Client Configuration)........................................223
Figure 13-5: Example of a User Configuration File for FreeRADIUS Using a Plain-Text Password .............223
Figure 15-1: Embedded Web Server CLI Screen...........................................................................................229
Figure 16-1: Example of Entries in a Device ini file Regarding SNMP...........................................................243
Figure 17-1: Call Progress Tone Types..........................................................................................................248
Figure 17-2: Defining a Dial Tone Example....................................................................................................249
Figure B-1: Main Screen.................................................................................................................................265
Figure B-2: Reset Screen ...............................................................................................................................265
Figure B-3: Preferences Screen .....................................................................................................................267
Figure B-4: Client Configuration Screen.........................................................................................................269
Figure B-5: Templates Screen........................................................................................................................273
Figure D-1: TrunkPack Downloadable Conversion Utility Opening Screen ...................................................277
Figure D-2: Call Progress Tones Conversion Screen ....................................................................................278
Figure D-3: Voice Prompts Screen.................................................................................................................279
Figure D-4: File Data Window ........................................................................................................................280
Figure D-5: Call Associated Signaling (CAS) Screen.....................................................................................281
Figure D-6: Encode/Decode ini File(s) Screen...............................................................................................283
Figure D-7: Prerecorded Tones Screen .........................................................................................................284
Figure D-8: File Data Window ........................................................................................................................285
Figure D-9: Trunk Traces ...............................................................................................................................287
Figure D-10: UDP2File Utility .........................................................................................................................287
Page 12
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 12 Document #: LTRT-69903
List of Tables
Table 2-1: Mediant 2000 Front View Component Descriptions........................................................................25
Table 2-2: Chassis LED Indicators...................................................................................................................26
Table 2-3: Front and Upper View of the TP-1610 cPCI Board Component Descriptions................................27
Table 2-4: Status LED Indicators......................................................................................................................28
Table 2-5: E1/T1 Trunk Status LED Indicators.................................................................................................28
Table 2-6: Ethernet LED Indicators ..................................................................................................................28
Table 2-7: cPCI LED Indicators........................................................................................................................28
Table 2-8: Rear Panel with two 50-pin Connectors for 16 Trunks Component Descriptions...........................29
Table 2-9: Rear Panel with 8 RJ-48c Connectors for 8 Trunks Component Descriptions...............................29
Table 2-10: Mediant 1000 Front View Component Descriptions (continues on pages 30 to 31).....................30
Table 2-11: Functionality of the CPU Module LEDs.........................................................................................35
Table 2-12: Functionality of the I/O Modules LEDs..........................................................................................35
Table 2-13: Functionality of the Power Supply Module LEDs..........................................................................35
Table 2-14: Mediant 1000 Rear Connectors Component Descriptions............................................................36
Table 2-15: Extractable Mediant 1000 Modules...............................................................................................37
Table 2-16: CM Module Component Descriptions ...........................................................................................38
Table 2-17: iPMX Module Component Descriptions ........................................................................................39
Table 3-1: Mediant 2000 Rear Panel Cabling (16 Trunks, Dual AC Power) Component Descriptions ...........44
Table 3-2: Mediant 2000 Rear Panel Cabling (8 Trunks, DC Power) Component Descriptions......................44
Table 3-3: E1/T1 Connections on each 50-pin Telco Connector .....................................................................45
Table 3-4: Dry Contact Wires’ Mate Component Descriptions.........................................................................54
Table 3-5: Audio Levels....................................................................................................................................55
Table 4-1: Default Networking Parameters ......................................................................................................57
Table 5-1: Number Manipulation Parameters ..................................................................................................67
Table 5-2: NPI/TON Values for ISDN ETSI......................................................................................................69
Table 5-3: Tel to IP Routing Table....................................................................................................................71
Table 5-4: IP to Trunk Group Routing Table ....................................................................................................73
Table 5-5: Registration Prefixes Table .............................................................................................................81
Table 5-6: Trunk Group Table ..........................................................................................................................82
Table 5-7: Channel Select Modes ....................................................................................................................84
Table 5-8: IP Routing Table Column Description.............................................................................................87
Table 5-9: Ethernet Port Information Parameters ............................................................................................88
Table 5-10: Trunks Status Color Indicator Keys...............................................................................................90
Table 5-11: IP Connectivity Parameters...........................................................................................................96
Table 5-12: Call Counters Description (continues on pages 98 to 99).............................................................97
Table 5-13: Call Routing Status Parameters....................................................................................................98
Table 5-14: Auxiliary Files Descriptions .........................................................................................................108
Table 6-1: Networking Parameters (continues on pages 117 to 119)............................................................116
Table 6-2: System Parameters (continues on pages 120 to 123)..................................................................119
Table 6-3: Web and Telnet Parameters (continues on pages 124 to 125) ....................................................123
Table 6-4: RADIUS Parameter.......................................................................................................................125
Table 6-5: SNMP Parameter (continues on pages 127 to 128) .....................................................................126
Table 6-6: H.323 Configuration Parameters (continues on pages 129 to 139)..............................................128
Table 6-7: ISDN and CAS Interworking-Related Parameters (continues on pages 140 to 143) ...................138
Table 6-8: Number Manipulation and Routing Parameters (continues on pages 144 to 150).......................142
Table 6-9: E1/T1 Configuration Parameters (continues on pages 151 to 155)..............................................149
Table 6-10: Channel Parameters (continues on pages 156 to 159) ..............................................................154
Table 6-11: Configuration File Parameters.....................................................................................................158
Table 7-1: Vendor Specific Information Field .................................................................................................161
Table 7-2: Structure of the Vendor Specific Information Field .......................................................................161
Table 8-1: Supported CDR Fields ..................................................................................................................172
Table 8-2: Supported RADIUS Attributes (continues on pages 175 to 176)..................................................173
Table 10-1: Calling Name (Display)................................................................................................................184
Table 10-2: Redirect Number .........................................................................................................................184
Table 11-1: Example of Parameter Table - Remote Management Connections ...........................................190
Table 11-2: Example of Parameter Table - Port-to-Port Connections ...........................................................190
Table 11-3: Customizable Logo ini File Parameters ......................................................................................196
Table 11-4: Web Appearance Customizable ini File Parameters ..................................................................196
Table 11-5: Customizable Logo ini File Parameters ......................................................................................197
Page 13
Mediant Series and TP-1610 H.323 User’s Manual Contents
Version 4.6 13 July 2005
Table 11-6: Web Appearance Customizable ini File Parameters ..................................................................197
Table 12-1: SS7 Parameters (continues on pages 209 to 210).....................................................................207
Table 12-2: SIGTRAN Interface Groups (continues on pages 210 to 211)....................................................208
Table 12-3: SIGTRAN Interface IDs...............................................................................................................209
Table 12-4: SS7 Signaling Link (continues on pages 212 to 213) .................................................................210
Table 12-5: Structure of the ‘data’ Element of the Non-Standard Data Structure..........................................217
Table 12-6: Possible Detection Results..........................................................................................................217
Table 13-1: Default TCP/UDP Network Port Numbers...................................................................................225
Table 15-1: /CONFiguration Folder ................................................................................................................230
Table 15-2: /MGmt/FAult Folder.....................................................................................................................230
Table 15-3: /IPNetworking/Ping Folder...........................................................................................................230
Table 15-4: /TPApp Folder .............................................................................................................................230
Table 15-5: /BSP/EXCeption Folder...............................................................................................................230
Table 18-1: General Selected Technical Specifications (continues on pages 255 to 256)............................253
Table 18-2: Mediant 2000 Selected Technical Specifications (continues on pages 257 to 258)...................255
Table 18-3: TP-1610 Selected Technical Specifications (continues on pages 259 to 260)...........................257
Table 18-4: Mediant 1000 Selected Technical Specifications........................................................................259
Table A-1: Supplied Software Kit....................................................................................................................261
Table B-1: Command Line Switch Descriptions .............................................................................................272
Table C-1: Packet Types Defined in RFC 3551 .............................................................................................275
Table C-2: Defined Payload Types.................................................................................................................275
Table C-3: Default RTP/RTCP/T.38 Port Allocation.......................................................................................276
Table E-1: acBoardFatalError Alarm Trap......................................................................................................289
Table E-2: acBoardConfigurationError Alarm Trap ........................................................................................289
Table E-3: acBoardTemperatureAlarm Alarm Trap........................................................................................290
Table E-4: acBoardEvResettingBoard Alarm Trap.........................................................................................290
Table E-5: acFeatureKeyError Alarm Trap.....................................................................................................290
Table E-6: acBoardCallResourcesAlarm Alarm Trap.....................................................................................291
Table E-7: acBoardControllerFailureAlarm Alarm Trap..................................................................................291
Table E-8: acBoardOverloadAlarm Alarm Trap..............................................................................................292
Table E-9: acActiveAlarmTableOverflow Alarm Trap.....................................................................................292
Table E-10: acBoardEthernetLinkAlarm Alarm Trap ......................................................................................292
Table F-11: acSS7LinkStateChangeAlarm Trap ............................................................................................293
Table F-12: acSS7LinkCongestionStateChangeAlarm Trap..........................................................................293
Table E-13: acPerformanceMonitoringThresholdCrossing Log Trap.............................................................294
Table E-14: coldStart Trap .............................................................................................................................294
Table E-15: authenticationFailure Trap ..........................................................................................................295
Table E-16: acBoardEvBoardStarted Trap.....................................................................................................295
Page 14
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 14 Document #: LTRT-69903
Reader's Notes
Page 15
Mediant Series and TP-1610 H.323 User’s Manual General
Version 4.6 15 July 2005
Tip: When viewing this manual on CD, Web site or on any other electronic copy,
all cross-references are hyperlinked. Click on the page or section numbers
(shown in blue) to reach the individual cross-referenced item directly. To
return back to the point from where you accessed the cross-reference, press
the ALT and ◄ keys.
Trademarks
AC logo, Ardito, AudioCoded, AudioCodes, AudioCodes logo, IPmedia, Mediant, MediaPack, MPMLQ, NetCoder, Stretto, TrunkPack, VoicePacketizer and VoIPerfect, are trademarks or
registered trademarks of AudioCodes Limited. All other products or trademarks are property of
their respective owners.
Customer Support
Customer technical support and service are provided by AudioCodes’ Distributors, Partners, and
Resellers from whom the product was purchased. For Customer support for products purchased
directly from AudioCodes, contact support@audiocodes.com
.
Abbreviations and Terminology
Each abbreviation, unless widely used, is spelled out in full when first used. Only industrystandard terms are used throughout this manual. Hexadecimal notation is indicated by 0x
preceding the number.
Related Documentation
Document # Manual Name
LTRT-696xx (e.g., LTRT-69601) Mediant Series & TP-1610 H.323 Digital Gateways Release Notes
LTRT-701xx Mediant 2000 Fast Track Installation Guide
LTRT-683xx Digital Mediant 1000 Fast Track Installation Guide
Warning: The Mediant 2000 and Mediant 1000 are supplied as sealed units and
must only be serviced by qualified service personnel.
Note: Where ‘network’ appears in this manual, it means Local Area Network (LAN),
Wide Area Network (WAN), etc. accessed via the gateway’s Ethernet
interface.
Page 16
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 16 Document #: LTRT-69903
Reader's Notes
Page 17
Mediant Series and TP-1610 H.323 User’s Manual 1. Overview
Version 4.6 17 July 2005
1 Overview
1.1 Introduction
This document provides you with the information on installation, configuration and operation of
the Mediant 2000 H.323 gateway, digital Mediant 1000 H.323 gateway and TP-1610 H.323 cPCI
board. As these products have similar functionality (with the exception of their physical layout and
the number of trunks), they are collectively referred to in the manual (except for in hardwarerelated sections) as the Mediant 2000.
1.2 Mediant 2000 Overview
The Mediant 2000 H.323 gateway enables voice, fax, and data traffic to be sent over the same IP
network. The Mediant 2000 Voice over IP (VoIP) gateway provides excellent voice quality and
optimized packet voice streaming over IP networks.
The Mediant 2000 uses the award-winning, field-proven Digital Signal Processing (DSP) voice
compression technology used in other TrunkPack
TM
series products.
The Mediant 2000 incorporates 1, 2, 4, 8 or 16 E1 or T1 spans for connection, directly to Public
Switched Telephone Network (PSTN) / Private Branch Exchange (PBX) telephony trunks, and
includes one or two 10/100 Base-TX Ethernet ports for connection to the network.
The Mediant 2000 supports up to 480 simultaneous VoIP or Fax over IP (FoIP) calls, supporting
various Integrated Services Digital Network (ISDN) Primary Rate Interface (PRI) protocols such
as EuroISDN, North American NI2, Lucent™ 4/5ESS, Nortel
™
DMS100 and others. In addition, it
supports different variants of Channel Associated Signaling (CAS) protocols for E1 and T1 spans,
including MFC R2, E&M immediate start, E&M delay dial/start, loop start and ground start.
The Mediant 2000 gateway, best suited for large and medium-sized VoIP applications, is a
compact device, comprising a 19-inch 1U chassis with optional dual AC or single DC power
supplies.
The deployment architecture can include several Mediant 2000 gateways in branch or
departmental offices, connected to local PBXs. Call routing is performed by the gateways
themselves or by Gatekeeper(s).
The Mediant 2000 gateway enables users to make low cost long distance or international
telephone/fax calls between distributed company offices, using their existing telephones/fax.
These calls are routed over the existing network ensuring that voice traffic uses minimum
bandwidth.
The Mediant 2000 can be controlled over the network using H.323 (ITU-T) VoIP signaling and
control protocol, which enables the deployment of Voice over Packet solutions in environments
where the enterprise PBX is connected to a VoIP network using the Mediant 2000 as a Trunking
media gateway. This provides the enterprise the ability to transmit voice and telephony signals
over a packet network. The Mediant 2000 can be set up to route calls independently, or
optionally, it can be controlled by an H.323 compliant Gatekeeper that performs the routing of the
calls as well as many other functions.
Note: The Mediant 2000 is offered as a 1-module (1-8 spans) or 2-module (for 16
spans only) platform. The latter configuration supports two TrunkPack
modules, each having its own IP address. Configuration instructions in this
document relate to the Mediant 2000 as a 1-module platform and must be
repeated for the second module as well.
Page 18
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 18 Document #: LTRT-69903
1.3 TP-1610 Overview
The TP-1610 cPCI VoIP media gateway board, based on dual TPM-1100 PMC Modules, is a
complete H.323-compliant ‘two media gateways on a board’, delivering cost-effective solution in a
convenient cPCI form-factor.
The TP-1610 is an ideal solution for H.323 trunking gateways and integrated media gateways for
IP-PBXs and all-in-one communication servers. The board is designed for enterprise or carrier
applications. The TP-1610 provides up to 480 simultaneous ports for voice, fax or data for VoIP
media gateway applications providing excellent voice quality and optimized packet voice
streaming over IP networks. Employing H.323 as a control protocol, the TP-1610 enables
vendors and System Integrators (SIs) short time-to-market and reliable cost-effective deployment
of next-generation networks.
The TP-1610 matches the density requirements for small to medium locations, while meeting
Network Service Providers' (NSP) demands for scalability. The TP-1610, scales from no trunk
spans to 16 E1/T1/J1 spans in a single cPCI slot and provides an excellent gateway solution for
enterprise applications as well as carrier locations.
One or two packet processors (depending on the board's capacity) handle packet-streaming
functions through two, redundant integral 10/100 Base-TX interfaces. Each processor implements
the industry-standard RTP/RTCP packet-streaming protocol, advanced adaptive jitter buffer
management, and T.38 fax relay over IP.
The TP-1610 supports various ISDN PRI protocols such as EuroISDN, North American NI2,
Lucent™ 4/5ESS, Nortel™ DMS100 and others. In addition, it supports different variants of CAS
protocols for E1 and T1 spans, including MFC R2, E&M immediate start, E&M delay dial / start,
loop start and ground start.
The TP-1610 enables the deployment of ‘Voice over Packet’ solutions in environments where
access is enabled to PSTN subscribers by using a trunking media gateway. This provides the
ability to transmit voice and telephony signals between a packet network and a TDM network.
Routing of the calls from the PSTN to a H.323 service node (e.g., Call Center) is performed by
the TP-1610 internal routing feature or by a Gatekeeper.
Enabling accelerated design cycles with higher density and reduced costs, the TP-1610 is an
ideal building block for scalable, reliable VoIP solutions. With the TP-1610’s comprehensive
feature set, customers can quickly design a wide range of solutions for PSTN and VoIP networks.
Note: The TP-1610 is offered as a 1-module (up to 240 channels or 8 trunk spans)
or 2-module (for 480 channels or 16 trunk spans only) platform. The latter
configuration supports two TrunkPack modules, each having its own IP
address. Configuration instructions in this document relate to the TP-1610 as
a 1-module platform and must be repeated for the second module as well.
Page 19
Mediant Series and TP-1610 H.323 User’s Manual 1. Overview
Version 4.6 19 July 2005
1.4 Mediant 1000 Overview
The Mediant 1000 is a cost-effective, converged wireline VoIP media gateway utilizing cutting
edge technology. Intelligently packaged in a stackable 1U chassis, it is designed to interface
between TDM & IP networks as a Customer Premise(s) Equipment (CPE) device. Incorporating
innovative Voice over Packet technology, the Mediant 1000 enables rapid time-to-market and
reliable cost-effective deployment of next-generation networks.
The Mediant 1000 provides superior voice technology for connecting legacy telephone and PBX
systems to IP networks, as well as seamless connection of the IP-PBX to the PSTN. In addition to
operating as a pure media gateway, the Mediant 1000 can also host partner applications and
serve as an IP-PBX platform. The Mediant 1000 is fully interoperable with multiple vendor
gateways, softswitches, gatekeepers, proxy servers, IP phones, session border controllers and
firewalls.
The Mediant 1000 matches the density requirements for smaller locations while meeting service
providers' demands for scalability. The compact Mediant 1000 modular gateway is extremely
scalable and supports multiples of 1, 2, or 4 E1/T1/J1 spans.
The Mediant 1000 can support a variety of telephony interfaces. It contains up to 4 digital
interface modules each with an RJ-48 port. The digital module can be configured as regular
E1/T1/J1 interfaces, and with up to 1 or 2 paired spans acting as life-line telephone interfaces for
switching to the PSTN in case of power failure or network problems.
The Mediant 1000 has enhanced hardware and software capabilities to ease its installation and to
help maintain voice quality. If the measured voice quality falls beneath a pre-configured value, or
the path to the destination is disconnected, the Mediant 1000 can assure voice connectivity by
falling back to the PSTN. In the event of network problems or power failures, calls can be routed
back to the PSTN without requiring routing modifications in the PBX. Further reliability is provided
by dual Ethernet ports and optional dual AC power supply.
The Mediant 1000 extends its flexibility with additional deployment options. The open platform on
the Mediant 1000 offers partners the option to host their own applications (e.g., IP-PBX or call
center application) using a powerful, low-power consumption processor and hard disks to provide
a complete solution within the Mediant 1000 chassis.
The Mediant 1000 supports various ISDN PRI protocols such as EuroISDN, North American NI2,
Lucent™ 4/5ESS, Nortel™ DMS100 and others. In addition, it supports different variants of CAS
protocols for E1 and T1 spans, including MFC R2, E&M immediate start, E&M delay dial / start,
loop start and ground start.
Page 20
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 20 Document #: LTRT-69903
Figure 1-1 below illustrates a typical Mediant 2000 gateway application over VoIP Network.
Figure
1-1: Typical Mediant 2000 Gateway Application
1.5 Mediant 2000 Features
This section provides a high-level overview of some of the many Mediant 2000 supported
features.
1.5.1 General Features
• Compliant with H.323 Ver. 4.
• Coders include: G.711, G.723.1, G.726, G.729A/B, GSM and NetCoder at 6.4 to 8.8 kbps,
negotiable per channel. Note that GSM isn’t supported on the Mediant 1000.
• T.38 fax with superior performance (handling a round-trip delay of up to nine seconds).
• Echo Canceler (with up to 128 msec tail length), Jitter Buffer, Voice Activity Detection (VAD)
and Comfort Noise Generation (CNG) support.
• Silence suppression with Comfort Noise Generation.
• Web management for easy configuration and installation.
• EMS for comprehensive management operations (FCAPS).
• Simple Network Management Protocol (SNMP) and Syslog support.
Page 21
Mediant Series and TP-1610 H.323 User’s Manual 1. Overview
Version 4.6 21 July 2005
• Multiplexes RTP streams from several users together to reduce bandwidth overhead.
• Capable of automatically updating its firmware version and configuration.
• Secured Web access (HTTPS) and Telnet access using SSL / TLS.
1.5.2 PSTN-to-H.323 Interworking
The Mediant 2000 gateway performs interworking between ISDN or CAS via E1/T1/J1 digital
spans and H.323 VoIP ITU-T protocol. 16 E1 T1, or J1 spans are supported (480 channels) in a
two modules gateway.
The Mediant 2000 gateway supports various ISDN PRI protocols such as EuroISDN, North
American NI2, Lucent 4/5ESS, Nortel DMS100, Meridian 1 DMS100, Japan J1, as well as QSIG
(basic call). PRI support includes User Termination or Network Termination side. ISDN-PRI
protocols can be defined on an E1/T1 basis (i.e., different variants of PRI are allowed on different
E1/T1 spans).
In addition, it supports numerous variants of CAS protocols for E1 and T1 spans, including MFC
R2, E&M wink start, E&M immediate start, E&M delay dial/start, loop-start, and ground start. CAS
protocols can be defined on an E1/T1 basis (i.e., different variants of CAS are allowed on
different E1/T1 spans).
PSTN to H.323 and H.323 to PSTN Called and Calling number can be optionally modified
according to number manipulation rules, including also modification of Numbering Type and
Numbering Plan.
1.5.2.1 Supported Interw orking Features
• Definition and use of Trunk Groups for routing IPÆPSTN calls.
• B-channel negotiation for PRI spans.
• ISDN Non Facility Associated Signaling (NFAS).
• PRI to H.323 Interworking of Q.931 Display (Calling name) information element.
• ISDN to H.323 Interworking of Numbering Plan and Type, or option to configure the H.323
Numbering Plan and Type in the Source/Destination Manipulation tables.
• Interworking of PSTN to H.323 release causes.
• Interworking of ISDN redirect number, and optional swap of redirect number to called
number for ISDNÆIP calls.
• Interworking of ISDN calling line Presentation & Screening indicators.
• Option of interworking of ISDN and H.323 TransferCapability.
• Supports ISDN en-block or overlap dialing for incoming TelÆIP calls.
• Supports sending trunk ID and B-channel number in H.323 Setup and Proceeding messages
(in the non-standard part).
• Interworking of Progress Indicator between H.323 and PRI, or an option to configure PI
values in both directions.
• Supports routing of IPÆTel calls to predefined trunk groups.
• Supports a configurable channel select mode per trunk group.
• Supports various number manipulation rules for IPÆTel and TelÆIP, called and calling
numbers.
• Supports transfer of User-to-User Information Element between H.323 and PRI.
• Interworking of ISDN Progress message and Progress Cause.
Page 22
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 22 Document #: LTRT-69903
1.5.3 H.323 Compatibility
The Mediant 2000 H.323 gateway is built on and implements the RadVision™ H.323 version 4.2
protocol stack. The gateway complies with H.323 Version 4.0 ITU standard, H.245 Version 10
and H.225 Version 4.
1.5.3.1 Gatekeeper Features
• Registers to known Gatekeeper.
• Supports Gatekeeper registration with prefixes.
• Supports sending of Unregister request before reset.
• Uses routed or direct mode calls.
• Supports the Alternative Gatekeepers mechanism, used to obtain the IP addresses of
alternative Gatekeepers.
• Uses redundant Gatekeepers (if redundant Gatekeepers are defined).
• Works also without a Gatekeeper using the internal routing table with dialing plan rules.
• Can fallback to internal routing table if there is no communication with the Gatekeepers.
• Supports the ‘TimeToLive’ parameter. The gateway sends Registration requests up to
‘TimeToLive’ expiration.
• Supports Info Request Response (IRR) messages for KeepAlive.
• Supports the mapping of destination (Alias) numbers in ACF message by the Gatekeeper.
• Supports Gatekeeper ID configuration (per Gatekeeper IP) for different Gatekeepers.
• Supports Lightweight Registration.
• Supports RAI (Resource Available Indication) messages, informing Gatekeeper that the
gateway’s resources are below a threshold.
• Support registration types: E.164, H323-ID and PartyNumber.
• Supports H.235 Security, Annex D Procedure 1 (authentication with a Gatekeeper).
1.5.3.2 Call Setup Features
• Can use Normal Connect procedure.
• Can use the Fast Connect procedure with or without immediately opening H.245 channel.
• Can use Tunneling.
• Can negotiate a coder from a list of given coders for Normal or Fast Connect procedures.
• Can open an H.245 channel when using Fast Connect.
• Supports Early H.245 procedure, enabling opening of an H.245 channel before a Connect
message is received. Can be used for sending out-of-band Dual Tone Multi Frequency
(DTMF) digits before a call is answered.
• Can represent SourceNumber and DestinationNumber through: E.164, H323-ID and
PartyNumber.
• Can configure (in the manipulation tables) or map (according to H.225 V.4 Table 18) the
representation of the Src/Dest number types in H.323 messages.
• Supports Pre-Grant ARQ, enabling the gateway to skip ARQ messages for incoming or
outgoing calls.
Page 23
Mediant Series and TP-1610 H.323 User’s Manual 1. Overview
Version 4.6 23 July 2005
1.5.3.3 General H.323 Features
• The Mediant 2000 gateways are identified by Country Code (0xB5) and Manufacturers Code
(0x28) in H.323 messages.
• Supports H.323 Annex D, T.38 real time fax.
• Supports H.450 Call Hold, Call Transfer, Call Forwarding and Call waiting supplementary
services (H.450.1, H.450.2, H.450.3, H.450.4 and H.450.6).
• Supports the following coders:
¾ G.711 A-law 64 kbps (10, 20, 30, 40, 50, 60, 80, 100, 120 msec)
¾ G.711 µ-law 64 kbps (10, 20, 30, 40, 50, 60, 80, 100, 120 msec)
¾ G.723.1 5.3, 6.3 kbps (30, 60, 90, 120 msec)
¾ G.726 16, 24, 32, 40 kbps (10, 20, 30, 40, 50, 60, 80, 100, 120 msec)
¾ G.729A/B 8 kbps (10, 20, 30, 40, 50, 60, 80, 100 msec)
¾ NetCoder 6.4, 7.2, 8.0 and 8.8 kbps (20, 40, 60, 80, 100, 120 msec)
¾ Transparent (20, 40, 60, 80, 100, 120 msec)
¾ GSM Full-Rate (20, 40, 60, 80 msec) (isn’t supported on the
Mediant 1000)
• Supports DTMF negotiation.
• Supports DTMF signal out-of-band through H.245 channel, (using ‘Alphanumeric’ or ‘Signal’
field).
• Supports DTMF in band according to RFC 2833 including negotiation of payload type.
• Supports DTMF signal out-of-band using H.225/Q.931 Keypad facility messages.
• Supports reopening of logical channel and implementation of third-party reroute.
• Supports configurable H.323 Port Range.
• Supports H.225/Q.931 Progress Indicator parameter for Fast Connect, enabling playing of
local Ringback tone or to cut through the voice channel to listen to remote Call Progress
Tones/messages.
• Supports H.245 round trip delay. When activated the gateway periodically generates H.245
round trip delay requests.
• Supports ISDN PRI Setup and Facility messages tunneling in H.323 according to H.323
Annex M.3.
Note that the vulnerability of the Mediant 2000 was evaluated to H.323 messages per NISCC
Vulnerability Advisory 006489/H323 (refer to uniras.gov.uk
and to kb.cert.org).
For more updated information on the gateway’s supported features, refer to the latest Mediant
2000 & TP-1610 H.323 Release Notes.
Page 24
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 24 Document #: LTRT-69903
Reader's Notes
Page 25
Mediant Series and TP-1610 H.323 User’s Manual 2. Physical Description
Version 4.6 25 July 2005
2 Physical Description
This section provides detailed information on the hardware components, the location and
functionality of the LEDs, buttons and connectors of the following products:
• Mediant 2000 (refer to Section 2.1 below).
• TP-1610 (refer to Section 2.2 on page 27).
• Mediant 1000 (refer to Section 2.3 on page 30).
2.1 Mediant 2000 Physical Description
The Mediant 2000 (shown in Figure 2-1 below) comprises the following components:
• A 19-inch 1U high rack mount chassis (refer to Section
2.1.1 on page 26).
• A single compactPCI™ TP-1610 board (refer to Section
2.2 on page 27).
• A single TP-1610 Rear Transition Module (RTM) (refer to Section
2.2.2 on page 29).
• A single available cPCI slot for an optional third-party CPU board (refer to Section
2.1.2 on
page 29).
Figure
2-1: Mediant 2000 Front View
Table
2-1: Mediant 2000 Front View Component Descriptions
Item # Label Component Description
1 FAULT Dual AC Power LED.
2 cPCI board locking screws.
3 cPCI latches.
4 TP-1610 cPCI board, 16-trunk configuration.
5 Status LED Indicators.
6 T1/E1 STATUS E1/T1 Trunk Status LED Indicators.
7 ETH Ethernet LED Indicators.
8 Reset button.
9 cPCI LED Indicators.
10 Power and Fan LEDs
11 An available cPCI slot for an optional third-party CPU board.
1 7
2
3
6
5
4
8
6
9
10
11
Page 26
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 26 Document #: LTRT-69903
2.1.1 The Mediant 2000 Chassis
The Mediant 2000 chassis is an industrial platform, 19” wide, 1U high and 12” deep that houses
the TP-1610 board in its front cage, slot #1 (the lower slot) and the TP-1610 RTM in its rear cage,
slot #1 (the lower slot).
Slot # 2 in the Mediant 2000 chassis’ front and rear cages can optionally be used by customers
for a CPU board.
Refer to Table
2-2 for detailed description of the chassis’ LED indicators.
Table
2-2: Chassis LED Indicators
Location Color Function
Right side of front panel Green
The power is on.
Right side of front panel Red
Fan failure - indicates that any of the internal fans has significantly
reduced its speed or has frozen.
Left side of front panel Red
Power supply failure - indicates that one of the two AC redundant
power supplies is faulty or disconnected from the AC/mains outlet.
(This LED is only relevant for the dual AC power supply).
2.1.1.1 Power Supply
The Mediant 2000 power supply is available in three configuration options:
• Single universal 100-240 VAC 1 A max, 50-60 Hz.
• Dual-redundant 100-240 VAC 1.5 A max, 50-60 Hz.
• -48 VDC power supply suitable for field wiring applications.
2.1.2 Optional CPU Board
The Mediant 2000 provides an optional second cPCI slot that can be optionally used for
customer’s CPU board. This CPU board can be used for general applications such as a
Gatekeeper, Softswitch, Application Server or other. The following CPU boards were tested for
compliancy with the Mediant 2000 chassis:
• Sun™: CP2080 + PMC-233 (Ramix™ disk on board) + Rear Transition Module (RTM).
• Intel™ ZT5515B-1A with 40GB on-board disk plus RTM (ZT4807).
For details on removing / inserting the optional CPU board, refer to the directions accompanying
it.
Page 27
Mediant Series and TP-1610 H.323 User’s Manual 2. Physical Description
Version 4.6 27 July 2005
2.2 TP-1610 Physical Description
The TP-1610 (shown in Figure 2-2) is a high-density, hot-swappable, cPCI resource board with a
capacity of up to 480 ports, supporting all necessary functions for voice, data and fax streaming
over IP networks. The TP-1610 is composed of one or two identical media gateways modules:
Gateway-1 and Gateway-2, each containing 240 DSP channels. These media gateways are fully
independent, each gateway having its own MAC (Media Access Control) and IP addresses and
LED indicators. The TP-1610 board is supplied with a rear I/O configuration in which both PSTN
trunks and Ethernet interface are located on a passive rear I/O module (for information on the
RTM, refer to Section
2.2.2 on page 29).
Figure
2-2: Front and Upper View of the TP-1610 cPCI Board
Table
2-3: Front and Upper View of the TP-1610 cPCI Board Component Descriptions
Item # Label Component Description
1 Status LEDs
2 ETH Ethernet LEDs
3 Reset button
4 cPCI LEDs
5 cPCI Latch
6 T1 / E1 STATUS T1/E1 Trunk Status LEDs (for each of trunks 1 to 8)
7 T1 / E1 STATUS T1/E1 Trunk Status LEDs (for each of trunks 9 to 16)
2
1
3
4
5
6
7
Page 28
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 28 Document #: LTRT-69903
2.2.1 TP-1610 Front Panel LED Indicators
The functionality of the front panel LEDs for the TP-1610 is described in the following four tables
and illustrated in Figure
2-2 on page 27. Note that there is a choice of front panels according to
the number of channels.
Table
2-4: Status LED Indicators
Label LED Color LED Function
FAIL Red
Normally OFF; Red indicates gateway failure (fatal error)
Green
Gateway initialization sequence terminated OK
ACT
Yellow
N/A
Bi-color
LED
Table 2-5: E1/T1 Trunk Status LED Indicators
Label LED Color Signal Description
Green
Trunk is synchronized (normal operation)
Red
Loss due to any of the following 4 signals:
Bi-color
LED
LOS
Loss of Signal
LOF
Loss of Frame
AIS
Alarm Indication Signal (the Blue Alarm)
T1/E1 Status 1 to 8
and
T1/E1 Status 9 to 16
RAI
Remote Alarm Indication (the Yellow Alarm)
Note: On the front panel 16 LEDs are provided for 16-span units and 8 LEDs are
provided for 1-span, 2-span, 4-span, and 8-span units. In the case of 1-span,
2-span and 4-span units, the extra LEDs are unused.
Table 2-6: Ethernet LED Indicators
Label LED Color LED Function
LINK Green
Link all OK
ACT Yellow
Transmit / receive activity
Table 2-7: cPCI LED Indicators
Label LED Color LED Function
PWR Green
Power is supplied to the board
The cPCI board can now be removed.
SWAP READY Blue
The cPCI board was inserted successfully.
For detailed information on inserting / removing the TP-1610 board,
refer to Section 3.2.3 on page 49.
During correct operation, the ACT LED is lit green, the FAIL LED is off. Changing of the FAIL LED
to red indicates a failure.
Page 29
Mediant Series and TP-1610 H.323 User’s Manual 2. Physical Description
Version 4.6 29 July 2005
2.2.2 Rear Transition Module
The RTM includes PSTN trunks, an Ethernet interface and an optional RS-232 connector
(available only on the 1, 2 and 4-span configuration).
The Ethernet interface features dual 10/100 Base-TX, RJ-45 shielded connectors for (an active /
standby) redundancy scheme providing protection against the event of a failure.
The PSTN interface is provided with a choice of rear panels (1-span, 2-span, 4-span, 8-span or
16-span).
Rear panel with two 50-pin female Telco connectors (DDK 57AE-40500-21D) (shown in Figure
2-3) is required for a gateway equipped with 16 E1/T1 spans. Rear panel with RJ-48c connectors
(shown in Figure
2-4) is required for a gateway equipped with 1, 2, 4, or 8 E1/T1 spans. The
physical difference between the 1-Span, 2-Span and 4-Span RTMs, and the 8-span RTM is that
the RJ-48c ports are depopulated correspondingly.
Figure
2-3: Rear Panel with two 50-pin Connectors for 16 Trunks
Table
2-8: Rear Panel with two 50-pin Connectors for 16 Trunks Component Descriptions
Item # Label Component Description
1 ETHERNET 2 Ethernet Ports. 2 RJ-45 network connectors.
2 TRUNKS E1/T1 trunks 9 to 16. 50-pin male Telco connector.
3 TRUNKS E1/T1 trunks 1 to 8. 50-pin male Telco connector.
Figure 2-4: Rear Panel with 8 RJ-48c Connectors for 8 Trunks
Table
2-9: Rear Panel with 8 RJ-48c Connectors for 8 Trunks Component Descriptions
Item # Label Component Description
1 ETHERNET 2 Ethernet Ports. 2 RJ-45 network connectors
2 TRUNKS 8 E1/T-1 Spans. 8 RJ-48c trunk connectors
1
2
3
1
2
Page 30
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 30 Document #: LTRT-69903
2.3 Mediant 1000 Physical Description
Designed to meet Network Equipment Building System (NEBS) Level 3, the Mediant 1000 is a
19-inch industrial platform chassis, 1U high and 13.8 inch deep.
The Mediant 1000 supports a scalable, modular architecture that includes up to four modules, a
single CPU module, a power supply module and an optional fan try module (the extractable
modules are shown in Table
2-15 on page 37).
This section provides detailed information on the:
• Mediant 1000 front panel (refer to Section
2.3.1 below).
• Mediant 1000 rear panel (refer to Section
2.3.2 on page 36).
• Mediant 1000 modules (refer to Section
2.3.3 on page 37).
• Partner application platform (refer to Section
2.3.4 on page 38).
2.3.1 Mediant 1000 Front Panel
Figure 2-5 shows a front view of the Mediant 1000.
Figure
2-5: Mediant 1000 Front View & CPU Enlargement
Table
2-10: Mediant 1000 Front View Component Descriptions (continues on pages 30 to 31)
Item # Label Component Description
Front View of Chassis
1
4 RJ-48c ports module.
2 CPU
Spare CPU module slot.
3 CPU
Main CPU module.
4 Power 1
Spare power supply slot.
5 Power 2
Main power supply.
6 Schematic
Extractable fan tray.
Page 31
Mediant Series and TP-1610 H.323 User’s Manual 2. Physical Description
Version 4.6 31 July 2005
Item # Label Component Description
Enlarged View of CPU
3 CPU
Main CPU module.
7 -
Locking screw (2).
8 I0I0
RS-232 port.
9 //
Reset button.
10
II
10/100 Base-TX Ethernet Port 2.
11
I
10/100 Base-TX Ethernet Port 1.
12 ♫
Audio IN/OUT (for paging and MOH (Music on Hold) functionalities).
13
II
Dry contact port for paging PTT.
14
I
Dry contact port for alarm applications.
7 -
Locking screw (2).
Figure 2-6 illustrates the front layout of the Mediant 1000. There is also a schematic of the front
layout on the front panel of the fan tray. To view your specific device’s configuration via the
Embedded Web Server, refer to Section
5.7.5 on page 103.
Figure
2-6: Mediant 1000 Front Layout
I/O module
#1
I/O module
#2
I/O module
#3
CPU 1
I/O module
#4
Blank panel Blank panel
Spare CPU
module slot
Power 1
Spare
power
supply
slot
Fan
2.3.1.1 I/O Modules
The Mediant 1000 supports up to four digital trunks (fully flexible, from a single and up to four
trunks per module).
If the power fails, a relay connects trunks 1 to 2 and 3 to 4 (in the same module) acting as a
fallback for PSTN trunks.
2.3.1.2 CPU Module
The CPU (Central Processing Unit) module is located to the right of the six modules.
Figure
2-5 shows the CPU module’s front panel ports and connectors described in sequence from
left to right in the following sections.
2.3.1.2.1 Dry Contact Connector (Labeled I and II1)
The dry contact can be activated by software to produce a reliable switch (Push-To-Talk (PTT))
for the following devices:
• Audible or visual alarms – bell, siren, hooter, or light
• Loudspeakers for paging
• Locking mechanisms or general-purpose switches such as door locks etc.
1
Not currently supported. Contact AudioCodes regarding availability.
Page 32
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 32 Document #: LTRT-69903
2.3.1.2.2 Audio IN/OUT2
The Audio IN/OUT port is indicated by the musical note and loudspeaker symbols (refer to Figure
2-5 on page 30). It is used for Music on Hold (IN) and paging (OUT).
2.3.1.2.3 Two 10/100 Base-TX Ethernet Ports (Labeled I and II)
Two 10/100 Base-TX Ethernet ports provide a dual Ethernet redundancy scheme, protecting
against failure (for example, a disconnection) of any cable or associated LAN switch port.
2.3.1.2.4 RS-232 Port (Labeled I0I0)
The RS-232 port is used to access the CLI (Section 15 on page 229) and to receive error /
notification messages (a D9 adapting cable is supplied).
Note: The RS-232 port isn’t intended for a permanent connection.
2.3.1.2.5 Reset Button (Labeled //)
The Mediant 1000 Reset button, indicated by the ‘//’ symbol, is located directly above the RS-232
port.
To reset the system, take a pointed object and press in the Reset button.
You can also use the ‘Reset’ button to restore the Mediant 1000 networking parameters to their
factory default values (refer to Section
11.1 on page 185).
2.3.1.3 Power Supply Module (Labeled 1 and 2)
The Mediant 1000 features two extractable power supply units, Power 1 and Power 2 (refer to
Figure
2-6 on page 31), with an AC power connector at the rear of each (refer to Figure 2-10 on
page 36). Presently, only the left connector is active; the right connector is to be supported in the
future.
If both Power 1 and Power 2 units are used (future support), they share the load between them.
This (optional) load-sharing feature enables failure protection / redundancy. When using this
feature, users are advised to connect each power supply unit to a different AC supply circuit.
If a user chooses either a hardware configuration option involving only one power supply unit, or
two units but chooses to cable only one, failure protection / redundancy cannot occur.
The front panel of the power supply unit features a power supply LED that is lit green when the
Mediant 1000 is powered up. If this LED does not light up, a power supply problem may be
present.
2.3.1.4 Fan Tray Module
The Mediant 1000 components are cooled by a fan tray unit located to the extreme right, when
facing the front panel (refer to Figure
2-6 on page 31).
The fan tray unit draws air in by six fans through a perforated grill at the right side of the chassis.
The incoming air passes through a removable filter, whose honeycombed design prevents RF
interference. The clean air passes through the entire set of modules cooling each one and exits
the Mediant 1000 via perforated vents on the left side of the chassis.
2
Not currently supported. Contact AudioCodes regarding availability.
Page 33
Mediant Series and TP-1610 H.323 User’s Manual 2. Physical Description
Version 4.6 33 July 2005
Blank panels are used to cover all unoccupied slots on the front and rear sides of the chassis.
The blank panels are especially constructed to assist optimal air flow within the chassis.
Note: It is imperative to cover all unoccupied slots in the front and rear panels of the
chassis with blank panels to maintain internal airflow pressure.
2.3.1.4.1 Replacing the Air Filter
The fan try module includes a removable air filter (located within the fan assembly, immediately
inside the perforated grill). The air filter should be replaced approximately every 90 days and
should be checked weekly to ensure it is not saturated and require cleaning / replacement. You
should clean the air filter no more than three times, after which the air filter requires replacement.
The air filter removed from the fan try unit is shown in Table
2-15 on page 37.
Cleaning or replacing the air filter can be carried out while the system is fully functioning.
¾ To clean / replace the air filter, take these 7 steps:
1. Release the two screws on the top right-hand corner and the bottom right-hand corner of the
front panel of the fan tray unit.
2. Pull the fan tray unit outward. Figure
2-7 below shows the fan try unit slightly extracted.
Figure
2-7: Slightly Extracted Fan Try Unit
3. With your fingertips, grasp the steel frame of the air filter and separate it from the fan try unit;
you should be able to remove it relatively easily. Figure
2-8 below show the air filter
extracted from the fan try unit.
Page 34
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 34 Document #: LTRT-69903
Figure 2-8: Fan Try with Filter Extracted
4. Take one of the following steps:
¾ If you are cleaning the filter, use a vacuum cleaner (on light suction) to remove dust
particles from the filter.
¾ Alternatively, if you are replacing the filter, discard the old air filter and replace it with an
air filter purchased from AudioCodes.
5. Attach the (new / cleaned) air filter to the fan try module; position the two holes on the filter
over the pins on the fan tray (refer to Figure
2-8).
6. Insert the fan tray unit into its slot, until the front panel is flush with the chassis plate.
7. Fasten the two screws on the top right-hand corner and the bottom right-hand corner of the
front panel of the fan tray unit.
Warning: When removing the fan tray unit, the fans continue to rotate at a high
speed. Use caution not to touch the rotating fan blades.
Warning: Prepare all the equipment you need to clean the air filter before
removing it for cleaning. It is imperative that the chassis does not
remain without the fan tray unit for a long period of time. Be sure to
reinsert the fan tray unit while you are cleaning the air filter and reinsert
the air filter as soon as it is clean.
Page 35
Mediant Series and TP-1610 H.323 User’s Manual 2. Physical Description
Version 4.6 35 July 2005
2.3.1.5 Front Panel LEDs
Figure 2-9 below, shows the location of the front panel LEDs on the Mediant 1000. They are
described below in Table
2-11, Table 2-12 and Table 2-13.
Figure
2-9: Location of Front Panel LEDs
Table
2-11: Functionality of the CPU Module LEDs
LED Location Color State LED Indication
Green
On
Link OK.
Ethernet
Ports I & II
2
Yellow
Blinking
Data is being received.
General
Purpose
3
Green
Future support.
Table 2-12: Functionality of the I/O Modules LEDs
LED Location Color State LED Indication
Green
On
Trunk is synchronized (normal operation)
Loss due to any of the following 4 signals:
LOS Loss of Signal
LOF Loss of Frame
AIS Alarm Indication Signal (the Blue Alarm)
Red
On
RAI Remote Alarm Indication (the Yellow Alarm)
RJ-48c
1
- Off
Either there is a failure / disruption in the AC power supply or the
power is currently not being supplied to the Mediant 1000 through the
AC power supply entry.
Table 2-13: Functionality of the Power Supply Module LEDs
LED Location Color State LED Indication
Green
On
The LED of each AC power supply is lit green when the power supply
is operating correctly.
Power
Supply
4
- Off
Either there is a failure / disruption in the AC power supply or the
power is currently not being supplied to the Mediant 1000 through the
AC power supply entry.
Page 36
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 36 Document #: LTRT-69903
2.3.2 Mediant 1000 Rear Panel
The Mediant 1000 rear connectors are described in the following sections (refer to Figure 2-10).
Figure
2-10: Mediant 1000 Rear Connectors
Table
2-14: Mediant 1000 Rear Connectors Component Descriptions
Item # Label Component Description
1 ESD
ESD (Electrostatic Discharge) port.
2
Protective earthing screw.
3 100-240v~1A
Dual AC Power Supply Entry.
Currently only the left-hand connector is active. Support for an active righthand connector is intended in a future release.
1
2
3
3
Page 37
Mediant Series and TP-1610 H.323 User’s Manual 2. Physical Description
Version 4.6 37 July 2005
2.3.3 Mediant 1000 Modules
The extractable Mediant 1000 modules are shown in Table 2-15 below.
Table
2-15: Extractable Mediant 1000 Modules
Module Description
CPU module
Digital I/O module
Fan tray module with six fans and an air filter
Power supply module
Page 38
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 38 Document #: LTRT-69903
2.3.4 Partner Application Platform
The Mediant 1000 can also host a flexible platform for partner applications. The open platform on
the Mediant 1000 offers partners the option to host their own applications (e.g., IP-PBX or call
center application) using a powerful, low-power consumption processor and hard disks to provide
a complete solution within the Mediant 1000 chassis.
2.3.4.1 Connection Module (CM)
Figure 2-11 shows the front panel of the CM module (located on the Mediant 1000 front panel).
Figure
2-11: Front View of the CM Module
Table
2-16: CM Module Component Descriptions
Item # Component Description
1
RS-232 port, Molex 3 pin connector
2
General purpose LED
3
HDD 2 activity LED
4
HDD 1 activity LED
5
iPMX power LED
6
Type A USB connector
2.3.4.2 iPMX Module
The iPMX module (shown in Figure 2-12) is located on the Mediant 1000 rear panel. It includes
an embedded Intel
TM
Pentium-M TM Celeron ULV 600 MHz processor platform for third-party
hosted applications. The iPMX module is connected to the W1 on the rear end. The processor is
connected to a hard disk drive (described in Section
2.3.4.3 on page 39) located on the rear side
of the W1 chassis (second hard disk is optional). Both hard disks are connected to the W1 midplane via an edge connector.
Note: The iPMX module includes a backup battery that is responsible for retaining
the CMOS setup configuration. The battery lasts for 18 months of nonoperating conditions. When empty (the CMOS configuration returns to its
default). Replace with Lithium battery model CR-1225.
1 2
3
4 5
6
Page 39
Mediant Series and TP-1610 H.323 User’s Manual 2. Physical Description
Version 4.6 39 July 2005
Figure 2-12: iPMX Module
Table
2-17: iPMX Module Component Descriptions
Item # Component Description
1
RJ-45 connector as 10/100 Base-TX Ethernet port
2
Ethernet activity LED (yellow)
3
Ethernet link LED (green)
4
RJ-11 connector used for night bell relay output. The pinout of this connector is described in Figure
2-13.
5
RJ-11 connector (voice + PTT control) used for paging output. The pinout of this connector is
described in Figure 2-14.
6
General purpose LED
7
Second HDD activity LED
8
First HDD activity LED
9
SBC power LED
10
Reset switch
11
3.5 mm stereo mini jack connector used as an input for music on hold
Figure 2-13: RJ-11 Connector Used for Night Bell
1 2 3 4
1 -
2 3 4 -
Not connected
Not connected
Rel ay
Rel ay
Figure
2-14: RJ-11 Connector Used for Paging
1 2 3 4
1 -
2 3 4 -
Rel ay
Rel ay
Audio out
Audio out
1
4
5
2 3
6
7
8
9
11
10
Page 40
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 40 Document #: LTRT-69903
2.3.4.3 HDMX Module
The HDMX module is located on the Mediant 1000 rear panel.
A 40 Giga Byte Hard Disk Drive 5200 RPM. A second HDD is optional.
Figure
2-15: HDMX Module
HDD activity
LED
Page 41
Mediant Series and TP-1610 H.323 User’s Manual 3. Installation
Version 4.6 41 July 2005
3 Installation
This section provides detailed information on the installation procedures for the following
products:
• Mediant 2000 (refer to Section
3.1 below).
• TP-1610 (refer to Section
3.2 on page 49).
• Mediant 1000 (refer to Section
3.3 on page 51).
For information on how to start using the gateway, refer to Section
4 on page 57.
Caution Electrical Shock
The equipment must only be installed or serviced by qualified service personnel.
3.1 Installing the Mediant 2000
¾ To install the Mediant 2000, take these 4 steps:
1. Unpack the Mediant 2000 (refer to Section 3.1.1 below).
2. Check the package contents (refer to Section
3.1.2 below).
3. Mount the Mediant 2000 (refer to Section
3.1.3 on page 42).
4. Cable the Mediant 2000 (refer to Section
3.1.4 on page 44).
After powering-up the Mediant 2000, the Ready and LAN LEDs on the front panel turn to green
(after a self-testing period of about 3 minutes). Any malfunction changes the Ready LED to red
(refer to Section
2.2.1 on page 28 for details on the Mediant 2000 LEDs).
When you have completed the above relevant sections you are then ready to start configuring the
gateway (Section
4 on page 57).
3.1.1 Unpacking
¾ To unpack the Mediant 2000, take these 6 steps:
1. Open the carton and remove packing materials.
2. Remove the Mediant 2000 gateway from the carton.
3. Check that there is no equipment damage.
4. Check, retain and process any documents.
5. Notify AudioCodes or your local supplier of any damage or discrepancies.
6. Retain any diskettes or CDs.
3.1.2 Package Contents
Ensure that in addition to the Mediant 2000, the package contains:
• For the dual AC power supply version two AC power cables are supplied; for the single AC
power supply version one AC power cable is supplied.
• For the DC power supply version, one connectorized DC power cable (crimp connection
type) and one DC adaptor (screw connection type) connected to the rear panel of the
Mediant 2000 are supplied; use only one type.
Page 42
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 42 Document #: LTRT-69903
• CD (software and documentation).
• Small plastic bag containing (refer to Figure
3-1):
¾ Two brackets and four bracket-to-device screws for 19-inch rack installation option.
¾ Four anti-slide bumpers for desktop / shelf installation option.
• The Mediant 2000 Fast Track Installation Guide.
Figure
3-1: 19-inch Rack & Desktop Accessories
3.1.3 Mounting the Mediant 2000
The Mediant 2000 can be mounted on a desktop, or installed in a standard 19-inch rack. Refer to
Section
3.1.4 on page 44 for cabling the Mediant 2000.
3.1.3.1 Mounting the Mediant 2000 on a Desktop
No brackets are required. Optionally, attach the four (supplied) anti-slide bumpers to the base of
the Mediant 2000 and place it on the desktop in the position you require.
3.1.3.2 Installing the Mediant 2000 in a 19-inch Rack
Users can install the device in a standard 19-inch rack either by placing the device on a shelf
preinstalled in the rack (preferred method), or by attaching the device directly to the rack’s frame
via integral brackets.
Before rack mounting the chassis, attach the two (supplied) brackets to the front sides of the
device (refer to Figure
3-2).
¾ To attach the two front side brackets, take these 3 steps:
1. Remove the 2 screws nearest the front panel on either side of the device.
2. Align a bracket over 2 holes on one side (so that the bracket’s larger holes face front) and
with the 2 supplied replacement screws, screw in the bracket.
3. Perform the same procedure on the other side.
Page 43
Mediant Series and TP-1610 H.323 User’s Manual 3. Installation
Version 4.6 43 July 2005
Figure 3-2: Mediant 2000 Front View with 19-inch Rack Mount Brackets
Rack Mount Safety Instructions (UL)
When installing the chassis in a rack, be sure to implement the following Safety
instructions recommended by Underwriters Laboratories:
• Elevated Operating Ambient - If installed in a closed or multi-unit rack assembly,
the operating ambient temperature of the rack environment may be greater than
room ambient. Therefore, consideration should be given to installing the equipment
in an environment compatible with the maximum ambient temperature (Tma)
specified by the manufacturer.
• Reduced Air Flow - Installation of the equipment in a rack should be such that the
amount of air flow required for safe operation on the equipment is not compromised.
• Mechanical Loading - Mounting of the equipment in the rack should be such that a
hazardous condition is not achieved due to uneven mechanical loading.
• Circuit Overloading - Consideration should be given to the connection of the
equipment to the supply circuit and the effect that overloading of the circuits might
have on overcurrent protection and supply wiring. Appropriate consideration of
equipment nameplate ratings should be used when addressing this concern.
• Reliable Earthing - Reliable earthing of rack-mounted equipment should be
maintained. Particular attention should be given to supply connections other than
direct connections to the branch circuit (e.g., use of power strips.)
¾ To attach the device to a 19-inch rack, take these 2 steps:
1. Position the device in your 19-inch rack and align the left-hand and right-hand bracket holes
to holes (of your choosing) in the vertical tracks of the 19-inch rack.
2. Use standard 19-inch rack bolts (not provided) to fasten the device to the frame of the rack.
AudioCodes recommends using two additional (not supplied) rear mounting brackets to provide
added support.
Note: Users assembling the rear brackets by themselves should note the following:
• The distance between the screws on each bracket is 26.5 mm.
• To attach the brackets, use 4-40 screws with a maximal box penetration length
of 3.5 mm.
¾ To place the device on a 19-inch rack’s shelf, take these 2 steps:
1. Place the device on the preinstalled shelf.
2. You’re now recommended to take the optional steps of fastening the device to the frame of
the rack (as described above) while it is placed on the shelf, so preventing it from sliding
when inserting cables into connectors on the rear panel.
Page 44
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 44 Document #: LTRT-69903
3.1.4 Cabling the Mediant 2000
Refer to Section 2 on page 25 for detailed information on the Mediant 2000 rear panel connectors
and LEDs. Note that the Mediant 2000 is available in many configurations, i.e., AC or DC, in the
16-trunk, 8-trunk, 4-trunk, 2-trunk or 1-trunk device. The 16-trunk dual AC (Figure
3-3) and the
8-trunk DC (Figure
3-4) configurations are illustrated here as representative products.
Figure
3-3: Mediant 2000 Rear Panel Cabling (16 Trunks, Dual AC Power)
Table
3-1: Mediant 2000 Rear Panel Cabling (16 Trunks, Dual AC Power) Component Descriptions
Item # Label Component Description
1
RTM locking screws.
2 ETHERNET
Two Category 5 network cables, connected to the 2 Ethernet RJ-45 ports.
3 TRUNKS
Two 50-pin Telco connector cables, each supporting 8 trunks.
4
Protective earthing screw.
5
100-240~1.5A
Dual AC power cables.
Figure 3-4: Mediant 2000 Rear Panel Cabling (8 Trunks, DC Power))
Table
3-2: Mediant 2000 Rear Panel Cabling (8 Trunks, DC Power) Component Descriptions
Item # Label Component Description
1
RTM latches.
2 ETH
A Category 5 network cable, connected to the Ethernet 1 RJ-45 port.
3 PSTN
8 RJ-48c ports, each supporting a trunk.
4
Protective earthing screw.
5 48V 4A max
2-pin connector for DC.
5
2
4
3
21 1
5
2
4
3
1 13
Page 45
Mediant Series and TP-1610 H.323 User’s Manual 3. Installation
Version 4.6 45 July 2005
Electrical Earthing
The unit must be permanently connected to earth via the screw provided at the back on
the unit. Use 14-16 AWG wire and a proper ring terminal for the earthing.
¾ To cable the Mediant 2000, take these 5 steps:
1. Permanently connect the device to a suitable earth with the protective earthing screw on the
rear connector panel, using 14-16 AWG wire.
2. Connect the E1/T1 trunk interfaces (refer to Section
3.1.4.1 below).
3. Install the Ethernet connection (refer to Section
3.1.4.2 on page 46).
4. Optionally, connect the Mediant 2000 RS-232 port to your PC (refer to Section
3.1.4.3 on
page 46).
5. Connect the power supply (refer to Section
3.1.4.4 on page 47).
3.1.4.1 Connecting the E1/T1 Trunk Interfaces
Connect the E1/T1 Trunk Interfaces using either Telco or RJ-48 connectors:
¾ With 50-pin Telco connectors (16-trunk device), take these 3 steps:
1. Attach the Trunk cable with a 50-pin male Telco connector to the 50-pin female Telco
connector labeled ‘Trunks 1Æ8’ on the Rear Transition Module (RTM).
2. Connect the other end of the Trunk cable to the PBX/PSTN switch.
3. Repeat steps 1 and 2 for the other Trunk cable but this time connect it to the connector
labeled ‘Trunks 9Æ16’.
The 50-pin male Telco cable connector must be wired according to the pinout in Table
3-3 below,
and to mate with the female connector illustrated in Figure
3-5.
Figure
3-5: 50-pin Female Telco Board-Mounted Connector
125
26
50
Pin Numbers
Table 3-3: E1/T1 Connections on each 50-pin Telco Connector
E1/T1 Number
1 to 8 9 to 16
Tx Pins (Tip/Ring) Rx Pins (Tip/Ring)
1 9 27/2 26/1
2 10 29/4 28/3
3 11 31/6 30/5
4 12 33/8 32/7
5 13 35/10 34/9
6 14 37/12 36/11
7 15 39/14 38/13
8 16 41/16 40/15
Page 46
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 46 Document #: LTRT-69903
¾ With RJ-48c Connectors, take these 2 steps:
1. Connect the E1/T1 trunk cables to the ports labeled ’Trunks 1 to 8’ (in the case of the 8-trunk
device) on the RTM.
2. Connect the other ends of the Trunk cables to the PBX/PSTN switch.
RJ-48c trunk connectors are wired according to Figure
3-6 below.
Figure
3-6: Pinout of RJ-48c Trunk Connectors
1 2 3 4 5 6 7 8
3, 6, 7, 8
not connected
body = shield
1 = Rx Ring
2 = Rx Tip
4 = Tx Ring
5 = Tx Tip
RJ-48c Connector and Pinout
3.1.4.2 Installing the Ethernet Connection
Connect a standard Category 5 network cable to the Ethernet RJ-45 port (and the other as
optional redundancy/backup). Connect the other end of the Category 5 network cables to your IP
network. The Ethernet connectors (labeled Ethernet 1 and Ethernet 2) are wired according to
Figure
3-7.
Note that for redundant operation it is recommended to connect each of the Ethernet connectors
to a different switch.
When assigning an IP address to the gateway using HTTP (under step
1 in Section 4.2.1), you
may be required to disconnect this cable and re-cable it differently.
Figure
3-7: Pinout of RJ-45 Connectors
1 2 3 4 5 6 7 8
RJ-45 LAN Connector and Pinout
4, 5, 7, 8
not connected
1 = Tx+
2 = Tx3 = Rx+
6 = Rx-
3.1.4.3 Connecting the RS-232 Port to Your PC
Using a standard RS-232 straight cable (not a cross-over cable) with DB-9 connectors, connect
the RS-232 port to either COM1 or COM2 RS-232 communication port on your PC. The required
connector pinout and gender are shown below in Figure
3-8.
Note that the RS-232 port is available only on the 1, 2 and 4-span configuration.
For information on establishing a serial communications link with the gateway, refer to Section
11.2 on page 185.
Figure
3-8: RS-232 Cable Wiring
Page 47
Mediant Series and TP-1610 H.323 User’s Manual 3. Installation
Version 4.6 47 July 2005
3.1.4.4 Connecting the Power Suppl y
Connect the Mediant 2000 to the power supply using one of the following methods:
3.1.4.4.1 Connecting the AC Power Supply
¾ When using a single AC power cable:
Attach one end of the supplied 100/240 VAC power cable to the rear AC socket and connect the
other end to the correct earthed AC power supply.
¾ When using a dual AC power cable:
Attach one end of the supplied 100/240 VAC power cables to the rear AC sockets and connect
the other end to a separate earthed mains circuits (for power source redundancy).
Note: For the dual AC power supply note the following:
• The LED on the left side of the chassis is only connected when the dual AC is
used. It is not relevant to the single AC power connection.
• If only a single socket is connected to the AC power, (while the other plug is left
unconnected) the chassis’ LED (on the left side) is lit Red, indicating that one
of the dual power inlets is disconnected.
• When both the AC power cables are connected, one of the plugs can be
disconnected under power without affecting operation, in which case the
chassis’ left LED is lit Red.
• UPS can be connected to either (or both) of the AC connections.
• The dual AC connections operate in a 1 + 1 configuration and provide load-
sharing redundancy.
• Each of the dual power cables can be connected to different AC power phases.
3.1.4.4.2 Connecting the DC Power Supply
To connect the Mediant 2000 to a DC power supply use one of these two options:
• DC Terminal block with a screw connection type.
• DC Terminal block with a crimp connection type.
¾ When using a DC terminal block screw connector, take these 3 steps:
1. Create a DC cable by inserting two 14-16 AWG insulated wires into the supplied adaptor
(refer to Figure
3-9) and fasten the two screws, each one located directly above each wire.
2. Connect the two insulated wires to the correct DC power supply. Ensure that the connections
to the DC power supply maintain the correct polarity.
3. Insert the terminal block into the DC inlet located on the Mediant 2000.
Figure
3-9: DC Terminal Block Screw Connector
Page 48
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 48 Document #: LTRT-69903
¾ When using a DC terminal block crimp connector, take these 3 steps:
1. Remove the DC adaptor (screw connection type) that is attached to the Mediant 2000 rear
panel.
2. Connect the two insulated wires to the correct DC power supply. Ensure that the connections
to the DC power supply maintain the correct polarity (refer to Figure
3-10).
3. Insert the terminal block into the DC inlet located on the Mediant 2000.
Figure
3-10: DC Terminal Block Crimp Connector
2 screws for
connecting the
crimp terminal
block to the
Mediant 2000 rear
panel
Page 49
Mediant Series and TP-1610 H.323 User’s Manual 3. Installation
Version 4.6 49 July 2005
3.2 Installing the TP-1610
Electrical Earthing
Prior to installation of any board in a chassis, always correctly connect the chassis to a
safety ground according to the laws and regulations of the country in which the
installation is performed.
Electrical Component Sensitivity
Electronic components on printed circuit boards are extremely sensitive to static
electricity. Normal amounts of static electricity generated by clothing can damage
electronic equipment. To reduce the risk of damage due to electrostatic discharge when
installing or servicing electronic equipment, it is recommended that anti-static earthing
straps and mats be used.
¾ To install the TP-1610, take these 4 steps:
1. Unpack the TP-1610 (refer to Section 3.2.1 below).
2. Check the package contents (refer to Section
3.2.2 below).
3. Install the TP-1610 in your PC (refer to Section
3.2.3 on page below).
4. Cable the TP-1610 (refer to Section
3.2.4 on page 50).
When you have completed the above relevant sections you are then ready to start configuring the
gateway (Section
4 on page 57).
3.2.1 Unpacking
¾ To unpack the TP-1610, take these 6 steps:
1. Open the carton and remove packing materials.
2. Remove the TP-1610 board from the carton.
3. Check that there is no equipment damage.
4. Check, retain and process any documents.
5. Notify AudioCodes or your local supplier of any damage or discrepancies.
6. Retain any diskettes or CDs.
3.2.2 Package Contents
Ensure that in addition to the TP-1610, the package contains:
• Optionally, an RTM module.
• CD (software and documentation).
• This User’s Manual.
• The Mediant Series & TP-1610 H.323 Digital Gateways Release Notes
3.2.3 Installing the TP-1610
The TP-1610 cPCI board is hot-swappable and can therefore be removed from a slot (and
inserted into a slot) while the chassis is under power. It is recommended though that you power
down the chassis and read the notes below before replacing the components.
Page 50
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 50 Document #: LTRT-69903
Note 1: Before removing or inserting boards from / to the chassis, attach a wrist strap
for electrostatic discharge (ESD) and connect it to the rack frame using an
alligator clip.
Note 2: Do not set components down without protecting them with a static bag.
3.2.3.1 Inserting Boards
¾ To insert the TP-1610 board into the chassis, take these 3 steps:
1. Choose an available slot in a compactPCI™ chassis and gently insert the TP-1610 board
into it; as the TP-1610 board is inserted, the black plastic handles, at both ends of the
board’s front panel, must engage with the chassis. When the TP-1610 board is firmly
mounted into the correct position inside the chassis, the red plastic latches within each
handle self-lock (this also ensures that the TP-1610 board is properly earthed via the
chassis) and the blue hot-swap LED is lit.
2. Wait for the blue hot-swap LED to turn off, indicating that the board has been inserted
correctly and the power supply is functioning correctly.
3. Fasten the screws on the front panel of the board to secure the board to the chassis.
¾ To insert the TP-1610 RTM into the chassis, take these 2 steps:
1. Choose an available slot in a compactPCI™ chassis and gently insert the TP-1610 RTM into
it; as the TP-1610 RTM is inserted, the black plastic handles, at both ends of the board’s
panel, must engage with the chassis. When the TP-1610 RTM is firmly mounted into the
correct position inside the chassis, the red plastic latches within each handle self-lock (this
also ensures that the TP-1610 board is properly earthed via the chassis).
2. Fasten the screws on the front panel of the board to secure the board to the chassis.
3.2.3.2 Removing Boards
¾ To remove the TP-1610 board from the chassis, take these 3 steps:
1. Unfasten the screws on the plate of the board.
2. Press the red ejector buttons on the two black ejector/injector latches on both ends and wait
for the hot-swap blue LED to light, indicating that the board can be removed.
3. Pull on the two ejector/injector latches and ease out the board from the slot.
¾ To remove the TP-1610 RTM from the chassis, take these 4 steps:
1. Remove the cables attached to the RTM.
2. Unfasten the screws on the brackets at both ends of the panel that secure the RTM to the
chassis.
3. Press the red ejector buttons on the two black ejector/injector latches on both ends.
4. Grasp the panel and ease the RTM board out of the slot.
3.2.4 Cabling the TP-1610
¾ To cable the TP-1610, take these 3 steps:
1. Connect the E1/T1 trunk interfaces (refer to Section 3.1.4.1 on page 45).
2. Install the Ethernet connection (refer to Section
3.1.4.2 on page 46).
3. Optionally, connect the TP-1610 RS-232 port to your PC (refer to Section
3.1.4.3 on page
46).
Page 51
Mediant Series and TP-1610 H.323 User’s Manual 3. Installation
Version 4.6 51 July 2005
3.3 Installing the Mediant 1000
¾ To install your Mediant 1000, take these 4 steps:
1. Unpack the Mediant 1000 (refer to Section 3.3.1 below).
2. Check the package contents (refer to Section
3.3.2 below).
3. Mount the Mediant 1000 (refer to Section
3.3.3 on page 51).
4. Cable the Mediant 1000 (refer to Section
3.3.4 on page 53).
After connecting the Mediant 1000 to the power source, the power LED on the front panel of the
power supply unit is lit green (after a self-testing period of about 2 minutes). Any power supply
malfunction results in the LED switching off (refer to Table
2-11 on page 35 for details on the
Mediant 1000 LEDs).
When you have completed the above relevant sections you are then ready to start configuring the
gateway (Section
4 on page 57).
3.3.1 Unpacking
¾ To unpack the Mediant 1000, take these 6 steps:
1. Open the carton and remove packing materials.
2. Remove the Mediant 1000 from the carton.
3. Check that there is no equipment damage.
4. Check, retain and process any documents.
5. Notify AudioCodes or your local supplier of any damage or discrepancies.
6. Retain any diskettes or CDs.
3.3.2 Package Contents
Ensure that in addition to the Mediant 1000, the package contains:
• One or two AC power cables.
• Four anti-slide bumpers for desktop installation option (supplied in a small plastic bag).
• CD (software and documentation).
• RS-232 DB9 adapting cable, two meters in length (direct connection to PC).
• The Mediant 1000 Fast Track Installation Guide.
3.3.3 Mounting the Mediant 1000
The Mediant 1000 can be mounted on a desktop, or installed in a standard 19-inch rack. For
detailed information on cabling the Mediant 1000, refer to Section
3.3.4 on page 53.
3.3.3.1 Mounting the Mediant 1000 on a Desktop
The integral front brackets are not required for a desktop installation. Optionally, attach the four
(supplied) anti-slide bumpers to the base of the Mediant 1000 and place it on the desktop in the
position you require.
Page 52
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 52 Document #: LTRT-69903
3.3.3.2 Installing the Mediant 1000 in a 19-inch Rack
Users can install the Mediant 1000 in a standard 19-inch rack either by placing it on a shelf
preinstalled in the rack (preferred method), or by attaching it directly to the rack’s frame. If the
rack is without shelves, it is advised to acquire shelves.
Installation of a Mediant 1000 in a rack without shelves requires users to directly attach the
Mediant 1000 integral front brackets and the user-adapted rear brackets (not provided) to the
rack’s frame.
Note: Users assembling the rear brackets by themselves should note the following:
• The distance between the screws on each bracket is 28 mm.
• To attach the brackets, use 4-40 screws with a maximal box penetration length of
3.5 mm.
¾ To place the Mediant 1000 on a 19-inch rack’s shelf, take these 2 steps:
1. Place the Mediant 1000 on a preinstalled shelf.
2. It is recommended to attach the Mediant 1000 integral front brackets to the frame of the rack
to prevent it from sliding off the shelf during cabling. Use standard 19-inch rack bolts (not
provided) to fasten the front of the Mediant 1000 to the frame of the rack.
¾ To install the Mediant 1000 in a rack without shelves, take these 2 steps:
1. Position the Mediant 1000 in your 19-inch rack and align the front and rear bracket holes to
holes (of your choosing) in the vertical tracks of the 19-inch rack.
2. Use standard 19-inch rack bolts (not provided) to fasten the brackets to the frame of the
rack.
Rack Mount Safety Instructions (UL)
When installing the chassis in a rack, be sure to implement the following safety
instructions recommended by Underwriters Laboratories:
• Elevated Operating Ambient - If installed in a closed or multi-unit rack assembly,
the operating ambient temperature of the rack environment may be greater than
room ambient. Therefore, consideration should be given to installing the equipment
in an environment compatible with the maximum ambient temperature (Tma)
specified by the manufacturer.
• Redu ced Air Flow - Installation of the equipment in a rack should be such that the
amount of air flow required for safe operation on the equipment is not compromised.
• Mechanical Loading - Mounting of the equipment in the rack should be such that a
hazardous condition is not achieved due to uneven mechanical loading.
• Circuit Overloading - Consideration should be given to the connection of the
equipment to the supply circuit and the effect that overloading of the circuits might
have on overcurrent protection and supply wiring. Appropriate consideration of
equipment nameplate ratings should be used when addressing this concern.
• Reliable Earthing - Reliable earthing of rack-mounted equipment should be
maintained. Particular attention should be given to supply connections other than
direct connections to the branch circuit (e.g., use of power strips.)
Page 53
Mediant Series and TP-1610 H.323 User’s Manual 3. Installation
Version 4.6 53 July 2005
3.3.4 Cabling the Mediant 1000
Protective Earthing
The equipment is classified as Class I EN60950 and UL60950 and must be earthed at all
times.
To protect against electrical shock and fire, use a 26 AWG min wire to connect T1 or E1
ports to the PSTN.
¾ To cable the Mediant 1000, take these 7 steps:
1. The Mediant 1000 must be permanently earthed using an equipment-earthing conductor.
Connect an electrically earthed strap of 16 AWG wire (minimum) to the chassis earthing
screw, using the supplied washer. The connection to the protective earthing should be in
accordance with the regulations enforced in the country of installation.
2. Connect the E1/T1 trunk cables to the ports on the I/O module/s. Connect the other ends of
the trunk cables to your PBX/PSTN switch.
For a 1+1 or 2+2 fallback option, connect trunks 1 and 3 to your PBX and trunks 2 and 4 to
the PSTN. If the power fails, a relay connects trunks 1 to 2 and 3 to 4 (in the same module)
acting as a fallback for PSTN trunks.
RJ-48c trunk connectors are wired according to Figure
3-11 below.
3. Connect the first Ethernet connection (labeled I), located on the CPU module of the Mediant
1000 front panel, directly to the network using a standard RJ-45 Ethernet cable (and the
second connection as optional redundancy / backup). Note that for redundant operation it is
recommended to connect each of the Ethernet connectors to a different switch. For the
connector’s pinout, refer to Figure
3-12 on page 54.
When assigning an IP address to the Mediant 1000 using HTTP (under step
1 in Section
4.2.1), you may be required to disconnect this cable and re-cable it differently.
4. Optionally, connect the Mediant 1000 RS-232 port to your PC (refer to Section
3.3.4.1 on
page 54). The RS-232 port is used to access the CLI (Section
15 on page 229) and to
receive error / notification messages.
5. If you want to set up a dry contact system (future support), refer to Section
3.3.4.2 on page
54.
6. If you want to set up an audio system (future support), refer to Section
3.3.4.3 on page 55.
7. Connect the left (active) 100-240V~50-60 Hz power socket to the mains using the supplied
cord. For detailed information on the power supply module, refer to Section
2.3.1.3 on page
32.
Figure
3-11: Pinout of the RJ-48c Trunk Connectors
1 2 3 4 5 6 7 8
3, 6, 7, 8
not connected
body = shield
1 = Rx RING
2 = Rx TIP
4 = Tx RING
5 = Tx TIP
RJ-48c Connector and Pinout
Page 54
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 54 Document #: LTRT-69903
Figure 3-12: RJ-45 Ethernet Connector Pinout
1 2 3 4 5 6 7 8
4, 5, 7, 8
not
connected
1 - Tx+
2 - Tx3 - Rx+
6 - Rx-
3.3.4.1 Connecting the Mediant 1000 RS-232 Port to Your PC
Using the supplied RS-232 cable (shown in Figure 3-13) connect the Mediant 1000 RS-232 port
(Labeled I0I0) to either COM1 or COM2 RS-232 communication port on your PC.
For information on establishing a serial communications link with the Mediant 1000, refer to
Section
11.2 on page 185.
Figure
3-13: Supplied RS-232 Cable
3.3.4.2 Setting up a Dr y Contact System3
The dry contact wires’ mate (refer to Figure 3-14) is supplied. (It should be inserted in the dry
contact connector on the CPU module’s front panel).
Figure
3-14: Dry Contact Wires’ Mate
Table
3-4: Dry Contact Wires’ Mate Component Descriptions
Item # Component Description
1
Position 4
2
4 spring-cage connections
3
Orange Buttons: Press to open spring-cage connections
4
Position 1
3
Not currently supported. Contact AudioCodes regarding availability.
4
3
1
2
Page 55
Mediant Series and TP-1610 H.323 User’s Manual 3. Installation
Version 4.6 55 July 2005
The mate features four spring-cage connections:
Positions 4, 3, 2 and 1 (from left to right) correspond to the four pins in the connector on the CPU
module’s front panel.
Users need to supply their own wiring (to be inserted into the mate’s spring-cage connections) as
well as visual and/or audible alarm systems attached at the other end of the wires. The dry
contact connector can utilize wire sizes in the range 20 to 28 AWG.
¾ To set up a dry contact system, take these 3 steps:
Note: The dry contact alarm provided on the CPU card should be connected only to
SELV (Safety Extra-Low Voltage) non-energy hazard sources (Class 2) as
per UL60950 and EN60950.
1. Insert two wires into the mate’s spring-cage connections in position 4 and 3 (represented by
labels 14 and 15 in Figure
2-5 and Figure 3-14). With a sharp, pointed object press the
corresponding orange button in; the cage of the connection opens. Insert the wire into the
connection and release the orange button; the cage closes, locking in the wire.
During normal operation, dry contact labeled I is open. If a malfunction occurs, dry contact
labeled I closes.
2. Connect two additional wires into the mate’s spring-cage connections in position 2 and 1
(represented by label II in Figure
2-5) (refer also to Figure 3-14).
During normal operation, dry contact labeled II is closed. If a malfunction occurs, dry contact
labeled II opens.
3. Connect the other ends of the dry contact wiring to the alerts (alarm, siren or light) according
to your preferences and requirements.
3.3.4.3 Connecting the Audio IN/OUT Cable4
The audio cable (refer to Figure 3-15 below) splits into two RCA connectors; one is a standard
color-coded red RCA connector for IN (Input) and the other is a standard color-coded black RCA
connector for OUT (Output). Connect the red RCA input connector to your music-on-hold system,
and connect the black RCA output connector to your loudspeaker to enable paging.
Table
3-5: Audio Levels
Audio IN Level
The audio IN level must be below the AC signal 2V PTP (peak-to-peak).
Audio OUT Level
The audio OUT level is variable but must not exceed 3V PTP.
Figure 3-15: Audio Cable and IN/OUT RCA Connectors
4
Not currently supported. Contact AudioCodes regarding availability.
Page 56
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 56 Document #: LTRT-69903
Reader's Notes
Page 57
Mediant Series and TP-1610 H.323 User’s Manual4 4. Getting Started
Version 4.6 57 July 2005
4 Getting Started
The Mediant 2000 is composed of one or two identical media gateway modules. These media
gateways are fully independent, each gateway having its own MAC and IP addresses (Table
4-1
shows the default IP addresses of the Mediant 2000).
Before you begin configuring each gateway, change its default IP address to correspond with
your network environment (refer to Section
4.2) and learn about the configuration methods
available on the Mediant 2000 (refer to Section
4.1 below).
For information on quickly setting up the Mediant 2000 with basic parameters using a standard
Web browser, refer to Section
4.3 on page 59.
Table
4-1: Default Networking Parameters
Mediant 2000 Version Default Value
Mediant 2000 and TP-1610 with a single module
(up to 8 trunks) configuration, and Mediant 1000
10.1.10.10
Mediant 2000 and TP-1610 with a double module
(16 trunks) configuration
10.1.10.10 (trunks 1-8) and 10.1.10.11 (trunks 9-16)
Default subnet mask is 255.255.0.0, default gateway IP address is 0.0.0.0
4.1 Configuration Concepts
Users can utilize the Mediant 2000 in a wide variety of applications, enabled by its parameters
and configuration files (e.g., Call Progress Tones (CPT)). The parameters can be configured and
configuration files can be loaded using:
• A standard Web Browser (described and explained in Section
5 on page 61).
• A configuration file referred to as the ini file. For information on how to use the ini file, refer to
Section
6 on page 113.
• An SNMP browser software (refer to Section
15 on page 229).
• The embedded Command Line Interface (refer to Section
15 on page 229).
• AudioCodes’ Element Management System (EMS) (refer to Section
16.9 on page 245 and to
AudioCodes’ EMS User’s Manual or EMS Product Description).
To upgrade the Mediant 2000 (load new software or configuration files onto the gateway) use the
Software Upgrade wizard, available through the Web Interface (refer to Section
5.8.1 on page
104), or alternatively use the BootP/TFTP configuration utility (refer to Section
7.3.1 on page
160).
For information on the configuration files, refer to Section
17 on page 247.
Page 58
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 58 Document #: LTRT-69903
4.2 Assigning the Mediant 2000 IP Address
To assign an IP address to each of the Mediant 2000 modules use one of the following methods:
• HTTP using a Web browser (refer to Section
4.2.1 below).
• BootP (refer to Section
4.2.2 on page 59).
• Dynamic Host Control Protocol (DHCP) (refer to Section
7.2 on page 159).
• Embedded command line interface (refer to Section
15 on page 229).
Use the ‘Reset’ button at any time to restore the Mediant 2000 networking parameters to their
factory default values (refer to Section
11.1 on page 185).
4.2.1 Assigning an IP Address Using HTTP
¾ To assign an IP address using HTTP, take these 9 steps:
1. Disconnect the Mediant 2000 from the network and reconnect it to your PC using one of the
following two methods:
¾ Use a standard Ethernet cable to connect the network interface on your PC to a port on
a network hub / switch. Use a second standard Ethernet cable to connect the Mediant
2000 to another port on the same network hub / switch.
¾ Use an Ethernet cross-over cable to directly connect the network interface on your PC to
the Mediant 2000.
2. Change your PC’s IP address and subnet mask to correspond with the Mediant 2000 factory
default IP address and subnet mask, shown in Table
4-1. For details on changing the IP
address and subnet mask of your PC, refer to Windows™ Online Help (Start>Help).
3. Access the Mediant 2000 first module’s Embedded Web Server (refer to Section
5.3 on page
62).
4. In the ‘Quick Setup’ screen (shown in Figure
4-1), set the Mediant 2000 ‘IP Address’,
‘Subnet Mask’ and ‘Default Gateway IP Address’ fields under ‘IP Configuration’ to
correspond with your network IP settings. If your network doesn’t feature a default gateway,
enter a dummy value in the ‘Default Gateway IP Address’ field.
5. Click the Reset button and click OK in the prompt; the Mediant 2000 applies the changes
and restarts.
Tip: Record and retain the IP address and subnet mask you assign the Mediant
2000. Do the same when defining new username or password. If the
Embedded Web Server is unavailable (for example, if you’ve lost your
username and password), use the BootP/TFTP (Trivial File Transfer Protocol)
configuration utility to access the device, ‘reflash’ the load and reset the
password (refer to Section Appendix B on page 263 for detailed information
on using a BootP/TFTP configuration utility to access the device).
6. Repeat steps 3 to 5 for the Mediant 2000 second module (if used).
7. Disconnect your PC from the Mediant 2000 or from the hub / switch (depending on the
connection method you used in step
1).
8. Reconnect the Mediant 2000 and your PC (if necessary) to the network.
9. Restore your PC’s IP address and subnet mask to what they originally were. If necessary,
restart your PC and re-access the Mediant 2000 via the Embedded Web Server with its new
assigned IP address.
Page 59
Mediant Series and TP-1610 H.323 User’s Manual4 4. Getting Started
Version 4.6 59 July 2005
4.2.2 Assigning an IP Address Using BootP
Note: BootP procedure can also be performed using any standard compatible
BootP server.
Tip: You can also use BootP to load the auxiliary files to the Mediant 2000 (refer
to Section 6.16 on page 158).
¾ To assign an IP address using BootP, take these 4 steps:
1. Open the BootP application (supplied with the Mediant 2000 software package).
2. Add client configuration for the gateway that you want to initialize, refer to Section
B.11.1 on
page 269.
3. Use the reset button to physically reset the gateway causing it to use BootP; the Mediant
2000 changes its network parameters to the values provided by the BootP.
4. Repeat steps 2 and 3 for the Mediant 2000 second module (if used).
4.3 Configuring the Mediant 2000 Basic Parameters
To configure the Mediant 2000 basic parameters use the Embedded Web Server’s ‘Quick Setup’
screen (shown in Figure
4-1 below). Refer to Section 5.3 on page 62 for information on accessing
the ‘Quick Setup’ screen.
Figure
4-1: Mediant 2000 Quick Setup Screen
Page 60
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 60 Document #: LTRT-69903
¾ To configure basic H.323 parameters, take these 8 steps:
1. If the Mediant 2000 is connected to a router with NAT (Network Address Translation)
enabled, perform the following procedure. If it isn’t, leave the ‘NAT IP Address’ field
undefined.
¾ Determine the ‘public’ IP address assigned to the router (by using, for instance, router
Web management). Enter this public IP address in the ‘NAT IP Address’ field.
¾ Enable the DMZ (Demilitarized Zone) configuration on the residential router for the LAN
port where the Mediant 2000 gateway is connected. This enables unknown packets to
be routed to the DMZ port.
2. When working with a Gatekeeper, under ‘H.323 Parameters’, set ‘Working with Gatekeeper’
field to ‘Yes’ and enter the IP address of the primary Gatekeeper in the field ‘Gatekeeper IP
Address’. When no Gatekeeper is used, the internal routing table is used to route the calls.
3. Leave parameter ‘Enable Annex D/T.38 FAX Relay’ at its default unless your technical
requirements differ.
4. Select the coder (i.e., vocoder) that best suits your VoIP system requirements. The default
coder is: G.7231 30 msec. To program the entire list of coders you want the Mediant 2000 to
use, click the button on the left side of the ‘1
st
Coder’ field; the drop-down lists for the 2nd to
5
th
coders appear. Select coders according to your system requirements. Note that coders
higher on the list are preferred and take precedence over coders lower on the list.
Note: The preferred coder is the coder that the Mediant 2000 uses as a first choice
for all connections. If the far end gateway does not use this coder, the
Mediant 2000 negotiates with the far end gateway to select a coder that both
sides can use.
5. To program the Tel to IP Routing Table, press the arrow button next to ‘Tel to IP Routing
Table’. For information on how to configure the Tel to IP Routing Table, refer to Section
5.5.4.1 on page 70.
6. To program the E1/T1 B-channels, press the arrow button next to ‘Trunk Group Table’. For
information on how to configure the Trunk Group Table, refer to Section
5.5.7 on page 82.
7. Click the Reset button and click OK in the prompt; the Mediant 2000 applies the changes
and restarts.
8. After the gateway was reset, access the Advanced Configuration>Trunk Settings page, and
select the gateway’s E1/T1 protocol type and Framing method that best suits your system
requirements. Note that for E1 spans, the framing method must always be set to ‘Extended
Super Frame’. For information on how to configure the Trunk Settings, refer to Section
5.6.3
on page 89.
You are now ready to start using the gateway. To prevent unauthorized access to the Mediant
2000, it is recommended that you change the username and password that are used to access
the Web Interface. Refer to Section
5.6.7 on page 94 for details on how to change the username
and password.
Tip: Once the gateway is configured correctly back up your settings by making a
copy of the VoIP gateway configuration (ini file) and store it in a directory on
your PC. This saved file can be used to restore configuration settings at a
future time. For information on backing up and restoring the gateway’s
configuration, refer to Section 5.6.5 on page 92.
Page 61
Mediant Series and TP-1610 H.323 User’s Manual 5. Web Management
Version 4.6 61 July 2005
5 Web Management
The Embedded Web Server is used both for gateway configuration, including loading of
configuration files, and for run-time monitoring. The Embedded Web Server can be accessed
from a standard Web browser, such as Microsoft™ Internet Explorer, Netscape™ Navigator, etc.
Specifically, users can employ this facility to set up the gateway configuration parameters. Users
also have the option to remotely reset the gateway and to permanently apply the new set of
parameters.
5.1 Computer Requirements
To use the Embedded Web Server, the following is required:
• A computer capable of running your Web browser.
• A network connection to the VoIP gateway.
• One of the following compatible Web browsers:
¾ Microsoft™ Internet Explorer™ (version 6.0 and higher).
¾ Netscape™ Navigator™ (version 7.2 and higher).
Note: The browser must be Java-script enabled. If java-script is disabled, access to
the Embedded Web Server is denied.
5.2 Protection and Security Mechanisms
Access to the Embedded Web Server is controlled by the following protection and security
mechanisms:
• Dual access level username and password (refer to Section
5.2.1 below).
• Read-only mode (refer to Section
5.2.2 below).
• Disabling access (refer to Section
5.2.3 below).
• Secured HTTP connection (HTTPS) (refer to Section
13.1.1 on page 219).
• Limiting access to a predefined list of IP addresses (refer to Section
5.6.1.2 on page 86).
• Managed access using a RADIUS server (refer to Section
13.2 on page 223).
5.2.1 Dual Access Level Username and Password
To prevent unauthorized access to the Embedded Web Server, two levels of security are
available: Administrator (also used for Telnet access) and Monitoring. Each employs a different
username and password. Users can access the Embedded Web Server as either:
• Administrator - all Web screens are read-write and can be modified.
Default username ‘Admin’.
Default password ‘Admin’.
• Monitoring - all Web screens are read-only and cannot be modified. In addition, the following
screens cannot be accessed: ’Reset‘, ‘Save Configuration‘, ‘Software Upgrade Wizard’, ‘Load
Auxiliary Files’, ‘Configuration File’ and ‘Regional Settings’. The ’Change Password‘ screen
can only be used to change the monitoring password.
Default username ‘User’.
Default password ‘User’.
Page 62
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 62 Document #: LTRT-69903
The first time a browser request is made, the user is requested to provide his Administrator or
Monitoring username and password to obtain access. Subsequent requests are negotiated by the
browser on behalf of the user, so that the user doesn’t have to re-enter the username and
password for each request, but the request is still authenticated (the Embedded Web Server uses
the MD5 authentication method supported by the HTTP 1.1 protocol).
For details on changing the Administrator and Monitoring username and password, refer to
Section
5.6.7 on page 94. Note that the password and username can be a maximum of 19 case-
sensitive characters.
To reset the Administrator and Monitoring username and password to their defaults, enable the
ini file parameter ‘ResetWebPassword’.
5.2.2 Limiting the Embedded Web Server to Read-Only Mode
Users can limit access to the Embedded Web Server to read-only mode by changing the ini file
parameter ‘DisableWebConfig’ to 1. In this mode all Web screens, regardless to the access level
used (Administrator or Monitoring), are read-only and cannot be modified. In addition, the
following screens cannot be accessed: ‘Quick Setup’, ‘Change Password’, ’Reset‘, ‘Save
Configuration‘, ‘Software Upgrade Wizard’, ‘Load Auxiliary Files’, ‘Configuration File’ and
‘Regional Settings’.
5.2.3 Disabling the Embedded Web Server
Access to the Embedded Web Server can be disabled by using the ini file parameter
‘DisableWebTask = 1’. The default is access enabled.
5.3 Accessing the Embedded Web Server
¾ To access the Embedded Web Server, take these 4 steps:
1. Open a standard Web-browsing application such as Microsoft™ Internet Explorer™ or
Netscape™ Navigator™.
2. In the Uniform Resource Locator (URL) field, specify the IP address of the Mediant 2000
(e.g., http://10.1.10.10); the Embedded Web Server’s ‘Enter Network Password’ screen
appears, shown in Figure
5-1.
Figure
5-1: Embedded Web Server Login Screen
3. In the ‘User Name’ and ‘Password’ fields, enter the username (default: ‘Admin’) and
password (default: ‘Admin’). Note that the username and password are case-sensitive.
4. Click the OK button; the ‘Quick Setup’ screen is accessed (shown in Figure
4-1).
Page 63
Mediant Series and TP-1610 H.323 User’s Manual 5. Web Management
Version 4.6 63 July 2005
5.3.1 Using Internet Explorer to Access the Embedded Web Server
Internet explorer’s security settings may block access to the gateway’s Web browser if they’re
configured incorrectly. In this case, the following message is displayed:
Unauthorized
Correct authorization is required for this area. Either your browser does not perform
authorization or your authorization has failed. RomPager server.
¾ To troubleshoot blocked access to Internet Explorer, take these 2
steps:
1. Delete all cookies from the Temporary Internet files. If this does not clear up the problem, the
security settings may need to be altered (refer to Step 2).
2. In Internet Explorer, Tools, Internet Options select the Security tab, and then select Custom
Level. Scroll down until the Logon options are displayed and change the setting to Prompt
for username and password and then restart the browser. This fixes any issues related to
domain use logon policy.
5.4 Getting Acquainted with the Web Interface
Figure 5-2 shows the general layout of the Web Interface screen.
Figure
5-2: Mediant 2000 Web Interface
The Web Interface screen features the following components:
• Title bar - contains three configurable elements: corporate logo, a background image and the
product’s name. For information on how to modify these elements, refer to Section
11.6 on
page 194.
• Main menu bar - always appears on the left of every screen to quickly access parameters,
submenus, submenu options, functions and operations.
Main Menu
Ba
r
Corporate
Lo
g
o
Submenu
Ba
r
Title Bar
Main Action
Frame
Control
Protocol
MG Module
Page 64
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 64 Document #: LTRT-69903
• Submenu bar - appears on the top of screens and contains submenu options.
• Main action frame - the main area of the screen in which information is viewed and
configured.
• Corporate logo – AudioCodes’ corporate logo. For information on how to remove this logo,
refer to Section
11.6 on page 194.
• Control Protocol – the Mediant 2000 control protocol.
• MG Module – the Mediant 2000 media gateway module (Module 1 or Module 2).
5.4.1 Main Menu Bar
The main menu bar of the Web Interface is divided into the following 7 menus:
• Quick Setup – Use this menu to configure the gateway’s basic settings; for the full list of
configurable parameters go directly to ‘Protocol Management’ and ‘Advanced Configuration’
menus. An example of the Quick Setup configuration is described in Section
4.3 on page 59.
• Protocol Management – Use this menu to configure the gateway’s control protocol
parameters and tables (refer to Section
5.5 on page 65).
• Advanced Configuration – Use this menu to set the gateway’s advanced configuration
parameters (for advanced users only) (refer to Section
5.6 on page 85).
• Status & Diagnostics – Use this menu to view and monitor the gateway’s channels, Syslog
messages, hardware / software product information, and to assess the gateway’s statistics
and IP connectivity information (refer to Section
5.7 on page 95).
• Software Update – Use this menu when you want to load new software or configuration files
onto the gateway (refer to Section
5.8 on page 104).
• Save Configuration – Use this menu to save configuration changes to the non-volatile flash
memory (refer to Section
5.9 on page 110).
• Reset – Use this menu to remotely reset the gateway. Note that you can choose to save the
gateway configuration to flash memory before reset (refer to Section
5.9 on page 110).
When positioning your curser over a parameter name (or a table) for more than 1 second, a short
description of this parameter is displayed. Note that those parameters that are preceded with an
exclamation mark (!) are not changeable on-the-fly and require reset.
5.4.2 Saving Changes
To save changes to the volatile memory (RAM) press the Submit button (changes to parameters
with on-the-fly capabilities are immediately available, other parameter are updated only after a
gateway reset). Parameters that are only saved to the volatile memory revert to their previous
settings after hardware reset. When performing a software reset (i.e., via Web or SNMP) you can
choose to save the changes to the non-volatile memory. To save changes so they are available
after a power fail, you must save the changes to the non-volatile memory (flash). When Save
Configuration is performed, all parameters are saved to the flash memory.
To save the changes to flash, refer to Section
5.9 on page 110.
5.4.3 Entering Phone Numbers in Various Tables
Phone numbers entered into various tables on the gateway, such as the Tel to IP routing table,
must be entered without any formatting characters. For example, if you wish to enter the phone
number 555-1212, it must be entered as 5551212 without the hyphen (-). If the hyphen is entered,
the entry does not work. The hyphen character is used in number entry only, as part of a range
definition. For example, the entry [20-29] means ‘all numbers in the range 20 to 29’.
Page 65
Mediant Series and TP-1610 H.323 User’s Manual 5. Web Management
Version 4.6 65 July 2005
5.5 Protocol Management
Use this menu to configure the gateway’s H.323 parameters and tables.
5.5.1 Protocol Definition Parameters
Use this submenu to configure the following gateway’s specific H.323 protocol parameters:
• General Parameters
• Gatekeeper Parameters
• Coders (refer to Section
5.5.1.1 below)
• DTMF & Dialing Parameters
5.5.1.1 Coders
From the Coders screen you can configure the first to fifth preferred coders (and their
corresponding ptimes) for the gateway. The first coder is the highest priority coder and is used by
the gateway whenever possible. If the far end gateway cannot use the coder assigned as the first
coder, the gateway attempts to use the next coder and so forth.
¾ To configure the gateway’s coders, take these 6 steps:
1. Open the ‘Coders’ screen (Protocol Management menu > Protocol Definition submenu >
Coders option); the ‘Coders’ screen is displayed.
Figure
5-3: Coders Screen
2. From the coder drop-down list, select the coder you want to use. For the full list of available
coders and their corresponding ptimes, refer to the ini file parameter ‘CoderName’
(described in Table
6-6).
Note: Each coder can appear only once.
3. From the drop-down list to the right of the coder list, select the size of the Voice Packet
(ptime) used with this coder in milliseconds. Selecting the size of the packet determines how
many coder payloads are combined into one RTP (Real-Time Transport Protocol) (voice)
packet.
Note 1: The ptime packetization period depends on the selected coder name.
Note 2: If not specified, the ptime gets a default value.
Note 3: The ptime specifies the maximum packetization time the gateway can receive.
4. Repeat steps 2 and 3 for the second to fifth coders (optional).
5. Click the Submit button to save your changes.
6. To save the changes so they are available after a power fail, refer to Section
5.9 on page
110.
Page 66
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 66 Document #: LTRT-69903
5.5.2 Advanced Parameters
Use this submenu to configure the following gateway’s advanced control protocol parameters.
• Disconnect and Answer Supervision
• CDR and Debug
• Miscellaneous Parameters
• Supplementary Services
5.5.3 Number Manipulation Tables
The VoIP gateway provides four Number Manipulation tables for incoming and outgoing calls.
These tables are used to modify the destination and source telephone numbers so that the calls
can be routed correctly.
The Manipulation Tables are:
• Destination Phone Number Manipulation Table for IPÆTel calls
• Destination Phone Number Manipulation Table for TelÆIP call
• Source Phone Number Manipulation Table for IPÆTel calls
• Source Phone Number Manipulation Table for TelÆIP calls
Note: Number manipulation can be performed either before or after a routing
decision is made. For example, you can route a call to a specific trunk group
according to its original number, and then you can remove/add a prefix to that
number before it is routed. To control when number manipulation is done, set
the RouteModeIP2Tel and the RouteModeTel2IP parameters. For information
on these parameters, refer to Table 6-8 on page 142.
Possible uses for number manipulation can be as follows:
• To strip/add dialing plan digits from/to the number. For example, a user could dial 9 in front
of each number in order to indicate an external line. This number (9) can be removed here
before (after) the call is setup.
• Assignment of NPI/TON to TelÆIP and IPÆTel calls. The VoIP gateway can use a single
global setting for NPI/TON classification or it can use the setting in this table on a call by call
basis. Control for this is done using ‘Protocol Management>Protocol
Definition>Destination/Source Number Encoding Type’.
• Allow / disallow Caller ID information to be sent according to destination / source prefixes.
¾ To configure the Number Manipulation tables, take these 5 steps:
1. Open the Number Manipulation screen you want to configure (Protocol Management menu
> Manipulation Tables submenu); the relevant Manipulation table screen is displayed.
Figure
5-4 shows the ‘Source Phone Number Manipulation Table for TelÆIP calls’.
Page 67
Mediant Series and TP-1610 H.323 User’s Manual 5. Web Management
Version 4.6 67 July 2005
Figure 5-4: Source Phone Number Manipulation Table for TelÆIP Calls
2. In the ‘Table Index’ drop-down list, select the range of entries that you want to edit (up to 20
entries can be configured for Source Number Manipulation and 50 entries for Destination
Number Manipulation).
3. Configure the Number Manipulation table according to Table
5-1.
4. Click the Submit button to save your changes.
5. To save the changes so they are available after a power fail, refer to Section
5.9 on page
110.
Table
5-1: Number Manipulation Parameters
Parameter Description
Destination Prefix Each entry in the Destination Prefix fields represents a destination telephone number
prefix. An asterisk (*) represents any number.
Source Prefix Each entry in the Source Prefix fields represents a source telephone number prefix.
An asterisk (*) represents any number.
Source IP Each entry in the Source IP fields represents the source IP address of the call
(obtained from the Setup message).
This column only applies to the ‘Destination Phone Number Manipulation Table for IP
to Tel’.
Note: The source IP address can include the ‘x’ wildcard to represent single
digits. For
example: 10.8.8.xx represents all the addresses between 10.8.8.10 to 10.8.8.99.
The manipulation rules are applied to any incoming call whose:
• Destination number prefix matches the prefix defined in the ‘Destination Number’ field.
• Source number prefix matches the prefix defined in the ‘Source Prefix’ field.
• Source IP address matches the IP address defined in the ‘Source IP’ field (if applicable).
Note that number manipulation can be performed using a combination of each of the above criteria, or using each
criterion independently.
Note: For available notations that represent multiple numbers, refer to Section 5.5.3.1 on page 68.
Num of stripped digits
• Enter the number of digits that you want to remove from the left of the telephone
number prefix. For example, if you enter 3 and the phone number is 5551234, the
new phone number is 1234.
• Enter the number of digits (in brackets) that you want to remove from the right of
the telephone number prefix.
Note: A combination of the two options is allowed (e.g., 2(3)).
Prefix / Suffix to add
• Prefix - Enter the number / string you want to add to the front of the phone number.
For example, if you enter 9 and the phone number is 1234, the new number is
91234.
• Suffix - Enter the number / string (in brackets) you want to add to the end of the
phone number. For example, if you enter (00) and the phone number is 1234, the
new number is 123400.
Note: You can enter a prefix and a suffix in the same field (e.g., 9(00)).
Page 68
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 68 Document #: LTRT-69903
Table 5-1: Number Manipulation Parameters
Parameter Description
Number of digits to leave Enter the number of digits that you want to leave from the right.
Note: The manipulation rules are executed in the following order:
1. Num of stripped digits
2. Number of digits to leave
3. Prefix / suffix to add
Figure 5-4 on the previous page exemplifies the use of these manipulation rules in the ‘Source Phone Number
Manipulation Table for TelÆIP Calls’:
• When destination number equals 035000 and source number equals 20155, the source number is changed to
97220155.
• When source number equals 1001876, it is changed to 587623.
• Source number 1234510012001 is changed to 20018.
• Source number 3122 is changed to 2312.
NPI Select the Number Plan assigned to this entry.
You can select Unknown [0], Private [9] or E.164 Public [1].
The default is Unknown.
For a detailed list of the available NPI/TON values, refer to Section 5.5.3.2 on page
69.
TON Select the Number Type assigned to this entry.
• If you selected Unknown as the Number Plan, you can select Unknown [0].
• If you selected Private as the Number Plan, you can select Unknown [0], Level 2
Regional [1], Level 1 Regional [2], PSTN Specific [3] or Level 0 Regional (Local)
[4].
• If you selected E.164 Public as the Number Plan, you can select Unknown [0],
International [1], National [2], Network Specific [3], Subscriber [4] or Abbreviated
[6].
The default is Unknown.
Presentation Select ‘Allowed’ to send Caller ID information when a call is made using these
destination / source prefixes.
Select ‘Restricted’ if you want to restrict Caller ID information for these prefixes.
5.5.3.1 Dialing Plan Notation
The dialing plan notation applies, in addition to the four Manipulation tables, also to TelÆIP
Routing table and to IPÆTrunk Group Routing table.
When entering a number in the destination and source ‘Prefix’ columns, you can create an entry
that represents multiple numbers using the following notation:
• [n-m] represents a range of numbers
• [n,m] represents multiple numbers. Note that this notation only supports single digit numbers.
• x represents any single digit
• # (that terminates the number) represents the end of a number
• A single asterisk (*) represents any number
For example:
• [5551200-5551300]# represents all numbers from 5551200 to 5551300
• [2,3,4]xxx# represents four-digit numbers that start with 2, 3 or 4
• 54324 represents any number that starts with 54324
• 54324xx# represents a 7 digit number that starts with 54324
• 123[100-200]# represents all numbers from 123100 to 123200.
Page 69
Mediant Series and TP-1610 H.323 User’s Manual 5. Web Management
Version 4.6 69 July 2005
The VoIP gateway matches the rules starting at the top of the table. For this reason, enter more
specific rules above more generic rules. For example, if you enter 551 in entry 1 and 55 in entry
2, the VoIP gateway applies rule 1 to numbers that starts with 551 and applies rule 2 to numbers
that start with 550, 552, 553, 554, 555, 556, 557, 558 and 559. However if you enter 55 in entry 1
and 551 in entry 2, the VoIP gateway applies rule 1 to all numbers that start with 55 including
numbers that start with 551.
5.5.3.2 Numbering Plan and Type of Number
Numbers are classified by their Numbering Plan Indication (NPI) and their Type of Number
(TON). The Mediant 2000 supports all NPI/TON classifications used in the standard. The list of
ISDN ETSI NPI/TON values is shown as follows:
Table
5-2: NPI/TON Values for ISDN ETSI
NPI TON Description
Unknown [0] Unknown [0]
A valid classification, but one that has no information about the
numbering plan.
Unknown [0]
A public number in E.164 format, but no information on what
kind of E.164 number.
International [1]
A public number in complete international E.164 format. For
example: 16135551234
National [2]
A public number in complete national E.164 format. For
example: 6135551234
E.164 Public [1]
Subscriber [4]
A public number in complete E.164 format representing a local
subscriber. For example: 5551234
Unknown [0]
A private number, but with no further information about the
numbering plan
Level 2 Regional [1]
Level 1 Regional [2] A private number with a location. For example: 3932200
PISN Specific [3]
Private [9]
Level 0 Regional (local) [4] A private local extension number. For example: 2200
For NI-2 and DMS-100 ISDN variants the valid combinations of TON and NPI for calling and
called numbers are (Plan/Type):
• 0/0 - Unknown/Unknown
• 1/1 - International number in ISDN/Telephony numbering plan
• 1/2 - National number in ISDN/Telephony numbering plan
• 1/4 - Subscriber (local) number in ISDN/Telephony numbering plan
• 9/4 - Subscriber (local) number in Private numbering plan
Page 70
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 70 Document #: LTRT-69903
5.5.4 Configuring the Routing Tables
Use this submenu to configure the gateway’s IPÆTel and TelÆIP routing tables and their
associated parameters.
5.5.4.1 Tel to IP Routing Table
The Tel to IP Routing Table is used to route incoming Tel calls to IP addresses. This routing table
associates a called / calling telephone number’s prefixes with a destination IP address or with an
FQDN (Fully Qualified Domain Name). When a call is routed through the VoIP gateway
(Gatekeeper isn’t used), the called and calling numbers are compared to the list of prefixes on the
IP Routing Table (up to 50 prefixes can be configured); Calls that match these prefixes are sent
to the corresponding IP address. If the number dialed does not match these prefixes, the call is
not made.
When using a Gatekeeper, you do not need to configure the Telephone to IP Routing Table.
However, if you want to use fallback routing when communication with Gatekeepers is lost, or to
use the ‘Filter Calls to IP’ and IP Security features, you need to configure the IP Routing Table.
Note that for the Tel to IP Routing table to take precedence over a Gatekeeper for routing calls,
set the parameter ‘PreferRouteTable’ to 1. The gateway checks the 'Destination IP Address' field
in the 'Tel to IP Routing' table for a match with the outgoing call. Only if a match is not found, a
Gatekeeper is used.
Possible uses for Telephone to IP Routing can be as follows:
• Can fallback to internal routing table if there is no communication with the Gatekeepers.
• Call Restriction – (when Gatekeeper isn’t used), reject all outgoing TelÆIP calls that are
associated with the destination IP address: 0.0.0.0.
• IP Security - When the IP Security feature is enabled (SecureCallFromIP = 1), the VoIP
gateway accepts only those IPÆTel calls with a source IP address identical to one of the IP
addresses entered in the Telephone to IP Routing Table.
• Filter Calls to IP – When a Gatekeeper is used, the gateway checks the TelÆIP routing table
before a telephone number is routed to the Gatekeeper. If the number is not allowed
(number isn’t listed or a Call Restriction routing rule was applied), the call is released.
• Assign Profiles to destination address (also when a Gatekeeper is used).
• Alternative Routing – (When Gatekeeper isn’t used) an alternative IP destination for
telephone number prefixes is available. To associate an alternative IP address to called
telephone number prefix, assign it with an additional entry (with a different IP address), or
use an FQDN that resolves to two IP addresses. Call is sent to the alternative destination
when one of the following occurs:
¾ No ping to the initial destination is available, when poor Quality of Service (QoS) (delay
or packet loss, calculated according to previous calls) is detected, or when a Domain
Name Server (DNS) host name is not resolved. For detailed information on Alternative
Routing, refer to Section
8.6 on page 169.
¾ When a release reason that is defined in the ‘Reasons for Alternative Tel to IP Routing’
table is received. For detailed information on the ‘Reasons for Alternative Routing
Tables’, refer to Section
5.5.4.4 on page 75.
Note: If the alternative routing destination is the gateway itself, the call can be configured to
be routed back to PSTN. This feature is referred to as ‘PSTN Fallback’, meaning that if
sufficient voice quality is not available over the IP network, the call is routed through legacy
telephony system (PSTN).
Page 71
Mediant Series and TP-1610 H.323 User’s Manual 5. Web Management
Version 4.6 71 July 2005
Tip: Tel to IP routing can be performed either before or after applying the number
manipulation rules. To control when number manipulation is done, set the
RouteModeTel2IP parameter. For information on this parameter, refer to
Table 6-8 on page 142.
¾ To configure the Tel to IP Routing table, take these 6 steps:
1. Open the ‘Tel to IP Routing’ screen (Protocol Management menu > Routing Tables
submenu > Tel to IP Routing option); the ‘Tel to IP Routing’ screen is displayed (shown in
Figure
5-5).
2. In the ‘Tel to IP Routing Mode’ field, select the Tel to IP routing mode (refer to Table
6-8).
3. In the ‘Routing Index' drop-down list, select the range of entries that you want to edit.
4. Configure the Tel to IP Routing table according to Table
5-3.
5. Click the Submit button to save your changes.
6. To save the changes so they are available after a power fail, refer to Section
5.9 on page
110.
Figure
5-5: Tel to IP Routing Table Screen
Table
5-3: Tel to IP Routing Table
Parameter Description
Destination Phone Prefix Each entry in the Destination Phone Prefix fields represents a called telephone
number prefix. The prefix can be 1 to 19 digits long. An asterisk (*) represents all
numbers.
Source Phone Prefix Each entry in the Source Phone Prefix fields represents a calling telephone number
prefix. The prefix can be 1 to 19 digits long. An asterisk (*) represents all numbers.
Any telephone number whose destination number matches the prefix defined in the ‘Destination Phone Prefix’ field and
its source number matches the prefix defined in the adjacent ‘Source Phone Prefix‘ field, is sent to the IP address
entered in the ‘IP Address’ field.
Note that Tel to IP routing can be performed according to a combination of source and destination phone prefixes, or
using each independently.
Note 1: An additional entry of the same prefixes can be assigned to enable alternative routing.
Note 2: For available notations that represent multiple numbers, refer to Section 5.5.3.1 on page 68.
Destination IP Address In each of the IP Address fields, enter the IP address that is assigned to these
prefixes. Domain names, such as domain.com, can be used instead of IP addresses.
To discard outgoing IP calls, enter 0.0.0.0 in this field.
Note: When using domain names, you must enter a DNS server IP address, or
alternatively define these names in the ‘Internal DNS Table’.
Profile ID Enter the number of the IP profile that is assigned to the destination IP address
defined in the ‘Destination IP Address’ field.
Page 72
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 72 Document #: LTRT-69903
Table 5-3: Tel to IP Routing Table
Parameter Description
Status A read only field representing the quality of service of the destination IP address.
N/A = Alternative Routing feature is disabled.
OK = IP route is available
Ping Error = No ping to IP destination, route is not available
QoS Low = Bad QoS of IP destination, route is not available
DNS Error = No DNS resolution (only when domain name is used instead of an IP
address).
5.5.4.2 IP to Trunk Group Routing Table
The IP to Trunk Group Routing Table is used to route incoming IP calls to groups of E1/T1
B-channels called trunk groups. Calls are assigned to trunk groups according to any combination
of the following three options (or using each independently):
• Destination phone prefix
• Source phone prefix
• Source IP address
The call is then sent to the VoIP gateway channels assigned to that trunk group. The specific
channel, within a trunk group, that is assigned to accept the call is determined according to the
trunk group’s channel selection mode which is defined in the Trunk Group Settings table (Section
5.5.8 on page 83), or according to the global parameter ‘ChannelSelectMode’ (refer to Table 6-8
on page 142).
Note that when a Gatekeeper is used, before an incoming call is being routed to the relevant
trunk group an Admission request is sent to the Gatekeeper. Calls that aren’t authorized are
dropped. When the parameter ‘PreferRouteTable’ is set to 1, the gateway checks the 'Source IP
Address' field in the 'IP to Trunk Group Routing' table for a match with the incoming call. If such a
match is found, the call is routed. If a match is not found, an Admission request is sent to the
Gatekeeper.
Note: When a release reason that is defined in the ‘Reasons for Alternative IP to Tel Routing’
table is received for a specific IPÆTel call, an alternative trunk group for that call is available. To
associate an alternative trunk group to an incoming IP call, assign it with an additional entry in the
‘IP to Trunk Group Routing’ table (repeat the same routing rules with a different trunk group ID).
For detailed information on the ‘Reasons for Alternative Routing Tables’, refer to Section
5.5.4.4
on page 75.
To use trunk groups you must also do the following:
• You must assign a trunk group ID to the VoIP gateway E1/T1 B-channels on the Trunk
Group Table. For information on how to assign a trunk group ID to a B-channel, refer to
Section
5.5.7 on page 82.
• You can configure the Channel Select Mode table to determine the method in which new
calls are assigned to channels within the trunk groups (a different method for each trunk
group can be configured). For information on how to enable this option, refer to Section
5.5.8
on page 83. If a Channel Select Mode for a specific trunk group isn’t specified, then the
global ‘Channel Select Mode’ parameter (defined in ‘Protocol Definition’ screen) applies.
¾ To configure the IP to Trunk Group Routing table, take these 6 steps:
1. Open the ‘IP to Trunk Group Routing’ screen (Protocol Management menu > Routing
Tables submenu > IP to Trunk Group Routing option); the ‘IP to Trunk Group Routing’
table screen is displayed.
Page 73
Mediant Series and TP-1610 H.323 User’s Manual 5. Web Management
Version 4.6 73 July 2005
Figure 5-6: IP to Trunk Group Routing Table
2. In the ‘IP to Tel Routing Mode’ field, select the IP to Tel routing mode (refer to Table
6-8 on
page 142).
3. In the ‘Routing Index’ drop-down list, select the range of entries that you want to edit (up to
24 entries can be configured).
4. Configure the IP to Trunk Group Routing table according to Table
5-4.
5. Click the Submit button to save your changes.
6. To save the changes so they are available after a power fail, refer to Section
5.9 on page
110.
Table
5-4: IP to Trunk Group Routing Table
Parameter Description
Destination Phone Prefix Each entry in the Destination Phone Prefix fields represents a called
telephone number prefix. The prefix can be 1 to 49 digits long. An asterisk
(*) represents all numbers.
Source Phone Prefix Each entry in the Source Phone Prefix fields represents a calling
telephone number prefix. The prefix can be 1 to 49 digits long. An asterisk
(*) represents all numbers.
Source IP Address Each entry in the Source IP Address fields represents the source IP
address of an IPÆTel call (obtained from the Setup message).
Note: The source IP address can include the ‘x’ wildcard to represent
single
digits. For example: 10.8.8.xx represents all the addresses between
10.8.8.10 to 10.8.8.99.
Any H.323 incoming call whose destination number matches the prefix defined in the ‘Destination Phone Prefix’ field an
d
its source number matches the prefix defined in the adjacent ‘Source Phone Prefix‘ field and its source IP address
matches the address defined in the ‘Source IP Address’ field, is assigned to the trunk group entered in the field to the
right of these fields.
Note that IP to trunk group routing can be performed according to any combination of source / destination phone
prefixes and source IP address, or using each independently.
Note: For available notations that represent multiple numbers (used in the prefix columns), refer to Section 5.5.3.1 on
page 68.
Trunk Group ID In each of the Trunk Group ID fields, enter the trunk group ID to which
calls that match these prefixes are assigned.
Profile ID Enter the number of the IP profile that is assigned to the routing rule.
Page 74
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 74 Document #: LTRT-69903
5.5.4.3 Internal DNS Table
The internal DNS table, similar to a DNS resolution, translates hostnames into IP addresses. This
table is used when hostname translation is required (e.g., ‘Tel to IP Routing’ table). Two different
IP addresses can be assigned to the same hostname. If the hostname isn’t found in this table, the
gateway communicates with an external DNS server.
Assigning two IP addresses to hostname can be used for alternative routing (using the ‘Tel to IP
Routing’ table).
Note that when the DNS table is used to resolve Gatekeeper domain names only the first IP
address is used.
¾ To configure the internal DNS table, take these 7 steps:
1. Open the ‘Internal DNS Table’ screen (Protocol Management menu > Routing Tables
submenu > Internal DNS Table option); the ‘Internal DNS Table’ screen is displayed.
Figure
5-7: Internal DNS Table Screen
2. In the ‘DNS Name’ field, enter the hostname to be translated. You can enter a string up to 31
characters long.
3. In the ‘First IP Address’ field, enter the first IP address that the hostname is translated to.
4. In the ‘Second IP Address’ field, enter the second IP address that the hostname is translated
to.
5. Repeat steps 2 to 4, for each Internal DNS Table entry.
6. Click the Submit button to save your changes.
7. To save the changes so they are available after a power fail, refer to Section
5.9 on page
110.
Page 75
Mediant Series and TP-1610 H.323 User’s Manual 5. Web Management
Version 4.6 75 July 2005
5.5.4.4 Reasons for Alternative Routing
The Reasons for Alternative Routing screen includes two tables (TelÆIP and IPÆTel). Each table
enables you to define up to 4 different release reasons. If a call is released as a result of one of
these reasons (received in Q.931 presentation), the gateway tries to find an alternative route to
that call. For TelÆIP calls an alternative IP address, for IPÆTel calls an alternative trunk group.
Refer to ‘Tel to IP Routing Table’ on page 70 for information on defining an alternative IP
address. Refer to the ‘IP to Trunk Group Routing Table’ on page 72 for information on defining an
alternative trunk group.
You can use this table for example:
For IPÆTel calls, when the destination is busy, and release reason #17 is issued or for other call
releases that issue the default release reason (#3). Refer to ‘DefaultReleaseCause’ in Table
6-6.
Note: The reasons for alternative routing option for TelÆIP calls only applies when Gatekeeper
isn’t used.
¾ To configure the reasons for alternative routing, take these 5 steps:
1. Open the ‘Reasons for Alternative Routing’ screen (Protocol Managemen t menu > Routing
Tables submenu > Reasons for Alternative Routing option); the ‘Reasons for Alternative
Routing’ screen is displayed.
Figure
5-8: Reasons for Alternative Routing Screen
2. In the ‘IP to Tel Reasons’ table, from the drop-down list select up to 4 different call failure
reasons that invoke an alternative IP to Tel routing.
3. In the ‘Tel to IP Reasons’ table, from the drop-down list select up to 4 different call failure
reasons that invoke an alternative Tel to IP routing.
4. Click the Submit button to save your changes.
5. To save the changes so they are available after a power fail, refer to Section
5.9 on page
110.
Page 76
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 76 Document #: LTRT-69903
5.5.5 Configuring the Profile Definitions
Utilizing the Profiles feature, the Mediant 2000 provides high-level adaptation when connected to
a variety of equipment (from both Tel and IP sides) and protocols, each of which require a
different system behavior. Using Profiles, users can assign different Profiles (behavior) on a percall basis, using the Tel to IP and IP to Trunk Group Routing tables, or associate different Profiles
to the gateway’s B-channels(s). The Profiles contain parameters such as Coders, T.38 Relay,
Voice and DTMF Gains, Silence Suppression, Echo Canceler, RTP DiffServ and more. The
Profiles feature allows users to tune these parameters or turn them on or off, per source or
destination routing and/or the specific gateway or its ports. For example, specific E1/T spans can
be designated for to have a profile which always uses G.711.
Each call can be associated with one or two Profiles, Tel Profile and (or) IP Profile. If both IP and
Tel profiles apply to the same call, the coders and other common parameters of the preferred
Profile (determined by the Preference option) are applied to that call. If the Preference of the Tel
and IP Profiles is identical, the Tel Profile parameters are applied.
Note: The default values of the parameters in the Tel and IP Profiles are identical to
the Web/ini file parameter values. If a value of a parameter is changed in the
Web/ini file, it is automatically updated in the Profiles correspondingly. After
any parameter in the Profile is modified by the user, modifications to
parameters in the Web/ini file no longer impact that Profile.
5.5.5.1 Coder Group Settings
Use the Coders Group Settings screen to define up to four different coder groups. These coder
groups are used in the Tel and IP Profile Settings screens to assign different coders to Profiles.
¾ To configure the coder group settings, take these 8 steps:
1. Open the ‘Coder Group Settings’ screen (Protocol Management menu > Profile
Definitions submenu > Coder Group Settings option); the ‘Coder Group Settings’ screen is
displayed.
Figure
5-9: Coder Group Settings Screen
2. In the ‘Coder Group ID’ drop-down list, select the coder group you want to edit (up to four
coder groups can be configured).
3. From the coder drop-down list, select the coder you want to use. For the full list of available
coders and their corresponding ptimes, refer to the ini file parameter ‘CoderName_ID’
(described in Table
6-6).
Note: Each coder can appear only once.
4. From the drop-down list to the right of the coder list, select the size of the Voice Packet
(ptime) used with this coder in milliseconds. Selecting the size of the packet determines how
many coder payloads are combined into one RTP (voice) packet.
Note 1: The ptime packetization period depends on the selected coder name.
Page 77
Mediant Series and TP-1610 H.323 User’s Manual 5. Web Management
Version 4.6 77 July 2005
Note 2: If not specified, the ptime gets a default value.
Note 3: The ptime specifies the maximum packetization time the gateway can receive.
5. Repeat steps 3 and 4 for the second to fifth coders (optional).
6. Repeat steps 2 to 5 for the second to forth coder groups (optional).
7. Click the Submit button to save your changes.
8. To save the changes so they are available after a power fail, refer to Section
5.9 on page
110.
5.5.5.2 Tel Profile Settings
Use the Tel Profile Settings screen to define up to four different Tel Profiles. These Profiles are
used in the ‘Trunk Group’ table to associate different Profiles to gateway’s B-channels, thereby
applying different behavior to different Mediant 2000 B-channels.
¾ To configure the Tel Profile settings, take these 8 steps:
1. Open the ‘Tel Profile Settings’ screen (Protocol Management menu > Profile Definitions
submenu > Tel Profile Settings option); the ‘Tel Profile Settings’ screen is displayed.
Figure
5-10: Tel Profile Settings Screen
5
2. In the ‘Profile ID’ drop-down list, select the Tel Profile you want to edit (up to four Tel Profiles
can be configured).
3. In the ‘Profile Preference’ drop-down list, select the preference (1-10) of the current Profile.
The preference option is used to determine the priority of the Profile. If both IP and Tel
profiles apply to the same call, the coders and other common parameters of the preferred
Profile are applied to that call. If the Preference of the Tel and IP Profiles is identical, the Tel
Profile parameters are applied.
5
In the current version the parameter ‘Signaling DiffServ’ cannot be configured using Profiles.
Page 78
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 78 Document #: LTRT-69903
Note: If the coder lists of both IP and Tel Profiles apply to the same call, an intersection of
the coders is performed (i.e., only common coders remain). The order of the coders is
determined by the preference.
4. Configure the Profile’s parameters according to your requirements. For detailed information
on each parameter refer to the description of the screen in which it is configured as an
individual parameter.
5. In the ‘Coder Group’ drop-down list, select the coder group you want to assign to that Profile.
You can select the gateway’s default coders (refer to Section
5.5.1.1 on page 65) or one of
the coder groups you defined in the Coder Group Settings screen (refer to Section
5.5.5.1 on
page 76).
6. Repeat steps 2 to 6 for the second to fifth Tel Profiles (optional).
7. Click the Submit button to save your changes.
8. To save the changes so they are available after a power fail, refer to Section
5.9 on page
110.
5.5.5.3 IP Profile Settings
Use the IP Profile Settings screen to define up to four different IP Profiles. These Profiles are
used in the Tel to IP and IP to Trunk Group Routing tables to associate different Profiles to
routing rules. IP Profiles can also be used when working with Gatekeeper (set
‘AlwaysUseRouteTable’ to 1).
¾ To configure the IP Profile settings, take these 8 steps:
1. Open the ‘IP Profile Settings’ screen (Protocol Management menu > Profile Definitions
submenu > IP Profile Settings option); the ‘IP Profile Settings’ screen is displayed.
Figure
5-11: IP Profile Settings Screen
6
2. In the ‘Profile ID’ drop-down list, select the IP Profile you want to edit (up to four IP Profiles
can be configured).
6
In the current version the parameter ‘Signaling DiffServ’ cannot be configured using Profiles.
Page 79
Mediant Series and TP-1610 H.323 User’s Manual 5. Web Management
Version 4.6 79 July 2005
3. In the ‘Profile Preference’ drop-down list, select the preference (1-10) of the current Profile.
The preference option is used to determine the priority of the Profile. If both IP and Tel
profiles apply to the same call, the coders and other common parameters of the preferred
Profile are applied to that call. If the Preference of the Tel and IP Profiles is identical, the Tel
Profile parameters are applied.
Note: If the coder lists of both IP and Tel Profiles apply to the same call, an intersection of
the coders is performed (i.e., only common coders remain). The order of the coders is
determined by the preference.
4. Configure the Profile’s parameters according to your requirements. For detailed information
on each parameter refer to the description of the screen in which it is configured as an
individual parameter.
5. In the ‘Coder Group’ drop-down list, select the coder group you want to assign to that Profile.
You can select the gateway’s default coders (refer to Section
5.5.1.1 on page 65) or one of
the coder groups you defined in the Coder Group Settings screen (refer to Section
5.5.5.1 on
page 76).
6. Repeat steps 2 to 6 for the second to fifth IP Profiles (optional).
7. Click the Submit button to save your changes.
8. To save the changes so they are available after a power fail, refer to Section
5.9 on page
110.
Page 80
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 80 Document #: LTRT-69903
5.5.6 Configuring the Registration Prefixes Table
The Gatekeeper Registration Prefixes Table enables the Mediant 2000 to register with a
Gatekeeper by associating dialing plan information with specific digit prefixes.
The Gatekeeper Registration Prefixes Table data is sent when the gateway requests permission
to register with the Gatekeeper. This registration request is triggered by a gateway reset, or by
the user from the Web Interface.
The prefix registration encoding type is configured by the parameter ‘GwRegistrType’ (described
in Table
6-6). If ‘GwRegistrType’ parameter contains NPI/TON (GwRegistrType = 3 or 4) the
gateway uses the prefixes defined in the ‘Registration Prefixes’ table to register as ‘PartyNumber’.
In this registration mode the ‘Type of Number’ columns are used, to define the prefix’s TON. In
other modes (GwRegistrType = 0, 1 or 2), the TON column is ignored.
For detailed information on the available methods the Mediant 2000 gateway registers with a
Gatekeeper, refer to Section
8.4 on page 168.
¾ To configure the Registration Prefixes, take these 4 steps:
1. Open the ‘Registration Prefixes Table’ screen (Protocol Management menu > Registration
Prefixes); the ‘Registration Prefixes Table’ screen is displayed.
Figure
5-12: Registration Prefixes Table Screen
2. Configure the Registration Prefixes according to Table
5-5.
3. Click the Submit button to save your changes or click the Re-Register button to save your
changes and to re-register to the Gatekeeper.
4. To save the changes so they are available after a power fail, refer to Section
5.9 on page
110.
Page 81
Mediant Series and TP-1610 H.323 User’s Manual 5. Web Management
Version 4.6 81 July 2005
Table 5-5: Registration Prefixes Table
Parameter Description
Gatekeeper Registration Prefixes Enter the Gatekeeper Registration prefixes. These prefixes are used by
the VoIP gateway to register to a Gatekeeper.
When entering a prefix, you can create an entry that represents multiple
prefixes using the following notation:
n-m represents a range of numbers. For example, enter ‘250-279’ to
specify all prefixes from 250 to 279.
The Type of Number parameter is composed of two columns, Number
Plan and Number Type.
Select the H.225/Q.931 Number Plan assigned to this entry. You can
select Unknown, Private or E.164 Public.
The default is Unknown.
Type of Number
Select the H.225/Q.931 Number Type assigned to this entry.
Note that the values available for the Number Type column are
determined according to the value selected in the Number Plan column.
• If you selected Unknown as the Number Plan, you can only select
Unknown.
• If you selected Private as the Number Plan, you can select Unknown,
Level 0 Regional (Local), Level 1 Regional, Level 2 Regional or PISN
Specific.
• If you selected E.164 Public as the Number Plan, you can select
Unknown, International, National, Network Specific, Subscriber or
Abbreviated.
The default is Unknown.
Note: The Type of Number information is used only if the gateway is
configured to register with PartyNumber Prefixes (GwRegistrType = 3 or
4).
For a detailed list of the available NPI/TON values, refer to Section
5.5.3.2 on page 69.
Page 82
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 82 Document #: LTRT-69903
5.5.7 Configuring the Trunk Group Table
Use the Trunk Group table to assign trunk groups, profiles and logical telephone numbers to the
gateway's E1/T1 B-channels. Trunk Groups are used for routing IPÆTel calls with common rules.
Channels that are not defined are disabled.
¾ To configure the Trunk Group table, take these 4 steps:
1. Open the ‘Trunk Group Table’ screen (Protocol Management menu > Trunk Group); the
‘Trunk Group Table’ screen is displayed.
Figure
5-13: Trunk Group Table Screen
2. Configure the Trunk Group according to Table
5-6
3. Click the Submit button to save your changes.
4. To save the changes so they are available after a power fail, refer to Section
5.9 on page
110.
Table
5-6: Trunk Group Table
Parameter Description
Trunk ID The numbers (1-8) in the Trunk ID drop-down list represent the physical trunks on the back of
the VoIP gateway.
Channels
To enable the trunk’s B-channels, you must enter their number in this field.
[n-m] represents a range of channels.
For example, enter [1-24] to specify the channels from 1 to 24.
Note: The number of defined channels must not exceed the number of the trunk’s B-channels
(1-24 for T1 spans and 1-30 for E1 spans).
Phone Number In each of the Phone Number fields, enter the first number in an ordered sequence that is
assigned to the range of channels defined in the adjacent ‘Channels’ field.
Note: This field is optional. The logical numbers defined in this field are used when an
incoming PSTN / PBX call doesn’t contain the calling number or called number (the latter
being determined by the parameter ‘ReplaceEmptyDstWithPortNumber’), these numbers are
used to replace them.
These logical numbers are also used for B-channel allocation for IP to Tel calls, if the trunk
group’s ‘Channel Select Mode’ is set to ‘By Phone Number’.
Page 83
Mediant Series and TP-1610 H.323 User’s Manual 5. Web Management
Version 4.6 83 July 2005
Table 5-6: Trunk Group Table
Parameter Description
Trunk Group ID In each of the Trunk Group ID fields, enter the trunk group ID (1-99) assigned to the channels.
The same trunk group ID can be used for more than one group of channels.
Trunk group ID is used to define a group of common behavior channels that are used for
routing IP to Tel calls. If an IP to Tel call is assigned to a trunk group, the call is routed to the
channel or channels that correspond to the trunk group ID.
You can configure the Trunk Group Settings table to determine the method in which new calls
are assigned to channels within the trunk groups (refer to Section 5.5.7 on page 82).
Note: You must configure the IP to Trunk Group Routing Table (assigns incoming IP calls to
the appropriate trunk group). If you do not configure the IP to Trunk Group Routing Table,
calls do not complete.
For information on how to configure this table, refer to Section 5.5.4.2 on page 72.
Profile ID Enter the number of the Tel profile that is assigned to the B-channels defined in the
‘Channels’ field.
5.5.8 Trunk Group Settings
The Trunk Group Settings Table is used to determine the method in which new calls are assigned
to B-channels within each trunk group. If such a rule doesn’t exist (for a specific Trunk group), the
global rule, defined by the Channel Select Mode parameter (Protocol Definition > General
Parameters), applies.
¾ To configure the Trunk Group Settings table, take these 7 steps:
1. Open the ‘Trunk Group Settings’ screen (Protocol Management menu > Trunk Group
Settings); the ‘Trunk Group Settings’ screen is displayed.
Figure
5-14: Trunk Group Settings Screen
2. In the Routing Index drop-down list, select the range of entries that you want to edit (up to
24 entries can be configured).
3. In the Trunk Group ID field, enter the Trunk Group Id number.
Page 84
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 84 Document #: LTRT-69903
4. In the Channel Select Mode drop-down list, select the Channel Select Mode that
determines the method in which new calls are assigned to B-channels within the Trunk
groups entered in the field to the right of this field. For information on available Channel
Select Modes, refer to Table
5-7.
5. Repeat steps 4 and 5, for each defined Trunk group.
6. Click the Submit button to save your changes.
7. To save the changes so they are available after a power fail, refer to Section
5.9 on page
110.
Table
5-7: Channel Select Modes
Mode Description
By phone number Select the gateway port according to the called number (refer to the note
below).
Cyclic Ascending Select the next available channel in an ascending cycle order. Always select
the next higher channel number in the Trunk Group. When the gateway
reaches the highest channel number in the Trunk Group, it selects the lowest
channel number in the Trunk Group and then starts ascending again (default).
Ascending Select the lowest available channel. Always start at the lowest channel
number in the Trunk Group and if that channel is not available, select the next
higher channel.
Cyclic Descending Select the next available channel in descending cycle order. Always select the
next lower channel number in the Trunk Group. When the gateway reaches
the lowest channel number in the Trunk Group, it selects the highest channel
number in the Trunk Group and then start descending again.
Descending Select the highest available channel. Always start at the highest channel
number in the Trunk Group and if that channel is not available, select the next
lower channel.
Number + Cyclic Ascending First select the gateway port according to the called number (refer to the note
below). If the called number isn’t found, then select the next available channel
in ascending cyclic order. Note that if the called number is found, but the port
associated with this number is busy, the call is released.
Note: The internal numbers of the gateway’s B-channels are defined in the ‘Trunk
Group Table’ under the ‘Phone Number’ column. For detailed information on
the ‘Trunk Group Table’, refer to Section 5.5.7 on page 82).
Page 85
Mediant Series and TP-1610 H.323 User’s Manual 5. Web Management
Version 4.6 85 July 2005
5.6 Advanced Configuration
Use this menu to set the gateway’s advanced configuration parameters (for advanced users
only).
5.6.1 Configuring the Network Settings
From the Network Settings you can:
• Define the IP Settings.
• Define the Application Settings.
• Define the SNMP Managers Table (refer to Section
5.6.1.1 below).
• Define the Web & Telnet Access List (refer to Section
5.6.1.2 on page 86).
• Define the RTP Settings.
• Define the IP Routing Table (refer to Section
5.6.1.3 on page 86).
• View the Ethernet Port Information (read-only) (refer to Section
5.6.1.4 on page 88).
5.6.1.1 Configuring the SNMP Managers Table
The SNMP Managers table allows you to configure the attributes of up to five SNMP managers.
¾ To configure the SNMP Managers Table, take these 6 steps:
1. Access the ‘Application Settings’ screen (Advanced Configuration menu > Network
Settings > Application Settings option); the ‘Application Settings’ screen is displayed.
2. Open the SNMP Managers Table screen by clicking the arrow sign (-->) to the right of the
SNMP Managers Table label; the SNMP Managers Table screen is displayed (Figure
5-15).
3. Configure the SNMP manager’s parameters.
4. Click the Submit button to save your changes.
5. Click the Close Window button.
6. To save the changes so they are available after a power fail, refer to Section
5.9 on page
110.
Figure
5-15: SNMP Managers Table Screen
Note: If you clear a checkbox and click Submit, all settings in the same row revert
to their defaults.
Page 86
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 86 Document #: LTRT-69903
5.6.1.2 Configuring the Web and Telnet Access List
Use this screen to define up to ten IP addresses that are permitted to access the gateway’s Web
and Telnet interfaces. Access from an undefined IP address is denied. This security feature is
inactive (the gateway can be accessed from any IP address) when the table is empty.
¾ To manage the Web & Telnet access list, take these 4 steps:
1. Open the ‘Web & Telnet Access List’ screen (Advanced Configuration menu > Network
Settings > Web & Telnet Access List option); the ‘Web & Telnet Access List’ screen is
displayed.
Figure
5-16: Web & Telnet Access List Screen
2. To add a new authorized IP address, in the ‘New Authorized IP Address’ field, enter the
required IP address (refer to Note 1 below) and click the button Add New Address; the IP
address you entered is added as a new entry to the Web & Telnet Access List table.
3. To delete authorized IP addresses, check the Delete Row checkbox in the rows of the IP
addresses you want to delete (refer to Note 2 below) and click the button Delete Selected
Addresses; the IP addresses are removed from the table and can no longer access the
Web & Telnet interfaces.
4. To save the changes so they are available after a power fail, refer to Section
5.9 on page
110.
Note 1: The first authorized IP address you add must be your own terminal's IP address.
If it isn’t, further access from your terminal is denied.
Note 2: Delete your terminal's IP address from the Web & Telnet Access List last. If it is
deleted before the last, access from your terminal is denied from the point of its
deletion on.
5.6.1.3 Configuring the IP Routing Table
The IP routing table is used by the gateway to determine IP routing rules. Before sending an IP
packet, the gateway searches this table for an entry that matches the requested destination host /
network. If such entry is found, the gateway sends the packet to the indicated router. If no explicit
entry is found, the packet is sent to the default gateway (configured in Network Settings>IP
Settings screen). Up to 50 routing entries are available.
¾ To configure the IP Routing table, take these 3 steps:
1. Open the ‘IP Routing Table’ screen (Advanced Configuration menu > Net work Settings >
IP Routing Table option); the ‘IP Routing Table’ screen is displayed.
Page 87
Mediant Series and TP-1610 H.323 User’s Manual 5. Web Management
Version 4.6 87 July 2005
Figure 1-3: IP Routing Table Screen
2. Use the ‘Add a new table entry’ pane to add a new routing rule. Each field in the IP routing
table is described in Table
5-8.
3. Click the button Add New Entry; the new routing rule is added to the IP routing table.
Note: In the current version, the option to save changes to the IP Routing table so they
are available after power fail isn’t available via the Embedded Web Server. Use
ini file configuration instead.
Table 5-8: IP Routing Table Column Description
Column Name
[ini File Parameter Name]
Description
Delete Row To delete IP routing rules from the IP Routing Table, check the Delete Row
checkbox in the rows of the routing rules you want to delete and click the
button Delete Selected Entries; the routing rules are removed from the
table.
Destination IP Address
Specifies the IP address of the destination host / network.
Destination Mask Specifies the subnet mask of the destination host / network.
The address of the host / network you want to reach is determined by an AND operation that is applied on the fields
‘Destination IP Address’ and ‘Destination Mask’.
For example:
To reach the network 10.8.x.x, enter 10.8.0.0 in the field ‘Destination IP Address’ and 255.255.0.0 in the field
‘Destination Mask’. As a result of the AND operation, the value of the last two octets in the field ‘Destination IP Address’
is ignored.
To reach a specific host, enter its IP address in the field ‘Destination IP Address’ and 255.255.255.255 in the field
‘Destination Mask’.
Gateway IP Address Specifies the IP address of the router to which the packets are sent if their
destination matches the rules in the adjacent columns.
TTL
A read-only field that indicates the time period for which the specific routing
rule is valid. The lifetime of a static route is infinite.
Hop Count The maximum number of allowed routers between the gateway and
destination.
Network Type
N/A. Leave at its default (OAM).
Page 88
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 88 Document #: LTRT-69903
5.6.1.4 Viewing the Ethernet Port Information
The Ethernet Port Information screen provides read-only information on the Ethernet connection
used by the Mediant 2000. The Ethernet Port Information parameters are displayed in Table
5-9.
For detailed information on the Ethernet redundancy scheme, refer to Section
9.2 on page 177.
For detailed information on the Ethernet interface configuration, refer to Section
9.1 on page 177.
¾ To view the Ethernet Port Information parameters, take this step:
• Open the ‘Ethernet Port Information’ screen (Advanced Configuration menu > Network
Settings > Ethernet Port Information option); the ‘Ethernet Port Information’ screen is
displayed.
Figure 5-17: Ethernet Port Information Screen
Table 5-9: Ethernet Port Information Parameters
Parameter Description
Active Port Shows the active Ethernet port (1 or 2).
Port 1 Duplex Mode Shows the Duplex mode Ethernet port 1 is using (Half Duplex or Full Duplex).
Port 1 Speed Shows the speed, in Mbps, that Ethernet port 1 is using (10 Mbps or 100 Mbps).
Port 2 Duplex Mode Shows the Duplex mode Ethernet port 2 is using (Half Duplex or Full Duplex).
Port 2 Speed Shows the speed, in Mbps, that Ethernet port 2 is using (10 Mbps or 100 Mbps).
5.6.2 Configuring the Channel Settings
Use these menus to set the gateway’s channel parameters. These parameters are applied to all
Mediant 2000 channels. Several Channels Settings parameters can be configured per call using
profiles (refer to Section
5.5.5 on page 76). Note that channel parameters are changeable on-the-
fly. Changes take effect from next call.
From the Channel Settings you can:
• Define the Voice Settings.
• Define the Fax / Modem and CID Settings.
• Define the RTP Settings.
• Define the IPmedia Settings.
Note 1: The parameters ‘MF Transport Type’ (Voice Settings screen) and the five
Answer Detector (IPmedia Settings screen) parameters are not applicable to
the Mediant 2000.
Note 2: The parameters ‘DTMF Transport Type’ (Voice Settings screen) and ‘Fax
Transport Mode’ (Fax / Modem / CID Settings screen) are overridden by the
parameters ‘IsDTMFUsed’ and ‘IsFaxUsed’ respectively.
Page 89
Mediant Series and TP-1610 H.323 User’s Manual 5. Web Management
Version 4.6 89 July 2005
5.6.3 Configuring the Trunk Settings
¾ To configure the Trunk Settings, take these 9 steps:
1. Open the ‘Trunk Settings’ screen (Advanced Configuration menu > Trunk Settings); the
‘Trunk Settings’ screen is displayed.
Initially, the screen appears with the parameters fields grayed (indicating read-only). The
Stop Trunk button appears at the bottom of the screen.
The Trunk Status indicators appear colored. Table
5-10 shows the possible indicators and
their descriptions.
Figure
5-18: E1/T1 Trunk Settings Screen
2. To configure the parameters of a specific trunk, from the trunks displayed on the top, select
the trunk you want to configure by clicking the Trunk’s Status indicator. The first parameter
named ‘Trunk ID’ changes according to the trunk you click. The parameters displayed are for
the selected trunk only.
Page 90
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 90 Document #: LTRT-69903
Table 5-10: Trunks Status Color Indicator Keys
Indicator Color Description
Gray Disabled
Green Active-OK
Yellow RAI Alarm
Red LOS/LOF Alarm
Blue AIS Alarm
Orange
D-channel Alarm
(ISDN only)
3. To modify the selected trunk’s parameters, click the Stop Trunk button; the trunk is stopped,
the status of the parameter ‘Trunk Configuration State’ changes to ‘Non Active’, the
parameters are no longer grayed and can be modified and the Apply Trunk Settings button
appears at the bottom of the screen.
When all trunks are stopped, the Apply to all Trunks button also appears at the bottom of
the screen.
Note: If the trunk can’t be stopped because it provides the gateway’s clock
(assuming the Mediant 2000 is synchronized with the E1/T1 clock), assign a
different E1/T1 trunk to provide the gateway’s clock or enable ‘TDM Bus
PSTN Auto Clock’ on the TDM Bus Settings screen.
To assign a different E1/T1 trunk that provides the gateway’s clock, access
the ‘TDM Bus Setting’ screen and change the ‘TDM Bus Local Reference’
number to any other trunk number (this operation can be performed on-thefly).
4. Select the ‘Protocol Type’ you use. Note that different trunks can be defined with different
protocols (CAS or ISDN variants) on the same gateway (subject to the constraints in the
Mediant 2000 Release Notes).
Note: When modifying the ‘Protocol Type’ field, the menu is automatically updated
according to the selected protocol (ISDN, CAS or Transparent). Additional
parameters are appropriate to the selected protocol type.
5. Modify the relevant trunk configuration parameters according to your requirements.
6. To configure the different behavior bits: either enter the exact hexadecimal value of the bits
in the field to the right of the relevant behavior parameter, or directly configure each bit field
by completing the following steps:
¾ Click the arrow button (-->) to the right of the relevant behavior parameter; a new window
appears.
¾ Modify each bit field according to your requirements.
¾ Click the Submit button to save your changes.
Page 91
Mediant Series and TP-1610 H.323 User’s Manual 5. Web Management
Version 4.6 91 July 2005
¾ Click the Clo se Window button.
7. After modifying the parameters:
¾ To apply the changes to the selected trunk only, click the Apply Trunk Settings button.
¾ To apply the changes to all the trunks, click the Apply to all Trunks button.
The screen is refreshed, parameters become read-only (indicated by being grayed). The
Stop Trunk button appears at the bottom of the screen.
8. To save the changes so they are available after a power fail, refer to Section
5.9 on page
110.
Note: Some parameter configuration options require a device reset; when this is the
case, the Web Interface prompts the user.
9. To reset the Mediant 2000, refer to Section 5.9 on page 110.
5.6.4 Configuring the TDM Bus Settings
¾ To configure the TDM Bus Settings parameters, take these 5 steps:
1. Open the ‘TDM Bus Settings’ screen (Advanced Configuration menu > TDM Bus
Settings); the ‘TDM Bus Settings’ screen is displayed.
2. Configure the TDM Bus Settings parameters.
3. Click the Submit button to save your changes.
4. To save the changes so they are available after a power fail, refer to Section
5.9 on page
110.
5. A device reset is required to activate the TDM Bus Settings parameters. To reset the
Mediant 2000, refer to Section
5.9 on page 110.
Figure
5-19: TDM Bus Settings Screen
Note: Usually the ‘PCM Law Select’ parameter is set to A-law for E1 trunks and to
µ-law for T1 trunks.
Refer to Section 10.1 on page 181 for information on configuring the ‘TDM Bus Clock Source’,
‘TDM Bus Enable Fallback’ and ‘TDM Bus PSTN Auto Clock’ parameters.
Page 92
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 92 Document #: LTRT-69903
5.6.5 Restoring and Backing Up the Gateway Configuration
The Configuration File screen enables you to restore (load a new ini file to the gateway) or to
back up (make a copy of the VoIP gateway ini file and store it in a directory on your computer) the
current configuration the gateway is using.
Back up your configuration if you want to protect your VoIP gateway programming. The backup
ini file includes only those parameters that were modified and contain other than default values.
Restore your configuration if the VoIP gateway has been replaced or has lost its programming
information, you can restore the VoIP gateway configuration from a previous backup or from a
newly created ini file. To restore the VoIP gateway configuration from a previous backup you
must have a backup of the VoIP gateway information stored on your computer.
¾ To restore or back up the ini file:
• Open the ‘Configuration File’ screen (Advanced Configuration menu > Configuration
File); the ‘Configuration File’ screen is displayed.
Figure
5-20: Configuration File Screen
¾ To back up the ini file, take these 4 steps:
1. Click the Get ini File button; the ‘File Download’ window opens.
2. Click the Save button; the ‘Save As’ window opens.
3. Navigate to the folder where you want to save the ini file.
4. Click the Save button; the VoIP gateway copies the ini file into the folder you selected.
¾ To restore the ini file, take these 4 steps:
1. Click the Browse button.
2. Navigate to the folder that contains the ini file you want to load.
3. Click the file and click the Open button; the name and path of the file appear in the field
beside the Browse button.
4. Click the Send ini File button, and click OK in the prompt; the gateway is automatically reset
(from the cmp version stored on the flash memory).
Page 93
Mediant Series and TP-1610 H.323 User’s Manual 5. Web Management
Version 4.6 93 July 2005
5.6.6 Regional Settings
The ‘Regional Settings’ screen enables you to set and view the gateway’s internal date and time
and to load to the gateway the following configuration files: Call Progress Tones, CAS and Voice
Prompts. For detailed information on the configuration files, refer to Section
17 on page 247.
¾ To configure the date and time of the Mediant 2000, take these 3 steps:
1. Open the ‘Regional Settings’ screen (Advanced Configuration menu > Regional
Settings); the ‘Regional Settings' screen is displayed.
Figure
5-21: Regional Settings Screen
2. Enter the time and date where the gateway is installed.
3. Click the Set Date & Time button; the date and time are automatically updated.
Note that after performing a hardware reset, the date and time are returned to their defaults and
should be updated.
¾ To load a configuration file to the VoIP gateway, take these 8 steps:
1. Open the ‘Regional Settings’ screen (Advanced Configuration menu > Regional
Settings); the ‘Regional Settings’ screen is displayed (shown in Figure
5-21).
2. Click the Browse button adjacent to the file you want to load.
3. Navigate to the folder that contains the file you want to load.
4. Click the file and click the Open button; the name and path of the file appear in the field
beside the Browse button.
5. Click the Send File button that is next to the field that contains the name of the file you want
to load. An exclamation mark in the screen section indicates that the file’s loading doesn’t
take effect on-the-fly (e.g., CPT file).
6. Repeat steps 2 to 5 for each file you want to load.
Page 94
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 94 Document #: LTRT-69903
Note 1: Saving a configuration file to flash memory may disrupt traffic on the Mediant
2000. To avoid this, disable all traffic on the device before saving to flash
memory.
Note 2: A device reset is required to activate a loaded CPT file.
7. To save the loaded auxiliary files so they are available after a power fail, refer to Section 5.9
on page 110.
8. To reset the Mediant 2000, refer to Section
5.9 on page 110.
5.6.7 Changing the Mediant 2000 Username and Password
To prevent unauthorized access to the Embedded Web Server, two levels of security are
available: Administrator and Monitoring. Each employs a different username and password. For
detailed information on the dual access mechanism, refer to Section
5.2.1 on page 61.
It is recommended that you change the default username and password of the security mode you
use to access the Embedded Web Server.
¾ To change the username and password, take these 4 steps:
1. Open the ‘Change Password’ screen (Advanced Configuration menu > Change
Password); the ‘Change Password’ screen is displayed.
Figure
5-22: Change Password Screen
2. In the ‘User Name’ and ‘New Password’ fields, enter the new username and the new
password respectively. Note that the username and password of both levels can be a
maximum of 19 case-sensitive characters.
3. In the ‘Confirm Password’ field, reenter the new password.
4. To apply the new username and password to the Administrator level:
Click the button Change Administrator Password; the new username and password are
applied and the ‘Enter Network Password’ screen appears, shown in Figure
5-1 on page 62.
Enter the updated username and password in the ‘Enter Network Password’ screen.
To apply the new username and password to the Monitoring level:
Click the button Change Monitoring Password; the new username and password are
applied.
Page 95
Mediant Series and TP-1610 H.323 User’s Manual 5. Web Management
Version 4.6 95 July 2005
5.7 Status & Diagnostic
Use this menu to view and monitor the gateway’s channels, Syslog messages, hardware /
software product information, and to assess the gateway’s statistics and IP connectivity
information.
5.7.1 Gateway Statistics
Use the screens under Gateway Statistics to monitor real-time activity such as IP Connectivity
information, call details and call statistics, including the number of call attempts, failed calls, fax
calls, etc.
Note: The Gateway Statistics screens doesn’t refresh automatically. To view updated information
re-access the screen you require.
5.7.1.1 IP Connectivity
The IP Connectivity screen provides you with an online read-only network diagnostic connectivity
information on all destination IP addresses configured in the Tel to IP Routing table.
Note: This information is available only if the parameter ‘AltRoutingTel2IPEnable’ (described in
Table
6-8) is set to 1 (Enable) or 2 (Status Only).
Note: The information in columns ‘Quality Status’ and ‘Quality Info.’ (per IP address)
is reset if two minutes elapse without a call to that destination.
¾ To view the IP connectivity information, take these 2 steps:
1. Set ‘AltRoutingTel2IPEnable’ to 1 or 2.
2. Open the ‘IP Connectivity’ screen (Status & Diagnostics menu > Gateway Statistics
submenu > IP Connectivity); the ‘IP Connectivity’ screen is displayed (Figure
5-23).
Figure
5-23: IP Connectivity Screen
Page 96
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 96 Document #: LTRT-69903
Table 5-11: IP Connectivity Parameters
Column Name Description
IP Address
IP address defined in the destination IP address field in the Tel to IP Routing table.
or
IP address that is resolved from the host name defined in the destination IP address field in the
Tel to IP Routing table.
Host Name
Host name (or IP address) defined in the destination IP address field in the Tel to IP Routing
table.
Connectivity Method
The method according to which the destination IP address is queried periodically (currently
only by ping).
Connectivity Status
Displays the status of the IP address’ connectivity according to the method in the ‘Connectivity
Method’ field.
Can be one of the following:
• OK = Remote side responds to periodic connectivity queries.
• Lost = Remote side didn’t respond for a short period.
• Fail = Remote side doesn’t respond.
• Init = Connectivity queries not started (e.g., IP address not resolved).
• Disable = The connectivity option is disabled (‘AltRoutingTel2IPMode’ equals 0 or 2).
Quality Status
Determines the QoS (according to packet loss and delay) of the IP address.
Can be one of the following:
• Unknown = Recent quality information isn’t available.
• OK
• Poor
Note 1: This field is applicable only if the parameter ‘AltRoutingTel2IPMode’ is set to 2 or 3.
Note 2: This field is reset if no QoS information is received for 2 minutes.
Quality Info.
Displays QoS information: delay and packet loss, calculated according to previous calls.
Note 1: This field is applicable only if the parameter ‘AltRoutingTel2IPMode’ is set to 2 or 3.
Note 2: This field is reset if no QoS information is received for 2 minutes.
DNS Status
Can be one of the following:
• DNS Disable
• DNS Resolved
• DNS Unresolved
5.7.1.2 Call Counters
The Call Counters screens provide you with statistic information on incoming (IPÆTel) and
outgoing (TelÆIP) calls. The statistic information is updated according to the release reason that
is received after a call is terminated (during the same time as the end-of-call CDR message is
sent). The release reason can be viewed in the Termination Reason field in the CDR message.
For detailed information on each counter, refer to Table
5-12 on page 97.
You can reset this information by clicking the Reset Counters button.
¾ To view the IPÆTel and TelÆIP Call Counters information:
• Open the Call Counters screen you want to view (Status & Diagnostics menu > Gateway
Statistics submenu); the relevant Call Counters screen is displayed. Figure
5-24 shows the
‘TelÆIP Call Counters’ screen.
Page 97
Mediant Series and TP-1610 H.323 User’s Manual 5. Web Management
Version 4.6 97 July 2005
Figure 5-24: TelÆIP Call Counters Screen
Table
5-12: Call Counters Description (continues on pages 97 to 98)
Counter Description
Number of Attempted
Calls
This counter indicates the number of attempted calls.
It is composed of established and failed calls. The number of established calls is
represented by the ‘Number of Established Calls’ counter. The number of failed
calls is represented by the five failed-call counters. Only one of the established /
failed call counters is incremented every time.
Number of Established
Calls
This counter indicates the number of established calls. It is incremented as a result
of one of the following release reasons, if the duration of the call is bigger then zero:
GWAPP_REASON_NOT_RELEVANT (0)
GWAPP_NORMAL_CALL_CLEAR (16)
GWAPP_NORMAL_UNSPECIFIED (31)
And the internal reasons:
RELEASE_BECAUSE_UNKNOWN_REASON
RELEASE_BECAUSE_REMOTE_CANCEL_CALL
RELEASE_BECAUSE_MANUAL_DISC
RELEASE_BECAUSE_SILENCE_DISC
RELEASE_BECAUSE_DISCONNECT_CODE
Note: When the duration of the call is zero, the release reason
GWAPP_NORMAL_CALL_CLEAR increments the ‘Number of Failed Calls due to
No Answer’ counter. The rest of the release reasons increment the ‘Number of
Failed Calls due to Other Failures’ counter.
Number of Failed Calls
due to a Busy Line
This counter indicates the number of calls that failed as a result of a busy line. It is
incremented as a result of the following release reason:
GWAPP_USER_BUSY (17)
Number of Failed Calls
due to No Answer
This counter indicates the number of calls that weren’t answered. It is incremented
as a result of one of the following release reasons:
GWAPP_NO_USER_RESPONDING (18)
GWAPP_NO_ANSWER_FROM_USER_ALERTED (19)
And (when the call duration is zero) as a result of the following:
GWAPP_NORMAL_CALL_CLEAR (16)
Number of Failed Calls
due to No Route
This counter indicates the number of calls whose destinations weren’t found. It is
incremented as a result of one of the following release reasons:
GWAPP_UNASSIGNED_NUMBER (1)
GWAPP_NO_ROUTE_TO_DESTINATION (3)
Page 98
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 98 Document #: LTRT-69903
Table 5-12: Call Counters Description (continues on pages 97 to 98)
Counter Description
Number of Failed Calls
due to No Matched
Capabilities
This counter indicates the number of calls that failed due to mismatched gateway
capabilities. It is incremented as a result of an internal identification of capability
mismatch. This mismatch is reflected to CDR via the value of the parameter
‘DefaultReleaseReason’ (default is GWAPP_NO_ROUTE_TO_DESTINATION (3)),
or by the GWAPP_SERVICE_NOT_IMPLEMENTED_UNSPECIFIED(79) reason.
Number of Failed Calls
due to Other Failures
This counter is incremented as a result of calls that fail due to reasons not covered
by the other counters.
Percentage of
Successful Calls
The percentage of established calls from attempted calls.
Average Call Duration
[sec]
The average call duration of established calls.
Attempted Fax Calls
Counter
This counter indicates the number of attempted fax calls.
Successful Fax Calls
Counter
This counter indicates the number of successful fax calls.
5.7.1.3 Call Routing Status
The Call Routing Status screen provides you with information on the current routing method used
by the gateway. This information includes the IP address of the Gatekeeper the gateway currently
operates with.
Figure
5-25: Call Routing Status Screen
Table
5-13: Call Routing Status Parameters
Parameter Description
Gatekeeper = Gatekeeper is used to route calls.
Routing Table preferred to Gatekeeper = The Tel to IP Routing table takes
precedence over a Gatekeeper for routing calls (PreferRouteTable = 1).
Current Call-Routing Method
Routing Table = The Tel to IP Routing table is used to route calls.
Not Used = Gatekeeper isn’t defined.
Current Gatekeeper
IP address of the Gatekeeper the gateway currently operates with.
N/A = Gatekeeper isn’t defined.
OK = Communication with the Gatekeeper is in order.
Current Gatekeeper State
Fail = No response from any of the defined Gatekeepers.
Page 99
Mediant Series and TP-1610 H.323 User’s Manual 5. Web Management
Version 4.6 99 July 2005
5.7.2 Monitoring the Mediant 2000 Trunks & Channels
The Trunk & Channel Status screen provides real time monitoring on the current status of the
Mediant 2000 trunks & channels.
¾ To monitor the status of the trunks and B-channels take this step:
• Open the ‘Trunk & Channel Status’ screen (Status & Diagnostics menu > Channel
Status); the ‘Trunk & Channel Status’ screen is displayed.
Figure
5-26: Mediant 2000 Trunk & Channel Status Screen
The number of trunks and channels that appear on the screen depends on the system
configuration. The example above depicts a system with 8 T1 spans.
The trunk and channel status indicators appear colored. Figure
5-27 shows the possible
indicators and their descriptions.
Figure
5-27: Trunk and Channel Status Color Indicator Keys
¾ To monitor the details of a specific channel, take these 2 steps:
1. Click the numbered icon of the specific channel whose detailed status you need to
check/monitor; the channel-specific Channel Status screen appears, shown in Figure
5-28.
Page 100
Mediant Series and TP-1610 H.323
Mediant Series and TP-1610 H.323 100 Document #: LTRT-69903
2. Click the submenu links to check/view a specific channel’s parameter settings.
Figure
5-28: Channel Status Details Screen
Loading...