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

Sip media gateways
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
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
Table of Contents

Advertisement

Quick Links

Download this manual See also: Troubleshooting Manual, User Manual
™ Mediant™ Media Gateways
SIP
Mediant 1000
User's Manual Version 5.0
Document #: LTRT-83301
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 Mediant 1000 User’s Manual Version 5.0 Document #: LTRT-83301 December 2006...

  • Page 3: Table Of Contents

    3.3.2 Installing the Mediant 1000 in a 19-inch Rack............38 Cabling the Mediant 1000 ..................39 3.4.1 Connecting the Mediant 1000 RS-232 Port to Your PC ..........40 3.4.2 Setting up a Dry Contact Relay Alarm System............41 3.4.3 Cabling the Digital Lifeline ..................42 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.................. 200 5.10 Monitoring the Gateway (Home Page)..............202 5.10.1 Monitoring the Mediant 1000 Trunks and Channels..........204 5.10.2 Monitoring the Modules ..................206 5.10.3 Monitoring Ethernet Ports, Dry Contacts, Power Supply Units, and Fan Tray Unit207 5.10.4 Viewing the Active Alarms Table ................
  • Page 6 Using BootP / DHCP..................259 BootP/DHCP Server Parameters ................. 259 Using DHCP......................259 Using BootP ......................260 7.3.1 Upgrading the Mediant 1000 ................260 7.3.2 Vendor Specific Information Field................. 261 Media Server Capabilities................263 Conference Server -- Simple Conferencing (NetAnn).......... 263 1.1.1 SIP Call Flow ......................
  • Page 7 9.14.4.1 Dialing from Remote Extension (Phone Connected to FXS) ....297 9.14.4.2 Dialing from other PBX line, or from PSTN ........... 298 9.14.4.3 FXS Mediant 1000 Configuration (using the Embedded Web Server) . 298 9.14.4.4 FXO Mediant 1000 Configuration (using the Embedded Web Server). 299 10 Networking Capabilities..................301...
  • Page 8 11.4 Redirect Number and Calling Name (Display) ............. 318 12 Advanced System Capabilities ..............319 12.1 Restoring Networking Parameters to their Initial State ........319 12.2 Establishing a Serial Communications Link with the Mediant 1000 ..... 319 12.3 Automatic Update Mechanism ................320 12.4 Startup Process....................323 12.5 Using Parameter Tables ..................
  • Page 9 14.6 Network Port Usage ..................... 362 14.7 Recommended Practices ..................363 14.8 Legal Notice ......................363 15 Diagnostics......................365 15.1 Self-Testing ......................365 15.2 Mediant 1000 Line Testing................... 366 15.3 Syslog Support..................... 366 15.3.1 Syslog Servers...................... 367 15.3.2 Operation ......................367 16 SNMP-Based Management ................369 16.1 SNMP Standards and Objects ................
  • Page 10 16.11 SNMP Administrative State Control ..............389 16.11.1 Node Maintenance....................389 16.11.2 Graceful Shutdown ....................389 16.12 AudioCodes’ Element Management System............390 17 Configuration Files..................391 17.1 Configuring the Call Progress Tones and Distinctive Ringing File....... 391 17.1.1 Format of the Call Progress Tones Section in the ini File ........391 17.1.2 Format of the Distinctive Ringing Section in the ini File ........
  • Page 11 SIP User's Manual Contents D.9 Log Window ......................416 D.10 Setting the Preferences..................417 D.10.1 BootP Preferences....................417 D.10.2 TFTP Preferences ....................418 D.11 Configuring the BootP Clients ................419 D.11.1 Adding Clients....................... 419 D.11.2 Deleting Clients..................... 420 D.11.3 Editing Client Parameters ..................420 D.11.4 Testing the Client....................
  • Page 12 Windows 2000/XP Operation Systems ..............461 Linux Operation Systems ..................462 K OSN Server Hardware Installation ..............465 Required Working Tools..................465 OSN Server Installation on the Mediant 1000............465 Linux™ Operating System Installation for the OSN Server......471 Physical Mounting Requirements................. 471 Software Requirements..................471 Physical Mounting Requirements.................
  • Page 13 Figure 3-4: Supplied RS-232 Cable .......................40 Figure 3-5: Dry Contact Wires’ Mate ......................41 Figure 3-6: Mediant 1000 Lifeline Cabling (e.g., Trunk 1 and Trunk 2) ..........42 Figure 3-7: Lifeline Pinout and RJ-11 Port 1 in the FXS Module ............43 Figure 3-8: Mediant 1000 Lifeline Setup ....................43 Figure 3-9: Slightly Extracted Fan Try Unit ....................46...
  • Page 14 Mediant 1000 Figure 5-42: Fax / Modem / CID Settings Screen ................151 Figure 5-43: RTP / RTCP Settings Screen..................154 Figure 5-44: Hook-Flash Settings Screen ................... 157 Figure 5-45: General Media Settings Screen ..................158 Figure 5-46: E1/T1 Trunk Settings Screen..................160 Figure 5-47: TDM Bus Settings Screen....................
  • Page 15 Figure 12-1: RS-232 Status and Error Messages ................320 Figure 12-2: Example of an ini File Activating the Automatic Update Mechanism......321 Figure 12-3: Mediant 1000 Startup Process..................324 Figure 12-4: Structure of a Parameter Table in the ini File ..............327 Figure 12-5: User-Customizable Web Interface Title Bar ..............
  • Page 16 Figure K-5: Inserting the CM Module ....................467 Figure K-6: Mediant 1000 Rear Panel View ..................468 Figure K-7: Mediant 1000 With Cover Plates Removed ..............468 Figure K-8: Mediant 1000 With Cutter Tool..................469 Figure K-9: Inserting the iPMX Module ....................469 Figure K-10: Inserting the HDMX Module ...................
  • Page 17 SIP User's Manual Contents List of Tables Table 2-1: Mediant 1000 Front View Component Descriptions (continues on pages 29 to 30).....29 Table 2-2: CPU Module LEDs Description .....................33 Table 2-3: Analog I/O Modules LEDs Description..................33 Table 2-4: Digital I/O Modules LED Description..................34 Table 2-5: Power Supply Module LED Description ................34...
  • Page 18 Table 16-4: SNMP v3 Predefined Groups................... 380 Table 17-1: User Information Items..................... 397 Table A-1: Mediant 1000 Functional Specifications (continues on pages 401 to 404) ....... 399 Table B-1: Mediant 1000 SIP Supplied Software Kit................403 Table C-1: SIP Functions ........................405 Table C-2: SIP Methods ........................
  • Page 19 SIP User's Manual Contents Table E-2: Defined Payload Types...................... 425 Table E-3: Default RTP/RTCP/T.38 Port Allocation................426 Table F-1: RTCP-XR Published VoIP Metrics (continues on pages 430 to 431)........ 427 Table H-1: Mapping of ISDN Release Reason to SIP Response (continues on pages 449 to 450) .. 446 Table H-2: Mapping of SIP Response to ISDN Release Reason (continues on pages 451 to 452) .
  • Page 20 Mediant 1000 Reader's Notes SIP User's Manual Document #: LTRT-83301...

  • Page 21: Weee Eu Directive

    Notices Notices Notice This document describes the AudioCodes Mediant 1000 Voice-over-IP (VoIP) SIP 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 22: Related Documentation

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

  • Page 23: 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 24: Sip Overview

    SIP also provides a registration function that enables users to upload their current locations for use by Proxy servers. SIP, on the Mediant 1000, complies with the IETF (Internet Engineering Task Force) RFC 3261 (refer to http://www.ietf.org/rfc/rfc3261.txt?number=3261).

  • Page 25: Pstn-To-Sip Interworking

    1.2.2 PSTN-to-SIP Interworking The Mediant 1000 Digital SIP gateway supports various ISDN PRI protocols such as EuroISDN, North American NI2, Lucent 4/5ESS, Nortel DMS100, Meridian1 DMS100, Japan J1, as well as QSIG. PRI support includes User Termination or Network Termination side.

  • Page 26: Supported Media Server Features

    Up to 60 participants in a full duplex conference. Up to 20 three-way conferences. 1.2.5 SIP Features The Mediant 1000 SIP gateway complies with the IETF RFC 3261 standard. Reliable User Datagram Protocol (UDP) transport, with retransmissions. Transmission Control Protocol (TCP) Transport layer. SIPS using TLS.
  • Page 27 SIP User's Manual 1. Overview The "sipgatewayname" parameter (defined in the ini file or set from the Web browser), can be any string. Some Proxy servers require that the "sipgatewayname" (in REGISTER messages) is set equal to the Registrar/Proxy IP address or to the Registrar/Proxy domain name.
  • Page 28 Publishes the total number of free Tel channels in a 200 OK response to an OPTIONS requests. Supports 3-Way Conference using an external media server. For more updated information on the gateway’s supported features, refer to the latest Mediant 1000 SIP Release Notes. SIP User's Manual Document #: LTRT-83301...

  • Page 29: 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 try module (the extractable modules are shown in Section on page 35).

  • Page 30: 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 31: 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 32: Port (Labeled I0I0)

    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 33: Front Panel Leds

    SIP User's Manual 2. Physical Description 2.1.6 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. Figure 2-3: Location of Front Panel LEDs...

  • Page 34: 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 35: Mediant 1000 Modules

    SIP User's Manual 2. Physical Description Mediant 1000 Modules The extractable Mediant 1000 modules are shown in Table 2-7 below. Table 2-7: Extractable Mediant 1000 Modules Module Description CPU module Digital I/O module (e.g., 2 spans) 4-port FXS Analog I/O module...
  • Page 36 Mediant 1000 Table 2-7: Extractable Mediant 1000 Modules Module Description Fan tray module with six fans and an air filter Power supply module SIP User's Manual Document #: LTRT-83301...

  • Page 37: Installing The Mediant 1000

    Cable the Mediant 1000 (refer to Section on page 39). 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 38: 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 39: 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 40: 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 41: Setting Up A Dry Contact Relay Alarm System

    (refer to Section 5.10.4 on page 207) 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 42: 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 43: 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 44: Maintenance

    45) 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 465). The replacement of Mediant 1000 communication modules (i.e., digital, FXS, and FXO) is performed using the Mediant 1000 embedded Web server.

  • Page 45: Replacing The Air Filter

    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 46: Figure 3-9: Slightly Extracted Fan Try Unit

    • Alternatively, if you are replacing the filter, discard the old air filter and replace it with an air filter purchased from AudioCodes. Attach the (new / cleaned) air filter to the fan tray module; position the two holes on...

  • 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 Section on page 55).

  • Page 48: Assigning An Ip Address Using Http

    Configuration’ to correspond with your network IP settings. If your network doesn’t feature a default gateway, enter a dummy value in the ‘Default Gateway IP Address’ field. Click the Reset button, and then at the prompt, click OK; the Mediant 1000 applies the changes and restarts. Tip: Record and retain the IP address and subnet mask you assign the Mediant 1000.

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

    419. 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 40). 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

    DMZ port. Under ‘SIP Parameters’, enter the Mediant 1000 domain name in the field ‘Gateway Name’. If the field is not specified, the Mediant 1000 IP address is used instead (default). When working with a Proxy server, set ‘Working with Proxy’ field to ‘Yes’, and then enter the IP address of the primary Proxy server in the field ‘Proxy IP Address’.

  • Page 53: December

    Section 5.5.4.2 on page 107. 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 SIP User's Manual Document #: LTRT-83301...

  • Page 55: Web Management

    SIP 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

    SIP 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: Using Internet Explorer To Access The Embedded Web Server

    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 202). Corporate logo: AudioCodes’ corporate logo. For information on how to remove this logo Section 12.5 on page 325. Search engine: for searching ini file parameters that are configured 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

    SIP 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 Note: If the searched parameter is not located, the "No Matches Found For This String"...

  • Page 62: Protocol Management

    Mediant 1000 Protocol Management The Protocol Management menu is used to configure the gateway’s SIP parameters and tables. Note: Throughout this chapter, parameters contained within square brackets are 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 SIP protocol parameters:...

  • Page 63: Figure 5-5: Protocol Definition, General Parameters Screen

    SIP User's Manual 5. Web Management Figure 5-5: Protocol Definition, General Parameters Screen Configure the general parameters according to Table 5-3. 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 200.

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

    Required [2]. Note 1: The Supported and Required headers contain the ‘100rel’ parameter. Note 2: Mediant 1000 sends PRACK message if 180/183 response is received with ‘100rel’ in the Supported or the Required headers. Channel Select Mode Port allocation algorithm for IP to Tel calls.
  • Page 65 SIP User's Manual 5. Web Management Table 5-3: Protocol Definition, General Parameters (continues on pages 64 to 70) Parameter Description Minimum Session-Expires Defines the time (in seconds) that is used in the Min-SE header. This header [MINSE] defines the minimum time that the user agent supports for session refresh. The valid range is 10 to 100000.
  • Page 66 Mediant 1000 Table 5-3: Protocol Definition, General Parameters (continues on pages 64 to 70) Parameter Description SIP Transport Type Determines the default transport layer used for outgoing SIP calls initiated by the [SIPTransportType] gateway. UDP [0] (default). TCP [1]. TLS [2] (SIPS).
  • Page 67 SIP User's Manual 5. Web Management Table 5-3: Protocol Definition, General Parameters (continues on pages 64 to 70) Parameter Description EnableHistoryInfo Enables usage of the History-Info header. [Enable History-Info Header] Valid options include: 0 = Disable (default) 1 = Enable UAC Behavior: Initial request: The History-Info header is equal to the Request URI.
  • Page 68 Mediant 1000 Table 5-3: Protocol Definition, General Parameters (continues on pages 64 to 70) Parameter Description Use Display Name as Applicable to IP Tel calls. Source Number No [0] = The IP Source Number is used as the Tel Source Number and the IP [UseDisplayNameAsSourc Display Name is used as the Tel Display Name (if IP Display Name is received).
  • Page 69 User-Agent Information Defines the string that is used in the SIP request header ‘User-Agent’ and SIP [UserAgentDisplayInfo] response header ‘Server’. If not configured, the default string ‘AudioCodes product-name s/w-version’ is used (e.g., User-Agent: Audiocodes-Sip-Gateway- Mediant 1000 FXS/v.4.80.004.008). When configured, the string ‘UserAgentDisplayInfo s/w-version’...

  • Page 70: Proxy & Registration Parameters

    Mediant 1000 Table 5-3: Protocol Definition, General Parameters (continues on pages 64 to 70) Parameter Description Enable Reason Header Enables / disables the usage of the SIP Reason header. [EnableReasonHeader] Disable [0]. Enable (default) [1]. Enable Semi-Attended Determines the gateway behavior when Transfer is initiated while still in Alerting Transfer state.

  • Page 71: Figure 5-6: Proxy & Registration Parameters Screen

    SIP User's Manual 5. Web Management Figure 5-6: Proxy & Registration Parameters Screen Configure the Proxy & Registration parameters according to Table 5-4. Click the Submit button to save your changes, or click the Register or Un-Register buttons to save your changes and to register / unregister to a Proxy / Registrar. To save the changes so they are available after a power fail, refer to Section 5.9.2 page 200.

  • Page 72: Table 5-4: Proxy & Registration Parameters (Continues On Pages 72 To 78)

    Mediant 1000 Table 5-4: Proxy & Registration Parameters (continues on pages 72 to 78) Parameter Description Enable Proxy Don’t Use Proxy [0] = Proxy isn’t used, the internal routing table is used instead [IsProxyUsed] (default). Use Proxy [1] = Proxy is used.
  • Page 73 SIP User's Manual 5. Web Management Table 5-4: Proxy & Registration Parameters (continues on pages 72 to 78) Parameter Description Third Redundant Proxy IP IP addresses of the third redundant Proxy you are using. Address Enter the IP address as FQDN or in dotted format notation (for example [ProxyIP] 192.10.1.255).
  • Page 74 Mediant 1000 Table 5-4: Proxy & Registration Parameters (continues on pages 72 to 78) Parameter Description Proxy Load Balancing Enables the usage of the Proxy Load Balancing mechanism. Method Valid options include: [ProxyLoadBalancingMe 0 = Load Balancing is disabled (default).
  • Page 75 SIP User's Manual 5. Web Management Table 5-4: Proxy & Registration Parameters (continues on pages 72 to 78) Parameter Description Enable Fallback to No [0] = Gateway fallback is not used (default). Routing Table Yes [1] = Internal Tel to IP Routing table is used when Proxy servers are not [IsFallbackUsed] available.
  • Page 76 Mediant 1000 Table 5-4: Proxy & Registration Parameters (continues on pages 72 to 78) Parameter Description Registration Time Defines the time (in seconds) for which registration to a Proxy server is valid. The [RegistrationTime] value is used in the header ‘Expires‘. In addition, this parameter defines the time interval between Keep-Alive messages when EnableProxyKeepAlive = 2 (REGISTER).
  • Page 77 SIP User's Manual 5. Web Management Table 5-4: Proxy & Registration Parameters (continues on pages 72 to 78) Parameter Description Proxy DNS Query Type Enables the use of DNS Naming Authority Pointer (NAPTR) and Service Record [ProxyDNSQueryType] (SRV) queries to discover Proxy servers. Valid options include: 0 = A-Record (default) 1 = SRV...

  • Page 78: Coders

    Mediant 1000 Table 5-4: Proxy & Registration Parameters (continues on pages 72 to 78) Parameter Description Cnonce String used by the server and client to provide mutual authentication. (Free format [Cnonce] i.e., ‘Cnonce = 0a4f113b’). Default_Cnonce The default is ‘...

  • Page 79: Table 5-5: Supported Coders

    SIP User's Manual 5. Web Management In the 'Payload Type' field, if the payload type for the coder you selected is dynamic, enter a value from 0 to 120 (payload types of ‘well-known’ coders cannot be modified). payload type identifies format payload.

  • Page 80: Dtmf & Dialing Parameters

    Mediant 1000 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 81 No [0] = Don’t declare RFC 2833 telephony-event parameter in SDP Yes [3] = Declare RFC 2833 telephony-event parameter in SDP (default) The Mediant 1000 is designed to always be receptive to RFC 2833 DTMF relay packets. Therefore, it is always correct to include the ‘telephony-event’ parameter as a default in the SDP.
  • Page 82 Mediant 1000 Table 5-6: DTMF & Dialing Parameters (continues on pages 80 to 82) Parameter Description Digit Mapping Rules Digit map pattern used to reduce the dialing period when Overlap dialing is used. If [DigitMapping] the digit string (dialed number) has matched one of the patterns in the digit map,...

  • Page 83: Configuring The Advanced Parameters

    SIP User's Manual 5. Web Management 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 83) Supplementary Services (refer to Section 5.5.2.2 on page 91) Metering Tones (refer to Section 5.5.2.3 on page 95)

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

    Mediant 1000 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 85: Table 5-7: Advanced Parameters, General Parameters (Continues On Pages 85 To 90)

    SIP User's Manual 5. Web Management Table 5-7: Advanced Parameters, General Parameters (continues on pages 85 to 90) Parameter Description IP Security No [0] = Gateway accepts all SIP calls (default). [SecureCallsFromIP] Yes [1] = Gateway accepts SIP calls only from IP addresses defined in the Tel to IP routing table.
  • Page 86 The digit delivery feature enables sending of DTMF digits to the gateway’s port after the call was answered. For IPàTel calls, after answering the call, the Mediant 1000 plays the DTMF digits (of the called number) towards the phone line.
  • Page 87 SIP User's Manual 5. Web Management Table 5-7: Advanced Parameters, General Parameters (continues on pages 85 to 90) Parameter Description Disconnect and Answer Supervision Enable Polarity Reversal Disable [0] = Disable the polarity reversal service (default). [EnableReversalPolarity] Enable [1] = Enable the polarity reversal service. If the polarity reversal service is enabled, then the FXS module changes the line polarity on call answer and changes it back on call release.
  • Page 88 Mediant 1000 Table 5-7: Advanced Parameters, General Parameters (continues on pages 85 to 90) Parameter Description Send Digit Pattern on Connect Defines a digit pattern that is sent to the Tel side after 200 OK is received from [TelConnectCode] the IP side. The digit pattern is a predefined DTMF sequence that is used to indicate an answer signal (e.g., for billing purposes).
  • Page 89 SIP User's Manual 5. Web Management Table 5-7: Advanced Parameters, General Parameters (continues on pages 85 to 90) Parameter Description Enable X-Channel Header 0 = x-channel header is not used (default). [XChannelHeader] 1 = x-channel header is generated, with trunk/B-channel information. The header provides information on the E1/T1 physical trunk/B-channel on which the call is received or placed.
  • Page 90 Mediant 1000 Table 5-7: Advanced Parameters, General Parameters (continues on pages 85 to 90) Parameter Description Max Call Duration (sec) Defines the maximum call duration in seconds. If this time expires, both sides of [MaxCallDuration] the call are released (IP and Tel).

  • Page 91: Supplementary Services

    SIP 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 267. To configure the supplementary services’ parameters, take these 4 steps: Open the ‘Supplementary Services’...

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

    Mediant 1000 Table 5-8: Supplementary Services Parameters (continues on pages 92 to 94) Parameter Description Enable Hold No [0] = Disable the Hold service. [EnableHold] Yes [1] = Enable the Hold service (default). If the Hold service is enabled, a user can activate Hold (or Unhold) using the hook- flash.
  • Page 93 [0] = Disabled (default). Enable [1] = MWI service is enabled. This parameter is applicable only to FXS modules. Note: The Mediant 1000 only supports reception of MWI. For detailed information on MWI, refer to Section 9.1.6 on page 270.
  • Page 94 Conference-initiating INVITE that is sent to the media server when Enable3WayConferenceis set to 1. When using the Mediant 1000 Conference module: To join a conference, the INVITE URI must include the Conference ID string, preceded by the number of the participants in the conference, and terminated by a unique number.

  • Page 95: Metering Tones

    SIP User's Manual 5. Web Management 5.5.2.3 Metering Tones FXS modules can generate 12/16 KHz metering pulses towards the Tel side (e.g., for connection to a payphone or private meter). Tariff pulse rate is determined according to an internal table. This capability enables users to define different tariffs according to the Source / Destination numbers and the Time-of-Day.

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

    Mediant 1000 Table 5-9: Metering Tones Parameters Parameter Description Metering Tone Type Defines the metering tone (12 kHz or 16 kHz) that is detected by FXO modules [MeteringType] and generated by FXS modules. 12 kHz [0] = 12 kHz metering tone (default).

  • Page 97: Keypad Features

    SIP User's Manual 5. Web Management 5.5.2.4 Keypad Features The Keypad Features screen (applicable only to FXS modules) enables you to activate and deactivate the following features directly from the connected telephone’s keypad: Hotline (refer to Section 5.5.6.2 on page 122). Caller ID Restriction (refer to Section 5.5.6.3 on page 123).

  • Page 98: Configuring The Number Manipulation Tables

    Mediant 1000 Table 5-10: Keypad Features Parameters (continues on pages 98 to 98) Parameter Description Forward Note that the forward type and number can be viewed in the Call Forward Table (refer to Section 5.5.6.4 page Unconditional Keypad sequence that activates the immediate forward option.
  • Page 99 SIP User's Manual 5. Web Management Note: Number manipulation can occur either before or after a routing decision is made. For example, you can route a call to a specific hunt (analog module) or trunk (digital module) group according to its original number, and then you can remove / add a prefix to that number before it is routed.

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

    Mediant 1000 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 101: Parameter Description

    SIP User's Manual 5. Web Management Table 5-11: Number Manipulation Parameters (continues on pages 100 to 101) Parameter Description Enter the number of digits that you want to remove from the left of the Number of Stripped Digits telephone number prefix. For example, if you enter 3 and the phone number is 5551234, the new phone number is 1234.

  • Page 102: 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. The list of ISDN ETSI NPI/TON values is shown as follows:...

  • Page 103: Mapping Npi/Ton To Phone-Context

    SIP User's Manual 5. Web Management For NI-2 and DMS-100 ISDN variants the valid combinations of TON and NPI for calling and called numbers are (Plan/Type): 0/0 - Unknown/Unknown 1/1 - International number in ISDN/Telephony numbering plan 1/2 - National number in ISDN/Telephony numbering plan 1/4 - Subscriber (local) number in ISDN/Telephony numbering plan 9/4 - Subscriber (local) number in Private numbering plan 5.5.3.3...

  • Page 104: Configuring The Routing Tables

    Mediant 1000 From the 'Phone Context Index' drop-down list, select the index number. Configure the Phone Context table according to Table 5-13. 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 105: General Parameters

    SIP User's Manual 5. Web Management 5.5.4.1 General Parameters Use this screen to configure the gateway’s IP Tel and Tel IP routing parameters. To configure the general parameters under Routing Tables, take these 4 steps: Open the ‘General Parameters’ screen (Protocol Management menu > Routing Tables submenu >...
  • Page 106 Mediant 1000 Table 5-14: Routing Tables, General Parameters (continues on pages 105 to 106) Parameter Description Add NPI and TON to Calling 0 = Do not change the Calling Number (default). Number 1 = Add NPI and TON to the Calling Number of incoming (Tel to IP) ISDN call.

  • Page 107: Tel To Ip Routing Table

    SIP User's Manual 5. Web Management 5.5.4.2 Tel to IP Routing Table The Tel to IP Routing Table is used to route incoming Tel calls to IP addresses. This routing table associates a called / calling telephone number’s prefixes with a destination IP address or with an FQDN (Fully Qualified Domain Name).

  • Page 108: Figure 5-17: Tel To Ip Routing Table Screen

    Mediant 1000 Note: If the alternative routing destination is the gateway itself, the call can be configured to be routed back to PSTN. This feature is referred to as ‘PSTN Fallback’, meaning that if sufficient voice quality is not available over the IP network, the call is routed through legacy telephony system (PSTN).

  • Page 109: Ip To Trunk Group Routing

    SIP User's Manual 5. Web Management Table 5-15: Tel to IP Routing Table (continues on pages 108 to 109) Parameter Description Dest. Phone Prefix Each entry in the Destination Phone Prefix fields represents a called telephone number prefix. The prefix can be 1 to 19 digits long. An asterisk (*) represents all numbers.

  • Page 110: Figure 5-18: Ip To Trunk Group Routing Table Screen

    Mediant 1000 Note: When a release reason that is defined in the ‘Reasons for Alternative IP to Tel Routing’ table is received for a specific IP Tel call, an alternative trunk group for that call is available. To associate an alternative trunk group to an incoming IP call, assign it with an additional entry in the ‘IP to Trunk Group...

  • Page 111: Internal Dns Table

    SIP User's Manual 5. Web Management Table 5-16: IP to Trunk Group Routing Table Parameter Description IP to Tel Routing Mode Defines order between routing calls to Trunk group and manipulation of [RouteModeIP2Tel] destination number. Route calls before manipulation [0] = IP Tel calls are routed before the number manipulation rules are applied (default).

  • Page 112: Internal Srv Table

    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-19: Internal DNS Table Screen In the ‘Domain Name' field, enter the host name to be translated.

  • Page 113: Reasons For Alternative Routing

    SIP User's Manual 5. Web Management To configure the Internal SRV table, take these 9 steps: Open the ‘Internal SRV Table’ screen (Protocol Management menu > Routing Tables submenu > Internal SRV Table option); the ‘Internal SRV Table’ screen is displayed.

  • Page 114: Release Cause Mapping

    200. 5.5.4.7 Release Cause Mapping The Release Cause Mapping screen enables the Mediant 1000 to map (up to 12) different SIP Responses to Q.850 Release Causes and vice versa, thereby overriding the hard- coded mapping mechanism (described in Appendix on page 445).

  • Page 115: 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 116: Coder Group Settings

    Mediant 1000 5.5.5.1 Coder Group Settings Use the Coder Group Settings screen to define up to four different coder groups. These coder groups are used in the Tel and IP Profile Settings screens to assign different coders to Profiles. For each group you can define the first to fifth preferred coders (and their attributes) for the gateway.

  • Page 117: Tel Profile Settings

    SIP User's Manual 5. Web Management Notes: • Each coder can appear only once. • The ptime specifies the packetization time the gateway expects to receive. The gateway always uses the ptime requested by the remote side for sending RTP packets. •...

  • Page 118: Figure 5-24: Tel Profile Settings Screen

    Mediant 1000 Figure 5-24: Tel Profile Settings Screen In the ‘Profile ID’ drop-down list, select the Tel Profile you want to edit (up to four Tel Profiles can be configured). In the ‘Profile Name’ field, enter a name that enables you to identify the Profile intuitively and easily.

  • Page 119: Ip Profile Settings

    SIP User's Manual 5. Web Management Configure the Profile’s parameters according to your requirements. For detailed information on each parameter, refer to the description of the screen in which it is configured as an individual parameter. In the ‘Coder Group’ drop-down list, select the coder group you want to assign to that Profile.

  • Page 120: Configuring The Endpoint Settings

    The Endpoint Settings screens are only applicable to the analog modules. 5.5.6.1 Authentication The Authentication screen (normally used with FXS modules) defines a username and password combination for authentication for each Mediant 1000 port. The ‘Authentication Mode’ parameter (described in Section 5.5.1.2 on page 70) determines if authentication is performed per port or for the entire gateway.

  • Page 121: Figure 5-26: Authentication Screen

    SIP User's Manual 5. Web Management To configure the Authentication Table, take these 6 steps: Set the ‘Authentication Mode’ parameter to ‘Per Endpoint’ (refer to Section 5.5.1.2 page 70). Open the ‘Authentication’ screen (Protocol Management menu > Endpoint Settings > Authentication option); the ‘Authentication’ screen is displayed. Figure 5-26: Authentication Screen In the ‘User Name’...

  • Page 122: Automatic Dialing

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

  • Page 123: Caller Id

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

  • Page 124: Call Forward

    Mediant 1000 Repeat steps 2 and 3 for each VoIP gateway port. 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 200. 5.5.6.4 Call Forward...

  • Page 125: Caller Id Permissions

    SIP User's Manual 5. Web Management Table 5-17: Call Forward Table Parameter Description Forward Type Not in use [0] = Don’t forward incoming calls (default). On Busy [1] = Forward incoming calls when the gateway port is busy. Immediate [2] = Forward any incoming call to the Phone number specified. No Answer [3] = Forward incoming calls that are not answered with the time specified in the ‘Time for No Reply Forward’...

  • Page 126: Configuring The Fxo Parameters

    Mediant 1000 In the ‘Caller ID’ field, select one of the following: • Enable: Enables Caller ID generation (FXS) or detection (FXO) for the specific port. • Disable: Caller ID generation (FXS) or detection (FXO) for the specific port is disabled.

  • Page 127: Table 5-18: Fxo Parameters (Continues On Pages 128 To 130)

    [IsWaitForDialTone] Yes [1] = Wait for dial tone (default). 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 128 Mediant 1000 Table 5-18: FXO Parameters (continues on pages 127 to 129) Parameter Description Analog: Busy or Reorder tone duration (seconds) the FXO module plays Reorder Tone Duration [sec] before releasing the line. [TimeForReorderTone] The valid range is 0 to 100. The default is 10 seconds for digital gateways and 0 seconds for analog gateways.

  • Page 129: Configuring The Voice Mail (Vm) Parameters

    SIP User's Manual 5. Web Management Table 5-18: FXO Parameters (continues on pages 127 to 129) Parameter Description Guard Time Between Calls Defines the time interval (in seconds) after a call has ended and a new call can be [GuardTimeBetweenCalls] accepted for IP to Tel calls.

  • Page 130: Table 5-19: Voice Mail Parameters

    Table 5-19: Voice Mail Parameters Parameter Description General Voice Mail Interface Enables the VM application on the Mediant 1000 and determines the [VoiceMailInterface] communication method used between the PBX and the gateway. None [0] (default) DTMF [1] SMDI [2] (N/A)

  • Page 131: Configuring The Trunk Group Table

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

  • Page 132: Configuring The Trunk Group Settings

    Mediant 1000 Table 5-20: Trunk Group Table (continues on pages 131 to 132) 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.

  • Page 133: Figure 5-34: Trunk Group Settings Screen

    SIP User's Manual 5. Web Management To configure the Trunk Group Settings table, take these 7 steps: Open the ‘Trunk Group Settings’ screen (Protocol Management menu > Trunk Group Settings); the ‘Trunk Group Settings’ screen is displayed. Figure 5-34: Trunk Group Settings Screen From the 'Routing Index' drop-down list, select the range of entries that you want to edit (up to 24 entries can be configured).

  • Page 134: Table 5-21: Channel Select Modes

    Mediant 1000 Table 5-21: 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 135: Configuring The Digital Gateway Parameters

    SIP User's Manual 5. Web Management 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);...

  • Page 136: Table 5-22: Digital Gateway Parameters (Continues On Pages 137 To 139)

    0 = Disabled (default). [EnableTDMoverIP] 1 = TDM Tunneling is enabled. When TDM Tunneling is enabled, the originating Mediant 1000 automatically initiates SIP calls from all enabled B-channels belonging to the E1/T1/J1 spans that are configured with the ‘Transparent’ protocol.
  • Page 137 SIP User's Manual 5. Web Management Table 5-22: Digital Gateway Parameters (continues on pages 136 to 138) Parameter Description Enable User-to-User IE for Tel to IP 0 = Disabled (default). [EnableUUITel2IP] 1 = Enable transfer of User-to-User Information Element (UUIE) from PRI Setup message to SIP INVITE message.

  • Page 138: Advanced Configuration

    Mediant 1000 Table 5-22: Digital Gateway Parameters (continues on pages 136 to 138) Parameter Description Remove CLI when Restricted Determines (for IP to Tel calls) whether the Calling Number IE and Calling [RemoveCLIWhenRestricted] Name IE are removed from the outgoing ISDN Setup message if the presentation is set to Restricted.

  • Page 139: Configuring The Ip Settings

    SIP User's Manual 5. Web Management 5.6.1.1 Configuring the IP Settings To configure the IP Settings parameters, take these 4 steps: Open the ‘IP Settings’ screen (Advanced Configuration menu > Network Settings > IP Settings option); the ‘IP Settings’ screen is displayed. Figure 5-36: IP Settings Screen Configure the IP Settings according to Table...
  • Page 140 Mediant 1000 Table 5-23: Network Settings, IP Settings Parameters (continues on pages 139 to 140) Parameter Description Subnet Mask Subnet mask of the gateway. Enter the subnet mask in dotted format notation, for example 255.255.0.0 Note 1: A warning message is displayed (after pressing the button ‘Submit’) if the entered value is incorrect.
  • Page 141 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 on page 259.

  • Page 142: Configuring The Application Settings

    Mediant 1000 5.6.1.2 Configuring the Application Settings To configure the Application Settings parameters, take these 4 steps: Open the ‘Application Settings’ screen (Advanced Configuration menu > Network Settings > Application Settings option); the ‘Application Settings’ screen is displayed. Figure 5-37: Application Settings Screen...

  • Page 143: 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 12.3...

  • Page 144: Figure 5-38: 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-37). Open the NFS Table screen by clicking the arrow sign (-->) to the right of the NFS label;...

  • Page 145: Configuring The Ip Routing Table

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

  • Page 146: Table 5-26: Ip Routing Table Column Description

    Mediant 1000 To configure the IP Routing table, take these 3 steps: Open the ‘IP Routing Table’ screen (Advanced Configuration menu > Network Settings > Routing Table option); the ‘IP Routing Table’ screen is displayed. Figure 1-3: IP Routing Table Screen Use the ‘Add a new table entry’...

  • Page 147: Configuring The Vlan Settings

    10.9 page 308. 5.6.1.5 Configuring the VLAN Settings For detailed information on the Mediant 1000 VLAN implementation, refer to Section 10.9 on page 308. To configure the VLAN Settings parameters, take these 4 steps: Open the ‘VLAN Settings’ screen (Advanced Configuration menu > Network Settings >...

  • Page 148: 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 149: Configuring The Voice Settings

    SIP User's Manual 5. Web Management 5.6.2.1 Configuring the Voice Settings To configure the Voice Settings parameters, take these 4 steps: Open the ‘Voice Settings’ screen (Advanced Configuration menu > Media Settings > Voice Settings option); the ‘Voice Settings’ screen is displayed. Figure 5-41: Voice Settings Screen Configure the Voice Settings according to Table...
  • Page 150 Mediant 1000 Table 5-28: Media Settings, Voice Settings Parameters Parameter Description Silence Suppression Silence Suppression is a method conserving bandwidth on VoIP calls by not [EnableSilenceCompression] sending packets when silence is detected. Disable [0] = Silence Suppression disabled (default). Enable [1] = Silence Suppression enabled.

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

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

  • Page 152: Table 5-29: Media Settings, Fax/Modem/Cid Parameters (Continues On Pages 153 To 154)

    Mediant 1000 Table 5-29: Media Settings, Fax/Modem/CID Parameters (continues on pages 152 to 153) Parameter Description Fax Transport Mode Fax Transport Mode that the gateway uses. [FaxTransportMode] You can select: Disable [0] (transparent mode). T.38 Relay [1] (default). Bypass [2].
  • Page 153 SIP User's Manual 5. Web Management Table 5-29: Media Settings, Fax/Modem/CID Parameters (continues on pages 152 to 153) Parameter Description V.34 Modem Transport Type V.90 / V.34 Modem Transport Type that the gateway uses. [V34ModemTransportType] You can select: 0 = Disable (Transparent) 1 = Enable Relay -- N/A 2 = Enable Bypass -- default 3 = Events Only (Transparent with Events)

  • Page 154: Configuring The Rtp / Rtcp Settings

    Mediant 1000 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 155: Table 5-30: Media Settings, Rtp / Rtcp Parameters (Continues On Pages 156 To 157)

    SIP User's Manual 5. Web Management Table 5-30: Media Settings, RTP / RTCP Parameters (continues on pages 155 to 156) Parameter Description Dynamic Jitter Buffer Minimum Delay Minimum delay for the Dynamic Jitter Buffer. [DJBufMinDelay] The valid range is 0 to 150 milliseconds. The default delay is 10 milliseconds.
  • Page 156 Mediant 1000 Table 5-30: Media Settings, RTP / RTCP Parameters (continues on pages 155 to 156) Parameter Description RTP Base UDP Port Lower boundary of UDP port used for RTP, RTCP (Real-Time Control [BaseUDPPort] Protocol) (RTP port + 1) and T.38 (RTP port + 2). The upper boundary is the Base UDP Port + 10 * (number of gateway’s channels).

  • Page 157: Configuring The Hook-Flash Settings

    SIP User's Manual 5. Web Management Table 5-30: Media Settings, RTP / RTCP Parameters (continues on pages 155 to 156) Parameter Description RTCP XR Report Mode Determines whether or not RTCP-XR reports are sent to the Event State [RTCPXRReportMode] Compositor (ESC) and if so, defines the interval in which they are sent. Valid options include: 0 = Disable (RTCP-XR reports are not sent to the ESC) -- default 1 = End Call (RTCP-XR reports are sent to the ESC at the end of each...

  • Page 158: Configuring The General Media Settings

    Mediant 1000 Table 5-31: 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). [MinFlashHookTime] The valid range is 25 to 300. The default value is 300 msec.

  • Page 159: Table 5-32: Media Settings, General Media Settings Parameters

    SIP User's Manual 5. Web Management Table 5-32: 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 160: Configuring The Trunk Settings

    Mediant 1000 5.6.3 Configuring the Trunk Settings To configure the Trunk Settings, take these 9 steps: Open the ‘Trunk Settings’ screen (Advanced Configuration menu > Trunk Settings); the ‘Trunk Settings’ screen is displayed. Initially, the screen appears with the parameters fields grayed (i.e., read-only). The...
  • Page 161 Note: If the trunk can’t be stopped because it provides the gateway’s clock (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 162: Table 5-33: E1/T1/J1 Configuration Parameters (Continues On Pages 163 To 166)

    Mediant 1000 Table 5-33: E1/T1/J1 Configuration Parameters (continues on pages 162 to 165) ini File Field Name Valid Range and Description Web Parameter Name ProtocolType Sets the PSTN protocol to be used for this trunk. [Protocol Type] 1 = E1_EURO_ISDN...
  • Page 163 SIP User's Manual 5. Web Management Table 5-33: E1/T1/J1 Configuration Parameters (continues on pages 162 to 165) ini File Field Name Valid Range and Description Web Parameter Name TraceLevel Defines the trace level. [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 164 Mediant 1000 Table 5-33: E1/T1/J1 Configuration Parameters (continues on pages 162 to 165) ini File Field Name Valid Range and Description Web Parameter Name ISDNRxOverlap_x Enable / disable Rx ISDN overlap per trunk ID. [Enable Receiving of Overlap 0 = Disabled (default).
  • Page 165 SIP User's Manual 5. Web Management Table 5-33: E1/T1/J1 Configuration Parameters (continues on pages 162 to 165) ini File Field Name Valid Range and Description Web Parameter Name ISDNInCallsBehavior 2048 = Sends Channel ID in the first response to an incoming Q.931 Call [Incoming Calls Behavior] Setup message.

  • Page 166: Configuring The Tdm Bus Settings

    To save the changes so they are available after a power fail, refer to Section 5.9.2 page 200. 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 200. Note: Usually the ‘PCM Law Select’...
  • Page 167 SIP User's Manual 5. Web Management Table 5-34: TDM Bus Settings Parameters (continues on pages 166 to 167) Parameter Description Idle ABCD Pattern ABCD (CAS) Pattern to be applied to CAS signaling bus when the [IdleABCDPattern] channel is idle. Range 0x0 to 0xF Default = -1 (default, pattern = 0000) Note: This is only relevant when using PSTN interface with CAS protocols.

  • Page 168: Restoring And Backing Up The Gateway Configuration

    Mediant 1000 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 169: Regional Settings

    CAS) to the gateway. For detailed information on the configuration files, refer to Section 5.8.2 on page 196. 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 170: Security Settings

    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 198).

  • Page 171: Figure 5-50: Web User Accounts Screen (For Users With 'Security Administrator' Privileges)

    SIP User's Manual 5. Web Management To change the Web User Accounts attributes, take these 4 steps: Open the ‘Web User Accounts’ screen (Advanced Configuration menu > Security Settings > Web User Accounts option); the ‘Web User Accounts’ screen is displayed.

  • Page 172: Configuring The Web And Telnet Access List

    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 14.5 on page 360.

  • Page 173: Figure 5-52: Firewall Settings Screen

    SIP User's Manual 5. Web Management To create a new access rule, take these 6 steps: Open the ‘Firewall Settings’ screen (Advanced Configuration menu > Security Settings > Firewall Settings option); the ‘Firewall Settings’ screen is displayed. Figure 5-52: Firewall Settings Screen In the ‘New Rule Index’...

  • Page 174: Configuring The Certificates

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

  • Page 175: Configuring The General Security Settings

    SIP User's Manual 5. Web Management 5.6.7.5 Configuring the General Security Settings To configure the General Security Settings parameters, take these 4 steps: Open the ‘General Security Settings’ screen (Advanced Configuration menu > Security Settings > General Security Settings option); the ‘General Security Settings’...

  • Page 176: Table 5-36: General Security Settings Parameters (Continues On Pages 176 To 178)

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

  • Page 177: Configuring The Ipsec Table

    SIP User's Manual 5. Web Management Table 5-36: General Security Settings Parameters (continues on pages 176 to 177) 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 [RadiusLocalCacheMode] username and password (verified by the RADIUS server).

  • Page 178: Configuring The Ike Table

    Mediant 1000 5.6.7.7 Configuring the IKE Table Use the IKE Table screen to configure the IKE parameters. For detailed information on IPSec and IKE, refer to Section 14.1 on page 343. 5.6.8 Configuring the Management Settings To configure the Management Settings parameters, take these 4 steps: Open the ‘Management Settings’...

  • Page 179: Table 5-37: Management Settings Parameters (Continues On Pages 180 To 181)

    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 180: Configuring The Snmp Managers Table

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

  • Page 181: Configuring The Snmp Community Strings

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

  • Page 182: Configuring Snmp V3 Users

    Mediant 1000 Figure 5-56: SNMP Community Strings Screen Configure the SNMP Community Strings parameters according to Table 5-39. 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 183: Figure 5-57: Snmp V3 Setting Screen

    SIP User's Manual 5. Web Management Figure 5-57: SNMP V3 Setting Screen To add an SNMP v3 user, in the 'New Row Index' field, type the desired row index, and then click Add an Empty Row. A new row appears. Configure the SNMP V3 Setting parameters according to Table 5-40 on page 183.

  • Page 184: Status & Diagnostics

    Mediant 1000 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 185: Figure 5-58: Ip Connectivity Screen

    SIP User's Manual 5. Web Management Figure 5-58: IP Connectivity Screen Table 5-41: IP Connectivity Parameters Column Name Description IP Address IP address defined in the destination IP address field in the Tel to IP Routing table. - or - IP address that is resolved from the host name defined in the destination IP address field in the Tel to IP Routing table.

  • Page 186: Call Counters

    Mediant 1000 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 187 SIP User's Manual 5. Web Management Table 5-42: Call Counters Description (continues on pages 186 to 187) 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: GWAPP_REASON_NOT_RELEVANT (0) GWAPP_NORMAL_CALL_CLEAR (16) GWAPP_NORMAL_UNSPECIFIED (31)

  • Page 188: Call Routing Status

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

  • Page 189: Activating The Internal Syslog Viewer

    It's not recommended to keep a ‘Message Log’ session open (even if the 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 15.3...

  • Page 190: 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 191: Software Update

    5. Web Management 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.

  • Page 192: Figure 5-63: 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 193: Figure 5-65: Cmp File Successfully Loaded

    SIP User's Manual 5. Web Management 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-65).

  • Page 194: Figure 5-67: 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 195: Figure 5-68: Finish Screen

    SIP User's Manual 5. Web Management Figure 5-68: FINISH Screen Figure 5-69: ‘End Process’ Screen Click the End Process button; the ‘Quick Setup’ screen appears and the full Web application is reactivated. Version 5.0 December 2006...

  • Page 196: Auxiliary Files

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

  • Page 197: Figure 5-70: Auxiliary Files Screen

    200. 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 198).

  • Page 198: 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 199: Figure 5-71: Maintenance Actions Screen

    SIP User's Manual 5. Web Management To lock the gateway, take these 4 steps: Open the ‘Maintenance Actions' screen (Maintenance menu); the ‘Maintenance Actions' screen is displayed. Figure 5-71: Maintenance Actions Screen Under the LOCK / UNLOCK group, from the 'Graceful Option' drop-down list, select one of the following options: •...

  • Page 200: Saving Configuration

    Click the BURN button; a confirmation message appears when the save is completed successfully. 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 201: Figure 5-73: Maintenance Actions Screen

    SIP User's Manual 5. Web Management To reset the gateway, take these 6 steps: Open the ‘Maintenance Actions' screen (Maintenance menu); the ‘Maintenance Actions' screen is displayed. Figure 5-73: Maintenance Actions Screen Under the RESET group, from the 'Burn To FLASH' drop-down list, select one of the following options: •...

  • Page 202: Monitoring The Gateway (Home Page)

    IP address, the number of digital and analog ports, and firmware version. Table 5-45 on page describes the areas of the graphic display of the Mediant 1000 chassis. SIP User's Manual Document #: LTRT-83301...

  • Page 203: Table 5-45: Description Of The Areas Of The Home Page

    SIP User's Manual 5. Web Management Table 5-45: 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 207. Module slot number (1 to 6). Module type (digital, FXO, or FXS).

  • Page 204: 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 205: Figure 5-75: Status Of Channels Per Trunk In The Trunk & Channel Screen

    SIP User's Manual 5. Web Management Figure 5-75: Status of Channels per Trunk in the Trunk & Channel Screen The trunk's channels are graphically displayed as icons. The colors of the icons depict the channels' statuses. For a description of the color coding for the channel status, refer to Table 5-47 on page 205.

  • Page 206: Monitoring The Modules

    Mediant 1000 5.10.2 Monitoring the Modules The Home page also provides color-coding for displaying the status of the modules (digital and anlog). In the Home page, the color of the 'square brackets' enclosing the module depicts the status of the module.

  • Page 207: Monitoring Ethernet Ports, Dry Contacts, Power Supply Units, And Fan Tray Unit207

    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 208: Viewing Trunk Settings

    Mediant 1000 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 160), in which the trunk settings are viewed and configured.

  • Page 209: Viewing Ethernet Port Settings

    5. Web Management 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-50. For detailed information on the Ethernet interface configuration, refer to Section 10.1...

  • Page 210: Releasing An Analog Channel

    Mediant 1000 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 211: Figure 5-84: Confirmation Message Box After Clicking Remove Module Button

    SIP User's Manual 5. Web Management Figure 5-84: Confirmation Message Box after Clicking Remove Module Button Click OK to confirm module removal; after a few seconds, the module is "removed" and the module status indicator is grayed. The name of the module is suffixed with the word 'Reserved'.

  • Page 212: Logging Off The Embedded Web Server

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

  • Page 213: 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 214: 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 215) System parameters (refer to Section 6.5.2 on page 220) Web and Telnet parameters (refer to Section 6.5.3...

  • Page 215: December

    SIP 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: SIP ini File Example [Channel Params] DJBufMinDelay = 75...
  • Page 216 Mediant 1000 Table 6-1: Networking Parameters (continues on pages 215 to 220) ini File Field Name Valid Range and Description Web Parameter Name DNS2IP The Internal DNS table is used to resolve host names to IP addresses. Two different IP addresses (in dotted format notation) can be assigned to a hostname.
  • Page 217 SIP User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-1: Networking Parameters (continues on pages 215 to 220) ini File Field Name Valid Range and Description Web Parameter Name EnableUDPPortTranslation 0 = Disable UDP port translation (default).
  • Page 218 Mediant 1000 Table 6-1: Networking Parameters (continues on pages 215 to 220) ini File Field Name Valid Range and Description Web Parameter Name IP Routing Table parameters: The IP routing ini file parameters are array parameters. Each parameter configures a specific column in the IP routing table.
  • Page 219 SIP User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-1: Networking Parameters (continues on pages 215 to 220) ini File Field Name Valid Range and Description Web Parameter Name LocalMediaIPAddress For a description of this parameter, refer to Table 5-23 on page 139.

  • Page 220: 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 221 SIP User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-2: System Parameters (continues on pages 220 to 225) ini File Field Name Valid Range and Description Web Parameter Name EnableDiagnostics Checks the correct functionality of the different hardware components on the gateway.
  • Page 222 Mediant 1000 Table 6-2: System Parameters (continues on pages 220 to 225) ini File Field Name Valid Range and Description Web Parameter Name ECHybridLoss Sets the four wire to two wire worst case Hybrid loss, the ratio between the signal level sent to the hybrid and the echo level returning from the hybrid.
  • Page 223 SIP User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-2: System Parameters (continues on pages 220 to 225) ini File Field Name Valid Range and Description Web Parameter Name FarEndDisconnectSilenceT Threshold of the packet count (in percents), below which is considered silence hreshold by the media gateway.
  • Page 224 Mediant 1000 Table 6-2: System Parameters (continues on pages 220 to 225) ini File Field Name Valid Range and Description Web Parameter Name AutoUpdateCmpFile Enables / disables the Automatic Update mechanism for the cmp file. 0 = The Automatic Update mechanism doesn’t apply to the cmp file (default).

  • Page 225: Web And Telnet Parameters

    SIP User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-2: System Parameters (continues on pages 220 to 225) ini File Field Name Valid Range and Description Web Parameter Name ExtBootPReqEnable 0 = Disable (default). 1 = Enable extended information to be sent in BootP request.
  • Page 226 Name of the image file containing the user’s logo. 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 227: Security

    SIP User's Manual 6. ini File Configuration of the Mediant 1000 6.5.4 Security Table 6-4: Security Parameters (continues on pages 227 to 228) ini File Field Name Valid Range and Description Web Parameter Name EnableIPSec For a description of this parameter, refer to Table 5-36 on page 176.

  • Page 228: Radius Parameters

    Mediant 1000 Table 6-4: Security Parameters (continues on pages 227 to 228) ini File Field Name Valid Range and Description Web Parameter Name AccessList_Allow_Type For a description of this parameter, refer to Table 5-35 on page 174. AccessList_MatchCount For a description of this parameter, refer to Table 5-35 on page 174.

  • Page 229: Snmp Parameters

    SIP User's Manual 6. ini File Configuration of the Mediant 1000 6.5.6 SNMP Parameters Table 6-6: SNMP Parameters ini File Field Name Valid Range and Description Web Parameter Name DisableSNMP For a description of this parameter, refer to Table 5-37 on page 179.

  • Page 230: Sip Configuration Parameters

    Mediant 1000 6.5.7 SIP Configuration Parameters Table 6-7: SIP Configuration Parameters (continues on pages 230 to 236) ini File Field Name Valid Range and Description Web Parameter Name SIPTransportType For a description of this parameter, refer to Table 5-3 on page 64.
  • Page 231 SIP User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-7: SIP Configuration Parameters (continues on pages 230 to 236) ini File Field Name Valid Range and Description Web Parameter Name GWRegistrationName For a description of this parameter, refer to Table 5-4 on page 72.
  • Page 232 Mediant 1000 Table 6-7: SIP Configuration Parameters (continues on pages 230 to 236) ini File Field Name Valid Range and Description Web Parameter Name CoderName Defines the gateway’s coder list (Coders table). Up to five coders can be configured. Enter coders in the following format: CoderName=<Coder Name>,<Ptime>,<Rate>,<Payload Type>,<Silence...
  • Page 233 SIP User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-7: SIP Configuration Parameters (continues on pages 230 to 236) ini File Field Name Valid Range and Description Web Parameter Name IPPSessionExpires For a description of this parameter, refer to Table 5-3 on page 64.
  • Page 234 Mediant 1000 Table 6-7: SIP Configuration Parameters (continues on pages 230 to 236) ini File Field Name Valid Range and Description Web Parameter Name FirstCallWaitingToneID Determines the index of the first Call Waiting Tone in the CPT file. This feature enables the called party to distinguish between four different call origins (e.g.,...
  • Page 235 SIP User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-7: SIP Configuration Parameters (continues on pages 230 to 236) ini File Field Name Valid Range and Description Web Parameter Name SITDetectorEnable Enables or disables Special Information Tone (SIT) detection according to the ITU-T recommendation E.180/Q.35.
  • Page 236 Mediant 1000 Table 6-7: SIP Configuration Parameters (continues on pages 230 to 236) ini File Field Name Valid Range and Description Web Parameter Name IPProfile_ID IPProfile_<Profile ID> = [IP Profile Settings] <Profile Name>,<Preference>,<Coder Group ID>,<IsFaxUsed*>, <DJBufMinDelay *>, <DJBufOptFactor *>,<IPDiffServ*>, <ControlIPDiffServ*>,<N/A use $$ instead>, <RTPRedundancyDepth>,<RemoteBaseUDPPort>,<CNGmode>,...

  • Page 237: Voice Mail Parameters

    SIP User's Manual 6. ini File Configuration of the Mediant 1000 6.5.8 Voice Mail Parameters For detailed information on the Voice Mail (VM) application, refer to the CPE Configuration Guide for Voice Mail. Table 6-8: Voice Mail Configuration Parameters ini File Field Name...
  • Page 238 Mediant 1000 Table 6-9: ISDN and CAS Interworking-Related Parameters (continues on pages 237 to 242) ini File Field Name Valid Range and Description Web Parameter Name PlayRBTone2Trunk_ID ID = Trunk number (0-7). 0 (Don’t play) = The ISDN / CAS gateway doesn’t play a Ringback Tone (RBT).
  • Page 239 SIP User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-9: ISDN and CAS Interworking-Related Parameters (continues on pages 237 to 242) ini File Field Name Valid Range and Description Web Parameter Name CauseMapSIP2ISDN_ID Defines a flexible mapping of SIP Responses and Q.850 Release Causes.
  • Page 240 Mediant 1000 Table 6-9: ISDN and CAS Interworking-Related Parameters (continues on pages 237 to 242) ini File Field Name Valid Range and Description Web Parameter Name LocalISDNRBSource_ID ID = Trunk number (0-7). Determines whether Ringback tone is played to the ISDN by the PBX / PSTN or by the gateway.
  • Page 241 Table 5-18 on page 127. PlayBusyTone2ISDN This parameter enables the Mediant 1000 ISDN gateway to play a Busy or a Reorder tone to the PSTN after a call is released. 0 = Immediately sends an ISDN Disconnect message (default). 1 = Sends an ISDN Disconnect message with PI=8 and plays a Busy or a Reorder tone to the PSTN (depending on the release cause).

  • Page 242: Analog Telephony Parameters

    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 243 SIP User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-10: Analog Telephony Parameters (continues on pages 242 to 246) ini File Field Name Valid Range and Description Web Parameter Name [Module n] TargetOfChannel<Port> = <Phone>,<Mode> TargetOfChannelX Port = 0 to 3.
  • Page 244 Mediant 1000 Table 6-10: Analog Telephony Parameters (continues on pages 242 to 246) ini File Field Name Valid Range and Description Web Parameter Name NumberOfWaitingIndicati For a description of this parameter, refer to Table 5-8 on page 92. TimeBetweenWaitingIndi For a description of this parameter, refer to Table 5-8 on page 92.
  • Page 245 SIP User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-10: Analog Telephony Parameters (continues on pages 242 to 246) ini File Field Name Valid Range and Description Web Parameter Name EnableDID Enables Japan NTT ‘Modem’ Direct Inward Dialing (DID) support. FXS modules can be connected to Japan’s NTT PBX using ‘Modem’...
  • Page 246 Mediant 1000 Table 6-10: Analog Telephony Parameters (continues on pages 242 to 246) ini File Field Name Valid Range and Description Web Parameter Name ETSIVMWITypeOneStand Selects the ETSI Visual Message Waiting Indication (VMWI) Type 1 sub- standard. 0 = ETSI VMWI between rings (default)

  • Page 247: Number Manipulation And Routing Parameters

    SIP User's Manual 6. ini File Configuration of the Mediant 1000 6.5.11 Number Manipulation and Routing Parameters Table 6-11: Number Manipulation and Routing Parameters (continues on pages 247 to 253) ini File Field Name Valid Range and Description Web Parameter Name...
  • Page 248 Mediant 1000 Table 6-11: Number Manipulation and Routing Parameters (continues on pages 247 to 253) ini File Field Name Valid Range and Description Web Parameter Name ReplaceEmptyDstWithPort For a description of this parameter, refer to Table 5-14 on page 105.
  • Page 249 SIP User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-11: Number Manipulation and Routing Parameters (continues on pages 247 to 253) ini File Field Name Valid Range and Description Web Parameter Name PSTNPrefix PSTNPrefix = a,b,c,d,e a = Destination Number Prefix...
  • Page 250 Mediant 1000 Table 6-11: Number Manipulation and Routing Parameters (continues on pages 247 to 253) ini File Field Name Valid Range and Description Web Parameter Name NumberMapTel2IP Manipulates the destination number for Tel to IP calls (Destination Phone Number Manipulation Table for Tel IP calls).
  • Page 251 SIP User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-11: Number Manipulation and Routing Parameters (continues on pages 247 to 253) ini File Field Name Valid Range and Description Web Parameter Name SourceNumberMapTel2IP Configures the Source Phone Number Manipulation Table for Tel IP calls.
  • Page 252 Mediant 1000 Table 6-11: Number Manipulation and Routing Parameters (continues on pages 247 to 253) ini File Field Name Valid Range and Description Web Parameter Name For ETSI ISDN variant, the following Number Plan and Type combinations (Plan/Type) are supported in the...

  • Page 253: E1/T1 Configuration Parameters

    SIP User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-11: Number Manipulation and Routing Parameters (continues on pages 247 to 253) ini File Field Name Valid Range and Description Web Parameter Name Alternative Routing Parameters AltRoutingTel2IPEnable For a description of this parameter, refer to Table 5-14 on page 105.
  • Page 254 Mediant 1000 Table 6-12: E1/T1/J1 Configuration Parameters (continues on pages 253 to 255) ini File Field Name Valid Range and Description Web Parameter Name TerminationSide_x Same as the description for parameter TerminationSide, but for a specific trunk ClockMaster For a description of this parameter, refer to Table 5-33 on page 162.

  • Page 255: Channel Parameters

    SIP User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-12: E1/T1/J1 Configuration Parameters (continues on pages 253 to 255) ini File Field Name Valid Range and Description Web Parameter Name HeldTimeout Determines the time period the gateway can stay on-hold. If a Resume (un-hold Re- INVITE) message is received before the timer expires, the call is renewed.
  • Page 256 The payload type used with these G.711 coders is a standard one (8 for G.711 A-Law and 0 for G.711 µ-Law). The parameters defining payload type for the ‘old' AudioCodes’ Bypass mode. ‘FaxBypassPayloadType’ and ‘ModemBypassPayloadType’ are not used with NSE Bypass. The bypass packet interval is selected according to the parameter ‘FaxModemBypassBasicRtpPacketInterval’.
  • Page 257 SIP User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-13: Channel Parameters (continues on pages 255 to 258) ini File Field Name Valid Range and Description Web Parameter Name VoiceVolume For a description of this parameter, refer to Table 5-28 on page 149.

  • Page 258: Configuration Files Parameters

    158. 6.5.14 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 196).

  • Page 259: 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 260: Using Bootp

    Using BootP 7.3.1 Upgrading the Mediant 1000 When upgrading the Mediant 1000 (loading new software onto the gateway) using the BootP/TFTP configuration utility: From version 4.4 to version 4.4 or to any higher version, the device retains its configuration (ini file). However, the auxiliary files (CPT, logo, etc.) may be erased.

  • Page 261: Vendor Specific Information Field

    7. Using BootP / DHCP 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 D-1).
  • Page 262 Mediant 1000 Reader's Notes SIP User's Manual Document #: LTRT-83301...

  • Page 263: Media Server Capabilities

    The conference application is a special order option. The Mediant 1000 server supports dial-in, multi-party conferencing. In conference applications, the Mediant 1000 server functions as a centralized conference bridge. In ad- hoc or prearranged conferences, users ‘invite’ the conference bridge. The conference bridge combines the media and sends it to all participants.

  • Page 264: Sip Call Flow

    Mediant 1000 1.1.1 SIP Call Flow Figure 8-1: Simple Conferencing SIP Call Flow SIP User's Manual Document #: LTRT-83301...

  • Page 265: Creating A Conference

    '6conf100' reserves six resources for the duration of the conference. If the Mediant 1000 can allocate the requested number of resources, it responds with a 200 The Conference Service Identifier can be set via the Mediant 1000 ini file (ConferenceID) or via the Web interface.

  • Page 266: Pstn Participants

    PSTN Participants Adding PSTN participants is done by performing loopback from the IP side (TEL2IP have the Mediant 1000 IP address). If the destination phone number in the incoming call from the PSTN is equal to the Conference Service Identifier and Unique Conference Identifier, the participant joins the conference.

  • Page 267: Telephony Capabilities

    SDP message, the gateway stops sending RTP packets, but continues to listen to the incoming RTP packets. Usually, the remote party plays, in this scenario, Music on Hold (MOH) and the Mediant 1000 forwards the MOH to the held party 9.1.1.2 Receiving Hold / Retrieve When an active call receives REINVITE message with either the IP address 0.0.0.0 or...

  • Page 268: Consultation / Alternate

    Consultation / Alternate The consultation feature is relevant only for the holding party (applicable only to the Mediant 1000/FXS module). After holding a call (by pressing hook-flash), the holding party hears a dial tone and can now initiate a new call, which is called a consultation call.

  • Page 269: Call Waiting

    Disturb call, the 603 Decline SIP response code 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 270: Message Waiting Indication

    Message Waiting Indication Support for Message Waiting Indication (MWI) according to IETF <draft-ietf-sipping-mwi- 04.txt>, including SUBSCRIBE (to MWI server). Mediant 1000/FXS modules can accept an MWI NOTIFY message that indicates waiting messages or that the MWI is cleared. Users are informed of these messages by a stutter dial tone. The stutter and confirmation tones are defined in the CPT file (refer to Section 17.1...
  • Page 271 To exclude RFC 2833 Telephony event parameter from the gateway’s SDP, set ‘RxDTMFOption = 0’ in the ini file. The following parameters affect the way the Mediant 1000 SIP handles the DTMF digits: TxDTMFOption, RxDTMFOption and RFC2833PayloadType (described in Table 5-6).

  • Page 272: Fax & Modem Transport Modes

    Mediant 1000 Fax & Modem Transport Modes 9.3.1 Fax/Modem Settings Users may choose to use one of the following transport methods for fax and for each modem type (V.22/V.23/Bell/V.32/V.34): Fax relay: demodulation / modulation Bypass: using a high bit rate coder to pass the signal...

  • Page 273: Supporting V.34 Faxes

    SIP User's Manual 9. Telephony Capabilities 9.3.4 Supporting V.34 Faxes V.34 faxes don’t comply with the T.38 relay standard. We therefore provide the optional modes described under Sections 9.3.4.1 and 9.3.4.2: Note that the CNG detector is disabled (CNGDetectorMode=0) in all the following examples.

  • Page 274: Supporting V.152 Implementation

    Mediant 1000 9.3.5 Supporting V.152 Implementation The gateway supports the ITU-T recommendation V.152 (Procedures for Supporting Voice- Band Data over IP Networks). Voice-band data (VBD) is the transport of modem, facsimile, and text telephony signals over a voice channel of a packet network with a codec appropriate for such signals.

  • Page 275: Fxo Operating Modes

    SIP User's Manual 9. Telephony Capabilities FXO Operating Modes This section provides a description of the FXO operating modes and gateway configurations for Tel-to-IP and IP-to-Tel calls. 9.4.1 IP-to-Telephone Calls The FXO gateway provides the following operating modes for IP-to-Tel calls: One-stage dialing •...

  • Page 276: Two-Stage Dialing

    Mediant 1000 One -stage dialing incorporates the following FXO functionality: Waiting for Dial Tone The Waiting for Dial Tone feature enables the gateway to dial the digits to the Tel side only after detecting a dial tone from the PBX line. The ini file parameter IsWaitForDialTone is used to configure this operation.

  • Page 277: Call Termination (Disconnect Supervision) On Mediant 1000/Fxo

    DTMFInterDigitInterval (100 msec): time between generated DTMF digits to PSTN (PBX) side 9.4.1.3 Call Termination (Disconnect Supervision) on Mediant 1000/FXO The FXO Disconnect Supervision enables the gateway's FXO ports to monitor call- progress tones from a PBX or from the PSTN. This allows the FXO to determine when the call has terminated on the PBX side, and thereby, prevents analog trunks (i.e., lines to the...

  • Page 278: Did Wink

    Mediant 1000 Interruption of RTP stream: Relevant parameters: BrokenConnectionEventTimeout and DisconnectOnBrokenConnection. Note: This method operates correctly only if silence suppression is not used. Protocol-based termination of the call from the IP side Note: The implemented disconnect method must be supported by the CO or PBX.

  • Page 279: Automatic Dialing

    SIP User's Manual 9. Telephony Capabilities 9.4.2.1 Automatic Dialing Automatic dialing is defined using the ini file parameter TargetOfChannelX (where 'X' is the channel number) or the embedded Web server's 'Automatic Dialing' screen (refer to Section 5.5.6.2 on page 122). The SIP call flow diagram below illustrates Automatic Dialing.

  • Page 280: Collecting Digits Mode

    Mediant 1000 9.4.2.2 Collecting Digits Mode When automatic dialing is not defined, the gateway collects the digits. The SIP call flow diagram below illustrates the Collecting Digits Mode. Figure 9-4: Call Flow for Collecting Digits Mode 9.4.2.3 Ring Detection Timeout The ini file parameters IsWaitForDialTone and WaitForDialTone apply to Ring Detection Timeout.

  • Page 281: Fxo Supplementary Services

    SIP User's Manual 9. Telephony Capabilities 9.4.2.4 FXO Supplementary Services Hold / Transfer toward the Tel side The ini file parameter LineTransferMode must be set to 0 (default). If the FXO receives a hook-flash from the IP side (using out-of-band or RFC 2833), the gateway sends the hook-flash to the Tel side by one of the following: •...
  • Page 282 Mediant 1000 The X-Detect event notification process is as follows: For IP-to-Tel or Tel-to-IP calls, the gateway receives a SIP request message (using the X-Detect header) that the remote party wishes to detect events on the media stream. For incoming (IP-to-Tel) calls, the request must be indicated in the initial INVITE and responded to either in the 183 response (for early dialogs) or in the 200 OK response (for confirmed dialogs).

  • Page 283: Throughpacket

    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 284: Configuring The Gateway's Alternative Routing (Based On Connectivity And Qos)284

    PSTN (PSTN Fallback). 9.8.1 Alternative Routing Mechanism When a Tel IP call is routed through the Mediant 1000 gateway, the call’s destination number is compared to the list of prefixes defined in the Tel to IP Routing table (described in Section 5.5.4.2...

  • Page 285: Determining The Availability Of Destination Ip Addresses

    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 286: Mapping Pstn Release Cause To Sip Response

    Mediant 1000 sends SIP response (to IP) according to the parameter ‘DefaultReleaseCause’. This parameter defines Q.931 release causes.

  • Page 287: Table 9-2: Supported Cdr Fields

    SIP User's Manual 9. Telephony Capabilities Table 9-2: 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) SourceIp...

  • Page 288: Supported Radius Attributes

    9.11 Supported RADIUS Attributes Table 9-3 below for explanations on the RADIUS attributes contained in the communication packets transmitted between the Mediant 1000 and a RADIUS Server. Table 9-3: Supported RADIUS Attributes (continues on pages 288 to 289) Attribute Attribute...

  • Page 289: 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 String type on which the call is Asynchrono Type Stop Acc active Response Attributes...

  • Page 290: Trunk-To-Trunk Routing Example

    9.12 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 291: Proxy Or Registrar Registration Example

    SIP User's Manual 9. Telephony Capabilities 9.13 Proxy or Registrar Registration Example The REGISTER message is sent to the Registrar’s IP address (if configured) or to the Proxy’s IP address. The message is sent per gateway or per gateway endpoint according to the ‘AuthenticationMode’...

  • Page 292: Configuration Examples

    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 293: Sip Call Flow

    SIP User's Manual 9. Telephony Capabilities 9.14.2 SIP Call Flow The following Call Flow describes SIP messages exchanged between two Mediant 1000 gateways during simple call. Phone ‘6000’ dials ‘2000’, sending INVITE message to Gateway 10.8.201.161 Figure 9-6: SIP Call Flow 10.8.201.158...

  • Page 294: Mediant 1000

    F2 10.8.201.161 ==> 10.8.201.158 180 RINGING SIP/2.0 180 Ringing Via: SIP/2.0/UDP 10.8.201.158;branch=z9hG4bKacolwbzYF From: <sip:2000@10.8.201.158>;tag=1c3535 To: <sip:6000@10.8.201.161>;tag=1c29715 Call-ID: 2123353775377NrpL-2000--6000@10.8.201.158 Server: Audiocodes-Sip-Gateway/Mediant 1000/v.4.20.299.410 CSeq: 20214 INVITE Supported: 100rel,em Content-Length: 0 Note: Phone ‘2000’ answers the call, and sends 200 OK message to gateway 10.8.201.158.

  • Page 295: Sip Authentication Example

    Content-Length: 0 9.14.3 SIP Authentication Example Mediant 1000 gateways support basic and digest (MD5) authentication types, according to SIP RFC 3261 standard. A proxy server might require authentication before forwarding an INVITE message. A Registrar/Proxy server may also require authentication for client registration.
  • Page 296 Since the algorithm used is MD5, take: The username is equal to the endpoint phone number: 122 The realm return by the proxy: audiocodes.com The password from the ini file: AudioCodes. The equation to be evaluated: (according to RFC this part is called A1).

  • Page 297: Remote Ip Extension Between Fxo And Fxs

    9.14.4 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 298: Dialing From Other Pbx Line, Or From Pstn

    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 299: Fxo Mediant 1000 Configuration (Using The Embedded Web Server)

    In the ‘Tel to IP Routing’ screen, enter 10 in the ‘Destination Phone Prefix’ field, and the IP address of the FXS Mediant 1000 gateway (10.1.10.3) in the field ‘IP Address’. In the ‘Protocol Management’ screen, set the parameter ‘...
  • Page 300 Mediant 1000 Reader's Notes SIP User's Manual Document #: LTRT-83301...

  • Page 301: Networking Capabilities

    SIP User's Manual 10. Networking Capabilities Networking Capabilities 10.1 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 302: 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 303: Stun

    SIP User's Manual 10. Networking Capabilities To solve these problems the following mechanisms are available: STUN (refer to Section 10.3.1 below). First Incoming Packet Mechanism (refer to Section 10.3.2 on page 304) RTP / T.38 No-Op packets according to the avt-rtp-noop draft (refer to Section 10.3.3 on page 304).

  • Page 304: Document #: Ltrt-83301 Mediant

    Mediant 1000 10.3.2 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 305: Point-To-Point Protocol Over Ethernet (Pppoe)

    SIP User's Manual 10. Networking Capabilities 10.4 Point-to-Point Protocol over Ethernet (PPPoE) PPPoE is a method of sending the Point-to-Point Protocol over Ethernet network. 10.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.

  • Page 306: Pppoe Overview

    Further information on the transmission of PPPoE is available on the IETF website (http://www.ietf.org/rfc/rfc2516.txt). 10.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.

  • Page 307: Ip Multicasting

    SIP User's Manual 10. Networking Capabilities 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. This done using...

  • Page 308: 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 309: December

    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 10.10.3 on page 311.

  • Page 310: Table 10-1: Traffic / Network Types And Priority (Continues On Pages 312 To 312)

    Mediant 1000 For the mapping of an application to its class-of-service and traffic type, refer to Table 10-1 below. 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’...

  • Page 311: Operation

    10.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 10.10.3.1) and ini file (refer to...

  • Page 312: Integrating Using The Embedded Web Server

    Use the Software Upgrade Wizard (Section 5.8.1 on page 191) 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 313: Figure 10-3: Example Of The Ip Settings Screen

    SIP User's Manual 10. Networking Capabilities Figure 10-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 314: Integrating Using The Ini File

    414) 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 315: 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 316: 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 317: 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 318: Working With Dms-100 Switches

    ;B-Channel NFAS trunk DchConfig_3 = 2 ;B-channel NFAS trunk 11.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 11-1: Calling Name (Display) DMS-100 NI-2...

  • Page 319: Advanced System Capabilities

    Advanced System Capabilities 12.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 320: Automatic Update Mechanism

    12.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 321: Figure 12-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 322 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 323: Startup Process

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

  • Page 324: Figure 12-3: Mediant 1000 Startup Process

    Mediant 1000 Figure 12-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 325: Using Parameter Tables

    12. Advanced System Capabilities 12.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 326: Table Permissions

    Mediant 1000 12.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 327: Using The Ini File To Configure Parameter Tables

    SIP User's Manual 12. Advanced System Capabilities 12.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 328: Customizing The Mediant 1000 Web Interface

    Customers incorporating the Mediant 1000 into their portfolios can customize the Web Interface to suit their specific corporate logo and product naming conventions. Customers can customize the Web Interface’s title bar (AudioCodes’ title bar is shown in Figure 12-5; a customized title bar is shown in Figure 12-7).

  • Page 329: Replacing The Main Corporate Logo

    (refer to Section 12.6.1.2 on page 331). 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 191) disappear.

  • Page 330: Table 12-3: Customizable Logo Ini File Parameters

    Note: The length of the name of the image file is limited to 47 characters. LogoWidth Width (in pixels) of the logo image. Note: The optimal setting depends on the resolution settings. The default value is 441 which is the width of AudioCodes’ displayed logo. SIP User's Manual Document #: LTRT-83301...

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

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

  • Page 332: Customizing The Product Name

    12.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 12-6...

  • Page 333: Figure 12-8: Ini Parameters Screen

    SIP User's Manual 12. Advanced System Capabilities Figure 12-8: INI Parameters Screen From the 'Parameter Name' drop-down list, select the required ini file parameter. In the 'Enter Value' field, enter the parameter’s new value. Click the Apply new value button to the right; the INI Parameters screen is refreshed, the parameter name with the new value appears in the fields at the top of the screen and the Output Window displays a log displaying information on the operation.

  • Page 334: 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 335: Loading The Software Upgrade Key Using The Embedded Web Server

    SIP User's Manual 12. Advanced System Capabilities 12.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 336: Loading The Software Upgrade Key Using Bootp/Tftp

    Mediant 1000 When loading a Software Upgrade Key text file containing multiple S/N lines to a device (refer to Figure 12-10): In the 'Send “Upgrade Key” file from your computer to the device' field, click the Browse button, and then navigate to the Software Upgrade Key text file.

  • Page 337: 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 338 Mediant 1000 Reader's Notes SIP User's Manual Document #: LTRT-83301...

  • Page 339: Special Applications

    13. Special Applications Special Applications 13.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 13-1 below. Figure 13-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 340: Tdm Tunneling

    13.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 341: Figure 13-3: 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 342: Qsig Tunneling

    13.3 QSIG Tunneling The Mediant 1000 supports QSIG tunneling over SIP according to <draft-elwell-sipping- qsig-tunnel-03>. This method enables all QSIG messages to be sent as raw data in corresponding SIP messages using a dedicated message body. This mechanism is useful for two QSIG subscribers (connected to the same / different QSIG PBX) to communicate with each other over an IP network.

  • Page 343: Security

    SIP User's Manual 14. 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 344: Ipsec

    Mediant 1000 The IKE negotiation is separated into two phases: main mode and quick mode. The main mode employs the Diffie-Hellman (DH) protocol to obtain an encryption key (without any prior keys), and uses a pre-shared key to authenticate the peers. The created channel secures the messages of the following phase (quick mode) in which the IPSec SA properties are negotiated.

  • Page 345: Configuring Ipsec And Ike

    SIP User's Manual 14. Security 14.1.3 Configuring IPSec and IKE To enable IPSec and IKE on the gateway set the ini file parameter ‘EnableIPSec’ to 1. 14.1.3.1 IKE Configuration The parameters described in Table 14-1 below are used to configure the first phase (main mode) of the IKE negotiation for a specific peer.

  • Page 346: Table 14-2: Default Ike First Phase Proposals

    Mediant 1000 Table 14-1: IKE Table Configuration Parameters (continues on pages 345 to 346) Parameter Name Description IKE SA LifeTime (sec) Determines the time (in seconds) the SA negotiated in the first IKE session [IKEPolicyLifeInSec] (main mode) is valid. After the time expires, the SA is re-negotiated.

  • Page 347: Figure 14-3: Ike Table Screen

    SIP User's Manual 14. Security To configure the IKE table using the Embedded Web Server, take these 6 steps: Access the Embedded Web Server (refer to Section on page 57). Open the ‘IKE Table’ screen (Advanced Configuration menu > Security Settings > IKE Table option);...

  • Page 348: Ipsec Configuration

    Mediant 1000 14.1.3.2 IPSec Configuration The parameters described in Table 14-3 below are used to configure the SPD table. A different set of parameters can be configured for each of the 20 available IP destinations. Table 14-3: SPD Table Configuration Parameters (continues on pages 348 to 349)

  • Page 349: Table 14-4: Default Ike Second Phase Proposals

    SIP User's Manual 14. Security Table 14-3: SPD Table Configuration Parameters (continues on pages 348 to 349) Parameter Name Description First to Fourth Proposal Determines the authentication protocol used in the quick mode negotiation for Authentication Type up to four proposals. [IPSecPolicyProposalAuthent X stands for the proposal number (0 to 3).

  • Page 350: Figure 14-5: Ipsec Table Screen

    Mediant 1000 To configure the SPD table using the Embedded Web Server, take these 6 steps: Access the Embedded Web Server (refer to Section on page 57). Open the ‘IPSec Table’ screen (Advanced Configuration menu > Security Settings > IPSec Table option); the ‘IPSec Table’ screen is displayed.

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

    [\IPSEC_SPD_TABLE] 14.2 SSL/TLS SSL, also known as TLS, is the method used to secure the Mediant 1000 SIP Signaling connections, Embedded Web Server and Telnet server. The SSL protocol provides confidentiality, integrity and authenticity between two communicating applications over TCP/IP.

  • Page 352: Sip Over Tls (Sips)

    The Mediant 1000 uses TLS over TCP to encrypt SIP transport and (optionally) to authenticate it. To enable TLS on the Mediant 1000, set the selected transport type to TLS (SIPTransportType = 2). In this mode the gateway initiates a TLS connection only for the next network hop.

  • Page 353: Secured Telnet

    14.2.4 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 354: Figure 14-9: Certificate Signing Request Screen

    Mediant 1000 Figure 14-9: Certificate Signing Request Screen In the Subject Name field, enter the DNS name and click Generate CSR. A textual certificate signing request, that contains the SSL device identifier, is displayed. Copy this text and send it to your security provider; the security provider (also known as Certification Authority or CA) signs this request and send you a server certificate for the device.

  • Page 355: 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 356: Srtp

    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 357: Radius Login Authentication

    SIP User's Manual 14. Security 14.4 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 358: Configuring Radius Support

    ID=35. Figure 14-13: 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 359 SIP User's Manual 14. Security 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 360: Internal Firewall

    Mediant 1000 14.5 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 Only allow traffic from known friendly sources, and block all others...

  • Page 361: Figure 14-16: Advanced Example Of An Access List Definition Via Ini File

    SIP User's Manual 14. Security Figure 14-16 shows an advanced example of an access list definition via ini file: Figure 14-16: 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 362: Network Port Usage

    Mediant 1000 14.6 Network Port Usage The following table lists the default TCP/UDP network port numbers used by the Mediant 1000. Where relevant, the table lists the ini file parameters that control the port usage and provide source IP address filtering capabilities.

  • Page 363: Recommended Practices

    Mediant 1000. 14.8 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 364 Mediant 1000 Reader's Notes SIP User's Manual Document #: LTRT-83301...

  • Page 365: 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 366: Mediant 1000 Line Testing

    15.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 367: Syslog Servers

    IP sender address, time, date, etc. 15.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 368 Mediant 1000 Reader's Notes SIP User's Manual Document #: LTRT-83301...

  • Page 369: 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 370: 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 371: Carrier Grade Alarm System

    SIP User's Manual 16. 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 372: Cold Start Trap

    Mediant 1000 16.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 373: Total Counters

    16.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 374 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 375 SIP User's Manual 16. 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 376: Traps

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

  • Page 377: Snmp Interface Details

    SIP User's Manual 16. SNMP-Based Management Table 16-1: Proprietary Traps Description (continues on pages 376 to 377) 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 378: Configuration Of Community Strings Via The Web

    Mediant 1000 16.7.1.1 Configuration of Community Strings via the Web For detailed information on configuration the community strings via the Embedded Web Server, refer to Section 5.6.8.2 on page 181. 16.7.1.2 Configuration of Community Strings via the ini File The following ini file parameters are used to configure community strings: SNMPReadOnlyCommunityString_<x>...
  • Page 379 SIP User's Manual 16. SNMP-Based Management To change the only read-write community string from v2admin to v2mgr, take these 4 steps: Follow the procedure above to add a read-write community string to a row for v2mgr. Set up the EM so that subsequent ‘set’ requests use the new community string, v2mgr.

  • Page 380: Snmp V3 Usm Users

    Mediant 1000 16.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 381: Configuring Snmp V3 Users Via Snmp

    SIP User's Manual 16. SNMP-Based Management The following example configuration creates three SNMPv3 USM users: [ SNMPUsers ] FORMAT SNMPUsers_Index = SNMPUsers_Username, SNMPUsers_AuthProtocol, SNMPUsers_PrivProtocol, SNMPUsers_AuthKey, SNMPUsers_PrivKey, SNMPUsers_Group; SNMPUsers 0 = v3user, 0, 0, -, -, 0; SNMPUsers 1 = v3admin1, 1, 0, myauthkey, -, 1; SNMPUsers 2 = v3admin2, 2, 1, myauthkey, myprivkey, 1;...

  • Page 382: Trusted Managers

    Mediant 1000 To add a read-write, authPriv SNMPv3 user (v3user), take these 4 steps: Clone the row with the same security level. Change the authentication key and privacy key. Activate the row. That is, set the row status to active(1).

  • Page 383: Configuration Of Trusted Managers Via Snmp

    SIP User's Manual 16. SNMP-Based Management 16.7.3.2 Configuration of Trusted Managers via SNMP To configure Trusted Managers, the EM must use the SNMP-COMMUNITY-MIB, the snmpTargetMIB and the snmpTargetMIB. The procedure below assumes that there is at least one configured read-write community, are currently no Trusted Managers, and the TransportTag for columns for all snmpCommunityTable rows are currently empty.

  • Page 384: Snmp Ports

    Mediant 1000 The procedure below assumes that there is at least one configured read-write community, currently only one Trusted Manager, and the taglist for columns for all rows in the snmpCommunityTable are currently set to MGR. This procedure must be done from thefinal Trusted Manager.

  • Page 385: Configuring Trap Managers Via The Ini File

    16. SNMP-Based Management 16.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 386: Configuring Trap Managers Via Snmp

    Mediant 1000 configure trap manger host name, parameter SNMPTrapManagerHostName. For example: ;SNMPTrapManagerHostName = 'myMananger.corp.MyCompany.com’ Note: The same information configurable in the ini file can also be configured via the acBoardMIB. 16.7.5.3 Configuring Trap Managers via SNMP The standard snmpTargetMIB interface is available for configuring trap managers.

  • Page 387: Snmp Manager Backward Compatibility

    SIP User's Manual 16. SNMP-Based Management You can change the IP address and/or port number of an existing trap destination. The same effect can be achieved by removing a row and adding a new row. To modify a trap destination, take this step: Modify the IP address and/or port number for the appropriate row in the snmpTargetAddrTable.

  • Page 388: Snmp Nat Traversal

    Mediant 1000 16.10 SNMP NAT Traversal A NAT placed between the gateway and the element manager calls for traversal solutions: Trap source port: all traps are sent out from the SNMP port (default 161). A manager receiving these traps can use the binding information (in the UDP layer) to traverse the NAT back to the device.

  • Page 389: Snmp Administrative State Control

    SIP User's Manual 16. SNMP-Based Management 16.11 SNMP Administrative State Control 16.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 390: 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 391: Configuration Files

    430. Note: Only the dat file can be loaded to the Mediant 1000 gateway. 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 196) or the ini file (refer to Section 5.8.2.2...

  • Page 392: Figure 17-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 393: Figure 17-2: Defining A Dial Tone Example

    SIP User's Manual 17. 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 394: Format Of The Distinctive Ringing Section In The Ini File

    Mediant 1000 17.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 395: Examples Of Various Ringing Signals

    CPT file. 17.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.

  • Page 396: Cas Protocol Configuration Files

    The current file supports US line type of 600 ohm AC impedance and40 V RMS ringing voltage for REN = 2. To load the coeff.dat file to the Mediant 1000, use the Embedded Web Server (refer to Section 5.8.2 on page 196) or alternatively specify the FXS coeff.dat file name in the...

  • Page 397: User Information File

    17.5 User Information File The User Information file maps PBX extensions (connected to the Mediant 1000 gateway) to global IP phone numbers (alphanumerical). In this context, a global IP number serves as a routing identifier for calls in the ‘IP World’. The PBX extension uses this mapping to emulate the behavior of an IP phone.
  • Page 398 Mediant 1000 Reader's Notes SIP User's Manual Document #: LTRT-83301...

  • Page 399: A Selected Technical Specifications

    SIP User's Manual A. Selected Technical Specifications Selected Technical Specifications Table A-1: Mediant 1000 Functional Specifications (continues on pages 399 to 402) 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 400 Mediant 1000 Table A-1: Mediant 1000 Functional Specifications (continues on pages 399 to 402) 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 401 SIP User's Manual A. Selected Technical Specifications Table A-1: Mediant 1000 Functional Specifications (continues on pages 399 to 402) Protocols VoIP Signaling Protocol SIP RFC 3261 RTP/RTCP packetization. Communication IP stack (UDP, TCP, and RTP). Protocols Remote Software load (TFTP, HTTP and HTTPS).
  • Page 402 Mediant 1000 Table A-1: Mediant 1000 Functional Specifications (continues on pages 399 to 402) Management Configuration Gateway configuration using Web browser, CLI or ini files SNMP v2c, SNMP v3 Syslog, per RFC 3164 Management and Local RS-232 terminal Maintenance Web Management via HTTP or HTTPS...

  • Page 403: B Supplied Sip Software Kit

    B. Supplied SIP Software Kit Supplied SIP Software Kit Table B-1 describes the standard supplied software kit for Mediant 1000. The supplied documentation includes this User’s Manual, the Mediant 1000 MEGACO-H.323-SIP Fast Track Guide and the Mediant 1000 SIP Release Notes.
  • Page 404 Mediant 1000 Reader’s Notes SIP User's Manual Document #: LTRT-83301...

  • Page 405: Csip Compliance Tables

    SIP User's Manual C. SIP Compliance Tables SIP Compliance Tables The gateway complies with RFC 3261, as shown in the following sections. SIP Functions Table C-1: SIP Functions Function Supported User Agent Client (UAC) User Agent Server (UAS) Proxy Server Third-party only (verified with Ubiquity, Delta3, Microsoft, 3Com, BroadSoft, Snom and Cisco Proxies amongst others) Redirect Server...

  • Page 406: Sip Headers

    Mediant 1000 SIP Headers The following SIP Headers are supported by the gateway: Table C-3: SIP Headers (continues on pages 406 to 407) Header Field Supported Accept Accept–Encoding Alert-Info Allow Also Asserted-Identity Authorization Call-ID Call-Info Contact Content-Disposition Content-Encoding Content-Length Content-Type...

  • Page 407: Sdp Headers

    SIP User's Manual C. SIP Compliance Tables Table C-3: SIP Headers (continues on pages 406 to 407) Header Field Supported Response- Key Retry- After Route Rseq Session-Expires Server SIP-If-Match Subject Supported Timestamp Unsupported User- Agent Voicemail Warning WWW- Authenticate SDP Headers The following SDP Headers are supported by the gateway: Table C-4: SDP Headers SDP Header Element...

  • Page 408: Sip Responses

    Mediant 1000 SIP Responses The following SIP responses are supported by the gateway: 1xx Response - Information Responses 2xx Response - Successful Responses 3xx Response - Redirection Responses 4xx Response - Client Failure Responses 5xx Response - Server Failure Responses 6xx Response - Global Responses C.5.1...

  • Page 409: 3Xx Response - Redirection Responses

    SIP User's Manual C. SIP Compliance Tables C.5.3 3xx Response – Redirection Responses Table C-7: 3xx SIP Responses 3xx Response Supported Comments Multiple Choice The gateway responds with an ACK and resends the request to first in the contact list, new address. Moved The gateway responds with an ACK and resends the request to Permanently...
  • Page 410 Mediant 1000 Table C-8: 4xx SIP Responses (continues on pages 409 to 410) 4xx Response Supported Comments Conflict gateway does not generate this response. On reception of this message, before a 200OK has been received, the gateway responds with an ACK and disconnects the call.

  • Page 411: 5Xx Response - Server Failure Responses

    SIP User's Manual C. SIP Compliance Tables C.5.5 5xx Response – Server Failure Responses Table C-9: 5xx SIP Responses 5xx Response Comments Internal Server Error Not Implemented On reception of any of these Responses, the GW releases the call, sending appropriate release cause gateway to PSTN side.
  • Page 412 Mediant 1000 Reader's Notes SIP User's Manual Document #: LTRT-83301...

  • Page 413: D Bootp/Tftp Configuration Utility

    SIP User's Manual D. 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 414: 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 415: Bootp/Tftp Application User Interface

    SIP User's Manual D. BootP/TFTP Configuration Utility BootP/TFTP Application User Interface Figure D-1 shows the main application screen for the BootP/TFTP utility. Figure D-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 416: Log Window

    Mediant 1000 Figure D-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 417: Setting The Preferences

    SIP User's Manual D. BootP/TFTP Configuration Utility View Client: Selecting this option, or double clicking on the line in the log window, opens the Client Configuration window. If the MAC address indicated on the line exists in the client database, it is highlighted. If the address is not in the client database, a new client is added with the MAC address filled out.

  • Page 418: Tftp Preferences

    Mediant 1000 ARP Manipulation Enabled: Enable ARP Manipulation to remotely reset a gateway that does not yet have a valid IP address. If ARP Manipulation is enabled, the following two commands are available. • Reply Type: Reply to a BootRequest can be either Broadcast or Unicast. The default for the BootP Tool is Broadcast.

  • Page 419: Configuring The Bootp Clients

    SIP User's Manual D. BootP/TFTP Configuration Utility D.11 Configuring the BootP Clients The Clients window, shown in Figure D-4 below, is used to set up the parameters for each specific VoIP gateway. Figure D-4: Client Configuration Screen D.11.1 Adding Clients Adding a client creates an entry in the BootP Tool for a specific gateway.

  • Page 420: Deleting Clients

    Mediant 1000 To add a client to the list using a template, take these 5 steps: Click the Add New Client icon ; a client with blank parameters is displayed. In the field Template, located on the right side of the Client Configuration Window, click on the down arrow to the right of the entry field and select the template that you want to use.

  • Page 421: Setting Client Parameters

    SIP User's Manual D. BootP/TFTP Configuration Utility Examine the Log Window on the Main Application Screen. If there is another BootP utility that supports this client MAC, there is a response indicated from that utility showing the status Listed At along with the IP address of that utility. If there is another utility responding to this client, you must remove that client from either this utility or the other one.

  • Page 422: 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 423: Table D-1: Command Line Switch Descriptions

    SIP User's Manual D. BootP/TFTP Configuration Utility Table D-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 424: Managing Client Templates

    Mediant 1000 D.12 Managing Client Templates Templates can be used to simplify configuration of clients when most of the parameters are the same. Figure D-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 425: Ertp/Rtcp Payload Types And Port Allocation

    SIP User's Manual E. 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 426: 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. Table E-3: Default RTP/RTCP/T.38 Port Allocation Channel Number RTP Port RTCP Port T.38 Port 6000 6001 6002 6010 6011 6012 6020 6021 6022 6030 6031...

  • Page 427: Frtp Control Protocol Extended Reports (Rtcp-Xr)

    SIP User's Manual F. RTP Control Protocol Extended Reports (RTCP-XR) RTP Control Protocol Extended Reports (RTCP-XR) RTP Control Protocol Extended Reports (RTCP-XR) is a VoIP management control that defines a set of metrics containing information for assessing VoIP call quality and diagnosing problems.
  • Page 428 Mediant 1000 Table F-1: RTCP-XR Published VoIP Metrics (continues on pages 427 to 428) Metric Name Burst Gap Loss Burst Loss Density Burst Duration Gap Loss Density Gap Duration Minimum Gap Threshold Delay Round Trip Delay End System Delay One Way Delay...

  • Page 429: G Accessory Programs And Tools

    SIP User's Manual G. 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 430: Converting A Cpt Ini File To A Binary Dat File

    Mediant 1000 G.1.1 Converting a CPT ini File to a Binary dat File For detailed information on creating a CPT ini file, refer to Section 17.1 on page 391. 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 431: Creating A Loadable Cas Protocol Table File

    SIP User's Manual G. Accessory Programs and Tools G.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 432: 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 433: Creating A Loadable Prerecorded Tones File

    SIP User's Manual G. 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 434: Figure G-5: Prerecorded Tones Screen

    Mediant 1000 Figure G-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 435: 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 436: Initial Settings

    Execute the CPTWizard.exe file; the wizard’s initial settings screen is displayed. Figure G-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 437: Recording Screen - Automatic Mode

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

  • Page 438: Figure G-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 439: Recording Screen - Manual Mode

    SIP User's Manual G. Accessory Programs and Tools G.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 440: The Call Progress Tones Ini File

    Mediant 1000 G.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 441: 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 442: 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 443: Figure G-14: Trunk Traces

    SIP User's Manual G. Accessory Programs and Tools Figure G-14: Trunk Traces Figure G-15: UDP2File Utility Version 5.0 December 2006...
  • Page 444 Mediant 1000 Reader's Notes SIP User's Manual Document #: LTRT-83301...

  • Page 445: H Release Reason Mapping

    SIP User's Manual H. Release Reason Mapping Release Reason Mapping This appendix describes the available mapping mechanisms of SIP Responses to Q.850 Release Causes and vice versa. Table H-1 Table H-2 describe the existing mapping of ISDN Release Causes to SIP Responses.

  • Page 446: Fixed Mapping Of Isdn Release Reason To Sip Response

    Mediant 1000 Fixed Mapping of ISDN Release Reason to SIP Response Table H-1 below describes the mapping of ISDN release reason to SIP response. Table H-1: Mapping of ISDN Release Reason to SIP Response (continues on pages 446 to 447)
  • Page 447 SIP User's Manual H. Release Reason Mapping Table H-1: Mapping of ISDN Release Reason to SIP Response (continues on pages 446 to 447) ISDN Release Description Description Reason Response Facility not subscribed 503* Service unavailable Incoming calls barred within CUG Forbidden Bearer capability not authorized Forbidden...

  • Page 448: Fixed Mapping Of Sip Response To Isdn Release Reason

    Mediant 1000 Fixed Mapping of SIP Response to ISDN Release Reason Table H-2 below describes the mapping of SIP response to ISDN release reason. Table H-2: Mapping of SIP Response to ISDN Release Reason (continues on pages 448 to 449)
  • Page 449 SIP User's Manual H. Release Reason Mapping Table H-2: Mapping of SIP Response to ISDN Release Reason (continues on pages 448 to 449) ISDN Release Description Description Response Reason Server timeout Recovery on timer expiry 505* Version not supported Interworking Busy everywhere User busy Decline...
  • Page 450 Mediant 1000 Reader's Notes SIP User's Manual Document #: LTRT-83301...

  • Page 451: Snmp Traps

    SIP User's Manual I. 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 452: Table I-2: Acboardconfigurationerror Alarm Trap

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

  • Page 453: Table I-4: Acboardevresettingboard Alarm Trap

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

  • Page 454: Table I-7: Acboardcontrollerfailurealarm Alarm Trap

    Mediant 1000 Table I-7: acBoardControllerFailureAlarm Alarm Trap Alarm: acBoardControllerFailureAlarm OID: 1.3.6.1.4.1.5003.9.10.1.21.2.0.9 Default Severity: Minor Event Type: processingErrorAlarm Probable Cause: softwareError (46) 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 455: Table I-9: Acgwadminstatechange Alarm Trap

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

  • Page 456: Component: Alarmmanager#0

    Mediant 1000 I.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 I-11: acActiveAlarmTableOverflow Alarm Trap Alarm: acActiveAlarmTableOverflow OID: 1.3.6.1.4.15003.9.10.1.21.2.0.12 Default Severity: Major Event Type: processingErrorAlarm Probable Cause:...

  • Page 457: Component: Ethernetlink#0

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

  • Page 458: Log Traps (Notifications)

    Mediant 1000 I.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 459: Other Traps

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

  • Page 460: Trap Varbinds

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

  • Page 461: J Installation And Configuration Of Apache Http Server

    SIP User's Manual J. 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 Note: For detailed installation information, refer to http://perl.apache.org/docs/2.0/os/win32/config.html.

  • Page 462: 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 463 SIP User's Manual J. 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 464 Mediant 1000 Reader's Notes SIP User's Manual Document #: LTRT-83301...

  • Page 465: Kosn 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 Module (CM) iPMX Hard Drive Module (HDMX)

  • Page 466: Figure K-2: Ipmx Module

    Mediant 1000 Figure K-2: iPMX Module Figure K-3: Hard Drive (HDMX) Module SIP User's Manual Document #: LTRT-83301...

  • Page 467: Figure K-4: Mediant 1000 Front Panel View

    SIP User's Manual K. 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 K-4. Using a Phillips screwdriver, remove the black metal cover plate from the slot below...

  • Page 468: Figure K-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 K-6. Figure K-6: Mediant 1000 Rear Panel View Remove the black metal cover plates in the first and second slots located on the right...

  • Page 469: Figure K-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 K-8. Figure K-8: Mediant 1000 With Cutter Tool Insert the iPMX module in the first slot, closest to the power connection, as shown in Figure K-9.

  • Page 470: Figure K-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 K-6 Remove the black metal cover plates in the first and second slots located on the right...

  • Page 471: 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 472: 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 473: 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 474: Figure L-4: Iso Screen

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

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

    SIP User's Manual L. Linux™ Operating System Installation for the OSN Server L.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 L-5: Selecting Extract Option Extract the isolinux.cfg file to the Partner Install folder created in Stage 1.

  • Page 476: Figure L-7: Iso-Extract Screen

    Mediant 1000 Click Extract; a screen opens containing the extracted isolinux folder. Figure L-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 L-8: Text Edit screen...
  • Page 477 SIP User's Manual L. 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 478: Figure L-9: Deleting Cfg

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

  • Page 479: Stage 3: Burn The Cd

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

  • Page 480: Stage 4: Installation

    Mediant 1000 L.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 481: 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 482: 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). L.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 483: Stage 2: Preparing The Boot Media

    SIP User's Manual L. Linux™ Operating System Installation for the OSN Server The .iso file starts being created. Figure L-15: Creating .iso file L.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 484: Stage 3: Editing The Isolinux.cfg File

    Figure L-18: Extracting to Partner Install folder L.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 L.6.3.1, or edit it using the steps detailed in Section L.6.3.2.

  • Page 485: Editing The Isolinux.cfg File

    SIP User's Manual L. Linux™ Operating System Installation for the OSN Server L.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 486: Figure L-19: Deleting Cfg

    Mediant 1000 F7 f7.txt F8 f8.txt F9 f9.txt F0 f10.txt Note: If the timeout line does not exist, do not add it.1. If you want to install '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 487: Stage 4: Burn The Cd

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

  • Page 488: Stage 5: Installation

    Mediant 1000 L.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 489 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 490: 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). L.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 491: Stage 2: Preparing The Boot Media

    SIP User's Manual L. 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 L-23: Create ISO from CD-ROM The .iso file begins being created. Figure L-24: Creating .iso file L.7.3 Stage 2: Preparing the Boot Media...

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

    L.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 L.7.4.1, or edit it using the steps detailed in Section L.7.4.2. L.7.4.1 Downloading an updated SUSE isolinux.cfg file To download an updated SUSE isolinux.cfg file from the...

  • Page 493: Editing The Isolinux.cfg File

    SIP User's Manual L. Linux™ Operating System Installation for the OSN Server L.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 494 Mediant 1000 Add the following parameters to the 'append' line: text console=ttyS0,115200. Note: In the above string, 'ttyS0,115200' consists of a capital 'S', only zeros and one comma. The following examples show how the 'label linux' line and its kernel & append...

  • Page 495: Figure L-29: Deleting Cfg

    SIP User's Manual L. 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 496: Stage 4: Burn The Cd

    Mediant 1000 Navigate to the Partner Install folder, select the isolinux.cfg file, and then click Open. Figure L-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 497: Stage 5: Installation

    L. Linux™ Operating System Installation for the OSN Server L.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™...
  • Page 498 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 499: M 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 500: Document #: Ltrt-83301 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 501 SIP User's Manual M. Regulatory Information (Digital Interface) Reader's Notes Version 5.0 December 2006...
  • Page 502 ™ Mediant™ Media Gateways Mediant 1000 User’s Manual Version 5.0 http://www.audiocodes.com/...

Table of Contents