AudioCodes Mediant 500 E-SBC User Manual
  1. Manuals
  2. Brands
  3. AudioCodes Manuals
  4. Gateway
  5. Mediant 500 E-SBC
  6. User manual

AudioCodes Mediant 500 E-SBC User Manual

Enterprise session border controller digital voip media gateway
Hide thumbs Also See for Mediant 500 E-SBC:
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
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
Table of Contents

Advertisement

Quick Links

User's Manual
Enterprise Session Border Controller
Digital VoIP Media Gateway
Mediant 500 E-SBC
Version 6.8

Advertisement

Table of Contents
loading

Related Manuals for AudioCodes Mediant 500 E-SBC

Summary of Contents for AudioCodes Mediant 500 E-SBC

  • Page 1 User's Manual Enterprise Session Border Controller Digital VoIP Media Gateway Mediant 500 E-SBC Version 6.8...

  • Page 3: Table Of Contents

    CLI-Based Management ..................65 Getting Familiar with CLI ..................65 7.1.1 Understanding Configuration Modes ...............65 7.1.2 Using CLI Shortcuts ....................66 7.1.3 Common CLI Commands ..................67 7.1.4 Configuring Tables in CLI ..................68 7.1.5 Understanding CLI Error Messages ................69 Version 6.8 Mediant 500 E-SBC...
  • Page 4 Mediant 500 E-SBC Enabling CLI ......................69 7.2.1 Enabling Telnet for CLI ....................69 7.2.2 Enabling SSH with RSA Public Key for CLI.............70 Establishing a CLI Session ................... 72 Configuring Maximum Telnet/SSH Sessions ............73 Viewing and Terminating Current CLI Sessions ............ 73 Configuring Displayed Output Lines in CLI Terminal Window .......
  • Page 5 14.2.2.7 Fax / Modem Transparent Mode ............165 14.2.2.8 RFC 2833 ANS Report upon Fax/Modem Detection ......166 14.2.3 V.34 Fax Support ....................166 14.2.3.1 Bypass Mechanism for V.34 Fax Transmission ........167 14.2.3.2 Relay Mode for T.30 and V.34 Faxes ............167 Version 6.8 Mediant 500 E-SBC...
  • Page 6 Mediant 500 E-SBC 14.2.3.3 V.34 Fax Relay for SG3 Fax Machines ..........168 14.2.4 V.150.1 Modem Relay ...................169 14.2.5 Simultaneous Negotiation of Fax (T.38) and Modem (V.150.1) Relay ....170 14.2.6 V.152 Support ......................171 14.2.7 Fax Transmission behind NAT ................172 14.3 Configuring RTP/RTCP Settings ................. 172 14.3.1 Configuring the Dynamic Jitter Buffer ..............172...
  • Page 7 21.2 TDM and Timing ....................335 21.2.1 Configuring TDM Bus Settings ................335 21.2.2 Clock Settings ......................336 21.2.2.1 Recovering Clock from PSTN Line Interface .........336 21.2.2.2 Configuring Internal Clock as Clock Source...........337 21.3 Configuring CAS State Machines ............... 337 Version 6.8 Mediant 500 E-SBC...
  • Page 8 Mediant 500 E-SBC 21.4 Configuring Digital Gateway Parameters ............340 21.5 Tunneling Applications ..................341 21.5.1 TDM Tunneling ......................341 21.5.1.1 DSP Pattern Detector ................344 21.5.2 QSIG Tunneling .....................344 21.6 ISDN Non-Facility Associated Signaling (NFAS) ..........345 21.6.1 NFAS Interface ID ....................346 21.6.2 Working with DMS-100 Switches ................346...
  • Page 9 26.5.2 Enhanced 9-1-1 Support for Lync Server 2010 .............419 26.5.2.1 About E9-1-1 Services ................419 26.5.2.2 Microsoft Lync Server 2010 and E9-1-1 ..........420 26.5.2.3 AudioCodes ELIN Gateway for Lync Server 2010 E9-1-1 Calls to PSTN 26.5.2.4 Configuring AudioCodes ELIN Gateway ..........429 26.6 Multilevel Precedence and Preemption ............... 432 26.6.1 MLPP Preemption Events in SIP Reason Header ..........434...
  • Page 10 Mediant 500 E-SBC 27.7.2 Interworking SIP Diversion and History-Info Headers ...........459 27.7.3 Interworking SIP REFER Messages ..............459 27.7.4 Interworking SIP PRACK Messages ..............460 27.7.5 Interworking SIP Session Timer ................460 27.7.6 Interworking SIP Early Media ................461 27.7.7 Interworking SIP re-INVITE Messages ..............463 27.7.8 Interworking SIP UPDATE Messages ..............463...
  • Page 11 39.1.4.1 Creating a Dial Plan File.................556 39.1.4.2 Dialing Plans for Digit Collection ............557 39.1.4.3 Dial Plan Prefix Tags for Routing ............559 39.1.4.4 Obtaining IP Destination from Dial Plan File ..........562 39.1.4.5 Modifying ISDN-to-IP Calling Party Number ..........563 Version 6.8 Mediant 500 E-SBC...
  • Page 12 40.1.3 Provisioning from TFTP Server using DHCP Option 66 ........585 40.1.4 HTTP-based Provisioning ..................585 40.1.5 FTP- based Provisioning ..................586 40.1.6 Provisioning using AudioCodes EMS ..............586 40.2 HTTP/S-Based Provisioning using the Automatic Update Feature ...... 587 40.2.1 Files Provisioned by Automatic Update ..............587 40.2.2 File Location for Automatic Update ...............587...
  • Page 13 49 Syslog and Debug Recordings ..............657 49.1 Syslog Message Format ..................657 49.1.1 Event Representation in Syslog Messages ............658 49.1.2 Identifying AudioCodes Syslog Messages using Facility Levels ......660 49.1.3 SNMP Alarms in Syslog Messages ...............661 49.2 Enabling Syslog ....................662 49.3 Configuring Web Operations to Report to Syslog ..........
  • Page 14 Mediant 500 E-SBC 50 Self-Testing ...................... 671 51 Creating Core Dump and Debug Files upon Device Crash ......673 52 Testing SIP Signaling Calls ................675 52.1 Configuring Test Call Endpoints ................. 675 52.2 Starting and Stopping Test Calls ................ 679 52.3 Viewing Test Call Statistics .................
  • Page 15 54.14.3 Least Cost Routing Parameters ................912 54.14.4 Call Setup Rules Parameters ................913 55 SBC and DSP Channel Capacity ..............915 55.1 Signaling-Media Sessions & User Registrations ..........915 55.2 Channel Capacity and Capabilities ..............916 56 Technical Specifications ................917 Version 6.8 Mediant 500 E-SBC...
  • Page 16 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10437...

  • Page 17: Weee Eu Directive

    This document is subject to change without notice. Date Published: June-21-2016 Trademarks AudioCodes, AC, HD VoIP, HD VoIP Sounds Better, IPmedia, Mediant, MediaPack, What’s Inside Matters, OSN, SmartTAP, VMAS, VoIPerfect, VoIPerfectHD, Your Gateway To VoIP, 3GX, VocaNOM and CloudBond 365 are trademarks or registered trademarks of AudioCodes Limited All other products or trademarks are property of their respective owners.

  • Page 18: Related Documentation

    Mediant 500 E-SBC Related Documentation Manual Name SIP CPE Release Notes Mediant 500 E-SBC Hardware Installation Manual Complementary Guides CLI Reference Guide CPE Configuration Guide for IP Voice Mail SNMP Reference Guide SBC Design Guide Recommended Security Guidelines Configuration Note...
  • Page 19 Some of the features listed in this document are available only if the relevant Software License Key has been purchased from AudioCodes and installed on the device. For a list of Software License Keys that can be purchased, please consult your AudioCodes sales representative.
  • Page 20 Server; Disconnect on Broken Connection; Forward Destination; Call Trigger; Configuring RTCP XR. Documentation Feedback AudioCodes continually strives to produce high quality documentation. If you have any comments (suggestions or errors) regarding this document, please fill out the Documentation Feedback form on our Web site at http://www.audiocodes.com/downloads.

  • Page 21: Overview

    Overview The Mediant 500 Enterprise Session Border Controller (E-SBC), hereafter referred to as the device, is a member of AudioCodes family of E-SBCs, enabling connectivity and security between small medium businesses (SMB) and service providers' VoIP networks. The device provides SBC functionality as well as voice-over-IP (VoIP) media gateway functionality.
  • Page 22 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10437...

  • Page 23: Getting Started With Initial Connectivity

    Part I Getting Started with Initial Connectivity...

  • Page 25: Introduction

    User's Manual 2. Introduction Introduction This part describes how to initially access the device's management interface and change its default IP address to correspond with your networking scheme. Version 6.8 Mediant 500 E-SBC...
  • Page 26 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10437...

  • Page 27: Default Oamp Ip Address

    The table below lists the device's default IP address. Table 3-1: Default VoIP LAN IP Address for OAMP IP Address Value Application Type OAMP + Media + Control IP Address 192.168.0.2 Prefix Length 255.255.255.0 (24) Default Gateway 192.168.0.1 Underlying Device Interface Name "O+M+C" Version 6.8 Mediant 500 E-SBC...
  • Page 28 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10437...

  • Page 29: Configuring Voip Lan Interface For Oamp

    IP address of the device; the Web interface's Web Login screen appears: Figure 4-1: Web Login Screen In the 'Username' and 'Password' fields, enter the case-sensitive, default login username ("Admin") and password ("Admin"). Click Login. Version 6.8 Mediant 500 E-SBC...
  • Page 30 Mediant 500 E-SBC Open the Physical Ports Settings page (Configuration tab > VoIP menu > Network > Physical Ports Table) and then configure the device's physical Ethernet port-pair (group) that you want to later assign to the OAMP interface. For more information, see Configuring Physical Ethernet Ports on page 109.

  • Page 31: Cli

    At the prompt, type the password (default is "Admin" - case sensitive): Password: Admin At the prompt, type the following: enable At the prompt, type the password again: Password: Admin Access the VoIP configuration mode: # configure voip Access the Interface table: (config-voip)# interface network-if 0 Version 6.8 Mediant 500 E-SBC...
  • Page 32 Mediant 500 E-SBC Configure the IP address: (network-if-0)# ip-address <IP address> Configure the prefix length: (network-if-0)# prefix-length <prefix length / subnet mask, e.g., 16> Configure the Default Gateway address: (network-if-0)# gateway <IP address> Exit the Interface table: (network-if-0)# exit Exit the VoIP configuration mode:...

  • Page 33: Management Tools

    Part II Management Tools...

  • Page 35: Introduction

    Web, CLI, and ini file parameter is mentioned. The ini file parameters are enclosed in square brackets [...]. • For a list and description of all the configuration parameters, see ''Configuration Parameters Reference'' on page 691. Version 6.8 Mediant 500 E-SBC...
  • Page 36 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10437...

  • Page 37: Web-Based Management

    Microsoft™ Internet Explorer™ (Version 6.0 and later) • ® Mozilla Firefox (Versions 5 through 9.0)  Recommended screen resolutions: 1024 x 768 pixels, or 1280 x 1024 pixels Note: Your Web browser must be JavaScript-enabled to access the Web interface. Version 6.8 Mediant 500 E-SBC...

  • Page 38: Accessing The Web Interface

    Mediant 500 E-SBC 6.1.2 Accessing the Web Interface The following procedure describes how to access the Web interface.  To access the Web interface: Open a standard Web browser (see ''Computer Requirements'' on page 37). In the Web browser, specify the OAMP IP address of the device (e.g., http://10.1.10.10);...

  • Page 39: Areas Of The Gui

    ''Navigation Tree'' on page 41. Work pane, displaying the configuration page of the selected menu in the Navigation tree. This is where configuration is done. For more information, see ''Working with Configuration Pages'' on page 43. Version 6.8 Mediant 500 E-SBC...

  • Page 40: Toolbar Description

    Mediant 500 E-SBC 6.1.4 Toolbar Description The toolbar provides frequently required command buttons, described in the table below: Table 6-2: Description of Toolbar Buttons Icon Button Description Name Submit Applies parameter settings to the device (see ''Saving Configuration'' on page 542).

  • Page 41: Navigation Tree

    The expanded view displays all the menus pertaining to the selected configuration tab; the reduced view displays only commonly used menus.  To display a reduced menu tree, select the Basic option (default). Version 6.8 Mediant 500 E-SBC...

  • Page 42: Showing / Hiding The Navigation Pane

    Mediant 500 E-SBC  To display all menus and submenus, select the Advanced option. Figure 6-4: Basic and Full View Options Note: After you reset the device, the Web GUI is displayed in Basic view. 6.1.5.2 Showing / Hiding the Navigation Pane You can hide the Navigation pane to provide more space for elements displayed in the Work pane.

  • Page 43: Working With Configuration

     Advanced Parameter List button with down-pointing arrow: click this button to display all parameters.  Basic Parameter List button with up-pointing arrow: click this button to show only common (basic) parameters. Version 6.8 Mediant 500 E-SBC...
  • Page 44 Mediant 500 E-SBC The figure below shows an example of a page displaying basic parameters only. If you click the Advanced Parameter List button (shown below), the page will also display the advanced parameters. Figure 6-6: Toggling between Basic and Advanced View Notes: •...

  • Page 45: Modifying And Saving Parameters

    Submit, a message box appears notifying you of the invalid value. In addition, the parameter value reverts to its previous value and is highlighted in red, as shown in the figure below: Figure 6-9: Value Reverts to Previous Valid Value Version 6.8 Mediant 500 E-SBC...

  • Page 46: Working With Tables

    Mediant 500 E-SBC 6.1.6.4 Working with Tables Many of the Web configuration pages provide tables for configuring various functionalities of the device. The figure below and subsequent table describe the areas of a typical configuration table: Figure 6-10: Displayed Details Pane...

  • Page 47: Searching For Configuration Parameters

    Link (in green) to the Web page on which the parameter appears • Brief description of the parameter • Menu navigation path to the Web page on which the parameter appears In the searched list, click the required parameter (green link) to open the page on Version 6.8 Mediant 500 E-SBC...

  • Page 48: Creating A Login Welcome Message

    Mediant 500 E-SBC which the parameter appears; the relevant page opens in the Work pane and the searched parameter is highlighted in the page for easy identification, as shown in the figure below: Figure 6-12: Searched Result Screen Table 6-5: Search Description...
  • Page 49 WelcomeMessage 2 = "********* This is a Welcome message **"; WelcomeMessage 3 = "*********************************"; [\WelcomeMessage] Each index row represents a line of text in the Welcome message box. Up to 20 lines (or rows) of text can be defined. Version 6.8 Mediant 500 E-SBC...

  • Page 50: Getting Help

    Mediant 500 E-SBC 6.1.9 Getting Help The Web interface provides you with context-sensitive Online Help. The Online Help provides brief descriptions of parameters pertaining to the currently opened page.  To view the Help topic of a currently opened page: On the toolbar, click the Help button;...

  • Page 51: Logging Off The Web Interface

     To access the Home page:  On the toolbar, click the Home icon. Figure 6-16: Home Page Note: The displayed number and type of telephony interfaces depends on the ordered hardware configuration. Version 6.8 Mediant 500 E-SBC...
  • Page 52 Mediant 500 E-SBC In addition to the color-coded status information depicted on the graphical display of the device, the Home page displays various read-only information in the General Information pane:  IP Address: IP address of the device  Subnet Mask: Subnet mask address of the device ...

  • Page 53: Assigning A Port Name

    Open the Home page. Click the required port icon; a shortcut menu appears: From the shortcut menu, choose Update Port Info; a text box appears: Type a brief description for the port, and then click Apply Port Info. Version 6.8 Mediant 500 E-SBC...

  • Page 54: Configuring Web User Accounts

    Mediant 500 E-SBC Configuring Web User Accounts Web user accounts define users for the Web interface and CLI. User accounts permit login access to these interfaces as well as different levels of read and write privileges. Thus, user accounts prevent unauthorized access to these interfaces, permitting access only to users with correct credentials (i.e., username and password).

  • Page 55: Basic User Accounts Configuration

    The username and password can be a string of up to 19 characters and are case- sensitive. • When only the basic user accounts are being used, up to two users can be concurrently logged in to the Web interface, and they can be the same user. Version 6.8 Mediant 500 E-SBC...
  • Page 56 Mediant 500 E-SBC  To configure the two pre-configured Web user accounts: Open the Web User Accounts page (Configuration tab > System menu > Web User Accounts). If you are logged in as Security Administrator, both Web user accounts are displayed (as shown below). If you are logged in with the second user account, only the details of this user account are displayed.

  • Page 57: Advanced User Accounts Configuration

    Subsequent access: Configuration tab > System menu > Web User Accounts. The Web Users table appears, listing the two default, pre-configured Web use accounts - Security Administrator ("Admin") and Monitor ("User"): Figure 6-18: Web Users Table Page Version 6.8 Mediant 500 E-SBC...
  • Page 58 Mediant 500 E-SBC Click Add; the following dialog box is displayed: Figure 6-19: Web Users Table - Add Record Dialog Box Configure a Web user according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory.
  • Page 59 The default is according to the settings of the 'Deny Authentication Timer' parameter (see ''Configuring Web Security Settings'' on page 61). Note: The 'Deny Authentication Timer' parameter relates to failed Web logins from specific IP addresses. Version 6.8 Mediant 500 E-SBC...

  • Page 60: Displaying Login Information Upon Login

    Mediant 500 E-SBC Parameter Description Web: User Level Defines the user's access level. CLI: privilege  Monitor = (Default) Read-only user. This user can only view Web pages and access to security-related pages is denied.  Administrator = Read/write privileges for all pages, except security- related pages including the Web Users table where this user has only read-only privileges.

  • Page 61: Configuring Web Security Settings

    - what the user has (i.e., the physical card) and what the user knows (i.e., the login password). This feature is enabled using the EnableMgmtTwoFactorAuthentication parameter. Note: For specific integration requirements for implementing a third-party smart card for Web login authentication, contact your AudioCodes representative. Version 6.8 Mediant 500 E-SBC...

  • Page 62: Configuring Web And Telnet Access List

    Mediant 500 E-SBC  To log in to the Web interface using CAC: Insert the Common Access Card into the card reader. Access the device using the following URL: https://<host name or IP address>; the device prompts for a username and password.
  • Page 63 PC is denied. • Delete your PC's IP address last from the 'Web & Telnet Access List page. If it is deleted before the last, subsequent access to the device from your PC is denied. Version 6.8 Mediant 500 E-SBC...
  • Page 64 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10437...

  • Page 65: Cli-Based Management

    This mode allows you to view various information (using the show commands) and activate various debugging capabilities. Welcome to AudioCodes CLI Username: Admin Password: >...

  • Page 66: Using Cli Shortcuts

    Mediant 500 E-SBC The Enable mode groups the configuration commands under the following command sets: • config-system: Provides the general and system related configuration commands, for example, Syslog configuration. This set is accessed by typing the following command: # configure system (config-system)# •...

  • Page 67: Common Cli Commands

    Applied to a command output. The filter should be typed after the command with a pipe mark (|). Supported filters:  include <word> – filter (print) lines which contain <word>  exclude <word> – filter lines which does not contain <word> Version 6.8 Mediant 500 E-SBC...

  • Page 68: Configuring Tables In Cli

    Mediant 500 E-SBC Command Description  grep <options> - filter lines according to grep common Unix utility options  egrep <options> - filter lines according to egrep common Unix utility options  begin <word> – filter (print) lines which begins with <word>...

  • Page 69: Understanding Cli Error Messages

    Configure the other Tenet parameters as required. For a description of these parameters, see ''Telnet Parameters'' on page 695. Click Submit, and then reset the device with a burn-to-flash for your settings to take effect. Version 6.8 Mediant 500 E-SBC...

  • Page 70: Enabling Ssh With Rsa Public Key For Cli

    Mediant 500 E-SBC 7.2.2 Enabling SSH with RSA Public Key for CLI Unless configured for TLS, Telnet is not secure as it requires passwords to be transmitted in clear text. To overcome this, Secure SHell (SSH) is used, which is the de-facto standard for secure CLI.
  • Page 71 'Admin Key' field. Click Submit. Connect to the device with SSH, using the following command: ssh -i admin.key xx.xx.xx.xx where xx.xx.xx.xx is the device's IP address. RSA-key negotiation occurs automatically and no password is required. Version 6.8 Mediant 500 E-SBC...

  • Page 72: Establishing A Cli Session

    Mediant 500 E-SBC Establishing a CLI Session The device's CLI can be accessed using any of the following methods:  RS-232: The device can be accessed through its RS-232 serial port, by connecting a VT100 terminal to it or using a terminal emulation program (e.g., HyperTerminal) with a PC.

  • Page 73: Configuring Maximum Telnet/Ssh Sessions

    # clear user <session ID> When this command is run, it ends the Telnet/SSH session (logs out the RS-232 session) and displays the CLI login prompt. Note: The session from which the command is run cannot be terminated. Version 6.8 Mediant 500 E-SBC...

  • Page 74: Configuring Displayed Output Lines In Cli Terminal Window

    Mediant 500 E-SBC Configuring Displayed Output Lines in CLI Terminal Window You can configure the maximum number of lines (height) displayed in the terminal window for the output of CLI commands (Telnet and SSH). The number of displayed lines can be specified from 0 to 65,535, or determined by re-sizing the terminal window by mouse- dragging the window's border.

  • Page 75: Snmp-Based Management

    SNMP Manager. All supported MIB files are supplied to customers as part of the release. AudioCodes EMS is an advanced solution for standards-based management that covers all areas vital for the efficient operation, administration, management and provisioning (OAM&P) of the device.
  • Page 76 Mediant 500 E-SBC  To configure SNMP community strings: Open the SNMP Community String page (Configuration tab > System menu > Management > SNMP > SNMP Community String). Configure SNMP community strings according to the table below. Click Submit, and then save ("burn") your settings to flash memory.

  • Page 77: Configuring Snmp Trap Destinations

    Management > SNMP > SNMP Trap Destinations). Figure 8-1: SNMP Trap Destinations Page Configure the SNMP trap manager parameters according to the table below. Select the check box corresponding to the SNMP Manager that you wish to enable. Click Submit. Version 6.8 Mediant 500 E-SBC...
  • Page 78 Mediant 500 E-SBC Note: Only row entries whose corresponding check boxes are selected are applied when clicking Submit; otherwise, settings revert to their defaults. Table 8-2: SNMP Trap Destinations Parameters Description Parameter Description Web: SNMP Manager Enables the SNMP Manager to receive traps and checks...

  • Page 79: Configuring 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. Define an IP address in dotted-decimal notation. Click Submit, and then save ("burn") your settings to flash memory. Version 6.8 Mediant 500 E-SBC...

  • Page 80: Configuring Snmp V3 Users

    Mediant 500 E-SBC Configuring SNMP V3 Users The SNMP v3 Users table lets you configure up to 10 SNMP v3 users for authentication and privacy. The following procedure describes how to configure SNMP v3 users in the Web interface. You can also configure this using the table ini file parameter, SNMPUsers or CLI command, configure system >...
  • Page 81 Group The group with which the SNMP v3 user is associated. CLI: group  [0] Read-Only (default) [SNMPUsers_Group]  [1] Read-Write  [2] Trap Note: All groups can be used to send traps. Version 6.8 Mediant 500 E-SBC...
  • Page 82 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10437...

  • Page 83: Ini File-Based Management

    (dynamic tables of other applications are empty, but static tables are not). The table ini file parameter is composed of the following elements:  Title of the table: The name of the table in square brackets, e.g., [MY_TABLE_NAME]. Version 6.8 Mediant 500 E-SBC...
  • Page 84 Mediant 500 E-SBC  Format line: Specifies the columns of the table (by their string names) that are to be configured. • The first word of the Format line must be "FORMAT", followed by the Index field name and then an equal "=" sign. After the equal sign, the names of the columns are listed.

  • Page 85: General Ini File Formatting Rules

    Save the file with the ini file extension name (e.g., myconfiguration.ini). Load the file to the device. For loading the ini file to the device, see ''Loading an ini File to the Device'' on page 86. Version 6.8 Mediant 500 E-SBC...

  • Page 86: Loading An Ini File To The Device

    The file may be loaded to the device using HTTP. These protocols are not secure and are vulnerable to potential hackers. To overcome this security threat, the AudioCodes DConvert utility allows you to binary-encode (encrypt) the ini file before loading it to the device.

  • Page 87: Configuring Password Display In Ini File

    $0$<plain text>: Password can be entered in plain text; useful for configuring a new password. When the ini file is loaded to the device and then later saved from the device to a PC, the password is displayed obscured (i.e., $1$<obscured password>). Version 6.8 Mediant 500 E-SBC...

  • Page 88: Ini Viewer And Editor Utility

    Mediant 500 E-SBC INI Viewer and Editor Utility AudioCodes INI Viewer & Editor utility provides a user-friendly graphical user interface (GUI) that lets you easily view and modify the device's ini file. This utility is available from AudioCodes Web site at www.AudioCodes.com/downloads, and can be installed on any Windows-based PC.

  • Page 89: General System Settings

    Part III General System Settings...

  • Page 91: Configuring Certificates

    Private key - externally created and then uploaded to device  X.509 certificates - self-signed certificates or signed as a result of a certificate signing request (CSR)  Trusted root certificate authority (CA) store (for validating certificates) Version 6.8 Mediant 500 E-SBC...
  • Page 92 Mediant 500 E-SBC When the device establishes a TLS connection (handshake) with a SIP user agent (UA), the TLS Context is determined as follows:  Incoming calls: Proxy Set: If the incoming call is successfully classified to an IP Group based on Proxy Set (i.e., IP address of calling party) and the Proxy Set is configured for...
  • Page 93  [5] 5 = TLS 1.2 and TLS 1.0 only.  [6] 6 = TLS 1.2 and TLS 1.1 only  [7] 7 = TLS 1.2, TLS 1.1 and TLS 1.0 only (excludes SSL 3.0). Version 6.8 Mediant 500 E-SBC...
  • Page 94 Mediant 500 E-SBC Parameter Description Web: Ciphers Server Defines the supported cipher suite for the TLS server (in OpenSSL cipher CLI: ciphers-server list format). [TLSContexts_Serve For valid values, refer to URL rCipherString] http://www.openssl.org/docs/apps/ciphers.html. The default is "AES:RC4". For example, use "ALL" for all ciphers suites (e.g., for ARIA encryption for TLS).

  • Page 95: Assigning Csr-Based Certificates To Tls Contexts

    Figure 10-2: Certificate Signing Request Group Copy the text and send it to your security provider (CA) to sign this request. When the CA sends you a server certificate, save the certificate to a file (e.g., cert.txt). Version 6.8 Mediant 500 E-SBC...

  • Page 96: Assigning Externally Created Private Keys To Tls Contexts

    Mediant 500 E-SBC Ensure that the file is a plain-text file containing the"‘BEGIN CERTIFICATE" header, as shown in the example of a Base64-Encoded X.509 Certificate below: -----BEGIN CERTIFICATE----- MIIDkzCCAnugAwIBAgIEAgAAADANBgkqhkiG9w0BAQQFADA/MQswCQYDVQQGEw JGUjETMBEGA1UEChMKQ2VydGlwb3N0ZTEbMBkGA1UEAxMSQ2VydGlwb3N0ZSBT ZXJ2ZXVyMB4XDTk4MDYyNDA4MDAwMFoXDTE4MDYyNDA4MDAwMFowPzELMAkGA1 UEBhMCRlIxEzARBgNVBAoTCkNlcnRpcG9zdGUxGzAZBgNVBAMTEkNlcnRpcG9z dGUgU2VydmV1cjCCASEwDQYJKoZIhvcNAQEBBQADggEOADCCAQkCggEAPqd4Mz iR4spWldGRx8bQrhZkonWnNm`+Yhb7+4Q67ecf1janH7GcN/SXsfx7jJpreWUL f7v7Cvpr4R7qIJcmdHIntmf7JPM5n6cDBv17uSW63er7NkVnMFHwK1QaGFLMyb FkzaeGrvFm4k3lRefiXDmuOe+FhJgHYezYHf44LvPRPwhSrzi9+Aq3o8pWDguJ uZDIUP1F1jMa+LPwvREXfFcUW+w== -----END CERTIFICATE----- Scroll down to the Upload certificates files from your computer group, click the Browse button corresponding to the 'Send Device Certificate...' field, navigate to the...

  • Page 97: Generating Private Keys For Tls Contexts

    Figure 10-5: Generate new private key and self-signed certificate Group From the 'Private Key Size' drop-down list, select the desired private key size (in bits) for RSA public-key encryption for newly self-signed generated keys: • • 1024 (default) • 2048 Version 6.8 Mediant 500 E-SBC...

  • Page 98: Creating Self-Signed Certificates For Tls Contexts

    Mediant 500 E-SBC Click Generate Private Key; a message appears requesting you to confirm key generation. Click OK to confirm key generation; the device generates a new private key, indicated by a message in the Certificate Signing Request group. Figure 10-6: Indication of Newly Generated Private Key Continue with the certificate configuration, by either creating a CSR or generating a new self-signed certificate.

  • Page 99: Importing Certificates And Certificate Chain Into Trusted Certificate Store

    Open the TLS Contexts page (Configuration tab > System menu > TLS Contexts). In the TLS Contexts table, select the required TLS Context index row, and then click the Context Trusted-Roots button, located at the bottom of the TLS Contexts page; the Trusted Certificates page appears. Version 6.8 Mediant 500 E-SBC...

  • Page 100: Configuring Mutual Tls Authentication

    Mediant 500 E-SBC Click the Import button, and then select the certificate file to load. Figure 10-9: Importing Certificate into Trusted Certificates Store Click OK; the certificate is loaded to the device and listed in the Trusted Certificates store. You can also do the following with certificates that are in the Trusted Certificates store: ...

  • Page 101: Tls For Remote Device Management

    The root certificate can also be loaded via the Automatic Update facility, using the HTTPSRootFileName ini file parameter. • You can enable the device to check whether a peer's certificate has been revoked by an OCSP server, per TLS Context (see 'Configuring TLS Certificate Contexts' on page 91). Version 6.8 Mediant 500 E-SBC...

  • Page 102: Configuring Tls Server Certificate Expiry Check

    Mediant 500 E-SBC 10.1.8 Configuring TLS Server Certificate Expiry Check You can also configure the TLS Server Certificate Expiry Check feature, whereby the device periodically checks the validation date of the installed TLS server certificates. You also configure device send...

  • Page 103: Date And Time

    Saving Time (DST), see 'Configuring Daylight Saving Time' on page 105. You can also configure the device to authenticate and validate the NTP messages received from the NTP server. Authentication is done using an authentication key with the MD5 Version 6.8 Mediant 500 E-SBC...
  • Page 104 Mediant 500 E-SBC cryptographic hash algorithm. When this feature is enabled, the device ignores NTP messages received without authentication. The following procedure describes how to configure SNTP. For detailed descriptions of the configuration parameters, see NTP and Daylight Saving Time Parameters on page 713.

  • Page 105: Configuring Daylight Saving Time

    If the current date falls within the DST period, verify that it has been successful applied to the device's current date and time. You can view the device's date and time in the Regional Settings page (see 'Configuring Date and Time Manually' on page 103). Version 6.8 Mediant 500 E-SBC...
  • Page 106 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10437...

  • Page 107: General Voip Configuration

    Part IV General VoIP Configuration...

  • Page 109: Network

    The linked image cannot be displayed. The file may have been moved, renamed, or deleted. Ve Note: All the LAN ports have the same MAC address. This is the MAC address of the device itself. Version 6.8 Mediant 500 E-SBC...
  • Page 110 Mediant 500 E-SBC  To configure the physical Ethernet ports: Open the Physical Ports Settings page (Configuration tab > VoIP menu > Network > Physical Ports Table). Select a port that you want to configure by clicking its table row, and then click Edit;...

  • Page 111: Configuring Ethernet Port Groups

    The port names (strings) displayed in the Ethernet Group Settings table represent the physical ports on the device. For the mapping of these strings to the physical ports, see 'Configuring Physical Ethernet Ports' on page 109. Version 6.8 Mediant 500 E-SBC...
  • Page 112 Mediant 500 E-SBC The following procedure describes how to configure Tx/Rx mode in the Web interface. You can also configure this using the table ini file parameter, EtherGroupTable or CLI command, configure voip/ether-group. Notes: • Before you can re-assign a port to a different Ethernet Group, you must first remove the port from its current Ethernet Group.
  • Page 113 Note: Before you can re-assign a port to a different Ethernet Group, you must first remove the port from its current Ethernet Group. To remove the port, either set this field to None or to a different port. Version 6.8 Mediant 500 E-SBC...

  • Page 114: Configuring Underlying Ethernet Devices

    Mediant 500 E-SBC 12.3 Configuring Underlying Ethernet Devices The Ethernet Device table lets you configure up to 16 Ethernet Devices (underlying devices). An Ethernet Device represents a Layer-2 bridging device and is assigned with a VLAN ID. An Ethernet Device is associated with an IP network interface in the Interface table ('Underlying Device' field) and/or with a static route in the Static Route table ('Device Name' field).

  • Page 115: Configuring Ip Network Interfaces

    12 interfaces, consisting of up to 11 Control and Media interfaces including a Maintenance interface if your device is deployed in a High Availability (HA) mode, and 1 OAMP interface. Each IP interface is configured with the following: Version 6.8 Mediant 500 E-SBC...
  • Page 116 Mediant 500 E-SBC  Application type allowed on the interface: • Control: call control signaling traffic (i.e., SIP) • Media: RTP traffic • Operations, Administration, Maintenance and Provisioning (OAMP): management (i.e., Web, CLI, and SNMP based management) • Maintenance: This interface is used in HA mode when two devices are deployed for redundancy, and represents one of the LAN interfaces or Ethernet groups on each device used for the Ethernet connectivity between the two devices.
  • Page 117 Configure the IP network interface according to the parameters described in the table below. Click Submit. To view configured network interfaces that are currently active, click the IP Interface Status Table button. For more information, see ''Viewing Active IP Interfaces'' on page 617. Version 6.8 Mediant 500 E-SBC...
  • Page 118 Mediant 500 E-SBC Table 12-4: Interface Table Parameters Description Parameter Description Table parameters Index Table index row of the interface. CLI: network-if The range is 0 to 11. [InterfaceTable_Index] Web: Application Type Defines the applications allowed on the interface. EMS: Application Types ...

  • Page 119: Assigning Ntp Services To Application Types

    The network interface types can be combined: • Example 1: ♦ One combined OAMP-Media-Control interface with an IPv4 address • Example 2: ♦ One OAMP interface with an IPv4 address ♦ One or more Control interfaces with IPv4 addresses Version 6.8 Mediant 500 E-SBC...

  • Page 120: Networking Configuration Examples

    Mediant 500 E-SBC ♦ One or more Media interfaces with IPv4 interfaces • Example 3: ♦ One OAMP with an IPv4 address ♦ One combined Media-Control interface with IPv4 address ♦ One combined Media-Control interface with IPv6 address  Each network interface can be configured with a Default Gateway. The address of the Default Gateway must be in the same subnet as the associated interface.

  • Page 121: Voip Interface Per Application Type

    Mode Gateway g Device Name OAMP IPv4 192.168.0.2 192.168.0.1 Mgmt Manual Media & IPv4 200.200.85.14 200.200.85. MediaCntrl1 Control Manual Media & IPv4 200.200.86.14 200.200.86. MediaCntrl2 Control Manual Media & IPv6 2000::1:200:200:86:1 V6CntrlMedia Control Manual Version 6.8 Mediant 500 E-SBC...
  • Page 122 Mediant 500 E-SBC Static Route table: A routing rule is required to allow remote management from a host in 176.85.49.0/24: Table 12-10: Example of Static Route Table Destination Prefix Length Gateway 176.85.49.0 192.168.0.10 The NTP application is configured (using the ini file) to serve as OAMP applications:...

  • Page 123: Voip Interfaces With Multiple Default Gateways

     To configure a static IP route: Open the Static Route Table page (Configuration tab > VoIP menu > Network > Static Route Table). Click Add; the following dialog box appears: Version 6.8 Mediant 500 E-SBC...
  • Page 124 Mediant 500 E-SBC Configure a static route according to the parameters described in the table below. Click Submit, and then reset the device with a burn-to-flash for your settings to take effect. Note: You can delete only static routing rules that are inactive.

  • Page 125: Configuration Example Of Static Ip Routes

     The static route in the Static Route table is associated with the IP network interface in the Interface table, using the 'Device Name' and 'Underlying Device' parameters, respectively. Version 6.8 Mediant 500 E-SBC...

  • Page 126: Troubleshooting The Routing Table

    Mediant 500 E-SBC  The static route's Gateway address in the Static Route table is in the same subnet as the IP address of the IP network interface in the Interface table. Figure 12-6: Example of using Static Route 12.5.2 Troubleshooting the Routing Table When adding a new static route to the Static Route table, the added rule passes a validation test.

  • Page 127: Configuring Quality Of Service

    SIP over TLS (SIPS) Control Premium control Syslog Management Bronze SNMP Traps Management Bronze DNS client Varies according to DNS settings: Depends on traffic type:   OAMP Control: Premium Control   Control Management: Bronze Version 6.8 Mediant 500 E-SBC...
  • Page 128 Mediant 500 E-SBC Application Traffic / Network Types Class-of-Service (Priority) Varies according to the interface Depends on traffic type: type associated with NTP (see  Control: Premium control ''Assigning NTP Services to  Management: Bronze Application Types'' on page 119): ...

  • Page 129: Configuring Icmp Messages

    To enable or disable sending and receipt of ICMP Redirect messages, use the 'Send and Receive ICMP Redirect Messages' parameter. To enable or disable the sending of ICMP Destination Unreachable messages, use the 'Send ICMP Unreachable Messages' parameter. Click Submit. Version 6.8 Mediant 500 E-SBC...

  • Page 130: Dns

    Mediant 500 E-SBC 12.8 You can use the device's embedded domain name server (DNS) or an external, third-party DNS to translate domain names into IP addresses. This is useful if domain names are used as the destination in call routing. The device supports the configuration of the following DNS types: ...

  • Page 131: Configuring The Internal Srv Table

    You can also configure this using the table ini file parameter, SRV2IP or CLI command, configure voip > voip-network dns srv2ip.  To configure an SRV rule: Open the Internal SRV Table page (Configuration tab > VoIP menu > Network > DNS > Internal SRV Table). Version 6.8 Mediant 500 E-SBC...
  • Page 132 Mediant 500 E-SBC Click Add; the following dialog box appears: Figure 12-11: Internal SRV Table Page Configure an SRV rule according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory.

  • Page 133: Network Address Translation Support

    If NAT is not configured by any of the above-mentioned methods, the device sends the packet according to its IP address configured in the Interface table. Note: The priority list above is applicable only to the Gateway calls. Version 6.8 Mediant 500 E-SBC...

  • Page 134: Configuring A Static Nat Ip Address For All Interfaces

    Mediant 500 E-SBC The figure below illustrates the NAT problem faced by the SIP networks where the device is located behind a NAT: Figure 12-12: Device behind NAT and NAT Issues 12.9.1.1 Configuring a Static NAT IP Address for All Interfaces You can configure a global (public) IP address of the router to enable static NAT between the device and the Internet for all network interfaces.

  • Page 135: Configuring Nat Translation Per Ip Interface

    Interface table. [NATTranslation_SourceIPInterfaceName] Target IP Address Defines the global IP address. This address is set in CLI: TargetIPAddress the SIP Via and Contact headers as well as in the o= [NATTranslation_TargetIPAddress] and c= SDP fields. Version 6.8 Mediant 500 E-SBC...

  • Page 136: Remote Ua Behind Nat

    Mediant 500 E-SBC Parameter Description Source Start Port Defines the optional starting port range (1-65536) of CLI: SourceStartPort the IP interface, used as matching criteria for this NAT [NATTranslation_SourceStartPort] rule. If not configured, the match is done on the entire port range.

  • Page 137: Media (Rtp/Rtcp/T.38)

    NAT Is Not Used: (Default) NAT feature is disabled. The device considers the UA as not located behind NAT and always sends the media packets to the UA using the IP address:port obtained from the first received SIP message. Version 6.8 Mediant 500 E-SBC...
  • Page 138 Mediant 500 E-SBC  NAT Is Used: NAT is always performed. The device considers the UA as located behind NAT and always sends the media packets to the UA using the source address obtained from the first media packet received from the UA. In this mode, the device does not send any packets until it receives the first packet from the UA (in order to obtain the IP address).

  • Page 139: Robust Receipt Of Media Streams By Media Latching

    12. Network 12.10 Robust Receipt of Media Streams by Media Latching The Robust Media mechanism (or media latching) is an AudioCodes proprietary mechanism to filter out unwanted media (RTP, RTCP, SRTP, SRTCP, and T.38) streams that are sent to the same port number of the device. Media ports may receive additional multiple unwanted media streams (from multiple sources of traffic) as result of traces of previous calls, call control errors, or deliberate malicious attacks (e.g., Denial of Service).

  • Page 140: Multiple Routers Support

    Mediant 500 E-SBC If you have set the InboundMediaLatchMode parameter to 1 or 2, scroll down to the Robust Settings group and do the following: • Define the minimum number of continuous media (RTP, RTCP, SRTP, and SRTCP) packets that need to be received by the channel before it can latch onto this new incoming stream: ♦...

  • Page 141: Security

    If you are using the High Availability feature and you have configured "block" rules, ensure that you also add "allow" rules for HA traffic. For more information, see Configuring Firewall Allowed Rules on page 534. Version 6.8 Mediant 500 E-SBC...
  • Page 142 Mediant 500 E-SBC The following procedure describes how to configure Firewall rules in the Web interface. You can also configure this using the table ini file parameter, AccessList or the CLI command, configure voip/access-list.  To configure a Firewall rule: Open the Firewall Settings page (Configuration tab >...
  • Page 143 ''Configuring IP Network Interfaces'' on page 115. Packet Size Defines the maximum allowed packet size. CLI: packet-size The valid range is 0 to 65535. [AccessList_Packet_Size] Note: When filtering fragmented IP packets, this field relates to the Version 6.8 Mediant 500 E-SBC...
  • Page 144 Mediant 500 E-SBC Parameter Description overall (re-assembled) packet size, and not to the size of each fragment. Byte Rate Defines the expected traffic rate (bytes per second), i.e., the allowed CLI: byte-rate bandwidth for the specified protocol. In addition to this field, the...

  • Page 145: Configuring General Security Settings

    TLS all the way to the destination (over multiple hops), set the 'Enable SIPS' (EnableSIPS) parameter to Enable in the SIP General Parameters page (Configuration tab > VoIP menu > SIP Definitions > General Parameters). Version 6.8 Mediant 500 E-SBC...

  • Page 146: Intrusion Detection System

    Mediant 500 E-SBC 13.3 Intrusion Detection System The device's Intrusion Detection System (IDS) feature detects malicious attacks on the device and reacts accordingly. A remote host is considered malicious if it has reached or exceeded a user-defined threshold (counter) of specified malicious attacks.

  • Page 147: Enabling Ids

    Open the IDS Policy Table page (Configuration tab > VoIP menu > Security > Intrusion Detection and Prevention > Policy Table); the table shows the pre- configured IDS policies: Figure 13-3: IDS Policy Table with Default Rules Version 6.8 Mediant 500 E-SBC...
  • Page 148 Mediant 500 E-SBC Click Add; the following dialog box appears: Figure 13-4: IDS Policy Table - Add Record Configure an IDS Policy name according to the parameters described in the table below. Click Submit. Table 13-3: IDS Policy Table Parameter Descriptions...
  • Page 149 [4] Dialog establish failure =  Classification failure (see ''Configuring Classification Rules'' on page 480)  Routing failure  Other local rejects (prior to SIP 180 response)  Remote rejects (prior to SIP 180 response) Version 6.8 Mediant 500 E-SBC...
  • Page 150 Mediant 500 E-SBC Parameter Description  [5] Abnormal flow =  Requests and responses without a matching transaction user (except ACK requests)  Requests and responses without a matching transaction (except ACK requests) Threshold Scope Defines the source of the attacker to consider in the device's CLI: threshold-scope detection count.

  • Page 151: Assigning Ids Policies

    A hyphen "-" indicates a range of SIP Interfaces (e.g., 3,4-7 means IDs 3, and 4 through 7)  A prefix of an exclamation mark "!" means negation of the set (e.g., !3,4-7 means all indexes excluding 3, and excluding 4 through 7) Version 6.8 Mediant 500 E-SBC...

  • Page 152: Viewing Ids Alarms

    Mediant 500 E-SBC Parameter Description Proxy Set ID Defines the Proxy Set(s) to which the IDS Policy is assigned. This CLI: proxy-set indicates the Proxy Sets from where the attacks are coming from. The [IDSMatch_ProxySet] following syntax is supported: ...
  • Page 153 The table below lists the Syslog text messages per malicious event: Table 13-6: Types of Malicious Events and Syslog Text String Type Description Syslog String Connection TLS authentication failure abuse-tls-auth-fail Abuse   Message exceeds a user-defined maximum malformed-invalid- Malformed Version 6.8 Mediant 500 E-SBC...
  • Page 154 Mediant 500 E-SBC Type Description Syslog String Messages message length (50K) msg-len   Any SIP parser error malformed-parse-error   Message policy match malformed-message- policy  Basic headers not present  malformed-miss-  Content length header not present (for TCP) header ...

  • Page 155: Media

    When silence is detected, it stops sending packets in the channel. The following procedure describes how to enable silence suppression using the Web interface. Version 6.8 Mediant 500 E-SBC...

  • Page 156: Echo Cancellation

    Mediant 500 E-SBC  To enable silence suppression using the Web interface: Open the Voice Settings page (Configuration tab > VoIP menu > Media > Voice Settings). Figure 14-2: Enabling Silence Suppression in Voice Settings Page Set the 'Silence Suppression' (EnableSilenceCompression) field to Enable.

  • Page 157: Fax And Modem Capabilities

    Some SIP parameters override these fax and modem parameters. For example, the IsFaxUsed parameter and V.152 parameters in Section ''V.152 Support'' on page 171. • For a detailed description of the parameters appearing on this page, see ''Configuration Parameters Reference'' on page 691. Version 6.8 Mediant 500 E-SBC...
  • Page 158 Mediant 500 E-SBC  To access the fax and modem parameters: Open the Fax/Modem/CID Settings page (Configuration tab > VoIP menu > Media > Fax/Modem/CID Settings). Configure the parameters, as required. Click Submit. User's Manual Document #: LTRT-10437...

  • Page 159: Fax/Modem Operating Modes

    You can also enable or disable Error Correction Mode (ECM) fax mode using the 'Fax Relay ECM Enable' parameter (FaxRelayECMEnable). When using T.38 mode, you can define a redundancy feature to improve fax transmission over congested IP networks. This feature is activated using the 'Fax Relay Redundancy Version 6.8 Mediant 500 E-SBC...
  • Page 160 Mediant 500 E-SBC Depth' parameter (FaxRelayRedundancyDepth) 'Fax Relay Enhanced Redundancy Depth' parameter (FaxRelayEnhancedRedundancyDepth). Although this is a proprietary redundancy scheme, it should not create problems when working with other T.38 decoders. 14.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.
  • Page 161 RTP method is used, whereby the device encapsulates the entire T.38 packet (payload with all its headers) in the sent RTP. For T.38 over RTP, AudioCodes devices use the proprietary identifier "AcUdptl" in the 'a=ftmp' line of the SDP. For example: o=AudiocodesGW 1357424688 1357424660 IN IP4 10.8.6.68...

  • Page 162: Fax / Modem Transport Mode

    Mediant 500 E-SBC 14.2.2.2 G.711 Fax / Modem Transport Mode In this mode, when the terminating device detects fax or modem signals (CED or AnsAM), it sends a Re-INVITE message to the originating device, requesting it to re-open the channel in G.711 VBD with the following adaptations: ...

  • Page 163: Fax/Modem Bypass Mode

    Configure the following optional parameters: • 'Fax/Modem Bypass Coder Type' (FaxModemBypassCoderType). • 'Fax Bypass Payload Type' (FaxBypassPayloadType) - in the RTP/RTCP Settings page (Configuration tab > VoIP menu > Media > RTP/RTCP Settings). • ModemBypassPayloadType (ini file). Version 6.8 Mediant 500 E-SBC...

  • Page 164: Fax / Modem Nse Mode

    INVITE messages are sent. The voice channel is optimized for fax/modem transmission (same as for usual bypass mode). The parameters defining payload type for AudioCodes proprietary Bypass mode -- 'Fax Bypass Payload Type' (RTP/RTCP Settings page) and ModemBypassPayloadType (ini file) -- are not used with NSE Bypass.

  • Page 165: Fax / Modem Transparent With Events Mode

    Fax (IsFaxUsed = 0). In the Fax/Modem/CID Settings page, do the following: Set the 'Fax Transport Mode' parameter to Disable (FaxTransportMode = 0). Set the 'V.21 Modem Transport Type' parameter to Disable (V21ModemTransportType = 0). Version 6.8 Mediant 500 E-SBC...

  • Page 166: Rfc 2833 Ans Report Upon Fax/Modem Detection

    Mediant 500 E-SBC Set the 'V.22 Modem Transport Type' parameter to Disable (V22ModemTransportType = 0). Set the 'V.23 Modem Transport Type' parameter to Disable (V23ModemTransportType = 0). Set the 'V.32 Modem Transport Type' parameter to Disable (V32ModemTransportType = 0). Set the 'V.34 Modem Transport Type' parameter to Disable (V34ModemTransportType = 0).

  • Page 167: Bypass Mechanism For V.34 Fax Transmission

    Set the ini file parameter, V34FaxTransportType to 2 (Bypass). 14.2.3.2 Relay Mode for T.30 and V.34 Faxes In this scenario, V.34 fax machines are forced to use their backward compatibility with T.30 faxes and operate in the slower T.30 mode. Version 6.8 Mediant 500 E-SBC...

  • Page 168: Fax Relay For Sg3 Fax Machines

    Mediant 500 E-SBC  To use T.38 mode for V.34 and T.30 faxes: In the Fax/Modem/CID Settings page, do the following: Set the 'Fax Transport Mode' parameter to Relay (FaxTransportMode = 1). Set the 'V.22 Modem Transport Type' parameter to Disable (V22ModemTransportType = 0).

  • Page 169: Modem Relay

    SIP INVITE and 200 OK, using the SDP body according to the USA Department of Defense (DoD) UCR-2008, Change 2 specification. This eliminates the need for sending a re-INVITE to negotiate V.150.1. The device sends an INVITE’s SDP offer in a Version 6.8 Mediant 500 E-SBC...

  • Page 170: Simultaneous Negotiation Of Fax (T.38) And Modem (V.150.1) Relay

    • The V.150.1 feature has been tested with certain IP phones. For more details, please contact your AudioCodes sales representative. • The V.150.1 SSE Tx payload type is according to the offered SDP of the remote side.

  • Page 171: Support

    SDP offer containing G.729 and “regular” G.711 coders, it sends an SDP answer containing G.729 and G.711 VBD coders, allowing subsequent bypass (passthrough) sessions if fax / modem signals are detected during the call. Version 6.8 Mediant 500 E-SBC...

  • Page 172: Fax Transmission Behind Nat

    Mediant 500 E-SBC 14.2.7 Fax Transmission behind NAT The device supports transmission from fax machines (connected to the device) located inside (behind) a Network Address Translation (NAT). Generally, the firewall blocks T.38 (and other) packets received from the WAN, unless the device behind the NAT sends at least one IP packet from the LAN to the WAN through the firewall.

  • Page 173: Comfort Noise Generation

    Open the RTP/RTCP Settings page (Configuration tab > VoIP menu > Media > RTP/RTCP Settings). The relevant parameters are listed under the 'General Settings' group, as shown below: Figure 14-4: Comfort Noise Parameter in RTP/RTCP Settings Page Version 6.8 Mediant 500 E-SBC...

  • Page 174: Dual-Tone Multi-Frequency Signaling

    Mediant 500 E-SBC Set the 'Comfort Noise Generation Negotiation' parameter (ComfortNoiseNegotiation) to Enable. Click Submit. Note: This feature is applicable only to the Gateway application. 14.3.3 Dual-Tone Multi-Frequency Signaling This section describes the configuration of Dual-Tone Multi-Frequency (DTMF) signaling. 14.3.3.1 Configuring DTMF Transport Types The device supports various methods for transporting DTMF digits over the IP network to the remote endpoint.

  • Page 175: Configuring Rfc 2833 Payload

    RTP/RTCP Settings). The relevant parameters are listed under the 'General Settings' group, as shown below: Figure 14-5: RFC 2833 Payload Parameters in RTP/RTCP Settings Page Configure the following parameters: • 'RTP Redundancy Depth' (RTPRedundancyDepth) - enables the device to generate RFC 2198 redundant packets. Version 6.8 Mediant 500 E-SBC...

  • Page 176: Configuring Rtp Base Udp Port

    Mediant 500 E-SBC • 'Enable RTP Redundancy Negotiation' (EnableRTPRedundancyNegotiation) - enables the device to include the RTP redundancy dynamic payload type in the SDP, according to RFC 2198. • 'RFC 2833 TX Payload Type' (RFC2833TxPayloadType) - defines the Tx RFC 2833 DTMF relay dynamic payload type.
  • Page 177 UDP port configured for a SIP Interface (see Configuring SIP Interfaces on page 259). For example, if your highest configured UDP port for a SIP Interface is 6060, you must configure the BaseUDPPort parameter to any value greater than 6060. Version 6.8 Mediant 500 E-SBC...

  • Page 178: Configuring Ip Media Settings

    Mediant 500 E-SBC 14.4 Configuring IP Media Settings This section describes the configuration of various IP media features. 14.4.1 Automatic Gain Control (AGC) Automatic Gain Control (AGC) adjusts the energy of the output signal to a required level (volume). This feature compensates for near-far gain differences. AGC estimates the energy of the incoming signal from the IP or PSTN, determined by the 'AGC Redirection' parameter, calculates the essential gain, and then performs amplification.

  • Page 179: Configuring Various Codec Attributes

    However, if it is included in the key it is ignored and the call does not fail. The device supports the following session parameters (as defined in RFC 4568, SDP Security Descriptions for Media Streams):  UNENCRYPTED_SRTP  UNENCRYPTED_SRTCP  UNAUTHENTICATED_SRTP Version 6.8 Mediant 500 E-SBC...
  • Page 180 Mediant 500 E-SBC Session parameters should be the same for the local and remote sides. When the device is the offering side, the session parameters are configured by the following parameter - 'Authentication On Transmitted RTP Packets', 'Encryption On Transmitted RTP Packets, and 'Encryption On Transmitted RTCP Packets'.

  • Page 181: Services

    Subnet Mask Option 3 Router Option 6 Domain Name Server Option 44 NetBIOS Name Server Option 46 NetBIOS Node Type Option 42 Network Time Protocol Server Option 2 Time Offset Option 66 TFTP Server Name Version 6.8 Mediant 500 E-SBC...
  • Page 182 Mediant 500 E-SBC DHCP Option Code DHCP Option Name Option 67 Boot file Name Option 120 SIP Server Once you have configured the DHCP server, you can configure the following:  DHCP Vendor Class Identifier names (DHCP Option 60) - see ''Configuring the Vendor Class Identifier'' on page ...
  • Page 183 Defines the IP address (IPv4) of the NetBIOS WINS server CLI: netbios-server that is available to a Microsoft DHCP client. The value is sent [DhcpServer_NetbiosNameServer] in DHCP Option 44 (NetBIOS Name Server). The default value is 0.0.0.0. Version 6.8 Mediant 500 E-SBC...
  • Page 184 Mediant 500 E-SBC Parameter Description Web: NetBIOS Node Type Defines the node type of the NetBIOS WINS server for a CLI: netbios-node-type Microsoft DHCP client. The value is sent in DHCP Option 46 [DhcpServer_NetbiosNodeType] (NetBIOS Node Type).  [0] Broadcast (default) ...

  • Page 185: Configuring The Vendor Class Identifier

    The VCI is a string that identifies the vendor and functionality of a DHCP client to the DHCP server. For example, Option 60 can show the unique type of hardware (e.g., "AudioCodes 440HD IP Phone") or firmware of the DHCP client. The DHCP server can then differentiate between DHCP clients and process their requests accordingly.

  • Page 186: Configuring Additional Dhcp Options

    Mediant 500 E-SBC Click Add; the following dialog box appears: Figure 15-2: DHCP Vendor Class Table - Add Record Dialog Box Configure a VCI for the DHCP server according to the parameters described in the table below. Click Submit. Table 15-3: DHCP Vendor Class Table Parameter Descriptions...
  • Page 187  [1] IP address = IPv4 address.  [2] Hexadecimal = Hexadecimal-encoded string. For example, if you set the 'Value' parameter to "company.com", you need to set the 'Type' parameter to ASCII. Version 6.8 Mediant 500 E-SBC...

  • Page 188: Configuring Static Ip Addresses For Dhcp Clients

    Mediant 500 E-SBC Parameter Description Web: Value Defines the value of the DHCP Option. For example, if you are CLI: value using Option 66, this parameter is used for specifying the TFTP [DhcpOption_Value] provisioning server (e.g., http://192.168.3.155:5000/provisioning/). The valid value is a string of up to 256 characters. By default, no value is defined.

  • Page 189: Viewing And Deleting Dhcp Clients

    To view DHCP clients according to MAC address: # show voip dhcp mac  To view DHCP clients that have been blacklisted from DHCP implementation (due to duplicated IP addresses in the network, where another device is using the same IP Version 6.8 Mediant 500 E-SBC...
  • Page 190 Mediant 500 E-SBC address as the one assigned to the client): # show voip dhcp black-list  To view or delete DHCP clients: Open the DHCP Servers page (Configuration tab > VoIP menu > Services > DHCP Severs). In the DHCP Servers table, select the row of the desired DHCP server for which you want to view DHCP clients, and then click the DHCP Clients Table link located at the bottom of the page;...

  • Page 191: Sip-Based Media Recording

    • For the maximum number of concurrent sessions that the device can record, contact your AudioCodes sales representative. Session recording is a critical requirement in many business communications environments such as call centers and financial trading floors. In some of these environments, all calls must be recorded for regulatory and compliance reasons.
  • Page 192 Mediant 500 E-SBC The device can record calls between two IP Groups. The type of calls to record can be specified by source and/or destination prefix number or SIP Request-URI, as well as by call initiator. The side ("leg") on which the recording is done must be specified. Specifying the leg is important as it determines the various call media attributes of the recorded RTP (or SRTP) such as coder type.
  • Page 193 0-15 m=audio 6030 RTP/AVP 8 96 c=IN IP4 10.33.8.70 a=ptime:20 a=sendonly a=label:2 a=rtpmap:8 PCMA/8000 a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-15 --boundary_ac1fffff85b Content-Type: application/rs-metadata Content-Disposition: recording-session <?xml version="1.0" encoding="UTF-8"?> <recording xmlns='urn:ietf:params:xml:ns:recording'> <datamode>complete</datamode> <group id="00000000-0000-0000-0000-00003a36c4e3"> <associate-time>2010-01-24T01:11:57Z</associate-time> </group> <session id="0000-0000-0000-0000-00000000d0d71a52"> Version 6.8 Mediant 500 E-SBC...

  • Page 194: Enabling Sip-Based Media Recording

    Mediant 500 E-SBC <group-ref>00000000-0000-0000-0000-00003a36c4e3</group-ref> <start-time>2010-01-24T01:11:57Z</start-time> <ac:AvayaUCID xmlns="urn:ietf:params:xml:ns:Avaya">FA080030C4E34B5B9E59</ac:Avay aUCID> </session> <participant id="1056" session="0000-0000-0000-0000- 00000000d0d71a52"> <nameID aor="1056@192.168.241.20"></nameID> <associate-time>2010-01-24T01:11:57Z</associate-time> <send>00000000-0000-0000-0000-1CF23A36C4E3</send> <recv>00000000-0000-0000-0000-BF583A36C4E3</recv> </participant> <participant id="182052092" session="0000-0000-0000-0000- 00000000d0d71a52"> <nameID aor="182052092@voicelab.local"></nameID> <associate-time>2010-01-24T01:11:57Z</associate-time> <recv>00000000-0000-0000-0000-1CF23A36C4E3</recv> <send>00000000-0000-0000-0000-BF583A36C4E3</send> </participant> <stream id="00000000-0000-0000-0000-1CF23A36C4E3" session="0000- 0000-0000-0000-00000000d0d71a52"> <label>1</label> </stream> <stream id="00000000-0000-0000-0000-BF583A36C4E3" session="0000- 0000-0000-0000-00000000d0d71a52"> <label>2</label>...

  • Page 195: Configuring Sip Recording Routing Rules

    SRTP. Recorded Source Prefix Defines calls to record based on source number or CLI: recorded-src-prefix URI. [SIPRecRouting_RecordedSourcePrefix] Recorded Destination Prefix Defines calls to record based on destination CLI: recorded-dst-prefix number or URI. [SIPRecRouting_RecordedDestinationPrefix] Version 6.8 Mediant 500 E-SBC...

  • Page 196: Configuring Sip User Part For Srs

    SIP message, typically in the INVITE and the first 18x response. If the device receives a SIP message with Genesys SIP header, it adds the header's information to AudioCodes' proprietary tag in the XML metadata of the SIP INVITE that it sends to the recording server, as shown below: <ac:GenesysUUID...

  • Page 197: Avaya Ucid

    If the device receives a SIP INVITE from Avaya, it adds the UCID value, received in the User-to-User SIP header to AudioCodes' proprietary tag in the XML metadata of the SIP INVITE that it sends to the recording server. For example, if the received SIP header is: User-to-User: 00FA080019001038F725B3;encoding=hex...

  • Page 198: Radius Authentication

    Mediant 500 E-SBC 15.3 RADIUS Authentication You can enhance security for your device by implementing Remote Authentication Dial-In User Service (RADIUS - RFC 2865) for authenticating multiple management user accounts of the device’s embedded Web and Telnet (CLI) servers. Thus, RADIUS also prevents unauthorized access to your device.

  • Page 199: Setting Up A Third-Party Radius Server

     To set up a third-party RADIUS server (e.g., FreeRADIUS): Define the AudioCodes device as an authorized client of the RADIUS server, with the following: • Predefined shared secret (password used to secure communication between the device and the RADIUS server) •...

  • Page 200: Configuring Radius Authentication

    Mediant 500 E-SBC 15.3.2 Configuring RADIUS Authentication The following procedure describes how to configure the RADIUS feature. For a detailed description of the RADIUS parameters, see 'RADIUS Parameters' on page 734.  To configure RADIUS: Open the Authentication Settings page (Configuration tab > System menu >...

  • Page 201: Securing Radius Communication

    However, authentication with the RADIUS server can also be done immediately after the user enters the URL, if the URL also contains the login credentials, example: http://10.4.4.112/Forms/RadiusAuthentication?WSBackUserName=John&WSBackPasswor d=1234 Note: This feature allows up to five simultaneous users only. Version 6.8 Mediant 500 E-SBC...

  • Page 202: Ldap-Based Management And Sip Services

    Mediant 500 E-SBC 15.4 LDAP-based Management and SIP Services The device supports the Lightweight Directory Access Protocol (LDAP) application protocol and can operate with third-party, LDAP-compliant servers such as Microsoft Active Directory (AD). You can use LDAP for the following LDAP services: ...

  • Page 203: Enabling The Ldap Service

    Figure 15-9: Enabling LDAP on the LDAP Settings Page Under LDAP Settings, from the 'LDAP Service' drop-down list, select Enable. Click Submit, and then reset the device with a burn-to-flash for your settings to take effect. Version 6.8 Mediant 500 E-SBC...

  • Page 204: Enabling Ldap-Based Web/Cli User Login Authentication And Authorization

    Mediant 500 E-SBC 15.4.2 Enabling LDAP-based Web/CLI User Login Authentication and Authorization The LDAP service can be used for authenticating and authorizing device management users (Web and CLI), based on the user's login username and password (credentials). At the same, it can also be used to determine users' management access levels (privileges).
  • Page 205 LDAP server for authenticating the user's username-password combination. For example, $. Note: By default, the device sends the password in clear-text format. You can enable the device to encrypt the password using TLS (see the 'Use SSL' parameter below). Version 6.8 Mediant 500 E-SBC...
  • Page 206 Mediant 500 E-SBC Parameter Description LDAP Bind DN Defines the LDAP server's bind Distinguished Name (DN) or username. CLI: bind-dn  LDAP-based SIP queries: The DN is used as the username during [LdapConfiguration_Ld connection and binding to the LDAP server. The DN is used to apConfBindDn] uniquely name an AD object.

  • Page 207: Configuring Ldap Dns (Base Paths) Per Ldap Server

    Figure 15-12: LDAP Search DN Table - Add Record Configure an LDAP DN base path according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Version 6.8 Mediant 500 E-SBC...

  • Page 208: Configuring The Ldap Search Filter Attribute

    Mediant 500 E-SBC LDAP Search DN Table Parameter Descriptions Parameter Description Index Defines an index number for the new table record. CLI: set internal-index Note: Each table row must be configured with a unique index. [LdapServersSearchD Ns_Index] Base Path Defines the full path (DN) to the objects in the AD where the query is CLI: set base-path done.

  • Page 209: Configuring Access Level Per Management Groups Attributes

    Search base object (distinguished name or DN, e.g., "ou=ABC,dc=corp,dc=abc,dc=com"), which defines the location in the directory from which the LDAP search begins. This is configured in 'Configuring LDAP DNs (Base Paths) per LDAP Server' on page 207. Version 6.8 Mediant 500 E-SBC...
  • Page 210 Mediant 500 E-SBC  Filter (e.g., "(&(objectClass=person)(sAMAccountName=johnd))"), which filters the search in the subtree to include only the login username (and excludes others). This is configured by the 'LDAP Authentication Filter' parameter.  Attribute (e.g., "memberOf") to return from objects that match the filter criteria. This attribute is configured by the 'Management Attribute' parameter in the LDAP Configuration table.

  • Page 211: Configuring Ldap Search Methods

    The device can optionally store recent LDAP queries and responses with an LDAP server in its local cache. The cache is used for subsequent queries and/or in case of LDAP server failure. Note: The LDAP Cache feature is applicable only to LDAP-based SIP queries (Control). Version 6.8 Mediant 500 E-SBC...
  • Page 212 Mediant 500 E-SBC The advantage of enabling this feature includes the following:  Improves routing decision performance by using local cache for subsequent LDAP queries  Reduces number of queries performed on an LDAP server and corresponding bandwidth consumption ...

  • Page 213: Configuring Local Database For Management User Authentication

    Web Users table. To configure local Web/CLI users in the Web Users table, see Configuring Web User Accounts. Notes: • This feature is applicable to LDAP and RADIUS servers. • This feature is applicable only to user management authentication. Version 6.8 Mediant 500 E-SBC...
  • Page 214 Mediant 500 E-SBC  To use the Web Users table for authenticating management users: Open the Authentication Settings page (Configuration tab > System menu > Management > Authentication Settings). Figure 15-18: Authentication Settings Page - Local Database for Login Authentication Under General Login Authentication Settings: •...

  • Page 215: Ldap-Based Login Authentication Example

    The LDAP server's entry data structure schema in the example is as follows:  DN (base path): OU=testMgmt,OU=QA,DC=testqa,DC=local. The DN path to search for the username in the directory is shown below: Figure 15-19: Base Path (DN) in LDAP Server Version 6.8 Mediant 500 E-SBC...
  • Page 216 Mediant 500 E-SBC  Search Attribute Filter: (sAMAccountName=$). The login username is found based on this attribute (where the attribute's value equals the username): Figure 15-20: Username Found using sAMAccount Attribute Search Filter  Management Attribute: memberOf. The attribute contains the member groups of the...
  • Page 217 The search attribute filter based on username is configured by the 'LDAP Authentication Filter' parameter in the LDAP Settings page (see 'Configuring the LDAP Search Filter Attribute' on page 208): Figure 15-24: Configuring Search Attribute Filter Version 6.8 Mediant 500 E-SBC...
  • Page 218 Mediant 500 E-SBC  The group management attribute is configured by the 'Management Attribute' parameter in the LDAP Configuration table: Figure 15-25: Configuring Management Attribute  The management group and its corresponding access level is configured in the Management LDAP Groups table (see 'Configuring Access Level per Management...

  • Page 219: Active Directory-Based Routing For Microsoft Lync

    Primary or Secondary key. MSLDAPPrimaryKey Primary Key query search instead of PBX msRTCSIP-PrivateLine= key - can be any AD attribute +3233554480 MSLDAPSecondaryKey Secondary Key query key search if Primary Key fails - can be any attribute Version 6.8 Mediant 500 E-SBC...
  • Page 220 Mediant 500 E-SBC The process for querying the AD and subsequent routing based on the query results is as follows: If the Primary Key is configured, it uses the defined string as a primary key instead of the one defined in MSLDAPPBXNumAttributeName. It requests the attributes which are described below.
  • Page 221 The flowchart below summarizes the device's process for querying the AD and routing the call based on the query results: Figure 15-27: LDAP Query Flowchart Note: If you are using the device's local LDAP cache, see 'Configuring the Device's LDAP Cache' on page for the LDAP query process. Version 6.8 Mediant 500 E-SBC...

  • Page 222: Configuring Ad-Based Routing Rules

    Mediant 500 E-SBC 15.4.11.2 Configuring AD-Based Routing Rules The following procedure describes how to configure outbound IP routing based on LDAP queries.  To configure LDAP-based IP routing for Lync Server: Configure the LDAP server parameters, as described in 'Configuring LDAP Servers' on page 204.
  • Page 223 Rule 5: Sends call to IP address of device (10.33.45.80) if AD query failure (e.g., no response from LDAP server or attribute not found).  Rule 6: Sends query for original destination number of received call to the LDAP server. Version 6.8 Mediant 500 E-SBC...

  • Page 224: Querying The Ad For Calling Name

    Mediant 500 E-SBC  Rule 7: Alternative routing rule that sends the call of original dialed number to IP destination 10.33.45.72. This rule is applied in any of the following cases • LDAP functionality is disabled. • LDAP query is successful but call fails (due to, for example, busy line) to all the...

  • Page 225: Least Cost Routing

    Note that for one minute, Cost Groups "A" and "D" are identical, but due to the average call duration, Cost Group "D" is cheaper. Therefore, average call duration is an important factor in determining the cheapest routing role. Below are a few examples of how you can implement LCR: Version 6.8 Mediant 500 E-SBC...
  • Page 226 Mediant 500 E-SBC  Example 1: This example uses two different Cost Groups for routing local calls and international calls: Two Cost Groups are configured as shown below: Cost Group Connection Cost Minute Cost 1. "Local Calls" 2. "International Calls"...

  • Page 227: Configuring Lcr

    Cost Groups in the Outbound IP Routing table. The following procedure describes how to enable LCR in the Web interface. You can also do this using the table ini file parameter, RoutingRuleGroups or CLI command, configure voip > services least-cost-routing routing-rule-groups. Version 6.8 Mediant 500 E-SBC...
  • Page 228 Mediant 500 E-SBC  To enable LCR: Open the Routing Rule Groups Table page (Configuration tab > VoIP menu > Services > Least Cost Routing > Routing Rule Groups Table). Click Add; the following dialog box appears: Figure 15-30: Routing Rule Groups Table - Add Record Enable LCR according to the parameters described in the table below.

  • Page 229: Configuring Cost Groups

    The valid value range is 0-65533. The default is 0. onCost] Note: When calculating the cost of a call, if the current time of the call is not within a time band configured for the Cost Group, then this default connection cost is used. Version 6.8 Mediant 500 E-SBC...

  • Page 230: Configuring Time Bands For Cost Groups

    Mediant 500 E-SBC Parameter Description Default Minute Cost Defines the call charge per minute for a call outside the time CLI: default-minute-cost bands. [CostGroupTable_DefaultMinuteC The valid value range is 0-65533. The default is 0. ost] Note: When calculating the cost of a call, if the current time of the call is not within a time band configured for the Cost Group, then this default charge per minute is used.

  • Page 231: Assigning Cost Groups To Routing Rules

    To use your configured Cost Groups, you need to assign them to routing rules:  Gateway application: Outbound IP Routing table - see Configuring Outbound IP Routing Table on page  SBC application: IP-to-IP Routing table - see Configuring SBC IP-to-IP Routing Rules on page Version 6.8 Mediant 500 E-SBC...

  • Page 232: Configuring Call Setup Rules

    Mediant 500 E-SBC 15.6 Configuring Call Setup Rules The Call Setup Rules table lets you configure up to 40 Call Setup rules. Call Setup rules define various sequences that are run upon the receipt of an incoming call (dialog) at call setup, before the device routes the call to its destination.
  • Page 233 10 Set IDs, where each Set ID can include up to 10 rules. The Set ID is used to assign the Call Setup rules to a routing rule in the routing table. The valid value is 0 to 9. The default is 0. Version 6.8 Mediant 500 E-SBC...
  • Page 234 Mediant 500 E-SBC Parameter Description Attributes To Query Defines the query string that the device sends to the LDAP CLI: attr-to-query server. [CallSetupRules_AttributesToQuery] The valid value is a string of up to 100 characters. Combined strings and values can be configured like in the Message Manipulations table, using the '+' operator.
  • Page 235 The valid value is a string of up to 300 characters (case- [CallSetupRules_ActionValue] insensitive). Examples:  '+9723976'+ldap.attr.alternateNumber  '9764000'  ldap.attr.displayName  true (if the 'Action Type' is set to Exit)  false (if the 'Action Type' is set to Exit) Version 6.8 Mediant 500 E-SBC...

  • Page 236: Call Setup Rule Examples

    Mediant 500 E-SBC 15.6.1 Call Setup Rule Examples Below are configuration examples for using Call Setup Rules.  Example 1: This example configures the device to replace (manipulate) the incoming call's source number with a number retrieved from the AD by an LDAP query. The device queries the AD server for the attribute record, "telephoneNumber"...
  • Page 237 Rules Set ID. ♦ Index 1:  'Call Setup Rules Set Id': 3  'Destination IP Group ID': 3 (IP Group for Lync) ♦ Index 2:  'Destination IP Group ID': 4 (IP Group of PBX) Version 6.8 Mediant 500 E-SBC...
  • Page 238 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10437...

  • Page 239: Quality Of Experience

    The device can be configured to report voice (media) Quality of Experience (QoE) to AudioCodes' Session Experience Manager (SEM) server, a plug-in for AudioCodes EMS. The reports include real-time metrics of the quality of the actual call experience, which are then processed by the SEM.

  • Page 240: Configuring Clock Synchronization Between Device And Sem

    In other words, you need to configure them with the same NTP server. The NTP server can be one of the following:  AudioCodes EMS server (also acting as an NTP server)  Third-party, external NTP server Once you have determined the NTP server, all the elements--device, SEM, and EMS--must be configured with the same NTP server address.
  • Page 241  Report the change in the measured metrics to AudioCodes' Session Experience Manager (SEM) server. The SEM displays this call quality status for the associated SEM link (IP Group, Media Realm, or Remote Media Subnet). For configuring the SEM server's address, see ''Configuring SEM Server'' on page 239.
  • Page 242 Mediant 500 E-SBC Table 16-1: Quality of Experience Profile Table Parameter Descriptions Parameter Description Index Defines an index number for the new table record. [QOEProfile_Index] Profile Name Defines an arbitrary name to easily identify the QoE Profile. CLI: name The valid value is a string of up to 20 characters.
  • Page 243 SEM indicating this wHysteresis] change. Note: If the monitored parameter crosses two thresholds at once (e.g., from Green to Red), the device ignores the hysteresis value and reports the call state change to the SEM. Version 6.8 Mediant 500 E-SBC...

  • Page 244: Configuring Bandwidth Profiles

    Mediant 500 E-SBC Parameter Description Yellow Red Threshold Defines the parameter threshold values between Yellow (medium CLI: yellow-red-threshold quality) and Red (poor quality) states. [QOEColorRules_YellowRedT The valid threshold values are as follows: hreshold]  MOS values are in multiples of 10. For example, to denote a MOS of 3.2, the value 32 (i.e., 3.2*10) must be entered.
  • Page 245 Defines the outgoing audio traffic threshold (in Kbps). CLI: egress-audio-bandwidth [BWProfile_EgressAudioBandwidth] Ingress Audio Bandwidth Defines the incoming audio traffic threshold (in Kbps). CLI: ingress-audio-bandwidth [BWProfile_IngressAudioBandwidth] Egress Video Bandwidth Defines the outgoing video traffic threshold (in Kbps). CLI: egress-video-bandwidth [BWProfile_EgressVideoBandwidth] Version 6.8 Mediant 500 E-SBC...
  • Page 246 Mediant 500 E-SBC Parameter Description Ingress Video Bandwidth Defines the incoming video traffic threshold (in Kbps). CLI: ingress-video-bandwidth [BWProfile_IngressVideoBandwidth] Total Egress Bandwidth Defines the total (video and audio) outgoing bandwidth CLI: total-egress-bandwidth threshold (in Kbps). [BWProfile_TotalEgressBandwidth] Total Ingress Bandwidth Defines the total (video and audio) incoming bandwidth CLI: total-ingress-bandwidth threshold (in Kbps).

  • Page 247: Configuring Media Enhancement Profiles

    Web interface. You can also configure Media Enhancement Profiles using other management platforms:  Media Enhancement Profile table: Table ini file parameter, MediaEnhancementProfile or CLI command, configure voip/qoe media-enhancement  Media Enhancement Rules table: Table ini file parameter, MediaEnhancementRules or CLI command, configure voip/qoe media-enhancement-rules Version 6.8 Mediant 500 E-SBC...
  • Page 248 Mediant 500 E-SBC  To configure a Media Enhancement Profile: Open the Media Enhancement Profile page (Configuration tab > VoIP menu > Quality of Experience > Media Enhancement Profile). Click Add; the following dialog box appears: Figure 16-5: Media Enhancement Profile Table - Add Record Configure a Media Enhancement Profile according to the parameters described in the table below.
  • Page 249 Defines an alternative IP Profile ID for the IP Group that CLI: value is associated with this rule, if this rule is applied. This [MediaEnhancementRules_ActionValue] parameter is applicable only if the 'Rule Action' parameter is set to Alternative IP Profile. Version 6.8 Mediant 500 E-SBC...
  • Page 250 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10437...

  • Page 251: Control Network

    The following procedure describes how to configure Media Realms in the Web interface. You can also configure Media Realms using the table ini file parameter, CpMediaRealm or CLI command, configure voip/voip-network realm. Version 6.8 Mediant 500 E-SBC...
  • Page 252 Mediant 500 E-SBC  To configure a Media Realm: Open the Media Realm Table page (Configuration tab > VoIP menu > VoIP Network > Media Realm Configuration). Click Add; the following dialog box appears: Figure 17-1: Media Realm Page - Add Record Dialog Box Configure the Media Realm according to the parameters described in the table below.
  • Page 253 QoE Profiles, see ''Configuring Quality of Experience [CpMediaRealm_QoeProfile] Profiles'' on page 240. BW Profile Assigns a Bandwidth Profile to the Media Realm. For CLI: bw-profile configuring Bandwidth Profiles, see ''Configuring Bandwidth [CpMediaRealm_BWProfile] Profiles'' on page 244. Version 6.8 Mediant 500 E-SBC...

  • Page 254: Configuring Remote Media Subnets

    Mediant 500 E-SBC 17.2 Configuring Remote Media Subnets Remote Media Subnets define destination subnets for media (RTP/SRTP) traffic on a specific Media Realm. Each Remote Media Subnet can be assigned different call quality (Quality of Experience Profile) and bandwidth utilization (Bandwidth Profile) profiles. These profiles are configured in ''Configuring Quality of Experience Profiles'' on page ''Configuring Bandwidth Profiles'' on page 244, respectively.
  • Page 255 The default is 0.0.0.0. [RemoteMediaSubnet_DstIPAddress] QOE Profile Name Assigns a Quality of Experience Profile to the CLI: qoe-profile Remote Media Subnet. [RemoteMediaSubnet_QOEProfileName] BW Profile Name Assigns a Bandwidth Profile to the Remote CLI: bw-profile Media Subnet. [RemoteMediaSubnet_BWProfileName] Version 6.8 Mediant 500 E-SBC...

  • Page 256: Configuring Srds

    Mediant 500 E-SBC 17.3 Configuring SRDs The SRD table lets you configure up to 32 signaling routing domains (SRD). An SRD represents a logical VoIP network. Each logical or physical connection requires an SRD. For example, if the device interfaces with both the LAN and WAN, you need to configure an SRD for each one.
  • Page 257 WAN and the other on the LAN. The reason for this is that in Media Anchoring, the device does not interfere in the SIP signaling such as manipulation of IP Version 6.8 Mediant 500 E-SBC...
  • Page 258 Mediant 500 E-SBC Parameter Description addresses, which is necessary for calls between LAN and WAN.  When the global parameter SBCDirectMedia is disabled, Media Anchoring can only be enabled for calls between endpoints belonging to the same SRD.  For more information on Media Anchoring, see No Media Anchoring (Anti-Tromboning) on page 451.

  • Page 259: Configuring Sip Interfaces

    Table 17-4: SIP Interface Table Parameter Descriptions Parameter Description Index Defines an index for the new table record. [SIPInterface_Index] The valid value is 0 to 31. Interface Name Defines an arbitrary name to easily identify the SIP Interface. Version 6.8 Mediant 500 E-SBC...
  • Page 260 Mediant 500 E-SBC Parameter Description CLI: interface-name The valid value is a string of up to 21 characters. [SIPInterface_InterfaceName Network Interface Assigns a Control-type IP network interface to the SIP Interface. This CLI: network-interface string value must be identical (case-sensitive) to that configured in...
  • Page 261 NAT entry open for clients located behind a NAT server, or simply to Enable] check that the connection to the IP entity is available.  [0] Disable (default)  [1] Enable Note: For configuring TCP keepalive, use the following ini file parameters: TCPKeepAliveTime, TCPKeepAliveInterval, and TCPKeepAliveRetry. Version 6.8 Mediant 500 E-SBC...
  • Page 262 Mediant 500 E-SBC Parameter Description Classification Failure Defines the SIP response code that the device sends if a received Response Type SIP request (OPTIONS, REGISTER, or INVITE) has failed the SBC CLI: Classification process. classification_fail_response_ty The valid value can be a SIP response code from 400 through 699, or it can be set to 0 to not send any response at all.

  • Page 263: Configuring Ip Groups

    Proxy Set takes precedence. The following procedure describes how to configure IP Groups in the Web interface. You can also configure IP Groups using the table ini file parameter, IPGroup or CLI command, configure voip > control-network ip-group. Version 6.8 Mediant 500 E-SBC...
  • Page 264 Mediant 500 E-SBC  To configure an IP Group: Open the IP Group Table page (Configuration tab > VoIP menu > VoIP Network > IP Group Table). Click Add; the following dialog box appears: Figure 17-5: IP Group Table - Add Dialog Box Configure an IP Group according to to the parameters described in the table below.
  • Page 265 IP Group, or the host name in the From header [IPGroup_SIPGroupName] of INVITE messages received from this IP Group. In other words, it replaces the original host name. The valid value is a string of up to 100 characters. The default is an Version 6.8 Mediant 500 E-SBC...
  • Page 266 Mediant 500 E-SBC Parameter Description empty field. Notes:  If this parameter is not configured, the value of the global parameter, ProxyName is used instead (see ''Configuring Proxy and Registration Parameters'' on page 285).  The parameter overrides inbound message manipulation rules that manipulate the host name in Request-URI, To, and/or From SIP headers.
  • Page 267 [1] Yes = The device sends SIP requests and responses to the source IP address received in the previous SIP message packet. For information on NAT traversal, see Remote UA behind NAT on page 136. Version 6.8 Mediant 500 E-SBC...
  • Page 268 Mediant 500 E-SBC Parameter Description CLI: Msg-Man-User-Defined- Defines a value for the SIP user part that can be used in Message String1 Manipulation rules configured in the Message Manipulations table. The [IPGroup_MsgManUserDef Message Manipulation rule obtains this value from the IP Group, by using the following syntax: param.ipg.<src|dst>.user-defined.<0>.
  • Page 269 Serving IP Group. The Request-URI host name in the INVITE messages are set to the value of the ‘SIP Group Name’ parameter defined for the Serving IP Group. Notes:  This parameter is applicable only to the IP-to-IP application. Version 6.8 Mediant 500 E-SBC...
  • Page 270 Mediant 500 E-SBC Parameter Description  If the PreferRouteTable parameter is set to 1, the routing rules in the Outbound IP Routing table take precedence over this ‘Serving IP Group ID’ parameter.  If this parameter is not configured, the INVITE messages are sent to the default Proxy or according to the Outbound IP Routing table.
  • Page 271 The default value is null. Multiple entries are separated by a backslash "\", for example, INVITE\REGISTER. Note: This parameter is applicable only if the 'Authentication Mode' parameter is set to SBC as Server [2]. Version 6.8 Mediant 500 E-SBC...
  • Page 272 Mediant 500 E-SBC Parameter Description SBC Client Forking Mode Defines call forking of INVITE messages to up to five separate SIP CLI: enable-sbc-client- outgoing legs for User-type IP Groups. This occurs if multiple contacts forking are registered under the same AOR in the device's registration [IPGroup_EnableSBCClient database.
  • Page 273 'Authentication Mode' parameter is set to SBC as Server (i.e., authentication of servers).  To specify the SIP request types (e.g., INVITE) that must be challenged by the device, use the 'Authentication Method List' parameter. Version 6.8 Mediant 500 E-SBC...

  • Page 274: Configuring Proxy Sets

    Mediant 500 E-SBC Parameter Description Password Defines the shared password for authenticating the IP Group, when CLI: password the device acts as an Authentication server. IPGroup_Password] The valid value is a string of up to 51 characters. By default, no password is defined.
  • Page 275 CLI: voip-network proxy-ip >  [0] UDP transport-type  [1] TCP [ProxyIp_TransportType]  [2] TLS  [-1] = Undefined Note: If this parameter is not defined, the settings of the global parameter SIPTransportType is used. Version 6.8 Mediant 500 E-SBC...
  • Page 276 Mediant 500 E-SBC Parameter Description Proxy Name Defines an arbitrary name to easily identify the Proxy Set. CLI: proxy-name The valid value is a string of up to 20 characters. [ProxySet_ProxyName] DNS Resolve Method Defines the DNS query record type for resolving the Proxy server's CLI: dns-resolve-method host name into an IP address.
  • Page 277 Proxy server to is-proxy-hot-swap redundant Proxies when no response is received from the primary. [ProxySet_IsProxyHotSwap]  [0] No (default)  [1] Yes = The device sends the SIP INVITE/REGISTER message Version 6.8 Mediant 500 E-SBC...
  • Page 278 Mediant 500 E-SBC Parameter Description to the first address (Proxy/Registrar server) listed in the Proxy Set. If a SIP response is received and this response code is defined in the 'Keep Alive Failure Response' parameter (above), the device assumes the Proxy as down and sends the message again;...
  • Page 279 UDP, the device uses UDP to communicate with the proxy and no TLS Context is used. For more information about how certificates are associated with calls and for configuring TLS Contexts, see Configuring SSL/TLS Certificates on page 91. Version 6.8 Mediant 500 E-SBC...
  • Page 280 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10437...

  • Page 281: Sip Definitions

    Proxy & Registration page. The following procedure describes how to configure Accounts in the Web interface. You can also configure Accounts using the table ini file parameter, Account or CLI command, configure voip > sip-definition account. Version 6.8 Mediant 500 E-SBC...
  • Page 282 Mediant 500 E-SBC  To configure an Account: Open the Account Table page (Configuration tab > VoIP menu > SIP Definitions > Account Table). Click Add; the following dialog box appears: Configure an account according to the parameters described in the table below.
  • Page 283 If this parameter is not configured, the 'Contact User' parameter in the IP Group table is used instead.  If registration fails, the user part in the INVITE Contact header contains the source party number. Version 6.8 Mediant 500 E-SBC...

  • Page 284: Regular Registration Mode

    Mediant 500 E-SBC Parameter Description Application Type Defines the application type: CLI: application-type  [0] GW/IP2IP = (Default) Gateway and IP-to-IP application. [Account_ApplicationType]  [2] SBC = SBC application. 18.2.1 Regular Registration Mode When you configure the registration mode in the Account table to Regular, the device sends REGISTER requests to the Serving IP Group.

  • Page 285: Configuring Proxy And Registration Parameters

    For a description of the parameters appearing on this page, see ''Configuration Parameters Reference'' on page 691. Note: To view the registration status of endpoints with a SIP Registrar/Proxy server, see Viewing Endpoint Registration Status on page 625. Version 6.8 Mediant 500 E-SBC...
  • Page 286 Mediant 500 E-SBC  To configure the Proxy and registration parameters: Open the Proxy & Registration page (Configuration tab > VoIP menu > SIP Definitions > Proxy & Registration). Configure the parameters as required. Click Submit.  To register or un-register the device to a Proxy/Registrar: ...

  • Page 287: Sip Message Authentication Example

    • The password from the ini file is "AudioCodes". • The equation to be evaluated is "122:audiocodes.com:AudioCodes". According to the RFC, this part is called A1. • The MD5 algorithm is run on this equation and stored for future usage.
  • Page 288 Mediant 500 E-SBC • The equation to be evaluated is "REGISTER:sip:10.2.2.222". • The MD5 algorithm is run on this equation and stored for future usage. • The result is "a9a031cfddcb10d91c8e7b4926086f7e". Final stage: • A1 result: The nonce from the proxy response is "11432d6bce58ddf02e3b5e1c77c010d2".

  • Page 289: Configuring Sip Message Manipulation

    Deletion of SIP body (e.g., if a message body is not supported at the destination network this body is removed)  Translating one SIP response code to another  Topology hiding (generally present in SIP headers such as Via, Record Route, Route Version 6.8 Mediant 500 E-SBC...
  • Page 290 Mediant 500 E-SBC and Service-Route).  Configurable identity hiding (information related to identity of subscribers, for example, P-Asserted-Identity, Referred-By, Identity and Identity-Info)  Apply conditions per rule - the condition can be on parts of the message or call’s parameters ...
  • Page 291 Figure 18-3: Message Manipulations Table - Add Record Dialog Box Configure a Message Manipulation rule according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Version 6.8 Mediant 500 E-SBC...
  • Page 292 Mediant 500 E-SBC An example of configured message manipulation rules are shown in the figure below: Figure 18-4: Message Manipulations Page  Index 0: Adds the suffix ".com" to the host part of the To header.  Index 1: Changes the user part of the From header to the user part of the P-Asserted- ...
  • Page 293 Previous Condition, Index 4 and 5 use the condition configured for Index 3. A configuration example is shown in the beginning of this section. The option allows you to use the same condition for multiple manipulation rules. Version 6.8 Mediant 500 E-SBC...

  • Page 294: Configuring Sip Message Policy Rules

    Mediant 500 E-SBC Parameter Description Notes:  When configured to Use Previous Condition, the 'Message Type' and 'Condition' parameters are not applicable and if configured are ignored.  When multiple manipulation rules apply to the same header, the next rule applies to the resultant string of the previous rule.
  • Page 295 SIP 513 'Message Too Large' response. Max Num Bodies Defines the maximum number of bodies (e.g., SDP) in the CLI: max-num-bodies SIP message. [MessagePolicy_MaxNumBodies] The valid value is any number up to 8. The default is 8. Version 6.8 Mediant 500 E-SBC...
  • Page 296 Mediant 500 E-SBC Parameter Description Send Rejection Determines whether the device sends a 400 "Bad CLI: send-rejection Request" response if a message request is rejected. [MessagePolicy_SendRejection]  [0] Policy Reject = (Default) If the message is a request, then the device sends a response to reject the request.

  • Page 297: Coders And Profiles

     To configure coders: Open the Coders page (Configuration tab > VoIP menu > Coders and Profiles > Coders). Figure 19-1: Coders Table Page Configure coders according to the parameters described in the table below. Version 6.8 Mediant 500 E-SBC...
  • Page 298 Mediant 500 E-SBC Click Submit, and then reset the device with a save ("burn") to flash memory. Table 19-1: Coders Table Parameter Descriptions Parameter Description Coder Name Defines the coder. CLI: name Note: Each coder type (e.g., G.729) can be configured only once [CodersGroup0_Name] in the table.
  • Page 299 20 (default), 40, 60, 80, Dynamic; [Silk-8Khz] and 100 Default 76 silk-wb 20 (default), 40, 60, 80, Dynamic; [Silk-16Khz] and 100 Default 77 T.38 [t38fax] T.38 Version 3 [t38fax] T.38 Over RTP Dynamic (90 - 127); Default 106 Version 6.8 Mediant 500 E-SBC...

  • Page 300: Configuring Coder Groups

    Mediant 500 E-SBC 19.2 Configuring Coder Groups The Coder Group Settings table lets you configure up to 10 Coder Groups. A Coder Group is a set of configured coders (coder type, packetization time, rate, payload type, and silence suppression). Each Coder Group can include up to 10 coders.

  • Page 301: Configuring Tel Profile

    Trunk Group table (see Configuring Trunk Group Table on page 353)). The following procedure describes how to configure Tel Profiles in the Web interface. You can also configure Tel Profiles using the table ini file parameter, TelProfile or CLI command, configure voip/coders-and-profiles tel-profile. Version 6.8 Mediant 500 E-SBC...
  • Page 302 Mediant 500 E-SBC  To configure a Tel Profile: Open the Tel Profile Settings page (Configuration tab > VoIP menu > Coders and Profiles > Tel Profile Settings). Click Add; the following dialog box appears: Configure a Tel Profile according to the parameters described in the table below. For a description of each parameter, refer to the corresponding "global"...
  • Page 303 Web: Dynamic Jitter Buffer Optimization Factor DJBufOptFactor CLI: jitter-buffer-optimization-factor [TelProfile_JitterBufOptFactor] Web: DTMF Volume DTMFVolume CLI: dtmf-volume [TelProfile_DtmfVolume] Web: Input Gain InputGain CLI: input-gain [TelProfile_InputGain] Web: Voice Volume VoiceVolume CLI: voice-volume [TelProfile_VoiceVolume] Web: Echo Canceler EnableEchoCanceller CLI: echo-canceller [TelProfile_EnableEC] Version 6.8 Mediant 500 E-SBC...

  • Page 304: Configuring Ip Profiles

    Mediant 500 E-SBC Tel Profile Parameter Global Parameter Web: Enable AGC EnableAGC CLI: enable-agc [TelProfile_EnableAGC] Web: EC NLP Mode ECNLPMode CLI: echo-canceller-nlp-mode [TelProfile_ECNlpMode] 19.4 Configuring IP Profiles The IP Profile Settings table lets you configure up to 20 IP Profiles. An IP Profile is a set of parameters with user-defined settings relating to signaling (e.g., SIP message terminations...
  • Page 305 The order of the coders is determined by the preference.  This parameter is applicable only to the Gateway application. Web: Dynamic Jitter Buffer Minimum Defines the minimum delay (in msec) of the device's Version 6.8 Mediant 500 E-SBC...
  • Page 306 Mediant 500 E-SBC Parameter Description Delay dynamic Jitter Buffer. CLI: jitter-buffer-minimum-delay The valid range is 0 to 150. The default delay is 10. [IpProfile_JitterBufMinDelay] Notes:  For more information on the Jitter Buffer, see Dynamic Jitter Buffer Operation on page 172.
  • Page 307 RTP packets are received by the device) is changed without notifying the device, the device rejects these RTP packets. To overcome this, configure the DisconnectOnBrokenConnection parameter to 0. By this configuration, the device doesn't detect RTP packets Version 6.8 Mediant 500 E-SBC...
  • Page 308 Mediant 500 E-SBC Parameter Description arriving from the original source IP address and switches (after 300 msec) to the RTP packets arriving from the new source IP address.  The corresponding global parameter is DisconnectOnBrokenConnection. Web: Input Gain Defines the pulse-code modulation (PCM) input gain control CLI: input-gain (in decibels).
  • Page 309 SIP entity. [IpProfile_GenerateSRTPKeys]  [0] Only If Required= (Default) The device generates an SRTP key only if necessary.  [1] Always = The device always generates a new SRTP Version 6.8 Mediant 500 E-SBC...
  • Page 310 Mediant 500 E-SBC Parameter Description key. Jitter Buffer Max Delay Defines the maximum delay and length (in msec) of the Jitter CLI: jitter-buffer-max-delay Buffer. [IpProfile_JitterBufMaxDelay] The valid range is 150 to 2,000. The default is 250. Web: Coders Group ID...
  • Page 311 0 for G.711 -Law). The parameters defining payload type for the 'old' Bypass mode FaxBypassPayloadType and ModemBypassPayloadType are not used with NSE Bypass. The bypass packet interval is configured according to the FaxModemBypassBasicRtpPacketInterval parameter. Version 6.8 Mediant 500 E-SBC...
  • Page 312 Mediant 500 E-SBC Parameter Description The SDP contains the following line: 'a=rtpmap:100 X-NSE/8000'. Notes:  When enabled, the following conditions must also be met:  The Cisco gateway must include the following definition: 'modem passthrough nse payload-type 100 codec g711alaw'.
  • Page 313 [1] After Manipulation = Copies the called number after manipulation. The device first performs IP-to-Tel destination phone number manipulation, and only then copies the manipulated called number to the redirect number sent in the Q.931 Setup message to the Tel. Version 6.8 Mediant 500 E-SBC...
  • Page 314 Mediant 500 E-SBC Parameter Description Thus, the called and redirect numbers are the same.  [2] Before Manipulation = Copies the called number before manipulation. The device first copies the original called number to the SIP Diversion header, and then performs IP-to-Tel destination phone number manipulation.
  • Page 315  The corresponding global parameter is TxDTMFOption. Web: Second Tx DTMF Option Defines the second preferred transmit DTMF negotiation CLI: second-tx-dtmf-option method. For a description, see IpProfile_FirstTxDtmfOption [IpProfile_SecondTxDtmfOption] (above). Note: The corresponding global parameter is Version 6.8 Mediant 500 E-SBC...
  • Page 316 Mediant 500 E-SBC Parameter Description TxDTMFOption Web: Rx DTMF Option Enables the device to declare the RFC 2833 'telephony- CLI: rx-dtmf-option event' parameter in the SDP. [IpProfile_RxDTMFOption]  [0] Not Supported  [3] Supported (default) The device is always receptive to RFC 2833 DTMF relay packets.
  • Page 317 CLI: sbc-allowed-media-types type appears in the SDP 'm=' line (e.g., 'm=audio'). The [IPProfile_SBCAllowedMediaTypes] device permits only media types that appear in both the SDP offer and this configured list. If no common media types exist Version 6.8 Mediant 500 E-SBC...
  • Page 318 Mediant 500 E-SBC Parameter Description between the SDP offer and this list, the device drops the call. The valid value is a string of up to 64 characters. To configure multiple media types, separate the strings with a comma, e.g., "media, audio" (without quotes). By default, no media types are configured (i.e., all media types are...
  • Page 319 [4] INFO - Lucent = INFO, Korea Note: If the device interworks between different DTMF methods and one of the methods is in-band DTMF packets (RFC 2833), detection and generation of DTMF methods requires DSP resources. Version 6.8 Mediant 500 E-SBC...
  • Page 320 Mediant 500 E-SBC Parameter Description Web: P-Asserted-Identity Defines the device's handling of the SIP P-Asserted-Identity CLI: sbc-assert-identity header for this SIP entity. This header indicates how the [IpProfile_SBCAssertIdentity] outgoing SIP message asserts identity.  [0] As Is = (Default) P-Asserted Identity header is not...
  • Page 321 Extension Coders Group ID for IP Profiles that do not support delayed offer. Web: Remote REFER Behavior Defines the device's handling of REFER requests for this CLI: sbc-rmt-refer-behavior SIP entity. [IpProfile_SBCRemoteReferBehavior]  [0] Regular = (Default) Refer-To header is unchanged Version 6.8 Mediant 500 E-SBC...
  • Page 322 Mediant 500 E-SBC Parameter Description and the device forwards the REFER as is.  [1] Database URL = Changes the Refer-To header so that the re-routed INVITE is sent through the SBC: Before forwarding the REFER request, the device changes the host part to the device's IP address and adds a special prefix ("T~&R_") to the Contact user...
  • Page 323 SBC call leg for this SIP entity.  [0] Don't enforce = (Default) Device forwards the MKI size as is.  [1] Enforce = Device changes the MKI length according to the settings of the IP Profile parameter, MKISize. Version 6.8 Mediant 500 E-SBC...
  • Page 324 Mediant 500 E-SBC Parameter Description Web: Remote Early Media RTP Defines whether the destination UA sends RTP immediately Behavior after it sends 18x response. CLI: sbc-rmt-early-media-rtp  [0] Immediate = (Default) Remote client sends RTP [IpProfile_SBCRemoteEarlyMediaRTP immediately after it sends 18x response with early media.
  • Page 325 Replaces header to reflect the call identifiers of the leg.  [1] Handle Locally = The SIP entity does not support INVITE messages containing Replaces headers. The device terminates the received INVITE containing the Version 6.8 Mediant 500 E-SBC...
  • Page 326 Mediant 500 E-SBC Parameter Description Replaces header and establishes a new call between the SIP entity and the new call party. It then disconnects the call with the initial call party, by sending it a SIP BYE request.  [2] Keep as is = The SIP entity supports INVITE messages containing Replaces headers.
  • Page 327 RTP periods. In other words, the device does not generate RTCP when there is no RTP traffic (such as when a call is on hold). Note: The corresponding global parameter is SBCRTCPMode. Version 6.8 Mediant 500 E-SBC...
  • Page 328 Minimum Delay' (DJBufMinDelay) and 'Dynamic Jitter Buffer Optimization Factor' (DJBufOptFactor) can be used to configure minimum packet delay only when transcoding is employed.  This functionality may require DSP resources. For more information, contact your AudioCodes sales representative. User's Manual Document #: LTRT-10437...

  • Page 329: Gateway Application

    Part V Gateway Application...

  • Page 331: Introduction

    IP-to-Tel refers to calls received from the IP network and destined to the PSTN/PBX (i.e., telephone connected directly or indirectly to the device); Tel-to-IP refers to calls received from the PSTN/PBX, and destined for the IP network. Version 6.8 Mediant 500 E-SBC...
  • Page 332 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10437...

  • Page 333: Digital Pstn

    E1 Euro ISDN and E1 CAS (subject to the constraints in the device's Release Notes). • If the protocol type is CAS, you can assign or modify a dial plan (in the 'Dial Plan' field) and perform this without stopping the trunk. Version 6.8 Mediant 500 E-SBC...
  • Page 334 Mediant 500 E-SBC  To configure trunks: Open the Trunk Settings page (Configuration tab > VoIP menu > PSTN > Trunk Settings). On the top of the page, a bar with Trunk number icons displays the status of each trunk, according to the following color codes: •...

  • Page 335: Tdm And Timing

    For a description of these parameters, see ''PSTN Parameters'' on page 819.  To configure the TDM Bus settings: Open the TDM page (Configuration tab > VoIP menu > TDM > TDM Bus Settings). Figure 21-2: TDM Bus Settings Page Version 6.8 Mediant 500 E-SBC...

  • Page 336: Clock Settings

    Mediant 500 E-SBC Configure the parameters as required. Click Submit. Save the changes to flash memory, see ''Saving Configuration'' on page 542. 21.2.2 Clock Settings In a traditional TDM service network such as PSTN, both ends of the TDM connection must be synchronized.

  • Page 337: Configuring Internal Clock As Clock Source

    Settings page, by clicking the trunk number in the 'Related Trunks' field, and in the Trunk Settings page, select the required Trunk number icon, and then click Apply Trunk Settings. Click Submit, and then reset the device (see ''Resetting the Device'' on page 539). Version 6.8 Mediant 500 E-SBC...
  • Page 338 Mediant 500 E-SBC Notes: • The CAS state machine can only be configured using the Web-based management tool. • Don't modify the default values unless you fully understand the implications of the changes and know the default values. Every change affects the configuration of the state machine parameters and the call process related to the trunk you are using with this state machine.
  • Page 339 Defines which Signaling System to use in both directions [CasStateMachineDigitSignalingSyst (detection\generation).  [0] DTMF = Uses DTMF signaling.  [1] MF = Uses MF signaling (default).  [-1] Default = Default value - use value from CAS state machine. Version 6.8 Mediant 500 E-SBC...

  • Page 340: Configuring Digital Gateway Parameters

    Mediant 500 E-SBC 21.4 Configuring Digital Gateway Parameters The Digital Gateway Parameters page allows you to configure miscellaneous digital parameters. For a description of these parameters, see ''Configuration Parameters Reference'' on page 691.  To configure the digital gateway parameters: Open the Digital Gateway Parameters page (Configuration tab >...

  • Page 341: Tunneling Applications

    For tunneling 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'). Version 6.8 Mediant 500 E-SBC...
  • Page 342 Mediant 500 E-SBC Note: For TDM over IP, the parameter CallerIDTransportType must be set to '0' (disabled), i.e., transparent. Below is an example of ini files for two devices implementing TDM Tunneling for four E1 spans. Note that in this example both devices are dedicated to TDM tunneling.
  • Page 343 CodersGroup0 1 = Transparent; [ \CodersGroup0 ] [TelProfile] FORMAT TelProfile_Index = TelProfile_ProfileName, TelProfile_TelPreference, TelProfile_CodersGroupID, TelProfile_IsFaxUsed, TelProfile_JitterBufMinDelay, TelProfile_JitterBufOptFactor, TelProfile_IPDiffServ, TelProfile_SigIPDiffServ, TelProfile_DtmfVolume, TelProfile_InputGain, TelProfile_VoiceVolume, TelProfile_EnableReversePolarity, 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] Version 6.8 Mediant 500 E-SBC...

  • Page 344: Dsp Pattern Detector

    Mediant 500 E-SBC 21.5.1.1 DSP Pattern Detector For TDM tunneling applications, you can use the DSP pattern detector feature to initiate the echo canceller at call start. The device can be configured to support detection of a specific one-byte idle data pattern transmitted over digital E1/T1 timeslots. The device can be configured to detect up to four different one-byte data patterns.

  • Page 345: Isdn Non-Facility Associated Signaling (Nfas)

    To assign a number of T1 trunks to the same NFAS group, use the NFASGroupNumber_x = groupID (where x is the physical trunk ID (0 to the maximum number of trunks) or the Web interface (see ''Configuring Trunk Settings'' on page 333). Version 6.8 Mediant 500 E-SBC...

  • Page 346: Nfas Interface Id

    Mediant 500 E-SBC The parameter DchConfig_x = Trunk_type defines the type of NFAS trunk. Trunk_type is set to 0 for the primary trunk, to 1 for the backup trunk, and to 2 for an ordinary NFAS trunk. ‘x’ denotes the physical trunk ID (0 to the maximum number of trunks). You can also use the Web interface (see ''Configuring Trunk Settings'' on page 333).

  • Page 347: Creating An Nfas-Related Trunk Configuration

    • All trunks in the group must be configured with the same values for trunk parameters TerminationSide, ProtocolType, FramingMethod, and LineCode. • After stopping or deleting the backup trunk, delete the group and then reconfigure Version 6.8 Mediant 500 E-SBC...

  • Page 348: Performing Manual D-Channel Switchover In Nfas Group

    Mediant 500 E-SBC 21.6.4 Performing Manual D-Channel Switchover in NFAS Group If an NFAS group is configured with two D-channels (Primary and Backup), you can do a manual switchover between these D-channels.  To manually switchover from active to standby D-channel: Open the NFAS Group &...

  • Page 349: Interworking Isdn Overlap Dialing With Sip According To Rfc 3578

    • MuteDTMFInOverlap: Enables the device to ignore in-band DTMF digits received during overlap dialing. Note: If the device receives SIP 4xx responses during the overlap dialing (while collecting digits), it does not release the call. Version 6.8 Mediant 500 E-SBC...
  • Page 350 Mediant 500 E-SBC  Interworking SIP to ISDN overlap dialing (IP to Tel): The device sends the first digits (e.g., "331") received from the initial SIP INVITE message to the Tel side in an ISDN Setup message. Each time it receives additional (collected) digits for the same dialog, which are received from subsequent SIP re-INVITE messages or SIP INFO messages, it sends them to the Tel side in SIP Q.931 Information messages.

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

    NI-2 4/5ESS Euro ISDN QSIG NT-to-TE TE-to-NT Table 21-3: Redirect Number NT/TE Interface DMS-100 NI-2 4/5ESS Euro ISDN QSIG NT-to-TE TE-to-NT Yes* * When using ETSI DivertingLegInformation2 in a Facility IE (not Redirecting Number IE). Version 6.8 Mediant 500 E-SBC...
  • Page 352 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10437...

  • Page 353: Trunk Group

    ''Configuring Hunt Group Settings'' on page 355).  To register the Trunk Groups, click the Register button, located below the Trunk Group table.  To unregister the Trunk Groups, click the Unregister button, located below the Trunk Group table. Version 6.8 Mediant 500 E-SBC...
  • Page 354 Mediant 500 E-SBC Table 22-1: Trunk Group Table Parameter Descriptions Parameter Description Module Defines the module (i.e., PRI) for which you want to define the CLI: module Trunk Group. [TrunkGroup_Module] From Trunk Defines the starting physical Trunk number in the Trunk Group.

  • Page 355: Configuring Trunk Group Settings

    Open the Trunk Group Settings page (Configuration tab > VoIP menu > GW and IP to IP > Trunk Group > Trunk Group Settings). Configure a Trunk Group according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Version 6.8 Mediant 500 E-SBC...
  • Page 356 Mediant 500 E-SBC Table 22-2: Trunk Group Settings Parameter Descriptions Parameter Description Trunk Group ID Defines the Trunk Group ID that you want to configure. CLI: trunk-group-id [TrunkGroupSettings_TrunkGr oupId] Channel Select Mode Defines the method by which IP-to-Tel calls are assigned to the CLI: channel-select-mode channels of the Trunk Group.
  • Page 357 From: <sip:101@GatewayName>;tag=1c862422082 To: <sip:101@GatewayName> Call-ID: 9907977062512000232825@10.33.37.78 CSeq: 3 REGISTER Contact: <sip:101@10.33.37.78>;expires=3600 Expires: 3600 User-Agent: Sip-Gateway/v.6.60A.011.002 Content-Length: 0 The "SipGroupName" in the Request-URI is configured in the IP Group table (see ''Configuring IP Groups'' on page 263). Version 6.8 Mediant 500 E-SBC...
  • Page 358 Mediant 500 E-SBC Parameter Description Notes:  If this parameter is not configured, the registration is performed according to the global registration parameter, ChannelSelectMode.  To enable Trunk Group registration, set the global parameter, IsRegisterNeeded to 1. This is unnecessary for 'Per Account' registration mode.
  • Page 359 Voice Mail on page 440. Admin State (Read-only) Displays the administrators state:  "Locked": The Lock command has been chosen from the Action drop-down button.  "Unlocked": The Unlock command has been chosen from the Action drop-down button. Version 6.8 Mediant 500 E-SBC...
  • Page 360 Mediant 500 E-SBC Parameter Description Status (Read-only) Displays the current status of the trunks/channels in the Trunk Group:  "In Service": Indicates that all channels in the Trunk Group are in service, for example, when the Trunk Group is unlocked or Busy Out state cleared (see the EnableBusyOut parameter for more information).

  • Page 361: Manipulation

    551 and uses rule index 2 for numbers that start with 550, 552, 553, and so on until 559. However, if you configure the source prefix number as "55" for rule index 1 and "551" for rule index 2, the device applies rule index 1 to all numbers that start with 55, including Version 6.8 Mediant 500 E-SBC...
  • Page 362 Mediant 500 E-SBC numbers that start with 551. If the device doesn't find a matching rule, no manipulation is done on the call. You can perform a second "round" (additional) of source and destination number manipulations for IP-to-Tel calls, on an already manipulated number. The initial and additional number manipulation rules are both configured in the number manipulation tables for Ip-to-Tel calls.
  • Page 363 2001, it is changed to 3146. Parameter Rule 1 Rule 2 Rule 3 Rule 4 Rule 5 Source IP Group Destination [6,7,8] Prefix Source Prefix 1001 123451001# [30-40]x 2001 Stripped Digits from Left Stripped Digits from Right Prefix to Add Version 6.8 Mediant 500 E-SBC...
  • Page 364 Mediant 500 E-SBC Parameter Rule 1 Rule 2 Rule 3 Rule 4 Rule 5 Suffix to Add Number of Digits to Leave Presentation Allowed Restricted Table 23-1: Number Manipulation Tables Parameter Descriptions Parameter Description Index Defines an index number for the new table record.
  • Page 365 [Prefix2Add] Web: Suffix to Add Defines the number or string that you want added to the end of the EMS: Prefix/Suffix To Add telephone number. For example, if you enter 00 and the phone number Version 6.8 Mediant 500 E-SBC...
  • Page 366 Mediant 500 E-SBC Parameter Description CLI: suffix-to-add is 1234, the new number is 123400. [Suffix2Add] Web/EMS: Number of Defines the number of digits that you want to keep from the right of the Digits to Leave phone number. For example, if you enter 4 and the phone number is CLI: num-of-digits-to-leave 00165751234, then the new number is 1234.

  • Page 367: Manipulating Number Prefix

    In this configuration example, the following manipulation process occurs: The prefix is calculated as 020215. The first seven digits from the left are removed from the original number, thereby changing the number to 8888888. The prefix that was previously calculated is then added. Version 6.8 Mediant 500 E-SBC...

  • Page 368: Sip Calling Name Manipulations

    Mediant 500 E-SBC 23.4 SIP Calling Name Manipulations The calling name manipulation tables lets you configure up to 120 manipulation rules for manipulating the calling name (i.e., caller ID) in SIP messages, for IP-to-Tel and Tel-to-IP calls. Manipulation includes modifying or removing the calling name. The calling name manipulation tables include the following: ...
  • Page 369 ''Dialing Plan Notation for Routing and Manipulation Tables'' on page 689. The default value is the asterisk (*) symbol (i.e., any source prefix). Web: Calling Name Prefix Defines the caller name (i.e., caller ID) prefix. Version 6.8 Mediant 500 E-SBC...
  • Page 370 Mediant 500 E-SBC Parameter Description CLI: calling-name-prefix You can use special notations for denoting the prefix. For example, to [_CallingNamePrefix] denote calls without a calling name, use the $ sign. For a description of available notations, see ''Dialing Plan Notation for Routing and Manipulation Tables'' on page 689.

  • Page 371: Configuring Redirect Number Ip To Tel

    The device searches the table from top to bottom for the first rule that matches the characteristics of the incoming call. If it finds a matching rule, it applies the manipulation configured for that rule. Version 6.8 Mediant 500 E-SBC...
  • Page 372 Mediant 500 E-SBC Notes: • If the device copies the received destination number to the outgoing SIP redirect number (enabled by the CopyDest2RedirectNumber parameter), no redirect number Tel-to-IP manipulation is done. • The manipulation rules are done in the following order: Stripped Digits From Left, Stripped Digits From Right, Number of Digits to Leave, Prefix to Add, and then Suffix to Add.
  • Page 373 This parameter is applicable only to the Redirect Number IP-to-Tel table.  If the P-Asserted-Identity header is present in the incoming INVITE message, then the value of this parameter is compared to the P- Asserted-Identity URI host name (instead of to the From header). Version 6.8 Mediant 500 E-SBC...
  • Page 374 Mediant 500 E-SBC Parameter Description Web: Destination Host Prefix Defines the Request-URI host name prefix, which appears in the CLI: dst-host-prefix incoming SIP INVITE message. [_DestHost] The default value is the asterisk (*) symbol (i.e., any prefix). Note: This parameter is applicable only to the Redirect Number IP-to- Tel table.

  • Page 375: Manipulating Redirected And Diverted Numbers For Call Diversion

    Suffix to Add Number of Digits to Leave After the above manipulation is done, the device sends the following outgoing SIP 302 response: SIP/2.0 302 Moved Temporarily Via: SIP/2.0/TLS 10.33.45.68;branch=z9hG4bKac54132643;alias From: "MP118 1" <sip:8001@10.33.45.68>;tag=1c54119560 To: <sip:6001@10.33.45.69;user=phone>;tag=1c664560944 Version 6.8 Mediant 500 E-SBC...

  • Page 376: Mapping Npi/Ton To Sip Phone-Context

    Mediant 500 E-SBC Call-ID: 541189832710201115142@10.33.45.68 CSeq: 1 INVITE Contact: <sip:8005@10.33.45.68;user=phone> Supported: em,timer,replaces,path,early-session,resource-priority Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUB SCRIBE,UPDATE Diversion: <tel:6005>;reason=unknown;counter=1 Server: Audiocodes-Sip-Gateway-IPmedia 260_UN/v.6.20A.043.001 Reason: SIP ;cause=302 ;text="302 Moved Temporarily" Content-Length: 0 23.7 Mapping NPI/TON to SIP Phone-Context The Phone Context table lets you configure rules for mapping the Numbering Plan Indication (NPI) and Type of Number (TON) to the SIP 'phone-context' parameter, and vice versa.
  • Page 377 If you selected E.164 Public as the NPI, you can select one of the following:  [0] Unknown  [1] International  [2] National  [3] Network Specific  [4] Subscriber  [6] Abbreviated Phone Context Defines the SIP 'phone-context' URI parameter. CLI: context [PhoneContext_Context] Version 6.8 Mediant 500 E-SBC...

  • Page 378: Configuring Release Cause Mapping

    Mediant 500 E-SBC 23.8 Configuring Release Cause Mapping The release cause mapping tables let you configure rules to map up to 12 different ISDN ITU-T Q.850 release cause codes (call failure) to SIP response codes, and vice versa. These tables allow you to override the default ISDN-SIP release cause mappings, described in ''Fixed Mapping of ISDN Release Reason to SIP Response'' on page ''Fixed Mapping of SIP Response to ISDN Release Reason'' on page 379.

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

    Request entity too long Interworking Request URI too long Interworking 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 Version 6.8 Mediant 500 E-SBC...

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

    Mediant 500 E-SBC ISDN Release SIP Response Description Description Reason Address incomplete Invalid number format Ambiguous Unallocated number Busy here User busy Not acceptable here Normal, unspecified Server internal error Temporary failure Not implemented Network out of order Bad gateway...
  • Page 381 No call suspended 503* Service unavailable Call having the requested call identity 408* Request timeout has been cleared User not member of CUG Service unavailable Incompatible destination Service unavailable Invalid transit network selection 502* Bad gateway Version 6.8 Mediant 500 E-SBC...
  • Page 382 Mediant 500 E-SBC ISDN Release Description Description Reason Response Invalid message Service unavailable Mandatory information element is 409* Conflict missing 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 383: Reason Header

    If the message isn’t a final response, it is translated to a Q.850 cause. • When the Reason header is received twice (i.e., SIP Reason and Q.850), the Q.850 takes precedence over the SIP reason and is sent to the Tel side. Version 6.8 Mediant 500 E-SBC...

  • Page 384: Numbering Plans And Type Of Number

    Mediant 500 E-SBC 23.9 Numbering Plans and Type of Number The IP-to-Tel destination or source number manipulation tables allow you to classify numbers by their Numbering Plan Indication (NPI) and Type of Number (TON). The device supports all NPI/TON classifications used in the ETSI ISDN variant, as shown in the table...

  • Page 385: Routing

    If it finds a matching rule, it sends the call to the IP destination configured for that rule. If it doesn't find a matching rule, it rejects the call. Matching Characteristics: One or more characteristics can be defined for the rule: Version 6.8 Mediant 500 E-SBC...
  • Page 386 Mediant 500 E-SBC • Source IP Group (to which the call belongs) • Source and destination Request-URI host name prefix • Source Trunk Group (from where the call is received) • Source (calling) and destination (called) telephone number prefix and suffix •...
  • Page 387 IP addresses. Instead of an IP address, you can use an FQDN to resolve into two IP addresses. For more information on alternative routing, see ''Alternative Routing for Tel-to-IP Calls'' on page 400. Version 6.8 Mediant 500 E-SBC...
  • Page 388 Mediant 500 E-SBC  Advice of Charge (AOC): AOC is a pre-billing feature that tasks the rating engine with calculating the cost of using a service (Tel-to-IP call) and relaying that information to the customer. AOC, which is configured in the Charge Codes table, can be applied per Tel-to-IP routing rule.
  • Page 389 [1] Route calls after manipulation = Calls are routed after the number manipulation rules are applied. Notes:  This parameter is not applicable if outbound proxy routing is used.  For number manipulation, see ''Configuring Source/Destination Number Manipulation'' on page 361. Version 6.8 Mediant 500 E-SBC...
  • Page 390 Mediant 500 E-SBC Parameter Description Route Name Defines an arbitrary name to easily identify the routing rule. CLI: route-name The valid value is a string of up to 20 characters. By default, no [PREFIX_RouteName] value is defined. Matching Call Characteristics Web: Src.
  • Page 391 Prefix' field, enter 00 and in the 'Dest IP Address' field, enter 0.0.0.0.  For routing calls between phones connected to the device (i.e., local routing), enter the device's IP address.  When the device's IP address is unknown (e.g., when DHCP is Version 6.8 Mediant 500 E-SBC...
  • Page 392 Mediant 500 E-SBC Parameter Description used), enter IP address 127.0.0.1.  When using domain names, enter the DNS server's IP address or alternatively, configure these names in the Internal DNS table (see ''Configuring the Internal DNS Table'' on page 130).
  • Page 393 1, 3, and 4 (all belonging to Forking Group "1"), and if the destination is unavailable and alternative routing is enabled, the device sends the call according to index entry 2.  Table index entry 1 is defined with Forking Group "1", index Version 6.8 Mediant 500 E-SBC...

  • Page 394: Configuring Inbound Ip Routing Table

    Mediant 500 E-SBC Parameter Description entry 2 with Forking Group "3", index entry 3 with Forking Group "2", and index entry 4 with Forking Group "1": The device first sends the call according to index entries 1 and 4 (all belonging to Forking Group "1"), and if the destination is...
  • Page 395 The following procedure describes how to configure Inbound IP Routing rules in the Web interface. You can also configure Inbound IP Routing rules using the table ini file parameter, PSTNPrefix or CLI command, configure voip > gw routing ip2tel-routing. Version 6.8 Mediant 500 E-SBC...
  • Page 396 Mediant 500 E-SBC  To configure IP-to-Tel or inbound IP routing rules: Open the Inbound IP Routing Table page (Configuration tab > VoIP menu > GW and IP to IP > Routing > IP to Trunk Group Routing). Figure 24-3: Inbound IP Routing Table The previous figure displays the following configured routing rules: •...
  • Page 397 CLI: src-srd-id Note: When the incoming INVITE matches the SRD in the [PstnPrefix_SrcSRDID] routing rule, if the 'Source IP Group ID' parameter (see below) is defined and it is associated with a different SRD, the Version 6.8 Mediant 500 E-SBC...
  • Page 398 Mediant 500 E-SBC Parameter Description incoming SIP call is rejected. If the 'Source IP Group ID' parameter is not defined, the SRD's default IP Group is used. If there is no valid source IP Group, the call is rejected. Call Setup Rules Set ID Assigns a Call Setup Rule Set ID to the routing rule.

  • Page 399: Ip Destinations Connectivity Feature

    You can view the connectivity status of IP destinations in the following Web interface pages:  Outbound IP Routing Table: The connectivity status of the IP destination per routing rule is displayed in the 'Status' column. For more information, see ''Configuring Outbound IP Routing Table'' on page 385. Version 6.8 Mediant 500 E-SBC...

  • Page 400: Alternative Routing For Tel-To-Ip Calls

    Mediant 500 E-SBC  IP Connectivity: This page displays a more informative connectivity status of the IP destinations used in Tel-to-IP routing rules in the Outbound IP Routing table. For viewing this page, see ''Viewing IP Connectivity'' on page 627.

  • Page 401: Alternative Routing Based On Sip Responses

    Tel-to-IP routing rules, see ''Configuring Outbound IP Routing Table'' on page 385. The table below shows an example of alternative routing where the device uses the first available alternative routing rule to re-route the initial, unsuccessful Tel-to-IP call destination: Version 6.8 Mediant 500 E-SBC...
  • Page 402 Mediant 500 E-SBC Table 24-5: Alternative Routing based on SIP Response Code Example Destination IP Destination SIP Response Rule Used? Phone Prefix 408 Request Main Route 10.33.45.68 Timeout Alternative Route #1 10.33.45.70 486 Busy Here Alternative Route #2 10.33.45.72 200 OK ...

  • Page 403: Alternative Routing Upon Sip 3Xx With Multiple Contacts

    The device tries each contact sequentially, listed in the Contact headers. If a SIP 6xx Global Failure response is received during this process (e.g., 600 Busy Everywhere), the device does not try to redirect the call to the next contact and drops the call. Version 6.8 Mediant 500 E-SBC...

  • Page 404: Pstn Fallback

    Mediant 500 E-SBC  The device redirects the call to the first contact listed in the Contact header. If the contact responds with a SIP response that is configured in the Reasons for Tel-to-IP Alternative Routing table (see ''Alternative Routing Based on SIP Responses'' on page 401), the device tries to redirect the call to the next contact, and so on.

  • Page 405: Alternative Routing For Ip-To-Tel Calls

    Routing Table so that the device uses the Inbound IP Routing table for alternative routing. In the Inbound IP Routing table, configure alternative routing rules with the same call matching characteristics, but with different Trunk Group destinations. Version 6.8 Mediant 500 E-SBC...

  • Page 406: Alternative Routing To An Ip Destination Upon A Busy Trunk

    Mediant 500 E-SBC Configure Q.931 cause codes that invoke alternative IP-to-Tel routing: Open the Reasons for IP-to-Tel Alternative Routing page (Configuration tab > VoIP menu > GW and IP to IP > Routing > Alternative Routing Reasons > Reasons for IP-to-Tel).
  • Page 407 (i.e., IP address, port and transport type). Note: • If you do not specify a port, the device uses UDP port 5060. • When configured with a user@host, the original destination number is replaced by the user part. Version 6.8 Mediant 500 E-SBC...

  • Page 408: Alternative Routing Upon Isdn Disconnect

    Mediant 500 E-SBC 24.6.3 Alternative Routing upon ISDN Disconnect You can configure when the device sends a call to an alternative route if it receives an ISDN Q.931 Disconnect message with a Progress Indicator (PI) IE from the Tel side for IP- to-Tel calls.

  • Page 409: Configuring Dtmf And Dialing

    Tel side by the device. When the number of collected digits reaches the maximum (or a digit map pattern is matched), the device uses these digits for the called destination number. Version 6.8 Mediant 500 E-SBC...
  • Page 410 Mediant 500 E-SBC  Inter-digit timeout expires (e.g., for open numbering schemes). This is defined using the TimeBetweenDigits parameter. This is the time that the device waits between each received digit. When this inter-digit timeout expires, the device uses the collected digits to dial the called destination number.

  • Page 411: External Dial Plan File

    Dial Plan. 25.1.2 External Dial Plan File The device can be loaded with a Dial Plan file with user-defined dialing plans. For more information, see ''Dial Plan File'' on page 556. Version 6.8 Mediant 500 E-SBC...
  • Page 412 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10437...

  • Page 413: Configuring Supplementary Services

    ''Configuration Parameters Reference'' on page 691.  To configure supplementary services parameters: Open the Supplementary Services page (Configuration tab > VoIP menu > GW and IP to IP > DTMF & Supplementary > Supplementary Services). Version 6.8 Mediant 500 E-SBC...

  • Page 414: Call Hold And Retrieve

    Mediant 500 E-SBC Configure the parameters as required. Click Submit, or click the Subscribe to MWI or Unsubscribe to MWI buttons to save your changes and to subscribe / unsubscribe to the MWI server. To save the changes to flash memory, see ''Saving Configuration'' on page 542.

  • Page 415: Consultation Transfer For Qsig Path Replacement

    The source number of the transferred call is taken from the original call, according to its initial direction: • Tel-to-IP call: source number of the original call. • IP-to-Tel call: destination number of the original call. Version 6.8 Mediant 500 E-SBC...

  • Page 416: Call Forward

    Mediant 500 E-SBC • If the UseReferredByForCallingNumber parameter is set to 1, the source number is taken from the SIP Referred-By header if included in the received SIP REFER message. This source number can also be used as the value for the 'Source Prefix' field in the IP-to-Tel Destination Phone Number Manipulation table.

  • Page 417: Message Waiting Indication

    The device sends another SIP NOTIFY to the softswitch, containing this MWI information. The SIP NOTIFY messages are sent to the IP Group defined by the NotificationIPGroupID parameter. Version 6.8 Mediant 500 E-SBC...

  • Page 418: Emergency E911 Phone Number Services

    Mediant 500 E-SBC When a change in the status occurs (e.g., a new voice message is waiting or the user has retrieved a message from the voice mail), the PBX initiates an ISDN Setup message with Facility IE containing an MWI Activate request, which includes the new number of voice messages waiting for the user.

  • Page 419: Enhanced 9-1-1 Support For Lync Server 2010

    E9-1-1 due to the difficulty in accurately locating the E9-1-1 caller. This section describes the E9-1-1 solution provided by Microsoft Lync Server 2010 (hereafter referred to as Lync Server 2010), and the deployed AudioCodes ELIN Gateway which provides the ISDN (or CAMA) connectivity to the PSTN-based E9-1-1 emergency providers.

  • Page 420: Microsoft Lync Server 2010 And E9-1-1

    Mediant 500 E-SBC The figure below illustrates the routing of an E9-1-1 call to the PSAP: Figure 26-1: Call Flow of E9-1-1 to PSTN-Based Emergency Services Provider The VoIP user dials 9-1-1. The call is eventually sent to the PSTN through a PSTN Gateway.
  • Page 421 IPv4 subnet ♦ Media Access Control (MAC) address • Depends on network connectivity: ♦ Wireless access point (WAP) Basic Service Set Identifier (BSSID) ♦ Link Layer Discovery Protocol-Media Endpoint Discovery (LLDP-MED) chassis ID and port ID Version 6.8 Mediant 500 E-SBC...
  • Page 422 Mediant 500 E-SBC For a Lync 2010 client that moves inside the corporate network such as a soft phone on a laptop that connects wirelessly to the corporate network, Lync Server 2010 can determine which subnet the phone belongs to or which WAP / SSID is currently serving the soft-client.
  • Page 423 (for example, less than 7000 square feet per ERL). Typically, you would have an ERL for each floor of the building. The ELIN is used as the phone number for 911 callers within this ERL. Version 6.8 Mediant 500 E-SBC...

  • Page 424: Audiocodes Elin Gateway For Lync Server 2010 E9-1-1 Calls To Pstn

    ELIN when dialing 9-1-1. 26.5.2.3 AudioCodes ELIN Gateway for Lync Server 2010 E9-1-1 Calls to PSTN The Microsoft Mediation Server sends the location information of the E9-1-1 caller in the XML-based PIDF-LO body contained in the SIP INVITE message.
  • Page 425 User's Manual 26. Configuring Supplementary Services The figure below illustrates an AudioCodes ELIN Gateway deployed in the Lync Server 2010 environment for handling E9-1-1 calls between the Enterprise and the PSTN. Figure 26-4: AudioCodes ELIN Gateway for E9-1-1 in Lync Server 2010 Environment 26.5.2.3.1 Detecting and Handling E9-1-1 Calls...
  • Page 426 ELIN is disregarded and no longer used (for PSAP callback). Therefore, table entries of only the most recently terminated E9-1-1 callers are considered in the ELIN table. The maximum entries in the ELIN table depend on the AudioCodes ELIN Gateway deployed in the Lync Server 2010 environment: •...
  • Page 427 However, as the Enterprise sends ELINs to the PSAP for E9-1-1 calls, a callback can only reach the original E9-1-1 caller using the ELIN Gateway to translate the ELIN number back into the E9-1-1 caller's extension number. Version 6.8 Mediant 500 E-SBC...
  • Page 428 Mediant 500 E-SBC In the ELIN table of the ELIN Gateway, the temporarily stored From header value of the SIP INVITE message originally received from the E9-1-1 caller is used for PSAP callback. When the PSAP makes a callback to the E9-1-1 caller, the ELIN Gateway translates the called number (i.e., ELIN) received from the PSAP to the corresponding E9-1-1 caller's...

  • Page 429: Configuring Audiocodes Elin Gateway

    26.5.2.4 Configuring AudioCodes ELIN Gateway This section describes E9-1-1 configuration of the AudioCodes ELIN Gateway deployed in the Lync Server 2010 environment. 26.5.2.4.1 Enabling the E9-1-1 Feature By default, the E9-1-1 feature in the ELIN Gateway for Lync Server 2010 is disabled.
  • Page 430 Mediant 500 E-SBC Note: This also configured using file parameter, EmergencySpecialReleaseCause.  To enable SIP response 503 upon failed E911: Open the Advanced Parameters page (Configuration tab > VoIP menu > SIP Definitions > Advanced Parameters). From the 'Emergency Special Release Cause' drop-down list, select Enable.
  • Page 431 4257275678 22:11:52 0 4258359333 4257275999 22:11:57 0 4258359444 4257275615 22:12:03 0 4258359555 4257275616 22:11:45 0 4258359777 ------------ Current Time: 22:12:40  Using Syslog, by invoking the following Web command shell: SIP / GateWay / E911Dump Version 6.8 Mediant 500 E-SBC...

  • Page 432: Multilevel Precedence And Preemption

    Mediant 500 E-SBC 26.6 Multilevel Precedence and Preemption The device supports Multilevel Precedence and Preemption (MLPP) service. MLPP is a call priority scheme, which does the following:  Assigns a precedence level (priority level) to specific phone calls or messages.
  • Page 433 Table 5.3.2.12-4 (Mapping of RPH r-priority Field to PRI Precedence Level Value): Table 26-6: Mapping of SIP Resource-Priority Header to PRI Precedence Level for MLPP MLPP Precedence Level PRI Precedence Level SIP Resource-Priority Header Field Routine Priority Immediate Flash Flash Override Version 6.8 Mediant 500 E-SBC...

  • Page 434: Mlpp Preemption Events In Sip Reason Header

    Mediant 500 E-SBC  If the network-domain field in the Resource-Priority header is any value other than "uc", then the device sets the Precedence Level field to "0 1 0 0" (i.e., "routine"). This can be modified using the EnableIp2TelInterworkingtable field of the ini file parameter, ResourcePriorityNetworkDomains.

  • Page 435: Precedence Ring Tone

    SIP ACK message to the softswitch. 26.6.2 Precedence Ring Tone You can configure the duration for which the device plays a preemption tone to the Tel and IP sides if a call is preempted, using the PreemptionToneDuration parameter. Version 6.8 Mediant 500 E-SBC...

  • Page 436: Detecting Collect Calls

    The device interworks these ISDN messages with SIP by converting the AOC messages into SIP INFO (during call) and BYE messages (end of call), using AudioCodes proprietary SIP AOC header, and vice versa. The device supports both currency (monetary units) and pulse (non-monetary units) AOC messages.
  • Page 437 Configuring Charge Codes), and then assign the Charge Code index to the relevant Tel-to-IP routing rule in the Outbound IP Routing table (see ''Configuring Outbound IP Routing'' on page 385). Note: This feature is applicable to Euro ISDN (PRI). Version 6.8 Mediant 500 E-SBC...

  • Page 438: Configuring Charge Codes

    Mediant 500 E-SBC 26.9 Configuring Charge Codes The Charge Codes table lets you configure metering tones for Advice of Charge (AOC) services for Euro ISDN trunks (see Advice of Charge Services for Euro ISDN on page 436). You can configure up to 25 different Charge Codes, where each table row represents a Charge Code.
  • Page 439 (00). This prevents undefined time frames in a day. Pulse Interval Defines the time interval between pulses (in tenths of a CLI: pulse-interval-<1-4> second). [ChargeCode_PulseInterval<1-4>] Pulses On Answer Defines the number of pulses sent on answer. CLI: pulses-on-answer-<1-4> [ChargeCode_PulsesOnAnswer<1- 4>] Version 6.8 Mediant 500 E-SBC...

  • Page 440: Configuring Voice Mail

    Mediant 500 E-SBC 26.10 Configuring Voice Mail The Voice Mail Settings page allows you to configure the voice mail parameters. For a description of these parameters, see ''Configuration Parameters Reference'' on page 691. Notes: • The Voice Mail Settings page is available only for CAS interfaces.

  • Page 441: Session Border Controller Application

    Part VI Session Border Controller Application...

  • Page 443: Sbc Overview

    Modifies SIP To, From, and Request-URI host names (must be configured using the Message Manipulations table). • Generates a new SIP Call-ID header value (different between legs). • Changes the SIP Contact header to the device's own address. Version 6.8 Mediant 500 E-SBC...

  • Page 444: Sip Network Definitions

    Mediant 500 E-SBC • Layer-3 topology hiding by modifying source IP address in the SIP IP header.  SIP normalization: The device supports SIP normalization, whereby the SBC application can overcome interoperability problems between SIP user agents. This is achieved by the following: •...
  • Page 445 ''SBC Manipulations'' on page 499. SIP message manipulations: You can configure SIP message manipulation rules that can add, remove, and/or modify SIP headers and parameters. For more information, see ''Configuring SIP Message Manipulation'' on page 288. Version 6.8 Mediant 500 E-SBC...
  • Page 446 Mediant 500 E-SBC The flowchart below illustrates the SBC process: Figure 27-1: Routing Process User's Manual Document #: LTRT-10437...

  • Page 447: User Registration

    By default, the Contact header in the outgoing REGISTER is populated with a unique contact generated by the device and associated with the specific registration. Alternatively, the original user can be retained in the Contact header and used in the outgoing REGISTER request (using the SBCKeepContactUserinRegister parameter). Version 6.8 Mediant 500 E-SBC...

  • Page 448: Sbc Users Registration Database

    Mediant 500 E-SBC 27.3.2 SBC Users Registration Database The device manages a dynamic Users Registration database that is updated according to registration requests that traverse it. Each database entry for a user represents a binding between an AOR (obtained from the SIP To header) and one or more contact (obtained from the SIP Contact headers).

  • Page 449: Registration Restriction Control

    The flowchart below depicts the process for blocking unregistered users. When the call is rejected, the device sends a SIP 500 (Server Internal Error) response to the remote end. Figure 27-2: Blocking Incoming Calls from Unregistered Users Version 6.8 Mediant 500 E-SBC...

  • Page 450: Sbc Media Handling

    Mediant 500 E-SBC 27.4 SBC Media Handling Media behavior includes anything related to the establishment, management and termination of media sessions within the SIP protocol. Media sessions are created using the SIP "offer"/"answer" mechanism. If successful, the result is a bi-directional media (RTP) flow (e.g.

  • Page 451: Media Anchoring Without Transcoding (Transparent)

    By default, media packets traverse the device to solve NAT problems, enforce media security policy, perform media transcoding between the two legs, and media monitoring. In certain deployments, specific calls do not require media anchoring, for example, when Version 6.8 Mediant 500 E-SBC...
  • Page 452 Mediant 500 E-SBC there is no need for NAT, security, or transcoding. This is typical for calls between users in the LAN:  Internal LAN calls: When the SBC routes a call between two UAs within the same LAN, the SBC can forward the SDP directly between caller and callee, and direct the media to flow between the UAs without traversing the SBC.

  • Page 453: Restricting Coders

    The Allowed Coders process is as follows: The device receives an incoming SIP message with SDP (offer) and checks the offered coders. The source (first) leg may have Allowed Coders (i.e. list of coders that can be used - enforced). Version 6.8 Mediant 500 E-SBC...

  • Page 454: Prioritizing Coder List In Sdp Offer

    Mediant 500 E-SBC The device checks for common coders between the SDP offered coders and the Allowed Coders Group list. For example, assume the following:  The SDP coder offer includes the following coders: G.729, G.711, and G.723.  The source (first) leg includes the following Allowed Coders: G.711 and G.729.

  • Page 455: Multiple Rtp Media Streams Per Call Session

    If the message is received without a SIP Authorization header, the device "challenges" the client by sending a SIP 401 or 407 response. The client then resends the request with an Authorization header (containing the user name and password). Version 6.8 Mediant 500 E-SBC...

  • Page 456: User Authentication Based On Radius

    Mediant 500 E-SBC The device validates the SIP message according to the AuthNonceDuration, AuthChallengeMethod and AuthQOP parameters. ♦ If validation fails, the device rejects the message and sends a 403 (Forbidden) response to the client. ♦ If validation succeeds, the device verifies client identification. It checks that...

  • Page 457: Interworking Sip Signaling

    The prefix ("T~&R_") remains in the user part for the classification, manipulation, and routing mechanisms. The classification, manipulation, and routing processes are done exactly like any other INVITE handling. The special prefix can be used for specific routing rules for 3xx resultant INVITEs. Version 6.8 Mediant 500 E-SBC...

  • Page 458: Local Handling Of Sip 3Xx

    Mediant 500 E-SBC The prefix is removed before the resultant INVITE is sent to the destination. Figure 27-5: SIP 3xx Response Handling The process of this feature is described using an example: The device receives the Redirect server's SIP 3xx response (e.g., Contact: <sip:User@IPPBX:5060;transport=tcp;param=a>;q=0.5).

  • Page 459: Interworking Sip Diversion And History-Info Headers

    This feature supports the following:  Attended, unattended, and semi-attended call transfers  Sending INVITE, REFER-notifications, BYE, PRACK and Session Timer on behalf of peer PBXs  Advanced routing rules for the new, initiated INVITE Version 6.8 Mediant 500 E-SBC...

  • Page 460: Interworking Sip Prack Messages

    Mediant 500 E-SBC  Forwarding early media after REFER while attempting to avoid transcoding (by sending session update)  Interoperate with environments were different SIP UAs lack basic SIP functionality such as re-INVITE, UPDATE, PRACK, Delayed Offer, re-INVITE without SDP ...

  • Page 461: Interworking Sip Early Media

    IP Profile parameters, 'SBC Remote Early Media RTP', 'SBC Remote Supports RFC 3960', and 'SBC Remote Can Play Ringback'. See the flowcharts below for the device's handling of such scenarios: Version 6.8 Mediant 500 E-SBC...
  • Page 462 Mediant 500 E-SBC Figure 27-6: SBC Early Media RTP 18x without SDP Figure 27-7: Early Media RTP - SIP 18x with SDP User's Manual Document #: LTRT-10437...

  • Page 463: Interworking Sip Re-Invite Messages

    Interworking generation of held tone where the device generates the tone to the held party instead of the call hold initiator. This is configured by the IP Profile parameter, 'SBC Reliable Held Tone Source'. For configuring IP Profiles, see ''Configuring IP Profiles'' on page 304. Version 6.8 Mediant 500 E-SBC...

  • Page 464: Call Survivability

    Mediant 500 E-SBC 27.8 Call Survivability This section describes various call survivability features supported by the SBC device. 27.8.1 Auto-Provisioning of Subscriber-Specific Information for BroadWorks Server for Survivability This feature enables SBC user registration for interoperability with BroadSoft BroadWorks server to provide call survivability in case of connectivity failure with the BroadWorks server, for example, due to a WAN failure.

  • Page 465: Broadsoft's Shared Phone Line Call Appearance For Sbc Survivability

    AOR registered in the device's registration database. In the IP-to-IP Routing table (see ''Configuring SBC IP-to-IP Routing Rules'' on page 487), add a rule for routing calls between the above configured IP Groups. Version 6.8 Mediant 500 E-SBC...

  • Page 466: Call Survivability For Call Centers

    Mediant 500 E-SBC In the IP to IP Inbound Manipulation table (see ''Configuring IP-to-IP Inbound Manipulations'' on page 502), add a manipulation rule for the secondary extensions (e.g., 601 and 602) so that they also register to the device's database under the primary extension contact (e.g., 600):...
  • Page 467 The 'Destination Type' field is set to Hunt Group, which is specifically used for call center survivability. ♦ The 'Destination IP Group ID' field is set to the IP Group of the call center agents. Version 6.8 Mediant 500 E-SBC...

  • Page 468: Survivability Mode Display On Aastra Ip Phones

    Mediant 500 E-SBC The figure below displays a routing rule example, assuming IP Group "1" represents the TDM Gateway and IP Group "3" represents the call center agents: Figure 27-12: Routing Rule Example for Call Center Survivability 27.8.4 Survivability Mode Display on Aastra IP Phones...

  • Page 469: Call Forking

    SDP answer that was forwarded to the INVITE- initiating UA is not relevant, and media synchronization is needed between the two UAs. Media synchronization is done by sending a re-INVITE request immediately after the call is Version 6.8 Mediant 500 E-SBC...

  • Page 470: Call Forking-Based Ip-To-Ip Routing Rules

    Mediant 500 E-SBC established. The re-INVITE is sent without an offer to the INVITE-initiating UA. This causes the UA to send an offer which is forwarded to the UA that confirmed the call. The media synchronization process is enabled by the EnableSBCMediaSync parameter.

  • Page 471: Sbc Configuration

    B. User B can then press a pre-configured key sequence to answer the call. The NOTIFY message contains the XML body with call identifiers (call-id and tags). However, as the application server is located in the external network WAN and the SIP Version 6.8 Mediant 500 E-SBC...
  • Page 472 Mediant 500 E-SBC clients behind the device, the call dialog information sent by the application server reflects only the dialog between the device and itself; not that of the involved SIP clients. This is due to, for example, the device's topology hiding (e.g., IP address) of its LAN elements.

  • Page 473: Configuring Admission Control

    SRD and its associated IP Groups are as follows:  SRD reserved call capacity: 40  IP Group ID 1 reserved call capacity: 10  IP Group ID 2 reserved call capacity: 20 Version 6.8 Mediant 500 E-SBC...
  • Page 474 Mediant 500 E-SBC In this setup, the SRD offers a shared pool for unreserved call capacity of 10 [i.e., 40 – (10 + 20)]. If IP Group ID 1 needs to handle 15 calls, it is guaranteed 10 calls and the remaining 5 is provided from the SRD's shared pool.
  • Page 475 CLI: limit-per-user user belonging to the specified IP Group or SRD. You can also [SBCAdmissionControl_LimitPerU use the following special values: ser]  [0] 0 = Block all these dialogs.  [-1] -1 = (Default) Unlimited. Version 6.8 Mediant 500 E-SBC...
  • Page 476 Mediant 500 E-SBC Parameter Description Rate Defines the rate (in seconds) at which tokens are added to the CLI: rate token bucket per second (i.e., token rate). [SBCAdmissionControl_Rate] The default is 0 (i.e., unlimited rate). Notes:  You must first configure the Maximum Burst parameter (see below) before configuring the Rate parameter.

  • Page 477: Configuring Allowed Audio Coder Groups

    Figure 28-4: Allowed Audio Coders Group Page Configure an Allowed Audio Coders Group according to the parameters described in the table below. Click Submit, and then reset the device with a save ("burn") to flash memory. Version 6.8 Mediant 500 E-SBC...
  • Page 478 Mediant 500 E-SBC Table 28-2: Allowed Audio Coders Group Table Parameter Descriptions Parameter Description Allowed Coders Group ID Defines an index number for the new table record. [AllowedCodersGroupX] Coder Name Defines the audio coder. This can be a pre-defined coder or a CLI: name user-defined coder.

  • Page 479: Configuring Allowed Video Coder Groups

    The valid value for user-defined coders [AllowedVideoCodersGroupX_Name] is a string of up to 25 characters (case-insensitive). For example, "WOW.789" (but without quotes). Note: Each coder type can be configured only once per Allowed Video Coders Group. Version 6.8 Mediant 500 E-SBC...

  • Page 480: Routing Sbc

    Mediant 500 E-SBC 28.5 Routing SBC This section describes the configuration of the routing entities for the SBC application. These include the following:  Classification rules - see ''Configuring Classification Rules'' on page  Message Condition rules - see ''Configuring Message Condition Rules'' on page ...
  • Page 481 SIP response code per SIP interface. This is configured by the 'Classification Failure Response Type' parameter in the SIP Interface table (see ''Configuring SIP Interfaces'' on page 258). Version 6.8 Mediant 500 E-SBC...
  • Page 482 Mediant 500 E-SBC The flowchart below illustrates the classification process: Figure 28-5: Classification Process (Identifying IP Group or Rejecting Call) Note: The device saves incoming SIP REGISTER messages in its registration database. If the REGISTER message is received from a User-type IP Group, the device sends the message to the configured destination.
  • Page 483 CLI: src-ip-address of the incoming SIP dialog. [Classification_SrcAddress] The IP address can be configured using the following wildcards:  "x" wildcard: represents single digits. For example, 10.8.8.xx represents all the addresses between 10.8.8.10 to 10.8.8.99. Version 6.8 Mediant 500 E-SBC...
  • Page 484 Mediant 500 E-SBC Parameter Description  asterisk (*) wildcard: represents any number between 0 and 255. For example, 10.8.8.* represents all addresses between 10.8.8.0 and 10.8.8.255. If this parameter is not configured or is configured as an asterisk (*), any source IP address is accepted.

  • Page 485: Classification Based On Uri Of Selected Header Example

    Source Username Destination Index Destination Host Source IP Group ID Prefix Username Prefix 1111 2000 10.10.10.10 In the IP Group table, add the following IP Groups: Index Source URI Input Destination URI Input P-Called-Party-ID Route Version 6.8 Mediant 500 E-SBC...

  • Page 486: Configuring Message Condition Rules

    Mediant 500 E-SBC In this example, a match exists only for Classification Rule #1. This is because the source (1111) and destination (2000) username prefixes match those in the INVITE's P-Called- Party-ID header (i..e., "<sip:1111@10.33.38.1>") Route header (i.e., "<sip:2000@10.10.10.10.10>"), respectively. These SIP headers were determined in IP Group ID 2.
  • Page 487 Defines the Condition rule of the SIP message. CLI: condition The valid value is a string. [ConditionTable_Condition] Note: User and host parts must be enclosed in single quotes. Description Defines a brief description of the Condition rule. CLI: description [ConditionTable_Description] Version 6.8 Mediant 500 E-SBC...

  • Page 488: Configuring Sbc Ip-To-Ip Routing

    Mediant 500 E-SBC 28.5.3 Configuring SBC IP-to-IP Routing The IP-to-IP Routing table lets you configure up to 500 SBC IP-to-IP routing rules. An IP- to-IP routing rule routes received SIP dialog messages (e.g., INVITE) to an IP destination. Configuration of IP-to-IP routing rules includes two areas: ...
  • Page 489 User's Manual 28. SBC Configuration Version 6.8 Mediant 500 E-SBC...
  • Page 490 Mediant 500 E-SBC The IP-to-IP Routing table also provides the following features:  Alternative routing or load balancing: In addition to the alternative routing/load balancing provided by the Proxy Set associated with the destination IP Group, the table allows the configuration of alternative routes whereby if a route fails, the next adjacent (below) rule in the table that is configured as 'Alt Route Ignore/Consider Inputs' are used.
  • Page 491 Figure 28-9: IP-to-IP Routing Table - Add Record Dialog Box Configure an IP-to-IP routing rule according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Version 6.8 Mediant 500 E-SBC...
  • Page 492 Mediant 500 E-SBC Table 28-6: IP-to-IP Routing Table Parameter Descriptions Parameter Description Index Defines an index number for the new table record. [IP2IPRouting_Index] Route Name Defines an arbitrary name to easily identify the IP-to-IP CLI: route-name routing rule. [IP2IPRouting_RouteName] The valid value is a string of up to 20 characters. By default, no value is defined.
  • Page 493 The device routes the call to the destination according to the routing rule's configured action, only after it has performed the Call Setup rules. For configuring Call Setup rules, see ''Configuring Call Setup Rules'' on page 232. Operation Routing Rule - Action Version 6.8 Mediant 500 E-SBC...
  • Page 494 Mediant 500 E-SBC Parameter Description Destination Type Determines the destination type to which the outgoing SIP [IP2IPRouting_DestType] dialog is sent. CLI: dst-type  [0] IP Group = (Default) The SIP dialog is sent to the IP Group’s Proxy Set (SERVER-type IP Group) or registered contact from the database (if USER-type IP Group).
  • Page 495 Dest Address [1] or ENUM [3].  When using domain names, enter a DNS server IP address or alternatively, define these names in the Internal DNS table (see ''Configuring the Internal SRV Version 6.8 Mediant 500 E-SBC...
  • Page 496 Mediant 500 E-SBC Parameter Description Table'' on page 131).  To terminate SIP OPTIONS messages at the device (i.e., to handle them locally), set this parameter to "internal". Destination Port Defines the destination port to where the call is sent.

  • Page 497: Configuring Sip Response Codes For Alternative Routing Reasons

    IP-to-IP Routing table. Alternative routing rules are configured with the 'Alternative Route Options' parameter set to Alt Route Ignore Inputs or Alt Route Consider Inputs (see ''Configuring SBC IP-to-IP Routing Rules'' on page 487). Version 6.8 Mediant 500 E-SBC...
  • Page 498 Mediant 500 E-SBC Typically, the device performs alternative routing when there is no response at all to an INVITE message. This is done after a user-defined number of INVITE re-transmissions, configured by the SIPMaxRtx parameter. In such a scenario, the device issues itself the SIP response code 408 (Request Timeout).

  • Page 499: Sbc Manipulations

    IP Group. Manipulated destination user and host are performed on the following SIP headers: Request-URI, To, and Remote-Party-ID (if exists). Manipulated source user and host are performed on the following SIP headers: From, P-Asserted (if exists), P- Preferred (if exists), and Remote-Party-ID (if exists). Version 6.8 Mediant 500 E-SBC...
  • Page 500 Mediant 500 E-SBC Figure 28-11: SIP URI Manipulation in IP-to-IP Routing You can also restrict source user identity in outgoing SIP dialogs in the Outbound Manipulation table (using the column PrivacyRestrictionMode). The device identifies an incoming user as restricted if one of the following exists: ...
  • Page 501 Inbound destination SIP URI user name from "1000" to 9721000": INVITE sip:1000@10.2.2.3;user=phone;x=y;z=a SIP/2.0 To: <sip:1000@10.2.2.3;user=phone> INVITE sip:9721000@ITSP;user=phone;x=y;z=a SIP/2.0 To: <sip:9721000@ITSP;user=phone>  Destination IP Group name (SIP URI host name) from "10.2.2.3" to "ITSP": INVITE sip:1000@10.2.2.3;user=phone;x=y;z=a SIP/2.0 To: <sip:1000@10.2.2.3;user=phone> INVITE sip:9721000@ITSP;user=phone;x=y;z=a SIP/2.0 To: <sip:9721000@ITSP;user=phone> Version 6.8 Mediant 500 E-SBC...

  • Page 502: Configuring Ip-To-Ip Inbound Manipulations

    Mediant 500 E-SBC 28.6.1 Configuring IP-to-IP Inbound Manipulations The IP to IP Inbound Manipulation table lets you configure up to 100 IP-to-IP Inbound Manipulation rules. An IP-to-IP Inbound Manipulation rule defines a manipulation sequence for the source or destination SIP URI user part of inbound SIP dialog requests. You can apply these manipulations to different SIP dialog message types (e.g., INVITE or...
  • Page 503 Defines the source SIP URI host name - full name (usually in CLI: src-host the From header). [IPInboundManipulation_SrcHost] The default is the asterisk (*) symbol (i.e., any host name). Destination Username Prefix Defines the prefix of the destination SIP URI user name, Version 6.8 Mediant 500 E-SBC...
  • Page 504 Mediant 500 E-SBC Parameter Description CLI: dst-user-name-prefix typically located in the Request-URI and To headers. [IPInboundManipulation_DestUser The default is the asterisk (*) symbol (i.e., any destination namePrefix] username prefix). Note: The prefix can be a single digit or a range of digits. For available notations, see ''Dialing Plan Notation for Routing and Manipulation'' on page 689.

  • Page 505: Configuring Ip-To-Ip Outbound Manipulations

    The following procedure describes how to configure IP-to-IP Outbound Manipulation rules in the Web interface. You can also configure these rules using the table ini file parameter, IPOutboundManipulation or CLI command, configure voip > sbc manipulations ip- outbound-manipulation. Version 6.8 Mediant 500 E-SBC...
  • Page 506 Mediant 500 E-SBC  To configure IP-to-IP outbound manipulation rules: Open the IP to IP Outbound Manipulation page (Configuration tab > VoIP menu > SBC > Manipulations SBC > IP to IP Outbound). Click Add; the following dialog box appears:...
  • Page 507 [2] REGISTER = Only SIP REGISTER messages.  [3] SUBSCRIBE = Only SIP SUBSCRIBE messages.  [4] INVITE and REGISTER = All SIP messages except SUBSCRIBE.  [5] INVITE and SUBSCRIBE = All SIP messages Version 6.8 Mediant 500 E-SBC...
  • Page 508 Mediant 500 E-SBC Parameter Description except REGISTER. ReRoute IP Group ID Defines the IP Group that initiated (sent) the SIP redirect CLI: re-route-ip-group-id response (e.g., 3xx) or REFER message. This parameter [IPOutboundManipulation_ReRouteIP is typically used for re-routing requests (e.g., INVITEs)
  • Page 509 The device identifies an incoming user as restricted if one of the following exists:  From header user is anonymous.  P-Asserted-Identity and Privacy headers contain the value "id". Note: All restriction logic is performed after the user number has been manipulated. Version 6.8 Mediant 500 E-SBC...
  • Page 510 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10437...

  • Page 511: Cloud Resilience Package

    Part VII Cloud Resilience Package...

  • Page 513: Crp Overview

    Distributed PBX or unified communications deployments The CRP application is based on the functionality of the SBC application, providing branch offices with call routing and survivability support similar to AudioCodes' Stand-Alone Survivability (SAS) application. CRP is implemented in a network topology where the...
  • Page 514 Mediant 500 E-SBC Survivability Quality of Experience/Service Security registration process)  Survivability indication to IP phone  Call hold and retrieve  Call transfer (if the IP phone initiates REFER)  Basic Shared Line Appearance (excluding correct busy line indications) ...

  • Page 515: Crp Configuration

    Open the Applications Enabling page (Configuration tab > VoIP menu > Applications Enabling > Applications Enabling). From the 'CRP Application' drop-down list, select Enable. Click Submit, and then reset the device with a burn-to-flash for your settings to take effect. Version 6.8 Mediant 500 E-SBC...

  • Page 516: Configuring Call Survivability Mode

    Mediant 500 E-SBC 30.2 Configuring Call Survivability Mode The CRP can be configured to operate in one of the following call survivability modes:  Normal (Default): The CRP interworks between the branch users and the IP PBX located at headquarters. The CRP forwards all requests (such as for registration) from the branch users to the IP PBX, and routes the calls based on the IP-to-IP routing rules.

  • Page 517: Pre-Configured Ip Groups

    The IP Groups can be edited, except for the fields listed above, which are read-only. • For accessing the IP Group table and for a description of its parameters, see ''Configuring IP Groups'' on page 263. Version 6.8 Mediant 500 E-SBC...

  • Page 518: Pre-Configured Ip-To-Ip Routing Rules

    Mediant 500 E-SBC 30.4 Pre-Configured IP-to-IP Routing Rules For the CRP application, the IP-to-IP Routing table is pre-configured with IP-to-IP routing rules. These rules depend on the configured Call Survivability mode, as described in ''Configuring Call Survivability Mode'' on page 516.

  • Page 519: Emergency Mode

    For the routing rule of Index 2, the destination is the source IP Group (i.e., from where the REGISTER message was received). Index 7 appears only if the CRPGatewayFallback parameter is enabled (see ''Configuring PSTN Fallback'' on page 520). Version 6.8 Mediant 500 E-SBC...

  • Page 520: Configuring Pstn Fallback

    Mediant 500 E-SBC 30.5 Configuring PSTN Fallback You can enable the CRP to route emergency calls (or PSTN-intended calls) such as "911" from the Proxy server (IP Group 2) to the PSTN (IP Group 3). In addition, for calls from the...

  • Page 521: High-Availability System

    Part VIII High-Availability System...

  • Page 523: Ha Overview

    The device's High Availability (HA) feature provides 1+1 system redundancy using two Mediant 500 E-SBC devices. If failure occurs in the active device, a switchover occurs to the redundant device which takes over the call handling process. Thus the continuity of call services is ensured.

  • Page 524: Device Switchover Upon Failure

    Mediant 500 E-SBC In the active device, all logical interfaces (i.e., Media, Control, OAMP, and Maintenance) are active. In the redundant device, only the Maintenance interface is active, which is used for connectivity to the active device. Therefore, management is done only through the active device.

  • Page 525: Ha Status On The Home Page

    In the 'HA Device Name' field, enter a name for the active device. Click Submit. Note: Once the devices are running in HA mode, you can change the name of the redundant device, through the active device only, in the 'Redundant HA Device Name' field. Version 6.8 Mediant 500 E-SBC...
  • Page 526 Mediant 500 E-SBC The Home page also displays the HA operational status of the device to which you are currently logged in. This is displayed in the 'High Availability' field under the General Information pane:  "Not Operational": HA is not configured or the installed Software License Key does not include the HA feature ...

  • Page 527: Ha Configuration

    Figure 32-1: Rx/Tx Mode for Geographical HA  If the Maintenance ports of both devices are connected directly to each other without intermediation of switches, configure the mode to 2RX/1TX: Figure 32-2: Rx/Tx Mode for Direct Connection Version 6.8 Mediant 500 E-SBC...

  • Page 528: Configuring The Ha Devices

    Mediant 500 E-SBC  If the two devices are connected through two (or more) isolated LAN switches (i.e., packets from one switch cannot traverse the second switch), configure the mode to 2RX/2TX: Figure 32-3: Redundancy Mode for Two Isolated Switches Notes: •...

  • Page 529: Step 1: Configure The First Device

    Ethernet Device "vlan 2" (which is associated with Ethernet Port Group "GROUP_2") in the 'Underlying Device' field, while the other interface is assigned to "vlan 1" (associated with "GROUP_1"): Figure 32-4: Configured MAINTENANCE Interface in Interface Table Version 6.8 Mediant 500 E-SBC...
  • Page 530 Mediant 500 E-SBC If the connection is through a switch, the packets of both interfaces should generally be untagged. In such a scenario, set the Native VLAN ID of each Ethernet Port Group so that it is the same as the VLAN ID set for each interface assigned to that Ethernet Port Group.

  • Page 531: Step 2: Configure The Second Device

    (configured in Step 1: Configure the First Device on page 529). Burn the configuration to flash without a reset. Power down the device. Continue to ''Step 3: Initialize HA on the Devices'' on page for completing the HA configuration. Version 6.8 Mediant 500 E-SBC...

  • Page 532: Step 3: Initialize Ha On The Devices

    Mediant 500 E-SBC 32.1.2.3 Step 3: Initialize HA on the Devices Once you have configured both devices for HA as described in the previous sections, follow the procedure below to complete and initialize HA so that the devices become operational in HA. This last stage applies to both devices.

  • Page 533: Configuration While Ha Is Operational

    After it synchronizes with the active device, it initiates a switchover and becomes the new active device (the former active device resets and becomes the new redundant device). Version 6.8 Mediant 500 E-SBC...

  • Page 534: Configuring Firewall Allowed Rules

    Mediant 500 E-SBC 32.3 Configuring Firewall Allowed Rules If you add firewall rules in the Firewall Settings page (see ''Configuring Firewall Settings'' on page 141) that block specified traffic, you also need to add rules that ensure traffic related to the HA feature is allowed. These allowed HA rules include the following: ...

  • Page 535: Ha Maintenance

    The previously active device burns and resets with the new software version. The previously active device switches over to become the active device. For more information on upgrading the software, see ''Software Upgrade Wizard'' on page 574. Version 6.8 Mediant 500 E-SBC...
  • Page 536 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10437...

  • Page 537: Maintenance

    Part IX Maintenance...

  • Page 539: Basic Maintenance

    After you reset the device, the Web GUI is displayed in Basic view (see ''Displaying Navigation Tree in Basic and Full View'' on page 41).  To reset the device: Open the Maintenance Actions page (see ''Basic Maintenance'' on page 539). Version 6.8 Mediant 500 E-SBC...

  • Page 540: Remotely Resetting Device Using Sip Notify

    Mediant 500 E-SBC Under the 'Reset Configuration' group, from the 'Burn To FLASH' drop-down list, select one of the following options: • Yes: The device's current configuration is saved (burned) to the flash memory prior to reset (default). • No: Resets the device without saving the current configuration to flash (discards all unsaved modifications).

  • Page 541: Locking And Unlocking The Device

    Under the Misc Parameters group, set the 'SIP Remote Rest' parameter to Enable. Click Submit. Note: This SIP Event header value is proprietary to AudioCodes. 34.3 Locking and Unlocking the Device The Lock and Unlock option allows you to lock the device so that it doesn't accept any new calls and maintains only the current calls.

  • Page 542: Saving Configuration

    Mediant 500 E-SBC Click OK to confirm device lock; if you set 'Graceful Option' to Yes, a lock icon is delayed and a window appears displaying the number of remaining calls and time. If you set 'Graceful Option' to No, the lock process begins immediately. The 'Gateway Operational State' field displays "LOCKED".

  • Page 543: High Availability Maintenance

    Under the 'Switch Over' group, click Switch Over; a confirmation box appears requesting you to confirm. Click OK.  To reset the Redundant device: Under the 'Redundant Options' group, click Reset; a confirmation box appears requesting you to confirm. Click OK. Version 6.8 Mediant 500 E-SBC...
  • Page 544 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10437...

  • Page 545: Disconnecting Active Calls

    Session ID. This is done in the CLI using the following commands (from basic command mode):  Disconnects all active calls: # clear voip calls  Disconnects active calls belonging to a specified Session ID: # clear voip calls <Session ID> Version 6.8 Mediant 500 E-SBC...
  • Page 546 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10437...

  • Page 547: Resetting Channels

    If a voice call is currently in progress on the B-channel, it is disconnected when the B-channel is restarted. • B-channel restart can only be done if the D-channel of the trunk to which it belongs is synchronized (Layer 2). • B-channel restart does not affect the B-channel's configuration. Version 6.8 Mediant 500 E-SBC...
  • Page 548 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10437...

  • Page 549: Locking And Unlocking Trunk Groups

    Appears when the device is locking the Trunk Group and indicates the number of buys channels and the time remaining until the graceful period ends, after which the device locks the channels regardless of whether the call has ended or not. Version 6.8 Mediant 500 E-SBC...
  • Page 550 Mediant 500 E-SBC • "Out Of Service": All fully configured trunks in the Trunk Group are out of service, for example, when the Trunk Group is locked or in Busy Out state (see the EnableBusyOut parameter). Note: • If the device is reset, a locked Trunk Group remains locked. If the device is reset while graceful lock is in progress, the Trunk Group is forced to lock immediately after the device finishes its reset.

  • Page 551: Software Upgrade

    The Auxiliary files listed in the ini file are then automatically loaded through TFTP during device startup. If the ini file does not contain a specific auxiliary file type, the device uses the last auxiliary file of that type that was stored on its non-volatile memory. Version 6.8 Mediant 500 E-SBC...
  • Page 552 Mediant 500 E-SBC Notes: • You can schedule automatic loading of updated auxiliary files using HTTP/HTTPS. For more information on automatic updates, see Automatic Update Mechanism. • When loading an ini file using this Web page, parameters that are excluded from the loaded ini file retain their current settings (incremental).

  • Page 553: Call Progress Tones File

    AudioCodes DConvert utility. For a description on converting a CPT ini file into a binary dat file, refer to the DConvert Utility User's Guide.
  • Page 554 Mediant 500 E-SBC ♦ [18] Comfort Tone ♦ [23] Hold Tone ♦ [46] Beep Tone • Tone Modulation Type: Amplitude Modulated (1) or regular (0) • Tone Form: The tone's format can be one of the following: ♦ Continuous (1) ♦...

  • Page 555: Prerecorded Tones File

    Up to 40 tones (totaling approximately 10 minutes) can be stored in a single PRT file on the device's flash memory. The prerecorded tones are prepared offline using third- party recording utilities and combined into a single file, using AudioCodes DConvert utility (refer to the document, DConvert Utility User's Guide for more information).

  • Page 556: Cas Files

    Plans, as required. Save the file with the ini file extension name (e.g., mydialplanfile.ini). Convert the ini file to a dat binary file, using AudioCodes DConvert utility. For more information, refer to DConvert Utility User's Guide. Load the converted file to the device, as described in ''Loading Auxiliary Files'' on page 551.

  • Page 557: Dialing Plans For Digit Collection

    • To use the Dial Plan file, you must also use a special CAS .dat file that supports this feature. For more information, contact your AudioCodes sales representative. • For E1 CAS MFC-R2 variants, which don't support terminating digit for the called party number, usually I-15, the Dial Plan file and the DigitMapping parameter are ignored.
  • Page 558 Plans, as required. Save the file with the ini file extension name (e.g., mydialplans.ini). Convert the ini file to a dat binary file, using AudioCodes DConvert utility. For more information, refer to DConvert Utility User's Guide. Install the converted file on the device, as described in ''Loading Auxiliary Files'' on page 551.

  • Page 559: Dial Plan Prefix Tags For Routing

    The example Dial Plan file below defines the prefix tags "LOCL"and "LONG" to represent different called number prefixes for local and long distance calls: [ PLAN1 ] 42520[3-5],0,LOCL 425207,0,LOCL 42529,0,LOCL 425200,0,LONG 425100,0,LONG ..Note: Called and calling prefix tags can be used in the same routing rule. Version 6.8 Mediant 500 E-SBC...
  • Page 560 Mediant 500 E-SBC The following procedure describes how to configure IP-to-Tel routing using prefix tags.  To configure IP-to-Tel routing using prefix tags: Configure a Dial Plan file with prefix tags, and then load the file to the device. On the Routing General Parameters page (Configuration tab > VoIP menu > SIP Definitions >...
  • Page 561 [ PLAN1 ] 42520[3-5],0,LOCL 425207,0,LOCL 42529,0,LOCL 425200,0,INTL 425100,0,INTL ..Note: Called and calling prefix tags can be used in the same routing rule. The following procedure describes how to configure IP-to-IP routing using prefix tags. Version 6.8 Mediant 500 E-SBC...

  • Page 562: Obtaining Ip Destination From Dial Plan File

    Mediant 500 E-SBC  To configure IP-to-IP routing using prefix tags: Configure a Dial Plan file with prefix tags, and then load the file to the device. Add the prefix tags to the numbers of specific incoming calls using Inbound IP-to-IP Manipulation rules: Open the IP to IP Inbound Manipulation table (Configuration tab >...

  • Page 563: Modifying Isdn-To-Ip Calling Party Number

    DConvert Utility User's Guide. You can load this *.dat file to the device using the Web interface (see ''Loading Auxiliary Files'' on page 551), AcBootP utility, or using the Auto-update mechanism from an external HTTP server. Version 6.8 Mediant 500 E-SBC...

  • Page 564: User Information File

    Mediant 500 E-SBC Notes: • Tel-to-IP routing is performed on the original source number if the parameter 'Tel to IP Routing Mode' is set to 'Route calls before manipulation'. • Tel-to-IP routing is performed on the modified source number as defined in the Dial Plan file, if the parameter 'Tel To IP Routing Mode' is set to 'Route calls after manipulation'.
  • Page 565 If a User Info file is loaded to the device (as described in ''Configuring GW User Info Table in Loadable Text File'' on page 567), all previously configured entries are removed from the table in the Web interface and replaced with the entries from the loaded User Info file. Version 6.8 Mediant 500 E-SBC...
  • Page 566 Mediant 500 E-SBC  To configure the GW User Info table in the Web interface: Open the GW User Info Table page (Configuration tab > VoIP menu > SIP Definitions > User Information > GW User Info Table). Click Add: the following dialog box appears: Figure 39-2: GW User Info Table in Web Interface Configure the GW User Info table parameters according to the table below.
  • Page 567 To add mapping rules to the User Info file, use the following syntax: [ GW ] FORMAT PBXExtensionNum,GlobalPhoneNum,DisplayName,UserName,Password Where:  [ GW ] indicates that this part of the file is the GW User Info table Version 6.8 Mediant 500 E-SBC...

  • Page 568: User Information File For Sbc User Database

    Mediant 500 E-SBC  PBXExtensionNum is the PBX extension number (up to 10 characters)  GlobalPhoneNum is the "global" phone number (up to 20 characters) for the IP side  DisplayName is the Caller ID (string of up to 30 characters) of the PBX extension ...
  • Page 569 The valid value is a string of up to 20 characters. IP Group ID Defines the IP Group ID to which the user belongs and is used as [SBCUserInfoTable_IPGroupID] the Request-URI source host part for the AOR in the database. Version 6.8 Mediant 500 E-SBC...
  • Page 570 Mediant 500 E-SBC Parameter Description Status (Read-only field) Displays the status of the user - "Registered" or [SBCUserInfoTable_Status] "Not Registered". 39.1.5.3.2 Configuring SBC User Info Table in CLI The SBC User Info table can be configured in the CLI using the following commands: ...
  • Page 571 URI source host part for the AOR in the database Note: To modify the SBC User Info table using a User Info file, you need to load to the device a new User Info file containing your modifications. Version 6.8 Mediant 500 E-SBC...

  • Page 572: Software License Key

    Before you can install a new Software License Key, you need to obtain a Software License Key file for your device with the required features from your AudioCodes representative. The Software License Key is an encrypted key in string format that is associated with the device's serial number ("S/N") and supplied in a text-based file.

  • Page 573: Installing The Software License Key

     CLI - see Installing Software License Key using CLI  AudioCodes EMS - refer to the EMS User’s Manual or EMS Product Description Note: When you install a new Software License Key, it is loaded to the device's non- volatile flash memory and overwrites the previously installed Software License Key.

  • Page 574: Installing Software License Key Using Cli

    Open the Software License Key file and check that the "S/N" line appears. If it does not appear, contact AudioCodes. Verify that you have loaded the correct file. Open the file and ensure that the first line displays "[LicenseKeys]".

  • Page 575: Software Upgrade Wizard

    If you upgraded your firmware (.cmp file) and the "SW version mismatch" message appears in the Syslog or Web interface, your Software License Key does not support the new .cmp file version. If this occurs, contact AudioCodes support for assistance.
  • Page 576 Mediant 500 E-SBC The following procedure describes how to load files using the Web interface's Software Upgrade Wizard. Alternatively, you can load files using the CLI:  cmp file: copy firmware from <URL>  ini or auxiliary file: copy <ini file or auxiliary file> from <URL>...
  • Page 577 See the description of these methods in the beginning of this section. Note: If you select the Hitless Upgrade option, the wizard can only be used to upload a .cmp file; Auxiliary and ini files cannot be uploaded. Version 6.8 Mediant 500 E-SBC...
  • Page 578 Mediant 500 E-SBC If you want to load additional files, skip this step and continue with the next step. If you only want to load a .cmp file, click Reset ; the device burns the .cmp file to its flash memory and then resets. The device uses the existing configuration (ini) and auxiliary files.
  • Page 579 Click End Process to close the wizard; the Web Login dialog box appears. Enter your login username and password, and then click Login; a message box appears informing you of the new .cmp file version. Click OK; the Web interface becomes active, reflecting the upgraded device. Version 6.8 Mediant 500 E-SBC...

  • Page 580: Backing Up And Loading Configuration File

    Mediant 500 E-SBC 39.4 Backing Up and Loading Configuration File You can save a copy/backup of the device's current configuration settings as an ini file to a folder on your computer, using the Configuration File page. The saved file includes only parameters that were modified and parameters with other than default values.
  • Page 581 Click the Load INI File button, and then at the prompt, click OK; the device uploads the file and then resets. Once complete, the Web Login screen appears, requesting you to enter your user name and password. Version 6.8 Mediant 500 E-SBC...
  • Page 582 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10437...

  • Page 583: Automatic Update Mechanism

    To activate the DHCP process, reset the device. The following shows an example of a configuration file for a Linux DHCP server (dhcpd.conf). The devices are allocated temporary IP addresses in the range 10.31.4.53 to Version 6.8 Mediant 500 E-SBC...

  • Page 584: Provisioning From Http Server Using Dhcp Option 67

    Mediant 500 E-SBC 10.31.4.75. TFTP is assumed to be on the same computer as the DHCP server (alternatively, the "next-server" directive may be used). ddns-update-style ad-hoc; default-lease-time 60; max-lease-time 60; class "gateways" { match if(substring(hardware, 1, 3) = 00:90:8f); subnet 10.31.0.0 netmask 255.255.0.0 { pool { allow members of "audiocodes";...

  • Page 585: Provisioning From Tftp Server Using Dhcp Option 66

    This method is suitable when the network in which the device is deployed contains a provisioning TFTP server for all network equipment, without being able to distinguish between AudioCodes and non-AudioCodes devices. Upon startup, the device searches for Option 66 in the DHCP response from the DHCP server.

  • Page 586: Ftp- Based Provisioning

    URL is "ftp" (instead of "http"). 40.1.6 Provisioning using AudioCodes EMS AudioCodes EMS server functions as a core-network provisioning server. The device's SNMP Manager should be configured with the IP address of the EMS server, using one of the methods detailed in the previous sections.

  • Page 587: Http/S-Based Provisioning Using The Automatic Update Feature

    The Automatic Update feature is done per file and configured by specifying the file name and URL address of the provisioning server where the file is located. For a description of the parameters used to configure URLs per file, see Automatic Update Parameters. Version 6.8 Mediant 500 E-SBC...

  • Page 588: Triggers For Automatic Update

    Upon receipt of an SNMP request from the provisioning server. • Upon receipt of a special SIP NOTIFY message from the provisioning server. The NOTIFY message includes an Event header with the AudioCodes proprietary value, "check-sync;reboot=false", as shown in the example below: NOTIFY sip:<user>@<dsthost> SIP/2.0 To: sip:<user>@<dsthost>...

  • Page 589: Access Authentication With Http Server

    <CONF> - configuration version, as configured in the ini file parameter, INIFileVersion or CLI command, configuration-version The device automatically populates these tag variables with actual values in the sent header. By default, the device sends the following in the User-Agent header: Version 6.8 Mediant 500 E-SBC...
  • Page 590 Mediant 500 E-SBC User-Agent: Mozilla/4.0 (compatible; AudioCodes; <NAME>;<VER>;<MAC>;<CONF>) For example, if you set AupdHttpUserAgent = MyWorld-<NAME>;<VER>(<MAC>), the device sends the following User-Agent header: User-Agent: MyWorld-Mediant;6.8.200.001(00908F1DD0D3) Note: If you configure the AupdHttpUserAgent parameter with the <CONF> variable tag, you must reset the device with a burn-to-flash for your settings to take effect.

  • Page 591: File Download Sequence

    If you use the ResetNow parameter in an ini file for periodic automatic provisioning with non-HTTP (e.g., TFTP) and without CRC, the device resets after every file download. Therefore, use this parameter with caution and only if necessary for your deployment requirements. Version 6.8 Mediant 500 E-SBC...

  • Page 592: Cyclic Redundancy Check On Downloaded Configuration Files

    Mediant 500 E-SBC Notes: • For ini file downloads, by default, parameters not included in the file are set to defaults. To retain the current settings of these parameters, set the SetDefaultOnINIFileProcess parameter to 0. • If you have configured one-time software file (.cmp) download (configured by the ini file parameter CmpFileURL or CLI command configure system >...

  • Page 593: Automatic Update Configuration Examples

    Automatic Update is done every 24 hours (1440 minutes): ♦ ini File: AutoUpdateFrequency = 1440 ♦ CLI: # configure system (config-system)# automatic update (automatic-update)# update-frequency 1440 Automatic Update of software file (.cmp): ♦ ini File: AutoCmpFileUrl = 'https://www.company.com/sw.cmp' ♦ CLI: Version 6.8 Mediant 500 E-SBC...

  • Page 594: Automatic Update From Remote Servers

    Mediant 500 E-SBC # configure system (config-system)# automatic update automatic-update)# auto-firmware 'http://www.company.com/sw.cmp' Automatic Update of Call Progress Tone file: ♦ ini File: CptFileURL = 'https://www.company.com/call_progress.dat' ♦ CLI: # configure system (config-system)# automatic update (automatic-update)# call-progress-tones 'http://www.company.com/call_progress.dat' Automatic Update of ini configuration file: ♦...

  • Page 595: Automatic Update For Mass Deployment

    # Software (.cmp) file update: AutoCmpFileUrl = 'https://www.company.com/sw.cmp' Configuration per device based on MAC address: IniFileURL = 'http://www.company.com/config_<MAC>.ini' Copy the master_configuration.ini file as well as the CPT and .cmp files to the HTTP- based provisioning server. Version 6.8 Mediant 500 E-SBC...
  • Page 596 Mediant 500 E-SBC Configure each device with the following: URL of the master_configuration.ini file for Automatic Update: ♦ ini File: IniFileURL = 'http://www.company.com/master_configuration.ini' ♦ CLI: # configure system (config-system)# automatic update (automatic-update)# voice-configuration 'http://www.company.com/master_configuration.ini' Configure the device with the IP address of the DNS server for resolving the domain name (e.g., http://www.company.com) that is used in the URL for the...

  • Page 597: Restoring Factory Defaults

    # enable At the prompt, type the password again, and then press Enter: # Password: Admin At the prompt, type the following to reset the device to default settings, and then press Enter: # write factory Version 6.8 Mediant 500 E-SBC...

  • Page 598: Restoring Defaults Using Hardware Reset Button

    Mediant 500 E-SBC 41.2 Restoring Defaults using Hardware Reset Button The device's hardware reset pinhole button can be used to reset the device to default settings.  To restore default settings using the hardware reset pinhole button:  With a paper clip or any other similar pointed object, press and hold down the reset pinhole button, located on the front panel for at least 12 seconds (but no more than 25 seconds).

  • Page 599: Saving Current Configuration To A File And Sending It To Remote Destination

    # write-and-backup to <URL path with file name> For example: # write-and-backup to tftp://192.168.0.3/config-device1.txt  Creating a Configuration file and saving it on a USB stick plugged into the device: # write-and-backup to usb:///<file name> For example: # write-and-backup to usb:///config-device1.txt Version 6.8 Mediant 500 E-SBC...
  • Page 600 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10437...

  • Page 601: Usb Storage Capabilities

    # copy voice-configuration from usb:///<ini configuration file name>  To save the current configuration to the USB: # copy voice-configuration to usb:///<ini configuration file name> Note: Only a single USB storage (formatted to FAT/FAT32) operation is supported at any given time. Version 6.8 Mediant 500 E-SBC...
  • Page 602 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10437...

  • Page 603: Status, Performance Monitoring And Reporting

    Part X Status, Performance Monitoring and Reporting...

  • Page 605: System Status

    To delete a loaded file:  Click the Delete button corresponding to the file that you want to delete. Deleting a file takes effect only after device reset (see ''Resetting the Device'' on page 539). Version 6.8 Mediant 500 E-SBC...

  • Page 606: Viewing Ethernet Port Information

    Mediant 500 E-SBC 44.2 Viewing Ethernet Port Information The Ethernet Port Information page displays read-only information about the Ethernet Port Group connections.  To view Ethernet port information:  Open the Ethernet Port Information page: • Navigation menu tree: Status & Diagnostics tab > System Status menu >...

  • Page 607: Carrier-Grade Alarms

    Source: unit from which the alarm was raised  Description: brief explanation of the alarm  Date: date and time that the alarm was generated You can view the next 20 alarms (if exist), by clicking the Go to page button. Version 6.8 Mediant 500 E-SBC...

  • Page 608: Viewing Alarm History

    Mediant 500 E-SBC 45.2 Viewing Alarm History The Alarms History page displays a list of alarms that have been raised and traps that have been cleared.  To view the list of history alarms:  Open the Alarms History page (Status & Diagnostics tab > System Status menu >...

  • Page 609: Performance Monitoring

    As you increase the resolution, more data is displayed on the graph. The minimum resolution is about 30 seconds; the maximum resolution is about an hour. To pause the graph, click the Pause button; click Play to resume. Version 6.8 Mediant 500 E-SBC...

  • Page 610: Viewing Trunk Utilization

    Mediant 500 E-SBC 46.2 Viewing Trunk Utilization The Trunk Utilization page provides an X-Y graph that displays the number of active channels per trunk over time. The x-axis indicates the time; the y-axis indicates the number of active trunk channels.

  • Page 611: Viewing Quality Of Experience

    Dialog Failed Attempts: displays the failed call attempts. This includes the number of calls and subscribes which were successfully and abnormally terminated.  Dialog Termination Ratio: displays call termination by reason (e.g., due to no answer). Version 6.8 Mediant 500 E-SBC...
  • Page 612 Mediant 500 E-SBC  To view Quality of Experience: Open the Quality Of Experience page (Status & Diagnostics tab > Performance Monitoring menu > Quality Of Experience). Figure 46-3: Quality Of Experience Graph From the 'SRD/IpGroup' drop-down list, select whether you want to view QoE for an SRD or IP Group.

  • Page 613: Viewing Average Call Duration

    Figure 46-4: Average Call Duration Graph From the 'SRD/IpGroup' drop-down list, select whether you want to view information for an SRD or IP Group. From the 'Index' drop-down list, select the SRD or IP Group index. Version 6.8 Mediant 500 E-SBC...
  • Page 614 Mediant 500 E-SBC Use the Zoom In button to increase the displayed time resolution or the Zoom Out button to decrease it. Instead of using these zoom buttons, you can use the slide ruler. As you increase the resolution, more data is displayed on the graph. The minimum resolution is about 30 seconds;...

  • Page 615: Voip Status

    Color Label Gray Disabled Green Active - OK Yellow RAI Alarm LOS / LOF Alarm Blue AIS Alarm Light Orange D-Channel Alarm Dark Orange NFAS Alarm Purple Lower Layer Down (DS3 physical layer is disabled) Version 6.8 Mediant 500 E-SBC...
  • Page 616 Mediant 500 E-SBC The status of the channels is depicted by color-coded icons, as described in the table below: Table 47-2: Description of Color-Coded Icons for Channel Status Icon Color Label Description Light blue Inactive Channel is configured, but currently has no calls...

  • Page 617: Viewing Nfas Groups And D-Channel Status

    To view the status of the D-channels and NFAS groups:  Open the NFAS Group & D-Channel Status page (Status & Diagnostics tab > VoIP Status menu > NFAS Group & D-Channel Status). Figure 47-3: NFAS Group & D-Channel Status Page Version 6.8 Mediant 500 E-SBC...

  • Page 618: Viewing Active Ip Interfaces

    Mediant 500 E-SBC 47.3 Viewing Active IP Interfaces The IP Interface Status page displays the device's active IP interfaces that are listed in the Interface table (see ''Configuring IP Network Interfaces'' on page 115).  To view active IP network interfaces: ...

  • Page 619: Viewing Ethernet Device Status

     To view the status of static IP routing:  Open the IP Routing Status Table page (Status & Diagnostics tab > VoIP Status menu >Static Route Status). Figure 47-4: IP Routing Status Table Page Version 6.8 Mediant 500 E-SBC...

  • Page 620: Viewing Performance Statistics

    Mediant 500 E-SBC 47.6 Viewing Performance Statistics The Basic Statistics page provides read-only, device performance statistics. This page is refreshed every 60 seconds. The duration that the currently displayed statistics has been collected is displayed above the statistics table. ...
  • Page 621 00:01:20 denotes 1 minute and 20 seconds. Termination Reason Displays the reason for the call being released (ended). For example, "NORMAL_CALL_CLEAR" indicates a normal off-hook (hang up) of the call party. Session ID Displays the SIP session ID of the call. Version 6.8 Mediant 500 E-SBC...

  • Page 622: Viewing Call Counters

    Mediant 500 E-SBC 47.8 Viewing Call Counters The IP to Tel Calls Count page and Tel to IP Calls Count page provide you with statistical information on incoming (IP-to-Tel) and outgoing (Tel-to-IP) calls. The statistical information is updated according to the release reason that is received after a call is terminated (during the same time as the end-of-call Call Detail Record or CDR message is sent).
  • Page 623 15 minute period. Attempted Fax Calls Indicates the number of attempted fax calls. Counter Successful Fax Calls Indicates the number of successful fax calls. Counter Version 6.8 Mediant 500 E-SBC...

  • Page 624: Viewing Registered Sas/Sbc Users

    Mediant 500 E-SBC 47.9 Viewing Registered SAS/SBC Users You can view SAS and SBC users listed in the device's Users Registration database. The list shows each Address of Record (AOR) and its corresponding contact. The contact's registration status is also shown: ...

  • Page 625: Viewing Registration 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. Version 6.8 Mediant 500 E-SBC...
  • Page 626 Mediant 500 E-SBC  To view call routing status:  Open the Call Routing Status page (Status & Diagnostics tab > VoIP Status menu > Call Routing Status). Figure 47-9: Call Routing Status Page Table 47-5: Call Routing Status Parameters...

  • Page 627: Viewing Ip Connectivity

    OK = Remote side responds to periodic connectivity queries.  Lost = Remote side didn't respond for a short period.  Fail = Remote side doesn't respond.  Init = Connectivity queries not started (e.g., IP address not resolved). Version 6.8 Mediant 500 E-SBC...
  • Page 628 Mediant 500 E-SBC Column Name Description  Disable = The connectivity option is disabled, i.e., parameter 'Alt Routing Tel to IP Mode' (AltRoutingTel2IPMode ini) is set to 'None' or 'QoS'. Quality Status Determines the QoS (according to packet loss and delay) of the IP address.

  • Page 629: Reporting Information To External Party

    Start timestamp in the RTCP XR indicates the start of the media segment; the End timestamp indicates the time of the last sent periodic RTCP XR (typically, up to 5 seconds before reported segment ends). Version 6.8 Mediant 500 E-SBC...
  • Page 630 Mediant 500 E-SBC Table 48-1: RTCP XR Published VoIP Metrics Group Metric Name General Start Timestamp Stop Timestamp Call-ID Local Address (IP, Port & SSRC) Remote Address (IP, Port & SSRC) Session Description Payload Type Payload Description Sample Rate Frame Duration...
  • Page 631 LocalID: <sip:1000@172.17.116.201> RemoteID: <sip:2000@172.17.116.202;user=phone> OrigID: <sip:1000@172.17.116.201> LocalAddr: IP=172.17.116.201 Port=6000 SSRC=0x54c62a13 RemoteAddr: IP=172.17.116.202 Port=6000 SSRC=0x243220dd LocalGroup: RemoteGroup: LocalMAC: 00:90:8f:57:d9:71 LocalMetrics: Timestamps: START=2015-12-16T20:09:45Z STOP=2015-12-16T20:09:52Z SessionDesc: PT=8 PD=PCMA SR=8000 FD=20 PLC=3 SSUP=Off JitterBuffer: JBA=3 JBR=0 JBN=7 JBM=10 JBX=300 Version 6.8 Mediant 500 E-SBC...
  • Page 632 Mediant 500 E-SBC PacketLoss: NLR=0.00 JDR=0.00 BurstGapLoss: BLD=0.00 BD=0 GLD=0.00 GD=6325 GMIN=16 Delay: RTD=0 ESD=11 Signal: SL=-34 NL=-67 RERL=17 QualityEst: RLQ=93 MOSLQ=4.1 MOSCQ=4.10 RemoteMetrics: Timestamps: START=2015-12-16T20:09:45Z STOP=2015-12-16T20:09:52Z JitterBuffer: JBA=3 JBR=0 JBN=0 JBM=0 JBX=300 PacketLoss: NLR=0.00 JDR=0.00 BurstGapLoss: BLD=0.00 BD=0 GLD=0.00 GD=0 GMIN=16...

  • Page 633: Generating Call Detail Records

    For CDR in RADIUS format, see ''Configuring RADIUS Accounting'' on page 645. Note: You can view the latest CDRs, which are stored on the device 's memory, in the CDR History table. For more information, see 'Viewing CDR History' on page 620. Version 6.8 Mediant 500 E-SBC...

  • Page 634: Configuring Cdr Reporting

    Mediant 500 E-SBC 48.2.1 Configuring CDR Reporting The following procedure describes how to configure CDR reporting.  To configure CDR reporting: Enable the Syslog feature for sending log messages generated by the device to a collecting log message server. For more information, see ''Enabling Syslog'' on page 662.
  • Page 635 String of up to 41 characters Durat Call duration (in seconds) String of up to 5 characters TrmSd Termination side: String  "LCL" – local  "RMT" - remote TrmReason Termination reason String of up to 40 Version 6.8 Mediant 500 E-SBC...
  • Page 636 Mediant 500 E-SBC CDR Field Name Description Format characters TrmReasonCategory Termination reason category: String of up to 17 characters Calls with duration 0 (i.e., not connected):  NO_ANSWER:  "GWAPP_NORMAL_CALL_CLEA R"  "GWAPP_NO_USER_RESPONDI NG"  "GWAPP_NO_ANSWER_FROM_ USER_ALERTED"  BUSY: ...
  • Page 637 Below shows an example of an SBC signaling CDR sent at the end of a call (call was terminated normally): [S=40] |SBCReportType |EPTyp |SIPCallId |SessionId |Orig |SourceIp |SourcePort |DestIp |DestPort |TransportType |SrcURI |SrcURIBeforeMap |DstURI |DstURIBeforeMap |Durat |TrmSd |TrmReason |TrmReasonCategory |SetupTime |ConnectTime |ReleaseTime |RedirectReason |RedirectURINum |RedirectURINumBeforeMap |TxSigIPDiffServ|IPGroup (description) |SrdId (name) Version 6.8 Mediant 500 E-SBC...

  • Page 638: Cdr Fields For Sbc Media

    Mediant 500 E-SBC |SIPInterfaceId |ProxySetId |IpProfileId (name) |MediaRealmId (name) |DirectMedia |SIPTrmReason |SIPTermDesc |Caller |Callee [S=41] |CALL_END |SBC |20767593291410201017029@10.33.45.80 |1871197419|LCL |10.33.45.80 |5060 |10.33.45.72 |5060 |UDP |9001@10.8.8.10 |9001@10.8.8.10 |6001@10.33.45.80 |6001@10.33.45.80 |15 |LCL |GWAPP_NORMAL_CALL_CLEAR |NORMAL_CALL_CLEAR |17:00:29.954 UTC Thu Oct 14 2014 |17:00:49.052 UTC Thu Oct 14 2014 |17:01:04.953...

  • Page 639: Cdr Fields For Gateway/Ip-To-Ip Application

    Note: This field is applicable only to the Gateway application. ConId SIP conference ID Note: This field is applicable only to the Gateway application. Trunk Group ID Note: This field is applicable only to the Gateway application. Version 6.8 Mediant 500 E-SBC...
  • Page 640 Mediant 500 E-SBC Field Name Description EPTyp Endpoint type:  ISDN    IPMEDIA  NETANN  STREAMING  TRANSPARENT  MSCML  VXML  IP2IP Orig Call originator:  LCL (Tel side)  RMT (IP side) SourceIp Source IP address...
  • Page 641 Data is stored per call and sent in the syslog as follows:  currency-type: amount multiplier for currency charge (euro or usd)  recorded-units: for unit charge (1-999999) Mult 0,001-1000 (in steps of 10) (See explanation above.) Version 6.8 Mediant 500 E-SBC...
  • Page 642 Mediant 500 E-SBC Field Name Description TrmReasonCategory Termination reason category:  Calls with duration 0 (i.e., not connected):  NO_ANSWER - GWAPP_NORMAL_CALL_CLEAR, GWAPP_NO_USER_RESPONDING, GWAPP_NO_ANSWER_FROM_USER_ALERTED  BUSY - GWAPP_USER_BUSY  NO_RESOURCES - GWAPP_RESOUUCE_UNAVAILABLE_UNSPECIFIED, RELEASE_BECAUSE_NO_CONFERENCE_RESOURCES_LEFT RESOURCE_BECAUSE_NO_TRANSCODING_RESOURCES_L EFT, RELEASE_BECAUSE_GW_LOCKED  NO_MATCH - RELEASE_BECAUSE_UNMATCHED_CAPABILITIES ...

  • Page 643: Release Reasons In Cdr

    "RELEASE_BECAUSE_NOANSWER"  "RELEASE_BECAUSE_UNKNOWN_REASON"  "RELEASE_BECAUSE_REMOTE_CANCEL_CALL"  "RELEASE_BECAUSE_UNMATCHED_CAPABILITIES"  "RELEASE_BECAUSE_UNMATCHED_CREDENTIALS"  "RELEASE_BECAUSE_UNABLE_TO_HANDLE_REMOTE_REQUEST"  "RELEASE_BECAUSE_NO_CONFERENCE_RESOURCES_LEFT"  "RELEASE_BECAUSE_CONFERENCE_FULL"  "RELEASE_BECAUSE_VOICE_PROMPT_PLAY_ENDED"  "RELEASE_BECAUSE_VOICE_PROMPT_NOT_FOUND"  "RELEASE_BECAUSE_TRUNK_DISCONNECTED"  "RELEASE_BECAUSE_RSRC_PROBLEM"  "RELEASE_BECAUSE_MANUAL_DISC"  "RELEASE_BECAUSE_SILENCE_DISC"  "RELEASE_BECAUSE_RTP_CONN_BROKEN"  "RELEASE_BECAUSE_DISCONNECT_CODE"  "RELEASE_BECAUSE_GW_LOCKED"  "RELEASE_BECAUSE_NORTEL_XFER_SUCCESS" Version 6.8 Mediant 500 E-SBC...
  • Page 644 Mediant 500 E-SBC  "RELEASE_BECAUSE_FAIL"  "RELEASE_BECAUSE_FORWARD"  "RELEASE_BECAUSE_ANONYMOUS_SOURCE"  "RELEASE_BECAUSE_IP_PROFILE_CALL_LIMIT"  "GWAPP_UNASSIGNED_NUMBER"  "GWAPP_NO_ROUTE_TO_TRANSIT_NET"  "GWAPP_NO_ROUTE_TO_DESTINATION"  "GWAPP_CHANNEL_UNACCEPTABLE"  "GWAPP_CALL_AWARDED_AND "  "GWAPP_PREEMPTION"  "PREEMPTION_CIRCUIT_RESERVED_FOR_REUSE"  "GWAPP_NORMAL_CALL_CLEAR"  "GWAPP_USER_BUSY"  "GWAPP_NO_USER_RESPONDING"  "GWAPP_NO_ANSWER_FROM_USER_ALERTED"  "MFCR2_ACCEPT_CALL"  "GWAPP_CALL_REJECTED"  "GWAPP_NUMBER_CHANGED"...

  • Page 645: Configuring Radius Accounting

    Accounting server. The device can send the accounting messages to the RADIUS server upon call release, call connection and release, or call setup and release. For a list of the CDR attributes, see the table following the procedure below. Version 6.8 Mediant 500 E-SBC...
  • Page 646 Mediant 500 E-SBC  To configure RADIUS accounting: Open the RADIUS Parameters page (Configuration tab > VoIP menu > SIP Definitions > RADIUS Parameters Settings). Figure 48-3: RADIUS Accounting Parameters Page Set the 'Enable RADIUS Access Control' parameter to Enable.
  • Page 647 Start Stop call- Terminator of the String Yes, No Stop terminator call:  "yes": Call terminated by the Tel side (Gateway) or outgoing leg (SBC)  "no": Call terminated by the IP side (Gateway) Version 6.8 Mediant 500 E-SBC...
  • Page 648 Mediant 500 E-SBC Vendor Specific Attribute Attribute Value Attribute Purpose Example Number Name Format (VSA) or incoming leg (SBC) terminator Terminator of the String terminator=originate Stop call:  "answer": Call originated from the IP side (Gateway) or incoming leg (SBC) "originate": Call...
  • Page 649 (4923 23) h323-remote-address = 212.179.22.214 (4923 1) h323-ivr-out = h323-incoming-conf-id:02102944 600a1899 3fd61009 0e2f3cc5 (4923 30) h323-disconnect-cause = 22 (0x16) (4923 27) h323-call-type = VOIP (4923 26) h323-call-origin = Originate (4923 24) h323-conf-id = 02102944 600a1899 3fd61009 0e2f3cc5 Version 6.8 Mediant 500 E-SBC...

  • Page 650: Event Notification Using X-Detect Header

    Mediant 500 E-SBC 48.4 Event Notification using X-Detect Header The device can notify a remote party of the occurrence (or detection) of certain events in the media stream. The device detects events and notifies their occurrence, using the SIP X-Detect message header and only when establishing a SIP dialog.
  • Page 651 Subtype = xxx (according to the defined subtypes of each type) Below is an example of SIP messages using the X-Detect header: INVITE sip:101@10.33.2.53;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.33.2.53;branch=z9hG4bKac5906 Max-Forwards: 70 From: "anonymous" <sip:anonymous@anonymous.invalid>;tag=1c25298 To: <sip:101@10.33.2.53;user=phone> Call-ID: 11923@10.33.2.53 Version 6.8 Mediant 500 E-SBC...
  • Page 652 Mediant 500 E-SBC CSeq: 1 INVITE Contact: <sip:100@10.33.2.53> X- Detect: Request=CPT,FAX SIP/2.0 200 OK Via: SIP/2.0/UDP 10.33.2.53;branch=z9hG4bKac5906 From: "anonymous" <sip:anonymous@anonymous.invalid>;tag=1c25298 To: <sip:101@10.33.2.53;user=phone>;tag=1c19282 Call-ID: 11923@10.33.2.53 CSeq: 1 INVITE Contact: <sip:101@10.33.2.53> X- Detect: Response=CPT,FAX INFO sip:101@10.33.2.53;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.33.2.53;branch=z9hG4bKac5906 Max-Forwards: 70 From: "anonymous"...

  • Page 653: Querying Device Channel Resources Using Sip Options

    In the example above, "telchs" specifies the number of available channels and the number of occupied channels (4 channels are occupied and 12 channels are available). Note: This feature is applicable only to the Gateway / IP-to-IP application. Version 6.8 Mediant 500 E-SBC...
  • Page 654 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10437...

  • Page 655: Diagnostics

    Part XI Diagnostics...

  • Page 657: Syslog And Debug Recordings

    Syslog message, messages 238 through 300 were not received. In other words, 63 Syslog messages were lost (the sequential numbers are indicated below in bold font): 18:38:14. 52 : 10.33.45.72 : NOTICE: [S=235][SID:1034099026] (lgr_psbrdex)(619) recv Version 6.8 Mediant 500 E-SBC...

  • Page 658: Event Representation In Syslog Messages

    Mediant 500 E-SBC Message Item Description <-- DIGIT(0) Ch:0 OnTime:0 InterTime:100 Direction:0 System:1 [File: Line:-1] 18:38:14. 83 : 10.33.45.72 : NOTICE: [S=236][SID:1034099026] (lgr_flow)(620) #0:DIGIT_EV [File: Line:-1] 18:38:14. 83 : 10.33.45.72 : NOTICE: [S=237][SID:1034099026] (lgr_flow)(621) #0:DIGIT_EV [File: Line:-1] 18:38:14.958 : 10.33.45.72 : NOTICE:...
  • Page 659 No Available Release Descriptor RTP Reorder Unknown RTP Payload Type RTP SSRC Error Unrecognized Fax Relay Command Invalid Accumulated Packets Counter Invalid Channel ID Invalid Header Length Invalid Codec Type Unknown Aggregation Payload Type Invalid Routing Flag Received Version 6.8 Mediant 500 E-SBC...

  • Page 660: Identifying Audiocodes Syslog Messages Using Facility Levels

    Mediant 500 E-SBC 49.1.2 Identifying AudioCodes Syslog Messages using Facility Levels The device’s Syslog messages can easily be identified and distinguished from Syslog messages from other equipment, by setting its Facility level. The Facility levels of the device's Syslog messages are numerically coded with decimal values. Facility level may use any of the "local use"...

  • Page 661: Snmp Alarms In Syslog Messages

    Notice Indeterminate Notice Cleared Notice  Cleared Alarms: CLEAR-ALARM: <Alarm Name>; Textual Description: <Textual Description>; Severity <Alarm Severity>; Source <Alarm Source>; Unique ID: <Alarm Unique ID >; If exists Additional Info1:/ Additional Info2:/ Additional Info3: Version 6.8 Mediant 500 E-SBC...

  • Page 662: Enabling Syslog

    Mediant 500 E-SBC 49.2 Enabling Syslog The following procedure describes how to enable and configure Syslog. Notes: • For configuring CDR reporting, see ''Configuring CDR Reporting'' on page 633. • For viewing Syslog messages in the Web interface, see ''Viewing Syslog Messages'' on page 667.

  • Page 663: Configuring Web Operations To Report To Syslog

    Debug recording is collected only on the device's OAMP interface. • You can also save debug recordings to an external USB hard drive that is connected to the device's USB port. For more information, see USB Storage Capabilities on page 601. Version 6.8 Mediant 500 E-SBC...

  • Page 664: Filtering Syslog Messages And Debug Recordings

    Mediant 500 E-SBC  To configure and activate debug recording: Open the Logging Settings page (Configuration tab > System menu > Logging > Logging Settings). Figure 49-3: Logging Settings Page Configure the debug capturing server using the 'Debug Recording Destination IP' and 'Debug Recording Destination Port' parameters.
  • Page 665 INVITE: INVITE sip:2222@10.33.45.201;user=phone SIP/2.0.  [13] IP Trace = Filters according to a specified IP network trace wireshark-like expression. For a detailed description on configuring IP traces, see ''Filtering IP Network Traces'' on page 666. Version 6.8 Mediant 500 E-SBC...

  • Page 666: Filtering Ip Network Traces

    Mediant 500 E-SBC Parameter Description Value Defines the value of the selected filtering type in the 'Filter Type' CLI: value parameter. [LoggingFilters_Value] The value can be the following:  A single value  A range, using a hyphen "-" between the two values, e.g., "1-3"...

  • Page 667: Viewing Syslog Messages

    • You can select the Syslog messages in this page, and 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. Version 6.8...
  • Page 668 Mediant 500 E-SBC  To activate the Web interface's Message Log: Enable Syslog (see ''Enabling Syslog'' on page 662). Open the Message Log page (Status & Diagnostics tab > System Status menu > Message Log); the Message Log page is displayed and the log is activated.

  • Page 669: Collecting Debug Recording Messages

    User's Manual 49. Syslog and Debug Recordings 49.7 Collecting Debug Recording Messages To collect debug recording packets, use the open source program Wireshark. AudioCodes proprietary plug-in files for Wireshark are required. Notes: • The default debug recording port is 925. You can change the port in Wireshark (Edit menu >...

  • Page 670: Debug Capturing On Physical Voip Interfaces

    Mediant 500 E-SBC 49.8 Debug Capturing on Physical VoIP Interfaces You can capture traffic on the device's physical (Ethernet LAN) VoIP interfaces (Layer-2 VLAN tagged packets). The captured traffic can be saved in a PCAP-format file (suitable for Wireshark) to a TFTP (default) or an FTP server. The generated PCAP file is in the Extensible Record Format (ERF).

  • Page 671: Self-Testing

    Startup Test (automatic): This hardware test has minor impact in real-time. While this test is executed, the regular operation of the device is disabled. If an error is detected, an error message is sent to the Syslog. Version 6.8 Mediant 500 E-SBC...
  • Page 672 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10437...

  • Page 673: Creating Core Dump And Debug Files Upon Device Crash

    The core dump can either be included in or excluded from the debug file, or alternatively, sent separately to a TFTP server. The files can then be sent to AudioCodes support team for troubleshooting. ...
  • Page 674 Mediant 500 E-SBC The following procedure describes how to retrieve the debug file from the device in the Web interface.  To save the debug file from the device:  In the Debug Utilities page, click the Save Debug File button.

  • Page 675: Testing Sip Signaling Calls

    By default, you can configure up to five test calls. However, this number can be increased by installing the relevant Software License Key. For more information, contact your AudioCodes sales representative. The following procedure describes how to configure test calls in the Web interface. You can also configure this using the table ini file parameter, Test_Call or CLI command, configure system >...
  • Page 676 Mediant 500 E-SBC  To configure a test call: Open the Test Call Table page (Configuration tab > System menu > Test Call > Test Call Table). Click Add; the following dialog box appears: Figure 52-1: General Tab of Test Call Table Configure a test call according to the parameters described in the table below.
  • Page 677 'Destination Address' or 'IP [Test_Call_AutoRegister] Group ID' parameter settings (see above).  [0] Disable (default)  [1] Enable Username Defines the authentication username. CLI: user-name By default, no username is defined. [Test_Call_UserName] Version 6.8 Mediant 500 E-SBC...
  • Page 678 Mediant 500 E-SBC Parameter Description Password Defines the authentication password. CLI: password By default, no password is defined. [Test_Call_Password] Test Settings Tab Call Party Defines whether the test endpoint is the initiator or receiving side CLI: call-party of the test call.

  • Page 679: Starting And Stopping Test Calls

    "Done": test call has been successfully completed (or was prematurely stopped by clicking the Drop Call command) A more detailed description of this field is displayed below the table when you click the Show/Hide button (see ''Viewing Test Call Statistics'' on page 680). Version 6.8 Mediant 500 E-SBC...

  • Page 680: Viewing Test Call Statistics

    Mediant 500 E-SBC 52.3 Viewing Test Call Statistics In addition to viewing a brief status description of the test call in the 'Test Status' field (as described in ''Starting, Stopping and Restarting Test Calls'' on page 679), you can also view a more detailed status description which includes test call statistics.

  • Page 681: Configuring Dtmf Tones For Test Calls

    Open the Test Call Settings page (Configuration tab > System menu > Test Call > Test Call Settings). Figure 52-3: DTMF in Test Call Settings Page In the 'Test Call DTMF String' field, enter the DTMF string (up to 15 digits). Click Submit. Version 6.8 Mediant 500 E-SBC...

  • Page 682: Configuring Basic Test Call

    Mediant 500 E-SBC 52.5 Configuring Basic Test Call The Basic Test Call feature tests incoming Gateway calls from a remote SIP endpoint to a simulated test endpoint on the device. The only required configuration is to assign a prefix number (test call ID) to the simulated endpoint. All incoming calls with this called (destination) prefix number is identified as a test call and sent to the simulated endpoint.

  • Page 683: Configuring Sbc Test Call With External Proxy

    The device receives the call from the proxy server. As the 'Test Call ID' parameter is set to "101", the device identifies the incoming call as a test call and sends it directly to the simulated test endpoint "101". Version 6.8 Mediant 500 E-SBC...

  • Page 684: Test Call Configuration Examples

    Mediant 500 E-SBC  To configure SBC call testing: Configure the test call parameters (for a full description, see ''SIP Test Call Parameters'' on page 716): Open the Test Call Settings page (Configuration tab > System menu > Test Call > Test Call Settings).
  • Page 685 The test call is done between two AudioCodes devices - Device A and Device B - with simulated test endpoints. This eliminates the need for phone users, who would otherwise need to answer and end calls many times for batch testing.
  • Page 686 Mediant 500 E-SBC  Registration Test Call Scenario: This example describes the configuration for testing the registration and authentication (i.e., username and pas,sword) process of a simulated test endpoint on the device with an external proxy/registrar server. This is useful, for example, for verifying that endpoints located in the LAN can register with an external proxy and subsequently, communicate with one another.

  • Page 687: Appendix

    Part XII Appendix...

  • Page 689: Dialing Plan Notation For Routing And Manipulation

    03(100): for any number that starts with 03 and ends with 100.  [100-199](100,101,105): for a number that starts with 100 to 199 and ends with 100, 101 or 105.  03(abc): for any number that starts with 03 and ends with abc. Version 6.8 Mediant 500 E-SBC...
  • Page 690 Mediant 500 E-SBC Notation Description  03(5xx): for any number that starts with 03 and ends with 5xx.  03(400,401,405): for any number that starts with 03 and ends with 400 or 401 or 405. Notes:  The value n must be less than the value m.

  • Page 691: Configuration Parameters Reference

    [WebUserPassChangeInterval] passwords. When this duration expires, the password of the Web user must be changed. The valid value is 0 to 100000, where 0 means that the password is always valid. The default is 1140. Version 6.8 Mediant 500 E-SBC...
  • Page 692 Mediant 500 E-SBC Parameter Description Note: This parameter is applicable only when using the Web Users table, where the default value of the 'Password Age' parameter in the Web Users table inherits this parameter's value. Web: User Inactivity Timer Defines the duration (in days) for which a user has not logged in...
  • Page 693 WEBPasswordControlViaSNMP = 1, and reset the device with a flash burn (set acSysActionSetResetControl to 1 and acSysActionSetReset to 1). 2) Change the username and password in the acSysWEBAccessEntry table. Use the following format: Username acSysWEBAccessUserName: old/pass/new Password acSysWEBAccessUserCode: username/old/new Version 6.8 Mediant 500 E-SBC...
  • Page 694 Mediant 500 E-SBC Parameter Description [WelcomeMessage] Enables and defines a Welcome message that appears on the Web Login page for logging in to the Web interface. The format of this parameter is as follows: [WelcomeMessage ] FORMAT WelcomeMessage_Index = WelcomeMessage_Text...

  • Page 695: Telnet Parameters

    "Admin". Notes:  The password is case-sensitive.  The password is required only by Admin and Monitor user access levels; Security Administrator and Master user access levels automatically enter the Enable mode upon initial login. Version 6.8 Mediant 500 E-SBC...

  • Page 696: Ini File Parameters

    The valid range is a string of up to 64 characters. [SendKeepAliveTrap] Enables the device to send NAT keep-alive traps to the port of the SNMP network management station (e.g., AudioCodes EMS). This is used for NAT traversal, and allows SNMP communication with AudioCodes EMS management platform, located in the WAN, when the device is located behind NAT.
  • Page 697 (":") in the format xx:xx:...:xx. For example, 00:11:22:33:44:55:66:77:88:99:aa:bb Notes:  For this parameter to take effect, a device reset is required.  Before setting this parameter, all SNMPv3 users must be deleted; otherwise, the parameter setting is ignored. Version 6.8 Mediant 500 E-SBC...
  • Page 698 Mediant 500 E-SBC Parameter Description  If the supplied key does not pass validation of the 12 Hex values input or it is set with the default value, the engine ID is generated according to RFC 3411. Web: SNMP Trap Destination Parameters EMS: Network >...
  • Page 699 Web/EMS: SNMP V3 Users This parameter table defines SNMP v3 users. The format of this CLI: configure system > snmp v3- parameter is as follows: users [SNMPUsers] [SNMPUsers] FORMAT SNMPUsers_Index = SNMPUsers_Username, SNMPUsers_AuthProtocol, SNMPUsers_PrivProtocol, SNMPUsers_AuthKey, SNMPUsers_PrivKey, SNMPUsers_Group; Version 6.8 Mediant 500 E-SBC...

  • Page 700: Serial Parameters

    Mediant 500 E-SBC Parameter Description [\SNMPUsers] For example: SNMPUsers 1 = v3admin1, 1, 0, myauthkey, -, 1; The example above configures user 'v3admin1' with security level authNoPriv(2), authentication protocol MD5, authentication text password 'myauthkey', and ReadWriteGroup2. For a description of this table, see ''Configuring SNMP V3 Users'' on page 80.

  • Page 701: Auxiliary And Configuration File Name Parameters

    0 is Trunk 1. Web: Dial Plan File Defines the name (and path) of the Dial Plan file. This file should be EMS: Dial Plan File Name created using AudioCodes DConvert utility (refer to DConvert Utility [DialPlanFileName] User's Guide). [UserInfoFileName] Defines the name (and path) of the file containing the User Information data.

  • Page 702: Automatic Update Parameters

    Mediant 500 E-SBC 54.1.8 Automatic Update Parameters The automatic update of software and configuration files parameters are described in the table below. Table 54-8: Automatic Update of Software and Configuration Files Parameters Parameter Description General Automatic Update Parameters CLI: configure Enables the Automatic Update mechanism for the cmp file.
  • Page 703  [2] = Enable CRC for individual lines only. Same as option [1], except that the CRC ignores the order of lines (i.e., same text can be on different lines). Version 6.8 Mediant 500 E-SBC...
  • Page 704 Mediant 500 E-SBC Parameter Description CLI: config-system > Defines the size of the TFTP data blocks (packets) when automatic-update tftp-block- downloading a file from a TFTP server for the Automatic Update size mechanism. This is in accordance to RFC 2348. TFTP block size is [AUPDTftpBlockSize] the physical packet size (in bytes) that a network can transmit.
  • Page 705 Defines the name of the User Information file and the path to the server (IP address or FQDN) on which it is located. For example: http://server_name/file, https://server_name/file Note: The maximum length of the URL address is 99 characters. Version 6.8 Mediant 500 E-SBC...

  • Page 706: Networking Parameters

    Mediant 500 E-SBC 54.2 Networking Parameters This subsection describes the device's networking parameters. 54.2.1 Ethernet Parameters The Ethernet parameters are described in the table below. Table 54-9: Ethernet Parameters Parameter Description Physical Ports Settings Table Web: Physical Ports This table parameter configures the physical Ethernet ports. The format...

  • Page 707: Multiple Voip Network Interfaces And Vlan Parameters

    Table parameter format is: CLI: configure voip > static [ StaticRouteTable ] [StaticRouteTable] FORMAT StaticRouteTable_Index = StaticRouteTable_DeviceName, StaticRouteTable_Destination, StaticRouteTable_PrefixLength, StaticRouteTable_Gateway, StaticRouteTable_Description; [ \StaticRouteTable ] For a description, see ''Configuring Static IP Routes'' on page 123. Version 6.8 Mediant 500 E-SBC...

  • Page 708: Quality Of Service Parameters

    Mediant 500 E-SBC 54.2.4 Quality of Service Parameters The Quality of Service (QoS) parameters are described in the table below. Table 54-12: QoS Parameters Parameter Description Layer-2 Class Of Service (CoS) Parameters (VLAN Tag Priority Field) Web: DiffServ Table This table parameter configures DiffServ-to-VLAN Priority EMS: QoS Settings –...

  • Page 709: Nat Parameters

    1. The parameter is used to allow SNMP communication with AudioCodes EMS management platform, located in the WAN, when the device is located behind NAT. It is needed to keep the NAT pinhole open for the SNMP messages sent from EMS to the device .

  • Page 710: Dns Parameters

    Mediant 500 E-SBC 54.2.6 DNS Parameters The Domain name System (DNS) parameters are described in the table below. Table 54-14: DNS Parameters Parameter Description Internal DNS Table Web: Internal DNS Table This table parameter defines the internal DNS table for resolving host EMS: DNS Information names into IP addresses.

  • Page 711: Dhcp Parameters

    Otherwise, the renewal time is divided by this factor. Some DHCP- enabled routers perform better when set to 4. Note: For this parameter to take effect, a device reset is required. DHCP Servers Table Version 6.8 Mediant 500 E-SBC...
  • Page 712 Mediant 500 E-SBC Parameter Description Web: DHCP Servers Defines the device's embedded DHCP server. Table The format of the ini file table parameter is as follows: CLI: configure voip > [ DhcpServer ] dhcp server <index> FORMAT DhcpServer_Index = DhcpServer_InterfaceName,...

  • Page 713: Ntp And Daylight Saving Time Parameters

    Web: Day Light Saving Time Enables daylight saving time. EMS: Mode  [0] Disable (default) CLI: summer-time  [1] Enable [DayLightSavingTimeEnable] Web: Start Time / Day of Defines the date and time when daylight saving begins. This value Version 6.8 Mediant 500 E-SBC...
  • Page 714 Mediant 500 E-SBC Parameter Description Month Start can be configured using any of the following formats: EMS: Start  Day of year - mm:dd:hh:mm, where: CLI: start  mm denotes month [DayLightSavingTimeStart]  dd denotes date of the month ...

  • Page 715: Debugging And Diagnostics Parameters

    [GWAppDelayTime] The valid range is 0 to 45. The default is 7 seconds. Note: This feature helps overcome connection problems caused by some LAN routers or IP configuration parameters' modifications by a DHCP server. Version 6.8 Mediant 500 E-SBC...

  • Page 716: Sip Test Call Parameters

    Mediant 500 E-SBC Parameter Description [EnableAutoRAITransmitBER] Enables the device to send a remote alarm indication (RAI) when the bit error rate (BER) is greater than 0.001.  [0] Disable (default)  [1] Enable 54.3.2 SIP Test Call Parameters The SIP Signaling Test Call parameters are described in the table below.

  • Page 717: Syslog, Cdr And Debug Parameters

    [CDRReportLevel]  [0] None = (Default) CDRs are not used.  [1] End Call = CDR is sent to the Syslog server at the end of each Version 6.8 Mediant 500 E-SBC...
  • Page 718 Note: When debug reporting is enabled, in order to view Syslog messages with Wireshark, you need to install AudioCodes Wireshark plug-in (acsyslog.dll). Once the plug-in is installed, the Syslog messages are decoded as "AC SYSLOG" and are displayed using the 'acsyslog' filter instead of the regular 'syslog' filter.
  • Page 719 EMS: SyslogFacility messages, according to RFC 3164. This allows you to identify Syslog [SyslogFacility] messages generated by the device. This is useful, for example, if you collect the device’s and other equipments’ Syslog messages, at one Version 6.8 Mediant 500 E-SBC...
  • Page 720 Mediant 500 E-SBC Parameter Description single server. The device’s Syslog messages can easily be identified and distinguished from other Syslog messages by its Facility level. Therefore, in addition to filtering Syslog messages according to IP address, the messages can be filtered according to Facility level.
  • Page 721 The format of the ini file table parameter is: [LoggingFilters] [ LoggingFilters ] FORMAT LoggingFilters_Index = LoggingFilters_FilterType, LoggingFilters_Value, LoggingFilters_Syslog, LoggingFilters_CaptureType; [ \LoggingFilters ] For a detailed description of this table, see ''Filtering Syslog Messages and Debug Recordings'' on page 664. Version 6.8 Mediant 500 E-SBC...

  • Page 722: Resource Allocation Indication Parameters

    Mediant 500 E-SBC 54.3.4 Resource Allocation Indication Parameters The Resource Allocation Indication (RAI) parameters are described in the table below. Table 54-20: RAI Parameters Parameter Description [EnableRAI] Enables Resource Available Indication (RAI) alarm generation if the device's busy endpoints exceed a user-defined threshold, configured by the RAIHighThreshold parameter.

  • Page 723: Ha Ping Parameters

    Defines the device's IP network interface from where the ping is sent. Reachability Source The valid value is the name of the IP interface as configured in the Interface Name 'Interface Name' field of the Interface table. By default, no IP network is [HAPingSourceIfName] defined. Version 6.8 Mediant 500 E-SBC...

  • Page 724: Security Parameters

    Mediant 500 E-SBC Parameter Description HA Network Reachability Defines the timeout (in seconds) for which the ping request waits for a Ping Timeout reply. [HAPingTimeout] The valid value is 1 to 60. The default is 1. HA Network Reachability Defines the number of ping requests that the device sends after no...
  • Page 725 Timeout To Relatch RTP (msec) Defines a period (msec) during which if no packets are received [TimeoutToRelatchRTPMsec] from the current RTP session, the channel can re-latch onto another stream. Version 6.8 Mediant 500 E-SBC...

  • Page 726: Https Parameters

    Mediant 500 E-SBC Parameter Description The valid range is any value from 0. The default is 200. Timeout To Relatch SRTP Defines a period (msec) during which if no packets are received [TimeoutToRelatchSRTPMsec] from the current SRTP session, the channel can re-latch onto another stream.
  • Page 727 Notes:  For this parameter to take effect, a device reset is required.  For a description on implementing client certificates, see for Remote Device Management on page 101. Version 6.8 Mediant 500 E-SBC...

  • Page 728: Srtp Parameters

    Mediant 500 E-SBC 54.4.3 SRTP Parameters The Secure Real-Time Transport Protocol (SRTP) parameters are described in the table below. Table 54-24: SRTP Parameters Parameter Description Web: Media Security Enables Secure Real-Time Transport Protocol (SRTP). EMS: Enable Media Security  [0] Disable (default) CLI: media-security-enable ...
  • Page 729 Profile table, see ''Configuring IP Profiles'' on page 304. Note: If this functionality is configured for a specific IP Profile, the settings of this global parameter is ignored for calls associated with the IP Profile. Version 6.8 Mediant 500 E-SBC...

  • Page 730: Tls Parameters

    Mediant 500 E-SBC 54.4.4 TLS Parameters The Transport Layer Security (TLS) parameters are described in the table below. Table 54-25: TLS Parameters Parameter Description Web: TLS Contexts Table Defines SSL/TLS certificates. CLI: configure system > tls # The format of the ini file table parameter is as follows:...
  • Page 731 (‘*’) to replace parts of the domain name. The valid range is a string of up to 49 characters. Note: This parameter is applicable only if the parameter PeerHostNameVerificationMode is set to 1 or 2. Version 6.8 Mediant 500 E-SBC...

  • Page 732: Ssh Parameters

    Mediant 500 E-SBC Parameter Description Web: TLS Expiry Check Start Defines the number of days before the installed TLS server CLI: expiry-check-start certificate is to expire at which the device must send a trap [TLSExpiryCheckStart] (acCertificateExpiryNotifiaction) to notify of this.

  • Page 733: Ids Parameters

    The format of the ini file parameter is: [ IDSRule ] FORMAT IDSRule_Index = IDSRule_Policy, IDSRule_RuleID, IDSRule_Reason, IDSRule_ThresholdScope, IDSRule_ThresholdWindow, IDSRule_MinorAlarmThreshold, IDSRule_MajorAlarmThreshold, IDSRule_CriticalAlarmThreshold, IDSRule_DenyThreshold, IDSRule_DenyPeriod; [ \IDSRule ] For a detailed description of this table, see ''Configuring IDS Policies'' on Version 6.8 Mediant 500 E-SBC...
  • Page 734 Mediant 500 E-SBC Parameter Description page 147. IDS Match Table Web: IDS Match Table Defines target rules per IDS Policy. [IDSMatch] The format of the ini file parameter is: [ IDSMatch ] FORMAT IDSMatch_Index = IDSMatch_SIPInterface, IDSMatch_ProxySet, IDSMatch_Subnet, IDSMatch_Policy; [ \IDSMatch ] For a detailed description of this table, see ''Assigning IDS Policies'' on page 151.

  • Page 735: Quality Of Experience Parameters

    The Quality of Experience (QoE) parameters are described in the table below. Table 54-28: Quality of Experience Parameters Parameter Description SEM Parameters Web: Server IP Defines the IP address of AudioCodes primary Session Experience CLI: configure voip/qoe Manager (SEM) server to where the quality experience reports are configuration/server-ip sent. [QOEServerIP] Note: For this parameter to take effect, a device reset is required.
  • Page 736 Mediant 500 E-SBC Parameter Description [BWProfile] FORMAT BWProfile_Index = BWProfile_Name, BWProfile_EgressAudioBandwidth, BWProfile_IngressAudioBandwidth, BWProfile_EgressVideoBandwidth, BWProfile_IngressVideoBandwidth, BWProfile_TotalEgressBandwidth, BWProfile_TotalIngressBandwidth, BWProfile_WarningThreshold, BWProfile_hysteresis, BWProfile_GenerateAlarms; [\BWProfile] For a detailed description of this table, see ''Configuring Bandwidth Profiles'' on page 244. Note: For this parameter to take effect, a device reset is required.

  • Page 737: Control Network Parameters

    The format of the ini file table parameter is as follows: [Account] FORMAT Account_Index = Account_ServedTrunkGroup, Account_ServedIPGroup, Account_ServingIPGroup, Account_Username, Account_Password, Account_HostName, Account_Register, Account_ContactUser, Account_ApplicationType; [\Account] For a detailed description of this table, see ''Configuring Registration Accounts'' on page 281. Proxy Registration Parameters Version 6.8 Mediant 500 E-SBC...
  • Page 738 Mediant 500 E-SBC Parameter Description Web: Use Default Proxy Enables the use of a SIP proxy server. EMS: Proxy Used  [0] No = (Default) Proxy isn't used and instead, the internal CLI: enable-proxy routing table is used. [IsProxyUsed] ...
  • Page 739 [0]. If DNS resolution fails, the device attempts to route the call to the Proxy. If routing to the Proxy also fails, the Redirect/Transfer request is rejected.  When this parameter is set to [2], the XferPrefix parameter Version 6.8 Mediant 500 E-SBC...
  • Page 740 Mediant 500 E-SBC Parameter Description can be used to define different routing rules for redirect calls.  This parameter is disregarded if the parameter AlwaysSendToProxy is set to 1. Web/EMS: DNS Query Type Enables the use of DNS Naming Authority Pointer (NAPTR)
  • Page 741 The first request to the Proxy is sent without authorization. The [SIPChallengeCachingMode] Proxy sends a 401/407 response with a challenge. This response is saved for further uses. A new request is re-sent with the appropriate credentials. Subsequent requests to the Version 6.8 Mediant 500 E-SBC...
  • Page 742 Mediant 500 E-SBC Parameter Description Proxy are automatically sent with credentials (calculated from the saved challenge). If the Proxy doesn't accept the new request and sends another challenge, the old challenge is replaced with the new one.  [0] None = (Default) Challenges are not cached. Every new request is sent without preliminary authorization.
  • Page 743 Type initiated by the device to the Registrar. CLI: registrar-transport  [-1] Not Configured (default) [RegistrarTransportType]  [0] UDP  [1] TCP  [2] TLS Notes:  This parameter is applicable only to the Gateway Version 6.8 Mediant 500 E-SBC...
  • Page 744 Mediant 500 E-SBC Parameter Description application.  When set to ‘Not Configured’, the value of the parameter SIPTransportType is used. Web/EMS: Registration Time Defines the time interval (in seconds) for registering to a Proxy CLI: registration-time server. The value is used in the SIP Expires header. This...
  • Page 745 If all the Accounts of a specific Trunk Group fail registration and if the Trunk Group comprises a complete trunk, then the entire trunk is set to out-of-service. Version 6.8 Mediant 500 E-SBC...
  • Page 746 Mediant 500 E-SBC Parameter Description Note: This parameter is applicable only to the Gateway application. CLI: expl-un-reg Enables the device to perform explicit unregisters. [UnregistrationMode]  [0] Disable (default)  [1] Enable = The device sends an asterisk ("*") value in the SIP Contact header, instructing the Registrar server to remove all previous registration bindings.
  • Page 747 200 sec, the interval used is any random time between 160 to 200 seconds. This prevents an “avalanche” of keep-alive by multiple SIP UAs to a specific server. Max Generated Register Rate Defines the maximum number of user register requests Version 6.8 Mediant 500 E-SBC...

  • Page 748: Network Application Parameters

    Mediant 500 E-SBC Parameter Description configure voip > sip-definition (REGISTER messages) that the device sends (to a proxy or settings > max-gen-reg-rate registrar server) at a user-defined rate configured by the GeneratedRegistersInterval parameter. The parameter is [MaxGeneratedRegistersRate] useful in that it may be used to prevent an overload on the device's CPU caused by sending many registration requests at a given time.
  • Page 749 EMS: Media Realm allows you to divide a Media-type interface (defined in the Interface CLI: configure voip > voip- table) into several realms, where each realm is specified by a UDP port network realm range. Version 6.8 Mediant 500 E-SBC...

  • Page 750: General Sip Parameters

    Mediant 500 E-SBC Parameter Description [CpMediaRealm] The format of the ini file table parameter is as follows: [ CpMediaRealm ] FORMAT CpMediaRealm_Index = CpMediaRealm_MediaRealmName, CpMediaRealm_IPv4IF, CpMediaRealm_IPv6IF, CpMediaRealm_PortRangeStart, CpMediaRealm_MediaSessionLeg, CpMediaRealm_PortRangeEnd, CpMediaRealm_IsDefault, CpMediaRealm_QoeProfile, CpMediaRealm_BWProfile; [ \CpMediaRealm ] For a detailed description of this table, see ''Configuring Media Realms'' on page 251.
  • Page 751 (if Automatic Update has been enabled on the device)  'check-sync;reboot=true': triggers a device reset Note: The Event header value is proprietary to AudioCodes. Web/EMS: Max SIP Defines the maximum size (in Kbytes) for each SIP message that can Message Length [KB] be sent over the network.
  • Page 752 Mediant 500 E-SBC Parameter Description Release Call SIP BYE and SIP 200 OK response to BYE, using the proprietary SIP [QoSStatistics] header X-RTP-Stat.  [0] = Disable (default)  [1] = Enable The X-RTP-Stat header provides the following statistics: ...
  • Page 753 SIP 4xx response even if the EnableEarlyMedia parameter is set to 1.  [0] = (Default) If a Progress with Cause message is received from the PSTN for an outgoing IP-to-ISDN call, the device does not Version 6.8 Mediant 500 E-SBC...
  • Page 754 Mediant 500 E-SBC Parameter Description disconnect the call by sending a SIP 4xx response to the originating party.  [1] = The device sends a SIP 4xx response when the EnableEarlyMedia parameter is set to 0.  [2] = The device always sends a SIP 4xx response, even if he EnableEarlyMedia parameter is set to 1.
  • Page 755 INVITE SDP offer is a VBD coder. For example, if the device is configured with G.729 and G.711 VBD coders and it receives an INVITE with an SDP offer containing G.729 and “regular” G.711 coders, it sends an SDP answer containing G.729 and G.711 VBD Version 6.8 Mediant 500 E-SBC...
  • Page 756 Mediant 500 E-SBC Parameter Description coders, allowing a subsequent bypass (passthrough) session if fax/modem signals are detected during the call. Note: This parameter is applicable only if G.711 VBD coder(s) with regular G.711 payload types 0 or 8 are configured for the device (using the CodersGroup parameter).
  • Page 757 [0] = (Default) Disable. All TCP connections (except those that are [ReliableConnectionPersis set to a proxy IP) are released if not used by any SIP tentMode] dialog\transaction.  [1] = Enable - TCP connections to all destinations are persistent Version 6.8 Mediant 500 E-SBC...
  • Page 758 Mediant 500 E-SBC Parameter Description and not released unless the device reaches 70% of its maximum TCP resources. While trying to send a SIP message connection, reuse policy determines whether live connections to the specific destination are re- used. Persistent TCP connection ensures less network traffic due to fewer setting up and tearing down of TCP connections and reduced latency on subsequent requests due to avoidance of initial TCP handshake.
  • Page 759 [1]. In addition, for incoming SIP INVITEs, if the Request-URI includes a 'tgrp' parameter, the device routes the call according to that value (if possible). The Contact header in the outgoing SIP INVITE (Tel-to- Version 6.8 Mediant 500 E-SBC...
  • Page 760 Mediant 500 E-SBC Parameter Description IP call) contains "tgrp=<source trunk group ID>;trunk- context=<gateway IP address>”. The <source trunk group ID> is the Trunk Group ID where incoming calls from Tel is received. For IP-Tel calls, the SIP 200 OK device's response contains “tgrp=<destination trunk group ID>;trunk-context=<gateway IP...
  • Page 761 B, and user A wants to transfer the call to user C. User A sends a REFER to user C: REFER sip:C@domain.com SIP/2.0 From: sip:A@domain.com;tag=99asd To: sip:C@domain.com Refer-To: (URI that identifies B's UA) The Refer-To header needs to contain a URI that user C can use to Version 6.8 Mediant 500 E-SBC...
  • Page 762 EMS: User Agent Display value>/software version' is used, for example: Info User-Agent: myproduct/v.6.40.010.006 CLI: user-agent-info If not configured, the default string, <AudioCodes product- [UserAgentDisplayInfo] name>/software version' is used, for example: User-Agent: Audiocodes-Sip-Gateway-Mediant 500 E- SBC/v.6.80.010.006 The maximum string length is 50 characters.
  • Page 763 Party B is put on-hold while Party A blind transfers Party B to Party Party C answers and Party B is made un-hold. However, as Party C supports only G.729 coder, re-negotiation of the supported coder is required. Version 6.8 Mediant 500 E-SBC...
  • Page 764 Mediant 500 E-SBC Parameter Description Note: This parameter is applicable only to the Gateway application. Web: Multiple Packetization Determines whether the 'mptime' attribute is included in the outgoing Time Format SDP. EMS: Multi Ptime Format  [0] None = (Default) Disabled.
  • Page 765 Ensure that the parameter value is the one with which the Proxy has been configured with to identify the device.  This parameter can also be configured for an IP Group (in the IP Group table). Version 6.8 Mediant 500 E-SBC...
  • Page 766 Mediant 500 E-SBC Parameter Description [ZeroSDPHandling] Determines the device's response to an incoming SDP that includes an IP address of 0.0.0.0 in the SDP's Connection Information field (i.e., "c=IN IP4 0.0.0.0").  [0] = (Default) Sets the IP address of the outgoing SDP's c= field to 0.0.0.0.
  • Page 767 INVITE messages and 180, 183, and 200 OK SIP responses. The header includes the Trunk number, B-channel, and the device's IP address. For example, 'x-channel: DS/DS1-5/8;IP=192.168.13.1', where:  'DS/DS-1' is a constant string  '5' is the Trunk number Version 6.8 Mediant 500 E-SBC...
  • Page 768 Mediant 500 E-SBC Parameter Description  '8' is the B-channel  'IP=192.168.13.1' is the device's IP address Web/EMS: Progress Global parameter that defines the progress indicator (PI) sent to the IP. Indicator to IP You can also configure this functionality per specific calls, using IP CLI: prog-ind-2ip Profiles (IpProfile_ProgressIndicator2IP) or Tel Profiles.
  • Page 769 If the parameter EnableMicrosofExt is enabled, the device modifies the called number by adding an "e" as the prefix, removing the "ext=" parameter, and adding the extension number as the suffix (e.g., e622125519100104). Once modified, the Version 6.8 Mediant 500 E-SBC...
  • Page 770 Mediant 500 E-SBC Parameter Description device can then manipulate the number further, using the Number Manipulation tables to leave only the last 3 digits (for example) for sending to a PBX. EMS: Use SIP URI For Defines the URI format in the SIP Diversion header.
  • Page 771 PSTNAlertTimeout parameter value is overridden. Web/EMS: RTP Only Mode Enables the device to send and receive RTP packets to and from CLI: rtp-only-mode remote endpoints without the need to establish a SIP session. The Version 6.8 Mediant 500 E-SBC...
  • Page 772 Mediant 500 E-SBC Parameter Description [RTPOnlyMode] remote IP address is determined according to the Outbound IP Routing table (Prefix parameter). The port is the same port as the local RTP port (configured by the BaseUDPPort parameter and the channel on which the call is received).
  • Page 773 Digital: The Busy-Out condition can also be applied to a specific Trunk Group. If there is no connectivity to the Serving IP Group of a specific Trunk Group (defined in the Hunt Group Settings table), all Version 6.8 Mediant 500 E-SBC...
  • Page 774 Mediant 500 E-SBC Parameter Description physical trunks pertaining to that Trunk Group are set to the Busy- Out condition. Each trunk uses the proper Out-Of-Service method according to the selected ISDN/CAS variant.  Digital: For configuring the method for taking trunks/channels out- of-service, see the DigitalOOSBehaviorForTrunk_x parameter for per trunk or the DigitalOOSBehavior parameter for all trunks.
  • Page 775 - Partially configured trunk (only some channels configured): The device rejects new incoming calls and sends out-of-service Service messages to all the configured channels (D-channel remains up).  Graceful out-of-service enabled: The device rejects new Version 6.8 Mediant 500 E-SBC...
  • Page 776 Mediant 500 E-SBC Parameter Description incoming calls and does the following: - Fully configured trunk (all channels): > If all channels are idle when the graceful period begins, the device immediately takes the channels out-of-service without sending out-of-service Service messages and instead, only takes the D-channel down.
  • Page 777 SipT2Rtx. Web: SIP Maximum RTX Defines the maximum number of UDP transmissions of SIP messages EMS: Max RTX (first transmission plus retransmissions). CLI: sip-max-rtx The range is 1 to 30. The default is 7. [SIPMaxRtx] Version 6.8 Mediant 500 E-SBC...
  • Page 778 Mediant 500 E-SBC Parameter Description Web: Number of RTX Defines the number of retransmitted INVITE/REGISTER messages Before Hot-Swap before the call is routed (hot swap) to another Proxy/Registrar. EMS: Proxy Hot Swap Rtx The valid range is 1 to 30. The default is 3.

  • Page 779: Coders And Profile Parameters

    IP Groups. The format of the ini file table parameter is profile as follows: [IPProfile] [IPProfile] FORMAT IpProfile_Index = IpProfile_ProfileName, IpProfile_IpPreference, IpProfile_CodersGroupID, IpProfile_IsFaxUsed, IpProfile_JitterBufMinDelay, IpProfile_JitterBufOptFactor, IpProfile_IPDiffServ, IpProfile_SigIPDiffServ, IpProfile_SCE, IpProfile_RTPRedundancyDepth, IpProfile_RemoteBaseUDPPort, IpProfile_CNGmode, IpProfile_VxxTransportType, IpProfile_NSEMode, IpProfile_IsDTMFUsed, IpProfile_PlayRBTone2IP, Version 6.8 Mediant 500 E-SBC...
  • Page 780 Mediant 500 E-SBC Parameter Description IpProfile_EnableEarlyMedia, IpProfile_ProgressIndicator2IP, IpProfile_EnableEchoCanceller, IpProfile_CopyDest2RedirectNumber, IpProfile_MediaSecurityBehaviour, IpProfile_CallLimit, IpProfile_DisconnectOnBrokenConnection, IpProfile_FirstTxDtmfOption, IpProfile_SecondTxDtmfOption, IpProfile_RxDTMFOption, IpProfile_EnableHold, IpProfile_InputGain, IpProfile_VoiceVolume, IpProfile_AddIEInSetup, IpProfile_SBCExtensionCodersGroupID, IpProfile_MediaIPVersionPreference, IpProfile_TranscodingMode, IpProfile_SBCAllowedMediaTypes, IpProfile_SBCAllowedCodersGroupID, IpProfile_SBCAllowedVideoCodersGroupID, IpProfile_SBCAllowedCodersMode, IpProfile_SBCMediaSecurityBehaviour, IpProfile_SBCRFC2833Behavior, IpProfile_SBCAlternativeDTMFMethod, IpProfile_SBCAssertIdentity, IpProfile_AMDSensitivityParameterSuit, IpProfile_AMDSensitivityLevel, IpProfile_AMDMaxGreetingTime, IpProfile_AMDMaxPostSilenceGreetingTime, IpProfile_SBCDiversionMode, IpProfile_SBCHistoryInfoMode, IpProfile_EnableQSIGTunneling, IpProfile_SBCFaxCodersGroupID, IpProfile_SBCFaxBehavior, IpProfile_SBCFaxOfferMode,...
  • Page 781 TelProfile_EnableCurrentDisconnect, TelProfile_EnableDigitDelivery, TelProfile_EnableEC, TelProfile_MWIAnalog, TelProfile_MWIDisplay, TelProfile_FlashHookPeriod, TelProfile_EnableEarlyMedia, TelProfile_ProgressIndicator2IP, TelProfile_TimeForReorderTone, TelProfile_EnableDIDWink, TelProfile_IsTwoStageDial, TelProfile_DisconnectOnBusyTone, TelProfile_EnableVoiceMailDelay, TelProfile_DialPlanIndex, TelProfile_Enable911PSAP, TelProfile_SwapTelToIpPhoneNumbers, TelProfile_EnableAGC, TelProfile_ECNlpMode, TelProfile_DigitalCutThrough, TelProfile_EnableFXODoubleAnswer, TelProfile_CallPriorityMode; [\TelProfile] For a description of this parameter, see Configuring Tel Profiles on page 301. Version 6.8 Mediant 500 E-SBC...

  • Page 782: Channel Parameters

    Mediant 500 E-SBC 54.9 Channel Parameters This subsection describes the device's channel parameters. 54.9.1 Voice Parameters The voice parameters are described in the table below. Table 54-33: Voice Parameters Parameter Description Web/EMS: Input Gain Global parameter that defines the pulse-code modulation CLI: input-gain (PCM) input (received) gain control level (in decibels).
  • Page 783 Web: Enable Answer Detector Currently, not supported. [EnableAnswerDetector] Web: Answer Detector Activity Delay Defines the time (in 100-msec resolution) between CLI: answer-detector-activativity-delay activating the Answer Detector and the time that the [AnswerDetectorActivityDelay] detector actually starts to operate. Version 6.8 Mediant 500 E-SBC...

  • Page 784: Coder Parameters

    Mediant 500 E-SBC Parameter Description The valid range is 0 to 1023. The default is 0. Web: Answer Detector Silence Time Currently, not supported. [AnswerDetectorSilenceTime] Web: Answer Detector Redirection Currently, not supported. [AnswerDetectorRedirection] Web: Answer Detector Sensitivity Defines the Answer Detector sensitivity.

  • Page 785: Dtmf Parameters

    NTEs (RFC 4733/2833 DTMF relay) to the IP side, regardless of duration the DTMF signal duration on the TDM side. [NTEMaxDuration] The range is -1 to 200,000,000 msec. The default is -1 (i.e., NTE stops only upon detection of an End event). Version 6.8 Mediant 500 E-SBC...

  • Page 786: Rtp, Rtcp And T.38 Parameters

    Mediant 500 E-SBC 54.9.4 RTP, RTCP and T.38 Parameters The RTP, RTCP and T.38 parameters are described in the table below. Table 54-36: RTP/RTCP and T.38 Parameters Parameter Description Web: Dynamic Jitter Buffer Minimum Global parameter that defines the minimum delay (in msec) of Delay the device's dynamic Jitter Buffer.
  • Page 787 If the device is located in a network subnet which is connected to other gateways using a router that uses Virtual Router Redundancy Protocol (VRRP) for redundancy, then set this parameter to 0 or 2. Version 6.8 Mediant 500 E-SBC...
  • Page 788 Mediant 500 E-SBC Parameter Description Web: RTP Base UDP Port Global parameter that defines the lower boundary of the UDP EMS: Base UDP Port port used for RTP, RTCP (RTP port + 1) and T.38 (RTP port + [BaseUDPport] 2). For a detailed description of configuring the UDP port range, see Configuring RTP Base UDP Port on page 176.
  • Page 789 IP address or as a domain name. Note:  Instead of sending RTCP XR to an ESC server, you can send RTCP XR to an IP Group (see the PublicationIPGroupID parameter).  This parameter is applicable only to the Gateway application. Version 6.8 Mediant 500 E-SBC...
  • Page 790 Mediant 500 E-SBC Parameter Description Web: Gateway RTCP XR Report Enables the device to send RTCP XR in SIP PUBLISH Mode messages to the Event State Compositor (ESC) server and EMS: Report Mode defines the interval at which they are sent.

  • Page 791: Gateway And Ip-To-Ip Parameters

    Note: You can also configure this functionality per specific calls, using IP Profiles (IpProfile_VxxTransportType). For more information, see ''Configuring IP Profiles'' on page 304. Web: V.32 Modem Transport Type Determines the V.32 modem transport type. EMS: V32 Transport  [0] Disable = Transparent. Version 6.8 Mediant 500 E-SBC...
  • Page 792 Mediant 500 E-SBC Parameter Description  [2] Enable Bypass (default) CLI: V32-modem-transport-type [V32ModemTransportType]  [3] Events Only = Transparent with Events. Notes:  This parameter applies only to V.32 and V.32bis modems.  You can also configure this functionality per specific calls, using IP Profiles (IpProfile_VxxTransportType).
  • Page 793 The rate is negotiated between both sides (i.e., the device adapts to the capabilities of the remote side). Negotiation of the T.38 maximum supported fax data rate is provided in SIP’s SDP T38MaxBitRate parameter. The negotiated T38MaxBitRate is the minimum rate supported between the Version 6.8 Mediant 500 E-SBC...
  • Page 794 Mediant 500 E-SBC Parameter Description local and remote endpoints.  Fax relay rates greater than 14.4 kbps are applicable only to V.34 / T.38 fax relay. For non-T.38 V.34 supporting devices, configuration greater than 14.4 kbps is truncated to 14.4 kbps.
  • Page 795 When the device is configured to use V.152 to negotiate audio and T.38 coders, the UDP port published in SDP for RTP and for T38 must be different. Therefore, set the T38UseRTPPort parameter to 0. Version 6.8 Mediant 500 E-SBC...
  • Page 796 Mediant 500 E-SBC Parameter Description Web/EMS: T.38 Max Datagram Defines the maximum size of a T.38 datagram that the device Size can receive. This value is included in the outgoing SDP when CLI: t38-mx-datagram-sz T.38 is used. [T38MaxDatagramSize] The valid range is 120 to 600. The default is 560.
  • Page 797 [V1501SPRTTransportChannel2M axWindowSize] Web: SPRT Transport Ch.3 Max Defines the maximum payload size for V.150.1 SPRT Transport Payload Size Channel 3. CLI: SPRT-transport-channel3- The range is 140 to 256. The default is 140. max-payload-size [V1501SPRTTransportChannel3M axPayloadSize] Version 6.8 Mediant 500 E-SBC...

  • Page 798: Dtmf And Hook-Flash Parameters

    Mediant 500 E-SBC 54.10.2 DTMF and Hook-Flash Parameters The DTMF and hook-flash parameters are described in the table below. Table 54-38: DTMF and Hook-Flash Parameters Parameter Description Hook-Flash Parameters Web/EMS: Hook-Flash Code For digital interfaces: Defines the digit pattern used by the PBX CLI: hook-flash-code to indicate a Hook Flash event.
  • Page 799 SDP. Expects to receive RFC 2833 packets with the same payload type as configured by the parameter RFC2833PayloadType. Removes DTMF digits in transparent mode (as part of Version 6.8 Mediant 500 E-SBC...
  • Page 800 Mediant 500 E-SBC Parameter Description the voice stream).  When TxDTMFOption is set to 0, the RFC 2833 payload type is set according to the parameter RFC2833PayloadType for both transmit and receive.  If an ISDN phone user presses digits (e.g., for interactive...

  • Page 801: Digit Collection And Dial Plan Parameters

    Dial Plan file. The default is -1 (disabled). For more information on this feature, see ''Modifying ISDN-to-IP Calling Party Number'' on page 563. Web: Digit Mapping Rules Defines the digit map pattern (used to reduce the dialing period when Version 6.8 Mediant 500 E-SBC...
  • Page 802 Mediant 500 E-SBC Parameter Description EMS: Digit Map Pat terns ISDN overlap dialing for digital interfaces). If the digit string (i.e., CLI: default-dm dialed number) matches one of the patterns in the digit map, the [DigitMapping] device stops collecting digits and establishes a call with the collected number.

  • Page 803: Voice Mail Parameters

    >> 486 No reply >> 408 Deflection >> 487/480 Unconditional >> 302 Others >> 302 If the device receives a Request-URI that includes a 'target' and 'cause' parameter, the 'target' is mapped to the Redirect phone Version 6.8 Mediant 500 E-SBC...
  • Page 804 Mediant 500 E-SBC Parameter Description number and the 'cause' is mapped to the Redirect number reason. [WaitForBusyTime] Defines the time (in msec) that the device waits to detect busy and/or reorder tones. This feature is used for semi-supervised PBX call transfers (i.e., the LineTransferMode parameter is set to 2).
  • Page 805 Note: If this parameter is not configured, the MWI SUBSCRIBE message is sent to the MWI server as defined by the MWIServerIP parameter. [NotificationIPGroupID] Defines the IP Group ID to which the device sends SIP NOTIFY MWI messages. Version 6.8 Mediant 500 E-SBC...
  • Page 806 Mediant 500 E-SBC Parameter Description Notes:  This is used for MWI Interrogation. For more information on the interworking of QSIG MWI to IP, see Message Waiting Indication on page 417.  To determine the handling method of MWI Interrogation messages, use the TrunkGroupSettings_MWIInterrogationType, parameter (in the Trunk Group Settings table).
  • Page 807 Defines a digit pattern that if received as Src (S) or Redirect (R) Pattern numbers is ignored and not added to that number. EMS: Digit To Ignore The valid range is a 25-character string. CLI: dig-to-ignore-dig-pattern [DigitPatternDigitToIgnore] Version 6.8 Mediant 500 E-SBC...

  • Page 808: Supplementary Services Parameters

    Mediant 500 E-SBC 54.10.5 Supplementary Services Parameters This subsection describes the device's supplementary telephony services parameters. 54.10.5.1 Caller ID Parameters The caller ID parameters are described in the table below. Table 54-41: Caller ID Parameters Parameter Description Web/EMS: Enable Caller ID Global parameter that enables Caller ID.

  • Page 809: Call Waiting Parameters

    EMS: Send 180 For Call Waiting Determines the SIP response code for indicating Call Waiting. [Send180ForCallWaiting]  [0] = (Default) Use 182 Queued response to indicate call waiting.  [1] = Use 180 Ringing response to indicate call waiting. Version 6.8 Mediant 500 E-SBC...

  • Page 810: Call Forwarding Parameters

    Mediant 500 E-SBC 54.10.5.3 Call Forwarding Parameters The call forwarding parameters are described in the table below. Table 54-43: Call Forwarding Parameters Parameter Description Web: Enable Call Enables the Call Forwarding feature. Forward  [0] Disable CLI: call-forward  [1] Enable (Default)

  • Page 811: Call Transfer Parameters

    XferPrefixIP2Tel to "*8" and the parameter TrunkTransferMode to 5. Web/EMS: Enable Semi-Attended Determines the device behavior when Transfer is initiated Transfer while in Alerting state. Version 6.8 Mediant 500 E-SBC...
  • Page 812 Mediant 500 E-SBC Parameter Description  [0] Disable = (Default) Send REFER with the Replaces CLI: semi-att-transfer [EnableSemiAttendedTransfer] header.  [1] Enable = Send CANCEL, and after a 487 response is received, send REFER without the Replaces header. Web: Blind...

  • Page 813: Mlpp And Emergency Call Parameters

    This parameter is applicable to CAS and ISDN.  MLPP and Emergency services can also be configured in a Tel Profile.  For more information, see ''Pre-empting Existing Call for E911 IP-to-Tel Call'' on page 418. Version 6.8 Mediant 500 E-SBC...
  • Page 814 Mediant 500 E-SBC Parameter Description Emergency E911 Parameters [E911Gateway] Enables Enhanced 9-1-1(E9-1-1) support for ELIN handling in Microsoft Lync Server 2010 environment.  [0] = Disable (default)  [1] = Enable  [2] = Location-based manipulations [E911CallbackTimeout] Defines the maximum interval within which the PSAP can use the ELIN to call back the E9-1-1 caller.
  • Page 815 IP packets containing SIP messages that CLI: mlpp-diffserv are related to MLPP calls. This parameter defines DiffServ for [MLPPDiffserv] incoming and outgoing MLPP calls with the Resource-Priority header. The valid range is 0 to 63. The default is 50. Version 6.8 Mediant 500 E-SBC...
  • Page 816 Mediant 500 E-SBC Parameter Description Web/EMS: Preemption Tone Defines the duration (in seconds) in which the device plays a Duration preemption tone to the Tel and IP sides if a call is preempted. CLI: preemp-tone-dur The valid range is 0 to 60. The default is 3.
  • Page 817 PremiumServiceClassMediaDiffServ or as defined in IP Profiles per call. Web/EMS: RTP DSCP for MLPP Defines the RTP DSCP for MLPP Flash-Override-Override Flash-Override-Override precedence call level. CLI: dscp-4-mlpp-flsh-ov-ov The valid range is -1 to 63. The default is -1. Version 6.8 Mediant 500 E-SBC...

  • Page 818: Call Cut-Through Parameters

    Mediant 500 E-SBC Parameter Description [MLPPFlashOverOverRTPDSCP] Note: If set to -1, the DiffServ value is taken from the global parameter PremiumServiceClassMediaDiffServ or as defined in IP Profiles per call. 54.10.5.7 Call Cut-Through Parameters The call cut-through parameters are described in the table below.

  • Page 819: Pstn Parameters

    [11] T1 4ESS ISDN = ISDN PRI protocol for the Lucent™/AT&T™ 4ESS switch.  [12] T1 5ESS 9 ISDN = ISDN PRI protocol for the Lucent™/AT&T™ 5ESS-9 switch.  [13] T1 5ESS 10 ISDN = ISDN PRI protocol for the Version 6.8 Mediant 500 E-SBC...
  • Page 820 Mediant 500 E-SBC Parameter Description Lucent™/AT&T™ 5ESS-10 switch.  [14] T1 DMS100 ISDN = ISDN PRI protocol for the Nortel™ DMS switch.  [15] J1 TRANSPARENT  [16] T1 NTT ISDN = ISDN PRI protocol for the Japan - Nippon Telegraph Telephone (known also as INS 1500).
  • Page 821 [A] T1 FRAMING F4 = T1 4-Frame multiframe.  [B] T1 FRAMING F12 = T1 12-Frame multiframe (D4).  [C] T1 FRAMING ESF = T1 Extended SuperFrame without CRC6  [D] T1 FRAMING ESF CRC6 = T1 Extended SuperFrame with CRC6 Version 6.8 Mediant 500 E-SBC...
  • Page 822 Mediant 500 E-SBC Parameter Description  [E] T1 FRAMING F72 = T1 72-Frame multiframe (SLC96)  [F] T1 FRAMING ESF CRC6 J2 = J1 Extended SuperFrame with CRC6 (Japan) [FramingMethod_x] Same as the description for parameter FramingMethod, but for a specific trunk ID (where x denotes the Trunk ID and 0 is the first Trunk).
  • Page 823 (a, e, i, o, and u, respectively).  [1] Western European (Default)  [2] Central European  [3] South European  [4] North European  [5] Cyrillic  [6] Arabic  [7] Hebrew  [8] Turkish Version 6.8 Mediant 500 E-SBC...

  • Page 824: Tdm Bus And Clock Timing Parameters

    Mediant 500 E-SBC 54.10.6.2 TDM Bus and Clock Timing Parameters The TDM Bus parameters are described in the table below. Table 54-49: TDM Bus and Clock Timing Parameters Parameter Description TDM Bus Parameters Web/EMS: PCM Law Select Determines the type of pulse-code modulation (PCM) companding [PCMLawSelect] algorithm law in input and output TDM bus.
  • Page 825 100 indicates that the device does not perform a fallback to the [AutoClockTrunkPriority] trunk (typically, used to mark untrusted source of clock). Note: Fallback is enabled when the TDMBusPSTNAutoClockEnable parameter is set to 1. Version 6.8 Mediant 500 E-SBC...

  • Page 826: Cas Parameters

    Mediant 500 E-SBC 54.10.6.3 CAS Parameters The Common Channel Associated (CAS) parameters are described in the table below. Table 54-50: CAS Parameters Parameter Description Web: CAS Transport Type Determines the ABCD signaling transport type over IP. EMS: CAS Relay Transport Mode ...
  • Page 827 To configure this parameter, the trunk must first be stopped.  Only one of these formats can be implemented; not both.  When this parameter is not configured, a single CAS table for the entire trunk is used, configured by the parameter CASTableIndex. Version 6.8 Mediant 500 E-SBC...
  • Page 828 Mediant 500 E-SBC Parameter Description [CASTablesNum] Defines how many CAS protocol configurations files are loaded. The valid range is 1 to 8. Note: For this parameter to take effect, a device reset is required. CAS State Machines Parameters Note: For configuring the CAS State Machine table using the Web interface, see ''Configuring CAS State Machines'' on page 337.

  • Page 829: Isdn Parameters

    [0] = PI is not added (default).  [1] = PI 1 is added to a sent ISDN Setup message - call is not end-to-end ISDN.  [3] = PI 3 is added to a sent ISDN Setup message - Version 6.8 Mediant 500 E-SBC...
  • Page 830 Mediant 500 E-SBC Parameter Description calling equipment is not ISDN. NFAS Parameters Note: These parameters are applicable to PRI interfaces. Web: NFAS Group Number Defines the ISDN Non-Facility Associated Signaling (NFAS) EMS: Group Number group number (NFAS member), per trunk.
  • Page 831 Bit-field used to determine several behavior options that Behavior influence the behaviour of the Q.931 protocol. CLI: isdn-bits-ns-behavior  [0] = Disable (default). [ISDNIBehavior]  [1] NO STATUS ON UNKNOWN IE = Q.931 Status message isn't sent if Q.931 received message contains Version 6.8 Mediant 500 E-SBC...
  • Page 832 Mediant 500 E-SBC Parameter Description an unknown/unrecognized IE. By default, the Status message is sent. Note: This value is applicable only to ISDN variants in which sending of Status message is optional.  [2] NO STATUS ON INV OP IE = Q.931 Status message isn't sent if an optional IE with invalid content is received.
  • Page 833 1 to 15 and 17 to 31. This is the new QSIG mode of operation. When this bit is not set (default), the channel_id #16 is not allowed, as for all ETSI-like standards. Version 6.8 Mediant 500 E-SBC...
  • Page 834 Mediant 500 E-SBC Parameter Description  [64] USE T1 PRI = PRI interface type is forced to T1.  [128] USE E1 PRI = PRI interface type is forced to E1.  [256] START WITH B CHAN OOS = B-channels start in the Out-Of-Service state (OOS).
  • Page 835 [64] NS BEHAVIOUR2 FAC REJECT = When this bit is set, the device answers with a Facility IE message with the Reject component on receipt of Facility IE with unknown/invalid Invoke component. This bit is implemented in QSIG and ETSI variants. Version 6.8 Mediant 500 E-SBC...

  • Page 836: Isdn And Cas Interworking Parameters

    Mediant 500 E-SBC Parameter Description [PSTNExtendedParams] Determines the bit map for special PSTN behavior parameters:  [0] = (Default) Applicable for NI-2 ISDN and QSIG "Networking Extensions". This bit (i.e., bit #0) is responsible for the Invoke ID size: ...
  • Page 837  [3] Through SIP INFO =Interworking of ISDN Overlap Dialing to SIP according to RFC 3578. The device sends the first received digits from the ISDN Setup message to the IP side in the initial Version 6.8 Mediant 500 E-SBC...
  • Page 838 Mediant 500 E-SBC Parameter Description INVITE message. For each subsequently received ISDN Info Q.931 message, the device sends the collected digits to the IP side in INFO messages. Notes:  When option [2] or [3] is configured, you can define the minimum...
  • Page 839 Defines the format of encapsulated QSIG message data in the SIP message MIME body.  [0] = (Default) ASCII presentation of Q.931 QSIG message.  [1] = Binary encoding of Q.931 QSIG message (according to Version 6.8 Mediant 500 E-SBC...
  • Page 840 Mediant 500 E-SBC Parameter Description ECMA-355, RFC 3204, and RFC 2025). Note: This parameter is applicable only if the QSIG Tunneling feature is enabled (using the EnableQSIGTunneling parameter). Web: Enable Hold to ISDN Enables SIP-to-ISDN interworking of the Hold/Retrieve EMS: Enable Hold 2 ISDN supplementary service.
  • Page 841 The CPC is denoted in the PSTN message as follows:  ISDN PRI NI-2: In the Originating Line Information (OLI) Information Element (IE) of the ISDN Setup message.  MFC-R2: ANI II digits. The device supports the Brazilian and Version 6.8 Mediant 500 E-SBC...
  • Page 842 Mediant 500 E-SBC Parameter Description Argentinian variants. This regional support is configured using the CallingPartyCategoryMode. The CPC is denoted in the SIP INVITE message using the 'cpc=' parameter in the From or P-Asserted-Identity headers. For example, the 'cpc=' parameter in the below INVITE message is set to "payphone":...
  • Page 843 [-1] Use Global Parameter = (Default) Settings of the global [RemoveCallingNameForTru parameter RemoveCallingName are used. nk_x]  [0] Disable = Does not remove Calling Name.  [1] Enable = Remove Calling Name. Note: The x in the ini file parameter name denotes the trunk Version 6.8 Mediant 500 E-SBC...
  • Page 844 Mediant 500 E-SBC Parameter Description number, where 0 is Trunk 1. Web/EMS: Progress Indicator Determines the Progress Indicator (PI) to ISDN per trunk. to ISDN  [-1] Not Configured = (Default) The PI in ISDN messages is set CLI: pi-to-isdn according to the parameter PlayRBTone2Tel.
  • Page 845 Determines whether the Carrier Identification Code (CIC) is relayed [EnableCIC] to ISDN.  [0] = (Default) Do not relay the Carrier Identification Code (CIC) to ISDN.  [1] = CIC is relayed to the ISDN in Transit Network Selection Version 6.8 Mediant 500 E-SBC...
  • Page 846 Mediant 500 E-SBC Parameter Description (TNS) IE. If enabled, the CIC code (received in an INVITE Request-URI) is included in a TNS IE in the ISDN Setup message. For example: INVITE sip:555666;cic=2345@100.2.3.4 sip/2.0. Notes:  This feature is supported only for SIP-to-ISDN calls.
  • Page 847 Trunk's PSTN protocol (configured by the parameter ProtocolType) [TrunkTransferMode] and is applicable only when one of these protocols are used: PSTN Protocol Transfer Method (Described Below) E1 Euro ISDN [1] ECT [2] or InBand [5] Version 6.8 Mediant 500 E-SBC...
  • Page 848 Mediant 500 E-SBC Parameter Description E1 QSIG [21], Single Step Transfer [4], Path T1 QSIG [23] Replacement Transfer [2], or InBand [5] T1 NI2 ISDN [10], TBCT [2] or InBand [5] T1 4ESS ISDN [11], T1 5ESS 9 ISDN [12]...
  • Page 849 Web: ISDN Transfer Defines the IP-to-ISDN Transfer Capability of the Bearer Capability Capabilities IE in ISDN Setup messages, per trunk. EMS: Transfer Capability To  [-1] Not Configured ISDN  [0] Audio 3.1 (default) CLI: isdn-xfer-cab Version 6.8 Mediant 500 E-SBC...
  • Page 850 Mediant 500 E-SBC Parameter Description  [ISDNTransferCapability_x] [1] Speech  [2] Data  [3] Audio 7 Notes:  If this parameter is not configured or is set to -1, Audio 3.1 capability is used.  The x in the ini file parameter name denotes the trunk number, where 0 is Trunk 1.
  • Page 851 This table parameter maps ISDN Q.850 Release Causes to SIP Table responses. EMS: ISDN to SIP Cause The format of the ini file table parameter is as follows: Mapping [CauseMapISDN2SIP] CLI: configure voip > gw FORMAT CauseMapISDN2SIP_Index = manipulations CauseMapISDN2SIP_IsdnReleaseCause, Version 6.8 Mediant 500 E-SBC...

  • Page 852: Answer And Disconnect Supervision Parameters

    Mediant 500 E-SBC Parameter Description CauseMapIsdn2Sip CauseMapISDN2SIP_SipResponse; [CauseMapISDN2SIP] [\CauseMapISDN2SIP] Release Cause Mapping from SIP to ISDN Table Web: Release Cause Mapping This table parameter maps SIP responses to Q.850 Release Table Causes. The format of the ini file table parameter is as follows:...
  • Page 853 The range is 10 to 28,800 (i.e., 8 hours). The default is 120 [FarEndDisconnectSilencePeri seconds. Note: For this parameter to take effect, a device reset is required. Web: Silence Detection Method Determines the silence detection method. Version 6.8 Mediant 500 E-SBC...
  • Page 854 Mediant 500 E-SBC Parameter Description  [FarEndDisconnectSilenceMeth [0] None = Silence detection option is disabled.  [1] Packets Count = According to packet count. Note: For this parameter to take effect, a device reset is required. [FarEndDisconnectSilenceThre Defines the threshold of the packet count (in percentages) below shold] which is considered silence by the device.

  • Page 855: Tone Parameters

    Web: Play Busy Tone to Tel Enables the device to play a busy or reorder tone to the PSTN after CLI: play-bsy-tone-2tel a Tel-to-IP call is released. [PlayBusyTone2ISDN]  [0] Don't Play = (Default) Immediately sends an ISDN Disconnect message. Version 6.8 Mediant 500 E-SBC...
  • Page 856 Tel side. The user-defined tone is configured when creating the PRT file, using AudioCodes DConvert utility. The tone must be assigned to the "acSpecialConditionTone" (Tone Type 21) option in DConvert. The parameter can be configured with up to 10 release codes.
  • Page 857 Web: Play Ringback Tone to Determines the playing method of the ringback tone to the trunk Trunk side, per trunk. CLI: play-rbt-to-trk  [-1] Not configured = (Default) The settings of the [PlayRBTone2Trunk_x] PlayRBTone2Tel parameter is used. Version 6.8 Mediant 500 E-SBC...
  • Page 858 Mediant 500 E-SBC Parameter Description  [0] Don't Play = When the device is configured for ISDN / CAS, it doesn't play a ringback tone. No Progress Indicator (PI) is sent to the ISDN unless the ProgressIndicator2ISDN_x parameter is configured differently.
  • Page 859 CLI: mfcr2-category National or International call, Operator or Subscriber and [R2Category] Subscriber priority. The value range is 1 to 15 (defining one of the MFC R2 tones). The default is 1. Version 6.8 Mediant 500 E-SBC...

  • Page 860: Tone Detection Parameters

    Mediant 500 E-SBC 54.10.9.2 Tone Detection Parameters The signal tone detection parameters are described in the table below. Table 54-55: Tone Detection Parameters Parameter Description EMS: DTMF Enable Enables the detection of DTMF signaling. CLI: DTMF-detector-enable  [0] = Disable [DTMFDetectorEnable] ...

  • Page 861: Metering Tone Parameters

    (that is placed in the AOC-E). Note: This parameter is applicable only to ISDN Euro trunks for sending AOC Facility messages (see Advice of Charge Services for Euro ISDN Version 6.8 Mediant 500 E-SBC...

  • Page 862: Trunk Groups And Routing Parameters

    Mediant 500 E-SBC Parameter Description on page 436). Charge Codes Table Web: Charge Codes Table This table parameter configures metering tones and their time intervals EMS: Charge Codes that the E1 trunk (Euro ISDN) sends in AOC Facility messages to the CLI: configure voip >...
  • Page 863 Web: Source IP Address Input Determines which IP address the device uses to determine CLI: src-ip-addr-input the source of incoming INVITE messages for IP-to-Tel [SourceIPAddressInput] routing.  [-1] = (Default) Auto Decision - if the IP-to-IP feature is Version 6.8 Mediant 500 E-SBC...
  • Page 864 Mediant 500 E-SBC Parameter Description enabled, this parameter is automatically set to Layer 3 Source IP. If the IP-to-IP feature is disabled, this parameter is automatically set to SIP Contact Header (1).  [0] SIP Contact Header = The IP address in the Contact header of the incoming INVITE message is used.
  • Page 865 Inbound IP Routing Table'' on page 394. Web/EMS: IP to Tel Routing Mode Determines whether to route IP calls to the Trunk Group (or CLI: ip2tel-rte-mode IP Group) before or after manipulation of the destination [RouteModeIP2Tel] number (configured in ''Configuring Source/Destination Version 6.8 Mediant 500 E-SBC...
  • Page 866 Mediant 500 E-SBC Parameter Description Number Manipulation Rules'' on page 361).  [0] Route calls before manipulation = (Default) Calls are routed before the number manipulation rules are applied.  [1] Route calls after manipulation = Calls are routed after the number manipulation rules are applied.
  • Page 867 A routing rule in the Outbound IP Routing table having the value "FAX" (case-sensitive) as the destination number is then used to re-route the call to a fax destination and the destination number manipulation Version 6.8 Mediant 500 E-SBC...
  • Page 868 Mediant 500 E-SBC Parameter Description mechanism is used to remove the "FAX" prefix before sending the fax, if required. If the initial INVITE used to establish the voice call (not fax) was already sent, a CANCEL (if not connected yet) or a BYE (if already connected) is sent to release the voice call.
  • Page 869 INVITE messages to the other members of the forking invite group. The INVITE is immediately sent to the first member. [ForkingDelayTimeForInvite] The valid value range is 0 to 40. The default is 0 (i.e., send immediately). Version 6.8 Mediant 500 E-SBC...

  • Page 870: Ip Connectivity Parameters

    Mediant 500 E-SBC 54.10.11 IP Connectivity Parameters The IP connectivity parameters are described in the table below. Table 54-58: IP Connectivity Parameters Parameter Description Web: Enable Alt Routing Tel to IP Enables the Alternative Routing feature for Tel-to-IP calls. EMS: Enable Alternative Routing ...

  • Page 871: Alternative Routing Parameters

     [2] Proxy = Proxy list is used to locate a redundant route. Note: To implement the Redundant Routing Mode mechanism, you first need to configure the parameter AltRouteCauseTEL2IP (Reasons for Alternative Routing table). Version 6.8 Mediant 500 E-SBC...
  • Page 872 Mediant 500 E-SBC Parameter Description [DisconnectCallwithPIifAlt] Defines when the device sends the IP-to-Tel call to an alternative route (if configured) when it receives an ISDN Q.931 Disconnect message from the Tel side.  [0] (Default) = The device forwards early media to the IP side if Disconnect includes PI, and disconnects the call when a Release message is received.

  • Page 873: Number Manipulation Parameters

    Source number of the original call if it is a Tel-to-IP call  Destination number of the original call if it is an IP-to-Tel call This source number can also be used as the value for the 'Source Version 6.8 Mediant 500 E-SBC...
  • Page 874 Mediant 500 E-SBC Parameter Description Prefix' field in the IP-to-Tel Destination Phone Number Manipulation table. The local IP address is used as the value for the 'Source IP Address' field. Note: This manipulation does not affect IP-to-Trunk Group routing rules.
  • Page 875 Web: Send Screening Overrides the screening indicator of the calling party's number for IP- Indicator to ISDN to-Tel ISDN calls. EMS: Screening Indicator To  [-1] Not Configured = (Default) Not configured (interworking from ISDN Version 6.8 Mediant 500 E-SBC...
  • Page 876 Mediant 500 E-SBC Parameter Description [ScreeningInd2ISDN] IP to ISDN).  [0] User Provided = user provided, not screened.  [1] User Passed = user provided, verified and passed.  [2] User Failed = user provided, verified and failed.  [3] Network Provided = network provided Note: This parameter is applicable only to digital PSTN interfaces (ISDN).
  • Page 877 Prefix To Called Number  [1] Yes = Add NPI and TON to the Called Number of ISDN Tel-to- CLI: npi-n-ton-to-cld-nb IP call. [AddNPIandTON2CalledNumb For example: After receiving a Called Number of 555, NPI of 1 and Version 6.8 Mediant 500 E-SBC...
  • Page 878 Mediant 500 E-SBC Parameter Description TON of 3, the modified number becomes 13555. This number can later be used for manipulation and routing. Web: Add NPI and TON to Determines whether the NPI and TON values are added as the prefix...
  • Page 879 This table parameter configures rules for manipulating the calling manipulations calling-name- name (caller ID) for Tel-to-IP calls. This can include modifying or map-tel2ip removing the calling name. [CallingNameMapTel2Ip] [ CallingNameMapTel2Ip ] FORMAT CallingNameMapTel2Ip_Index = CallingNameMapTel2Ip_ManipulationName, CallingNameMapTel2Ip_DestinationPrefix, CallingNameMapTel2Ip_SourcePrefix, CallingNameMapTel2Ip_CallingNamePrefix, CallingNameMapTel2Ip_SrcTrunkGroupID, CallingNameMapTel2Ip_SrcIPGroupID, CallingNameMapTel2Ip_RemoveFromLeft, CallingNameMapTel2Ip_RemoveFromRight, CallingNameMapTel2Ip_LeaveFromRight, Version 6.8 Mediant 500 E-SBC...
  • Page 880 Mediant 500 E-SBC Parameter Description CallingNameMapTel2Ip_Prefix2Add, CallingNameMapTel2Ip_Suffix2Add; [ \CallingNameMapTel2Ip ] For a detailed description of this table, see ''Configuring SIP Calling Name Manipulation'' on page 368. Destination Phone Number Manipulation for IP-to-Tel Calls Table Web: Destination Phone This table parameter manipulates the destination number of IP-to-Tel Number Manipulation Table calls.
  • Page 881 [\SourceNumberMapTel2Ip] For a detailed description of this table, see ''Configuring Source/Destination Number Manipulation'' on page 361. Redirect Number IP -to-Tel Table Web: Redirect Number IP -> This table parameter manipulates the redirect number for IP-to-Tel Version 6.8 Mediant 500 E-SBC...
  • Page 882 Mediant 500 E-SBC Parameter Description EMS: Redirect Number Map calls. The format of the ini file table parameter is as follows: IP to Tel [RedirectNumberMapIp2Tel] CLI: configure voip > gw FORMAT RedirectNumberMapIp2Tel_Index = manipulations redirect- RedirectNumberMapIp2Tel_ManipulationName, number-map-ip2tel RedirectNumberMapIp2Tel_DestinationPrefix, [RedirectNumberMapIp2Tel] RedirectNumberMapIp2Tel_RedirectPrefix,...
  • Page 883 Determines whether the received Phone-Context parameter is added Context As Prefix as a prefix to the outgoing ISDN Setup message with (for digital CLI: add-ph-cntxt-as-pref interfaces) Called and Calling numbers. [AddPhoneContextAsPrefix]  [0] Disable (default)  [1] Enable Version 6.8 Mediant 500 E-SBC...

  • Page 884: Sbc Parameters

    Mediant 500 E-SBC 54.11 SBC Parameters The SBC and CRP parameters are described in the table below. Table 54-61: SBC and CRP Parameters Parameter Description CRP-specific Parameters Web: CRP Application Enables the CRP application. EMS: Enable CPR Application  [0] Disable (default) CLI: enable-crp ...
  • Page 885  If the received header’s original value is less than this parameter's value, the header’s value is decremented before being sent on.  If the received header’s original value is greater than the Version 6.8 Mediant 500 E-SBC...
  • Page 886 Mediant 500 E-SBC Parameter Description parameter's value, the header’s value is replaced by the user-defined parameter’s value. The valid value range is 1-70. The default is 10. Web: SBC Session-Expires Defines the SBC session refresh timer (in seconds) in the CLI: sbc-sess-exp-time Session-Expires header of outgoing INVITE messages.
  • Page 887 Note: If this functionality is configured for a specific IP Profile, the settings of this global parameter is ignored for calls associated with the IP Profile. [SBCEnforceMediaOrder] Enables the device to include all previously negotiated media Version 6.8 Mediant 500 E-SBC...
  • Page 888 Mediant 500 E-SBC Parameter Description lines within the current session ('m=' line) in the SDP offer- answer exchange (RFC 3264).  [0] Disable (default)  [1] Enable For example, assume a call (audio) has been established between two endpoints and one endpoint wants to subsequently send an image in the same call session.
  • Page 889 REGISTER and SUBSCRIBE SIP messages. When the device receives such a request from a user, it forwards it to the proxy or registrar server. Upon a successful registration or subscription, the server sends a SIP 200 OK response. If the Version 6.8 Mediant 500 E-SBC...
  • Page 890 Mediant 500 E-SBC Parameter Description expiry time was unchanged by the server, the device applies this feature and changes the expiry time in the SIP 200 OK response before forwarding it to the user; otherwise, the device does not change the expiry time.
  • Page 891 RFC 5627. The public GRUU provided to the client is denoted in the SIP Contact header parameters, "pub-gruu". Public GRUU remains the same over registration expirations. On the other SBC leg communicating with the Proxy/Registrar, the device acts as a GRUU client. Version 6.8 Mediant 500 E-SBC...
  • Page 892 Mediant 500 E-SBC Parameter Description The device creates a GRUU value for each of its registered clients, which is mapped to the GRUU value received from the Proxy server. In other words, the created GRUU value is only used between the device and its clients (endpoints).
  • Page 893 For more information, see Configuring SBC IP-to-IP Routing Rules on page 487. CLI: sbc-media-sync Enables synchronization of media between two SIP user agents [EnableSBCMediaSync] when a call is established between them. Media synchronization means that the media is properly negotiated (SDP offer/answer) Version 6.8 Mediant 500 E-SBC...
  • Page 894 Mediant 500 E-SBC Parameter Description between the user agents. In some scenarios, the call is established despite the media not being synchronized. This may occur, for example, in call transfer (SIP REFER) where the media between the transfer target and transferee are not synchronized.
  • Page 895 IP destination. The format of the ini file table parameter is ip2ip-routing as follows: [IP2IPRouting] [ IP2IPRouting ] FORMAT IP2IPRouting_Index = IP2IPRouting_RouteName, IP2IPRouting_SrcIPGroupID, IP2IPRouting_SrcUsernamePrefix, IP2IPRouting_SrcHost, IP2IPRouting_DestUsernamePrefix, IP2IPRouting_DestHost, IP2IPRouting_RequestType, IP2IPRouting_MessageCondition, IP2IPRouting_ReRouteIPGroupID, IP2IPRouting_Trigger, IP2IPRouting_CallSetupRulesSetId, IP2IPRouting_DestType, IP2IPRouting_DestIPGroupID, IP2IPRouting_DestSRDID, IP2IPRouting_DestAddress, IP2IPRouting_DestPort, IP2IPRouting_DestTransportType, Version 6.8 Mediant 500 E-SBC...
  • Page 896 Mediant 500 E-SBC Parameter Description IP2IPRouting_AltRouteOptions, IP2IPRouting_GroupPolicy, IP2IPRouting_CostGroup; [ \IP2IPRouting ] For a detailed description of this table, see ''Configuring SBC IP- to-IP Routing Rules'' on page 487. SBC Alternative Routing Reasons Table Web: SBC Alternative Routing This table parameter configures the SBC Alternative Routing Reasons Reasons table.

  • Page 897: Standalone Survivability Parameters

    (up to 49 characters). You can also configure the IP address with a destination port, e.g., "10.1.2.3:5060". The default is a null string, i.e., the local IP address of the gateway. Version 6.8 Mediant 500 E-SBC...
  • Page 898 Mediant 500 E-SBC Parameter Description Web: SAS Registration Time Defines the value of the SIP Expires header that is sent in a 200 EMS: Registration Time OK response to an incoming REGISTER message when in SAS CLI: sas-registration-time 'Emergency Mode'.
  • Page 899 [4] Use Routing Table only in Normal mode = The device uses the IP-to-IP Routing table to route IP-to-IP SAS calls only when in SAS Normal mode (and is unavailable when SAS is in Emergency mode). This allows routing of SAS IP- Version 6.8 Mediant 500 E-SBC...
  • Page 900 Mediant 500 E-SBC Parameter Description to-IP calls to different destinations (and not only to the SAS Proxy Set). Web: SAS Subscribe Response Defines the SIP response upon receipt of a SUBSCRIBE CLI: sas-subscribe-resp message when SAS is in Emergency mode. For example, if this [SASSubscribeResponse] parameter is set to "200", then SAS sends a SIP 200 OK in...
  • Page 901 This table parameter configures the IP-to-IP Routing table for SAS routing rules. The format of the ini file table parameter is as follows: [IP2IPRouting] FORMAT IP2IPRouting_Index = IP2IPRouting_SrcIPGroupID, IP2IPRouting_SrcUsernamePrefix, IP2IPRouting_SrcHost, IP2IPRouting_DestUsernamePrefix, IP2IPRouting_DestHost, IP2IPRouting_DestType, IP2IPRouting_DestIPGroupID, IP2IPRouting_DestSRDID, IP2IPRouting_DestAddress, IP2IPRouting_DestPort, IP2IPRouting_DestTransportType, IP2IPRouting_AltRouteOptions; Version 6.8 Mediant 500 E-SBC...

  • Page 902: Ip Media Parameters

    Mediant 500 E-SBC Parameter Description [\IP2IPRouting] For example: IP2IPRouting 1 = -1, *, *, *, *, 0, -1, -1, , 0, -1, 0; 54.13 IP Media Parameters The IP media parameters are described in the table below. Table 54-63: IP Media Parameters...
  • Page 903 [11] 11 = 4.00 dB/sec  [12] 12 = 4.50 dB/sec  [13] 13 = 5.00 dB/sec  [14] 14 = 5.50 dB/sec  [15] 15 = 6.00 dB/sec  [16] 16 = 7.00 dB/sec Version 6.8 Mediant 500 E-SBC...
  • Page 904 Mediant 500 E-SBC Parameter Description  [17] 17 = 8.00 dB/sec  [18] 18 = 9.00 dB/sec  [19] 19 = 10.00 dB/sec  [20] 20 = 11.00 dB/sec  [21] 21 = 12.00 dB/sec  [22] 22 = 13.00 dB/sec ...
  • Page 905 Defines the number of consecutive patterns to trigger the pattern detection event. The valid range is 0 to 31. The default is 5. Note: For this parameter to take effect, a device reset is required. Version 6.8 Mediant 500 E-SBC...

  • Page 906: Services

    Mediant 500 E-SBC 54.14 Services 54.14.1 SIP-based Media Recording Parameters The SIP-based media recording parameters are described in the table below. Table 54-64: SIP-based Media Recording Parameters Parameter Description Web: SIP Recording Application Enables the SIP-based Media Recording feature: CLI: configure voip/services sip- ...

  • Page 907: Radius And Ldap Parameters

    CLI: enable  [1] Enable [EnableRADIUS] Note: For this parameter to take effect, a device reset is required. Web: Accounting Server Defines the IP address of the RADIUS accounting server. IP Address CLI: accounting-server-ip [RADIUSAccServerIP] Version 6.8 Mediant 500 E-SBC...
  • Page 908 Mediant 500 E-SBC Parameter Description Web: Accounting Port Defines the port of the RADIUS accounting server. CLI: accounting-port The default is 1646. [RADIUSAccPort] Web/EMS: RADIUS Determines when the RADIUS accounting messages are sent to the Accounting Type RADIUS accounting server.

  • Page 909: Ldap Parameters

    LDAP Parameters Parameter Description Web: LDAP Service Enables the LDAP feature. CLI: configure  [0] Disable (default) voip/ldap/enable  [1] Enable [LDAPServiceEnable] Note: For this parameter to take effect, a device reset is required. Version 6.8 Mediant 500 E-SBC...
  • Page 910 Mediant 500 E-SBC Parameter Description CLI: search-dns-in-parallel Defines the method of how the device queries the DN object within [LDAPSearchDNsinParalle each LDAP server.  [0] Sequential = (Default) The query is done in each DN object, one by one, until a result is returned.
  • Page 911 LDAP Configuration Table Web: LDAP Configuration Defines the LDAP servers. Table [ LdapConfiguration ] CLI: configure voip > ldap > FORMAT LdapConfiguration_Index = ldap-configuration LdapConfiguration_LdapConfServerIp, [LdapConfiguration] LdapConfiguration_LdapConfServerPort, LdapConfiguration_LdapConfServerMaxRespondTime, LdapConfiguration_LdapConfServerDomainName, LdapConfiguration_LdapConfPassword, LdapConfiguration_LdapConfBindDn, LdapConfiguration_LdapConfInterfaceType, LdapConfiguration_Type, LdapConfiguration_MngmAuthAtt, LdapConfiguration_ConnectionStatus; Version 6.8 Mediant 500 E-SBC...

  • Page 912: Least Cost Routing Parameters

    Mediant 500 E-SBC Parameter Description [ \LdapConfiguration ] For a detailed description of this table, see 'Configuring LDAP Servers' on page 204. LDAP Server Search DN Table Web: LDAP Search DN Defines the full base path (i.e., distinguished name / DN) to the Table objects in the AD where the query is done, per LDAP server.

  • Page 913: Call Setup Rules Parameters

    [CallSetupRules] [ CallSetupRules ] FORMAT CallSetupRules_Index = CallSetupRules_RulesSetID, CallSetupRules_AttributesToQuery, CallSetupRules_AttributesToGet, CallSetupRules_RowRole, CallSetupRules_Condition, CallSetupRules_ActionSubject, CallSetupRules_ActionType, CallSetupRules_ActionValue; [ \CallSetupRules ] Note: For a detailed description of this table, see ''Configuring Call Setup Rules'' on page 232. Version 6.8 Mediant 500 E-SBC...
  • Page 914 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10437...

  • Page 915: Sbc And Dsp Channel Capacity

    The capacity figures listed in the table below are accurate at the time of publication of this document. However, these figures may change due to a later software update. For the latest figures, please contact your AudioCodes sales representative. •...

  • Page 916: Channel Capacity And Capabilities

    Mediant 500 E-SBC 55.2 Channel Capacity and Capabilities The SBC session capacity and DSP channel capacity are shown in the tables below. Table 55-2: SBC Session Capacity and Capabilities for Mediant 500 E-SBC Wideband Coders Hardware DSP Channels Max. SBC Sessions...

  • Page 917: Technical Specifications

    The device's technical specifications are listed in the table below. Notes: • All specifications in this document are subject to change without prior notice. • The compliance and regulatory information can be downloaded from AudioCodes Web site at http://www.audiocodes.com/library. Table 56-1: Technical Specifications Function Specification...
  • Page 918 Low latency, unprocessed payload transfer Media De-anchoring Hair-pinning of local calls to avoid unnecessary media delays and bandwidth consumption Voice Quality Monitoring AudioCodes Session Experience Manager (SEM) Quality of Experience Access control and media quality enhancements based on QoE and bandwidth utilization Test agent...
  • Page 919 User's Manual 56. Technical Specifications This page is intentionally left blank. Version 6.8 Mediant 500 E-SBC...
  • Page 920 User's Manual Ver. 6.8 www.audiocodes.com...

Table of Contents