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

AudioCodes Mediant 1000 User Manual

Voice-over-ip (voip) 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
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
Table of Contents

Advertisement

Quick Links

See also: Troubleshooting Manual , User Manual
User's Manual
Version 5.4
Document #: LTRT-83303
May 2008

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 User's Manual Version 5.4 Document #: LTRT-83303 May 2008...

  • Page 3: Table Of Contents

    SIP User's Manual Contents Table of Contents Overview ......................19 Mediant 1000 ......................19 Mediant 600 ......................20 SIP Overview ......................21 Configuration Concepts ...................23 Web-Based Management..................25 Computer Requirements ..................25 Accessing the Web Interface ................. 26 Getting Acquainted with the Web Interface............27 3.3.1...
  • Page 4 Mediant 1000 & Mediant 600 3.4.2 Media Settings ......................80 3.4.2.1 Configuring the Voice Settings..............81 3.4.2.2 Configuring the Fax / Modem / CID Settings .......... 84 3.4.2.3 Configuring the RTP / RTCP Settings............. 88 3.4.2.4 Configuring the IPmedia Settings............92 3.4.2.5...
  • Page 5 SIP User's Manual Contents ini File Configuration ..................291 Secured Encoded ini File ..................291 The ini File Structure .................... 292 4.2.1 Structure Rules ..................... 292 4.2.2 Structure of Individual ini File Parameters............292 4.2.3 Structure of ini File Table Parameters ..............293 4.2.4 Example of an ini File ...................
  • Page 6 Mediant 1000 & Mediant 600 7.2.3 Supporting V.34 Faxes ..................404 7.2.3.1 Using Bypass Mechanism for V.34 Fax Transmission......404 7.2.3.2 Using Relay mode for both T.30 and V.34 faxes ........405 7.2.4 Supporting V.152 Implementation ................ 405 FXO Operating Modes ..................406 7.3.1...
  • Page 7 SIP User's Manual Contents Networking Capabilities..................445 Ethernet Interface Configuration ................445 Ethernet Interface Redundancy ................445 NAT (Network Address Translation) Support............446 8.3.1 STUN ........................447 8.3.2 First Incoming Packet Mechanism................ 448 8.3.3 No-Op Packets ..................... 448 IP Multicasting...................... 448 Robust Reception of RTP Streams ..............
  • Page 8 13.2.2 Stage 2: Creating the ISO Image ................. 510 13.2.3 Stage 3: Burning the CD..................514 13.2.4 Stage 4: Cabling the Mediant 1000 OSN Server..........515 13.2.5 Stage 5: Booting and Installing................515 13.2.6 Stage 6: Enabling the Firewall with Remote Desktop Access......517 13.3 Connecting Remotely to OSN Server using Windows XP ........
  • Page 9 14.5.5 Stage 4: Burning the CD..................551 14.5.6 Stage 5: Installing the Boot Media................ 552 15 Supplied SIP Software Package..............555 16 Selected Technical Specifications..............557 16.1 Mediant 1000 ....................... 557 16.2 Mediant 600 ......................561 17 Glossary......................565 Version 5.4 May 2008...
  • Page 10 Figure 3-27: Mediant 600 Home Page ....................53 Figure 3-28: Shortcut Menu (Example, Mediant 1000 Home Page) ............57 Figure 3-29: Text Box for Typing Port Name (Example, Mediant 1000 Home Page) ......57 Figure 3-30: Selecting Port Settings from Shortcut Menu..............58 Figure 3-31: Basic Information Screen....................58 Figure 3-32: Resetting Channel ......................59...
  • Page 11 SIP User's Manual Contents Figure 3-58: Web & Telnet Access List Page - Add New Entry ............114 Figure 3-59: Web & Telnet Access List Table ..................115 Figure 3-60: Firewall Settings Page ....................116 Figure 3-61: Certificates Signing Request Page ................. 119 Figure 3-62: General Security Settings Page..................
  • Page 12 Figure 12-4: Mediant 1000 Front Panel....................503 Figure 12-5: Inserting CM Module....................... 503 Figure 12-6: Mediant 1000 Rear Panel ....................504 Figure 12-7: Mediant 1000 with Cover Plates Removed..............504 Figure 12-8: Mediant 1000 with Cutter Tool ..................505 SIP User's Manual...
  • Page 13 Figure 13-16: Entering IP Address in Remote Desktop Connection ........... 521 Figure 13-17: Entering User Name and Password in Remote Desktop Connection ......521 Figure 14-1: Mediant 1000 Front Panel OSN Server Connections ............. 524 Figure 14-2: Disk 1 of Redhat Partner Installation ................526 Figure 14-3: Images Folder .........................
  • Page 14 Table 3-4: ini File Parameters for Customizing Product Name ..............51 Table 3-5: ini File Parameter for Welcome Login Message ..............51 Table 3-6: Description of the Areas of the Mediant 1000 Home Page...........54 Table 3-7: Description of the Areas of the Mediant 600 Home Page.............56 Table 3-8: Color-Coding Status for Trunk's Channels................60...
  • Page 15 Table 9-3: Calling Name (Display) ...................... 468 Table 9-4: Redirect Number ........................ 468 Table 15-1: Supplied Software Package ..................... 555 Table 16-1: Mediant 1000 Functional Specifications ................557 Table 16-2: Mediant 600 Functional Specifications ................561 Table 17-1: Glossary of Terms ......................565 Version 5.4...
  • Page 16 Mediant 1000 & Mediant 600 Reader's Notes SIP User's Manual Document #: LTRT-83303...

  • Page 17: Weee Eu Directive

    SIP User's Manual Notices Notice This document describes the AudioCodes Mediant 1000 and Mediant 600 Voice-over-IP (VoIP) SIP media gateways. 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 18: Related Documentation

    The following naming conventions are used throughout this manual, unless otherwise specified: • The term device refers to the Mediant 1000 and Mediant 600 gateways. • The term Trunk is used synonymously with Hunt. Trunk typically refers to digital modules, while Hunt typically refers to analog modules.

  • Page 19: Overview

    SIP User's Manual 1. Overview Overview This section provides an overview of the Mediant 1000 and Mediant 600 media gateways. Mediant 1000 The AudioCodes Mediant 1000 (hereafter referred to as device) is a best-of-breed Voice- over-IP (VoIP) Session Initiation Protocol (SIP) Media Gateway, using field-proven, market- leading technology, implementing analog and digital cutting-edge technology.

  • Page 20: Mediant 600

    Microsoft™ Internet Explorer™), from anywhere in the world with IP connectivity to the device. Mediant 600 AudioCodes' Mediant 600 (hereafter referred to as device) is a cost-effective, wireline Voice-over-IP (VoIP) Session Initiation Protocol (SIP)-based media gateway. It is designed to interface between Time-Division Multiplexing (TDM) and IP networks in enterprises, small and medium businesses (SMB), and CPE application service providers.

  • Page 21: Sip Overview

    SIP User's Manual 1. Overview SIP Overview Session Initiation Protocol (SIP) is an application-layer control (signaling) protocol used on the gateway for creating, modifying, and terminating sessions with one or more participants. These sessions can include Internet telephone calls, media announcements, and conferences.
  • Page 22 Mediant 1000 & Mediant 600 Reader's Notes SIP User's Manual Document #: LTRT-83303...

  • Page 23: Configuration Concepts

    Note: To initialize the device by assigning it an IP address, a firmware file (cmp), and a configuration file (ini file), you can use AudioCodes' BootP/TFTP utility, which accesses the device using its MAC address (refer to the Product Reference Manual).
  • Page 24 Mediant 1000 & Mediant 600 Reader's Notes SIP User's Manual Document #: LTRT-83303...

  • Page 25: Web-Based Management

    SIP User's Manual 3. Web-Based Management Web-Based Management The device's Embedded Web Server (Web interface) provides FCAPS (fault management, configuration, accounting, performance, and security) functionality. The Web interface allows you to remotely configure your device for quick-and-easy deployment, including uploading of configuration (software upgrade) and auxiliary files, and resetting the device. The Web interface provides real-time, online monitoring of the device, including display of alarms and their severity.

  • Page 26: Accessing The Web Interface

    Mediant 1000 & Mediant 600 Accessing the Web Interface The Web interface can be opened using any standard Web browser (refer to ''Computer Requirements'' on page 25). When initially accessing the Web interface, use the default user name ('Admin') and password ('Admin'). For changing the login user name and password, refer to ''Configuring the Web User Accounts'' on page 112).

  • Page 27: Getting Acquainted With The Web Interface

    SIP User's Manual 3. Web-Based Management Getting Acquainted with the Web Interface The figure below displays the general layout of the Graphical User Interface (GUI) of the Web interface: Figure 3-2: Main Areas of the Web Interface GUI The Web GUI is composed of the following main areas: Title bar: Displays the corporate logo and product name.

  • Page 28: Toolbar

    Mediant 1000 & Mediant 600 3.3.1 Toolbar The toolbar provides command buttons for quick-and-easy access to frequently required commands, as described in the table below: Table 3-1: Description of Toolbar Buttons Icon Button Name Description Submit Applies parameter settings to the device (refer to ''Saving Configuration'' on page 265).

  • Page 29: Navigation Tree

    SIP User's Manual 3. Web-Based Management 3.3.2 Navigation Tree The Navigation tree, located in the Navigation pane, displays the menus (pertaining to the menu tab selected on the Navigation bar) used for accessing the configuration pages. The Navigation tree displays a tree-like structure of menus. You can easily drill-down to the required page item level to open its corresponding page in the Work pane.

  • Page 30: Displaying Navigation Tree In Basic And Full View

    Mediant 1000 & Mediant 600 To navigate to a page, take these 2 steps: Navigate to the required page item, by performing the following: • Drilling-down using the plus signs to expand the menus and submenus • Drilling-up using the minus signs to collapse the menus and submenus Select the required page item;...

  • Page 31: Showing / Hiding The Navigation Pane

    SIP User's Manual 3. Web-Based Management 3.3.2.2 Showing / Hiding the Navigation Pane The Navigation pane can be hidden to provide more space for elements displayed in the Work pane. This is especially useful when the Work pane displays a page with a table that's wider than the Work pane and to view the all the columns, you need to use scroll bars.

  • Page 32: Accessing Pages

    Mediant 1000 & Mediant 600 3.3.3.1 Accessing Pages The configuration pages are accessed by clicking the required page item in the Navigation tree. To open a configuration page in the Work pane, take these 2 steps: On the Navigation bar, click the required tab: •...

  • Page 33: Figure 3-7: Toggling Between Basic And Advanced Page View

    SIP User's Manual 3. Web-Based Management 3.3.3.2.1 Displaying Basic and Advanced Parameters Some pages provide you with an Advanced Parameter List / Basic Parameter List toggle button that allows you to show or hide advanced parameters (in addition to displaying the basic parameters). This button is located on the top-right corner of the page and has two states: Advanced Parameter List button with down-pointing arrow: click this button to display all parameters.

  • Page 34: Modifying And Saving Parameters

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

  • Page 35: Figure 3-9: Editing Symbol After Modifying Parameter Value

    SIP User's Manual 3. Web-Based Management Figure 3-9: Editing Symbol after Modifying Parameter Value To save configuration changes on a page to the device's volatile memory (RAM), take this step: Click the Submit button, which is located near the bottom of the page in which you are working;...

  • Page 36: Entering Phone Numbers In Various Tables

    Mediant 1000 & Mediant 600 3.3.3.4 Entering Phone Numbers in Various Tables Phone numbers or prefixes that you enter in various tables throughout the Web interface such as the 'Tel to IP Routing' table, must only be entered as digits without any other characters.

  • Page 37: Figure 3-12: Compacting A Web Interface Table

    SIP User's Manual 3. Web-Based Management To add a copy of an existing index table entry, take these 3 steps: In the 'Index' column, select the index that you want to duplicate; the Edit button appears. Click Edit; the fields in the corresponding index row become available. Click Duplicate;...

  • Page 38: Searching For Configuration Parameters

    Mediant 1000 & Mediant 600 To delete an existing index table entry, take these 3 steps: In the 'Index' column, select the index corresponding to the table row that you want to delete. Click Delete; the table row is removed from the table.

  • Page 39: Figure 3-13: Searched Result Screen

    SIP User's Manual 3. Web-Based Management In the searched list, click the required parameter (link in green) to open the page in which the parameter appears; the relevant page opens in the Work pane and the searched parameter is highlighted for easy identification, as shown in the figure below: Figure 3-13: Searched Result Screen Note: If the searched parameter is not located, a notification message is displayed.

  • Page 40: Working With Scenarios

    Mediant 1000 & Mediant 600 3.3.5 Working with Scenarios The Web interface allows you to create your own "menu" with up to 20 pages selected from the menus in the Navigation tree (i.e., pertaining to the Configuration, Management, and Status & Diagnostics tabs). The "menu" is a set of configuration pages grouped into a logical entity referred to as a Scenario.

  • Page 41: Figure 3-15: Creating A Scenario

    SIP User's Manual 3. Web-Based Management Click the Next button located at the bottom of the page; the Step is added to the Scenario and appears in the Scenario Step list: Figure 3-15: Creating a Scenario Repeat steps 5 through 8 to add additional Steps (i.e., pages). When you have added all the required Steps for your Scenario, click the Save &...

  • Page 42: Accessing A Scenario

    Mediant 1000 & Mediant 600 3.3.5.2 Accessing a Scenario Once you have created the Scenario, you can access it at anytime by following the procedure below: To access the Scenario, take these 2 steps: On the Navigation bar, select the Scenario tab; a message box appears, requesting you to confirm the loading of the Scenario.

  • Page 43: Editing A Scenario

    SIP User's Manual 3. Web-Based Management To navigate between Scenario Steps, you can perform one of the following: In the Navigation tree, click the required Scenario Step. In an opened Scenario Step (i.e., page appears in the Work pane), use the following navigation buttons: •...

  • Page 44: Saving A Scenario To A Pc

    Mediant 1000 & Mediant 600 • Add or Remove Parameters: In the Navigation tree, select the required Step; the corresponding page opens in the Work pane. To add parameters, select the check boxes corresponding to the desired parameters; to remove parameters, clear the check boxes corresponding to the parameters that you want removed.

  • Page 45: Figure 3-18: Scenario File Page

    SIP User's Manual 3. Web-Based Management To save a Scenario to a PC, take these 5 steps: On the Navigation bar, click the Scenarios tab; the Scenario appears in the Navigation tree. Click the Get/Send Scenario File button (located at the bottom of the Navigation tree);...

  • Page 46: Loading A Scenario To The Device

    Mediant 1000 & Mediant 600 3.3.5.5 Loading a Scenario to the Device Instead of creating a Scenario, you can load a Scenario file (data file) from your PC to the device. To load a Scenario to the device, take these 4 steps: On the Navigation bar, click the Scenarios tab;...

  • Page 47: Exiting Scenario Mode

    SIP User's Manual 3. Web-Based Management Click the Delete Scenario File button; a message box appears requesting confirmation for deletion. Figure 3-20: Message Box for Confirming Scenario Deletion Click OK; the Scenario is deleted and the Scenario mode closes. Note: You can also delete a Scenario using the following alternative methods: •...

  • Page 48: Customizing The Web Interface

    The figure below shows an example of a customized Title bar. The top image displays the Title bar with AudioCodes logo and product name. The bottom image displays a customized Title bar with a different image logo and product name.

  • Page 49: Figure 3-23: Image Download Screen

    SIP User's Manual 3. Web-Based Management On the left pane, click Image Load to Device; the 'Image Download' page is displayed, as shown in the figure below: Figure 3-23: Image Download Screen Click the Browse button, and then navigate to the folder in which the logo image file that you want to use is located.

  • Page 50: Customizing The Product Name

    The corporate logo can be replaced with a text string instead of an image. To replace AudioCodes’ default logo with a text string using the ini file, configure the ini file parameters listed in the table below. (For a description on using the ini file, refer to ''Modifying an ini File'' on page 296.)

  • Page 51: Creating A Login Welcome Message

    [0] = Don’t change the product name (default). [1] = Enable product name change. The text string that replaces the product name. UserProductName The default is ‘Mediant 1000’. The string can be up to 29 characters. 3.3.6.3 Creating a Login Welcome Message You can create a Welcome message box (alert message) that appears after each successful login to the device's Web interface.

  • Page 52: Getting Help

    Mediant 1000 & Mediant 600 3.3.7 Getting Help The Web interface provides you with context-sensitive Online Help. The Online Help provides you with brief descriptions of most of the parameters you'll need to successfully configure the device. The Online Help provides descriptions of parameters pertaining to the currently opened page.

  • Page 53: Figure 3-26: Mediant 1000 Home Page

    To access the Home page, take this step: On the toolbar, click the Home icon; the 'Home' page is displayed: Figure 3-26: Mediant 1000 Home Page Figure 3-27: Mediant 600 Home Page Note: The number and type of modules, trunks and channels displayed in the 'Home' page depends on the device's hardware configuration.

  • Page 54: Table 3-6: Description Of The Areas Of The Mediant 1000 Home Page

    Mediant 1000 & Mediant 600 The table below describes the areas of the 'Home' page. Table 3-6: Description of the Areas of the Mediant 1000 Home Page Item# / Description Label Displays the highest severity of an active alarm raised (if any) by the device:...
  • Page 55 SIP User's Manual 3. Web-Based Management Item# / Description Label Port (trunk or channel) status icon (refer to Monitoring the Mediant 1000 Trunks and Channels on page 59). Icon Trunk Description Channel Description (Digital Module) (Analog Module) Disable: Trunk not configured (not in use)

  • Page 56: Table 3-7: Description Of The Areas Of The Mediant 600 Home Page

    Mediant 1000 & Mediant 600 Table 3-7: Description of the Areas of the Mediant 600 Home Page Item# / Description Label Displays the highest severity of an active alarm raised (if any) by the device: Green = No alarms Red = Critical alarm...

  • Page 57: Assigning A Name To A Port

    Figure 3-28: Shortcut Menu (Example, Mediant 1000 Home Page) From the shortcut menu, choose Update Port Info; a text box appears. Figure 3-29: Text Box for Typing Port Name (Example, Mediant 1000 Home Page) Type a brief description for the port, and then click Apply Port Info.

  • Page 58: Viewing Analog Port Information

    (analog) port such as RTP/RTCP and voice settings. Note: This section is applicable only to Mediant 1000. To view detailed port information, take these 3 steps: Click the port for which you want to view port settings; the shortcut menu appears.

  • Page 59: Resetting An Analog Channel

    In the Home page, click the desired trunk of whose status you want to view; a shortcut menu appears. From the shortcut menu, choose Port Settings; the 'Trunks & Channels Status' page pertaining to the specific trunk appears: Figure 3-33: Trunks & Channels Status Page (Example, Mediant 1000) Version 5.4 May 2008...

  • Page 60: Figure 3-34: Basic Channel Information Page (Example, Mediant 1000)

    To view information of a specific trunk's channel, in the 'Trunks & Channels Status' screen, click the required Channel icon; the 'Basic Channel Information' page appears: Figure 3-34: Basic Channel Information Page (Example, Mediant 1000) Click the buttons located above the 'Basic Channel Information' screen to view additional parameters.

  • Page 61: Replacing Modules

    (refer to Inserting Modules into Previously Empty Slots). Note: This section is applicable only to Mediant 1000. To replace a module, take these 2 steps: Remove the module by performing the following: In the 'Home' page, click the title of the module that you want to replace;...

  • Page 62: Logging Off The Web Interface

    Mediant 1000 & Mediant 600 Click OK to confirm removal; after a few seconds, the module is software- removed, the module status icon turns to grey, and the name of the module is suffixed with the word 'Reserved': Figure 3-37: Removed Module Physically remove the module (refer to the device's Fast Track Installation Guide).

  • Page 63: Figure 3-40: Web Session Logged Off

    SIP User's Manual 3. Web-Based Management Click OK; the Web session is logged off and the Log In button appears. Figure 3-40: Web Session Logged Off To log in again, simply click the Log In button, and then in the 'Enter Network Password' dialog box, enter your user name and password (refer to ''Accessing the Web Interface'' on page 26).

  • Page 64: Configuration Tab

    Mediant 1000 & Mediant 600 Configuration Tab The Configuration tab on the Navigation bar displays all menus related to device configuration. These menus appear in the Navigation tree and include the following: Network Settings (refer to ''Network Settings'' on page 64)

  • Page 65: Figure 3-41: Ip Settings Page

    SIP User's Manual 3. Web-Based Management To configure the IP settings parameters, take these 4 steps: Open the 'IP Settings' page (Configuration tab > Network Settings menu > IP Settings page item). Figure 3-41: IP Settings Page Configure the IP parameters according to the table below. Click the Submit button to save your changes.

  • Page 66: Table 3-9: Network Settings -- Ip Settings Parameters

    Mediant 1000 & Mediant 600 Table 3-9: Network Settings -- IP Settings Parameters Parameter Description IP Settings IP Networking Mode Determines the IP network scheme. [EnableMultipleIPs] [0] Single IP Network = Single IP network (default). [1] Multiple IP Networks = Multiple IP networks (OAMP, Media, and Control).
  • Page 67 SIP User's Manual 3. Web-Based Management Parameter Description Control Network Settings (Available only in Multiple IP and Dual IP modes.) IP Address The device's source IP address in the Control network. [LocalControlIPAddress] The default value is 0.0.0.0. Subnet Mask The device's subnet mask in the Control network. [LocalControlSubnetMask] The default subnet mask is 0.0.0.0.

  • Page 68: Configuring The Multiple Interface Table

    Mediant 1000 & Mediant 600 3.4.1.2 Configuring the Multiple Interface Table The 'Multiple Interface Table' page allows you to configure up to three logical network interfaces, each with its own IP address, unique VLAN ID (if enabled), interface name, and application types (i.e., Control, Media, and/or Operations, Administration, Maintenance and...

  • Page 69: Table 3-10: Multiple Interface Table Parameters Description

    SIP User's Manual 3. Web-Based Management Notes: • When adding more than one interface to the table, ensure that you enable VLANs, using the 'VLAN Mode' (VlANMode) parameter. • When booting using BootP/DHCP protocols (refer to the Product Reference Manual), an IP address is obtained from the server. This address is used as the OAMP address for this session, overriding the IP address you configured in the 'Multiple Interface Table' page.

  • Page 70: Parameter Description

    Mediant 1000 & Mediant 600 Parameter Description This column lists the number of ‘1’ bits in the subnet mask (i.e., replaces the standard dotted-decimal representation of the subnet mask for IPv4 interfaces). For example: A subnet mask of 255.0.0.0 is represented by a prefix length of 8 (i.e., 11111111 00000000 00000000 00000000), and a...

  • Page 71: Configuring The Application Settings

    SIP User's Manual 3. Web-Based Management 3.4.1.3 Configuring the Application Settings The 'Application Settings' page is used for configuring various application parameters such as Telnet. To configure the Application settings parameters, take these 4 steps: Open the 'Application Settings' page (Configuration tab > Network Settings menu > Application Settings page item).

  • Page 72: Table 3-11: Application Settings Parameters

    [NTPUpdateInterval] a time update. The default interval is 86400 (i.e., 24 hours). The range is 0 to 214783647. Note: AudioCodes does not recommend setting this parameter to beyond one month (i.e., 2592000 seconds). Telnet Settings Embedded Telnet Server Enables or disables the device's embedded Telnet server. Telnet is [TelnetServerEnable] disabled by default for security reasons.
  • Page 73 SIP User's Manual 3. Web-Based Management Parameter Description STUN is used to discover whether the device is located behind a NAT and the type of NAT. In addition, it is used to determine the IP addresses and port numbers that the NAT assigns to outgoing signaling messages (using SIP) and media streams (using RTP, RTCP and T.38).

  • Page 74: Configuring The Nfs Settings

    Mediant 1000 & Mediant 600 3.4.1.4 Configuring the NFS Settings Network File System (NFS) enables the device to access a remote server's shared files and directories, and to handle them as if they're located locally. You can configure up to five different NFS file systems.

  • Page 75: Configuring The Ip Routing Table

    SIP User's Manual 3. Web-Based Management Table 3-12: Network Settings -- NFS Settings Parameters Parameter Description The row index of the remote file system. Index The valid range is 0 to 4. The domain name or IP address of the NFS server. If a domain name is HostOrIP provided, a DNS server must be configured.

  • Page 76: Figure 3-46: Ip Routing Table Page

    Mediant 1000 & Mediant 600 To configure static IP routing, take these 3 steps: Open the 'IP Routing Table' page (Configuration tab > Network Settings menu > IP Routing Table page item). Figure 3-46: IP Routing Table Page In the 'Add a new table entry' group, add a new static routing rule according to the parameters described in the table below.
  • Page 77 SIP User's Manual 3. Web-Based Management Column Name Description [ini File Parameter Name] Gateway IP Address The IP address of the router (next hop) to which the packets are [RoutingTableGatewaysColum sent if their destination matches the rules in the adjacent columns. Note: The Gateway address must be in the same subnet on which the address is configured on the 'Multiple Interface Table' page (refer to ''Configuring the Multiple Interface Table'' on page 68).

  • Page 78: Configuring The Qos Settings

    Mediant 1000 & Mediant 600 3.4.1.6 Configuring the QoS Settings The 'QoS Settings' page is used for configuring the Quality of Service (QoS) parameters. This page allows you to assign VLAN priorities (IEEE 802.1p) and Differentiated Services (DiffServ) for the supported Class of Service (CoS).
  • Page 79 SIP User's Manual 3. Web-Based Management Parameter Description Bronze Priority Defines the priority for the Bronze CoS content. [VLANBronzeServiceClass The valid range is 0 to 7. The default value is 2. Priority] Differential Services (For detailed information on IP QoS using Differentiated Services, refer to ''IP QoS via Differentiated Services (DiffServ)'' on page 450).

  • Page 80: Mediant 1000 & Mediant

    Mediant 1000 & Mediant 600 3.4.2 Media Settings The Media Settings menu allows you to configure the device's channel parameters. These parameters are applied to all the device's channels. This menu contains the following page items: Voice Settings (refer to ''Configuring the Voice Settings'' on page 81)

  • Page 81: Configuring The Voice Settings

    SIP User's Manual 3. Web-Based Management 3.4.2.1 Configuring the Voice Settings The 'Voice Settings' page is used for configuring various voice parameters such as voice volume. To configure the Voice parameters, take these 4 steps: Open the 'Voice Settings' page (Configuration tab > Media Settings menu > Voice Settings page item).
  • Page 82 Mediant 1000 & Mediant 600 Parameter Description Silence Suppression Silence Suppression is a method for conserving bandwidth on VoIP [EnableSilenceCompression calls by not sending packets when silence is detected. [0] Disable = Silence Suppression is disabled (default). [1] Enable = Silence Suppression is enabled.
  • Page 83 SIP User's Manual 3. Web-Based Management Parameter Description Answer Detector Sensitivity Determines the Answer Detector sensitivity. [AnswerDetectorSensitivity] The range is 0 (most sensitive) to 2 (least sensitive). The default is 0. CAS Transport Type Controls the ABCD signaling transport type over IP. [CASTransportType] [0] CAS Events Only = Disable CAS relay (default).

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

    Mediant 1000 & Mediant 600 3.4.2.2 Configuring the Fax / Modem / CID Settings The 'Fax/Modem/CID Settings' page is used for configuring fax, modem, and Caller ID (CID) parameters. To configure the fax, modem, and CID parameters, take these 4 steps: Open the 'Fax/Modem/CID Settings' page (Configuration tab >...
  • Page 85 [18] India [19] Brazil Notes: This parameter is applicable only to Mediant 1000. Typically, the Caller ID signals are generated/detected between the first and second rings. However, sometimes the Caller ID is detected before the first ring signal. In such a scenario, configure RingsBeforeCallerID to Caller ID detection for Britain [4] is not supported on the device’s FXO...
  • Page 86 Mediant 1000 & Mediant 600 Parameter Description V.23 Modem Transport V.23 Modem Transport Type used by the device. Type [0] Disable = Disable (Transparent) [V23ModemTransportT [1] Enable Relay = N/A ype] [2] Enable Bypass = (default) [3] Events Only = Transparent with Events V.32 Modem Transport...
  • Page 87 SIP User's Manual 3. Web-Based Management Parameter Description Fax/Modem Bypass Coder used by the device when performing fax/modem bypass. Usually, Coder Type high-bit-rate coders such as G.711 should be used. [FaxModemBypassCo [0] G.711Alaw= G.711 A-law 64 (default). derType] [1] G.711Mulaw = G.711 µ-law. Fax/Modem Bypass Number of (20 msec) coder payloads that are used to generate a Packing Factor...

  • Page 88: Configuring The Rtp / Rtcp Settings

    Mediant 1000 & Mediant 600 3.4.2.3 Configuring the RTP / RTCP Settings The 'RTP/RTCP Settings' page allows you to configure the Real-Time Transport Protocol (RTP) and Real-Time Transport (RTP) Control Protocol (RTCP) parameters. To configure the RTP / RTCP parameters, take these 4 steps: Open the 'RTP/RTCP Settings' page (Configuration tab >...

  • Page 89: Table 3-17: Media Settings, Rtp / Rtcp Parameters

    SIP User's Manual 3. Web-Based Management Table 3-17: Media Settings, RTP / RTCP Parameters Parameter Description Dynamic Jitter Buffer Minimum Minimum delay (in msec) for the Dynamic Jitter Buffer. Delay The valid range is 0 to 150. The default delay is 10. [DJBufMinDelay] Note: For more information on Jitter Buffer, refer to ''Dynamic Jitter Buffer Operation'' on page 414.
  • Page 90 [0] Ignore Analog Signals = Ignore (default) [1] RFC2833 Analog Signal Relay = Transfer hookflash via RFC 2833 Note: This parameter is applicable only to Mediant 1000. RTP Base UDP Port Lower boundary of UDP port used for RTP, RTCP (RTP port + 1) and T.38 (RTP port + 2).
  • Page 91 SIP User's Manual 3. Web-Based Management Parameter Description RTP Multiplexing Local UDP Port Determines the local UDP port used for outgoing multiplexed RTP [L1L1ComplexTxUDPPort] packets (applies to RTP multiplexing). The valid range is the range of possible UDP ports: 6,000 to 64,000.

  • Page 92: Configuring The Ipmedia Settings

    Mediant 1000 & Mediant 600 3.4.2.4 Configuring the IPmedia Settings The 'IPMedia Settings' page allows you to configure the IP media parameters. To configure the IP media parameters, take these 4 steps: Open the 'IPMedia Settings' page (Configuration tab > Media Settings menu >...

  • Page 93: Configuring The General Media Settings

    SIP User's Manual 3. Web-Based Management Parameter Description Answer Detector Redirection N/A. [AnswerDetectorRedirection] Answer Detector Sensitivity Determines the Answer Detector sensitivity. [AnswerDetectorSensitivity] The range is 0 (most sensitive) to 2 (least sensitive). The default is Enable Energy Detector [EnableEnergyDetector] Energy Detector Quality Factor [EnergyDetectorQualityFactor] Energy Detector Threshold [EnergyDetectorThreshold]...

  • Page 94: Configuring The Hook-Flash Settings

    [11] = 64 msec [22] = 128 msec Notes: Mediant 1000 with analog / BRI module can use a max. echo canceller length of 64 msec. Mediant 1000 with PRI can use a max. echo canceller length of 128 msec.

  • Page 95: Table 3-20: Hook-Flash Settings Parameters

    SIP User's Manual 3. Web-Based Management Table 3-20: Hook-Flash Settings Parameters Parameter Description Min. Flash-Hook Detection Period Defines the minimum time (in msec) for detection of a hook-flash [msec] event. [MinFlashHookTime] The valid range is 25 to 300. The default value is 300. Detection is guaranteed for hook-flash periods of at least 60 msec (when setting the minimum time to 25).

  • Page 96: Pstn Settings

    Mediant 1000 & Mediant 600 3.4.3 PSTN Settings The PSTN Settings menu allows you to configure various PSTN settings and includes the following page items: Trunk Settings (refer to ''Configuring the Trunk Settings'' on page 96) CAS State Machines (refer to ''Configuring the CAS State Machines'' on page 109) 3.4.3.1...

  • Page 97: Figure 3-55: Trunk Scroll Bar

    SIP User's Manual 3. Web-Based Management On the top of the page, a bar with Trunk number icons displays the status of each trunk, according to the following color codes: • Grey: Disabled • Green: Active • Yellow: RAI alarm •...

  • Page 98: Table 3-21: Trunk (E1/T1/J1/Bri) Configuration Parameters

    Mediant 1000 & Mediant 600 Click Apply Trunk Settings to apply the changes to the selected trunk (or click Apply to all Trunks to apply the changes to all trunks); the Stop Trunk button replaces Apply Trunk Settings and the ‘Trunk Configuration State’ displays 'Active'.
  • Page 99 SIP User's Manual 3. Web-Based Management ini File Field Name Valid Range and Description Web Parameter Name [19] E1 KOR ISDN = Korean operator [20] T1 HKT ISDN = Hong Kong - HKT over T1 [21] E1 QSIG [23] T1 QSIG [31] E1 FRENCH VN3 ISDN [35] T1 DMS100 Meridian ISDN [40] E1 NI2 ISDN...
  • Page 100 Mediant 1000 & Mediant 600 ini File Field Name Valid Range and Description Web Parameter Name Line Build Out Loss Defines the line build out loss for the selected T1 trunk. [LineBuildOut.Loss] [0] 0 dB (default) [1] -7.5 dB [2] -15 dB [3] -22.5 dB...
  • Page 101 SIP User's Manual 3. Web-Based Management ini File Field Name Valid Range and Description Web Parameter Name BRI Layer 2 Mode Determines whether Point-to-Point or Point-to-Multipoint mode for BRI [BriLayer2Mode] ports. [0] Point to Point (default) [1] Point to Multipoint = Must be configured for Network side. NFAS Group Number Indicates the NFAS group number (NFAS member) for the selected [NFASGroupNumber_x]...
  • Page 102 Mediant 1000 & Mediant 600 ini File Field Name Valid Range and Description Web Parameter Name Enable Receiving of Enables Rx ISDN overlap per trunk ID. Overlap Dialing [0] Disable = Disabled (default). [ISDNRxOverlap_x] [1] Enable = Enabled. Notes: If enabled, the device receives ISDN called number that is sent in the 'Overlap' mode.
  • Page 103 SIP User's Manual 3. Web-Based Management ini File Field Name Valid Range and Description Web Parameter Name ISDN Transfer Capabilities Defines the IP-to-ISDN Transfer Capability of the Bearer Capability IE in [ISDNTransferCapability_ ISDN SETUP messages. The ID in the ini file parameter depicts the trunk number.
  • Page 104 Mediant 1000 & Mediant 600 ini File Field Name Valid Range and Description Web Parameter Name the D-channel. Note: Applicable to 4/5ESS, DMS and NI-2 variants. [32768] ACCEPT MU LAW =Mu-Law is also accepted in ETSI. [65536] EXPLICIT PRES SCREENING = The calling party number (octet 3a) is always present even when presentation and screening are at their default.
  • Page 105 SIP User's Manual 3. Web-Based Management ini File Field Name Valid Range and Description Web Parameter Name indicates an unused channel ID, preferred only. [572] USE A LAW = When set, the device sends G.711 A-Law in outgoing voice calls. When disabled, the device sends the default G.711-Law in outgoing voice calls.
  • Page 106 Mediant 1000 & Mediant 600 ini File Field Name Valid Range and Description Web Parameter Name [8] REVERSE CHAN ALLOC ALGO = Channel ID allocation algorithm. [16] = The device clears down the call if it receives a NOTIFY message specifying 'User-Suspended'. A NOTIFY (User-Suspended) message is used by some networks (e.g., in Italy or Denmark) to...
  • Page 107 SIP User's Manual 3. Web-Based Management ini File Field Name Valid Range and Description Web Parameter Name ''E1/T1 Configuration Parameters'' on page 344. This parameter is not applicable to BRI interfaces. Dial Plan The Dial Plan name that is used on a specific trunk. [CasTrunkDialPlanName] The range is up to 11 character strings.
  • Page 108 Mediant 1000 & Mediant 600 ini File Field Name Valid Range and Description Web Parameter Name 1) If the device receives a 180 Ringing response (with or without SDP) and LocalISDNRBSource = 1, it plays an RBT and sends an Alert with PI = 8 (unless the parameter ProgressIndicator2ISDN_ID is configured differently).

  • Page 109: Configuring The Cas State Machines

    SIP User's Manual 3. Web-Based Management ini File Field Name Valid Range and Description Web Parameter Name RTP Only Mode Enables the device to start sending and/or receiving RTP packets to and [RTPOnlyModeForTrunk_ from remote endpoints without the need to establish a Control session. The remote IP address is determined according to the 'Tel to IP Routing' table.

  • Page 110: Figure 3-56: Cas State Machine Page

    Mediant 1000 & Mediant 600 To modify the CAS state machine parameters, take these 6 steps: Open the ‘CAS State Machine' page (Configuration tab > PSTN Settings menu > CAS State Machines page item). Figure 3-56: CAS State Machine Page Ensure that the trunk is inactive.

  • Page 111: Security Settings

    SIP User's Manual 3. Web-Based Management Table 3-22: CAS State Machine Parameters Description Parameter Description Generate Digit On Time Generates digit on-time (in msec). [CasStateMachineGenerateD The value must be a positive value. The default value is -1. igitOnTime] Generate Inter Digit Time Generates digit off-time (in msec).

  • Page 112: Configuring The Web User Accounts

    Mediant 1000 & Mediant 600 Certificates (refer to ''Configuring the Certificates'' on page 118) General Security Settings (refer to ''Configuring the General Security Settings'' on page 123) IPSec Table (refer to ''Configuring the IPSec Table'' on page 126) IKE Table (refer to ''Configuring the IKE Table'' on page 130) 3.4.4.1...

  • Page 113: Figure 3-57: Web User Accounts Page (For Users With 'Security Administrator' Privileges)

    SIP User's Manual 3. Web-Based Management To change the Web user accounts attributes, take these 4 steps: Open the 'Web User Accounts' page (Configuration tab > Security Settings menu > Web User Accounts page item). Figure 3-57: Web User Accounts Page (for Users with 'Security Administrator' Privileges) To change the access level of the secondary account (the access level of the primary account cannot be changed), from the 'Access Level' drop-down list, select the new access level, and then click Change Access Level;...

  • Page 114: Configuring The Web And Telnet Access List

    Mediant 1000 & Mediant 600 Notes: • For security, it's recommended that you change the default user name and password used for initially accessing the Web interface. • The access level of the primary Web user account is 'Security Administrator', which cannot be modified; all its' other account-attributes can be modified.

  • Page 115: Figure 3-59: Web & Telnet Access List Table

    SIP User's Manual 3. Web-Based Management To add an authorized IP address, in the 'Add a New Authorized IP Address' field, enter the required IP address, and then click Add New Address; the IP address you entered is added as a new entry to the 'Web & Telnet Access List' table. Figure 3-59: Web &...

  • Page 116: Configuring The Firewall Settings

    Mediant 1000 & Mediant 600 3.4.4.3 Configuring the Firewall Settings The device provides an internal firewall, allowing you (the security administrator) to define network traffic filtering rules. You can add up to 50 ordered firewall rules. For each packet received on the network interface, the table is scanned from the top down until a matching rule is found.

  • Page 117: Table 3-25: Internal Firewall Parameters

    SIP User's Manual 3. Web-Based Management To edit a rule, take these 4 steps: In the 'Edit Rule' column, select the rule that you want to edit. Modify the fields as desired. Click the Apply button to save the changes. To save the changes to flash memory, refer to ''Saving Configuration'' on page 265.

  • Page 118: Configuring The Certificates

    Mediant 1000 & Mediant 600 Parameter Description Packet Size Maximum allowed packet size. [AccessList_Packet_Size] The valid range is 0 to 65535. Note: When filtering fragmented IP packets, this field relates to the overall (re-assembled) packet size, and not to the size of each fragment.

  • Page 119: Figure 3-61: Certificates Signing Request

    SIP User's Manual 3. Web-Based Management To replace the device's self-signed certificate, take these 8 steps: Your network administrator should allocate a unique DNS name for the device (e.g., dns_name.corp.customer.com). This name is used to access the device, and should therefore be listed in the server certificate.
  • Page 120 Mediant 1000 & Mediant 600 In the 'Certificates Files' group, click the Browse button corresponding to 'Send Server Certificate...', navigate to the cert.txt file, and then click Send File. When the loading of the certificate is completed, save the configuration (refer to ''Saving Configuration'' on page 265) and restart the device;...
  • Page 121 SIP User's Manual 3. Web-Based Management When a user connects to the secured Web server: If the user has a client certificate from a CA that is listed in the Trusted Root Certificate file, the connection is accepted and the user is prompted for the system password. If both the CA certificate and the client certificate appear in the Trusted Root Certificate file, the user is not prompted for a password (thus, providing a single-sign- on experience - the authentication is performed using the X.509 digital signature).
  • Page 122 Mediant 1000 & Mediant 600 To export the current server certificate to a file using Microsoft Internet Explorer, take these 6 steps: Access the device's Web interface. Double-click the yellow padlock icon displayed at the bottom of the Browser's window.

  • Page 123: Configuring The General Security Settings

    SIP User's Manual 3. Web-Based Management 3.4.4.5 Configuring the General Security Settings The 'General Security Settings' page is used to configure various security features. To configure the general security parameters, take these 4 steps: Open the 'General Security Settings' page (Configuration tab > Security Settings menu >...

  • Page 124: Table 3-26: General Security Parameters

    The default value is 12345. For detailed information on the voice menu, refer to the device's Fast Track Guide. Note: This parameter is applicable only to Mediant 1000. General RADIUS Settings Enable RADIUS Access Determines whether the RADIUS application is enabled.
  • Page 125 SIP User's Manual 3. Web-Based Management Parameter Description RADIUS Authentication Server IP Address IP address of the RADIUS authentication server. [RADIUSAuthServerIP] RADIUS Authentication Server Port number of the RADIUS authentication server. Port The default value is 1645. [RADIUSAuthPort] RADIUS Shared Secret 'Secret' used to authenticate the device to the RADIUS server.

  • Page 126: Configuring The Ipsec Table

    Mediant 1000 & Mediant 600 Parameter Description SRTP Setting Media Security Enables Secure Real-Time Transport Protocol (SRTP). [EnableMediaSecurity] [0] Disable = SRTP is disabled (default). [1] Enable = SRTP is enabled. Media Security Behavior Determines the device's mode of operation when SRTP is used [MediaSecurityBehaviour] (EnableMediaSecurity = 1).

  • Page 127: Figure 3-63: Ipsec Table

    SIP User's Manual 3. Web-Based Management To configure the IPSec SPD table, take these 5 steps: Open the ‘IPSec Table’ page (Configuration tab > Security Settings menu > IPSec Table page item). Figure 3-63: IPSec Table Page From the ‘Policy Index’ drop-down list, select the rule you want to edit (up to 20 policy rules can be configured).

  • Page 128: Table 3-28: Ipsec Spd Table Configuration Parameters

    Mediant 1000 & Mediant 600 Table 3-28: IPSec SPD Table Configuration Parameters Parameter Name Description IPSec Mode Defines the IPSec mode of operation. [IPSecMode] [0] Transport (Default) [1] Tunneling Remote Tunnel IP Address Defines the IP address of the remote IPSec [IPSecPolicyRemoteTunne tunneling device.
  • Page 129 SIP User's Manual 3. Web-Based Management Parameter Name Description IKE Second Phase Parameters (Quick Mode) SA Lifetime (sec) Determines the time (in seconds) that the SA negotiated in the second [PsecPolicyLifeInSec] IKE session (quick mode) is valid. After the time expires, the SA is re- negotiated.

  • Page 130: Configuring The Ike Table

    Mediant 1000 & Mediant 600 3.4.4.7 Configuring the IKE Table The 'IKE Table' page is used to configure the Internet Key Exchange (IKE) parameters. Note: You can also configure the IKE table using the ini file table parameter IPSec_IKEDB_Table (refer to ''Security Parameters'' on page 314).

  • Page 131: Table 3-29: Default Ike First Phase Proposals

    SIP User's Manual 3. Web-Based Management If no IKE methods are defined (Encryption / Authentication / DH Group), the default settings (shown in the following table) are applied. Table 3-29: Default IKE First Phase Proposals Proposal Encryption Authentication DH Group Proposal 0 3DES SHA1...
  • Page 132 Mediant 1000 & Mediant 600 Parameter Name Description IKE SA LifeTime (KB) Determines the lifetime (in kilobytes) that the SA negotiated in the first IKE session (main mode) is valid. After this size is reached, the SA is re-negotiated. The default value is 0 (i.e., this parameter is ignored).

  • Page 133: Protocol Configuration

    SIP User's Manual 3. Web-Based Management 3.4.5 Protocol Configuration The Protocol Configuration menu allows you to configure the device's SIP parameters and contains the following submenus: Protocol Definition (refer to ''Configuring the Protocol Definition Parameters'' on page 133) SIP Advanced Parameters (refer to ''Configuring the SIP Advanced Parameters'' on page 165) Manipulation Tables (refer to ''Configuring the Number Manipulation Tables'' on page 190)

  • Page 134: Figure 3-65: Sip General Parameters

    Mediant 1000 & Mediant 600 3.4.5.1.1 SIP General Parameters The 'SIP General Parameters' page is used to configure general SIP parameters. To configure the general SIP protocol parameters, take these 4 steps: Open the 'SIP General Parameters' page (Configuration tab > Protocol Configuration menu >...

  • Page 135: Table 3-31: Sip General Parameters (Protocol Definition)

    SIP User's Manual 3. Web-Based Management Configure the parameters according to the table below. Click the Submit button to save your changes. To save the changes to flash memory, refer to ''Saving Configuration'' on page 265. Table 3-31: SIP General Parameters (Protocol Definition) Parameter Description PRACK Mode...
  • Page 136 [0] Disable = Early Media is disabled (default). [1] Enable = Enables Early Media. For Mediant 1000 Analog interface: Note that to send a 183 response, you must also set the parameter ProgressIndicator2IP to 1. If it is equal to 0, 180 Ringing response is sent.
  • Page 137 SIP User's Manual 3. Web-Based Management Parameter Description 183 Message Behavior Defines the ISDN message that is sent when the 183 Session Progress [SIP183Behaviour] message is received for IP-to-Tel calls. [0] Progress = The device sends a PROGRESS message (default). [1] Alert = The device sends an ALERT message (upon receipt of a 183 response) instead of an ISDN PROGRESS message.
  • Page 138 Mediant 1000 & Mediant 600 Parameter Description Fax Signaling Method Determines the SIP signaling method for establishing and transmitting a [IsFaxUsed] fax session after a fax is detected. [0] No Fax = No fax negotiation using SIP signaling. Fax transport method is according to the parameter FaxTransportMode (default).
  • Page 139 SIP User's Manual 3. Web-Based Management Parameter Description SIP TCP Local Port Local TCP port for SIP messages. [TCPLocalSIPPort] The valid range is 1 to 65534. The default value is 5060. SIP TLS Local Port Local TLS port for SIP messages. [TLSLocalSIPPort] The valid range is 1 to 65534.
  • Page 140 Mediant 1000 & Mediant 600 Parameter Description Add Number Plan and Determines whether the TON/PLAN parameters are included in the Type to Remote Party ID Remote-Party-ID (RPID) header. Header [0] No [AddTON2RPI] [1] Yes (default) If RPID header is enabled (EnableRPIHeader = 1) and AddTON2RPI = 1, it's possible to configure the calling and called number type and number plan using the Number Manipulation tables for Tel-to-IP calls.
  • Page 141 SIP User's Manual 3. Web-Based Management Parameter Description Use Source Number as Determines the use of Tel Source Number and Display Name for Tel-to-IP Display Name calls. [UseSourceNumberAsD [0] No = If a Tel Display Name is received, the Tel Source Number is isplayName] used as the IP Source Number and the Tel Display Name is used as the IP Display Name.
  • Page 142 180+SDP response, signaling to the calling party to open a voice channel to hear the played ringback tone. Notes: This parameter is applicable only to Mediant 1000 FXS interfaces. To enable the device to send a 183/180+SDP responses, set EnableEarlyMedia to 1.
  • Page 143 Defines the string that is used in the SIP request header User-Agent and [UserAgentDisplayInfo] SIP 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/v.5.40.010.006). When configured, the string 'UserAgentDisplayInfo s/w-version' is used (e.g., User-Agent: MyNewOEM/v.5.40.010.006).
  • Page 144 Mediant 1000 & Mediant 600 Parameter Description Play Busy Tone to Tel Enables the device to play a busy or reorder tone to the PSTN after a Tel- [PlayBusyTone2ISDN] to-IP call is released. [0] Don't Play = Immediately sends an ISDN Disconnect message (default).
  • Page 145 SIP User's Manual 3. Web-Based Management Parameter Description Enable VoiceMail URI Enables or disables the interworking of target and cause for redirection [EnableVMURI] from Tel to IP and vice versa, according to RFC 4468. [0] Disable = Disable (default). [1] Enable = Enable Upon receipt of an ISDN SETUP message with redirect values, the device maps the Redirect phone number to the SIP 'target' parameter and the Redirect number reason to the SIP 'cause' parameter in the Request-URI.
  • Page 146 Mediant 1000 & Mediant 600 Parameter Description SIP Maximum RTX Maximum number of UDP transmissions (first transmission plus [SIPMaxRtx] retransmissions) of SIP messages. The range is 1 to 30. The default value is 7. 3.4.5.1.2 Proxy & Registration Parameters The 'Proxy & Registration' page allows you to configure parameters that are associated with Proxy and Registration.

  • Page 147: Table 3-32: Proxy & Registration Parameters

    SIP User's Manual 3. Web-Based Management Table 3-32: Proxy & Registration Parameters Parameter Description Use Default Proxy Enables the use of a SIP Proxy server. [IsProxyUsed] [0] Don't Use Proxy = Proxy isn't used - the internal routing table is used instead (default).
  • Page 148 Mediant 1000 & Mediant 600 Parameter Description Prefer Routing Table Determines if the 'Tel to IP Routing' table takes precedence over a Proxy for [PreferRouteTable] routing calls. [0] No = Only Proxy is used to route calls (default). [1] Yes = The device checks the 'Dest Phone Prefix' and/or 'Source Phone Prefix' fields in the 'Tel to IP Routing' table for a match with the Tel-to-IP call.
  • Page 149 SIP User's Manual 3. Web-Based Management Parameter Description Registrar Transport Determines the transport layer used for outgoing SIP dialogs initiated by the Type device to the Registrar. [RegistrarTransportT [-1] Not Configured (default) ype] [0] UDP [1] TCP [2] TLS Note: When set to ‘Not Configured’, the value of the parameter SIPTransportType is used.
  • Page 150 Mediant 1000 & Mediant 600 Parameter Description Registration Time Defines a threshold (in seconds) for re-registration timing. If this parameter is Threshold greater than 0, but lower than the computed re-registration timing (according [RegistrationTimeThr to the parameter RegistrationTimeDivider), the re-registration timing is set to...
  • Page 151 Determines the method the device uses to subscribe to an MWI server. [SubscriptionMode] [0] Per Endpoint = Each endpoint subscribes separately - typically used for Mediant 1000 FXS interfaces (default). [1] Per Gateway = Single subscription for the entire device - typically used for Mediant 1000 FXO interfaces.
  • Page 152 Notes: Applicable only if single device registration is used (i.e., Authentication Mode is set to Authentication Per gateway). For Mediant 1000: The Authentication table can be used instead (refer to Authentication on page 219). Password The password used for Basic/Digest authentication with a Proxy / Registrar server.
  • Page 153 SIP User's Manual 3. Web-Based Management Parameter Description Challenge Caching Determines the mode for Challenge Caching, which reduces the number of Mode SIP messages transmitted through the network. The first request to the Proxy [SIPChallengeCachin is sent without authorization. The Proxy sends a 401/407 response with a gMode] challenge.

  • Page 154: Figure 3-66: Proxy Sets Table

    Mediant 1000 & Mediant 600 To add Proxy servers and configure Proxy parameters, take these 5 steps: Open the 'Proxy Sets Table' page (Configuration tab > Protocol Configuration menu > Protocol Definition submenu > Proxy Sets Table page item). Figure 3-66: Proxy Sets Table Page From the Proxy Set ID drop-down list, select an ID for the desired group.
  • Page 155 SIP User's Manual 3. Web-Based Management Parameter Description To summarize, if the default Proxy Set is used, the INVITE message is sent according to the following preferences: To the Trunk Group's ServingIPGroupID, as defined in the 'Trunk Group Settings' table. According to the 'Tel to IP Routing' table, if the parameter PreferRouteTable is set to 1.
  • Page 156 Mediant 1000 & Mediant 600 Parameter Description Proxy Load Balancing Enables the Proxy Load Balancing mechanism per Proxy Set ID. Method [0] Disable = Load Balancing is disabled (default). [ProxyLoadBalancing [1] Round Robin = Round Robin. Method] [2] Random Weights = Random Weights.
  • Page 157 SIP User's Manual 3. Web-Based Management Parameter Description Proxy Keep Alive Time Defines the Proxy keep-alive time interval (in seconds) between Keep-Alive [ProxyKeepAliveTime] messages. This parameter is configured per Proxy Set. The valid range is 5 to 2,000,000. The default value is 60. Note: This parameter is applicable only if the parameter EnableProxyKeepAlive is set to 1 (OPTIONS).

  • Page 158: Table 3-34: Supported Coders

    Mediant 1000 & Mediant 600 The coders supported by the device are listed in the table below: Table 3-34: Supported Coders Coder Name Packetization Time Rate Payload Type Silence Suppression Disable [0] • G.711 A-law 10, 20 (default), 30, Always 64...

  • Page 159: Figure 3-67: Coders

    SIP User's Manual 3. Web-Based Management To configure the device's coders, take these 9 steps: Open the 'Coders' page (Configuration tab > Protocol Configuration menu > Protocol Definition submenu > Coders page item). Figure 3-67: Coders Page From the 'Coder Name' drop-down list, select the coder you want to use. For the full list of available coders and their corresponding attributes, refer to the table below.

  • Page 160: Figure 3-68: Dtmf & Dialing

    Mediant 1000 & Mediant 600 3.4.5.1.5 DTMF & Dialing Parameters The 'DTMF & Dialing' page is used to configure parameters associated with dual-tone multi-frequency (DTMF) and dialing. To configure the DTMF and dialing parameters, take these 4 steps: Open the 'DTMF & Dialing' page (Configuration tab > Protocol Configuration menu >...

  • Page 161: Table 3-35: Dtmf And Dialing Parameters

    (ISDN uses overlap dialing). When the number of collected digits reaches the maximum, the device uses these digits for the called destination number. The valid range is 1 to 49. The default value is 5 for Mediant 1000 analog and 30 for digital. Notes: Digit Mapping Rules can be used instead.
  • Page 162 Mediant 1000 & Mediant 600 Parameter Description to 5 Tx DTMF Option Determines a single or several preferred transmit DTMF negotiation [TxDTMFOption] methods. [0] Not Supported = No negotiation - DTMF digits are sent according to the parameters DTMFTransportType and RFC2833PayloadType (default).
  • Page 163 [5] INFO (Lucent) = Send proprietary INFO message with Hook-Flash indication. Notes: This parameter is applicable only to Mediant 1000. The RFC 2833 (4) option is currently not supported by digital interfaces. The DTMF HookFlashCode is send to IP according to the parameter HookFlashOption for digital interfaces.
  • Page 164 [HotLineToneDuration] (refer to Automatic Dialing on page 220). The valid range is 0 to 60. The default is 16. Note: This parameter is applicable only to Mediant 1000 for both FXS and FXO interfaces. Enable Special Digits Determines whether the asterisk (*) and pound (#) digits can be used.

  • Page 165: Configuring The Sip Advanced Parameters

    SIP User's Manual 3. Web-Based Management 3.4.5.2 Configuring the SIP Advanced Parameters The SIP Advanced Parameters submenu allows you to configure advanced SIP control protocol parameters. This submenu contains the following page items: Advanced Parameters (refer to ''General Parameters'' on page 166) Supplementary Services (refer to ''Supplementary Services'' on page 176) Metering Tones (refer to "Metering Tones"...

  • Page 166: Figure 3-69: Advanced Parameters

    Mediant 1000 & Mediant 600 3.4.5.2.1 Advanced Parameters The 'Advanced Parameters' page allows you to configure general control protocol parameters. To configure the advanced general protocol parameters, take these 4 steps: Open the 'Advanced Parameters' page (Configuration tab > Protocol Configuration menu >...

  • Page 167: Table 3-36: Advanced Parameters Description

    SIP User's Manual 3. Web-Based Management Configure the parameters according to the table below. Click the Submit button to save your changes. To save the changes to flash memory, refer to ''Saving Configuration'' on page 265. Table 3-36: Advanced Parameters Description Parameter Description General...
  • Page 168 ('p') and plays the rest of the number (100) as DTMF digits. Additional examples: 1664wpp102, 66644ppp503, and 7774w100pp200. Notes for Mediant 1000 analog interfaces: The called number can include characters 'p' (1.5 seconds pause) and 'd' (detection of dial tone). If character 'd' is used, it must be the first 'digit' in the called number.
  • Page 169 Tel side (IP-to-Tel call establishment) and a CONNECT message is received. If an ALERTING message is received, the timer is restarted. For Mediant 1000 Analog: Alert Timeout (in seconds) for calls to the Tel side. This timer is used between the time ring is generated (FXS) or line is seized (FXO) until the call is connected.
  • Page 170 (applicable only to one-stage dialing) and releases a call when a second polarity reversal signal is detected. Note: This parameter is applicable only to Mediant 1000. Enable Current Disconnect Enables call release upon detection of a current disconnect signal.
  • Page 171 SIP User's Manual 3. Web-Based Management Parameter Description Disconnect Call on Silence Determines whether calls are disconnected after detection of silence. Detection [1] Yes = The device disconnects calls in which silence occurs (in [EnableSilenceDisconnec both call directions) for more than a user-defined time. [0] No = Call is not disconnected when silence is detected (default).
  • Page 172 Note: Usually set to 5 if debug traces are needed. Misc. Parameters Progress Indicator to IP For Mediant 1000 Analog (FXS/FXO) interfaces: [ProgressIndicator2IP] [0] No PI = For Tel-to-IP calls, the device sends 180 Ringing SIP response to IP after placing a call to a phone (FXS) or PBX (FXO).
  • Page 173 When Busy Out is enabled and certain scenarios exist, the device performs the following: Mediant 1000 Analog interface: A reorder tone (determined by FXSOOSBehavior) is played when the phone is off-hooked. Digital interface: All E1/T1 trunks are automatically taken out of service...
  • Page 174 Mediant 1000 & Mediant 600 Parameter Description Default Release Cause Default Release Cause (to IP) for IP-to-Tel calls when the device initiates [DefaultReleaseCause] a call release and an explicit matching cause for this release isn't found. The default release cause is NO_ROUTE_TO_DESTINATION (3).
  • Page 175 The waiting call is automatically answered by the device when the current call is terminated (configured by setting the parameter EnableCallWaiting to 1). Note: This option is applicable only to Mediant 1000 FXS interfaces. Enable User-Information Enables or disables usage of the User Information loaded to the device Usage in the User Information auxiliary file.

  • Page 176: Figure 3-70: Supplementary Services

    Mediant 1000 & Mediant 600 3.4.5.2.2 Supplementary Services The 'Supplementary Services' page is used to configure parameters that are associated with supplementary services. For detailed information on supplementary services, refer to ''Working with Supplementary Services'' on page 437. To configure the supplementary services' parameters, take these 4 steps: Open the 'Supplementary Services' page (Configuration tab >...

  • Page 177: Table 3-37: Supplementary Services Parameters

    [0] Disable = Disables. [1] Enable = Enables (default). For Mediant 1000 analog: If the Hold service is enabled, a user can place the call on hold (or remove from hold) using the hook-flash. On receiving a Hold request, the remote party is placed on hold and hears the hold tone.
  • Page 178 [0] Disable = Disable the Call Waiting service. [1] Enable = Enable the Call Waiting service (default). If enabled, when an FXS interface (only Mediant 1000) receives a call on a busy endpoint, it responds with a 182 response (and not with a 486 busy).
  • Page 179 For information on the Caller ID table, refer to "Caller ID" on page 221. To disable/enable caller ID generation per port, refer to "Call Forward" on page 222. Note: This parameter is applicable only to Mediant 1000. Caller ID Type Defines one of the following standards for detection (FXO) and generation...
  • Page 180 Mediant 1000 & Mediant 600 Parameter Description Message Waiting Indication (MWI) Parameters Note: MWI is applicable only to Mediant 1000. Enable MWI Enables Message Waiting Indication (MWI). [EnableMWI] [0] Disable = Disabled (default). [1] Enable = MWI service is enabled.
  • Page 181 Conference-initiating INVITE that is sent to the media server when Enable3WayConference is set to 1. When using the Mediant 1000 Media Processing Module (MPM): 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 182: Figure 3-71: Metering Tones

    Mediant 1000 & Mediant 600 3.4.5.2.3 Metering Tones The FXS interfaces 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 183: Figure 3-72: Charge Codes Table

    • The 'Charge Codes Table' page is only available if the device provides FXS interface (i.e., FXS module installed) and is applicable only to Mediant 1000. • You can also configure the Charge Codes table using the ini file table parameter ChargeCode (refer to ''Analog Telephony Parameters'' on page 355).

  • Page 184: Keypad Features

    Notes: • The 'Keypad Features' page is only available if the device supports FXS interface and is applicable only to Mediant 1000. • The method used by the device to collect dialed numbers is identical to the method used during a regular call (i.e., max digits, interdigit timeout, digit map, etc.).

  • Page 185: Figure 3-73: Keypad Features

    SIP User's Manual 3. Web-Based Management To configure the keypad features, take these 4 steps: Open the 'Keypad Features' page (Configuration tab > Protocol Configuration menu > SIP Advanced Parameters submenu > Keypad Features page item). Figure 3-73: Keypad Features Page Configure the Keypad Features according to the table below.
  • Page 186 Mediant 1000 & Mediant 600 Parameter Description On Busy Keypad sequence that activates the forward on busy option. [KeyCFBusy] On Busy or No Answer Keypad sequence that activates the forward on 'busy or no answer' option. [KeyCFBusyOrNoAnsw Do Not Disturb...
  • Page 187 SIP User's Manual 3. Web-Based Management Parameter Description Transfer Blind Keypad sequence that activates blind transfer for Tel-to-IP calls. There are [KeyBlindTransfer] two possible scenarios: Option 1: After this sequence is dialed, the current call is put on hold (using Re-INVITE), a dial tone is played to the phone, and then phone number collection starts.
  • Page 188 SAS local SIP UDP port. Note: The SAS feature is applicable only to Mediant 1000. The 'SAS Configuration' page is Feature Key dependant and therefore is available only if included in the device's Feature Key (refer to 'Updating the Software Upgrade Key' on page 268).

  • Page 189: Figure 3-74: Sas Configuration

    SIP User's Manual 3. Web-Based Management To configure the Stand-Alone Survivability parameters, take these 4 steps: Open the 'SAS Configuration' page (Configuration tab > Protocol Configuration menu > SIP Advanced Parameters submenu > Stand-Alone Survivability page item). Figure 3-74: SAS Configuration Page Configure the parameters according to the table below.

  • Page 190: Configuring The Number Manipulation Tables

    Mediant 1000 & Mediant 600 Parameter Description Short Number Length Determines the length of the suffix used for SAS Short Numbering support. [SASShortNumberLeng The dialed number is compared to the registered number. The registered (full) and dialed (full or short) numbers match only if one of the following conditions is met: The numbers match entirely (i.e., they are of the same length and all...

  • Page 191: Figure 3-75: Source Phone Number Manipulation Table For Tel-To-Ip Calls

    SIP User's Manual 3. Web-Based Management The number manipulation is performed in the following tables: Destination Phone Number Manipulation Table for IP-to-Tel Calls (NumberMapIP2Tel ini file parameter) Destination Phone Number Manipulation Table for Tel-to-IP Calls (NumberMapTel2IP ini file parameter) Source Phone Number Manipulation Table for IP-to-Tel Calls (SourceNumberMapIP2Tel ini file parameter) Source Phone Number Manipulation Table for Tel-to-IP Calls (SourceNumberMapTel2IP ini file parameter)

  • Page 192: Table 3-41: Number Manipulation Parameters Description

    Mediant 1000 & Mediant 600 • When the source number is 1234510012001, it is changed to 20018. • When the source number is 3122, it is changed to 2312. From the 'Table Index' drop-down list, select the range of entries that you want to edit (up to 20 entries can be configured for Source Number Manipulation and 50 entries for Destination Number Manipulation).
  • Page 193 SIP User's Manual 3. Web-Based Management Parameter Description Number of digits removed from the left of the telephone number Number of Stripped Digits prefix: Enter the number of digits that you want removed. For example, if you enter 3 and the phone number is 5551234, the new phone number is 1234.

  • Page 194: Table 3-42: Dialing Plan Notations

    Mediant 1000 & Mediant 600 Parameter Description Presentation Determines whether Caller ID is permitted: Allowed = sends Caller ID information when a call is made using these destination / source prefixes. Restricted = restricts Caller ID information for these prefixes.

  • Page 195: Table 3-43: Npi/Ton Values For Isdn Etsi

    SIP User's Manual 3. Web-Based Management 3.4.5.3.2 Numbering Plans and Type of Number Numbers are classified by their Numbering Plan Indication (NPI) and their Type of Number (TON). The device supports all NPI/TON classifications used in the standard. The list of ISDN ETSI NPI/TON values is shown in the following table: Table 3-43: NPI/TON Values for ISDN ETSI Description...

  • Page 196: Figure 3-76: Phone Context Table

    Mediant 1000 & Mediant 600 To configure the Phone-Context tables, take these 4 steps: Open the 'Phone Context Table' page (Configuration tab > Protocol Configuration menu > Manipulation Tables submenu > Phone Context Table page item). Figure 3-76: Phone Context Table Page Configure the Phone Context table according to the table below.

  • Page 197: Configuring The Routing Tables

    SIP User's Manual 3. Web-Based Management Parameter Description Select the Number Type assigned to this entry. If you selected Unknown as the NPI, you can select Unknown [0]. If you selected Private as the NPI, you can select Unknown [0], Level 2 Regional [1], Level 1 Regional [2], PSTN Specific [3], or Level 0 Regional (Local) [4].

  • Page 198: Table 3-45: Routing General Parameters Description

    Mediant 1000 & Mediant 600 3.4.5.4.1 Routing General Parameters The 'Routing General Parameters' page allows you to configure the device's IP-to-Tel and Tel-to-IP routing parameters. To configure the general routing parameters, take these 4 steps: Open the 'Routing General Parameters' page (Configuration tab > Protocol Configuration menu >...
  • Page 199 SIP User's Manual 3. Web-Based Management Parameter Description Replace Empty Determines whether the internal channel number is used as the destination Destination with B- number if the called number is missing. channel Phone Number [0] No (default) [ReplaceEmptyDstWith [1] Yes PortNumber] Note: Applicable only for Tel-to-IP calls and if the called number is missing.
  • Page 200 Mediant 1000 & Mediant 600 Parameter Description Alt Routing Tel to IP Determines the event(s) reason for triggering Alternative Routing. Mode [0] None = Alternative routing is not used. [AltRoutingTel2IPMode] [1] Connectivity = Alternative routing is performed if ping to initial destination fails.
  • Page 201 SIP User's Manual 3. Web-Based Management Note that for this table to take precedence over a Proxy for routing calls, set the parameter PreferRouteTable to 1. The device checks the 'Destination IP Address' field in this table for a match with the outgoing call. A Proxy is used only if a match is not found. Possible uses for Tel-to-IP routing include the following: Fallback to internal routing table if there is no communication with the Proxy servers.

  • Page 202: Figure 3-77: Tel To Ip Routing

    Mediant 1000 & Mediant 600 To configure the Tel to IP Routing table, take these 6 steps: Open the 'Tel to IP Routing' page (Configuration tab > Protocol Configuration menu > Routing Tables submenu > Tel to IP Routing page item).
  • Page 203 SIP User's Manual 3. Web-Based Management Parameter Description Src. Trunk Group ID The source Trunk Group for Tel-to-IP calls. The range is 1-99. Notes: If this parameter is not required in the routing rule, leave the field empty. To denote any Trunk Group, you can enter the asterisk (*) symbol. Dest.
  • Page 204 The 'IP to Trunk Group Routing Table' page provides a table for routing incoming IP calls to groups of channels (BRI,E1/T1 B-channels, and Mediant 1000 FXS/FXO endpoints) called Trunk Groups. You can add up to 24 entries in the table.

  • Page 205: Figure 3-78: Ip To Trunk Group Routing Table

    SIP User's Manual 3. Web-Based Management To configure the IP to Trunk Group Routing table, take these 6 steps: Open the 'IP to Trunk Group Routing' page (Configuration tab > Protocol Configuration menu > Routing Tables submenu > IP to Trunk Group Routing page item).
  • Page 206 Mediant 1000 & Mediant 600 Parameter Description Source Host Prefix The From URI host name prefix of the incoming INVITE message. If configured, the device uses it for IP-to-Tel routing. If not used, it must be left empty. Notes: The asterisk (*) symbol cannot be used to depict any source host prefix.

  • Page 207: Figure 3-79: Internal Dns Table

    SIP User's Manual 3. Web-Based Management 3.4.5.4.4 Internal DNS Table The 'Internal DNS Table' page, similar to a DNS resolution is used to translate up to 10 host (domain) names into IP addresses (e.g., when using the 'Tel to IP Routing' table). Two different IP addresses can be assigned to the same host name, typically used for alternative routing (using the 'Tel to IP Routing' table).

  • Page 208: Figure 3-80: Internal Srv Table Screen

    Mediant 1000 & Mediant 600 3.4.5.4.5 Internal SRV Table The 'Internal SRV Table' page provides a table for resolving host names to DNS A- Records. Three different A-Records can be assigned to each host name. Each A-Record contains the host name, priority, weight, and port.
  • Page 209 Tel-to-IP calls is provided in SIP 4xx, 5xx, and 6xx response codes. For Tel-to-IP calls, an alternative IP address is provided; for IP-to-Tel calls an alternative Hunt (Mediant 1000 analog modules) or Trunk (digital modules) Group is provided. Refer to ''Tel to IP Routing Table'' on page for information on defining an alternative IP address;...

  • Page 210: Figure 3-81: Reasons For Alternative Routing

    Mediant 1000 & Mediant 600 To configure the reasons for alternative routing, take these 5 steps: Open the 'Reasons for Alternative Routing' page (Configuration tab > Protocol Configuration menu > Routing Tables submenu > Reasons for Alternative Routing page item).

  • Page 211: Figure 3-82: Release Cause Mapping

    SIP User's Manual 3. Web-Based Management 3.4.5.4.7 Release Cause Mapping The 'Release Cause Mapping' page consists of two groups that allow the device 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 ''Release Reason Mapping'' on page 459).

  • Page 212: Configuring The Profile Definitions

    Mediant 1000 & Mediant 600 3.4.5.5 Configuring the Profile Definitions The Profile Definitions submenu includes the following page items: Coder Group Settings (refer to ''Coder Group Settings'' on page 212) Tel Profile Settings (refer to ''Tel Profile Settings'' on page 214)

  • Page 213: Figure 3-83: Coder Group Settings

    SIP User's Manual 3. Web-Based Management Note: You can also configure the coder groups using the ini file table parameter CoderName (refer to ''SIP Configuration Parameters'' on page 323). To configure coder groups, take these 11 steps: Open the 'Coder Group Settings' page (Configuration tab > Protocol Configuration menu >...

  • Page 214: Tel Profile Settings

    Tel Profiles to the device's channels (in the 'Trunk Group Table' page), thereby applying different behaviors to different channels. Notes: • The following parameters are applicable only to Mediant 1000: 'Enable Polarity Reversal', 'Enable Current Disconnect', 'MWI Analog Lamp', and 'MWI Display'. •...

  • Page 215: Figure 3-84: Tel Profile Settings

    SIP User's Manual 3. Web-Based Management To configure Tel Profiles, take these 9 steps: Open the 'Tel Profile Settings' page (Configuration tab > Protocol Configuration menu > Profile Definitions submenu > Tel Profile Settings page item). Figure 3-84: Tel Profile Settings Page From the 'Profile ID' drop-down list, select the Tel Profile identification number you want to configure.
  • Page 216 Mediant 1000 & Mediant 600 Configure the Profile's parameters according to your requirements. For detailed information on each parameter, refer to its description on the page in which it is configured as an individual parameter. From the 'Coder Group' drop-down list, select the Coder Group (refer to ''Coder Group Settings'' on page 212) or the device's default coder (refer to ''Coders'' on page 157) to which you want to assign the Profile.

  • Page 217: Figure 3-85: Ip Profile Settings

    SIP User's Manual 3. Web-Based Management To configure the IP Profile settings, take these 9 steps: Open the 'IP Profile Settings' page (Configuration tab > Protocol Configuration menu > Profile Definitions submenu > IP Profile Settings page item). Figure 3-85: IP Profile Settings Page From the 'Profile ID' drop-down list, select an identification number for the IP Profile.

  • Page 218: Configuring The Endpoint Settings

    Call Forward (refer to ''Call Forward'' on page 222) Caller ID Permissions (refer to ''Caller ID Permissions'' on page 224) Call Waiting (refer to ''Call Waiting'' on page 225) Note: The Endpoint Settings menu is applicable only to Mediant 1000 analog modules. SIP User's Manual Document #: LTRT-83303...

  • Page 219: Figure 3-86: Authentication Screen

    Authentication is typically used for FXS interfaces, but can also be used for FXO interfaces. Notes: • The 'Authentication' page is applicable only to Mediant 1000. • The 'Authentication Mode' parameter (refer to ''Proxy & Registration Parameters'' on page 146) determines whether authentication is performed per port or for the entire device.

  • Page 220: Figure 3-87: Automatic Dialing

    To save the changes to flash memory, refer to ''Saving Configuration'' on page 265. Notes: • The 'Automatic Dialing' page is applicable only to Mediant 1000. • After a ring signal is detected on an 'Enabled' FXO port, the device initiates a call to the destination number without seizing the line.

  • Page 221: Figure 3-88: Caller Display Information

    SIP User's Manual 3. Web-Based Management 3.4.5.6.3 Caller Display Information The 'Caller Display Information' page allows you to enable the device to send Caller ID information to IP when a call is made. The called party can use this information for caller identification.

  • Page 222: Call Forward

    Notes: • The 'Call Forwarding Table' page is relevant to FXS and FXO interfaces. In addition, it is applicable only to Mediant 1000. • Ensure that the Call Forward feature is enabled (default) for the settings on this page to take effect. To enable Call Forward, use the parameter EnableForward (''Supplementary Services'' on page 176).

  • Page 223: Figure 3-89: Call Forward Table

    SIP User's Manual 3. Web-Based Management To configure Call Forward per port, take these 4 steps: Open the 'Call Forward Table' page (Configuration tab > Protocol Configuration menu > Endpoint Settings submenu > Call Forward page item). Figure 3-89: Call Forward Table Page Configure the Call Forward parameters for each port according to the table below.

  • Page 224: Figure 3-90: Caller Id Permissions

    Notes: • The 'Caller ID Permissions' page is relevant to FXS and FXO interfaces and applicable only to Mediant 1000. • You can also configure the Caller ID Permissions table using the ini file table parameter EnableCallerID (refer to ''Analog Telephony Parameters'' on page 355).

  • Page 225: Figure 3-91: Caller Waiting

    Notes: • This page is applicable only to FXS interfaces and applicable only to Mediant 1000. • Instead of using this page, you can enable or disable call waiting for all the device's ports, using the global call waiting parameter 'Enable Call Waiting' (refer to ''Supplementary Services'' on page 176).

  • Page 226: Configuring The Trunk And Ip Groups

    Mediant 1000 & Mediant 600 3.4.5.7 Configuring the Trunk and IP Groups The Trunk/IP Group menu allows you to configure groups of channels. This submenu includes the following page items: Trunk Group (refer to "Configuring the Trunk Group Table" on page 226)

  • Page 227: Table 3-50: Trunk Group Table Description

    The module type (FXS, FXO, BRI, or PRI) for which you want to define the Trunk Group. Note: FXS and FXO modules are applicable only to Mediant 1000. From Trunk Starting physical Trunk number. The number of listed Trunks depends on the device's hardware configuration.

  • Page 228: Figure 3-93: Trunk Group Settings

    Mediant 1000 & Mediant 600 3.4.5.7.2 Configuring the Trunk Group Settings The 'Trunk Group Settings' page is mainly used to select the method for which IP-to-Tel calls are assigned to channels within each Trunk Group. If no method is selected (for a specific Trunk Group), the setting of the global parameter ChannelSelectMode in the 'SIP General Parameters' page (refer to ''SIP General Parameters'' on page 134) applies.
  • Page 229 SIP User's Manual 3. Web-Based Management Mode Description Channel Select The method in which IP-to-Tel calls are assigned to channels pertaining to a Mode Trunk Group: By Dest Phone Number = Selects the device's channel according to the called number defined in the 'Trunk Group Table' (refer to "Configuring the Trunk Group Table"...
  • Page 230 Mediant 1000 & Mediant 600 Mode Description To enable Trunk Group registrations, configure the global parameter IsRegisterNeeded to 1. This is unnecessary for 'Per Account' registration mode. If no mode is selected, the registration is performed according to the global registration parameter ChannelSelectMode (refer to ''Proxy &...

  • Page 231: Figure 3-94: Ip Group Table

    SIP User's Manual 3. Web-Based Management 3.4.5.7.3 Configuring the IP Groups The 'IP Group Table' page allows you to create logical IP entities (IP Groups) that are later used in the call routing tables. The IP Groups are typically implemented in Tel-to-IP call routing. The IP Group can be used as a destination entity (DestIPGroupID) in the 'Tel to IP Routing' table, and ServingIPGroupID in the 'Trunk Group Settings' (refer to ''Configuring the Trunk Group Settings'' on page 228) and 'Account' (refer to ''Configuring the Account Table'' on page...

  • Page 232: Table 3-52: Ip Group Parameters Description

    Mediant 1000 & Mediant 600 Table 3-52: IP Group Parameters Description Parameter Description IP Group ID The identifying number of the IP Group. The range is 1-9. Description Brief string description of the IP Group. The value range is a string of up to 29 characters. The default is an empty field.

  • Page 233: Figure 3-95: Account Table

    SIP User's Manual 3. Web-Based Management To configure Accounts, take these 5 steps: Open the 'Account Table' page (Configuration tab > Protocol Configuration menu > Trunk/IP Group submenu > Account Table page item). Figure 3-95: Account Table Page To add an Account, in the 'Add' field, enter the desired table row index, and then click Add.
  • Page 234 Mediant 1000 & Mediant 600 Parameter Description the username and password defined in the 'Authentication' table for FXS interfaces (refer to Authentication on page 219) or the global parameters (UserName and Password) defined on the 'Proxy & Registration' page (refer to ''Proxy &...

  • Page 235: Configuring The Digital Gateway Parameters

    SIP User's Manual 3. Web-Based Management 3.4.5.8 Configuring the Digital Gateway Parameters The 'Digital Gateway Parameters' page allows you to configure miscellaneous digital parameters. To configure the digital gateway parameters, take these 4 steps: Open the 'Digital Gateway Parameters' page (Configuration tab > Protocol Configuration menu >...

  • Page 236: Table 3-54: Digital Gateway Parameters Description

    Mediant 1000 & Mediant 600 Table 3-54: Digital Gateway Parameters Description Parameter Description B-channel Negotiation Determines the ISDN B-Channel negotiation mode. [BchannelNegotiation] [0] Preferred [1] Exclusive (default) [2] Any Notes: Applicable only to ISDN protocols. For some ISDN variants, when 'Any' (2) is selected, the SETUP message does not include the Channel Identification IE.
  • Page 237 SIP User's Manual 3. Web-Based Management Parameter Description Send Screening Indicator to IP Overrides the calling party's number (CPN) screening indication in [ScreeningInd2IP] the received ISDN SETUP message for Tel-to-IP calls. [-1] Not Configured = not configured (interworking from ISDN to IP) or set to 0 for CAS (default).
  • Page 238 Mediant 1000 & Mediant 600 Parameter Description Enable User-to-User IE for IP to Enables SIP-to-PRI ISDN interworking. [0] Disable = Disabled (default). [EnableUUIIP2Tel] [1] Enable = Enable transfer of UUIE from SIP INVITE message to PRI SETUP message. The device supports the following SIP-to-PRI ISDN interworking:...
  • Page 239 SIP User's Manual 3. Web-Based Management Parameter Description [0] Disable = Disable (default). Enable ISDN Tunneling IP to Tel [EnableISDNTunnelingIP2Tel] [1] Using Header = Enable ISDN Tunneling from SIP to ISDN PRI using a proprietary SIP header. [2] Using Body = Enable ISDN Tunneling from SIP to ISDN PRI using a dedicated message body.
  • Page 240 Mediant 1000 & Mediant 600 Parameter Description Enable Calling Party Category Determines whether Calling Party Category (CPC) is mapped [EnableCallingPartyCategory] between SIP and PRI. [0] Disable = Don't relay the CPC between SIP and PRI (default). [1] Enable = The CPC is relayed between SIP and PRI.
  • Page 241 SIP User's Manual 3. Web-Based Management Parameter Description Default Call Priority Defines the default call priority for MLPP calls. [SIPDefaultCallPriority] [0] 0 = ROUTINE (default) [2] 2 = PRIORITY [6] 6 = IMMEDIATE [8] 8 = FLASH-OVERRIDE [9] 9 = FLASH-OVERRIDE-OVERRIDE If the incoming SIP INVITE request doesn't contain a valid priority value in the SIP Resource-Priority header, the default value is used in the Precedence IE (after translation to the relevant ISDN...

  • Page 242: Configuring The Ipmedia Parameters

    The 'IPmedia Parameters' page allows you to configure the IP media parameters. Note: The 'IPmedia Parameters' page is applicable only to Mediant 1000. The 'IPmedia Parameters' page is Feature Key dependant and therefore is available only if included in the device's Feature Key (refer to 'Updating the Software Upgrade Key' on page 268).
  • Page 243 SIP User's Manual 3. Web-Based Management ini File Field Name Valid Range and Description Web Parameter Name NetAnn Announcement ID NetAnn identification string (up to 16 characters) for playing an [NetAnnAnncID] announcement using the NetAnn interface. The application server sends a regular SIP INVITE message with a SIP URI that includes this identifier string and a “play=”...

  • Page 244: Advanced Applications

    Mediant 1000 & Mediant 600 3.4.6 Advanced Applications The Advanced Applications menu allows you to configure advanced SIP-based applications. This menu includes the following page items: Voice Mail Settings (refer to ''Configuring the Voice Mail Parameters'' on page 244) RADIUS Parameters (refer to ''Configuring RADIUS Accounting Parameters'' on page...

  • Page 245: Table 3-56: Voice Mail Parameters

    FXO line to restore connection to the original call. Note: This parameter is applicable only to Mediant 1000. Digit Patterns The following digit pattern parameters apply only to voice mail applications that use the DTMF communication method.
  • Page 246 Mediant 1000 & Mediant 600 Parameter Description Forward on No Answer Determines the digit pattern used by the PBX to indicate 'call forward on Digit Pattern (Internal) no answer' when the original call is received from an internal extension. [DigitPatternForwardOnN The valid range is a 120-character string.

  • Page 247: Configuring Radius Accounting Parameters

    SIP User's Manual 3. Web-Based Management Parameter Description MWI Suffix Pattern Determines the digit code used by the device as a suffix for 'MWI On [MWISuffixCode] Digit Pattern' and 'MWI Off Digit Pattern'. This suffix is added to the generated DTMF string after the extension number. The valid range is a 25-character string.

  • Page 248: Configuring The Fxo Parameters

    Mediant 1000 & Mediant 600 Parameter Description RADIUS Accounting Type Determines when the RADIUS accounting messages are sent to the [RADIUSAccountingType] RADIUS accounting server. [0] At Call Release = Sent at call release only (default). [1] At Connect & Release = Sent at call connect and release.

  • Page 249: Table 3-58: Fxo Parameters Description

    SIP User's Manual 3. Web-Based Management Table 3-58: FXO Parameters Description Parameter Description Dialing Mode Determines the dialing mode for IP-to-Tel (FXO) calls. [IsTwoStageDial] [0] One Stage = One-stage dialing. [1] Two Stages = Two-stage dialing (default). If two-stage dialing is enabled, the device seizes one of the PSTN/PBX lines without performing any dialing, connects the remote IP user to the PSTN/PBX, and all further signaling (dialing and Call Progress Tones) is performed directly with the PBX without the device's intervention.
  • Page 250 Mediant 1000 & Mediant 600 Parameter Description Ring Detection Timeout Defines the timeout (in seconds) for detecting the second ring after the first [sec] detected ring. [FXOBetweenRingTime] If automatic dialing is not used and Caller ID is enabled, the device seizes the line after detection of the second ring signal (allowing detection of caller ID sent between the first and the second rings).

  • Page 251: Configuring The Tdm Bus Settings

    SIP User's Manual 3. Web-Based Management Parameter Description [0] Enable = Do not disconnect call on detection of busy tone. Disconnect Call on Detection of Busy Tone [1] Disable = Call is released if busy or reorder (fast busy) tones are [DisconnectOnBusyTon detected on the device's FXO port (default).

  • Page 252: Table 3-59: Tdm Bus Settings Parameters Description

    Mediant 1000 & Mediant 600 Table 3-59: TDM Bus Settings Parameters Description Parameter Description PCM Law Select Determines the type of PCM companding law in input/output TDM [PCMLawSelect] bus. [1] Alaw = Alaw (default) [3] MuLaw = MuLaw Note: Typically, A-Law is used for E1 spans and µ-Law for T1/J1 spans.

  • Page 253: Management Tab

    SIP User's Manual 3. Web-Based Management Parameter Description TDM Bus PSTN Auto Clock Enables or disables the PSTN trunk auto-fallback reverting feature. Reverting If enabled and a trunk returning to service has an [TDMBusPSTNAutoClockReve AutoClockTrunkPriority parameter value (refer to ''Configuring the rtingEnable] Trunk Settings'' on page 96) that is higher than the priority of the local reference trunk (set in the TDMBusLocalReference parameter),...

  • Page 254: Configuring The Management Settings

    Mediant 1000 & Mediant 600 3.5.1.1 Configuring the Management Settings The 'Management Settings' page allows you to configure the device's management parameters. To configure the Management parameters, take these 4 steps: Open the 'Management Settings' page (Management tab > Management Configuration menu >...

  • Page 255: Table 3-60: Management Settings Parameters

    SIP User's Manual 3. Web-Based Management Table 3-60: Management Settings Parameters Parameter Description Syslog Settings Syslog Server IP Address IP address (in dotted-decimal notation) of the computer you are using [SyslogServerIP] to run the Syslog server. The Syslog server is an application designed to collect the logs and error messages generated by the device.
  • Page 256 Mediant 1000 & Mediant 600 Parameter Description Trap Manager Host Name Defines an FQDN of a remote host that is used as an SNMP [SNMPTrapManagerHostNa manager. The resolved IP address replaces the last entry in the Trap Manager table (defined by the parameter SNMPManagerTableIP_x) and the last trap manager entry of snmpTargetAddrTable in the snmpTargetMIB.

  • Page 257: Figure 3-103: Snmp Trap Destinations

    SIP User's Manual 3. Web-Based Management 3.5.1.1.1 Configuring the SNMP Trap Destinations Table The 'SNMP Trap Destinations' page allows you to configure up to five SNMP trap managers. To configure the SNMP Trap Destinations table, take these 5 steps: Access the 'Management Settings' page, as described in ''Configuring the Management Settings'' on page 254.

  • Page 258: Figure 3-104: Snmp Community Strings

    Mediant 1000 & Mediant 600 Parameter Description Trap Enable Activates or de-activates the sending of traps to the corresponding [SNMPManagerTrapSendi SNMP Manager. ngEnable_x] [0] Disable = Sending is disabled. [1] Enable = Sending is enabled (default). 3.5.1.1.2 Configuring the SNMP Community Strings...

  • Page 259: Figure 3-105: Snmp V3 Setting

    SIP User's Manual 3. Web-Based Management Table 3-62: SNMP Community Strings Parameters Description Parameter Description Read Only [SNMPReadOnlyCommunityString_x]: Up to five Community String read-only community strings (up to 19 characters each). The default string is 'public'. Read / Write [SNMPReadWriteCommunityString_x]: Up to five read / write community strings (up to 19 characters each).

  • Page 260: Table 3-63: Snmp V3 Users Parameters

    Mediant 1000 & Mediant 600 Table 3-63: SNMP V3 Users Parameters Parameter Description Index The table index. [SNMPUsers_Index] The valid range is 0 to 9. Username Name of the SNMP v3 user. This name must be unique. [SNMPUsers_Username] AuthProtocol Authentication protocol of the SNMP v3 user.

  • Page 261: Configuring The Regional Settings

    SIP User's Manual 3. Web-Based Management In the 'SNMP Trusted Managers' field, click the right-pointing arrow button; the 'SNMP Trusted Managers' page appears. Figure 3-106: SNMP Trusted Managers Select the check box corresponding to the SNMP Trusted Manager that you want to enable and for whom you want to define an IP address.

  • Page 262: Maintenance Actions

    Mediant 1000 & Mediant 600 3.5.1.3 Maintenance Actions The 'Maintenance Actions' page allows you to perform the following operations: Reset the device (refer to ''Resetting the Device'' on page 262) Lock and unlock the device (refer to ''Locking and Unlocking the Device'' on page 264)

  • Page 263: Figure 3-109: Reset Confirmation Message Box

    SIP User's Manual 3. Web-Based Management To reset the device, take these 6 steps: Open the 'Maintenance Actions' page (refer to ''Maintenance Actions'' on page 262). Under the 'Reset Configuration' group, from the 'Burn To FLASH' drop-down list, select one of the following options: •...

  • Page 264: Figure 3-110: Device Lock Confirmation Message Box

    Mediant 1000 & Mediant 600 3.5.1.3.2 Locking and Unlocking the Device The Lock and Unlock options allow you to lock the device so that it doesn't accept any new incoming calls. This is useful when, for example, you are uploading new software files to the device and you don't want any traffic to interfere with the process.

  • Page 265: Saving Configuration

    SIP User's Manual 3. Web-Based Management 3.5.1.3.3 Saving Configuration The 'Maintenance Actions' page allows you to save (burn) the current parameter configuration (including loaded auxiliary files) to the device's non-volatile memory (i.e., flash). The parameter modifications that you make throughout the Web interface's pages are temporarily saved (to the volatile memory - RAM) when you click the Submit button on these pages.

  • Page 266: Software Update

    In most cases, you are required to load this type of file. Note: This file type is applicable only to Mediant 1000. Up to eight different CAS files containing specific CAS protocol definitions for digital modules.

  • Page 267: Figure 3-111: Load Auxiliary Files

    SIP User's Manual 3. Web-Based Management To load an auxiliary file to the device using the Web interface, take these 6 steps: Open the 'Load Auxiliary Files' page (Management tab > Software Update menu > Load Auxiliary Files page item). Figure 3-111: Load Auxiliary Files Page Click the Browse button corresponding to the file type that you want to load, navigate to the folder in which the file is located, and then click Open;...

  • Page 268: Updating The Software Upgrade Key

    To avoid this, disable all traffic on the device by performing a graceful lock (refer to ''Locking and Unlocking the Device'' on page 264). • The FXO Coefficient file is applicable only to Mediant 1000. • You can schedule automatic loading of updated auxiliary files using HTTP, HTTPS, FTP, or NFS (refer to the Product Reference Manual).
  • Page 269 SIP User's Manual 3. Web-Based Management The procedure below describes how to load a Software Upgrade Key to the device using the Web interface. To load a Software Upgrade Key, take these 6 steps: Open the 'Software Upgrade Key Status' page (Management tab > Software Update menu >...

  • Page 270: Figure 3-112: Software Upgrade Key With Multiple S/N Lines

    Open the Software Upgrade Key file and check that the S/N line appears. If it does not appear, contact AudioCodes. Verify that you’ve loaded the correct file. Open the file and ensure that the first line displays [LicenseKeys].
  • Page 271 3.5.2.2.1 Loading via BootP/TFTP The procedure below describes how to load a Software Upgrade Key to the device using AudioCodes' BootP/TFTP Server utility (for a detailed description on the BootP utility, refer to the Product Reference Manual). To load a Software Upgrade Key file using BootP/TFTP, take these 6 steps: Place the Software Upgrade Key file (typically, a *.txt file) in the same folder in which...

  • Page 272: Software Upgrade Wizard

    • VP (Voice Prompts) • PRT (Prerecorded Tones) • • FXS Coefficient (applicable only to Mediant 1000) • USRINF (User Info) Warnings: • Before upgrading the device to a new major software version (e.g., from version 5.2 to 5.4), save a copy of the device's configuration settings (i.e., ini file) to your PC (refer to ''Backing Up and Restoring Configuration'' on page 276), and ensure that you have all the original auxiliary files (e.g.,...

  • Page 273: Figure 3-113: Start Software Upgrade Wizard Screen

    SIP User's Manual 3. Web-Based Management To use the Software Upgrade Wizard, take these 11 steps: Stop all traffic on the device (refer to the note above). Open the 'Software Upgrade Wizard' (Management tab > Software Update menu > Software Upgrade Wizard); the 'Software Upgrade Wizard' page appears. Figure 3-113: Start Software Upgrade Wizard Screen Click the Start Software Upgrade button;...

  • Page 274: Figure 3-115: Loaded Cmp File

    Mediant 1000 & Mediant 600 Click the Browse button, navigate to the cmp file, and then click Send File; the cmp file is loaded to the device and you're notified as to a successful loading, as shown below. Figure 3-115: Loaded CMP File Click one of the following buttons: •...

  • Page 275: Figure 3-116: Load An Ini File

    SIP User's Manual 3. Web-Based Management Figure 3-116: Load an ini File Page You can now choose to either: • Click Reset; the device resets, utilizing the new cmp and ini file you loaded up to now as well as utilizing the other auxiliary files. •...

  • Page 276: Backing Up And Restoring Configuration

    Mediant 1000 & Mediant 600 In the 'FINISH' page, complete the upgrade process by clicking Reset; the device 'burns' the newly loaded files to flash memory and then resets t.he device. After the device resets, the 'End Process' screen appears displaying the burned configuration files (refer to the figure below).

  • Page 277: Figure 3-119: Configuration File

    SIP User's Manual 3. Web-Based Management To save and restore the ini file, take these 3 steps: Open the 'Configuration File' page (Management tab > Software Update menu > Configuration File). Figure 3-119: Configuration File Page To save the ini file to a PC, perform the following: Click the Save INI File button;...

  • Page 278: Status & Diagnostics Tab

    The 'Message Log' page displays Syslog debug messages sent by the device. You can select the Syslog messages in this page, and then copy and paste them into a text editor such as Notepad. This text file (txt) can then be sent to AudioCodes Technical Support for diagnosis and troubleshooting.

  • Page 279: Figure 3-120: Message Log Screen

    SIP User's Manual 3. Web-Based Management Open the 'Message Log' page (Status & Diagnostics tab > Status & Diagnostics menu > Message Log page item); the 'Message Log' page is displayed and the log is activated. Figure 3-120: Message Log Screen The displayed logged messages are color coded as follows: •...

  • Page 280: Viewing The Ethernet Port Information

    The 'Device Information' page displays the device's specific hardware and software product information. This information can help you to expedite troubleshooting. Capture the page and e-mail it to AudioCodes Technical Support personnel to ensure quick diagnosis and effective corrective action. This page also displays any loaded files used by the device (stored in the RAM) and allows you to remove them.

  • Page 281: Figure 3-122: Device Information

    Click the Delete button corresponding to the files that you want to delete. Deleting a file takes effect only after the device is reset (refer to ''Resetting the Device'' on page 262). Note: FXS and FXO Coefficient files are applicable only to Mediant 1000. Version 5.4 May 2008...

  • Page 282: Viewing Performance Statistics

    Mediant 1000 & Mediant 600 3.6.1.4 Viewing Performance Statistics The 'Performance Statistics' page provides read-only, device performance statistics. This page is refreshed with new statistics every 60 seconds. The duration that the current statistics has been collected, is displayed above the statistics table.

  • Page 283: Gateway Statistics

    SIP User's Manual 3. Web-Based Management To view the list of alarms, take this step: Open the 'Active Alarms’ page (Status & Diagnostics tab > Status & Diagnostics menu > Active Alarms page item). Figure 3-124: Active Alarms Page 3.6.2 Gateway Statistics The 'Gateway Statistics' page allows you to monitor real-time activity such as IP connectivity information, call details and call statistics, including the number of call...

  • Page 284: Figure 3-125: Calls Count

    Mediant 1000 & Mediant 600 To view the IP-to-Tel and Tel-to-IP Call Counters pages, take this step: Open the Call Counters page that you want to view (Status & Diagnostics tab > Gateway Statistics menu > IP to Tel Calls Count or Tel to IP Calls Count page item);...
  • Page 285 SIP User's Manual 3. Web-Based Management Counter Description Number of Calls Indicates the number of calls that weren't answered. It's incremented as a Terminated due to result of one of the following release reasons: No Answer GWAPP_NO_USER_RESPONDING (18) GWAPP_NO_ANSWER_FROM_USER_ALERTED (19) GWAPP_NORMAL_CALL_CLEAR (16) (when the call duration is zero) Number of Calls Indicates the number of calls that were terminated due to a call forward.

  • Page 286: Call Routing Status

    Mediant 1000 & Mediant 600 3.6.2.2 Call Routing Status The 'Call Routing Status' page provides you with information on the current routing method used by the device. This information includes the IP address and FQDN (if used) of the Proxy server with which the device currently operates.

  • Page 287: Registration Status

    The 'Registration Status' page displays whether the device or endpoints are registered to a SIP Registrar/Proxy server. Note: The 'Registration Status' page is applicable only to Mediant 1000. To view endpoint Registration status, take this step: Open the 'Registration Status' page (Status & Diagnostics tab > Gateway Statistics menu >...

  • Page 288: Sas/Sbc Registered Users

    (SAS) registered users. The SAS feature is configured in the 'SAS Configuration' page (refer to ''Stand-Alone Survivability'' on page 188). Note: The SAS feature is applicable only to Mediant 1000. To view the SAS registered users, take this step: Open the 'SAS Registered Users' page (Status & Diagnostics tab > Gateway Statistics menu >...

  • Page 289: Ip Connectivity

    SIP User's Manual 3. Web-Based Management 3.6.2.5 IP Connectivity The 'IP Connectivity' page displays online, read-only network diagnostic connectivity information on all destination IP addresses configured in the 'Tel to IP Routing' page (refer to ''Tel to IP Routing Table'' on page 200). Notes: •...
  • Page 290 Mediant 1000 & Mediant 600 Column Name Description Connectivity Status The status of the IP address' connectivity according to the method in the 'Connectivity Method' field. OK = Remote side responds to periodic connectivity queries. Lost = Remote side didn't respond for a short period.

  • Page 291: Ini File Configuration

    Typically, it is loaded to or retrieved from the device using TFTP or HTTP. These protocols are not secure and vulnerable to potential hackers. To overcome this security threat, the AudioCodes' TrunkPack Downloadable Conversion Utility (DConvert) allows you to binary-encode the ini file before loading it to the device (refer to the Product Reference Manual).

  • Page 292: The Ini File Structure

    Mediant 1000 & Mediant 600 The ini File Structure The ini file can contain any number of parameters. The ini file can contain the following types of parameters: Individual parameters, which are conveniently grouped (optional) by their functionality (refer to ''Structure of Individual ini File Parameters'' on page 292)

  • Page 293: Structure Of Ini File Table Parameters

    SIP User's Manual 4. ini File Configuration An example of an ini file containing individual ini file parameters is shown below: [SYSTEM Params] SyslogServerIP = 10.13.2.69 EnableSyslog = 1 ; These are a few of the system-related parameters. [WEB Params] LogoWidth = '339' WebLogoText = 'My Device' UseWeblogo = 1...
  • Page 294 Mediant 1000 & Mediant 600 Data line(s): Contain the actual values of the parameters. The values are interpreted according to the Format line. • The first word of the Data line must be the table’s string name followed by the Index field.

  • Page 295: Example Of An Ini File

    SIP User's Manual 4. ini File Configuration The table below displays an example of an ini file table parameter: [ PREFIX ] FORMAT PREFIX_Index = PREFIX_DestinationPrefix, PREFIX_DestAddress, PREFIX_SourcePrefix, PREFIX_ProfileId, PREFIX_MeteringCode, PREFIX_DestPort; PREFIX 0 = 10, 10.13.83.5, *, 0, 255, 0; PREFIX 1 = 20, 10.13.83.7, *, 0, 255, 0;...

  • Page 296: Modifying An Ini File

    Mediant 1000 & Mediant 600 Modifying an ini File You can modify an ini file currently used by a device. Modifying an ini file instead of loading an entirely new ini file preserves the device's current configuration, including factory default values.
  • Page 297 SIP User's Manual 4. ini File Configuration ini File Parameter Description MIIRedundancyEnable Enables the Ethernet Interface Redundancy feature. When enabled, the device performs a switchover to the secondary (redundant) Ethernet port upon sensing a link failure in the primary Ethernet port. When disabled, the device operates with a single port (i.e.
  • Page 298 Mediant 1000 & Mediant 600 ini File Parameter Description DNS2IP This ini file table parameter configures the internal DNS table for resolving host names to IP addresses. Two different IP addresses (in dotted-decimal notation) can be assigned to a host name.
  • Page 299 SIP User's Manual 4. ini File Configuration ini File Parameter Description Notes: If the Internal SRV table is used, the device first attempts to resolve a domain name using this table. If the domain name isn't located, the device performs an SRV resolution using an external DNS server. This parameter can include up to 10 indices.
  • Page 300 Mediant 1000 & Mediant 600 ini File Parameter Description [0] = Disable UDP port translation (default). EnableUDPPortTranslatio [1] = Enable UDP port translation. When enabled, the device compares the source UDP port of the first incoming packet, to the remote UDP port stated in the opening of the channel.
  • Page 301 SIP User's Manual 4. ini File Configuration ini File Parameter Description SyslogOutputMethod Determines the method used for Syslog messages. [0] = Send all Syslog messages to the defined Syslog server (default). [1] = Send all Syslog messages using the Debug Recording mechanism.
  • Page 302 Mediant 1000 & Mediant 600 ini File Parameter Description VLANNativeVLANID For a description of this parameter, refer to ''Configuring the IP Settings'' on page 64. For a description of this parameter, refer to ''Configuring the IP Settings'' VLANOamVLANID on page 64.
  • Page 303 SIP User's Manual 4. ini File Configuration ini File Parameter Description LocalControlSubnetMask For a description of this parameter, refer to ''Configuring the IP Settings'' on page 64. LocalControlDefaultGW For a description of this parameter, refer to ''Configuring the IP Settings'' on page 64.
  • Page 304 Mediant 1000 & Mediant 600 ini File Parameter Description GoldServiceClassDiffSer For a description of this parameter, refer to ''Configuring the QoS Settings'' on page 78. For a description of this parameter, refer to ''Configuring the QoS BronzeServiceClassDiffS Settings'' on page 78.

  • Page 305: System Parameters

    This parameter is applicable only to Mediant 1000. For ground-start signaling, ensure that the FXO G module is installed (and not the regular FXO module) in the Mediant 1000 chassis. For FXO ground-start signaling, ensure that the parameters EnableCurrentDisconnect is set to 1 and FXOBetweenRingTime is set to 300.
  • Page 306 Mediant 1000 & Mediant 600 ini File Parameter Description ActivityListToLog The Activity Log mechanism enables the device to send log messages (to a Syslog server) that report certain types of Web actions according to a pre-defined filter. The following filters are available: [PVC] (Parameters Value Change) = Changes made on-the-fly to parameters.
  • Page 307 SIP User's Manual 4. ini File Configuration ini File Parameter Description HeartBeatDestIP Destination IP address (in dotted format notation) to which the device sends proprietary UDP 'ping' packets. The default IP address is 0.0.0.0. HeartBeatDestPort Destination UDP port to which the heartbeat packets are sent. The range is 0 to 64000.
  • Page 308 Specifies the name of the FXS coefficients file and the location of the server (IP address or FQDN) from where it is loaded. For example: http://server_name/file, https://server_name/file. The maximum length of the URL address is 99 characters. Note: This parameter is applicable only to Mediant 1000. SIP User's Manual Document #: LTRT-83303...
  • Page 309 (IP address or FQDN) from which it is loaded. For example: http://server_name/file, https://server_name/file. The maximum length of the URL address is 99 characters. Note: This parameter is applicable only to Mediant 1000. CasFileURL Specifies the name of the CAS file and the location of the server (IP address or FQDN) from which it is loaded.
  • Page 310 Mediant 1000 & Mediant 600 ini File Parameter Description Set the number of BootP requests Set the number of DHCP packets the device sends during start-up. the device sends. The device stops sending BootP After all packets were sent, if there's...

  • Page 311: Web And Telnet Parameters

    SIP User's Manual 4. ini File Configuration ini File Parameter Description Serial Parameters [0] = RS-232 serial port is enabled (default). DisableRS232 [1] = RS-232 serial port is disabled. The RS-232 serial port can be used to change the networking parameters and view error / notification messages.
  • Page 312 Mediant 1000 & Mediant 600 ini File Parameter Description [0] = Enable Web management (default). DisableWebTask [1] = Disable Web management. ResetWebPassword Resets the username and password of the primary and secondary accounts to their defaults. [0] = Password and username retain their values (default).
  • Page 313 Name of the image file (of type GIF, JPEG, or JPG) 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. Version 5.4...

  • Page 314: Security Parameters

    Mediant 1000 & Mediant 600 4.4.4 Security Parameters Table 4-4: Security Parameters ini File Parameter Description For a description of this parameter, refer to ''Configuring the General EnableMediaSecurity Security Settings'' on page 123. MediaSecurityBehaviou For a description of this parameter, refer to ''Configuring the General Security Settings'' on page 123.
  • Page 315 SIP User's Manual 4. ini File Configuration ini File Parameter Description OCSPServerIP Defines the IP address of the OCSP server. The default IP address is 0.0.0.0. OCSPServerPort Defines the OCSP server's TCP port number. The default port number is 2560. OCSPDefaultResponse Determines the default OCSP behavior when the server cannot be contacted.
  • Page 316 Mediant 1000 & Mediant 600 ini File Parameter Description IPSecPolicyLifeInSec, IPSecPolicyLifeInKB, IPSecPolicyProposalEncryption_X, IPSecPolicyProposalAuthentication_X, IPSecPolicyKeyExchangeMethodIndex, IPSecPolicyLocalIPAddressType, IPSecPolicyRemoteTunnelIPAddress, IPsecPolicyRemoteSubnetMask; [\IPSEC_SPD_TABLE] Where, Mode = IPSec mode of operation: [0] Transport, [1] Tunneling. PolicyRemoteIPAddress = Destination IP address (or FQDN) to which the IPSec mechanism is applied.
  • Page 317 SIP User's Manual 4. ini File Configuration ini File Parameter Description (DES/SHA1 and 3DES/SHA1). IPsec is performed using the Transport mode. Notes: Each line in the table refers to a different IP destination. To support more than one Encryption / Authentication proposal, for each proposal specify the relevant parameters in the Format line.
  • Page 318 BootP/TFTP. For information on loading this file via the Web interface, refer to the Product Reference Manual. For a description of this parameter, refer to Configuring the General VoiceMenuPassword Security Settings on page 123. Note: This parameter is applicable only to Mediant 1000. SIP User's Manual Document #: LTRT-83303...
  • Page 319 SIP User's Manual 4. ini File Configuration ini File Parameter Description Internal Firewall Parameters This ini file table parameter configures the device's access list (firewall), which defines network traffic filtering rules. The format of this parameter is as follows: [ACCESSLIST] FORMAT AccessList_Index = AccessList_Source_IP, AccessList_Net_Mask, AccessList_Start_Port, AccessList_End_Port, AccessList_Protocol, AccessList_Packet_Size, AccessList_Byte_Rate,...

  • Page 320: Radius Parameters

    Mediant 1000 & Mediant 600 4.4.5 RADIUS Parameters For detailed information on the supported RADIUS attributes, refer to ''Supported RADIUS Attributes'' on page 419. Table 4-5: RADIUS Parameters ini File Parameter Description EnableRADIUS For a description of this parameter, refer to ''Configuring the General Security Settings'' on page 123.

  • Page 321: Snmp Parameters

    SIP User's Manual 4. ini File Configuration 4.4.6 SNMP Parameters Table 4-6: SNMP Parameters ini File Parameter Description DisableSNMP For a description of this parameter, refer to ''Configuring the Management Settings'' on page 254. SNMPPort The device's local UDP port used for SNMP Get/Set commands. The range is 100 to 3999.
  • Page 322 Mediant 1000 & Mediant 600 ini File Parameter Description SNMP Trap Parameters For a description of this parameter, refer to ''Configuring the SNMP SNMPManagerTableIP_x Managers Table'' on page 257. SNMPManagerTrapPort_x For a description of this parameter, refer to ''Configuring the SNMP Managers Table'' on page 257.

  • Page 323: Sip Configuration Parameters

    SIP User's Manual 4. ini File Configuration ini File Parameter Description authNoPriv(2), authentication protocol MD5, authentication text password 'myauthkey', and ReadWriteGroup2. Notes: This parameter can include up to 10 indices. To configure SNMP v3 users through the Web interface, refer to ''Configuring SNMP V3 Users'' on page 259.
  • Page 324 Mediant 1000 & Mediant 600 ini File Parameter Description DNSQueryType For a description of this parameter, refer to ''Proxy & Registration Parameters'' on page 146. For a description of this parameter, refer to ''Proxy & Registration ProxyDNSQueryType Parameters'' on page 146.
  • Page 325 SIP User's Manual 4. ini File Configuration ini File Parameter Description Notes: This table parameter can include up to 6 indices (0-5). For configuring the Proxy Sets, refer to the ini file parameter ProxyIP. For configuring the Proxy Set ID table using the Web interface, refer to ''Proxy Sets Table'' on page 153.
  • Page 326 Mediant 1000 & Mediant 600 ini File Parameter Description OfferUnencryptedSRTCP Determines whether the device adds the UNENCRYPTED_SRTCP attribute to outgoing SDP messages when SRTP/SRTCP is enabled. [0] Disable (default). [1] Enable. For example: a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:WxMz3YE0fcbjVJOGgSxweCZxySisl6SWi103t6No UNENCRYPTED_SRTCP Note: When enabled, the device adds the UNENCRYPTED_SRTCP attribute to the ‘crypto’...
  • Page 327 SIP User's Manual 4. ini File Configuration ini File Parameter Description RegistrarIP For a description of this parameter, refer to ''Proxy & Registration Parameters'' on page 146. RegistrarTransportType For a description of this parameter, refer to ''Proxy & Registration Parameters'' on page 146. RegistrarName For a description of this parameter, refer to ''Proxy &...
  • Page 328 Mediant 1000 & Mediant 600 ini File Parameter Description Account_Register, Account_ContactUser; [\Account] Where, ServedTrunkGroup = Trunk Group ID for which the device performs registration/authentication to a destination IP Group. ServedIPGroup = Currently not applicable (see note below). ServingIPGroup = Destination IP (Group) to where the device sends the REGISTER requests (and/or digest authentication username and password) for registering (and/or authenticating) the Trunk Group.
  • Page 329 SIP User's Manual 4. ini File Configuration ini File Parameter Description Where, Description = Brief description of the IP Group. ProxySetId = Proxy Set ID associated with the IP Group. SIPGroupName = Request URI host name used in INVITE and REGISTER messages.
  • Page 330 Mediant 1000 & Mediant 600 ini File Parameter Description UseAORInReferToHeader Defines the source for the SIP URI set in the Refer-To header of outgoing REFER messages. [0] = Use SIP URI from Contact header of the initial call (default). [1] = Use SIP URI from To/From header of the initial call.
  • Page 331 SIP User's Manual 4. ini File Configuration ini File Parameter Description EnableSilenceSuppInSDP Determines the device's behavior upon receipt of SIP Re-INVITE messages that include the silencesupp:off attribute. [0] = Disregard the silecesupp attribute (default). [1] = Handle incoming Re-INVITE messages that include the silencesupp:off attribute in the SDP as a request to switch to the Voice-Band-Data (VBD) mode.
  • Page 332 Mediant 1000 & Mediant 600 ini File Parameter Description DefaultReleaseCause For a description of this parameter, refer to ''SIP General Parameters'' on page 134. For a description of this parameter, refer to ''SIP General Parameters'' IPAlertTimeout on page 134. SIPPSessionExpires For a description of this parameter, refer to ''SIP General Parameters'' on page 134.
  • Page 333 Call Waiting Ringback tone to the calling party after a 182 response is received. Notes: This parameter is applicable only to Mediant 1000. If this parameter is not configured (default), use the global parameter EnableCallWaiting (refer to "Supplementary Services" on page 176).
  • Page 334 REFER messages sent by the device to the remote parties. The remote parties join the conference by sending INVITE messages to the media server using this conference URI. Note: This parameter is applicable only to Mediant 1000. Enable3WayConference For a description of this parameter, refer to "Supplementary Services"...
  • Page 335 The valid range is -1 to 2,147,483,647. The default is 600. Notes: This parameter is applicable only to Mediant 1000. A negative value indicates that the tone is played infinitely. 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., external vs.
  • Page 336 Mediant 1000 & Mediant 600 ini File Parameter Description TxDTMFOption This ini file table parameter determines a single or several (up to 5) preferred transmit DTMF negotiation methods. The format of this parameter is as follows: [TxDTMFOption] FORMAT TxDTMFOption_Index = TxDTMFOption_Type;...
  • Page 337 134. EmergencyRegretTimeout For a description of this parameter, refer to Advanced Parameters on page 166. Note: This parameter is applicable only to Mediant 1000. EmergencyNumbers For a description of this parameter, refer to Advanced Parameters on page 166.
  • Page 338 Authentication 3 = user1, 1234,1,0; [\Authentication] Notes: This parameter is applicable only to Mediant 1000. You can omit either the username or password using the sign '$$'. If omitted, the port's phone number is used for authentication. The indexing of this ini file table parameter starts at 1.
  • Page 339 Description SASDefaultGatewayIP For a description of this parameter, refer to "Stand-Alone Survivability" on page 188. Note: SAS is applicable only to Mediant 1000. SASRegistrationTime For a description of this parameter, refer to "Stand-Alone Survivability" on page 188. Note: SAS is applicable only to Mediant 1000.
  • Page 340 Mediant 1000 & Mediant 600 ini File Parameter Description standards (e.g., payload type of G.711 U-law is always 0). Other values can be set dynamically. If no value is specified for a dynamic field, a default value is assigned. If a value is specified for a hard- coded field, the value is ignored.
  • Page 341 SIP User's Manual 4. ini File Configuration ini File Parameter Description The 'Profile Name' assigned to a Profile index, must enable users to identify it intuitively and easily. To configure the IP Profile table using the Web interface, refer to ''IP Profile Settings'' on page 216.

  • Page 342: Media Server Parameters

    Mediant 1000 & Mediant 600 4.4.8 Media Server Parameters Table 4-8: Media Server Parameters ini File Parameter Description For a description of this parameter, refer to "Configuring the IPmedia MSCMLID Parameters" on page 242. AmsProfile Must be set to 1 to use advanced audio.

  • Page 343: Voice Mail Parameters

    SIP User's Manual 4. ini File Configuration ini File Parameter Description BipOnConference For a description of this parameter, refer to "Configuring the IPmedia Parameters" on page 242. TranscodingID For a description of this parameter, refer to "Configuring the IPmedia Parameters" on page 242. ActiveSpeakersNotifica For a description of this parameter, refer to Configuring the IPmedia tionMinInterval...

  • Page 344: Pstn Parameters

    Mediant 1000 & Mediant 600 ini File Parameter Description DigitPatternForwardOn For a description of this parameter, refer to ''Configuring the Voice Mail NoAnswer (VM) Parameters'' on page 244. For a description of this parameter, refer to ''Configuring the Voice Mail DigitPatternForwardOn (VM) Parameters'' on page 244.
  • Page 345 SIP User's Manual 4. ini File Configuration ini File Parameter Description TerminationSide_x Same as the description for parameter TerminationSide, but for a specific trunk ID (x = 0 - 3). ClockMaster For a description of this parameter, refer to "Configuring the Trunk Settings"...
  • Page 346 Mediant 1000 & Mediant 600 ini File Parameter Description ISDNRxOverlap_x For a description of this parameter, refer to "Configuring the Trunk Settings" on page 96. [0] = Disabled (default). ISDNRxOverlap [1] = Enabled. Any number bigger than one = Number of digits to receive.
  • Page 347 SIP User's Manual 4. ini File Configuration ini File Parameter Description ISDN Flexible Behavior Parameters ISDN protocol is implemented in different Switches / PBXs by different vendors. Several implementations vary a little from the specification. Therefore, to provide a flexible interface that supports these ISDN variants, the ISDN behavior parameters are used.

  • Page 348: Isdn And Cas Interworking-Related Parameters

    Mediant 1000 & Mediant 600 ini File Parameter Description DigitMapping For a description of this parameter, refer to ''DTMF & Dialing Parameters'' on page 160. For a description of this parameter, refer to ''DTMF & Dialing TimeBetweenDigits Parameters'' on page 160.
  • Page 349 SIP User's Manual 4. ini File Configuration ini File Parameter Description CauseMapSIP2ISDN This ini file table parameter maps SIP Responses to Q.850 Release Causes. The format of this parameter is as follows: [CauseMapSIP2ISDN] FORMAT CauseMapSIP2ISDN_Index = CauseMapSIP2ISDN_SipResponse, CauseMapSIP2ISDN_IsdnReleaseCause; [\CauseMapSIP2ISDN] Where, SipResponse = SIP Response IsdnReleaseCause = Q.850 Release Cause For example:...
  • Page 350 Mediant 1000 & Mediant 600 ini File Parameter Description SITQ850Cause Determines the Q.850 cause value specified in the Reason header that is included in a 4xx response when Special Information Tone (SIT) is detected on an IP-to-Tel call. The valid range is 0 to 127. The default value is 34.
  • Page 351 SIP User's Manual 4. ini File Configuration ini File Parameter Description ISDNSubAddressFormat Determines the format of the 'subaddress' value for ISDN Calling and Called numbers. [0] = ASCII (default). [1] = BCD (Binary Coded Decimal) For IP-to-Tel calls, if the incoming SIP INVITE message includes subaddress values in the 'isub' parameter for the Called Number (in the Request-URI) and/or the Calling Number (in the From header), these values are interworked to the outgoing ISDN SETUP message.
  • Page 352 Mediant 1000 & Mediant 600 ini File Parameter Description [0] = Not used (default). EnableAOC [1] = ISDN Advice of Charge (AOC) messages are interworked to SIP. The device supports receipt of ISDN (Euro ISDN) AOC messages. AOC messages can be received during a call (FACILITY messages) or at the end of a call (DISCONNECT or RELEASE messages).
  • Page 353 SIP User's Manual 4. ini File Configuration ini File Parameter Description CASAddressingDelimite Determines if delimiters are added to the dialed address or dialed ANI parameters. [0] = Disable (default) [1] = Enable When this parameter is enabled, delimiters such as '*', '#', and 'ST' are added to the dialed address or dialed ANI parameters.
  • Page 354 Mediant 1000 & Mediant 600 ini File Parameter Description SendIEonTG For a description of this parameter, refer to ''Configuring the Digital Gateway Parameters'' on page 235. Overrides the T310 timer for the DMS-100 ISDN variant. ISDNDMSTimerT310 T310 defines the timeout between the reception of a PROCEEDING message and the reception of an ALERTING / CONNECT message.

  • Page 355: Analog Telephony Parameters

    FXS port to play a secondary dial tone and then restart digit collection. The valid range is a 1-character string. The default is an empty string. Note: This parameter is applicable only to Mediant 1000 FXS interfaces. EnableMOH Enables the option of using an external audio source, which is connected to the device's AUDIO connector (on the CPU module).
  • Page 356 Mediant 1000 & Mediant 600 ini File Parameter Description ChargeCode This ini file table parameter configures metering tones (and their time intervals) that the device's FXS interface generates to the Tel side. The format of this parameter is as follows:...
  • Page 357 SIP User's Manual 4. ini File Configuration ini File Parameter Description For example: [TargetOfChannel] TargetOfChannel 1 = 1001,1,0,1; (Automatic dialing on Port 1, Module 1) [\TargetOfChannel] Notes: The indexing of this ini file table parameter starts at 1. The numbering of channels starts at 0. Define this parameter for each device port that implements Automatic Dialing.
  • Page 358 Mediant 1000 & Mediant 600 ini File Parameter Description FwdInfo This ini file table parameter forwards IP-to-Tel calls (using SIP 302 response), based on the device's port to which the call is routed. The format of this parameter is as follows:...
  • Page 359 SIP User's Manual 4. ini File Configuration ini File Parameter Description The numbering of ports starts at 0. If a port isn't configured, its Caller ID generation / detection are determined according to the global parameter EnableCallerID (described in ''Supplementary Services'' on page 176). To configure Call ID Permissions using the Web interface, refer to ''Caller ID Permissions'' on page 224.
  • Page 360 Mediant 1000 & Mediant 600 ini File Parameter Description SubscribeRetryTime For a description of this parameter, refer to ''Supplementary Services'' on page 176. For a description of this parameter, refer to ''Supplementary Services'' on MWIServerTransportTy page 176. MWIExpirationTime For a description of this parameter, refer to ''Supplementary Services'' on page 176.
  • Page 361 REFER message is sent toward the IP side. If this parameter is set to 0, the REFER message is immediately sent. The valid range is 0 to 1,000,000. The default is 0. Note: This parameter is applicable only to Mediant 1000. This ini file table parameter determines whether the device rejects RejectAnonymousCallP erPort incoming anonymous calls on FXS interfaces.
  • Page 362 Mediant 1000 & Mediant 600 ini File Parameter Description NTTDIDSignallingForm Determines the type of Direct Inward Dialing (DID) signaling support for NTT (Japan) modem: DTMF- or Frequency Shift Keying (FSK)-based signaling. The devices can be connected to Japan's NTT PBX using 'Modem' DID lines.
  • Page 363 SIP User's Manual 4. ini File Configuration ini File Parameter Description CurrentDisconnectDura The duration (in msec) of the current disconnect pulse. tion The range is 200 to 1500. The default is 900. Notes: This parameter is applicable for both FXS and FXO interfaces. The FXO interface detection range is approximately 200 msec of the parameter's value plus 100.

  • Page 364: Number Manipulation And Routing Parameters

    Mediant 1000 & Mediant 600 ini File Parameter Description BellcoreVMWITypeOne Selects the Bellcore VMWI sub-standard. Standard [0] = Between rings (default). [1] = Not ring related. 4.4.13 Number Manipulation and Routing Parameters Table 4-13: Number Manipulation and Routing Parameters ini File Parameter...
  • Page 365 ServingIPGroup = Serving IP Group ID to where INVITE messages initiated by the Trunk Group endpoints are sent. For example: [TrunkGroupSettings] TrunkGroupSettings 0 = 1, 0, 5, audiocodes, user, 1; TrunkGroupSettings 1 = 2, 1, 0, localname, user1, 2; [\TrunkGroupSettings] Notes: This parameter can include up to 240 indices.
  • Page 366 Mediant 1000 & Mediant 600 ini File Parameter Description [0] = Leave Source Number empty (default). CopyDestOnEmptySource [1] = If the Source Number of a Tel-to-IP call is empty, the Destination Number is copied to the Source Number. AddNPIandTON2CallingN For a description of this parameter, refer to Routing General Parameters umber on page 198.
  • Page 367 SIP User's Manual 4. ini File Configuration ini File Parameter Description Notes: This parameter can include up to 50 indices. The parameters SrcIPGroupID, DestHostPrefix, and SrcHostPrefix are currently not applicable and must be left empty (or -1). (They are used only for IP-to-IP routing, supported in the next applicable release).
  • Page 368 Mediant 1000 & Mediant 600 ini File Parameter Description DestHostPrefix = Request URI host name prefix of the incoming INVITE message. SrcHostPrefix = From URI host name prefix of the incoming INVITE message. For example: [PSTNPrefix] FORMAT PstnPrefix_Index = PstnPrefix_DestPrefix,...
  • Page 369 SIP User's Manual 4. ini File Configuration ini File Parameter Description SwapTel2IPCalled&Calling If enabled, the device swaps the calling and called numbers received Numbers from the Tel side. The INVITE message contains the swapped numbers. Applicable for Tel-to-IP calls. [0] = Disabled (default) [1] = Swap calling and called numbers For a description of this parameter, refer to ''SIP General Parameters'' AddTON2RPI...
  • Page 370 Mediant 1000 & Mediant 600 ini File Parameter Description (RPID) header by using the EnableRPIHeader and AddTON2RPI parameters. To configure manipulation of destination numbers for Tel-to-IP calls using the Web interface (i.e., in the 'Destination Phone Number Manipulation Table for Tel-to-IP Calls' table), refer to ''Configuring the Number Manipulation Tables'' on page 190).
  • Page 371 SIP User's Manual 4. ini File Configuration ini File Parameter Description The Source IP address can include the 'x' wildcard to represent single digits. For example: 10.8.8.xx represents all addresses between 10.8.8.10 and 10.8.8.99. The Source IP address can include the asterisk ('*') wildcard to represent any number between 0 and 255.
  • Page 372 Mediant 1000 & Mediant 600 ini File Parameter Description Notes: RemoveFromLeft, RemoveFromRight, Prefix2Add, Suffix2Add, LeaveFromRight, NumberType, NumberPlan, and IsPresentationRestricted are applied if the called and calling numbers match the DestinationPrefix and SourcePrefix conditions. The manipulation rules are executed in the following order: RemoveFromLeft, RemoveFromRight, LeaveFromRight, Prefix2Add, and Suffix2Add.
  • Page 373 SIP User's Manual 4. ini File Configuration ini File Parameter Description IsPresentationRestricted = Calling number presentation (0 to allow presentation; 1 to restrict presentation). For example: [SourceNumberMapIp2Tel] SourceNumberMapIp2Tel 0 = 22,03,$$,$$,$$,$$,2,667,$$,$$;SourceNumberMapIp2Tel 1 = 034,01,1.1.1.1,$$,0,2,$$,$$,972,$$,10; [\SourceNumberMapIp2Tel] Notes: RemoveFromLeft, RemoveFromRight, Prefix2Add, Suffix2Add, LeaveFromRight, NumberType, and NumberPlan are applied if the called and calling numbers match the DestinationPrefix, SourcePrefix, and SourceAddress conditions.
  • Page 374 Mediant 1000 & Mediant 600 ini File Parameter Description For ETSI ISDN variant, the following Number Plan and Type combinations (Plan/Type) are supported in the Destination and Source Manipulation tables: 0,0 = Unknown, Unknown 9,0 = Private, Unknown 9,1 = Private, Level 2 Regional...
  • Page 375 SIP User's Manual 4. ini File Configuration ini File Parameter Description AltRouteCauseIP2Tel This ini file table parameter configures call failure reason values received from the PSTN side (in Q.931 presentation). If a call is released as a result of one of these reasons, the device attempts to locate an alternative Trunk Group for the call in the 'IP to Trunk Group Routing' table.
  • Page 376 Mediant 1000 & Mediant 600 ini File Parameter Description Alternative Routing Parameters Determines the type of redundant routing mechanism to implement RedundantRoutingMode when a call can’t be completed using the main route. [0] = No redundant routing is used. If the call can’t be completed using the main route (using the active Proxy or the first matching rule in the internal routing table), the call is disconnected.

  • Page 377: Channel Parameters

    AnalogSignalTransportTyp For a description of this parameter, refer to "Configuring the RTP / RTCP Settings" on page 88. Note: This parameter is applicable only to Mediant 1000. FaxTransportMode For a description of this parameter, refer to ''Configuring the Fax / Modem / CID Settings'' on page 84.
  • Page 378 The range -18 to -3 corresponds to -18 dBm to -3 dBm in 1-dB steps. The default is -6 dBm fax gain control. Note: This parameter is applicable only to Mediant 1000. DetFaxOnAnswerTone For a description of this parameter, refer to ''SIP General Parameters'' on page 134.
  • Page 379 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 380 [1] = PCMLoopback, loopback the incoming PCM to the outgoing PCM. [2] = ToneInjection, generates a 1000-Hz tone to outgoing PCM. [3] = NoLoopback, (default). Note: This parameter is applicable only to Mediant 1000. EnableStandardSIDPayloa For a description of this parameter, refer to ''Configuring the RTP / dType RTCP Settings'' on page 88.
  • Page 381 Settings'' on page 81. AnswerDetectorSensitivity For a description of this parameter, refer to Configuring the Voice Settings on page 81. Note: This parameter is applicable only to Mediant 1000. For a description of this parameter, refer to ''DTMF & Dialing RFC2833PayloadType Parameters'' on page 160.
  • Page 382 MinFlashHookTime For a description of this parameter, refer to "Configuring the Hook-Flash Settings" on page 94. Note: This parameter is applicable only to Mediant 1000. FlashHookOption For a description of this parameter, refer to DTMF & Dialing Parameters on page 160.

  • Page 383: Auxiliary / Configuration Files Parameters

    FXSLoopCharacteristicsFileName The name (and path) of the file providing the FXS line characteristic parameters. Note: This parameter is applicable only to Mediant 1000. FXOLoopCharacteristicsFileName The name (and path) of the file providing the FXO line characteristic parameters.
  • Page 384 Mediant 1000 & Mediant 600 ini File Parameter Description UserInfoFileName The name (and path) of the file containing the User Information data. Determines if the device's configuration (parameters and files) is SaveConfiguration saved to flash (non-volatile memory). [0] = Configuration isn't saved to flash memory.

  • Page 385: Default Settings

    SIP User's Manual 5. Default Settings Default Settings You can restore the device's factory default settings or define your own default settings for the device. Note: You can also restore factory default settings using the device's hardware reset button (refer to the device's Fast Track Guide). Defining Default Settings The device is shipped with factory default configuration values stored on its non-volatile flash memory.
  • Page 386 Mediant 1000 & Mediant 600 Reader's Notes SIP User's Manual Document #: LTRT-83303...

  • Page 387: Auxiliary Configuration Files

    (refer to ''Loading Auxiliary Files'' on page 266). Configuring the Call Progress Tones File The Call Progress Tones (CPT) and Distinctive Ringing (applicable only to Mediant 1000) auxiliary file used by the device is a binary file (with file extension dat). This file is comprised of two sections.
  • Page 388 Mediant 1000 & Mediant 600 You can specify several tones of the same type. These additional tones are used only for tone detection. Generation of a specific tone conforms to the first definition of the specific tone. For example, you can define an additional dial tone by appending the second dial tone's definition lines to the first tone definition in the ini file.
  • Page 389 SIP User's Manual 6. Auxiliary Configuration Files • Second Signal On Time [10 msec]: 'Signal On' period (in 10 msec units) for the second cadence on-off cycle. Can be omitted if there isn't a second cadence. • Second Signal Off Time [10 msec]: 'Signal Off' period (in 10 msec units) for the second cadence on-off cycle.

  • Page 390: Configuring The Distinctive Ringing Section Of The Ini File

    10 to 200 Hz with a 5 Hz resolution. Note: Distinctive Ringing is applicable only to Mediant 1000. Each of the ringing pattern cadences is specified by the following parameters: Burst Ring On Time: Configures the cadence to be a burst cadence in the entire ringing pattern.

  • Page 391: Examples Of Ringing Signals

    SIP User's Manual 6. Auxiliary Configuration Files • Fourth (Burst) Ring On Time [10 msec]: 'Ring Off' period (in 10 msec units) for the fourth cadence on-off cycle. • Fourth (Burst) Ring Off Time [10 msec]: 'Ring Off' period (in 10 msec units) for the fourth cadence on-off cycle.

  • Page 392: Prerecorded Tones (Prt) File

    Mediant 1000 & Mediant 600 Prerecorded Tones (PRT) File The Call Progress Tones (CPT) mechanism has several limitations such as a limited number of predefined tones and a limited number of frequency integrations in one tone. To work around these limitations and provide tone generation capability that is more flexible, the Prerecorded Tones (PRT) file can be used.

  • Page 393: Coefficient File

    REN = 2. Note: The Coefficient File is applicable only to Mediant 1000. To load the coeff.dat file to the device, use the Web interface or specify the FXS coeff.dat file name in the device's ini file (refer to ''Loading Auxiliary Files'' on page 266).
  • Page 394 Mediant 1000 & Mediant 600 The following is an example of an ini file that includes these definitions. This ini file is converted (using the TrunkPack Conversion Utility - refer to the Product Reference Manual) to a binary file and loaded to the device.

  • Page 395: User Information File

    SIP User's Manual 6. Auxiliary Configuration Files User Information File The User Information file is a text file that maps PBX extensions, connected to the device, to global IP numbers. In this context, a global IP phone number (alphanumerical) serves as a routing identifier for calls in the 'IP World'.
  • Page 396 Mediant 1000 & Mediant 600 The maximum permissible size of the file is 10,800 bytes for Mediant 1000 analog modules and 108,000 bytes for digital modules. Each PBX extension registers separately (a REGISTER message is sent for each entry only if AuthenticationMode is set to Per Endpoint) using the IP number in the From / To headers.

  • Page 397: Ip Telephony Capabilities

    SIP User's Manual 7. IP Telephony Capabilities IP Telephony Capabilities This section describes the device's IP telephony capabilities. Configuring the DTMF Transport Types You can control the way DTMF digits are transported over the IP network to the remote endpoint, by using one of the following modes: Using INFO message according to Nortel IETF draft: DTMF digits are carried to the remote side in INFO messages.

  • Page 398: Fax And Modem Capabilities

    Mediant 1000 & Mediant 600 Note that to set the RFC 2833 payload type with a different value (other than its default, 96) configure the RFC2833PayloadType (RFC 2833 Payload Type) parameter. The device negotiates the RFC 2833 payload type using local and remote SDP and sends packets using the payload type from the received SDP.

  • Page 399: Fax/Modem Transport Modes

    SIP User's Manual 7. IP Telephony Capabilities remote endpoint at the establishment of the call. During a call, when a fax / modem signal is detected, transition from voice to VBD (or T.38) is automatically performed and no additional SIP signaling is required. If negotiation fails (i.e., no match is achieved for any of the transport capabilities), fallback to existing logic occurs (according to the parameter IsFaxUsed).

  • Page 400: Fax/Modem Bypass Mode

    Mediant 1000 & Mediant 600 7.2.2.1.1 Switching to T.38 Mode using SIP Re-INVITE In the Switching to T.38 Mode using SIP Re-INVITE mode, upon detection of a fax signal, the terminating device negotiates T.38 capabilities using a Re-INVITE message. If the far- end device doesn't support T.38, the fax fails.

  • Page 401: Fax / Modem Nse Mode

    Tip: When the remote (non-AudioCodes’) gateway uses G711 coder for voice and doesn’t change the coder payload type for fax or modem transmission, it is recommended to use the Bypass mode with the following configuration: •...

  • Page 402: Fax / Modem Transport Mode

    Mediant 1000 & Mediant 600 When configured for NSE mode, the device includes in its SDP the following line: a=rtpmap:100 X-NSE/8000 (where 100 is the NSE payload type) The Cisco gateway must include the following definition: "modem passthrough nse payload-type 100 codec g711alaw".

  • Page 403: Fax / Modem Transparent Mode

    SIP User's Manual 7. IP Telephony Capabilities Echo Canceller = on Silence Compression = off Echo Canceller Non-Linear Processor Mode = off Dynamic Jitter Buffer Minimum Delay = 40 Dynamic Jitter Buffer Optimization Factor = 13 When the device initiates a fax session using G.711, a ‘gpmd’ attribute is added to the SDP according to the following format: For G.711A-law: a=gpmd:0 vbd=yes;ecan=on For G.711 µ-law: a=gpmd:8 vbd=yes;ecan=on...

  • Page 404: Fax / Modem Transparent With Events Mode

    Mediant 1000 & Mediant 600 7.2.2.7 Fax / Modem Transparent with Events Mode In this mode, fax and modem signals are transferred using the current voice coder with the following automatic adaptations: Echo Canceller = on (or off, for modems)

  • Page 405: Supporting V.152 Implementation

    SIP User's Manual 7. IP Telephony Capabilities Configure the following parameters to use bypass mode for V.34 faxes and T.38 for T.30 faxes: FaxTransportMode = 1 (Relay) V34ModemTransportType = 2 (Modem bypass) V32ModemTransportType = 2 V23ModemTransportType = 2 V22ModemTransportType = 2 7.2.3.2 Using Relay mode for both T.30 and V.34 faxes In this scenario, V.34 fax machines are forced to use their backward compatibility with T.30...

  • Page 406: Fxo Operating Modes

    This section provides a description of the FXO operating modes and device configurations for Tel-to-IP and IP-to-Tel calls. Note: This section is applicable only to Mediant 1000. 7.3.1 IP-to-Telephone Calls The FXO device provides the following operating modes for IP-to-Tel calls: One-stage dialing (refer to ''One-Stage Dialing'' on page 406) •...

  • Page 407: Figure 7-1: Call Flow For One-Stage Dialing

    SIP User's Manual 7. IP Telephony Capabilities Figure 7-1: Call Flow for One-Stage Dialing One-stage dialing incorporates the following FXO functionality: Waiting for Dial Tone: Enables the device 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 408: Two-Stage Dialing

    Mediant 1000 & Mediant 600 7.3.1.2 Two-Stage Dialing Two-stage dialing is when the IP caller is required to dial twice. The caller initially dials to the FXO device and only after receiving a dial tone from the PBX (via the FXO device), dials the destination telephone number.

  • Page 409: Did Wink

    SIP User's Manual 7. IP Telephony Capabilities Relevant parameters: EnableReversalPolarity, EnableCurrentDisconnect, CurrentDisconnectDuration, CurrentDisconnectDefaultThreshold, and TimeToSampleAnalogLineVoltage. Detection of Reorder, Busy, Dial, and Special Information Tone (SIT) tones: The call is immediately disconnected after a Reorder, Busy, Dial, or SIT tone is detected on the Tel side (assuming the PBX / CO generates this tone).

  • Page 410: Telephone-To-Ip Calls

    Mediant 1000 & Mediant 600 The "start dial" signal is a wink from the PBX to the FXO device. The FXO then sends the last four to five DTMF digits of the called number. The PBX uses these digits to complete...

  • Page 411: Collecting Digits Mode

    SIP User's Manual 7. IP Telephony Capabilities 7.3.2.2 Collecting Digits Mode When automatic dialing is not defined, the device collects the digits. The SIP call flow diagram below illustrates the Collecting Digits Mode. Figure 7-3: Call Flow for Collecting Digits Mode 7.3.2.3 Ring Detection Timeout The ini file parameters IsWaitForDialTone and WaitForDialTone apply to Ring Detection...

  • Page 412: Fxo Supplementary Services

    Mediant 1000 & Mediant 600 7.3.2.4 FXO Supplementary Services The FXO supplementary services include the following: 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-...
  • Page 413 SIP User's Manual 7. IP Telephony Capabilities The X-Detect event notification process is as follows: For IP-to-Tel or Tel-to-IP calls, the device 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 414: Rtp Multiplexing (Throughpacket)

    Mediant 1000 & Mediant 600 RTP Multiplexing (ThroughPacket) The device supports a proprietary method to aggregate RTP streams from several channels to reduce the bandwidth overhead caused by the attached Ethernet, IP, UDP, and RTP headers, and to reduce the packet / data transmission rate. This option reduces the load on network routers and can typically save 50% (e.g., for G.723) on IP bandwidth.

  • Page 415: Configuring Alternative Routing (Based On Connectivity And Qos)

    SIP User's Manual 7. IP Telephony Capabilities The default settings of 10 msec Minimum delay and 10 Optimization Factor should provide a good compromise between delay and error rate. The jitter buffer ‘holds’ incoming packets for 10 msec before making them available for decoding into voice. The coder polls frames from the buffer at regular intervals in order to produce continuous speech.

  • Page 416: Determining The Availability Of Destination Ip Addresses

    Mediant 1000 & Mediant 600 Destination IP address is disallowed if no ping to the destination is available (ping is continuously initiated every seven seconds), when an inappropriate level of QoS was detected, or when a DNS host name is not resolved. The QoS level is calculated according to delay or packet loss of previously ended calls.

  • Page 417: Call Detail Record

    ‘34’, the SIP 503 response is sent. Other causes can be used as well. Note: This section is applicable only to Mediant 1000. Call Detail Record The Call Detail Record (CDR) contains vital statistic information on calls made by the device.
  • Page 418 Mediant 1000 & Mediant 600 Field Name Description DstPhoneNum Destination Phone Number Destination Number Before Manipulation DstNumBeforeMap Durat Call Duration Coder Selected Coder Packet Interval Intrv RtpIp RTP IP Address Port Remote RTP Port Initiator of Call Release (IP, Tel, Unknown)

  • Page 419: Supported Radius Attributes

    SIP User's Manual 7. IP Telephony Capabilities 7.10 Supported RADIUS Attributes Use the following table for explanations on the RADIUS attributes contained in the communication packets transmitted between the device and a RADIUS Server. Table 7-3: Supported RADIUS Attributes Attribute Attribute Value Purpose...
  • Page 420 Mediant 1000 & Mediant 600 Attribute Attribute Value Purpose Example Number Name Format Destination phone number String 2427456425 Stop Acc Calling- Start Acc Calling Party Number (ANI) String 5135672127 Station-ID Stop Acc Account Request Type (start or stop) Acct-Status- 1: start, 2: Start Acc Note: ‘start’...

  • Page 421: Trunk-To-Trunk Routing Example

    SIP User's Manual 7. IP Telephony Capabilities Below is an example of RADIUS Accounting, where the non-standard parameters are preceded with brackets. Accounting-Request (361) user-name = 111 acct-session-id = 1 nas-ip-address = 212.179.22.213 nas-port-type = 0 acct-status-type = 2 acct-input-octets = 4841 acct-output-octets = 8800 acct-session-time = 1 acct-input-packets = 122...

  • Page 422: Proxy Or Registrar Registration Example

    Mediant 1000 & Mediant 600 At Device B, route IP-to-PSTN calls to Trunk Group ID according to the first digit of the called number: • PSTNPrefix = 1,1 • PSTNPrefix = 2,2 • PSTNPrefix = 3,4 • PSTNPrefix = 4,4...

  • Page 423: Configuration Examples

    SIP User's Manual 7. IP Telephony Capabilities REGISTER messages are sent to the Registrar's IP address (if configured) or to the Proxy's IP address. A single message is sent once per device, or messages are sent per B-channel according to the parameter AuthenticationMode. There is also an option to configure registration mode per Trunk Group using the TrunkGroupSettings table.
  • Page 424 Mediant 1000 & Mediant 600 F1 (10.8.201.108 >> 10.8.201.10 INVITE): INVITE sip:1000@10.8.201.10;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.8.201.108;branch=z9hG4bKacsiJkDGd From: <sip:8000@10.8.201.108>;tag=1c5354 To: <sip:1000@10.8.201.10> Call-ID: 534366556655skKw-8000--1000@10.8.201.108 CSeq: 18153 INVITE Contact: <sip:8000@10.8.201.108;user=phone> User-Agent: Audiocodes-Sip-Gateway/Mediant 1000/v.5.40.010.006 Supported: 100rel,em Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE, NOTIFY,PRACK,REFER,INFO Content-Type: application/sdp Content-Length: 208 o=AudiocodesGW 18132 74003 IN IP4 10.8.201.108 s=Phone-Call c=IN IP4 10.8.201.108...
  • Page 425 F4 (10.8.201.10 >> 10.8.201.108 200 OK): SIP/2.0 200 OK Via: SIP/2.0/UDP 10.8.201.108;branch=z9hG4bKacsiJkDGd From: <sip:8000@10.8.201.108>;tag=1c5354 To: <sip:1000@10.8.201.10>;tag=1c7345 Call-ID: 534366556655skKw-8000--1000@10.8.201.108 CSeq: 18153 INVITE Contact: <sip:1000@10.8.201.10;user=phone> Server: Audiocodes-Sip-Gateway/Mediant 1000/v.5.40.010.006 Supported: 100rel,em Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE, NOTIFY,PRACK,REFER,INFO Content-Type: application/sdp Content-Length: 206 o=AudiocodesGW 30221 87035 IN IP4 10.8.201.10 s=Phone-Call c=IN IP4 10.8.201.10...

  • Page 426: Sip Authentication Example

    Mediant 1000 & Mediant 600 F7 (10.8.201.10 >> 10.8.201.108 200 OK): SIP/2.0 200 OK Via: SIP/2.0/UDP 10.8.201.108;branch=z9hG4bKacRKCVBud From: <sip:8000@10.8.201.108>;tag=1c5354 To: <sip:1000@10.8.201.10>;tag=1c7345 Call-ID: 534366556655skKw-8000--1000@10.8.201.108 Server: Audiocodes-Sip-Gateway/Mediant 1000/v.5.40.010.006 CSeq: 18154 BYE Supported: 100rel,em Content-Length: 0 7.13.2 SIP Authentication Example The device supports basic and digest (MD5) authentication types, according to SIP RFC 3261 standard.
  • Page 427 Since the algorithm is MD5, then: • The username is equal to the endpoint phone number 122. • The realm return by the proxy is audiocodes.com. • The password from the ini file is AudioCodes. • The equation to be evaluated is (according to RFC this part is called A1) ‘122:audiocodes.com:AudioCodes’.

  • Page 428: Establishing A Call Between Two Devices

    Expires: Thu, 26 Jul 2001 10:34:42 GMT 7.13.3 Establishing a Call between Two Devices This section provides an example on configuring two AudioCodes' devices with FXS interfaces for establishing call communication. After configuration, you can make calls between telephones connected to the same device or between the two devices.

  • Page 429: Remote Pbx Extension Between Fxo And Fxs Devices

    FXS device. The routing is transparent as if the telephone connected to the FXS device is directly connected to the PBX. Note: This section is applicable only to Mediant 1000. The following is required: FXO interfaces with ports connected directly to the PBX lines (shown in the figure...

  • Page 430: Dialing From Remote Extension (Phone At Fxs)

    Mediant 1000 & Mediant 600 Analog phones (POTS) PBX (one or more PBX loop start lines) LAN network Figure 7-8: FXO-FXS Remote PBX Extension (Example) 7.13.4.1 Dialing from Remote Extension (Phone at FXS) The procedure below describes how to dial from the 'remote PBX extension' (i.e., phone connected to the FXS interface).

  • Page 431: Dialing From Pbx Line Or Pstn

    SIP User's Manual 7. IP Telephony Capabilities 7.13.4.2 Dialing from PBX Line or PSTN The procedure below describes how to dial from a PBX line (i.e., from a telephone directly connected to the PBX) or from the PSTN to the 'remote PBX extension' (i.e., telephone connected to the FXS interface).

  • Page 432: Call Waiting For Remote Extensions

    Mediant 1000 & Mediant 600 7.13.4.4 Call Waiting for Remote Extensions When the FXO device detects a Call Waiting indication (FSK data of the Caller Id - CallerIDType2) from the PBX, it sends a proprietary INFO message, which includes the caller identification to the FXS device.

  • Page 433: Fxo Gateway Configuration

    SIP User's Manual 7. IP Telephony Capabilities In the ‘Tel to IP Routing’ page (refer to ''Tel to IP Routing Table'' on page 200), enter 20 for the destination phone prefix, and 10.1.10.2 for the IP address of the FXO device.

  • Page 434: Sip Trunking Between Enterprise And Itsps

    Mediant 1000 & Mediant 600 In the ‘FXO Settings’ page (refer to ''Configuring the FXO Parameters'' on page 248), set the parameter ‘Dialing Mode’ to ‘Two Stages’ (IsTwoStageDial = 1). 7.13.5 SIP Trunking between Enterprise and ITSPs By implementing the device's enhanced and flexible routing configuration capabilities using Proxy Sets, IP Groups, and Accounts, you can "design"...

  • Page 435: Figure 7-17: Configuring Proxy Set Id #1 In The Proxy Sets Table

    SIP User's Manual 7. IP Telephony Capabilities To configure call routing between Enterprise and two ITSPs using the device, take these 8 steps: Enable the device to register to a Proxy / Registrar server, using the parameter IsRegisterNeeded in the 'Proxy & Registration' page (refer to ''Proxy & Registration Parameters'' on page 146).

  • Page 436: Figure 7-19: Assign The Trunk To Trunk Group Id #1 In The Trunk Group Table

    Mediant 1000 & Mediant 600 In the 'Trunk Group Table' page (refer to "Configuring the Trunk Group Table" on page 226), enable the Trunks connected between the Enterprise's PBX and the device (Trunk Group ID #1), and between the local PSTN and the device (Trunk Group ID #2).

  • Page 437: Working With Supplementary Services

    SIP User's Manual 7. IP Telephony Capabilities 7.14 Working with Supplementary Services The device supports the following supplementary services: Call Hold and Retrieve (refer to ''Call Hold and Retrieve'' on page 437). Consultation / Alternate (refer to "Consultation / Alternate" on page 438). Call Transfer (refer to ''Call Transfer'' on page 438).

  • Page 438: Consultation / Alternate

    After the consultation call is connected, the user can switch between the held and active call by pressing hook-flash. Note: This section is applicable only to Mediant 1000. 7.14.3 Call Transfer There are two types of call transfers: Consultation Transfer (REFER and REPLACES):...

  • Page 439: Call Forward

    Notes: • This section is applicable only to Mediant 1000. • When call forward is initiated, the device sends a SIP 302 response with a contact that contains the phone number from the forward table and its corresponding IP address from the routing table (or when a proxy is used, the proxy’s IP address).

  • Page 440: Call Waiting

    Ringback Tone. The called party can accept the new call using hook-flash, and can toggle between the two calls. Note: This section is applicable only to Mediant 1000. To enable Call Waiting: Set EnableCallWaiting = 1 (or using the Web interface, refer to ''Supplementary Services'' on page 176) Set EnableHold = 1.

  • Page 441: Caller Id

    This section discusses the device's Caller ID support for analog modules. Note: This section is applicable only to Mediant 1000. 7.14.7.1 Caller ID Detection / Generation on the Tel Side By default, generation and detection of Caller ID to the Tel side is disabled. To enable Caller ID, set the parameter EnableCallerID to 1.

  • Page 442: Debugging A Caller Id Detection On Fxo

    Mediant 1000 & Mediant 600 The configuration for Caller ID is described below: Use the parameter CallerIDType to define the Caller ID standard. Note that the Caller ID standard that is used on the PBX or phone must match the standard defined in the device.

  • Page 443: Caller Id On The Ip Side

    PC. Capture the RTP using Wireshark (you can also use DSP trace) and send the file to AudioCodes. 7.14.7.3 Caller ID on the IP Side Caller ID is provided by the From header containing the caller's name and "number", for example: From: “David”...
  • Page 444 Mediant 1000 & Mediant 600 The value of the ‘Presentation’ field that is defined in the ‘Caller Display Information’ table can be overridden by configuring the ‘Presentation’ parameter in the ‘Tel to IP Source Number Manipulation’ table. Therefore, this table can be used to set the presentation for specific calls according to Source / Destination prefixes.

  • Page 445: Networking Capabilities

    SIP User's Manual 8. Networking Capabilities Networking Capabilities Ethernet Interface Configuration The device's Ethernet connection can be configured (using the ini file parameter EthernetPhyConfiguration) for one of the following modes: Manual mode: • 10Base-T Half-Duplex or 10Base-T Full-Duplex • 100Base-TX Half-Duplex or 100Base-TX Full-Duplex Auto-Negotiation: chooses common transmission parameters such as speed and duplex mode Auto-Negotiation falls back to Half-Duplex mode when the opposite port is not in Auto-...

  • Page 446: Nat (Network Address Translation) Support

    Mediant 1000 & Mediant 600 When the CPU module loses all Ethernet connectivity, a Critical alarm is generated: When MIIRedundancyEnable is disabled: the alarm is generated when the single physical connection is lost. The alarm is cleared when the single physical connection is restored.

  • Page 447: Stun

    SIP User's Manual 8. Networking Capabilities 8.3.1 STUN Simple Traversal of UDP through NATs (STUN), based on RFC 3489 is a client / server protocol that solves most of the NAT traversal problems. The STUN server operates in the public Internet and the STUN clients are embedded in end-devices (located behind NAT). STUN is used both for the signaling and the media streams.

  • Page 448: First Incoming Packet Mechanism

    No-Op packets are sent. This is performed using the RTPNoOpPayloadType ini parameter (refer to ''Networking Parameters'' on page 296). AudioCodes’ default payload type is 120. T.38 No-Op: T.38 No-Op packets are sent only while a T.38 session is activated. Sent packets are a duplication of the previously sent frame (including duplication of the sequence number).

  • Page 449: Robust Reception Of Rtp Streams

    SIP User's Manual 8. Networking Capabilities Robust Reception of RTP Streams This mechanism filters out unwanted RTP streams that are sent to the same port number on the device. These multiple RTP streams can result from traces of previous calls, call control errors, and deliberate attacks.

  • Page 450: Ip Qos Via Differentiated Services (Diffserv)

    Mediant 1000 & Mediant 600 The client requests a time update from a specified NTP server at a specified update interval. In most situations, this update interval is every 24 hours based on when the system was restarted. The NTP server identity (as an IP address) and the update interval...

  • Page 451: Ieee 802.1P/Q (Vlans And Priority)

    SIP User's Manual 8. Networking Capabilities Dual IP mode: The device is assigned two IP addresses for the different traffic types. One IP address is assigned to a combination of two traffic types (Media and Control, OAMP and Control, or OAMP and Media), while the other IP address is assigned to whichever traffic type not included in this combination.

  • Page 452: Figure 8-1: Multiple Network Interfaces And Vlans

    Mediant 1000 & Mediant 600 Media traffic type is assigned ‘Premium media’ CoS, Management traffic type is assigned ‘Bronze’ CoS, and Control traffic type is assigned ‘Premium control’ CoS. For example, RTP/RTCP traffic is assigned the Media VLAN ID and ‘Premium media’ CoS, whereas Web traffic is assigned the Management VLAN ID and ‘Bronze’...

  • Page 453: Getting Started With Vlans And Multiple Ips

    SIP User's Manual 8. Networking Capabilities Application Traffic / Network Types Class-of-Service (Priority) Web server (HTTP) Management Bronze SNMP GET/SET Management Bronze Web server (HTTPS) Management Bronze IPSec IKE Determined by the service Determined by the service RTP traffic Media Premium media RTCP traffic Media...

  • Page 454: Integrating Using The Web Interface

    Mediant 1000 & Mediant 600 Table 8-2: Example of VLAN and Multiple IPs Configuration Network Default Gateway External Routing IP Address Subnet Mask VLAN ID Type IP Address Rule OAMP 10.31.174.50 255.255.0.0 0.0.0.0 83.4.87.X Control 10.32.174.50 255.255.0.0 0.0.0.0 130.33.4.6 Media 10.33.174.50...

  • Page 455: Figure 8-3: Oam, Control, Media Ip Configuration In The Ip Settings

    SIP User's Manual 8. Networking Capabilities Configure the multiple IP parameters by completing the following steps: In the ‘IP Settings’ page, modify the IP parameters to correspond to the values shown in the figure below. Note that the OAM, Control, and Media Network Settings parameters appear only after you select the options ‘Multiple IP Networks’...

  • Page 456: Integrating Using The Ini File

    Mediant 1000 & Mediant 600 Configure the 'IP Routing' table to define static routing rules for the OAMP and Control networks, since a default gateway isn’t supported on these networks: Open the ‘IP Routing Table’ page (refer to ''Configuring the IP Routing Table'' on page 75).
  • Page 457 SIP User's Manual 8. Networking Capabilities Below is an example of an ini file containing VLAN and Multiple IPs parameters: ; Interface Table Configuration: [InterfaceTable] FORMAT InterfaceTable_Index = InterfaceTable_ApplicationTypes, InterfaceTable_IPv6InterfaceMode, InterfaceTable_IPAddress, InterfaceTable_PrefixLength, InterfaceTable_Gateway, InterfaceTable_VlanID, InterfaceTable_InterfaceName; InterfaceTable 0 = 0, 0, 10.31.174.50, 16, 0.0.0.0, 4, OAMP; InterfaceTable 0 = 1, 0, 10.33.174.50, 16, 10.33.0.1, 6, Media;...
  • Page 458 Mediant 1000 & Mediant 600 Instead of using the ini file table parameter InterfaceTable, you can configure multiple IPs and VLANs using the individual ini file parameters, as shown below: ; VLAN Configuration VlanMode=1 VlanOamVlanId=4 VlanNativeVlanId=4 VlanControlVlanId=5 VlanMediaVlanID=6 ; Multiple IPs Configuration EnableMultipleIPs=1 LocalMediaIPAddress=10.33.174.50...

  • Page 459: Advanced Pstn Configuration

    SIP User's Manual 9. Advanced PSTN Configuration Advanced PSTN Configuration Clock Settings The device's clock settings can be configured to either generate its own timing signals, use an internal clock, or recover them from one of the E1/T1 trunks. To use the device's internal clock source, configure the following parameters: TDMBusClockSource = 1 ClockMaster = 1 (for all trunks)

  • Page 460: Reason Header

    Mediant 1000 & Mediant 600 It is also possible to map the less commonly used SIP Responses to a single default ISDN Release Cause. Use the parameter DefaultCauseMapISDN2IP (described in ''ISDN and CAS Interworking-Related Parameters'' on page 348) to define a default ISDN Cause that is always used except when the following Release Causes are received: Normal Call Clearing (16), User Busy (17), No User Responding (18) or No Answer from User (19).
  • Page 461 SIP User's Manual 9. Advanced PSTN Configuration ISDN Release Description Description Reason Response Non-selected user clearing Not found Destination out of order Bad gateway Address incomplete Address incomplete Facility rejected Not implemented Response to status enquiry 501* Not implemented Normal unspecified Temporarily unavailable No circuit available Service unavailable...

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

    Mediant 1000 & Mediant 600 ISDN Release Description Description Reason Response Invalid message Service unavailable Mandatory information element is missing 409* Conflict Message type non-existent or not 480* Temporarily not available implemented Message not compatible with call state or message type non-existent or not...

  • Page 463: Isdn Overlap Dialing

    SIP User's Manual 9. Advanced PSTN Configuration ISDN Release SIP Response Description Description Reason Unsupported media type Service/option not implemented Bad extension Interworking Temporarily unavailable No user responding Call leg/transaction doesn’t 481* Interworking exist 482* Loop detected Interworking Too many hops Interworking Address incomplete Invalid number format...

  • Page 464: Using Isdn Nfas

    Mediant 1000 & Mediant 600 The device stops collecting digits (for ISDN-to-IP calls) when: The sending device transmits a ‘sending complete’ IE in the ISDN Setup or the following INFO messages to signal that no more digits are going to be sent.

  • Page 465: Nfas Interface Id

    SIP User's Manual 9. Advanced PSTN Configuration For example, to assign the first four T1 trunks to NFAS group #1, in which trunk #0 is the primary trunk and trunk #1 is the backup trunk, use the following configuration: NFASGroupNumber_0 = 1 NFASGroupNumber_1 = 1 NFASGroupNumber_2 = 1 NFASGroupNumber_3 = 1...

  • Page 466: Working With Dms-100 Switches

    Mediant 1000 & Mediant 600 9.4.2 Working with DMS-100 Switches The DMS-100 switch requires the following NFAS Interface ID definitions: InterfaceID #0 for the Primary trunk InterfaceID #1 for the Backup trunk InterfaceID #2 for a 24 B-channel T1 trunk...
  • Page 467 SIP User's Manual 9. Advanced PSTN Configuration To stop / delete an NFAS Group, take these 3 steps: Stop / delete all NFAS (‘slave’) trunks. Stop / delete the backup trunk if a backup trunk exists. Stop / delete the primary trunk. Notes: •...

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

    Mediant 1000 & Mediant 600 Redirect Number and Calling Name (Display) The following tables define the device's redirect number and calling name (Display) support for various PRI variants according to NT (Network Termination) / TE (Termination Equipment) interface direction: Table 9-3: Calling Name (Display)

  • Page 469: Media Server Capabilities

    IP-to-IP Transcoding (refer to ''IP-to-IP Transcoding'' on page 494) Note: This section is applicable only to Mediant 1000. The device conference, transcoding, announcement and media server applications can be used separately, each on a different platform, or all on the same device. The SIP URI name in the INVITE message is used to identify the resource (media server, conference or announcement) to which the SIP session is addressed.

  • Page 470: Simple Conferencing (Netann)

    Mediant 1000 & Mediant 600 10.1.1 Simple Conferencing (NetAnn) 10.1.1.1 SIP Call Flow Figure 10-1: Simple Conferencing SIP Call Flow 10.1.1.2 Creating a Conference The device creates a conference call when the first user joins the conference. To create a conference, the Application Server sends a regular SIP INVITE message to the device.

  • Page 471: Joining A Conference

    SIP User's Manual 10. Media Server Capabilities INVITE sip: conf100@audiocodes.com SIP/2.0 By default, a request to create a conference reserves three resources on the device. It is possible to reserve a larger number of resources in advance by adding the number of required participants to the User Part of the Request-URI.

  • Page 472: Pstn Participants

    Mediant 1000 & Mediant 600 10.1.1.5 PSTN Participants Adding PSTN participants is done by performing a loopback from the IP side (the device's IP address is configured in the 'Tel to IP Routing' table). 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 473: Figure 10-2: Advanced Conferencing Sip Call Flow

    SIP User's Manual 10. Media Server Capabilities Figure 10-2: Advanced Conferencing SIP Call Flow 10.1.2.2 Joining a Conference To join an existing conference, the Application Server sends a SIP INVITE message with the same Request-URI as the one that created the conference. The INVITE message may include a <configure_leg>...

  • Page 474: Modifying A Conference

    Mediant 1000 & Mediant 600 10.1.2.3 Modifying a Conference To modify an existing conference, INFO messages are used. Each INFO message carries an MSCML request. The MSCML response is included in an INFO message back from the device to the Application Server. It is possible to modify an entire conference (by issuing requests on the Control Leg) or only a certain participant (by issuing requests on that specific leg).

  • Page 475: Active Speaker Notification

    SIP User's Manual 10. Media Server Capabilities Figure 10-4: Applying Media Services on a Conference -- SIP Call Flow 10.1.2.5 Active Speaker Notification After an advanced conference is established, the Application Server can subscribe to the device to receive notifications of the current set of active speakers in a conference at any given moment.

  • Page 476: Terminating A Conference

    Mediant 1000 & Mediant 600 10.1.2.6 Terminating a Conference To remove a leg from a conference, the Application Server issues a SIP BYE request on the selected dialog representing the conference leg. The Application Server can terminate all legs in a conference by issuing a SIP BYE request on the Control Leg. If one or more...

  • Page 477: Conference Call Flow Example

    SIP User's Manual 10. Media Server Capabilities 10.1.3 Conference Call Flow Example The call flow, shown in the following figure, describes SIP messages exchanged between the device (10.8.58.4) and three conference participants (10.8.29.1, 10.8.58.6 and 10.8.58.8). Figure 10-6: Conference Call Flow Example Version 5.4 May 2008...

  • Page 478: Mediant 1000 & Mediant

    Mediant 1000 & Mediant 600 SIP MESSAGE 1: 10.8.29.1:5060 -> 10.8.58.4:5060 INVITE sip:conf100@10.8.58.4;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.8.29.1;branch=z9hG4bKacRHmJhMj Max-Forwards: 70 From: <sip:100@10.8.8.10>;tag=1c352329022 To: <sip:conf100@10.8.58.4;user=phone> Call-ID: 1792526528qlax@10.8.29.1 CSeq: 1 INVITE Contact: <sip:100@10.8.29.1> Supported: em,100rel,timer,replaces,path Allow:REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,IN FO,SUBSCRIBE,UPDATE User-Agent: Audiocodes-Sip-Gateway-Mediant 1000/v.5.40.010.006 Content-Type: application/sdp Content-Length: 216 o=AudiocodesGW 663410 588654 IN IP4 10.8.29.1...
  • Page 479 From: <sip:100@10.8.8.10>;tag=1c352329022 To: <sip:conf100@10.8.58.4;user=phone>;tag=1c222574568 Call-ID: 1792526528qlax@10.8.29.1 CSeq: 1 ACK Contact: <sip:100@10.8.29.1> Supported: em,timer,replaces,path Allow:REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,IN FO,SUBSCRIBE,UPDATE User-Agent: Audiocodes-Sip-Gateway-Mediant 1000/v.5.40.010.006 Content-Length: 0 SIP MESSAGE 5: 10.8.58.6:5060 -> 10.8.58.4:5060 INVITE sip:conf100@10.8.58.4;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.8.58.6;branch=z9hG4bKacfowEuut Max-Forwards: 70 From: <sip:600@10.8.8.10>;tag=1c201038291 To: <sip:conf100@10.8.58.4;user=phone> Call-ID: 1008914574iYgW@10.8.58.6 CSeq: 1 INVITE Contact: <sip:600@10.8.58.6>...
  • Page 480 Mediant 1000 & Mediant 600 SIP MESSAGE 7: 10.8.58.4:5060 -> 10.8.58.6:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP 10.8.58.6;branch=z9hG4bKacfowEuut From: <sip:600@10.8.8.10>;tag=1c201038291 To: <sip:conf100@10.8.58.4;user=phone>;tag=1c1673415884 Call-ID: 1008914574iYgW@10.8.58.6 CSeq: 1 INVITE Contact: <sip:conf100@10.8.58.4> Supported: em,timer,replaces,path Allow:REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,IN FO,SUBSCRIBE,UPDATE Server: Audiocodes-Sip-Gateway-Mediant 1000/v.5.40.010.006 Content-Type: application/sdp Content-Length: 236 v=0 o=AudiocodesGW 886442 597756 IN IP4 10.8.58.4 s=Phone-Call c=IN IP4 10.8.58.4...
  • Page 481 Via: SIP/2.0/UDP 10.8.58.8;branch=z9hG4bKaczJpxnnv From: <sip:800@10.8.58.8>;tag=1c2419012378 To: <sip:conf100@10.8.58.4;user=phone>;tag=1c3203015250 Call-ID: 150852731NDDC@10.8.58.8 CSeq: 1 INVITE Supported: em,timer,replaces,path Allow:REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,IN FO,SUBSCRIBE,UPDATE Server: Audiocodes-Sip-Gateway-Mediant 1000/v.5.40.010.006 Content-Length: 0 SIP MESSAGE 11: 10.8.58.4:5060 -> 10.8.58.8:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP 10.8.58.8;branch=z9hG4bKaczJpxnnv From: <sip:800@10.8.58.8>;tag=1c2419012378 To: <sip:conf100@10.8.58.4;user=phone>;tag=1c3203015250 Call-ID: 150852731NDDC@10.8.58.8 CSeq: 1 INVITE Contact: <sip:conf100@10.8.58.4>...
  • Page 482 Mediant 1000 & Mediant 600 SIP MESSAGE 13: 10.8.58.8:5060 -> 10.8.58.4:5060 BYE sip:conf100@10.8.58.4 SIP/2.0 Via: SIP/2.0/UDP 10.8.58.8;branch=z9hG4bKackSIyGww Max-Forwards: 70 From: <sip:800@10.8.58.8>;tag=1c2419012378 To: <sip:conf100@10.8.58.4;user=phone>;tag=1c3203015250 Call-ID: 150852731NDDC@10.8.58.8 CSeq: 2 BYE Contact: <sip:800@10.8.58.8> Supported: em,timer,replaces,path Allow:REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,IN FO,SUBSCRIBE,UPDATE User-Agent: Audiocodes-Sip-Gateway-Mediant 1000/v.5.40.010.006 Content-Length: 0 SIP MESSAGE 14: 10.8.58.4:5060 -> 10.8.58.8:5060 SIP/2.0 200 OK...

  • Page 483: Announcement Server

    SIP INVITE message with SIP URI that includes the NetAnn Announcement Identifier name. For example: INVITE sip:annc@audiocodes.com; play=file://12 SIP/2.0 The left part of the SIP URI includes the string ‘annc’. In the example above, the device starts playing announcement number 12 from the internal Voice Prompts file (file:// and http://localhost formats are supported).

  • Page 484: Supported Attributes

    Mediant 1000 & Mediant 600 Notes: • A 200 OK message is sent only after the HTTP connection is successfully established and the requested file is found. If the file isn’t found, a 404 Not Found response is sent. •...

  • Page 485: Operation

    SIP User's Manual 10. Media Server Capabilities The following figure illustrates standard MSCML application architecture: Figure 10-7: MSCML Architecture The architecture comprises the following components: device: Operating independently, the device controls and allocates its processing resources to match each application’s requirements. Its primary role is to handle requests from the Application server for playing announcements and collecting digits.
  • Page 486 Mediant 1000 & Mediant 600 An alternative method uses the AutoUpdate mechanism as described in Automatic Update Mechanism. Both the vp.dat and segments.xml file that were previously created using the APS should be located on an external storage server (HTTP, FTP). At startup, the device fetches the files from the remote storage.
  • Page 487 SIP User's Manual 10. Media Server Capabilities The <Play>, <PlayCollect>, and <PlayRecord> messages are composed of two sections: Attributes and a Prompt block (the request can contain several different Prompt blocks). The Attributes section includes several request-specific parameters. The Prompt block section itself is also composed of two sections: prompt-specific parameters and audio segments (audio / variable).

  • Page 488: Playing Announcements

    Mediant 1000 & Mediant 600 10.2.2.2 Playing Announcements A <Play> request is used to play an announcement to the caller. Each <Play> request contains a single Prompt block and the following request-specific parameters: id: an optional random number used to synchronize request and response.
  • Page 489 SIP User's Manual 10. Media Server Capabilities extradigittimer: used to enable the following: • Detection of command keys (ReturnKey and EscapeKey). • Not report the shortest match. MGCP Digitmap searches for the shortest possible match. This means that if a digitmap of (123 | 1234) is defined, once the user enters 123, a match is found and a response is sent.

  • Page 490: Playing Announcements And Recording Voice

    Mediant 1000 & Mediant 600 10.2.2.4 Playing Announcements and Recording Voice The <PlayRecord> request is used to play an announcement to the caller and to then record the voice stream associated with that caller. The play part of the <PlayRecord>...

  • Page 491: Stopping The Playing Of An Announcement

    SIP User's Manual 10. Media Server Capabilities An example is shown below of an MSCML <PlayRecord> Response: <?xml version="1.0" encoding="utf-8"?> <MediaServerControl version="1.0"> <response request=“playrecord” id=”75899” code=”200” text=”OK” reclength=”15005”> </response> </MediaServerControl> 10.2.2.5 Stopping the Playing of an Announcement The Application server issues a <stop> request when it requires that the device stops a request in progress and not initiate another operation.

  • Page 492: Announcement Call Flow Example

    The call flow, shown in the following figure, describes SIP messages exchanged between the device (10.33.24.1) and a SIP client (10.33.2.40) requesting to play local announcement #1 (10.8.25.17) using AudioCodes proprietary method. SIP MESSAGE 1: 10.33.2.40:5060 -> 10.33.24.1:5060 INVITE sip:annc@10.33.24.1;play=http://10.3.0.2/hello.wav;repeat=2 SIP/2.0...
  • Page 493 SIP MESSAGE 4: 10.33.2.40:5060 -> 10.33.24.1:5060 ACK sip:10.33.24.1 SIP/2.0 Via: SIP/2.0/UDP 10.33.2.40;branch=z9hG4bKacnNUEeKP Max-Forwards: 70 From: <sip:103@10.33.2.40>;tag=1c2917829348 To: <sip:annc@10.33.24.1>;tag=1c1528117157 Call-ID: 1414622340oZZq@10.33.2.40 CSeq: 1 ACK Contact: <sip:103@10.33.2.40> Supported: em,timer,replaces,path Allow:REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,IN FO,SUBSCRIBE,UPDATE User-Agent: Audiocodes-Sip-Gateway-4.0 GA/v.4.0 GA Content-Length: 0 Version 5.4 May 2008...

  • Page 494: Ip-To-Ip Transcoding

    Mediant 1000 & Mediant 600 SIP MESSAGE 5: 10.33.24.1:5060 -> 10.33.2.40:5060 BYE sip:103@10.33.2.40 SIP/2.0 Via: SIP/2.0/UDP 10.33.24.1;branch=z9hG4bKacFhtFbFR Max-Forwards: 70 From: <sip:annc@10.33.24.1>;tag=1c1528117157 To: <sip:103@10.33.2.40>;tag=1c2917829348 Call-ID: 1414622340oZZq@10.33.2.40 CSeq: 1 BYE Contact: <sip:10.33.24.1> Supported: em,timer,replaces,path Allow:REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,IN FO,SUBSCRIBE,UPDATE User-Agent: Audiocodes-Sip-Gateway-TrunkPack 1610/v.4.60AOH.006.002D Content-Length: 0 SIP MESSAGE 6: 10.33.2.40:5060 -> 10.33.24.1:5060 SIP/2.0 200 OK...

  • Page 495: Figure 10-8: Direct Connection (Example)

    SIP User's Manual 10. Media Server Capabilities The device uses two media (DSP) channels for each call, thereby reducing the number of available Transcoding sessions to half of the defined value for MediaChannels. To limit the number of resources available for Transcoding, use the ini file parameter MediaChannels or Web interface (refer to ''Configuring the IPmedia Parameters'' on page 242).

  • Page 496: Figure 10-9: Using An Application Server

    Mediant 1000 & Mediant 600 The figure below illustrates an example of implementing an Application server: Figure 10-9: Using an Application Server SIP User's Manual Document #: LTRT-83303...

  • Page 497: Tunneling Applications

    SIP User's Manual 11. Tunneling Applications Tunneling Applications This section discusses TDM and QISG tunneling, supported by the device. 11.1 TDM Tunneling The device's TDM Tunneling feature allows you to tunnel groups of digital trunk spans or timeslots (B-channels) over the IP network. TDM Tunneling utilizes the device's internal routing (without Proxy control) capabilities to receive voice and data streams from TDM (E1/T1/J1/) spans or individual timeslots, convert them into packets, and then transmit them over the IP network (using point-to-point or point-to-multipoint device distributions).
  • Page 498 Mediant 1000 & Mediant 600 For tunneling of E1/T1 CAS trunks, set the protocol type to 'Raw CAS' (ProtocolType = 3 / 9) and enable RFC 2833 CAS relay mode ('CAS Transport Type' parameter is set to 'CAS RFC2833 Relay' -- refer to ''Configuring the Voice Settings'' on page 81).
  • Page 499 SIP User's Manual 11. Tunneling Applications TelProfile_EnableCurrentDisconnect, TelProfile_EnableDigitDelivery, TelProfile_EnableEC, TelProfile_MWIAnalog, TelProfile_MWIDisplay, TelProfile_FlashHookPeriod, TelProfile_EnableEarlyMedia, TelProfile_ProgressIndicator2IP; TelProfile 1 = voice,$$,1,$$,$$,$$,$$,$$,$$,$$; TelProfile 2 = data,$$,2,$$,$$,$$,$$,$$,$$,$$; [\TelProfile] Originating Side: ;E1_TRANSPARENT_31 ProtocolType_0 = 5 ProtocolType_1 = 5 ProtocolType_2 = 5 ProtocolType_3 = 5 ;Channel selection by Phone number. ChannelSelectMode = 0 [TrunkGroup] FORMAT TrunkGroup_Index = TrunkGroup_TrunkGroupNum,...

  • Page 500: Qsig Tunneling

    Mediant 1000 & Mediant 600 11.2 QSIG Tunneling The device supports QSIG tunneling over SIP according to IETF draft 'Tunnelling of QSIG over SIP' (draft-elwell-sipping-qsig-tunnel-03) and the ECMA-355/ISO/IEC 22535 standard. This method enables all QSIG messages to be sent as raw data in corresponding SIP messages using a dedicated message body.

  • Page 501: Osn Server Hardware Installation

    This section is applicable only to Mediant 1000. 12.1 OSN Server Modules The Mediant 1000 OSN Server package is composed of three modules, which need to be installed in the Mediant 1000 chassis: Connection module (CM) Figure 12-1: Connection Module (CM)

  • Page 502: Required Working Tools

    The following tools are required for installing the OSN Server module: Phillips screwdriver Flathead screwdriver Wire cutter 12.3 Installing the CM Module The Connection Module (CM) is installed on the front panel of the Mediant 1000, as described in the following procedure: SIP User's Manual Document #: LTRT-83303...

  • Page 503: Figure 12-4: Mediant 1000 Front Panel

    12. OSN Server Hardware Installation To install the CM module, take these 4 steps: On the Mediant 1000 front panel, use a Phillips screwdriver to remove the black metal cover plate from the slot located below the module labeled CPU, as shown in the...

  • Page 504: Installing The Ipmx Module

    Mediant 1000 & Mediant 600 12.4 Installing the iPMX Module The iPMX module is installed on the rear panel of the Mediant 1000, as described in the following procedure: To install the iPMX module, take these 7 steps: Place the Mediant 1000 so that the rear panel is facing you, as shown in the figure below.

  • Page 505: Figure 12-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 the figure below. Figure 12-8: Mediant 1000 with Cutter Tool Insert the iPMX module into the first slot, closest to the power connection, as shown in the figure below.

  • Page 506: Installing The Hdmx Module

    Mediant 1000 & Mediant 600 12.5 Installing the HDMX Module The Hard Drive module (HDMX) is installed on the rear panel of the Mediant 1000, as described in the following procedure: To install the HDMX module, take these 6 steps: Place the Mediant 1000 so that the rear panel is facing you.

  • Page 507: Replacing The Ipmx Module's Lithium Battery

    The following procedure describes how to replace the Lithium battery in the iPMX module. To replace the Lithium battery in the iPMX, take these 6 steps: Remove the iPMX module from the slot in which it's housed in the Mediant 1000 rear panel, by performing the following: Using a flathead screwdriver, loosen the module's two lower mounting captive screws.

  • Page 508: Figure 12-11: Removing Lithium Battery From Ipmx Module

    Ensure that you install the battery in the correct orientation such that the positive side is facing up (i.e., the side containing the battery description is visible). Re-insert the iPMX module into the slot of the Mediant 1000 chassis as described in the previous section.

  • Page 509: Installing Windows Xp On The Osn Server

    13. Installing Windows XP on the OSN Server Installing Windows XP on the OSN Server The embedded PC on Mediant 1000 (OSN module) can be ordered with Windows XP pre- installed. However, if requested, the OSN server can be supplied without an installed Windows operating system.

  • Page 510: Stage 2: Creating The Iso Image

    Mediant 1000 & Mediant 600 These modifications can be performed by a commandfile run at the end of the installation. Use Notepad or a similar text editor to create the following two files and save them in a separate folder named "M1K" on your PC (for later use by the Windows Unattended CD Creator): File name: do.cmd...

  • Page 511: Figure 13-2: Selecting Target Directory For Windows Xp

    SIP User's Manual 13. Installing Windows XP on the OSN Server Define the target directory for the new Windows CD. Figure 13-2: Selecting Target Directory for Windows XP Wait for the copy process to complete. Use Windows Explorer to copy the "M1K" folder to the target directory. This is required to allow the .cmd scripts to operate correctly.

  • Page 512: Figure 13-4: Creating A User

    Mediant 1000 & Mediant 600 Create a default user with a password, and assign it to the Administrators group. Figure 13-4: Creating a User Add the drivers for LAN and AUDIO. Figure 13-5: Adding LAN and Audio Drivers SIP User's Manual...

  • Page 513: Figure 13-6: Adding Cmd Files Directory To Cd

    SIP User's Manual 13. Installing Windows XP on the OSN Server Add the directory with the cmd files to the CD. Ensure to select the 'Directories' check box (the description is arbitrary). Figure 13-6: Adding cmd Files Directory to CD Click the newly created name, and then click Select to browse to the do.cmd file.

  • Page 514: Stage 3: Burning The Cd

    Mediant 1000 & Mediant 600 Click Add to include this command file to the installation script. The result appears as follows: Figure 13-8: Adding cmd File to Installation Script Select the Done tab, and then click Save. Click create ISO-image.

  • Page 515: Stage 4: Cabling The Mediant 1000 Osn Server

    The procedure below describes the cabling for installing Windows. To cable the OSN server, take these 3 steps: Connect the CM module's (located on the Mediant 1000 front panel) RS-232 port to a PC (DB-9 connector), using the RS-232 serial cable.
  • Page 516 Press the <Enter> key; CD activity restarts, with several pauses. The installation runs for at least 60 minutes after which all CD activity and Mediant 1000 hard disk activity ends. Using Wireshark, check for BootP broadcasts to find the OSN module's IP address.

  • Page 517: Stage 6: Enabling The Firewall With Remote Desktop Access

    SIP User's Manual 13. Installing Windows XP on the OSN Server 13.2.6 Stage 6: Enabling the Firewall with Remote Desktop Access The OSN server's firewall was initially disabled to allow Windows XP installation and Remote Desktop access (in Stage 1: Creating the Helper Script). However, once you access the OSN Server after Windows installation has complete, you need to enable the Windows XP firewall and allow future Remote Desktop access.

  • Page 518: Figure 13-12: Remote Desktop Firewall

    Mediant 1000 & Mediant 600 Click Windows Firewall, and then add 'Remote Desktop' to the selected firewall exceptions. Figure 13-12: Remote Desktop Firewall Select the Advanced tab, click Settings for the 'Local Area Connection', and then also allow Internet access to Remote Desktop.

  • Page 519: Connecting Remotely To Osn Server Using Windows Xp

    Typically, for customers requiring Microsoft Windows® XP operating system (OS), the OSN Server is provided with Windows XP already pre-installed. Once the OSN Server modules have been installed in the Mediant 1000 chassis, you can connect to the OSN Server using Microsoft's Remote Desktop Connection program.

  • Page 520: Connecting Using Remote Desktop Connection

    Mediant 1000 & Mediant 600 13.3.2 Connecting Using Remote Desktop Connection Once you have cabled the PC to the OSN Server's iPMX module, perform the procedure below for connecting the PC remotely to the OSN Server (running Windows XP) using the Remote Desktop Connection program.

  • Page 521: Figure 13-16: Entering Ip Address In Remote Desktop Connection

    SIP User's Manual 13. Installing Windows XP on the OSN Server Start Microsoft's Remote Desktop Connection program - from the Start menu, point to Programs, to Accessories, to Communications, and then click Remote Desktop Connection. Figure 13-16: Entering IP Address in Remote Desktop Connection In the 'Computer' field, enter the OSN Server's default IP address (i.e., 10.1.10.12).
  • Page 522 Mediant 1000 & Mediant 600 Reader's Notes SIP User's Manual Document #: LTRT-83303...

  • Page 523: Installing Linux™ Operating System On The Osn Server

    Installing Linux™ Operating System on the OSN Server Once the OSN Server modules have been installed in the Mediant 1000 Media Gateway, you need to install an operating system (OS) on the OSN server on which the partner application (e.g. IP-PBX) is to run. If you require the Linux™ OS, follow the procedures...

  • Page 524: Software

    Mediant 1000 & Mediant 600 USB cable (not supplied) to connect the external USB CD ROM to the Mediant 1000 RS-232 cable (supplied) Linux Distributions Installation CDs Blank CD or DVD media Windows PC with CD RW or external CD ROM/RW 14.1.2 Software...

  • Page 525: Installing Linux™ Redhat (And Fedora)

    14.3.1 Stage 1: Obtaining the Linux Redhat ISO Image To obtain an updated ISO image, perform one of the following: Download it from the AudioCodes Web site, as described in ''Downloading an updated LinuxTM Redhat ISO Image'' on page 525, Create it using the steps detailed in ''Creating an updated Linux Redhat ISO Image'' on page 526.

  • Page 526: Creating An Updated Iso Image

    Mediant 1000 & Mediant 600 14.3.1.2 Creating an Updated ISO Image To create an updated Linux Redhat ISO Image take these 6 steps On the local hard disk of the Window’s™ PC, create a new folder called 'Partner Install'. If you have not already done so, download a utility that allows editing of an ISO image (e.g., WinISO™...

  • Page 527: Figure 14-3: Images Folder

    SIP User's Manual 14. Installing Linux™ Operating System on the OSN Server Locate the boot.iso file in the images folder on the CD (refer to the note below). Figure 14-3: Images Folder Copy the boot.iso file to the 'Partner Install' folder created in Step 1, and then open it with an ISO image editor.

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

    Mediant 1000 & Mediant 600 14.3.2 Stage 2: Editing the isolinux.cfg File To edit the isolinux.cfg file, take these 14 steps: Extract the isolinux.cfg file by performing the following: Right-click the isolinux.cfg file, and then from the shortcut menu, choose Extract.

  • Page 529: Figure 14-7: Iso-Extract Screen

    SIP User's Manual 14. Installing Linux™ Operating System on the OSN Server Click Extract; the files is extracted and a screen opens containing the extracted isolinux file. Figure 14-7: ISO-Extract Screen Open the isolinux.cfg file with a text editor that supports UNIX file format (e.g., PSPad or UltraEdit);...
  • Page 530 Mediant 1000 & Mediant 600 Locate the line 'default <my_label>' (usually 'default linux' appears), and then locate the line 'label <my_label>' (usually 'label linux' appears). Under this line, the following appears: kernel ... append ... Add the following parameters to the 'append' line of <my_label>:...

  • Page 531: Figure 14-9: Deleting Cfg

    SIP User's Manual 14. Installing Linux™ Operating System on the OSN Server Right-click the isolinux.cfg file, and then from the shortcut menu, choose Delete to delete this file. Figure 14-9: Deleting CFG From the ISO edit utility menu, select the Actions option, followed by Add Files. Figure 14-10: File Add Version 5.4 May 2008...

  • Page 532: Stage 3: Burning Iso Image File To Cd-Rom

    Ensure that the boot.iso file is burned to the CD as an image and not as a data file. 14.3.4 Stage 4: Installing the Boot Media Now you have the boot media which enables the installation of the Mediant 1000 using the serial connection (terminal) with RS-232 cable. Note: Some third-party applications require specific Linux OS installation steps.

  • Page 533: Figure 14-12: Choose A Language

    Flow Control: None Insert the “Boot CD” (created in Stage 3) into the USB CD-ROM drive. Power up the Mediant 1000. On the Terminal application, the BIOS phase starts and the Linux installation begins. The installation uncompresses the kernel, loads it and its drivers, and then starts the interactive installation.

  • Page 534: Additional Redhat™ And Fedora™ Installation Notes

    /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 535: Installing Linux™ Debian

    SIP User's Manual 14. Installing Linux™ Operating System on the OSN Server 14.4 Installing Linux™ Debian Perform the following five stages for installing Linux™ Debian. Note: Some distributions of Linux may vary slightly. 14.4.1 Stage 1: Obtaining the ISO Image To obtain an updated ISO image, create it using the steps detailed in the section below.

  • Page 536: Stage 2: Preparing The Boot Media

    Mediant 1000 & Mediant 600 Create a 'Partner Install' folder on your hard drive. Select boot.iso as the output filename, and then click Make. Figure 14-14: Create ISO from CD-ROM The .iso file starts being created. Figure 14-15: Creating .iso File 14.4.2 Stage 2: Preparing the Boot Media...

  • Page 537: Figure 14-16: Partner Install Folder

    SIP User's Manual 14. Installing Linux™ Operating System on the OSN Server Locate the boot.iso file in the 'Partner Install' folder on the hard disk of your PC and with the ISO image utility, navigate to the \isolinux\isolinux.cfg file. Figure 14-16: Partner Install Folder Extract the isolinux.cfg file by right-clicking the file name, and then from the shortcut menu, choosing Extract.

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

    14.4.3 Stage 3: Editing the isolinux.cfg File To obtain an updated isolinux.cfg file, perform one of the following: Download it from the AudioCodes Web site as described in ''Downloading an updated Debian isolinux.cfg file'' on page Edit it using the steps detailed in ''Editing the isolinux.cfg File'' on page 14.4.3.1 Downloading an Updated Debian isolinux.cfg File...
  • Page 539 SIP User's Manual 14. Installing Linux™ Operating System on the OSN Server Locate the line 'prompt <flag>' (usually appears as 'prompt 1') and change it to 'prompt Locate the line 'timeout <tenth_of_secs>' (usually appears as 'timeout 600') and change it to 'timeout 0'. Note: If the timeout line does not exist, do not add it.

  • Page 540: Figure 14-19: Deleting Cfg

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

  • Page 541: Stage 4: Burning Iso Image To Cd

    Ensure that the boot.iso file is burned as an image and not as a data file. 14.4.5 Stage 5: Installing the Boot Media Now you have the boot media which enables the installation of the Mediant 1000 using the serial connection (terminal) with RS-232 cable.

  • Page 542: Additional Linux™ Debian Installation Notes

    Mediant 1000 & Mediant 600 • Stop Bits: 1 • Flow Control: None Insert the “Boot CD” (created in Stage 3) into the USB CD-ROM drive. Power up the Mediant 1000. On the Terminal application, the BIOS phase starts and the Linux installation begins.
  • Page 543 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 544: Installing Linux™ Suse

    Mediant 1000 & Mediant 600 14.5 Installing Linux™ SUSE Perform the following five stages for the Linux SUSE Installation. Note: Some distributions of Linux may vary slightly. 14.5.1 Additional Requirement for Linux™ SUSE Installation To install Linux™ SUSE, a terminal emulation program is required that supports the following: ANSI colors (or Linux™...

  • Page 545: Figure 14-23: Create Iso From Cd-Rom

    SIP User's Manual 14. Installing Linux™ Operating System on the OSN Server Create a 'Partner Install' folder on your hard drive. Select boot.iso as the output filename, and then click Make. Figure 14-23: Create ISO from CD-ROM The utility begins creating the boot.iso file. Figure 14-24: Creating .iso File 14.5.3 Stage 2: Preparing the Boot Media To prepare the Boot Media, take these 5 steps:...

  • Page 546: Figure 14-25: Partner Install Folder

    Mediant 1000 & Mediant 600 Locate the boot.iso file in the 'Partner Install' folder on the hard disk of your PC and navigate to the isolinux.cfg file. Figure 14-25: Partner Install Folder Extract the isolinux.cfg file by right-clicking the filename, and then from the shortcut menu, choosing Extract.

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

    14.5.4 Stage 3: Editing the isolinux.cfg File To obtain an updated isolinux.cfg file, perform on of the following: Download it from the AudioCodes Web site as described in ''Downloading an updated SUSE isolinux.cfg file'' on page Edit it using the steps detailed in ''Editing the isolinux.cfg File'' on page 14.5.4.1 Downloading an Updated SUSE isolinux.cfg File...

  • Page 548: Editing The Isolinux.cfg File

    Mediant 1000 & Mediant 600 14.5.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 or UltraEdit).
  • Page 549 SIP User's Manual 14. Installing Linux™ Operating System on the OSN Server 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' and 'append' sublines may appear after you change them: label linux kernel linux...

  • Page 550: Figure 14-29: Deleting Cfg File

    Mediant 1000 & Mediant 600 implicit gfxboot bootlogo display message prompt timeout readinfo framebuffer 1 notice Save the changes to the isolinux.cfg file, and then close the text editor. Open the 'Partner Install' folder and with the ISO edit utility, open the boot.iso file.

  • Page 551: Stage 4: Burning The Cd

    SIP User's Manual 14. Installing Linux™ Operating System on the OSN Server Navigate to the 'Partner Install' folder, select the isolinux.cfg file, and then click Open. Figure 14-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 552: Stage 5: Installing The Boot Media

    Mediant 1000 & Mediant 600 14.5.6 Stage 5: Installing the Boot Media 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 553 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 554 Mediant 1000 & Mediant 600 Reader's Notes SIP User's Manual Document #: LTRT-83303...

  • Page 555: Supplied Sip Software Package

    Table 15-1: Supplied Software Package File Name Description Ram.cmp file M1000_Digital_SIP_xxx.cmp Image file containing the software for the Mediant 1000 device. M1000_SIP_xxx.cmp Image file containing the software for both FXS and FXO modules. M600_Digital_SIP_xxx.cmp Image file containing the software for the Mediant 600 device.
  • Page 556 Mediant 1000 & Mediant 600 Reader's Notes SIP User's Manual Document #: LTRT-83303...

  • Page 557: Selected Technical Specifications

    SIP User's Manual 16. Selected Technical Specifications Selected Technical Specifications 16.1 Mediant 1000 The table below lists the main technical specifications of the Mediant 1000. Table 16-1: Mediant 1000 Functional Specifications Function Specification Modularity and Capacity Six module slots supporting a mixed configuration of the following...
  • Page 558 Tx & Rx frequency response, Tx & Rx Gains, ring detection FXO Capabilities threshold, DC characteristics Note: For a specific coefficient file, please contact AudioCodes. Caller ID Detection: Bellcore GR-30-CORE Type 1 using Bell 202 FSK modulation, ETSI Type 1, NTT, Denmark, India, Brazil, and DTMF...
  • Page 559 SIP User's Manual 16. Selected Technical Specifications Function Specification Full-Duplex Parties per Conference Bridge (Max.) Fax/Modem Relay Group 3 fax relay up to 14.4 kbps with auto fallback T.30 (PSTN) and T.38 (IP) compliant, real time fax relay Fax Relay Tolerant network delay (up to 9 seconds round trip) CNG tone detection &...
  • Page 560 Mediant 1000 & Mediant 600 Function Specification Physical Dimensions (W x H x 482.6 mm (19”) x 1U x 350.5 mm (13.8”) Weight Approx. 5 kg (depending on number of installed modules) Supply Voltage and Universal 100 - 240 VAC; 50 - 60 Hz; 1 A max.

  • Page 561: Mediant 600

    SIP User's Manual 16. Selected Technical Specifications 16.2 Mediant 600 The table below lists the main technical specifications of the Mediant 600. Table 16-2: Mediant 600 Functional Specifications Function Specification Interfaces and Capacity 1 or 2 E1/T1/J1 spans using RJ-48c ports E1/T1/J1 Digital Modules 1 Fractional E1/T1/J1 (15 DS0) span using RJ-48c port (Balanced...
  • Page 562 Mediant 1000 & Mediant 600 Function Specification Automatic switching to PCM or ADPCM on V.34 or V.90 modem detection Modem Transparency Automatic switching (pass-through) to PCM, ADPCM or NSE bypass mode for modem signals (V.34 or V.90 modem detection) Protocols...
  • Page 563 SIP User's Manual 16. Selected Technical Specifications Function Specification Diagnostics Front Panel Status E1/T1, BRI, and LAN status LEDs Supported by Syslog Server (RFC 3164 IETF standard) Syslog Events SNMP MIBs and Traps SNMP v2c, SNMP v3 Management Configuration Embedded HTTP Web Server (Web browser), CLI or ini file SNMP v2c, SNMP v3 Syslog (according to RFC 3164) Management and...
  • Page 564 Mediant 1000 & Mediant 600 Reader's Notes SIP User's Manual Document #: LTRT-83303...

  • Page 565: Glossary

    Address of Record American Wire Gauge Bits per second BootP AudioCodes Proprietary Bootstrap Loader Utility Basic Rate Interface (ISDN) Channel Associated Signaling Class of Service Compressed File (device Firmware)

  • Page 566: Mediant 1000 & Mediant

    Mediant 1000 & Mediant 600 Term Meaning IPSec IP Security ISDN Integrated Services Digital Network International Standards Organization International Telecommunications Union ITU-T Telecommunications section of the ITU Interactive Voice Response Jitter Variation of interpacket timing interval kbps Kilobit per second. 1,000 bits per second...
  • Page 567 SIP User's Manual 17. Glossary Term Meaning PVID Port VLAN ID (VLAN ID assignment to Ethernet packet by switch) Quality of Service Request for Comment issued by IETF RTCP Real-Time Transport (RTP) Control Protocol Real-Time Transport Protocol Security Associations (contains encryption keys and profile used by IPSec to encrypt the IP stream) Stand Alone Survivability Feature Session Description Protocol...
  • Page 568 User's Manual Version 5.4 www.audiocodes.com...

This manual is also suitable for:

Mediant 600

Table of Contents