AudioCodes Mediant 1000 User Manual
  1. Manuals
  2. Brands
  3. AudioCodes Manuals
  4. Gateway
  5. Mediant 1000
  6. User manual

AudioCodes Mediant 1000 User Manual

Voice-over-ip (voip) h.323 media gateway
Hide thumbs Also See for Mediant 1000:
1
2
Table Of Contents
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
Table of Contents

Advertisement

Quick Links

See also: Troubleshooting Manual , User Manual
™ Mediant™ Media Gateways
H.323
Mediant 1000
User's Manual Version 5.0
Document #: LTRT-83401
December 2006

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Mediant 1000 and is the answer not in the manual?

Questions and answers

Related Manuals for AudioCodes Mediant 1000

Summary of Contents for AudioCodes Mediant 1000

  • Page 1 ™ Mediant™ Media Gateways H.323 Mediant 1000 User’s Manual Version 5.0 Document #: LTRT-83401 December 2006...

  • Page 3: Table Of Contents

    3.3.2 Installing the Mediant 1000 in a 19-inch Rack............36 Cabling the Mediant 1000 ..................37 3.4.1 Connecting the Mediant 1000 RS-232 Port to Your PC ..........38 3.4.2 Setting up a Dry Contact Relay Alarm System............39 3.4.3 Cabling the Digital Lifeline ..................40 3.4.4...
  • Page 4 Mediant 1000 Web Management....................55 Computer Requirements ..................55 Protection and Security Mechanisms..............55 5.2.1 User Accounts ......................55 5.2.2 Limiting the Embedded Web Server to Read-Only Mode ........57 5.2.3 Disabling the Embedded Web Server ..............57 Accessing the Embedded Web Server ..............57 5.3.1...
  • Page 5 Resetting the Mediant 1000.................. 195 5.10 Monitoring the Gateway (Home Page)..............197 5.10.1 Monitoring the Mediant 1000 Trunks and Channels..........199 5.10.2 Monitoring the Modules ..................201 5.10.3 Monitoring Ethernet Ports, Dry Contacts, Power Supply Units, and Fan Tray Unit202 5.10.4 Viewing the Active Alarms Table ................
  • Page 6 Using Bypass Mechanism for V.34 Fax Transmission......262 8.3.4.2 Using Relay mode for both T.30 and V.34 faxes ........262 Redundant Gatekeeper Implementation .............. 263 Mediant 1000 Registration with a Gatekeeper ............. 264 8.5.1 Registration with Prefixes ..................264 8.5.2 Registration with H.323-ID..................
  • Page 7 8.13.5.1 Dialing from Remote Extension (Phone Connected to FXS) ....276 8.13.5.2 Dialing from other PBX line, or from PSTN ........... 276 8.13.5.3 FXS Mediant 1000 Configuration (using the Embedded Web Server) . 276 8.13.5.4 FXO Mediant 1000 Configuration (using the Embedded Web Server). 277 Networking Capabilities..................279...
  • Page 8 11.5.5 Using the ini File to Configure Parameter Tables..........305 11.5.5.1 Structure of Parameter Tables in the ini File......... 305 11.6 Customizing the Mediant 1000 Web Interface ............. 307 11.6.1 Replacing the Main Corporate Logo..............307 11.6.1.1 Replacing the Main Corporate Logo with an Image File ....... 307 11.6.1.2 Replacing the Main Corporate Logo with a Text String ......
  • Page 9 15.11 SNMP Administrative State Control ..............365 15.11.1 Node Maintenance....................365 15.11.2 Graceful Shutdown ....................365 15.12 AudioCodes’ Element Management System............366 16 Configuration Files..................367 16.1 Configuring the Call Progress Tones and Distinctive Ringing File....... 367 16.1.1 Format of the Call Progress Tones Section in the ini File ........367 16.1.2 Format of the Distinctive Ringing Section in the ini File ........
  • Page 10 Mediant 1000 C BootP/TFTP Configuration Utility ..............381 C.1 When to Use the BootP/TFTP................381 C.2 An Overview of BootP ..................381 C.3 Key Features......................381 C.4 Specifications ....................... 382 C.5 Installation ......................382 C.6 Loading the cmp File, Booting the Device............382 C.7 BootP/TFTP Application User Interface ...............
  • Page 11 G.2 Linux Operation Systems ..................422 H OSN Server Hardware Installation ..............425 H.1 Required Working Tools..................425 H.2 OSN Server Installation on the Mediant 1000............425 Linux™ Operating System Installation for the OSN Server......431 Physical Mounting Requirements................. 431 Software Requirements..................431 Physical Mounting Requirements.................
  • Page 12 Figure 3-4: Supplied RS-232 Cable .......................38 Figure 3-5: Dry Contact Wires’ Mate ......................39 Figure 3-6: Mediant 1000 Lifeline Cabling (e.g., Trunk 1 and Trunk 2) ..........40 Figure 3-7: Lifeline Pinout and RJ-11 Port 1 in the FXS Module ............41 Figure 3-8: Mediant 1000 Lifeline Setup ....................41 Figure 3-9: Slightly Extracted Fan Tray Unit ..................44...
  • Page 13 Figure 11-1: RS-232 Status and Error Messages ................298 Figure 11-2: Example of an ini File Activating the Automatic Update Mechanism......299 Figure 11-3: Mediant 1000 Startup Process..................302 Figure 11-4: Structure of a Parameter Table in the ini File ..............305 Figure 11-5: User-Customizable Web Interface Title Bar ..............
  • Page 14 Figure H-5: Inserting the CM Module ....................427 Figure H-6: Mediant 1000 Rear Panel View..................428 Figure H-7: Mediant 1000 With Cover Plates Removed ..............428 Figure H-8: Mediant 1000 With Cutter Tool..................429 Figure H-9: Inserting the iPMX Module ....................429 Figure H-10: Inserting the HDMX Module ...................
  • Page 15 H.323 User's Manual Contents Figure I-5: Selecting Extract Option ....................435 Figure I-6: Extract Files ........................435 Figure I-7: ISO-Extract screen......................436 Figure I-8: Text Edit screen ......................... 436 Figure I-9: Deleting CFG ........................438 Figure I-10: File Add ..........................438 Figure I-11: ISO Open Function ......................
  • Page 16 Mediant 1000 List of Tables Table 2-1: Mediant 1000 Front View Component Descriptions (continues on pages 27 to 28).....27 Table 2-2: CPU Module LEDs Description .....................31 Table 2-3: Analog I/O Modules LEDs Description..................31 Table 2-4: Digital I/O Modules LED Description..................32 Table 2-5: Power Supply Module LED Description ................32...
  • Page 17 Table 15-3: SNMP v3 Security Levels....................356 Table 15-4: SNMP v3 Predefined Groups................... 356 Table A-1: Mediant 1000 Functional Specifications (continues on pages 375 to 377) ....... 375 Table B-1: Supplied Software Kit ......................379 Table C-1: Command Line Switch Descriptions.................. 391 Table D-1: Packet Types Defined in RFC 3551 ..................
  • Page 18 Mediant 1000 Table F-14: acBoardEthernetLinkAlarm Alarm Trap ................417 Table F-15: acKeepAlive Log Trap...................... 418 Table F-16: acPerformanceMonitoringThresholdCrossing Log Trap..........418 Table F-17: acHTTPDownloadResult Log Trap .................. 419 Table F-18: coldStart Trap........................419 Table F-19: authenticationFailure Trap ....................419 Table F-20: acBoardEvBoardStarted Trap..................419 Table F-21: AcDChannelStatus Trap ....................

  • Page 19: Weee Eu Directive

    Notices Notices Notice This document describes the AudioCodes Mediant 1000 Voice-over-IP (VoIP) H.323 media gateway. 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.

  • Page 20: Related Documentation

    Ensure that you connect FXS ports to analog telephone or to PBX-trunk Warning: lines only and FXO ports to CO/PBX lines only. Disconnect the Mediant 1000 from the mains and from the Telephone Warning: Network Voltage (TNV) before servicing. To protect against electrical shock and fire, use a 26AWG min wire to Warning: connect FXO ports to the Public Switching Telephone Network (PSTN).

  • Page 21: Overview

    FXS module can be connected to the external trunk lines of a PBX. When deployed with a combination of FXO and FXS modules, the Mediant 1000 can be used as a PBX for Small Office Home Office (SOHO) users, and businesses not equipped with a PBX.

  • Page 22: Mediant 1000 Features

    Web browser (such as Microsoft™ Internet Explorer™ or Netscape™ Navigator™), from anywhere in the world with IP connectivity to the device. Mediant 1000 Features This section provides a high-level overview of some of the many Mediant 1000 supported features. 1.1.1 PSTN to H.323 Interworking The Mediant 1000 H.323 gateway supports various ISDN PRI protocols such as EuroISDN,...

  • Page 23: General Features

    H.323 User's Manual 1. Overview Supports a configurable channel select mode per trunk group. Supports various number manipulation rules for IP Tel and Tel IP, called and calling numbers. Interworking of ISDN Progress message and Progress Cause. Supports transfer of User-to-User Information Element between H.323 and PRI. Interworking of Calling Name, Calling Name Presentation, and Redirect Number in QSIG-to-H.323 and H.323-to-QSIG calls.

  • Page 24: Features

    Mediant 1000 1.1.3 H.323 Features The Mediant 1000 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.1.3.1 Gatekeeper Registers to known Gatekeeper.

  • Page 25: General

    Supports H.245 round trip delay. When activated the gateway periodically generates H.245 round trip delay requests. Note that the vulnerability of the Mediant 1000 was evaluated to H.323 messages per NISCC Vulnerability Advisory 006489/H323 (refer to http://www.uniras.gov.uk/vuls/2004/006489/h323.htm and to https://www.kb.cert.org/CERT_WEB/services/vul-notes.nsf/id/749342).
  • Page 26 Mediant 1000 Reader's Notes H.323 User's Manual Document #: LTRT-83401...

  • Page 27: Mediant Physical Description

    19-inch industrial platform chassis, 1U high and 13.8 inch deep. The Mediant 1000 supports a scalable, modular architecture that includes up to six analog modules, up to four digital modules, a single CPU module, a power supply module and an optional fan tray module (the extractable modules are shown in Section on page 33).

  • Page 28: Figure 2-2: Mediant 1000 Front Layout

    Reset button. Figure 2-2 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 using the Embedded Web Server, refer to Section 5.10...

  • Page 29: I/O Modules

    2.1.2.1 Dry Contact Connector (Labeled I and II) The Mediant 1000 provides dry contacts that can be connected to an external audible or visual alarm system (bell, siren, hooter, or light). 2.1.2.2...

  • Page 30: Reset Button (Labeled //)

    AC supply circuit. The front panel of the power supply unit provides 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.

  • Page 31: Front Panel Leds

    H.323 User's Manual 2. Mediant Physical Description 2.1.5 Front Panel LEDs Figure 2-3 below, shows the location of the front panel LEDs on the Mediant 1000. They are described below in Table 2-2, Table 2-3, Table 2-4, and Table 2-5.

  • Page 32: Mediant 1000 Rear Panel

    Either there is a failure / disruption in the AC supply or the power is currently not being supplied to the Mediant 1000 through the AC power supply entry. Mediant 1000 Rear Panel The Mediant 1000 rear panel provides the power connectors, as described in Table 2-6 (refer to Figure 2-4).

  • Page 33: Mediant 1000 Modules

    2. Mediant Physical Description Mediant 1000 Modules The extractable Mediant 1000 modules are shown in Table 2-7 below. Table 2-7: Extractable Mediant 1000 Modules (continues on pages 33 to 34) Module Description CPU module Digital I/O module (e.g., 2 spans)
  • Page 34 Mediant 1000 Table 2-7: Extractable Mediant 1000 Modules (continues on pages 33 to 34) Module Description Fan tray module with six fans and an air filter Power supply module H.323 User's Manual Document #: LTRT-83401...

  • Page 35: Installing The Mediant 1000

    Cable the Mediant 1000 (refer to Section on page 37). 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...

  • Page 36: Mounting The Mediant 1000

    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.

  • Page 37: Cabling The Mediant 1000

    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.

  • Page 38: Connecting The Mediant 1000 Rs-232 Port To Your Pc

    For the connector’s pinouts, refer to the figure below. 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.

  • Page 39: Setting Up A Dry Contact Relay Alarm System

    (refer to Section 5.10.4 on page 202) in the gateway's embedded Web server. The external alarm system is connected to the Mediant 1000 gateway's dry contact connector on the CPU module, using the supplied dry contact wires’ mate (refer to Figure 3-5).

  • Page 40: Cabling The Digital Lifeline

    3.4.3 Cabling the Digital Lifeline The Mediant 1000 gateway containing either one or two digital modules, each with 1 or 2 pairs of spans can provide a “lifeline” telephone link. In the event of a power failure, a relay connects trunk 1 to 2, and / or 3 to 4 in the same module. The link is provided by the closing of a metallic switch inside the module so that the trunk from the PBX is routed from the module to the PSTN.

  • Page 41: Figure 3-7: Lifeline Pinout And Rj-11 Port 1 In The Fxs Module

    The Lifeline provides a wired analog POTS phone connection to any PSTN or PBX FXS port when there is no power, or when the network connection fails. You can therefore, use the Lifeline phone even when the Mediant 1000 is not powered on or not connected to the network.

  • Page 42: Maintenance

    43) 3.5.1 Replacing Modules The Mediant 1000 I/O modules are hot-swappable (except for the OSN Server modules -- refer to Appendix on page 425). The replacement of Mediant 1000 communication modules (i.e., digital, FXS, and FXO) is performed using the Mediant 1000 embedded Web server.

  • Page 43: Inserting Modules To Previously Empty Slots

    To install a module to a previously empty slot, take these 6 steps: Power off the Mediant 1000. On the Mediant 1000 front panel, using a Phillips screwdriver remove the black metal cover plate protecting the module slot. Insert the module into the empty slot, with the plain side of the Printed Circuit Board (PCB) facing up.

  • Page 44: Figure 3-9: Slightly Extracted Fan Tray Unit

    If you are cleaning the filter, use a vacuum cleaner (set to 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. H.323 User's Manual Document #: LTRT-83401...
  • Page 45 H.323 User's Manual 3. Installing the Mediant 1000 Attach the (new / cleaned) air filter to the fan tray module; position the two holes on the filter over the pins on the fan tray (refer to Figure 3-10). Insert the fan tray unit into its slot, until the front panel is flush with the chassis plate.
  • Page 46 Mediant 1000 Reader's Note H.323 User's Manual Document #: LTRT-83401...

  • Page 47: Getting Started

    Default Gateway IP Address 0.0.0.0 Configuration Concepts You can utilize the Mediant 1000 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 Chapter on page 55).

  • Page 48: Assigning An Ip Address Using Http

    ‘Default Gateway IP Address’ field. Click the Reset button, and then at the prompt, click OK; the Mediant 1000 applies the changes and restarts. Record and retain the IP address and subnet mask you assign the Mediant Tip: 1000.

  • Page 49: Assigning An Ip Address Using The Voice Menu Guidance

    387. Use the reset button to physically reset the gateway causing it to use BootP; the Mediant 1000 changes its network parameters to the values provided by the BootP. 4.2.3 Assigning an IP Address Using the Voice Menu Guidance Initial configuration of the gateway can be performed using a standard touch-tone telephone connected to one of the FXS analog ports.

  • Page 50: Assigning An Ip Address Using The Cli

    From the 'Burn to FLASH' drop-down list, select 'Yes', and then click the Reset button; the Mediant 1000 is shut down and re-activated. A message about the waiting period is displayed. The screen is refreshed. Use a standard Telnet application to connect to the Mediant 1000 Embedded Telnet Server.
  • Page 51 Connect the RS-232 port to your PC (refer to Section 3.4.1 on page 38). Use serial communication software (e.g., HyperTerminal ) to connect to the Mediant 1000. Set your serial communication software to the following communications port settings: ♦ Baud Rate: 115,200 bps ♦...

  • Page 52: Configure The Mediant 1000 Basic Parameters

    Figure 4-1: Quick Setup Screen To configure basic H.323 parameters, take these 6 steps: If the Mediant 1000 is connected to a router with Network Address Translation (NAT) enabled, perform the following procedure. If it isn’t, leave the ‘NAT IP Address’ field undefined.

  • Page 53: Mediant

    Section 5.5.4.2 on page 98. Click the Reset button, and then at the prompt, click OK; the Mediant 1000 applies the changes and restarts. You are now ready to start using the VoIP gateway. To prevent unauthorized access to the Mediant 1000, it is recommended that you change the username and password that are used to access the Web Interface.
  • Page 54 Mediant 1000 Reader's Notes H.323 User's Manual Document #: LTRT-83401...

  • Page 55: Web Management

    H.323 User's Manual 5. Web Management 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™...

  • Page 56: Table 5-1: Available Access Levels And Their Privileges

    Mediant 1000 Table 5-1: Available Access Levels and their Privileges Numeric Access Level Privileges Representation* Security Administrator Read / write privileges for all screens Read-only privilege for security-related screens and Administrator read / write privileges for the others No access to security-related and file-loading...

  • Page 57: Limiting The Embedded Web Server To Read-Only Mode

    H.323 User's Manual 5. Web Management 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 of the access level used, are read-only and cannot be modified.

  • Page 58: Getting Acquainted With The Web Interface

    Getting Acquainted with the Web Interface Figure 5-2 shows the general layout of the Web Interface screen. Figure 5-2: Mediant 1000 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.

  • Page 59: Main Menu Bar

    Home icon: when clicked it opens the Home page screen (refer to Section 5.10 page 197). Corporate logo: AudioCodes’ corporate logo. For information on how to remove this logo Section 11.5 on page 303. Search engine: for searching ini file parameters configurable by using the Embedded Web Server (refer to Section 5.4.4...

  • Page 60: Searching For Configuration Parameters

    Mediant 1000 5.4.4 Searching for Configuration Parameters The Embedded Web Server provides a search engine that allows you to search any ini file parameter that is configurable by the Web server. The Search button, located near the bottom of the Main menu bar is used to perform parameter searches.

  • Page 61: Figure 5-4: Searched Parameter Highlighted In Screen

    H.323 User's Manual 5. Web Management In the searched result list, click the required parameter to open the screen in which the parameter appears. The relevant parameter is highlighted in green in the screen for easy viewing. Figure 5-4: Searched Parameter Highlighted in Screen If the searched parameter is not located, the "No Matches Found For This Note: String"...

  • Page 62: Protocol Management

    Mediant 1000 Protocol Management The Protocol Management menu is used to configure the gateway’s H.323 parameters and tables. Throughout this chapter, parameters contained within square brackets are Note: the names used to configure the parameters via the ini file. 5.5.1 Protocol Definition Parameters Use this submenu to configure the following gateway’s specific H.323 protocol parameters:...

  • Page 63: General Parameters

    H.323 User's Manual 5. Web Management 5.5.1.1 General Parameters The General Parameters option is used to configure general H.323 parameters. To configure the general parameters under Protocol Definition, take these 4 steps: Open the ‘General Parameters’ screen (Protocol Management menu > Protocol Definition submenu >...

  • Page 64: Table 5-3: Protocol Definition, General Parameters (Continues On Pages 64 To 68)

    Mediant 1000 Table 5-3: Protocol Definition, General Parameters (continues on pages 64 to 68) Parameter Description Connection Mode Gateway’s connection modes: Normal [IsFastConnectUsed=0, IsTunnelingUsed=0] (default). [IsFastConnectUsed, Tunneling IsTunnelingUsed] [IsFastConnectUsed=0, IsTunnelingUsed=1]. Fast Start [IsFastConnectUsed=1, IsTunnelingUsed=0]. Fast Start + Tunneling [IsFastConnectUsed=1, IsTunnelingUsed=1].
  • Page 65 H.323 User's Manual 5. Web Management Table 5-3: Protocol Definition, General Parameters (continues on pages 64 to 68) Parameter Description Open Media on Connect No [0] = Voice channel is opened after an Alert message is sent (default). Yes [1] = Voice channel is opened after the call is answered and a Connect [IsFSOpenMediaOnConne message is sent.
  • Page 66 H.225/H.245 messages (used for RAS, H.225 and H.245 [H323BasePort] protocols). The Mediant 1000 gateways uses 500 dynamic ports (except RTP ports) starting from this port. If you enter 0, or if not specified, the default ports are used.
  • Page 67 H.323 User's Manual 5. Web Management Table 5-3: Protocol Definition, General Parameters (continues on pages 64 to 68) Parameter Description H.225 Dial Port TCP port number on which the gateway sends H.225/Setup messages. The valid range is 0 to 65534. The default value is 1720. [H225DialPort] Send Channel Non 0 = Don't send (default)
  • Page 68 Mediant 1000 Table 5-3: Protocol Definition, General Parameters (continues on pages 64 to 68) Parameter Description Applicable to Tel IP calls. UseSourceNumberAsDisp 0 = The Tel Source Number is used as the IP Source Number and the Tel Display layName [Use Source Number as Name is used as the IP Display Name (if Tel Display Name is received).

  • Page 69: Gatekeeper Parameters

    H.323 User's Manual 5. Web Management 5.5.1.2 Gatekeeper Parameters Use this screen to configure parameters that are associated with Gatekeepers. To configure the Gatekeeper parameters, take these 4 steps: Open the ‘Gatekeeper’ parameters screen (Protocol Management menu > Protocol Definition submenu > Gatekeeper option); the ‘Gatekeeper’ parameters screen is displayed.

  • Page 70: Table 5-4: Gatekeeper Parameters (Continues On Pages 70 To 73)

    Mediant 1000 Table 5-4: Gatekeeper Parameters (continues on pages 70 to 73) Parameter Description General Working with Gatekeeper No [0] = Gatekeeper isn’t used. Yes [1] = Gatekeeper is used (default). [IsGatekeeperUsed] If you are using a Gatekeeper, enter the IP address of the primary Gatekeeper in the ‘Gatekeeper IP address’...
  • Page 71 H.323 User's Manual 5. Web Management Table 5-4: Gatekeeper Parameters (continues on pages 70 to 73) Parameter Description Second Gatekeeper ID String used to identify the first redundant Gatekeeper. Used in Registration Request (RRQ messages). [GatekeeperIP] The default value is an empty string. Note: This parameter is available only if you select Yes in the Gatekeeper Redundancy field.
  • Page 72 E.164 and H323-ID [2] NPI/TON from Table [3] NPI/TON and H323-ID [4] For detailed information on the available methods the Mediant 1000 gateway registers with a Gatekeeper, refer to Section on page 263. For detailed information on the Registration Prefixes Table, refer to Section 5.5.6...

  • Page 73: Coders

    H.323 User's Manual 5. Web Management Table 5-4: Gatekeeper Parameters (continues on pages 70 to 73) Parameter Description RAS Response Timeout Time in seconds that the gateway waits for a RAS response from the Gatekeeper. [sec] When this time expires, the gateway retransmits the RAS message. The range is 0 to 2 0.

  • Page 74: Table 5-5: Supported Coders

    Mediant 1000 From the Packetization Time drop-down list, select the packetization time (in msec) for the coder you selected. The packetization time determines how many coder payloads are combined into a single RTP packet. Note 1: If not specified, the ptime gets a default value.

  • Page 75: Dtmf & Dialing Parameters

    H.323 User's Manual 5. Web Management 5.5.1.4 DTMF & Dialing Parameters Use this screen to configure parameters that are associated with DTMF and dialing. To configure the dialing parameters, take these 4 steps: Open the ‘DTMF & Dialing’ screen (Protocol Management menu > Protocol Definition submenu >...
  • Page 76 The RFC 2833 DTMF relay dynamic payload type. Range: 96 to 99, 106 to 127; Default = 96 [RFC2833PayloadType] The 100, 102 to 105 range is allocated for AudioCodes proprietary usage. Note: Cisco is using payload type 101 for RFC 2833. Max Digits in Phone Maximum number of digits that can be dialed.
  • Page 77 H.323 User's Manual 5. Web Management Table 5-6: DTMF & Dialing Parameters (continues on pages 75 to 77) Parameter Description Digit Mapping Rules Digit map pattern. If the digit string (dialed number) has matched one of the patterns in the digit map, the gateway stops collecting digits and starts to establish [DigitMapping] a call with the collected number The digit map pattern contains up to 52 options separated by a vertical bar (|) and...

  • Page 78: Configuring The Advanced Parameters

    Mediant 1000 5.5.2 Configuring the Advanced Parameters Use this submenu to configure the following gateway’s advanced control protocol parameters: General Parameters (refer to Section 5.5.2.1 on page 78) Supplementary Services (refer to Section 5.5.2.2 on page 85) Metering Tones (refer to Section 5.5.2.3...

  • Page 79: Figure 5-9: Advanced Parameters, General Parameters Screen

    H.323 User's Manual 5. Web Management Figure 5-9: Advanced Parameters, General Parameters Screen Configure the general parameters under ‘Advanced Parameters’ according to Table 5-7. Click the Submit button to save your changes. To save the changes so they are available after a power fail, refer to Section 5.9.2 page 193.

  • Page 80: Table 5-7: Advanced Parameters, General Parameters (Continues On Pages 80 To 84)

    / port after the line is offhooked (FXS), seized (FXO) or connected (Digital). For IP-to-Tel calls, after the line is offhooked / seized / connected, the Mediant 1000 plays the DTMF digits (of the called number) towards the phone line.
  • Page 81 [1] = Enable DID. [EnableDIDWink] If enabled, the Mediant 1000 can be used for connection to EIA/TIA-464B DID Loop Start lines. Both FXO (detection) and FXS (generation) are supported. An FXO module dials DTMF digits after a Wink signal is detected (instead of a Dial tone).
  • Page 82 Mediant 1000 Table 5-7: Advanced Parameters, General Parameters (continues on pages 80 to 84) Parameter Description Disconnect on Broken No [0] = Don’t release the call. Connection Yes [1] = Call is released if RTP packets are not received for a predefined timeout (default).
  • Page 83 H.323 User's Manual 5. Web Management Table 5-7: Advanced Parameters, General Parameters (continues on pages 80 to 84) Parameter Description Debug Level Syslog logging level. One of the following debug levels can be selected: 0 [0] = Debug is disabled (default) [GwDebugLevel] 1 [1] = Flow debugging is enabled 2 [2] = Flow and device interface debugging are enabled...
  • Page 84 Mediant 1000 Table 5-7: Advanced Parameters, General Parameters (continues on pages 80 to 84) Parameter Description Delay After Reset [sec] Defines the amount of time (in seconds) the gateway’s operation is delayed after a reset cycle. [GWAppDelayTime] The valid range is 0 to 45. The default value is 7 seconds.

  • Page 85: Supplementary Services

    H.323 User's Manual 5. Web Management 5.5.2.2 Supplementary Services Use this screen to configure parameters that are associated with supplementary services. For detailed information on the supplementary services, refer to Section on page 257. To configure the supplementary services’ parameters, take these 4 steps: Open the ‘Supplementary Services’...

  • Page 86: Table 5-8: Supplementary Services Parameters (Continues On Pages 86 To 88)

    Mediant 1000 Table 5-8: Supplementary Services Parameters (continues on pages 86 to 88) Parameter Description Enable Hold Disable [0] = Disable the Hold service. Enable [1] = Enable the Hold service (H.450.4) (default). [EnableHold] If the Hold service is enabled, a user can activate Hold (or Unhold) using the hook- flash.
  • Page 87 [0] = Disabled (default). Enable [1] = H.450.7 MWI service is enabled. [EnableMWI] This parameter is applicable only to FXS modules. Note: The Mediant 1000 only supports reception of MWI. MWI Analog Lamp Disable [0] = Disable (default). Enable [1] = Enable visual Message Waiting Indication, supplies line voltage of...

  • Page 88: Metering Tones

    Mediant 1000 Table 5-8: Supplementary Services Parameters (continues on pages 86 to 88) Parameter Description MWI Display Disable [0] = Disabled (default). Enable [1] = Enable digital MWI using Caller ID Interface. [MWIDisplay] If enabled, the gateway generates an MWI FSK message that is displayed on the MWI display.

  • Page 89: Figure 5-12: Charge Codes Table Screen

    H.323 User's Manual 5. Web Management In the Tel to IP Routing table (Section 5.5.4.2 on page 98) assign a charge code rule to the routing rules you require. When a new call is established, the Tel to IP Routing table is searched for the destination IP addresses.

  • Page 90: Keypad Features

    Mediant 1000 Use the table to define up to 25 different charge codes (each charge code is defined in a single row). Each code can include from a single and up to four different time periods in a day (24 hours). Each time period is composed of: •...

  • Page 91: Table 5-10: Keypad Features Parameters (Continues On Pages 91 To 91)

    H.323 User's Manual 5. Web Management To save the changes so they are available after a power fail, refer to Section 5.9.2 page 193. Notes: • The method used by the gateway to collect dialed numbers is identical to the method used during a regular call (i.e., max digits, interdigit timeout, digit map, etc.).

  • Page 92: Configuring The Number Manipulation Tables

    Mediant 1000 5.5.3 Configuring the 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.

  • Page 93: Figure 5-14: Source Phone Number Manipulation Table For Tel Ip Calls

    H.323 User's Manual 5. Web Management To configure the Number Manipulation tables, take these 5 steps: Open the Number Manipulation screen you want to configure (Protocol Management menu > Manipulation Tables submenu); the relevant Manipulation table screen is displayed. Figure 5-14 shows the ‘Source Phone Number Manipulation Table for Tel IP calls’.
  • Page 94 Mediant 1000 Table 5-11: Number Manipulation Parameters (continues on pages 93 to 94) Parameter Description Prefix - Enter the number / string you want to add to the front of the phone Prefix / Suffix to add number. For example, if you enter 9 and the phone number is 1234, the new number is 91234.

  • Page 95: Dialing Plan Notation

    Numbering Plans and Type of Number Numbers are classified by their Numbering Plan Indication (NPI) and their Type of Number (TON). The Mediant 1000 supports all NPI/TON classifications used in the standard. A short list of the most important NPI/TON values are as follows:...

  • Page 96: Configuring The Routing Tables

    Mediant 1000 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...

  • Page 97: Table 5-13: Routing Tables, General Parameters (Continues On Pages 97 To 98)

    H.323 User's Manual 5. Web Management Table 5-13: Routing Tables, General Parameters (continues on pages 97 to 98) Parameter Description Add Trunk Group ID as No [0] = Don’t add trunk group ID as prefix (default). Prefix Yes [1] = Add trunk group ID as prefix to called number. If enabled, then the trunk group ID is added as a prefix to the destination phone [AddTrunkGroupAsPrefix] number for Tel IP calls.

  • Page 98: Tel To Ip Routing Table

    Mediant 1000 Table 5-13: Routing Tables, General Parameters (continues on pages 97 to 98) Parameter Description Max Allowed Packet Loss Packet loss percentage at which the IP connection is considered a failure. for Alt Routing [%] The range is 1% to 20%. The default value is 20%.

  • Page 99: Figure 5-16: Tel To Ip Routing Table Screen

    H.323 User's Manual 5. Web Management 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.

  • Page 100: Ip To Trunk Group Routing

    Mediant 1000 Table 5-14: Tel to IP Routing Table (continues on pages 100 to 100) Parameter Description Tel to IP Routing Mode Route calls before manipulation [0] = Tel IP calls are routed before the number manipulation rules are applied (default).
  • Page 101 H.323 User's Manual 5. Web Management 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 screen (Section 5.5.10 on page 124) or according to the global parameter...

  • Page 102: Figure 5-17: Ip To Trunk Group Routing Table Screen

    Mediant 1000 To configure the IP to Trunk Group Routing table, take these 6 steps: 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’...

  • Page 103: Internal Dns Table

    H.323 User's Manual 5. Web Management Table 5-15: IP to Trunk Group Routing Table Parameter Description Any H.323 incoming call 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 and its source IP address matches the address defined in the ‘Source IP Address’...

  • Page 104: Reasons For Alternative Routing

    Mediant 1000 To configure the internal DNS table, take these 7 steps: 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-18: Internal DNS Table Screen In the ‘Domain Name' field, enter the host name to be translated.

  • Page 105: Figure 5-19: Reasons For Alternative Routing Screen

    H.323 User's Manual 5. Web Management For configuring this table, you can also use the ini file parameters AltRouteCauseTel2IP and AltRouteCauseIP2Tel (refer to Section 6.5.9 on page 236). To configure the reasons for alternative routing, take these 5 steps: Open the ‘Reasons for Alternative Routing’ screen (Protocol Management menu > Routing Tables submenu >...

  • Page 106: Configuring The Profile Definitions

    5.5.5 Configuring the Profile Definitions Utilizing the Profiles feature, the Mediant 1000 provides high-level adaptation when connected to a variety of equipment (from both Tel and IP sides) and protocols, each of which requires a different system behavior. Using Profiles, users can assign different Profiles (behavior) on a per-call basis, using the Tel to IP and IP to Trunk Group Routing tables, or associate different Profiles to the gateway’s endpoints (analog modules) or B-...

  • Page 107: Figure 5-20: Coder Group Settings Screen

    H.323 User's Manual 5. Web Management To configure the coder group settings, take these 11 steps: 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-20: Coder Group Settings Screen From the Coder Group ID drop-down list, select the coder group you want to edit (up to four coder groups can be configured).

  • Page 108: Tel Profile Settings

    Mediant 1000 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 the gateway’s channels, thereby applying different behavior to different channels.
  • Page 109 H.323 User's Manual 5. Web Management In the ‘Profile Name’ field, enter a name that enables you to identify the Profile intuitively and easily. In the ‘Profile Preference’ drop-down list, select the preference (1-20) of the current Profile. The preference option is used to determine the priority of the Profile. Where ‘20’...

  • Page 110: Ip Profile Settings

    Mediant 1000 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.
  • Page 111 H.323 User's Manual 5. Web Management From the ‘Profile Preference’ drop-down list, select the preference (1-20) of the current Profile. The preference option is used to determine the priority of the Profile. Where ‘20’ is the highest preference value. If both IP and Tel profiles apply to the same call, the coders and other common parameters (noted by an asterisk in the description of the parameter IPProfile_ID) of the preferred Profile are applied to that call.

  • Page 112: Configuring The Registration Prefixes

    5.5.6 Configuring the Registration Prefixes The Gatekeeper Registration Prefixes Table enables the Mediant 1000 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.

  • Page 113: Table 5-16: Registration Prefixes Table

    H.323 User's Manual 5. Web Management Table 5-16: 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.

  • Page 114: Configuring The Endpoint Settings

    Mediant 1000 5.5.7 Configuring the Endpoint Settings The Endpoint Settings screens enable you to configure port-specific parameters. The Endpoint Settings screens are only applicable to the analog modules. Note: 5.5.7.1 H.323 Port ID The H.323 Port ID table enables you to assign a specific ID to each FXS or FXO port.

  • Page 115: Automatic Dialing

    H.323 User's Manual 5. Web Management 5.5.7.2 Automatic Dialing Use the Automatic Dialing Table to define telephone numbers that are automatically dialed when a specific port is used. You can also configure the Automatic Dialing table using the ini file parameter TargetOfChannelX (refer to Section 6.5.9 on page 236).

  • Page 116: Caller Id

    Mediant 1000 5.5.7.3 Caller ID Use the Caller Display Information screen to send (to IP) Caller ID information when a call is made using the VoIP gateway (relevant to both FXS and FXO). The person receiving the call can use this information for caller identification. The information on this table is sent in the H.225 Setup message sent to the remote party.

  • Page 117: Call Forward

    H.323 User's Manual 5. Web Management 5.5.7.4 Call Forward The VoIP gateway allows you to forward incoming IP Tel calls based on the VoIP gateway port to which the call is routed (applicable only to FXS modules). The Call Forwarding Table is applicable only if the Call Forward feature is enabled. To enable Call Forward set ‘Enable Call Forward’...

  • Page 118: Caller Id Permissions

    Mediant 1000 5.5.7.5 Caller ID Permissions The Caller ID Permissions table is used to enable or disable (per port) the Caller ID generation (for FXS modules) and detection (for FXO modules). If a port isn’t configured, its Caller ID generation / detection are determined according to the global parameter ‘EnableCallerID’...

  • Page 119: Configuring The Fxo Parameters

    H.323 User's Manual 5. Web Management 5.5.8 Configuring the FXO Parameters Use this screen to configure the gateway’s specific FXO parameters. To configure the FXO parameters, take these 4 steps: Open the ‘FXO Settings’ screen (Protocol Management menu > FXO Settings > FXO Settings option);...
  • Page 120 No [0] = Don’t wait for dial tone. Yes [1] = Wait for dial tone (default). [IsWaitForDialTone] Used for IP Mediant 1000/FXO modules, when ‘One Stage Dialing’ is enabled. If ‘wait for dial tone’ is enabled, the FXO module dials the phone number (to the PSTN/PBX line) only after it detects a dial tone.
  • Page 121 H.323 User's Manual 5. Web Management Table 5-18: FXO Parameters (continues on pages 119 to 121) Parameter Description Answer Supervision Yes [1] = FXO module sends Connect message when speech/fax/modem is detected. [EnableVoiceDetection] No [0] = Connect is sent immediately after the FXO module finishes dialing (default).

  • Page 122: Configuring The Trunk Group Table

    Mediant 1000 5.5.9 Configuring the Trunk Group Table Use the Trunk Group table to assign trunk groups, profiles and logical telephone numbers to the gateway's channels. Trunk Groups are used for routing IP Tel calls with common rules. Channels that are not defined are disabled.
  • Page 123 H.323 User's Manual 5. Web Management Table 5-19: Trunk Group Table (continues on pages 122 to 123) Parameter Description 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.

  • Page 124: Configuring The Trunk Group Settings

    Mediant 1000 5.5.10 Configuring the Trunk Group Settings The Trunk Group Settings Table is used to determine the method in which new calls are assigned to 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 >...

  • Page 125: Table 5-20: Channel Select Modes

    H.323 User's Manual 5. Web Management Table 5-20: Channel Select Modes Mode Description By Dest 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.

  • Page 126: Configuring The Digital Gateway Parameters

    Mediant 1000 5.5.11 Configuring the Digital Gateway Parameters The 'Digital Gateway' screen is used to configure miscellaneous digital parameters. To configure the digital gateway parameters, take these 4 steps: Open the ‘Digital Gateway Parameters' screen (Protocol Management menu > Digital Gateway Parameters); the ‘Digital Gateway Parameters' screen is displayed.
  • Page 127 0 = Disabled (default). 1 = TDM Tunneling is enabled. [EnableTDMoverIP] When TDM Tunneling is enabled, the originating Mediant 1000 automatically initiates H.323 calls from all enabled B-channels belonging to the E1/T1/J1 spans that are configured with the ‘Transparent’ protocol.
  • Page 128 Mediant 1000 Table 5-21: Digital Gateway Parameters (continues on pages 126 to 128) Parameter Description Trunk Groups to Send IE A list of Trunk Group IDs (up to 50 characters) from where the optional ISDN IE, defined by the parameter ‘AddIEinSetup’, is sent.

  • Page 129: Advanced Configuration

    H.323 User's Manual 5. Web Management Advanced Configuration Use this menu to set the gateway’s advanced configuration parameters. Parameters contained within square brackets are the names used to Note: configure the parameters via the ini file. 5.6.1 Configuring the Network Settings From the Network Settings you can: Configure the IP Settings (refer to Section 5.6.1.1...

  • Page 130: Table 5-22: Network Settings, Ip Settings Parameters (Continues On Pages 130 To 132)

    Mediant 1000 Configure the IP Settings according to Table 5-22. Click the Submit button to save your changes. To save the changes so they are available after a power fail, refer to Section 5.9.2 page 193. Table 5-22: Network Settings, IP Settings Parameters (continues on pages 130 to 132)
  • Page 131 BootP/DHCP procedure and the parameter DHCPEnable reverts to ‘0’). Note that throughout the DHCP procedure the BootP/TFTP application must be deactivated. Otherwise, the Mediant 1000 receives a response from the BootP server instead of the DHCP server. Note: For additional information on DHCP, refer to Section page 254.

  • Page 132: Configuring The Application Settings

    Mediant 1000 Table 5-22: Network Settings, IP Settings Parameters (continues on pages 130 to 132) Parameter Description Media Premium QoS Sets the DiffServ value for Premium Media service class content (only if IPDiffServ is not set in the selected IP Profile).

  • Page 133: Configuring The Nfs Settings

    OSs, and network architectures. Up to five different NFS file systems can be configured. NFS is utilized by the Mediant 1000 to load the cmp, ini and configuration files via the Automatic Update mechanism (refer to Section 11.3...

  • Page 134: Figure 5-35: Nfs Settings Table Screen

    Mediant 1000 To configure the NFS Settings parameters, take these 7 steps: Open the ‘Application Settings’ screen (Advanced Configuration menu > Network Settings > Application Settings option); the ‘Application Settings’ screen is displayed (Figure 5-34). Open the NFS Table screen by clicking the arrow sign (-->) to the right of the NFS label;...

  • Page 135: Figure 5-36: Nfs Ini File Example

    H.323 User's Manual 5. Web Management Table 5-24: Network Settings, NFS Settings Parameters Parameter Description Line Number The row index of the remote file system. The valid range is 0 to 4. [NFSServers_Index] Host / IP The domain name or IP address of the NFS server. If a domain name is provided, a DNS server must be configured.

  • Page 136: Configuring The Ip Routing Table

    Mediant 1000 5.6.1.4 Configuring the IP Routing Table The IP routing table is used by the gateway to determine IP routing rules. It can be used, for example, to define static routing rules for the OAM and Control networks since a default gateway isn’t supported for these networks (refer to Section...
  • Page 137 H.323 User's Manual 5. Web Management Table 5-25: IP Routing Table Column Description Column Name Description [ini File Parameter Name] 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’...

  • Page 138: Configuring The Vlan Settings

    Mediant 1000 5.6.1.5 Configuring the VLAN Settings For detailed information on the Mediant 1000 VLAN implementation, refer to Section page 285. To configure the VLAN Settings parameters, take these 4 steps: Open the ‘VLAN Settings’ screen (Advanced Configuration menu > Network Settings >...
  • Page 139 H.323 User's Manual 5. Web Management Table 5-26: Network Settings, VLAN Settings Parameters Parameter Description Control VLAN ID Sets the control VLAN identifier. The valid range is 1 to 4094. The default value is 2. [VlanControlVlanID] Media VLAN ID Sets the media VLAN identifier. The valid range is 1 to 4094.

  • Page 140: Configuring The Media Settings

    5.6.2 Configuring the Media Settings Use these menus to set the gateway’s channel parameters. These parameters are applied to all Mediant 1000 channels. From the Media Settings page you can define: Voice Settings (refer to Section 5.6.2.1). Fax / Modem / CID Settings (refer to Section 5.6.2.2...

  • Page 141: Table 5-27: Media Settings, Voice Settings Parameters

    H.323 User's Manual 5. Web Management Click the Submit button to save your changes. To save the changes so they are available after a power fail, refer to Section 5.9.2 page 193. Table 5-27: Media Settings, Voice Settings Parameters Parameter Description Voice Volume Voice gain control in dB.

  • Page 142: Configuring The Fax / Modem / Cid Settings

    Mediant 1000 5.6.2.2 Configuring the Fax / Modem / CID Settings To configure the Fax / Modem / CID Settings parameters, take these 4 steps: Open the ‘Fax / Modem / CID Settings’ screen (Advanced Configuration menu > Media Settings > Fax / Modem / CID Settings option); the ‘Fax / Modem / CID Settings’...
  • Page 143 H.323 User's Manual 5. Web Management Table 5-28: Media Settings, Fax/Modem/CID Parameters (continues on pages 142 to 144) Parameter Description Caller ID Type Defines one of the following standards for detection (FXO) and generation (FXS) of Caller ID and detection (FXO) of MWI (when specified) signals. [CallerIDType] Bellcore [0] (Caller ID and MWI) (default).
  • Page 144 Mediant 1000 Table 5-28: Media Settings, Fax/Modem/CID Parameters (continues on pages 142 to 144) Parameter Description Fax Relay ECM Enable Disable [0] = Error Correction Mode (ECM) mode is not used during fax relay. [FaxRelayECMEnable] Enable [1] = ECM mode is used during fax relay (default).

  • Page 145: Configuring The Rtp / Rtcp Settings

    H.323 User's Manual 5. Web Management 5.6.2.3 Configuring the RTP / RTCP Settings To configure the RTP / RTCP Settings parameters, take these 4 steps: Open the ‘RTP / RTCP Settings’ screen (Advanced Configuration menu > Media Settings > RTP / RTCP Settings option); the ‘RTP / RTCP Settings’ screen is displayed.

  • Page 146: Table 5-29: Media Settings, Rtp / Rtcp Parameters

    Mediant 1000 Table 5-29: Media Settings, RTP / RTCP Parameters Parameter Description Dynamic Jitter Buffer Minimum Delay Minimum delay for the Dynamic Jitter Buffer. The valid range is 0 to 150 milliseconds. [DJBufMinDelay] The default delay is 10 milliseconds. Note: For more information on the Jitter Buffer, refer to Section page 266.

  • Page 147: Configuring The Hook-Flash Settings

    H.323 User's Manual 5. Web Management Table 5-29: Media Settings, RTP / RTCP Parameters Parameter Description Remote RTP Base UDP Port Determines the lower boundary of UDP ports used for RTP, RTCP and T.38 by a remote gateway. If this parameter is set to a non-zero value, [RemoteBaseUDPPort] ThroughPacket™...

  • Page 148: Configuring The General Media Settings

    Mediant 1000 Table 5-30: Media Settings, Hook-Flash Settings Parameters Parameter Description Min. Flash-Hook Detection Period Sets the minimal time (in msec) for detection of a flash-hook event (for [msec] FXS only). The valid range is 25 to 300. The default value is 300 msec.

  • Page 149: Table 5-31: Media Settings, General Media Settings Parameters

    H.323 User's Manual 5. Web Management Table 5-31: Media Settings, General Media Settings Parameters Parameter Description DSP Version Template Number N/A. Max Echo Canceller Length Maximum Echo Canceler Length in msec: [MaxEchoCancellerLength] 0 = based on various internal gateway settings -- 64 msec (default) 4 = 32 msec 11 = 64 msec Note 1: The gateway must be reset after the value of...

  • Page 150: Configuring The Trunk Settings

    If the trunk can’t be stopped because it provides the gateway’s clock Note: (assuming the Mediant 1000 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 (refer to Section 5.6.4...
  • Page 151 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 1000 H.323 Release Notes). When modifying the ‘Protocol Type’ field, the menu is automatically Note: updated according to the selected protocol (ISDN, CAS or Transparent).

  • Page 152: Table 5-32: E1/T1/J1 Configuration Parameters (Continues On Pages 152 To 156)

    Mediant 1000 Table 5-32: E1/T1/J1 Configuration Parameters (continues on pages 152 to 156) ini File Field Name Valid Range and Description Web Parameter Name Sets the PSTN protocol to be used for this trunk. ProtocolType [Protocol Type] 1 = E1_EURO_ISDN...
  • Page 153 H.323 User's Manual 5. Web Management Table 5-32: E1/T1/J1 Configuration Parameters (continues on pages 152 to 156) ini File Field Name Valid Range and Description Web Parameter Name Defines the trace level. TraceLevel [Trace Level] Valid options include: 0 = No trace (default) 1= Full ISDN trace 2 = Layer 3 ISDN trace 3 = Only ISDN Q.931 messages trace...
  • Page 154 Mediant 1000 Table 5-32: E1/T1/J1 Configuration Parameters (continues on pages 152 to 156) ini File Field Name Valid Range and Description Web Parameter Name Enable / disable Rx ISDN overlap per trunk ID. ISDNRxOverlap_x [Enable Receiving of Overlap 0 = Disabled (default).
  • Page 155 H.323 User's Manual 5. Web Management Table 5-32: E1/T1/J1 Configuration Parameters (continues on pages 152 to 156) ini File Field Name Valid Range and Description Web Parameter Name ISDN Flexible Behavior Parameters ISDN protocol is implemented in different Switches / PBXs by different vendors. Several implementations vary a little from the specification.
  • Page 156 Mediant 1000 Table 5-32: E1/T1/J1 Configuration Parameters (continues on pages 152 to 156) ini File Field Name Valid Range and Description Web Parameter Name 16 = The gateway clears down the call if it receives a NOTIFY message ISDNGeneralCCBehavior [General Call Control specifying ‘User-Suspended’.

  • Page 157: Configuring The Tdm Bus Settings

    5.9.2 page 193. A device reset is required to activate the TDM Bus Settings parameters. To reset the Mediant 1000, refer to Section 5.9.3 on page 195. Usually the ‘PCM Law Select’ parameter is set to A-law for E1 trunks and Note: to µ-law for T1 trunks.
  • Page 158 Mediant 1000 Table 5-33: TDM Bus Settings Parameters (continues on pages 157 to 158) Parameter Description Idle ABCD Pattern ABCD (CAS) Pattern to be applied to CAS signaling bus when the channel is idle. [IdleABCDPattern] Range 0x0 to 0xF Default = -1 (default, pattern = 0000) Note: This is only relevant when using PSTN interface with CAS protocols.

  • Page 159: Restoring And Backing Up The Gateway Configuration

    H.323 User's Manual 5. Web Management 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.

  • Page 160: Regional Settings

    CAS) to the gateway. For detailed information on the configuration files, refer to Section 5.8.2 on page 189. To configure the date and time of the Mediant 1000, take these 3 steps: Open the ‘Regional Settings’ screen (Advanced Configuration menu > Regional Settings); the ‘Regional Settings' screen is displayed.
  • Page 161 Notes: • Saving a configuration file to flash memory may disrupt traffic on the Mediant 1000. To avoid this, disable all traffic on the gateway before saving to flash memory by performing a graceful lock (refer to Section 5.9.1 on page 192).

  • Page 162: Security Settings

    Mediant 1000 5.6.7 Security Settings From the Security Settings you can: Configure the Web User Accounts (refer to Section 5.6.7.1 below) Configure the Web & Telnet Access List (refer to Section 5.6.7.2 on page 163) Configure the Firewall Settings (refer to Section 5.6.7.3...

  • Page 163: Configuring The Web And Telnet Access List

    H.323 User's Manual 5. Web Management To change the access level of the secondary account (the access level of the primary account cannot be changed), from the ‘Access Level’ drop-down list, select the new access level, and then click the button Change Access Level; the new access level is applied immediately.

  • Page 164: Configuring The Firewall Settings

    5.6.7.3 Configuring the Firewall Settings The Mediant 1000 accommodates an internal Firewall, allowing the security administrator to define network traffic filtering rules. For detailed information on the internal Firewall, refer to Section 13.4 on page 337.
  • Page 165 H.323 User's Manual 5. Web Management To edit a rule, take these 5 steps: Select the radio button of the entry you want to edit. Click the Make Rule Editable button; the rule’s fields can now be modified. Modify the fields according to your requirements. Click the Apply Rule Settings button to save the changes.

  • Page 166: Table 5-34: Internal Firewall Fields

    Mediant 1000 Table 5-34: Internal Firewall Fields Parameter Description A read-only field that indicates whether the rule is active or not. Is Rule Active Note: After reset all rules are active. Source IP IP address (or DNS name) of source network, or a specific host.

  • Page 167: Configuring The Certificates

    H.323 User's Manual 5. Web Management 5.6.7.4 Configuring the Certificates Use the Certificates screen to replace the server (refer to Section 13.2.3 on page 331) and client (refer to Section 13.2.4 on page 332) certificates and to update the private key (HTTPSPkeyFileName, described in Section 6.5.4 on page 223).

  • Page 168: Table 5-35: General Security Settings Parameters (Continues On Pages 168 To 169)

    Mediant 1000 Table 5-35: General Security Settings Parameters (continues on pages 168 to 169) Parameter Description Secured Web Connection Determines the protocol types used to access the Embedded Web Server. HTTP and HTTPS [0] (default). [HTTPSOnly] HTTPS only [1] (unencrypted HTTP packets are blocked).

  • Page 169: Configuring The Ipsec Table

    H.323 User's Manual 5. Web Management Table 5-35: General Security Settings Parameters (continues on pages 168 to 169) Parameter Description Local RADIUS Password Cache Defines the gateway’s mode of operation regarding the timer (configured by Mode the parameter RadiusLocalCacheTimeout) that determines the validity of the username and password (verified by the RADIUS server).

  • Page 170: Configuring The Management Settings

    Mediant 1000 5.6.8 Configuring the Management Settings To configure the Management Settings parameters, take these 4 steps: Open the ‘Management Settings’ screen (Advanced Configuration menu > Management Settings); the ‘Management Settings’ screen is displayed. Figure 5-51: Management Settings Screen Configure the Management Settings according to Table 5-36.

  • Page 171: Table 5-36: Management Settings Parameters (Continues On Pages 171 To 172)

    The valid range is a 99-character string Activity Types to Report via 'Activity Log' Messages The Activity Log mechanism enables the Mediant 1000 to send log messages (to a Syslog server) that report certain types of web actions according to a pre-defined filter.

  • Page 172: Configuring The Snmp Managers Table

    Mediant 1000 Table 5-36: Management Settings Parameters (continues on pages 171 to 172) Parameter Description Device Software Update cmp loading via the Software Upgrade Wizard. [ActivityListToLog = SWU] Access to Restricted Domains Access to Restricted Domains. The following screens are restricted:...

  • Page 173: Table 5-37: Snmp Managers Table Parameters

    H.323 User's Manual 5. Web Management If you clear a checkbox and then click Submit, all settings in the same row Note: revert to their defaults. Table 5-37: SNMP Managers Table Parameters Parameter Description Checkbox Up to five parameters, each determines the validity of the parameters (IP address and port number) of the corresponding SNMP Manager used to receive [SNMPManagerIsUsed_x] SNMP traps.

  • Page 174: Configuring The Snmp Community Strings

    Mediant 1000 5.6.8.2 Configuring the SNMP Community Strings Use the SNMP Community Strings table to configure up to five read-only and up to five read / write SNMP community strings, and to configure the community string that is used for sending traps. For detailed information on SNMP community strings, refer to section 15.7.1...

  • Page 175: Configuring Snmp V3 Users

    H.323 User's Manual 5. Web Management 5.6.8.3 Configuring SNMP V3 Users Use the SNMP V3 Table to configure authentication and privacy for up to 10 SNMP v3 users. To configure the SNMP v3 users, take the following 6 steps: Access the ‘Management Settings’ screen (Advanced Configuration menu > Management Settings);...
  • Page 176 Mediant 1000 Table 5-39: SNMP V3 Users Parameters (continues on pages 175 to 176) Parameter Description Privacy protocol to be used for the SNMP v3 user. [SNMPUsers_PrivProtocol] [PrivProtocol] 0 = none (default) 1 = DES 2 = 3DES 3 = AES128...

  • Page 177: Status & Diagnostics

    H.323 User's Manual 5. Web Management 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. 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.

  • Page 178: Figure 5-55: Ip Connectivity Screen

    Mediant 1000 Figure 5-55: IP Connectivity Screen Table 5-40: IP Connectivity Parameters Column Name Description IP Address IP address defined in the destination IP address field in the Tel to IP Routing table. IP address that is resolved from the host name defined in the destination IP address field in the Tel to IP Routing table.

  • Page 179: Call Counters

    H.323 User's Manual 5. Web Management 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).
  • Page 180 Mediant 1000 Table 5-41: Call Counters Description (continues on pages 179 to 180) Counter Description Number of Established This counter indicates the number of established calls. It is incremented as a result of Calls one of the following release reasons, if the duration of the call is bigger then zero:...

  • Page 181: Call Routing Status

    H.323 User's Manual 5. Web Management 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 and FQDN (if used) of the Proxy server with which the gateway currently operates. To view the Call Routing Status screen, take this step: Open the 'Call Routing Status' screen (Status &...

  • Page 182: Activating The Internal Syslog Viewer

    It's not recommended to keep a ‘Message Log’ session open (even if the Note: window is minimized) for a prolonged period (refer to the Note below). This may cause the Mediant 1000 to overload. For prolong debugging use an external Syslog server (refer to Section 14.3 on page 342).

  • Page 183: Device Information

    Capture the screen and email it to ‘our’ Technical Support personnel to ensure quick diagnosis and effective corrective action. From this screen you can also view and remove any loaded files used by the Mediant 1000 (stored in the RAM). To access the System Information screen, take this step: Open the ‘Device Information’...

  • Page 184: Software Update

    Mediant 1000 Software Update The Software Update menu enables users to upgrade the Mediant 1000 software by loading a new cmp file along with the ini and a suite of auxiliary files, or to update the existing auxiliary files. The ‘Software Update’ menu comprises the following submenus: Software Upgrade Wizard (refer to Section 5.8.1...

  • Page 185: Figure 5-60: Start Software Upgrade Screen

    Mediant 1000 (click the Cancel button). If you continue the process (by clicking the Start Software Upgrade button, the process must be followed through and completed with a Mediant 1000 reset at the end. If you click the Cancel button in any of the subsequent screens, the Mediant 1000 is automatically reset with the configuration that was previously burned in flash memory.

  • Page 186: Figure 5-62: Cmp File Successfully Loaded

    Mediant 1000 Click the Browse button, navigate to the cmp file and click the button Send File; the cmp file is loaded to the Mediant 1000 and you’re notified as to a successful loading (refer to Figure 5-62). Figure 5-62: cmp File Successfully Loaded Note that the four action buttons (Cancel, Reset, Back, and Next) are now activated (following cmp file loading).

  • Page 187: Figure 5-64: Load A Cpt File Screen

    Click Browse and navigate to the ini file; the check box ‘Use existing configuration’, by default checked, becomes unchecked. Click Send File; the ini file is loaded to the Mediant 1000 and you’re notified as to a successful loading. •...

  • Page 188: Figure 5-65: Finish Screen

    Mediant 1000 Figure 5-65: FINISH Screen Figure 5-66: ‘End Process’ Screen Click the End Process button; the ‘Quick Setup’ screen appears and the full Web application is reactivated. H.323 User's Manual Document #: LTRT-83401...

  • Page 189: Auxiliary Files

    The ‘Auxiliary Files’ screen enables you to load various files to the gateway, as described Table 5-43. For detailed information on these files, refer to Chapter on page 367. For information on deleting these files from the Mediant 1000, refer to Section 5.7.3 on page 183.

  • Page 190: Loading The Auxiliary Files Via The Embedded Web Server

    195. Notes: • Saving an auxiliary file to flash memory may disrupt traffic on the Mediant 1000. To avoid this, disable all traffic on the device by performing a graceful lock (refer to Section 5.9.1 on page 192).

  • Page 191: Loading The Auxiliary Files Via The Ini File

    To load the auxiliary files via the ini file, take these 3 steps: In the ini file, define the auxiliary files to be loaded to the Mediant 1000. You can also define in the ini file whether the loaded files should be stored in the non-volatile memory so that the TFTP process is not required every time the Mediant 1000 boots up.

  • Page 192: Maintenance

    Mediant 1000 Maintenance The Maintenance menu is used for the following operations: Locking and unlocking the gateway (refer to Section 5.9.1 on page 192) Saving the gateway's configuration (refer to Section 5.9.2 on page 193) Resetting the gateway (refer to Section 5.9.3...

  • Page 193: Saving Configuration

    H.323 User's Manual 5. Web Management In the 'Lock Timeout' field (relevant only if the 'Graceful Option' in the previous step is set to 'Yes'), enter the time (in seconds) after which the gateway locks. Note that if no traffic exists and the time has not expired, the gateway locks. Click the LOCK button;...

  • Page 194: Figure 5-69: Maintenance Actions Screen

    Mediant 1000 To save the changes to the non-volatile, take these 2 steps: Open the ‘Maintenance Actions' screen (Maintenance menu); the ‘Maintenance Actions' screen is displayed. Figure 5-69: Maintenance Actions Screen Click the BURN button; a confirmation message appears when the save is completed successfully.

  • Page 195: Resetting The Mediant 1000

    H.323 User's Manual 5. Web Management 5.9.3 Resetting the Mediant 1000 The 'Maintenance Actions' screen enables you to remotely reset the gateway. Before you reset the gateway, you can choose the following options: Save the gateway's current configuration to the flash memory (non-volatile).
  • Page 196 Mediant 1000 In the 'Shutdown Timeout' field (relevant only if the 'Graceful Option' in the previous step is set to 'Yes'), enter the time after which the gateway resets. Note that if no traffic exists and the time has not expired, the gateway resets.

  • Page 197: Monitoring The Gateway (Home Page)

    The Home page also displays general information in the General Information pane. This information includes parameters such as the gateway's IP address, the number of digital and analog ports, and firmware version. Table 5-44 on page describes the areas of the graphic display of the Mediant 1000 chassis. Version 5.0 December 2006...

  • Page 198: Table 5-44: Description Of The Areas Of The Home Page

    Mediant 1000 Table 5-44: Description of the Areas of the Home Page Item# Description ALARMS button for viewing the Active Alarms table. For a detailed description, refer to Section 5.10.4 on page 202. Module slot number (1 to 6). Module type (digital, FXO, or FXS).

  • Page 199: Monitoring The Mediant 1000 Trunks And Channels

    5.10.1 Monitoring the Mediant 1000 Trunks and Channels The Home page provides real-time monitoring of the trunks and channels. To monitor the status of the Mediant 1000 trunks and channel ports, take this step: Open the Home page by clicking the Home icon; the Home page is displayed.

  • Page 200: Figure 5-72: Status Of Channels Per Trunk In The Trunk & Channel Screen

    Mediant 1000 To view a detailed status of a channel, take these 3 steps: In the Home page, click the trunk or analog port of whose status you want to view; a shortcut menu appears. From the shortcut menu, choose Port Settings; the following appears, depending on whether you clicked a trunk or FXO/FXS port: •...

  • Page 201: Monitoring The Modules

    H.323 User's Manual 5. Web Management Table 5-46: Trunk Channel Status Color Indicators continues on pages 201 to 201) Indicator Color Label Description Grey Configured, but currently no call Inactive Green Call in progress (RTP traffic) Active Pink Configured for SS7 (Currently not supported) Dark blue Not configured...

  • Page 202: Monitoring Ethernet Ports, Dry Contacts, Power Supply Units, And Fan Tray Unit202

    Open the Home page by clicking the Home icon; the Home page is displayed. On the graphical display of the Mediant 1000 front panel, click the the area labelled 'ALARMS' or any area that displays the tooltip 'Click To Get Active Alarms Table'; the Active Alarms table appears.

  • Page 203: Viewing Trunk Settings

    H.323 User's Manual 5. Web Management 5.10.5 Viewing Trunk Settings The Home page provides an alternative path (Advanced Configuration menu > Trunk Settings) for accessing the 'Trunk Settings' screen (refer to Section 5.6.3 on page 150), in which the trunk settings are viewed and configured. To view the trunk settings, take these 3 steps: In the Home page, click the required trunk port;...

  • Page 204: Viewing Ethernet Port Settings

    Mediant 1000 5.10.6 Viewing Ethernet Port Settings The 'Ethernet Port Information' screen provides read-only information on the Ethernet connection used by the Mediant 1000. The Ethernet Port Information parameters are displayed in Table 5-49. For detailed information on the Ethernet interface configuration, refer to Section on page 279.

  • Page 205: Releasing An Analog Channel

    H.323 User's Manual 5. Web Management 5.10.8 Releasing an Analog Channel The Home page allows you to inactivate (release) an FXO or FXS analog channel. This is sometimes useful in scenarios, for example, when the gateway (FXO) is connected to a PBX and the communication between the two can't be disconnected (e.g., when using reverse polarity).

  • Page 206: Figure 5-81: Confirmation Message Box After Clicking Remove Module Button

    Mediant 1000 Click the Remove Module button; a message box appears requesting you to confirm module removal. Figure 5-81: Confirmation Message Box after Clicking Remove Module Button Click OK to confirm module removal; after a few seconds, the module is "removed"...

  • Page 207: Logging Off The Embedded Web Server

    H.323 User's Manual 5. Web Management 5.11 Logging Off the Embedded Web Server The Log Off button enables you to log off the Embedded Web Server and to re-access it with a different account. For detailed information on the Web User Accounts, refer to Section 5.2.1 on page 55.
  • Page 208 Mediant 1000 Reader's Notes H.323 User's Manual Document #: LTRT-83401...

  • Page 209: Ini File Configuration Of The Mediant 1000

    Therefore an encoded ini file significantly reduces these threats. You can choose to load an encoded ini file to the Mediant 1000. When you load an encoded ini file, the retrieved ini file is also encoded. Use the ‘TrunkPack Downloadable Conversion Utility’...

  • Page 210: The Ini File Content

    Mediant 1000 The ini File Content The ini file contains the following gateway information: Networking parameters (refer to Section 6.5.1 on page 212) System parameters (refer to Section 6.5.2 on page 217) Web and Telnet parameters (refer to Section 6.5.3...

  • Page 211: The Ini File Example

    H.323 User's Manual 6. ini File Configuration of the Mediant 1000 6.4.2 The ini File Example Figure 6-2 shows an example of an ini file for the VoIP gateway. Figure 6-2: H.323 ini File Example PCMLawSelect = 1 ProtocolType = 1...

  • Page 212: The Ini File Parameter Reference

    Mediant 1000 The ini File Parameter Reference The table below lists all the ini file parameters. References to their descriptions in the Web interface are provided, except for those ini file parameters that don't have corresponding Web interface parameters. 6.5.1...
  • Page 213 H.323 User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-1: Networking Parameters (continues on pages 212 to 217) ini File Field Name Valid Range and Description Web Parameter Name 0 = Disable IP address translation. EnableIPAddrTranslation 1 = Enable IP address translation for RTP, RTCP and T.38 packets (default).
  • Page 214 Mediant 1000 Table 6-1: Networking Parameters (continues on pages 212 to 217) ini File Field Name Valid Range and Description Web Parameter Name For a description of this parameter, refer to Table 5-29 on page 146. BaseUDPport For a description of this parameter, refer to Table 5-29 on page 146.
  • Page 215 H.323 User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-1: Networking Parameters (continues on pages 212 to 217) ini File Field Name Valid Range and Description Web Parameter Name This parameter applies to both Multiple IPs and VLAN mechanisms.
  • Page 216 Mediant 1000 Table 6-1: Networking Parameters (continues on pages 212 to 217) ini File Field Name Valid Range and Description Web Parameter Name User Name for PAP or Host Name for CHAP authentication. PPPoEUserName The valid range is a string of up to 47 characters. The default value is 0.

  • Page 217: System Parameters

    1= Enable (enables ground start) Note 1: For ground start signaling, ensure that the FXO G module is installed (and not the regular FXO module) in the Mediant 1000. Note 2: For ground start FXO, the following parameters should be configured: EnableCurrentDisconnect = 1;...
  • Page 218 Mediant 1000 Table 6-2: System Parameters (continues on pages 217 to 221) ini File Field Name Valid Range and Description Web Parameter Name The Activity Log mechanism enables the gateway to send log messages (to a ActivityListToLog Syslog server) that report certain types of web actions according to a pre- defined filter.
  • Page 219 H.323 User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-2: System Parameters (continues on pages 217 to 221) ini File Field Name Valid Range and Description Web Parameter Name For a description of this parameter, refer to Table 5-4 on page 70.
  • Page 220 Mediant 1000 Table 6-2: System Parameters (continues on pages 217 to 221) ini File Field Name Valid Range and Description Web Parameter Name Specifies the name of the FXO coefficients file and the location of the server (IP FXOCoeffFileURL address or FQDN) from which it is loaded.
  • Page 221 H.323 User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-2: System Parameters (continues on pages 217 to 221) ini File Field Name Valid Range and Description Web Parameter Name The interval between the device’s startup and the first BootP/DHCP request that BootPDelay is issued by the device.

  • Page 222: Web And Telnet Parameters

    The string can be up to 15 characters. Width (in pixels) of the logo image. LogoWidth Note: The optimal setting depends on the resolution settings. The default value is 441, which is the width of AudioCodes’ displayed logo. H.323 User's Manual Document #: LTRT-83401...

  • Page 223: Security

    Name of the image file containing the user’s logo. LogoFileName File name can be up to 47 characters. The logo file name can be used to replace AudioCodes’ default Web logo with a user defined logo. Use a gif, jpeg or jpg image file.

  • Page 224: Radius Parameters

    Mediant 1000 Table 6-4: Security Parameters (continues on pages 223 to 224) ini File Field Name Valid Range and Description Web Parameter Name AccessList_Start_Port For a description of this parameter, refer to Table 5-34 on page 166. AccessList_End_Port For a description of this parameter, refer to Table 5-34 on page 166.

  • Page 225: Snmp Parameters

    H.323 User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-5: RADIUS Parameter (continues on pages 224 to 225) ini File Field Name Valid Range and Description Web Parameter Name For a description of this parameter, refer to Table 5-35 on page 168.

  • Page 226: Configuration Parameters

    Mediant 1000 Table 6-6: SNMP Parameters (continues on pages 225 to 226) ini File Field Name Valid Range and Description Web Parameter Name For a description of this parameter, refer to Table 5-39 on page 175. SNMPUsers_AuthKey For a description of this parameter, refer to Table 5-39 on page 175.
  • Page 227 H.323 User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-7: H.323 Configuration Parameters (continues on pages 226 to 232) ini File Field Name Valid Range and Description Web Parameter Name Defines the gateway’s coder list (up to five coders can be configured).
  • Page 228 Mediant 1000 Table 6-7: H.323 Configuration Parameters (continues on pages 226 to 232) ini File Field Name Valid Range and Description Web Parameter Name Note 1: The coder name is case-sensitive. Note 2: If silence suppression is not defined (for a specific coder), the value defined by the parameter EnableSilenceCompression is used.
  • Page 229 Setup message from the ISDN with TransferCapabilities = data, it can initiate a Fast Start call using ‘Transparent’ coder (even if the coder is not included in the coders list). This option is an AudioCodes’ proprietary feature that requires the use of Fast Start mode and the inclusion of the ‘Transparent’...
  • Page 230 Mediant 1000 Table 6-7: H.323 Configuration Parameters (continues on pages 226 to 232) ini File Field Name Valid Range and Description Web Parameter Name For a description of this parameter, refer to Table 5-8 on page 86. EnableHold For a description of this parameter, refer to Table 5-8 on page 86.
  • Page 231 H.323 User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-7: H.323 Configuration Parameters (continues on pages 226 to 232) ini File Field Name Valid Range and Description Web Parameter Name EnableDigitDelivery2IP For a description of this parameter, refer to Table 5-7 on page 80.
  • Page 232 Mediant 1000 Table 6-7: H.323 Configuration Parameters (continues on pages 226 to 232) ini File Field Name Valid Range and Description Web Parameter Name TelProfile_<Profile ID> = TelProfile_ID [Tel Profile Settings] <Profile Name>,<Preference>,<Coder Group ID>,<IsFaxUsed *>,<DJBufMinDelay *>, <DJBufOptFactor *>,<IPDiffServ *>,<ControlIPDiffServ*>,<DTMFVolume>,<InputGain>, <VoiceVolume>,<N/A use $$ instead>,<N/A use $$ instead>, <EnableDigitDelivery>, <ECE>, <N/A...

  • Page 233: Isdn And Cas Interworking-Related Parameters

    H.323 User's Manual 6. ini File Configuration of the Mediant 1000 6.5.8 ISDN and CAS Interworking-Related Parameters Table 6-8: ISDN and CAS Interworking-Related Parameters (continues on pages 233 to 236) ini File Field Name Valid Range and Description Web Parameter Name...
  • Page 234 Mediant 1000 Table 6-8: ISDN and CAS Interworking-Related Parameters (continues on pages 233 to 236) ini File Field Name Valid Range and Description Web Parameter Name Defines a single default ISDN Release Cause that is used (in ISDN to IP calls) DefaultCauseMapISDN2I instead of all received release causes except when the following Q.931 cause...
  • Page 235 This parameter overrides the internal PSTN T301 timeout on the Users Side (TE side). If an outgoing call from the Mediant 1000 to ISDN is not answered during this timeout, the call is released. The valid range is 10 to 240. The default value is 50.

  • Page 236: Analog Telephony Parameters

    Mediant 1000 Table 6-8: ISDN and CAS Interworking-Related Parameters (continues on pages 233 to 236) ini File Field Name Valid Range and Description Web Parameter Name Enables or disables activation of the Pattern Detector (PD). EnablePatternDetector Valid options include: 0 = Disable (default).
  • Page 237 H.323 User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-9: Analog Telephony Parameters (continues on pages 236 to 239) ini File Field Name Valid Range and Description Web Parameter Name CallerDisplayInfo<Port> = <Caller ID string>,<Restriction> [Module n] Port = 0 to 3.
  • Page 238 Mediant 1000 Table 6-9: Analog Telephony Parameters (continues on pages 236 to 239) ini File Field Name Valid Range and Description Web Parameter Name For a description of this parameter, refer to Table 5-8 on page 86. MWIDisplay For a description of this parameter, refer to Table 5-8 on page 86.
  • Page 239 H.323 User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-9: Analog Telephony Parameters (continues on pages 236 to 239) ini File Field Name Valid Range and Description Web Parameter Name Defines the voltage change slope during polarity reversal or wink.

  • Page 240: Number Manipulation And Routing Parameters

    Mediant 1000 6.5.10 Number Manipulation and Routing Parameters Table 6-10: Number Manipulation and Routing Parameters (continues on pages 240 to 246) ini File Field Name Valid Range and Description Web Parameter Name For digital interfaces: TrunkGroup_x Defines the Trunk Group table.
  • Page 241 H.323 User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-10: Number Manipulation and Routing Parameters (continues on pages 240 to 246) ini File Field Name Valid Range and Description Web Parameter Name For a description of this parameter, refer to Table 5-13 on page 97.
  • Page 242 Mediant 1000 Table 6-10: Number Manipulation and Routing Parameters (continues on pages 240 to 246) ini File Field Name Valid Range and Description Web Parameter Name PSTNPrefix = a,b,c,d,e PSTNPrefix a = Destination Number Prefix b = Trunk group ID (1 to 99)
  • Page 243 H.323 User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-10: Number Manipulation and Routing Parameters (continues on pages 240 to 246) ini File Field Name Valid Range and Description Web Parameter Name Manipulates the destination number for Tel to IP calls (Destination Phone NumberMapTel2IP Number Manipulation Table for Tel IP calls).
  • Page 244 Mediant 1000 Table 6-10: Number Manipulation and Routing Parameters (continues on pages 240 to 246) ini File Field Name Valid Range and Description Web Parameter Name Configures the Source Phone Number Manipulation Table for Tel IP calls. SourceNumberMapTel2IP SourceNumberMapTel2IP = a,b,c,d,e,f,g,h...
  • Page 245 Note 1: This parameter can appear up to 5 times. Note 2: If the Mediant 1000 fails to establish a cal to the PSTN because it has no available channels in a specific trunk group (e.g., all of the trunk group’s channels are occupied, or the trunk group’s spans are disconnected or out of...

  • Page 246: E1/T1 Configuration Parameters

    Mediant 1000 Table 6-10: Number Manipulation and Routing Parameters (continues on pages 240 to 246) ini File Field Name Valid Range and Description Web Parameter Name Defines the method in which the Redirect Number is passed towards the Tel EnableETSIDiversion side.
  • Page 247 H.323 User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-11: E1/T1/J1 Configuration Parameters (continues on pages 246 to 248) ini File Field Name Valid Range and Description Web Parameter Name For a description of this parameter, refer to Table 5-32 on page 152.

  • Page 248: Channel Parameters

    Mediant 1000 Table 6-11: E1/T1/J1 Configuration Parameters (continues on pages 246 to 248) ini File Field Name Valid Range and Description Web Parameter Name Same as the description for parameter ISDNIBehavior, but for a specific trunk ISDNIBehavior_x Same as the description for parameter ISDNInCallsBehavior, for a specific trunk...
  • Page 249 H.323 User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-12: Channel Parameters (continues on pages 248 to 250) ini File Field Name Valid Range and Description Web Parameter Name Cisco compatible fax and modem bypass mode NSEMode...
  • Page 250 Mediant 1000 Table 6-12: Channel Parameters (continues on pages 248 to 250) ini File Field Name Valid Range and Description Web Parameter Name EnableStandardSIDPayloadType For a description of this parameter, refer to Table 5-29 on page 146. Determines the number of spectral coefficients added to an SID packet RTPSIDCoeffNum being sent according to RFC 3389.

  • Page 251: Configuration Files Parameters

    6. ini File Configuration of the Mediant 1000 6.5.13 Configuration Files Parameters The configuration files (Call Progress Tones, Prerecorded Tones, User Information, FXS/FXO Coefficient, and CAS) can be loaded to the Mediant 1000 using the Embedded Web Server or a TFTP session (refer to Section 5.8.2 on page 189).
  • Page 252 Mediant 1000 Reader's Notes H.323 User's Manual Document #: LTRT-83401...

  • Page 253: Using Bootp / Dhcp

    IP addresses of the primary and secondary DNS servers. These parameters are available only in DHCP and from Boot version 1.92. Syslog server IP address - An optional parameter that is sent to the Mediant 1000 only if configured. This parameter is available only in DHCP.

  • Page 254: Using Dhcp

    When DHCP is enabled, the gateway also includes its product name (e.g., ‘Mediant 1000') in the DHCP ‘option 60’ Vendor Class Identifier. The DHCP server can use this product name to assign an IP address accordingly.

  • Page 255: Using Bootp

    390. 7.3.2 Vendor Specific Information Field The Mediant 1000 uses the vendor specific information field in the BootP request to provide device-related initial startup information. The BootP/TFTP configuration utility displays this information in the ‘Client Info’ column (refer to Figure C-1).

  • Page 256: Table 7-1: Vendor Specific Information Field

    Table 7-1: Vendor Specific Information Field Description Value Length Tag # Gateway Type #09 = Mediant 1000 Current IP Address XXX.XXX.XXX.XXX Burned Boot Software Version X.XX Burned cmp Software Version XXXXXXXXXXXX Geographical Address 0 –...

  • Page 257: Telephony Capabilities

    H.323 User's Manual 8. Telephony Capabilities Telephony Capabilities Working with Supplementary Services The Mediant 1000 gateway supports the following supplementary services: Call Hold and Retrieve; refer to Section 8.1.1 on page Consultation / Alternate; refer to Section 8.1.2 on page Call Transfer (H.450.2);...

  • Page 258: Call Transfer

    603 Decline SIP response is sent. Three forms of forwarding parties are available: Served party: the party that is configured to forward the call – Mediant 1000/FXS. Originating party: the party that initiated the first call – Mediant 1000/FXS or FXO.

  • Page 259: Call Waiting

    ETSIVMWITypeOneStandard BellcoreVMWITypeOneStandard 8.1.7 Name Identification The H.450.8 service enables Mediant 1000 gateways to send and receive the calling party name and its presentation (allowed or restricted). To configure name identification set the EnableNameIdentification ini file parameter. Version 5.0 December 2006...

  • Page 260: Configuring The Dtmf Transport Types

    Mediant 1000 Configuring the DTMF Transport Types The Mediant 1000 gateway supports several methods of conveying DTMF digits over the IP network. Three methods are controlled by H.245 protocol and therefore use its capability exchange mechanism to ensure coordination with the remote side. A fourth method uses Q.931 Info messages.

  • Page 261: Fax And Modem Transport Modes

    8.2.1 Overview of In-Band DTMF Transport Types The Mediant 1000 gateway controls the way DTMF digits are transferred in-band (as part of the audio stream) using the DTMFTransport configuration parameter. Note that this parameter is automatically updated in the first four methods described in the previous section and therefore shouldn’t be changed, while, for the fifth method (in-band...

  • Page 262: Configuring Fax/Modem Bypass Mode

    Mediant 1000 8.3.3 Configuring Fax/Modem Bypass Mode When VxxTransportType= 2 (FaxModemBypass, Vxx can be one of the following: V32/V22/Bell/V34/Fax), then on detection of fax/modem, the channel automatically switches from the current voice coder to a high bit-rate coder (G.711 or G.726), as defined by the user, with the FaxModemBypassCoderType configuration parameter.

  • Page 263: Redundant Gatekeeper Implementation

    Gatekeeper. The Mediant 1000 gateway can fallback to the internal ‘Tel to IP Routing’ table when communication with Gatekeepers is lost. If this option is enabled (IsFallbackUsed=1), the Mediant 1000 starts using its internal routing table, and works without a Gatekeeper.

  • Page 264: Mediant 1000 Registration With A Gatekeeper

    Mediant 1000 Mediant 1000 Registration with a Gatekeeper The Mediant 1000 supports three different methods of registration with a Gatekeeper: 8.5.1 Registration with Prefixes The gateway registers with a Gatekeeper using prefixes (range of numbers). To register with prefixes, take these 2 steps: Configure the Registration Prefixes Table (refer to Section 5.5.6...

  • Page 265: Throughpacket

    H.323 User's Manual 8. Telephony Capabilities 8.5.3 Registration with Endpoints The gateway registers with the Gatekeeper using the numbers defined in the ‘Trunk Group Table' screen (normally used with FXS modules). To register with endpoints, take these 2 steps: Don’t configure the Registration Prefixes Table. Set the GWRegistrType parameter according to your requirements: •...

  • Page 266: Dynamic Jitter Buffer Operation

    The jitter buffer collects voice packets, stores them and sends them to the voice processor in evenly spaced intervals. The Mediant 1000 uses a dynamic jitter buffer that can be configured using two parameters: Minimum delay, ‘DJBufMinDelay’ (0 msec to 150 msec): Defines the starting jitter capacity of the buffer.

  • Page 267: Configuring The Gateway's Alternative Routing (Based On Connectivity And Qos)267

    If no call statistics are received for two minutes, the QoS information is reset. The Mediant 1000 gateway matches the rules starting at the top of the table. For this reason, enter the main IP route above any alternative route.

  • Page 268: Relevant Parameters

    IPConnQoSMaxAllowedDelay Call Termination on Mediant 1000 FXO The following six methods for call termination are supported by the Mediant 1000/FXO. Note that the used disconnection methods must be supported by the CO or PBX. Detection of polarity reversal / current disconnect: This is the recommended method.

  • Page 269: Mapping Pstn Release Cause To H.323 Response

    ‘DisconnectOnBusyTone = 0’ the FXO module ignores the detection of Busy/Reorder tones and doesn’t release the call. For all other Mediant 1000 FXO release types (caused when there are no free channels in the specific hunt group, or when an appropriate rule for routing the call to a hunt group doesn’t exist), the Mediant 1000 sends H.323 response (to IP) according to the parameter...

  • Page 270: Table 8-1: Supported Cdr Fields

    Mediant 1000 Table 8-1: Supported CDR Fields Field Name Description Port Number CallId H.323/SIP Call Identifier Trunk Physical Trunk Number (digital only) BChan Selected B-Channel (digital only) ConId H.323/SIP Conference ID Trunk Group Number EPTyp Endpoint Type Orig Call Originator (IP, Tel)

  • Page 271: Supported Radius Attributes

    8.12 Supported RADIUS Attributes Table 8-2 below for explanations on the RADIUS attributes contained in the communication packets transmitted between the Mediant 1000 and a RADIUS Server. Table 8-2: Supported RADIUS Attributes (continues on pages 271 to 272) Attribute Attribute...

  • Page 272: Radius Server Messages

    Numeric Stop Acc Packets during the call Acct-Output- Number of packets sent Numeric Stop Acc Packets during the call Mediant 1000 physical port NAS-Port- Start Acc type on which the call is String Asynchrono Type Stop Acc active Response Attributes...

  • Page 273: Configuration Examples

    Configuration Examples 8.13.1 Trunk-to-Trunk Routing Example This example describes two Mediant 1000 gateways, each interfacing with the PSTN through four E1 spans. Gateway ‘A’ is configured to route all incoming Tel IP calls to gateway ‘B’. Gateway ‘B’ generates calls to PSTN on the same E1 Trunk as the call was originally received (in gateway ‘A’).

  • Page 274: Establishing A Call Between Two Gateways

    10 to the first gateway and calls that start with 20 to the second gateway. Make a call. Pick up the phone connected to port #1 of the first Mediant 1000 and dial 102 (to the phone connected to port #2 of the same gateway). Listen for progress tones at the calling endpoint and for ringing tone at the called endpoint.

  • Page 275: Using Two Gateways With Gatekeeper

    8.13.5 Remote IP Extension between FXO and FXS This application explains how to implement remote extension via IP, using 4-port FXO and 4-port FXS Mediant 1000 gateways. In this configuration, PBX incoming calls are routed to the ‘Remote Extension’ via the FXO and FXS modules.

  • Page 276: Dialing From Remote Extension (Phone Connected To Fxs)

    Mediant 1000 seizes the PBX line and the voice path is established between the phone and the PBX line. There is a one to one mapping between PBX lines and FXS Mediant 1000 ports. Each PBX line is routed to the same phone (connected to FXS Mediant 1000).

  • Page 277: Fxo Mediant 1000 Configuration (Using The Embedded Web Server)

    In the ‘Tel to IP Routing’ screen, enter 20 in the ‘Destination Phone Prefix’ field, and the IP address of the FXO Mediant 1000 gateway (10.1.10.2) in the field ‘IP Address’. In remote extensions, for the transfer to function, hold must be disabled on Note: the FXS (i.e., Enable Hold = 0).
  • Page 278 Mediant 1000 Reader's Notes H.323 User's Manual Document #: LTRT-83401...

  • Page 279: Networking Capabilities

    H.323 User's Manual 9. Networking Capabilities Networking Capabilities Ethernet Interface Configuration Using the parameter ‘EthernetPhyConfiguration‘, users can control the Ethernet connection mode. Either the manual modes (10 Base-T Half-Duplex, 10 Base-T Full-Duplex, 100 Base-TX Half-Duplex, 100 Base-TX Full-Duplex) or Auto-Negotiate mode can be used. Auto-Negotiation falls back to Half-Duplex mode when the opposite port is not Auto- Negotiate, but the speed (10 Base-T, 100 Base-TX) in this mode is always configured correctly.

  • Page 280: Nat (Network Address Translation) Support

    Mediant 1000 After start-up has completed and the operational software is running, the gateway continues to use the Ethernet port used for program load. The gateway switches over from one Ethernet port to the other every time an Ethernet link carrier loss is detected on the active Ethernet port and if the Ethernet link of the other port is operational.

  • Page 281: First Incoming Packet Mechanism

    9.3.1 First Incoming Packet Mechanism If the remote gateway resides behind a NAT device, it’s possible that the Mediant 1000 can activate the RTP/RTCP/T.38 streams to an invalid IP address / UDP port. To avoid such cases, the Mediant 1000 automatically compares the source address of the incoming RTP/RTCP/T.38 stream with the IP address and UDP port of the remote gateway.

  • Page 282: Point-To-Point Protocol Over Ethernet (Pppoe)

    Mediant 1000 Point-to-Point Protocol over Ethernet (PPPoE) PPPoE is a method of sending the Point-to-Point Protocol over Ethernet network. 9.4.1 Point-to-Point Protocol (PPP) Overview Point-to-Point Protocol (PPP) provides a method of transmitting data over serial point-to- point links. The protocol defines establishing, configuring and testing the data link connection and the network protocol.

  • Page 283: Pppoe Overview

    (http://www.ietf.org/rfc/rfc2516.txt). 9.4.3 PPPoE in AudioCodes Gateways The AudioCodes gateway contains a PPPoE client embedded in its software. When correctly configured (see ini file parameters) the gateway can try to connect to a remote PPPoE Access Concentrator. When restarting the gateway after several BOOTP attempts, if PPPoE is enabled (see ini file parameter EnablePPPoE), the gateway tries to initiate a PPP session.

  • Page 284: Ip Multicasting

    Mediant 1000 When working in a PPPoE environment, the gateway negotiates for its IP address (as described above). However, if the user desires to disable the PPPoE client, the gateway can be configured to use default values for IP address, subnet mask and default gateway.

  • Page 285: Simple Network Time Protocol Support

    By prioritizing packets, DiffServ routers can minimize transmission delays for time- sensitive packets such as VoIP packets. The Mediant 1000 can be configured to set a different DiffServ value to IP packets according to their class-of-service (Network, Premium Media, Premium Control, Gold and Bronze).

  • Page 286: Vlans And Multiple Ips

    The IP address and subnet mask used in the Single IP Network mode are carried over to the OAM traffic type in the Multiple IP Network mode. For detailed information on integrating the Mediant 1000 into a VLAN and multiple IPs network, refer to Section 9.10.3 on page 288.

  • Page 287: Table 9-1: Traffic / Network Types And Priority

    H.323 User's Manual 9. Networking Capabilities For the mapping of an application to its class-of-service and traffic type, refer to Table 9-1 on page 287. Media traffic type is assigned ‘Premium media’ class of service, Management traffic type is assigned ‘Bronze’ class of service, and Control traffic type is assigned ‘Premium control’ class of service.

  • Page 288: Operation

    9.10.3 Getting Started with VLANS and Multiple IPs By default the Mediant 1000 operates without VLANs and multiple IPs, using a single IP address, subnet mask and default gateway IP address. This section provides an example of the configuration required to integrate the Mediant 1000 into a VLAN and multiple IPs network using the Embedded Web Server (refer to Section 9.10.3.1) and ini file (refer to...

  • Page 289: Integrating Using The Embedded Web Server

    Use the Software Upgrade Wizard (Section 5.8.1 on page 184) to load and burn the firmware version to the Mediant 1000 (VLANs and multiple IPs support is available only when the firmware is burned to flash). Configure the VLAN parameters by completing the following steps: •...

  • Page 290: Figure 9-3: Example Of The Ip Settings Screen

    Mediant 1000 Figure 9-3: Example of the IP Settings Screen • Click the Submit button to save your changes. Configure the IP Routing table by completing the following steps (the IP Routing table is required to define static routing rules for the OAM and Control networks since a default gateway isn’t supported for these networks):...

  • Page 291: Integrating Using The Ini File

    382) to load and burn (-fb option) the firmware version and the ini file you prepared in the previous step to the Mediant 1000 (VLANs and multiple IPs support is available only when the firmware is burned to flash).
  • Page 292 Mediant 1000 Reader's Notes H.323 User's Manual Document #: LTRT-83401...

  • Page 293: Advanced Pstn Configuration

    (or several at a time). As opposed to en-bloc dialing in which a complete number is sent. The Mediant 1000 can optionally support ISDN overlap dialing for incoming ISDN calls for the entire gateway by setting ‘ISDNRxOverlap’ to 1, or per E1/T1 span by setting ‘ISDNRxOverlap_x’...

  • Page 294: Using Isdn Nfas

    NFAS trunk. ‘x’ stands for the physical trunkID (0 to 3). For example, to assign the first four Mediant 1000 T1 trunks to NFAS group #1, in which trunk #0 is the primary trunk and trunk #1 is the backup trunk, use the following...

  • Page 295: Nfas Interface Id

    The default value of the Interface ID is identical to the number of the physical T1 trunk (0 for the first Mediant 1000 trunk, 1 for the second Mediant 1000 T1 trunk, and so on). To define an explicit Interface ID for a T1 trunk (that is different from the default), use the...

  • Page 296: Redirect Number And Calling Name (Display)

    ;B-Channel NFAS trunk DchConfig_3 = 2 ;B-channel NFAS trunk 10.4 Redirect Number and Calling Name (Display) The following tables define the Mediant 1000 redirect number and calling name (Display) support for various PRI variants: Table 10-1: Calling Name (Display) DMS-100 NI-2...

  • Page 297: Advanced System Capabilities

    Advanced System Capabilities 11.1 Restoring Networking Parameters to their Initial State You can use the ‘Reset’ button to restore the Mediant 1000 networking parameters to their factory default values (described in Table 4-1) and to reset the username and password.

  • Page 298: Automatic Update Mechanism

    11.3 Automatic Update Mechanism The Mediant 1000 is capable of automatically updating its cmp, ini and configuration files. These files can be stored on any standard Web, FTP or NFS server/s and can be loaded periodically to the gateway via HTTP, HTTPS, FTP or NFS. This mechanism can be used even for Customer Premises Equipment (CPE) devices that are installed behind NAT and firewalls.

  • Page 299: Figure 11-2: Example Of An Ini File Activating The Automatic Update Mechanism

    To automatically update the cmp file, use the parameter ‘CmpFileURL’ to specify its name and location. As a precaution (to protect the Mediant 1000 from an accidental update), the Automatic Update mechanism doesn’t apply to the cmp file by default.
  • Page 300 ResetNow = 1 You can modify the master_configuration.ini file (or any of the config_<MAC>.ini files) at any time. The Mediant 1000 queries for the latest version every 60 minutes and applies the new settings immediately. For additional security, use HTTPS or FTPS. The Mediant 1000 supports HTTPS (RFC 2818) and FTPS using the AUTH TLS method <draft-murray-auth-ftp-ssl-16>...

  • Page 301: Startup Process

    H.323 User's Manual 11. Advanced System Capabilities 11.4 Startup Process The startup process (illustrated in Figure 11-3 on page 302) begins when the gateway is reset (physically or from the Web / SNMP) and ends when the operational software is running.

  • Page 302: Figure 11-3: Mediant 1000 Startup Process

    Mediant 1000 Figure 11-3: Mediant 1000 Startup Process Reset from the Physical Web Interface Reset or SNMP BootP DHCP x times x times Response Response Update network BootP Response DHCP Response parameters from BootP/DHCP reply BootP/DHCP reply contains firmware file name?

  • Page 303: Using Parameter Tables

    11. Advanced System Capabilities 11.5 Using Parameter Tables The Mediant 1000 uses parameter tables to group related parameters of specific entities and manage them together. These tables, similar to regular parameters, can be configured via the ini file, Embedded Web Server, SNMP, etc.

  • Page 304: Table Permissions

    Mediant 1000 11.5.2 Table Permissions Each column has a 'permission' attribute that is applied to all instances in the column. This permission determines if and when a field can be modified. Several permissions can be applied to each column. The following permissions are available: Read: The value of the field can be read.

  • Page 305: Using The Ini File To Configure Parameter Tables

    H.323 User's Manual 11. Advanced System Capabilities 11.5.5 Using the ini File to Configure Parameter Tables You can use the ini file to add / modify parameter tables. When using tables, Read-Only parameters are not loaded, as they cause an error when trying to reload the loaded file. Therefore, Read-Only parameters mustn’t be included in tables in the ini file.
  • Page 306 Mediant 1000 Refer to the following notes: Indices (in both the Format and the Data lines) must appear in the same order determined by the specific table's documentation. The Index field must never be omitted. The Format line can include a sub-set of the configurable fields in a table. In this case, all other fields are assigned with the pre-defined default values for each configured line.

  • Page 307: Customizing The Mediant 1000 Web Interface

    (refer to Section 11.6.1.2 on page 309). Note that when the main corporation logo is replaced, AudioCodes’ logo on the left bar (refer to Figure 5-2) and in the Software Upgrade Wizard (Section 5.8.1 on page 184) disappear.

  • Page 308: Figure 11-7: Image Download Screen

    Mediant 1000 Figure 11-7: Image Download Screen Click the Browse button in the Send Logo Image File from your computer to the device box. Navigate to the folder that contains the logo image file you want to load. Click the Send File button; the file is sent to the device. When loading is complete, the screen is automatically refreshed and the new logo image is displayed.

  • Page 309: Replacing The Main Corporate Logo With A Text String

    Section 11.6.4 on page 311. To replace AudioCodes’ default logo with a text string via the ini file, add/modify the two ini file parameters in Table 11-4 according to the procedure described in Section on page 209.

  • Page 310: Customizing The Product Name

    11.6.3 Customizing the Product Name The Product Name text string can be modified according to OEMs specific requirements. To replace AudioCodes’ default product name with a text string via the Web Interface, modify the two ini file parameters in Table 11-6...

  • Page 311: Modifying Ini File Parameters Via The Web Adminpage

    To modify ini file parameters via the AdminPage, take these 6 steps: Access the Mediant 1000 Embedded Web Server (refer to Section on page 57). In the URL field, append the suffix ‘AdminPage’ (note that it’s case-sensitive) to the IP address, e.g., http://10.1.229.17/AdminPage.

  • Page 312: Software Upgrade Key

    Mediant 1000 gateways are supplied with a Software Upgrade Key already pre-configured for the gateway. Users can later upgrade their Mediant 1000 features, capabilities and quantity of available resources by specifying what upgrades they require, and purchasing a new key to match their specification.

  • Page 313: Loading The Software Upgrade Key Using The Embedded Web Server

    H.323 User's Manual 11. Advanced System Capabilities 11.7.3 Loading the Software Upgrade Key Using the Embedded Web Server To load a Software Upgrade Key using the Web Server, take these 6 steps: Access the devices Embedded Web Server (refer to Section on page 57).

  • Page 314: Loading The Software Upgrade Key Using Bootp/Tftp

    Mediant 1000 After verifying that the Software Upgrade Key was successfully loaded, reset the device; the new capabilities and resources are active. Figure 11-10: Example of a Software Upgrade Key File Containing Multiple S/N Lines 11.7.4 Loading the Software Upgrade Key using BootP/TFTP...

  • Page 315: Troubleshooting An Unsuccessful Loading Of A Key

    Open the Software Upgrade Key file and check that the S/N line of the specific device whose key you want to update is listed in it. If it isn’t, contact AudioCodes. Verify that you’ve loaded the correct file and that you haven’t loaded the device’s ini file or the CPT ini file by mistake.
  • Page 316 Mediant 1000 Reader's Notes H.323 User's Manual Document #: LTRT-83401...

  • Page 317: Special Applications

    12. Special Applications Special Applications 12.1 Metering Tones Relay The Mediant 1000 FXS and FXO modules can be used to relay standard 12 or 16 kHz metering tones over the IP network as illustrated in Figure 12-1 below. Figure 12-1: Metering Tone Relay Architecture After a call is established between the FXS and FXO modules, the PSTN generates 12 or 16 kHz metering tones towards the FXO module.

  • Page 318: Tdm Tunneling

    12.2 TDM Tunneling The Mediant 1000 TDM Tunneling feature allows you to tunnel groups of digital trunk spans or timeslots (B-channels) over the IP network. TDM Tunneling utilizes the internal routing capabilities of the Mediant 1000 (working without Proxy control) to receive voice...

  • Page 319: Figure 12-2: Ini File Example For Tdm Tunneling (Originating Side)

    ProtocolType_0 = 5 ProtocolType_1 = 5 ProtocolType_2 = 5 ProtocolType_3 = 5 prefix = '*,10.8.24.12' ;(IP address of the Mediant 1000 in the opposite location) ; Channel selection by Phone number ChannelSelectMode = 0 ;Profiles can be used do define different coders per B-channels, such as Transparent ;...
  • Page 320 Mediant 1000 Reader's Notes H.323 User's Manual Document #: LTRT-83401...

  • Page 321: Security

    H.323 User's Manual 13. Security Security This section describes the security mechanisms and protocols implemented on the Mediant 1000. The following list specifies the available security protocols and their objectives: IPSec and IKE protocols are part of the IETF standards for establishing a secured IP connection between two applications.

  • Page 322: Ike

    Mediant 1000 13.1.1 IKE IKE is used to obtain the Security Associations (SA) between peers (the gateway and the application it’s trying to contact). The SA contains the encryption keys and profile used by the IPSec to encrypt the IP stream. The IKE table lists the IKE peers with which the gateway performs the IKE negotiation (up to 20 peers are available).

  • Page 323: Configuring Ipsec And Ike

    H.323 User's Manual 13. Security IPSec Specifications: Transport mode only Encapsulation Security Payload (ESP) only Support for Cipher Block Chaining (CBC) Supported IPSec SA encryption algorithms: DES, 3DES, and AES Hash types for IPSec SA include SHA1 and MD5 13.1.3 Configuring IPSec and IKE To enable IPSec and IKE on the gateway set the ini file parameter ‘EnableIPSec’...

  • Page 324: Table 13-2: Default Ike First Phase Proposals

    Mediant 1000 Table 13-1: IKE Table Configuration Parameters (continues on pages 323 to 324) Parameter Name Description Authentication Method Determines the authentication method for IKE. [IkePolicyAuthenticationMeth The valid authentication method values include: 0 = Pre-shared Key (default) 1 = RSA Signiture...

  • Page 325: Figure 13-2: Example Of An Ike Table

    H.323 User's Manual 13. Security Figure 13-2: Example of an IKE Table [IPSec_IKEDB_Table] Format IKE_DB_INDEX = IKEPolicySharedKey, IKEPolicyProposalEncryption_0, IKEPolicypRoposalAuthentication_0, IKEPolicyProposalDHGroup_0, IKEPolicyProposalEncryption_1, IKEPolicypRoposalAuthentication_1, IKEPolicyProposalDHGroup_1, IKEPolicyLifeInSec, IkePolicyAuthenticationMethod; IPSEC_IKEDB_TABLE 0 = 123456789, 1, 2, 0, 2, 2, 1, 28800, 0; [\IPSEC_IKEDB_TABLE] In the example above, a single IKE peer is configured and a Pre-shared key authentication is selected.

  • Page 326: Ipsec Configuration

    Mediant 1000 Configure the IKE parameters according to Table 13-1 on page 323. Click the button Create; a row is create in the IKE table To save the changes so they are available after a power fail, refer to Section 5.9.2...

  • Page 327: Figure 13-4: Example Of An Spd Table

    H.323 User's Manual 13. Security Table 13-3: SPD Table Configuration Parameters Parameter Name Description First to Fourth Proposal Determines the encryption type used in the quick mode negotiation for up to Encryption Type four proposals. X stands for the proposal number (0 to 3). [IPSecPolicyProposalEncrypt The valid encryption values are: ion_X]...

  • Page 328: Figure 13-5: Ipsec Table Screen

    Mediant 1000 In the SPD example, all packets designated to IP address 10.11.2.21 that originates from the OAM interface (regardless to their destination and source ports) and whose protocol is UDP are encrypted, the SPD also defines an SA lifetime of 900 seconds and two security proposals: DES/SHA1 and 3DES/SHA1.

  • Page 329: Ipsec And Ike Configuration Table's Confidentiality

    H.323 User's Manual 13. Security 13.1.3.3 IPSec and IKE Configuration Table’s Confidentiality Since the pre-shared key parameter of the IKE table must remain undisclosed, measures are taken by the ini file, Embedded Web Server and SNMP agent to maintain this parameter’s confidentiality.

  • Page 330: Ssl/Tls

    Mediant 1000 13.2 SSL/TLS SSL, also known as TLS, is the method used to secure the Mediant 1000 Embedded Web Server and Telnet server. The SSL protocol provides confidentiality, integrity and authenticity between two communicating applications over TCP/IP. Specifications for the SSL/TLS implementation include the following: Supports transports: SSL 2.0, SSL 3.0, TLS 1.0...

  • Page 331: Server Certificate Replacement

    13.2.3 Server Certificate Replacement The Mediant 1000 is supplied with a working SSL configuration consisting of a unique self- signed server certificate. If an organizational Public Key Infrastructure (PKI) is used, you may wish to replace this certificate with one provided by your security administrator.

  • Page 332: Client Certificates

    (e.g., the new certificate expires). • It is possible to use the IP address of the Mediant 1000 (e.g., 10.3.3.1) instead of a qualified DNS name in the Subject Name. This practice is not recommended since the IP address is subject to changes and may not uniquely identify the device.
  • Page 333 HTTPSRequireClientCertificates = 1. Save the configuration (Section 5.9.2 on page 193) and restart the Mediant 1000. When a user connects to the secure Web server: If the user has a client certificate from a CA listed in the Trusted Root Certificate file, the connection is accepted and the user is prompted for the system password.

  • Page 334: Radius Login Authentication

    Mediant 1000 13.3 RADIUS Login Authentication Users can enhance the security and capabilities of logging to the gateway’s Web and Telnet embedded servers by using a Remote Authentication Dial-In User Service (RADIUS) to store numerous usernames, passwords and access level attributes (Web only), allowing multiple user management on a centralized platform.

  • Page 335: Configuring Radius Support

    ID=35. Figure 13-12: Example of a Dictionary File for FreeRADIUS (FreeRADIUS Client Configuration) # AudioCodes VSA dictionary VENDOR AudioCodes 5003 ATTRIBUTE ACL-Auth-Level 35 integer AudioCodes VALUE ACL-Auth-Level ACL-Auth-UserLevel 50 VALUE ACL-Auth-Level ACL-Auth-AdminLevel 100 VALUE ACL-Auth-Level ACL-Auth-SecurityAdminLevel 200 In the RADIUS server, define the list of users authorized to use the gateway, using one of the password authentication methods supported by the server implementation.
  • Page 336 Mediant 1000 Under section ‘RADIUS Authentication Settings’, in the field ‘Device Behavior Upon RADIUS Timeout’, select the gateway’s operation if a response isn’t received from the RADIUS server after the 5 seconds timeout expires: • Deny Access – the gateway denies access to the Web and Telnet embedded servers.

  • Page 337: Internal Firewall

    H.323 User's Manual 13. Security 13.4 Internal Firewall The Mediant 1000 accommodates an internal access list facility, allowing the security administrator to define network traffic filtering rules. The access list provides the following features: Block traffic from known malicious sources...

  • Page 338: Figure 13-15: Advanced Example Of An Access List Definition Via Ini File

    Mediant 1000 Figure 13-15 shows an advanced example of an access list definition via ini file: Figure 13-15: Advanced Example of an Access List Definition via ini File [ ACCESSLIST ] FORMAT AccessList_Index = AccessList_Source_IP, AccessList_Net_Mask, AccessList_Start_Port, AccessList_End_Port, AccessList_Protocol, AccessList_Packet_Size, AccessList_Byte_Rate, AccessList_Byte_Burst, AccessList_Allow_Type;...

  • Page 339: Network Port Usage

    Note: is the starting TCP / UDP transport port for H.225/H.245 messages (used for RAS, H.225 and H.245 protocols). Mediant 1000 gateways use 500 dynamic ports (except for RTP ports) starting from this port. If H323BasePort = 0, or if a value isn’t specified, the default ports are used.

  • Page 340: Recommended Practices

    Mediant 1000. 13.7 Legal Notice By default, the Mediant 1000 supports export-grade (40-bit and 56-bit) encryption due to US government restrictions on the export of security technologies. To enable 128-bit and 256-bit encryption on your device, contact your AudioCodes representative.

  • Page 341: Diagnostics

    Mediant 1000 is completed and if the parameter EnableDiagnostics is set to 1 or 2. In this mode, the Mediant 1000 tests its DSPs, RAM and flash memory. When EnableDiagnostics is set to 1, flash is tested thoroughly, when EnableDiagnostics is set to 2, flash is only partially tested.

  • Page 342: Mediant 1000 Line Testing

    14.2 Mediant 1000 Line Testing The Mediant 1000 features a mechanism that performs tests on the telephone lines connected to FXS and FXO ports. These tests provide various line measurements. Line testing is executed via SNMP only (using the acAnalogFxoLineTestTable SNMP table for FXO and the acAnalogFxsLineTestTable SNMP table for FXS).

  • Page 343: Syslog Servers

    IP sender address, time, date, etc. 14.3.2 Operation The Syslog client, embedded in the Mediant 1000, sends error reports/events generated by the Mediant 1000 unit application to a Syslog server, using IP/UDP protocol. To activate the Syslog client on the Mediant 1000, take these 5 steps: Set the parameter ‘EnableSyslog’...
  • Page 344 Mediant 1000 Reader's Notes H.323 User's Manual Document #: LTRT-83401...

  • Page 345: Snmp-Based Management

    MIB variables and their use. The device contains an embedded SNMP Agent supporting both general network MIBs (such as the IP MIB), VoP-specific MIBs (such as RTP) and AudioCodes' proprietary MIBs (acBoard, acGateway, acAlarm and other MIBs), enabling a deeper probe into the inter- working of the device.

  • Page 346: Snmp Mib Objects

    Mediant 1000 Set Request: The SNMP standard provides a method of effecting an action associated with a device (via the ‘set’ request) to accomplish activities such as disabling interfaces, disconnecting users, clearing registers, etc. This provides a way of configuring and controlling network devices via SNMP.

  • Page 347: Carrier Grade Alarm System

    H.323 User's Manual 15. SNMP-Based Management Typically, when a MIB is compiled into the system, the manager creates new folders or directories that correspond to the objects. These folders or directories can typically be viewed with a MIB Browser, which is a traditional SNMP management tool incorporated into virtually all Network Management Systems.

  • Page 348: Cold Start Trap

    Mediant 1000 15.3 Cold Start Trap Mediant 1000 technology supports a cold start trap to indicate that the device is starting. This allows the manager to synchronize its view of the device's active alarms. Two different traps are sent at start-up: The standard coldStart trap - iso(1).org(3).dod(6).internet(1).

  • Page 349: Total Counters

    15.5 TrunkPack-VoP Series Supported MIBs The Mediant 1000 contains an embedded SNMP Agent supporting the following MIBs: Standard MIB (MIB-2): The various SNMP values in the standard MIB are defined in RFC 1213. The standard MIB includes various objects to measure and monitor IP activity, TCP activity, UDP activity, IP routes, TCP connections, interfaces and general system indicators.
  • Page 350 Mediant 1000 RTCP-XR: This MIB (RFC) implements the following partial support: • The rtcpXrCallQualityTable is fully supported. • In the rtcpXrHistoryTable, support of the RCQ objects is provided only with no more than 3 intervals, 15 minutes long each. •...
  • Page 351 H.323 User's Manual 15. SNMP-Based Management acAlarm: This is AudioCodes' proprietary carrier-grade alarm MIB. It is a simpler implementation of the notificationLogMIB and the IETF suggested alarmMIB (both also supported in all AudioCodes’ devices). The acAlarm MIB has the following groups: •...

  • Page 352: Traps

    Mediant 1000 15.6 Traps All traps are sent from the SNMP port (default 161). This is part of the NAT Note: traversal solution. Full proprietary trap definitions and trap Varbinds are found in the acBoard MIB and acAlarm MIB. Table 15-1 lists the supported proprietary traps.

  • Page 353: Snmp Interface Details

    H.323 User's Manual 15. SNMP-Based Management Table 15-1: Proprietary Traps Description (continues on pages 352 to 353) Trap Description acHTTPDownloadResult Sent at the success or failure of HTTP download. acDChannelStatus Non-alarm trap sent at the establishment, re-establishment, or release of LAPD link with its peer connection. The trap is sent with one of the following textual descriptions: D-channel synchronized D-channel not-synchronized...

  • Page 354: Snmp Community Names

    Mediant 1000 15.7.1 SNMP Community Names By default, the device uses a single, read-only community string of ‘public’ and a single read-write community string of ‘private’. The following community strings can be defined: Up to five read-only community strings Up to five read-write community strings...
  • Page 355 H.323 User's Manual 15. SNMP-Based Management To add a read-write community string (v2admin), take these 2 steps: Add a new row to the snmpCommunityTable with CommunityName v2admin. Add a row to the vacmSecurityToGroupTable for SecurityName v2admin, GroupName ReadWriteGroup and SecurityModel snmpv2c. To delete the read-write community string (v2admin), take these 2 steps: If v2admin is being used as the trap community string, follow the procedure for...

  • Page 356: Snmp V3 Usm Users

    Mediant 1000 15.7.2 SNMP v3 USM Users You can define up to 10 User-based Security Model (USM) users (USM users are referred to as “v3 users”). Each v3 user can be associated with an authentication type (none, MD5, or SHA-1) and a privacy type (none, DES, 3DES, or AES).

  • Page 357: Configuring Snmp V3 Users Via The Ini File

    H.323 User's Manual 15. SNMP-Based Management 15.7.2.1 Configuring SNMP v3 users via the ini File Use the SNMPUsers ini table to add, modify, and delete SNMPv3 users. For a description of the SNMPUsers table ini file parameters, refer to Section 6.5.6 on page 225.
  • Page 358 Mediant 1000 To delete the read-only, noAuthNoPriv SNMPv3 user (v3user), take these 3 steps: If v3 user is associated with a trap destination, follow the procedure for associating a different user to that trap destination. (See below.) Delete the vacmSecurityToGroupTable row for SecurityName v3user, GroupName ReadGroup1, and SecurityModel usm.

  • Page 359: Trusted Managers

    H.323 User's Manual 15. SNMP-Based Management 15.7.3 Trusted Managers By default, the agent accepts ‘get’ and ‘set’ requests from any IP address, as long as the correct community string is used in the request. Security can be enhanced via the use of Trusted Managers.

  • Page 360: Snmp Ports

    Mediant 1000 The following procedure assumes that there is at least one configured read-write community, are currently one or more Trusted Managers, and the TransportTag for columns for all rows in the snmpCommunityTable are currently set to MGR. This procedure must be done from one of the existing Trusted Managers.

  • Page 361: Multiple Snmp Trap Destinations

    Note that several traps may be lost until the resolving is complete. 15.7.5.2 Configuring Trap Managers via the ini File In the Mediant 1000 ini file, the parameters below can be set to enable or disable the sending of SNMP traps. Multiple trap destinations can be supported on the device by setting multiple trap destinations in the ini file.

  • Page 362: Configuring Trap Managers Via Snmp

    Mediant 1000 Figure 15-1: Example of Entries in a Device ini file Regarding SNMP ; SNMP trap destinations ; The board maintains a table of trap destinations containing 5 ;rows. The rows are numbered 0..4. Each block of 4 items below ;apply to a row in the table.
  • Page 363 H.323 User's Manual 15. SNMP-Based Management To add an SNMPv2 trap destination, take this step: Add a row to the snmpTargetAddrTable with these values: • Name=trapN (where N is an unused number between 0 and 4) • TagList=AC_TRAP • Params=v2cparams All changes to the trap destination configuration take effect immediately.

  • Page 364: Snmp Manager Backward Compatibility

    Mediant 1000 15.8 SNMP Manager Backward Compatibility With support for the Multi Manager Trapping feature, the older acSNMPManagerIP MIB object, which is synchronized with the first index in the snmpManagers MIB table is also supported. This is translated in two features: SET/GET to either of the two MIB objects is identical.

  • Page 365: Snmp Administrative State Control

    NAT replace the symmetric one. 15.11 SNMP Administrative State Control 15.11.1 Node Maintenance Node maintenance for the Mediant 1000 is provided by an SNMP interface. The acBoardMIB provides two parameters for graceful and forced shutdowns of the Mediant 1000: acgwAdminState...

  • Page 366: Audiocodes' Element Management System

    (multiple media gateways in globally distributed enterprise offices, for example), that need to be managed by central personnel. The EMS is not included in the device’s supplied package. Contact AudioCodes for detailed information on AudioCodes’ EMS and on AudioCodes’ EVN - Enterprise VoIP Network –...

  • Page 367: Configuration Files

    396. Only the dat file can be loaded to the Mediant 1000 gateway. Note: To load the Call Progress Tones (dat) file to the Mediant 1000, use the Embedded Web Server (refer to Section 5.8.2 on page 189) or the ini file (refer to Section 5.8.2.2...

  • Page 368: Figure 16-1: Call Progress Tone Types

    For example, users can define an additional dial tone by appending the second dial tone’s definition lines to the first tone definition in the ini file. The Mediant 1000 reports dial tone detection if either of the two tones is detected.

  • Page 369: Figure 16-2: Defining A Dial Tone Example

    H.323 User's Manual 16. Configuration Files • Second Signal Off Time [10 msec]: ‘Signal Off’ period (in 10 msec units) for the second cadence on-off cycle. Can be omitted if there isn’t a second cadence. • Third Signal On Time [10 msec]: ‘Signal On’ period (in 10 msec units) for the third cadence ON-OFF cycle.

  • Page 370: Format Of The Distinctive Ringing Section In The Ini File

    Mediant 1000 16.1.2 Format of the Distinctive Ringing Section in the ini File Distinctive Ringing is only applicable to Mediant 1000/FXS modules. Using the distinctive ringing section of this configuration file, the user can create up to 16 distinctive ringing patterns.

  • Page 371: Examples Of Various Ringing Signals

    H.323 User's Manual 16. Configuration Files 16.1.2.1 Examples of Various Ringing Signals Figure 16-4: Examples of Various Ringing Signals #Regular North American Ringing Pattern: 20 Hz, 2 sec On, 4 sec Off [NUMBER OF DISTINCTIVE RINGING PATTERNS] Number of Ringing Patterns=1 [Ringing Pattern #0] Ring Type=0 Freq [Hz]=20...

  • Page 372: Prt File Format

    Mediant 1000 16.2.1 PRT File Format The PRT dat file contains a set of prerecorded tones to be played by the Mediant 1000 during operation. Up to 40 tones (totaling approximately one minute) can be stored in a single file in flash memory. The prerecorded tones (raw data PCM or L8 files) are prepared...
  • Page 373 H.323 User's Manual 16. Configuration Files Hybrid balance Frequency response in transmit and receive direction Hook thresholds Ringing generation and detection parameters This means, for example, that changing impedance matching or hybrid balance doesn’t require hardware modifications, so that a single device is able to meet requirements for different markets.
  • Page 374 Mediant 1000 Reader's Notes H.323 User's Manual Document #: LTRT-83401...

  • Page 375: A Selected Technical Specifications

    H.323 User's Manual A. Selected Technical Specifications Selected Technical Specifications Table A-1: Mediant 1000 Functional Specifications (continues on pages 375 to 377) Modularity and Capacity Six slots for analog modules.Up to 24 FXS/FXO analog ports. Up to four digital trunks (fully flexible, from a single and up to four trunks per...
  • Page 376 Mediant 1000 Table A-1: Mediant 1000 Functional Specifications (continues on pages 375 to 377) Voice & Tone Characteristics G.711 PCM at 64 kbps µ-law/A-law (10, 20, 30, 40, 50, 60, 80, 100, 120 msec) G.723.1 MP-MLQ at 5.3 or 6.3 kbps (30, 60, 90 msec) G.726 at 32 kbps ADPCM (10, 20, 30, 40, 50, 60, 80, 100, 120 msec)
  • Page 377 H.323 User's Manual A. Selected Technical Specifications Table A-1: Mediant 1000 Functional Specifications (continues on pages 375 to 377) Two Ethernet RJ-45 connectors, 10/100 Base-TX Network Interface RS-232 terminal interface. Non-standard RS-232 connector on the device’s CPU. RS-232 Interface Resets the device.
  • Page 378 Mediant 1000 Reader's Notes H.323 User's Manual Document #: LTRT-83401...

  • Page 379: B Supplied H.323 Software Kit

    B. Supplied H.323 Software Kit Supplied H.323 Software Kit The table below describes the standard supplied software kit for Mediant 1000. The supplied documentation includes this User’s Manual, the Mediant 1000 Analog & Digital Fast Track Guide and the Mediant 1000 H.323 Release Notes.

  • Page 380: Mediant

    Mediant 1000 Reader’s Notes H.323 User's Manual Document #: LTRT-83401...

  • Page 381: C Bootp/Tftp Configuration Utility

    H.323 User's Manual C. BootP/TFTP Configuration Utility BootP/TFTP Configuration Utility The BootP/TFTP utility enables you to easily configure and provision our boards and media gateways. Similar to third-party BootP/TFTP utilities (which are also supported) but with added functionality; our BootP/TFTP utility can be installed on Windows™ 98 or Windows™...

  • Page 382: Specifications

    Mediant 1000 Unicast BootP response. User-initiated BootP respond, for remote provisioning over WAN. Filtered display of BootP requests. Location of other BootP utilities that contain the same MAC entity. Common log window for both BootP and TFTP sessions. Works with Windows™ 98, Windows™ NT, Windows™ 2000 and Windows™ XP.

  • Page 383: Bootp/Tftp Application User Interface

    H.323 User's Manual C. BootP/TFTP Configuration Utility BootP/TFTP Application User Interface Figure C-1 shows the main application screen for the BootP/TFTP utility. Figure C-1: Main Screen Log Window Function Buttons on the Main Screen Pause: Click this button to pause the BootP Tool so that no replies are sent to BootP requests.

  • Page 384: Log Window

    Mediant 1000 Figure C-2: Reset Screen When a gateway resets, it first sends a BootRequest. Therefore, Reset can be used to force a BootP session with a gateway without needing to power cycle the gateway. As with any BootP session, the computer running the BootP Tool must be located on the same subnet as the controlled VoIP gateway.

  • Page 385: Setting The Preferences

    H.323 User's Manual C. BootP/TFTP Configuration Utility Use right-click on a line in the Log Window to open a pop-up window with the following options: Reset: Selecting this option results in a reset command being sent to the client VoIP gateway.

  • Page 386: Bootp Preferences

    Mediant 1000 C.10.1 BootP Preferences ARP is a common acronym for Address Resolution Protocol, and is the method used by all Internet devices to determine the link layer address, such as the Ethernet MAC address, in order to route Datagrams to devices that are on the same subnet.

  • Page 387: Configuring The Bootp Clients

    H.323 User's Manual C. BootP/TFTP Configuration Utility Timeout: This specifies the number of seconds that the TFTP utility waits before retransmitting TFTP messages. This can be left at the default value of 5 (the more congested your network, the higher the value you should define in these fields). Maximum Retransmissions: This specifies the number of times that the TFTP utility tries to resend messages after timing out.

  • Page 388: Deleting Clients

    Mediant 1000 Click Apply to save this entry to the list of clients, or click Apply & Reset to save this entry to the list of clients and send a reset message to that gateway to immediately implement the settings.

  • Page 389: Testing The Client

    H.323 User's Manual C. BootP/TFTP Configuration Utility C.11.4 Testing the Client There should only be one BootP utility supporting any particular client MAC active on the network at any time. To check if other BootP utilities support this client, take these 4 steps: Select the client that you wish to test by clicking on the client name in the main area of the Client Configuration Window.

  • Page 390: Using Command Line Switches

    Mediant 1000 Boot File: This field specifies the file name for the software (cmp) file that is loaded by the TFTP utility to the VoIP gateway after the VoIP gateway receives the BootReply message. The actual software file is located in the TFTP utility directory that is specified in the BootP Preferences window.

  • Page 391: Table C-1: Command Line Switch Descriptions

    H.323 User's Manual C. BootP/TFTP Configuration Utility Table C-1: Command Line Switch Descriptions Switch Description Burn ram.cmp in flash (only for cmp files) -em # Use this switch to set Ethernet mode. 0 = 10 Base-T half-duplex 1 = 10 Base-T full-duplex 2 = 100 Base-TX half-duplex 3 = 100 Base-TX full-duplex 4 = auto-negotiate (default)

  • Page 392: Managing Client Templates

    Mediant 1000 C.12 Managing Client Templates Templates can be used to simplify configuration of clients when most of the parameters are the same. Figure C-5: Templates Screen To create a new template, take these 4 steps: Click the Add New Template button Fill in the default parameter values in the parameter fields.

  • Page 393: Drtp/Rtcp Payload Types And Port Allocation

    H.323 User's Manual D. RTP/RTCP Payload Types and Port Allocation RTP/RTCP Payload Types and Port Allocation RTP Payload Types are defined in RFC 3550 and RFC 3551. We have added new payload types to enable advanced use of other coder types. These types are reportedly not used by other applications.

  • Page 394: Default Rtp/Rtcp/T.38 Port Allocation

    Mediant 1000 Default RTP/RTCP/T.38 Port Allocation The following table shows the default RTP/RTCP/T.38 port allocation. Channel Number RTP Port RTCP Port T.38 Port 4000 4001 4002 4010 4011 4012 4020 4021 4022 4030 4031 4032 4040 4041 4042 4050 4051...

  • Page 395: E Accessory Programs And Tools

    H.323 User's Manual E. Accessory Programs and Tools Accessory Programs and Tools The accessory applications and tools shipped with the device provide you with friendly interfaces that enhance device usability and smooth your transition to the new VoIP infrastructure. The following applications are available: TrunkPack Downloadable Conversion Utility (refer to Section below).

  • Page 396: Converting A Cpt Ini File To A Binary Dat File

    Mediant 1000 E.1.1 Converting a CPT ini File to a Binary dat File For detailed information on creating a CPT ini file, refer to Section 16.1 on page 367. To convert a CPT ini file to a binary dat file, take these 10 steps: Execute the TrunkPack Downloadable Conversion Utility, DConvert.exe (supplied with...

  • Page 397: Creating A Loadable Cas Protocol Table File

    H.323 User's Manual E. Accessory Programs and Tools E.1.2 Creating a loadable CAS Protocol Table File To create a loadable CAS protocol table file take the next 11 steps: Construct the CAS protocol files (xxx.txt and UserProt_defines_xxx.h). Copy the files generated in the previous step to the same directory the TrunkPack Downloadable Conversion utility is located and ensure that the files CASSetup.h and cpp.exe are also located in the same directory.

  • Page 398: Encoding / Decoding An Ini File

    Mediant 1000 To create a file (for troubleshooting purposes) that contains the name of the States and their actual values: Check the Output state names to file checkbox; the default file name TableStateNames.txt appears in the adjacent field (you can modify the name of the file).

  • Page 399: Creating A Loadable Prerecorded Tones File

    H.323 User's Manual E. Accessory Programs and Tools To decode an encoded ini file, take these 4 steps: Click the Select File… button under the ‘Decode ini File(s)’ section. Navigate to the folder that contains the file you want to decode. Click the file and click the Open button.

  • Page 400: Figure E-5: Prerecorded Tones Screen

    Mediant 1000 Figure E-5: Prerecorded Tones Screen To add the prerecorded tone files (you created in Step 1) to the ‘Prerecorded Tones’ screen follow one of these procedures: • Select the files and drag them to the ‘Prerecorded Tones’ screen.

  • Page 401: Call Progress Tones Wizard

    Call Progress Tones), providing a good starting point when configuring an Mediant 1000/FXO module. This ini file can then be converted to a dat file that can be loaded to the gateway using the TrunkPack Downloadable Conversion utility.

  • Page 402: Initial Settings

    Execute the CPTWizard.exe file; the wizard’s initial settings screen is displayed. Figure E-7: Initial Settings Screen Enter the IP address of the Mediant 1000/FXO module you are using. Select the gateway’s ports that are connected to your PBX, and specify the phone number of each extension.

  • Page 403: Recording Screen - Automatic Mode

    E. Accessory Programs and Tools E.2.4 Recording Screen – Automatic Mode After the connection to the Mediant 1000/FXO module is established, the recording screen is displayed. Figure E-8: Recording Screen –Automatic Mode To start recording in automatic mode, take these 3 steps: Click the Start Automatic Configuration button;...

  • Page 404: Figure E-9: Recording Screen After Automatic Detection

    PBX. During the first run of the CPTWizard, it is likely that the gateway does not detect any tones. • Some tones cannot be detected by the Mediant 1000 gateway hardware (such as 3-frequency tones and complex cadences). CPTWizard is therefore limited to detecting only those tones that can be detected on the Mediant 1000 gateway.

  • Page 405: Recording Screen - Manual Mode

    H.323 User's Manual E. Accessory Programs and Tools E.2.5 Recording Screen – Manual Mode In manual mode you can record and analyze tones, included in the Call Progress Tones ini file, in addition to those tones analyzed when in automatic mode. To start recording in manual mode, take these 6 steps: Click the Manual tab at the top of the recording screen, the manual recording screen is displayed.

  • Page 406: The Call Progress Tones Ini File

    Mediant 1000 E.2.6 The Call Progress Tones ini File After Call Progress Tones detection complete, text file named call_progress_tones.ini is created in the same directory as the directory in which the CPTWizard.exe is located. This file contains: Information about each tone that was recorded and analyzed by the wizard. This information includes frequencies and cadence (on/off) times, and is required for using this file with the TrunkPack Downloadable Conversion utility.

  • Page 407: Adding A Reorder Tone To The Cpt File

    CPT file. To add a Reorder tone to the CPT file, take these 11 steps: Make a call (using G.711) between the Mediant 1000 FXO, which is connected to the PBX, and a remote entity in the IP network.

  • Page 408: Pstn Trace Utility

    Mark the PSTN Trace check box. Click the Run button=> the UDP2File utility starts to collect the trace messages. Activate the Web page by entering <Mediant 1000 IP address>/TrunkTraces, such as: http://10.8.8.101/TrunkTraces. The user and password is the same for the unit.

  • Page 409: Figure E-14: Trunk Traces

    H.323 User's Manual E. Accessory Programs and Tools Determine the UDP port (the same as in step 3). Click the Submit button => the board starts to send the trace messages. In the UDP2File utility (Refer to Figure E-15) you should see the number in the packets counter increasing.
  • Page 410 Mediant 1000 Reader's Notes H.323 User's Manual Document #: LTRT-83401...

  • Page 411: Snmp Traps

    H.323 User's Manual F. SNMP Traps SNMP Traps This section provides information on proprietary SNMP traps currently supported by the gateway. There is a separation between traps that are alarms and traps that are not (logs). Currently all have the same structure made up of the same 11 varbinds (Variable Binding) (1.3.6.1.4.1.5003.9.10.1.21.1).

  • Page 412: Table F-2: Acboardconfigurationerror Alarm Trap

    Mediant 1000 Table F-2: acBoardConfigurationError Alarm Trap acBoardConfigurationError Alarm: 1.3.6.1.4.1.5003.9.10.1.21.2.0.2 OID: Critical Default Severity equipmentAlarm Event Type: underlyingResourceUnavailable (56) Probable Cause: Board Config Error: <text> Alarm Text: Status Changes: A configuration error was detected Condition: Alarm status: critical <text> value: A run-time specific string describing the configuration error.

  • Page 413: Table F-4: Acboardevresettingboard Alarm Trap

    H.323 User's Manual F. SNMP Traps Table F-4: acBoardEvResettingBoard Alarm Trap acBoardEvResettingBoard Alarm: 1.3.6.1.4.1.5003.9.10.1.21.2.0.5 OID: critical Default Severity: equipmentAlarm Event Type: outOfService (71) Probable Cause: User resetting board Alarm Text: Status Changes: When a soft reset is triggered via the Web interface or SNMP. Condition: Alarm status: Critical...

  • Page 414: Table F-7: Acboardcontrollerfailurealarm Alarm Trap

    Mediant 1000 Table F-7: acBoardControllerFailureAlarm Alarm Trap acBoardControllerFailureAlarm Alarm: 1.3.6.1.4.1.5003.9.10.1.21.2.0.9 OID: Minor Default Severity: processingErrorAlarm Event Type: softwareError (46) Probable Cause: Controller failure alarm Alarm Text: Status Changes: Proxy has not been found Condition: Alarm Status: Major Additional Info: Proxy not found. Use internal routing, Proxy lost.

  • Page 415: Table F-9: Acgwadminstatechange Alarm Trap

    H.323 User's Manual F. SNMP Traps Table F-9: acgwAdminStateChange Alarm Trap acgwAdminStateChange Alarm: 1.3.6.1.4.1.5003.9.10.1.21.2.0.7 OID: Major Default Severity processingErrorAlarm Event Type: outOfService (71) Probable Cause: Network element admin state change alarm Gateway is <text> Alarm Text: Status Changes: Admin state changed to shutting down Condition: Alarm status: Major...

  • Page 416: Component: Alarmmanager#0

    Mediant 1000 F.1.2 Component: AlarmManager#0 The source varbind text for all the alarms under this component is Board#<n>/AlarmManager#0 where n is the slot number. Table F-11: acActiveAlarmTableOverflow Alarm Trap acActiveAlarmTableOverflow Alarm: 1.3.6.1.4.15003.9.10.1.21.2.0.12 OID: Major Default Severity: processingErrorAlarm Event Type: resourceAtOrNearingCapacity (43)

  • Page 417: Component: Ethernetlink#0

    H.323 User's Manual F. SNMP Traps source varbind text alarm under this component Chassis#0/PowerSupply#<m>, where m is the power supply’s slot number. Table F-13: acPowerSupplyAlarm Alarm Trap acPowerSupplyAlarm Alarm: 1.3.6.1.4.1.5003.9.10.1.21.2.0.30 OID: Critical Default Severity: equipmentAlarm Event Type: powerProblem Probable Cause: Power-Supply Alarm.

  • Page 418: Log Traps (Notifications)

    Mediant 1000 F.1.5 Log Traps (Notifications) This section details traps that are not alarms. These traps are sent with the severity varbind value of ‘indeterminate’. These traps don’t ‘clear’, they don’t appear in the alarm history or active tables. One log trap that does send clear is acPerformanceMonitoringThresholdCrossing.

  • Page 419: Other Traps

    OID: SNMPv2-MIB MIB: Table F-20: acBoardEvBoardStarted Trap acBoardEvBoardStarted Trap Name: 1.3.6.1.4.1.5003.9.10.1.21.2.0.4 OID: AcBoard MIB: cleared Severity: equipmentAlarm Event Type: Other(0) Probable Cause: Initialization Ended Alarm Text: This is the AudioCodes Enterprise application cold start trap. Note: Version 5.0 December 2006...

  • Page 420: Trap Varbinds

    Mediant 1000 Table F-21: AcDChannelStatus Trap acDChannelStatus Trap Name: 1.3.6.1.4.1.5003.9.10.1.21.2.0.37 OID: AcBoard Minor Severity communicationsAlarm Event Type: communicationsProtocolError Probable Cause: D-Channel Trap. Alarm Text: Trunk <m> where m is the trunk number (starts from 0). Source: Status Changes: D-Channel un-established.

  • Page 421: G Installation And Configuration Of Apache Http Server

    H.323 User's Manual G. Installation and Configuration of Apache HTTP Server Installation and Configuration of Apache HTTP Server This appendix describes the installation and configuration of Apache’s HTTP server with Perl script environment (required for recording). Windows 2000/XP Operation Systems For detailed installation information, refer to Note: http://perl.apache.org/docs/2.0/os/win32/config.html.

  • Page 422: Linux Operation Systems

    Mediant 1000 Open the Apache2/conf/perl.conf file for editing and add the line “Script PUT /perl/put.cgi” after the last line in the following section (note that if the following section is omitted or different in the file, insert it into the file or change it there accordingly): Alias /perl/ "C:/Apache2/perl/...
  • Page 423 H.323 User's Manual G. Installation and Configuration of Apache HTTP Server Set MaxClients to 250 Change the mod_perl module lines to: <IfModule mod_perl.c> Alias /perl/ /var/www/perl/ <Directory /var/www/perl> SetHandler perl-script PerlHandler Apache::Registry Options +ExecCGI PerlSendHeader On </Directory> </IfModule> Script PUT /perl/put.cgi Version 5.0 December 2006...
  • Page 424 Mediant 1000 Reader's Notes H.323 User's Manual Document #: LTRT-83401...

  • Page 425: Hosn Server Hardware Installation

    Phillips screwdriver Flathead screwdriver Wire cutter OSN Server Installation on the Mediant 1000 The Mediant 1000 OSN Server package is composed of three modules, which need to be installed in the Mediant 1000: Connection (CM) module iPMX module Hard Drive (HDMX) module...

  • Page 426: Figure H-2: Ipmx Module

    Mediant 1000 Figure H-2: iPMX Module Figure H-3: Hard Drive Module (HDMX) H.323 User's Manual Document #: LTRT-83401...

  • Page 427: Figure H-4: Mediant 1000 Front Panel View

    H.323 User's Manual H. OSN Server Hardware Installation To install the CM module, take these 5 steps: Place the Mediant 1000, so that the front panel is facing you, as shown in Figure H-4. Using a Phillips screwdriver, remove the black metal cover plate from the slot below...

  • Page 428: Figure H-6: Mediant 1000 Rear Panel View

    Mediant 1000 To install the iPMX module, take these 6 steps: Place the Mediant 1000, so that the rear panel is facing you, as shown in Figure H-6. Figure H-6: Mediant 1000 Rear Panel View Remove the black metal cover plates in the first and second slots located on the right...

  • Page 429: Figure H-8: Mediant 1000 With Cutter Tool

    Use the cutter tool to remove the small metal strip between the upper and lower slots, as shown in Figure H-8. Figure H-8: Mediant 1000 With Cutter Tool Insert the iPMX module in the first slot, closest to the power connection, as shown in Figure H-9.

  • Page 430: Figure H-10: Inserting The Hdmx Module

    Mediant 1000 To install the Hard Drive (HDMX) module, take these 6 steps: Place the Mediant 1000, so that the rear panel is facing you, as shown in Figure H-6 Remove the black metal cover plates in the first and second slots located on the right...

  • Page 431: Linux™ Operating System Installation For The Osn Server

    Redhat Fedora Core 3 is not supported. Physical Mounting Requirements Before installing LinuxTM on the Mediant 1000 OSN Server, ensure you have the following: Ethernet cable cord External USB CD ROM or DVD ROM (not supplied by AudioCodes) USB cable (not supplied by AudioCodes) to connect the external USB CD ROM to the...

  • Page 432: Physical Mounting Requirements

    Mediant 1000 Rear Panel Connection To connect to the rear panel, take these 3 steps: Connect the Ethernet cable to the ACT Link, on the rear side of the Mediant 1000. Connect the external CD-ROM power supply. Connect the Mediant 1000 power supply.

  • Page 433: Downloading An Updated Linuxtm Redhat Iso Image

    6 steps: From http://www.audiocodes.com, navigate to the Support page. Login with your Username and Password. Under Product Documentation, select the Mediant 1000 link and click on Mediant 1000 OSN Server. Select Linux Boot Image and select the installation you need.

  • Page 434: Figure I-3: "Images" Folder

    Mediant 1000 Locate the boot.iso file in the images folder on the CD. Figure I-3: "Images" Folder The “images” folder may be named differently on different Linux™ Note: distributions. Copy the boot.iso file to the Partner Install folder created in Step 1 and open it with an ISO image editor.

  • Page 435: Stage 2: Editing The Isolinux.cfg File

    H.323 User's Manual I. Linux™ Operating System Installation for the OSN Server I.5.2 Stage 2: Editing the isolinux.cfg File To edit the isolinux.cfg file, take these 19 steps: Right-click the isolinux.cfg file, and then from the shortcut menu, choose Extract. Figure I-5: Selecting Extract Option Extract the isolinux.cfg file to the Partner Install folder created in Stage 1.

  • Page 436: Figure I-7: Iso-Extract Screen

    Mediant 1000 Click Extract; a screen opens containing the extracted isolinux folder. Figure I-7: ISO-Extract screen Open the isolinux.cfg file with a text editor that supports UNIX file format (e.g., PSPad, UltraEdit). The following screen appears. Figure I-8: Text Edit screen H.323 User's Manual...
  • Page 437 H.323 User's Manual I. Linux™ Operating System Installation for the OSN Server Insert the following line in the beginning of the file, so that it is the first line. serial 0 115200 Locate the line "default <my_label>". Usually "default linux" appears. Locate the line "label <my_label>".

  • Page 438: Figure I-9: Deleting Cfg

    Mediant 1000 Right-click the isolinux.cfg file, and then from the shortcut menu, choose Delete to delete this file. Figure I-9: Deleting CFG From the ISO edit utility menu, select the Actions option, followed by Add Files. Figure I-10: File Add H.323 User's Manual...

  • Page 439: Stage 3: Burn The Cd

    H.323 User's Manual I. Linux™ Operating System Installation for the OSN Server Navigate to the Partner Install folder, select the isolinux.cfg file, and then click Open. Figure I-11: ISO Open Function The updated isolinux.cfg file has now been copied from the Partner Install folder to the boot.iso image.

  • Page 440: Stage 4: Installation

    Mediant 1000 I.5.4 Stage 4: Installation Now you have the boot media which enables the installation of the Mediant 1000 using the serial connection (terminal) with RS-232 cable. To complete the installation, take these 9 steps: Connect your Windows™ PC via serial cable to the Mediant 1000.

  • Page 441: Additional Redhat™ And Fedora™ Installation Notes (7)

    /usr/bin/redhat-config-securitylevel-tui --quiet –disabled It is recommended that you assign a static IP address to your Mediant 1000. So when the installation has been completed, you will be able to create an SSH remote connection and continue the post-installation configuration.

  • Page 442: Linux™ Debian Installation Instructions

    Mediant 1000 Linux™ Debian Installation Instructions Perform the following five stages for the Linux™ Debian Installation. (Some Debian distributions may vary slightly). I.6.1 Stage 1: Obtaining the ISO Image To obtain an updated ISO image, create it using the steps detailed in the section below.

  • Page 443: Stage 2: Preparing The Boot Media

    H.323 User's Manual I. Linux™ Operating System Installation for the OSN Server The .iso file starts being created. Figure I-15: Creating .iso file I.6.2 Stage 2: Preparing the Boot Media To prepare the Boot Media, take these 5 steps: If you have not already done so, download a utility that allows editing of an ISO image. The WinISO™...

  • Page 444: Stage 3: Editing The Isolinux.cfg File

    Figure I-18: Extracting to Partner Install folder I.6.3 Stage 3: Editing the isolinux.cfg File In order to obtain an updated isolinux.cfg file, either download it from the AudioCodes website as described in Section I.6.3.1, or edit it using the steps detailed in Section I.6.3.2. I.6.3.1 Downloading an updated Debian isolinux.cfg file...

  • Page 445: Editing The Isolinux.cfg File

    H.323 User's Manual I. Linux™ Operating System Installation for the OSN Server I.6.3.2 Editing the isolinux.cfg File To edit the isolinux.cfg file, take these 16 steps: Open the Partner Install folder and select the isolinux.cfg file, with a text editor that supports UNIX file format (e.g., PSPad, UltraEdit).

  • Page 446: Figure I-19: Deleting Cfg

    Mediant 1000 F7 f7.txt F8 f8.txt F9 f9.txt F0 f10.txt If the timeout line does not exist, do not add it.1. If you want to install Note: 'kernel 2.6' rather than the 'default 2.4 version', then: a) Take the options from 'kernel' and 'append' lines under the label called 'LABEL linux26'.

  • Page 447: Stage 4: Burn The Cd

    H.323 User's Manual I. Linux™ Operating System Installation for the OSN Server From the ISO edit utility menu, select the Actions option, followed by Add Files. Figure I-20: File Add Navigate to the Partner Install folder, select the isolinux.cfg file, and then click Open.

  • Page 448: Stage 5: Installation

    Mediant 1000 I.6.5 Stage 5: Installation Now you have the boot media which enables the installation of the Mediant 1000 using the serial connection (terminal) with RS-232 cable. To complete the installation, take these 7 steps: Connect your Windows™ PC via serial cable to the Mediant 1000.
  • Page 449 After the whole installation has been completed, you will be able login to the system from the serial console and/or to “ssh” on your Mediant 1000 (to create an SSH remote connection to it) and to continue its post-installation configuring. You can use the boot media you have created in order to install multiple Mediant 1000 stations.

  • Page 450: Linux™ Suse Installation Instructions

    Mediant 1000 Linux™ SUSE Installation Instructions Perform the following five stages for the Linux SUSE Installation. (Some SUSE distributions may vary slightly). I.7.1 Additional Requirement for Linux™ SUSE Installation In order to install Linux™ SUSE, a terminal emulation program is needed which supports: ANSI colors (or LinuxTM emulation) Changing terminal size (to 132x47).

  • Page 451: Stage 2: Preparing The Boot Media

    H.323 User's Manual I. Linux™ Operating System Installation for the OSN Server Create a Partner Install folder on your hard drive. Select boot.iso as the output filename, and then click Make. Figure I-23: Create ISO from CD-ROM The .iso file begins being created. Figure I-24: Creating .iso file I.7.3 Stage 2: Preparing the Boot Media...

  • Page 452: Stage 3: Editing The Isolinux.cfg File

    Figure I-27: Extracting to Partner Install folder I.7.4 Stage 3: Editing the isolinux.cfg File To obtain an updated isolinux.cfg file, either download it from the AudioCodes Web site as described in Section I.7.4.1, or edit it using the steps detailed in Section I.7.4.2. I.7.4.1 Downloading an updated SUSE isolinux.cfg file...

  • Page 453: Editing The Isolinux.cfg File

    H.323 User's Manual I. Linux™ Operating System Installation for the OSN Server I.7.4.2 Editing the isolinux.cfg File To edit the isolinux.cfg file, take these 19 steps: From the Partner Install folder, open the isolinux.cfg file with a text editor that supports UNIX file format (e.g., PSPad, UltraEdit).
  • Page 454 Mediant 1000 Add the following parameters to the 'append' line: text console=ttyS0,115200. In the above string, 'ttyS0,115200' consists of a capital 'S', only zeros and Note: one comma. The following examples show how the 'label linux' line and its kernel & append...

  • Page 455: Figure I-29: Deleting Cfg

    H.323 User's Manual I. Linux™ Operating System Installation for the OSN Server # rescue label rescue kernel linux append initrd=initrd splash=silent rescue=1 showopts # memory test label memtest kernel memtest implicit 1 gfxboot bootlogo display message prompt timeout readinfo 2 framebuffer notice Save the changes to the isolinux.cfg file.

  • Page 456: Figure I-31: Partner Install Folder

    Mediant 1000 Navigate to the Partner Install folder, select the isolinux.cfg file, and then click Open. Figure I-31: Partner Install Folder The updated isolinux.cfg file is added to the Partner Install folder. Save the boot.iso in the Partner Install folder.

  • Page 457: Stage 4: Burn The Cd

    I.7.6 Stage 5: Installation Now you have the boot media which enables SUSE installation of the Mediant 1000 using serial connection (terminal) with RS232 cable. To complete the installation, take these 8 steps: Connect your Windows™ PC via serial cable to the Mediant 1000.
  • Page 458 After the whole installation has been completed, you will be able login to the system from the serial console and/or to 'ssh' on your Mediant 1000 (to create an SSH remote connection to it) and to continue its post-installation configuring. You can use the boot media you have created to install multiple Mediant 1000 stations.

  • Page 459: J Regulatory Information (Digital Interface)

    Undertegnede [AudioCodes Ltd] erklærer herved, at følgende udstyr [Mediant 1000 Digital Series] overholder de væsentlige krav og øvrige relevante krav i direktiv 1999/5/EF Dutch Hierbij verklaart [AudioCodes Ltd] dat het toestel [Mediant 1000 Digital Series] in overeenstemming is met de essentiële eisen en de andere relevante bepalingen van richtlijn 1999/5/EG English Hereby, [AudioCodes Ltd], declares that this [Mediant 1000 Digital Series] is in compliance with the essential requirements and other relevant provisions of Directive 1999/5/EC.

  • Page 460: Mediant

    ACTA Customer information 1. This equipment, the VoIP Gateway, models Mediant 1000 complies with Part 68 of the FCC Rules and the requirements adopted by the ACTA. On the bottom of the unit of this equipment is a label that contains among other information, a product identifier in the format US:AC1ISNANM1KDIG.
  • Page 461 H.323 User's Manual J. Regulatory Information (Digital Interface) Reader's Notes Version 5.0 December 2006...
  • Page 462 ™ Mediant™ Media Gateways H.323 Mediant 1000 User’s Manual Version 5.0 www.audiocodes.com...

Table of Contents

Save PDF