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

AudioCodes Mediant 1000B User Manual

Media gateway & enterprise session border controller (e-sbc)
Hide thumbs Also See for Mediant 1000B:
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
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
Table of Contents

Advertisement

Quick Links

Download this manual See also: User Manual, Quick Manual
User's Manual
Mediant 1000B
Media Gateway & Enterprise Session Border
Controller (E-SBC)
Version 7.0

Advertisement

Table of Contents
loading

Related Manuals for AudioCodes Mediant 1000B

Summary of Contents for AudioCodes Mediant 1000B

  • Page 1 User's Manual Mediant 1000B Media Gateway & Enterprise Session Border Controller (E-SBC) Version 7.0...

  • Page 3: Table Of Contents

    Viewing the Home Page ..................68 6.2.1 Assigning a Port Name ....................71 Configuring Web User Accounts ................71 6.3.1 Basic User Accounts Configuration .................73 6.3.2 Advanced User Accounts Configuration ..............75 Displaying Login Information upon Login .............. 79 Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 4 Mediant 1000B Gateway and E- SBC Configuring Web Security Settings ............... 79 6.5.1 Configuring Secured (HTTPS) Web ................79 6.5.2 Configuring Web Session and Access Settings ............80 Web Login Authentication using Smart Cards............81 Configuring Web and Telnet Access List .............. 81 CLI-Based Management ..................
  • Page 5 12.11 Robust Receipt of Media Streams by Media Latching ......... 159 12.12 Multiple Routers Support ..................159 13 Security ......................161 13.1 Configuring Firewall Settings ................161 13.2 Configuring General Security Settings ..............165 13.3 Intrusion Detection System ................. 166 Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 6 Mediant 1000B Gateway and E- SBC 13.3.1 Enabling IDS ......................167 13.3.2 Configuring IDS Policies ..................167 13.3.3 Assigning IDS Policies ...................171 13.3.4 Viewing IDS Alarms ....................173 14 Media ........................ 175 14.1 Configuring Voice Settings ................. 175 14.1.1 Configuring Voice Gain (Volume) Control .............175 14.1.2 Silence Suppression (Compression) ..............176...
  • Page 7 15.8.2.2 Adding ELINs to the Location Information Server ........290 15.8.2.3 Passing Location Information to the PSTN Emergency Provider ..291 15.8.3 AudioCodes ELIN Device for Lync Server E9-1-1 Calls to PSTN ......292 15.8.3.1 Detecting and Handling E9-1-1 Calls .............293 15.8.3.2 Pre-empting Existing Calls for E9-1-1 Calls ...........295 15.8.3.3 PSAP Callback to Lync Clients for Dropped E9-1-1 Calls .....295...
  • Page 8 Mediant 1000B Gateway and E- SBC 15.8.3.4 Selecting ELIN for Multiple Calls within Same ERL .......296 15.8.3.5 Location Based Emergency Routing ............297 15.8.4 Configuring AudioCodes ELIN Device ..............297 15.8.4.1 Enabling the E9-1-1 Feature ..............297 15.8.4.2 Configuring the E9-1-1 Callback Timeout ..........297 15.8.4.3 Configuring the SIP Release Cause Code for Failed E9-1-1 Calls ..298...
  • Page 9 23.8.2.2 Fixed Mapping of ISDN Release Reason to SIP Response ....477 23.8.3 Configuring ISDN-to-ISDN Release Cause Mapping ..........479 23.8.4 Reason Header ......................481 23.8.5 Mapping PSTN Release Cause to SIP Response ..........481 23.9 Numbering Plans and Type of Number ............... 482 Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 10 Mediant 1000B Gateway and E- SBC 24 Routing ......................483 24.1 Configuring General Routing Parameters ............483 24.2 Configuring Tel-to-IP Routing Rules ..............483 24.3 Configuring IP-to-Trunk Group Routing Rules ............ 494 24.4 Configuring a Gateway Routing Policy Rule ............499 24.5 IP Destinations Connectivity Feature ..............
  • Page 11 27.14.5 FXS Gateway Configuration ..................579 27.14.6 FXO Gateway Configuration ..................580 Session Border Controller Application..............583 28 SBC Overview ....................585 28.1 Feature List ......................585 28.2 B2BUA and Stateful Proxy Operating Modes............586 Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 12 Mediant 1000B Gateway and E- SBC 28.3 Call Processing of SIP Dialog Requests ............. 589 28.4 User Registration ....................591 28.4.1 Initial Registration Request Processing ..............591 28.4.2 Classification and Routing of Registered Users ............592 28.4.3 General Registration Request Processing ............593 28.4.4 Registration Refreshes ..................593...
  • Page 13 39 CRP Configuration ..................697 39.1 Enabling the CRP Application ................697 39.2 Configuring Call Survivability Mode ..............698 39.3 Pre-Configured IP Groups .................. 699 39.4 Pre-Configured IP-to-IP Routing Rules ............... 700 Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 14 Mediant 1000B Gateway and E- SBC 39.4.1 Normal Mode ......................700 39.4.2 Emergency Mode ....................701 39.4.3 Auto Answer to Registrations ................701 39.5 Configuring PSTN Fallback ................702 Maintenance ......................703 40 Basic Maintenance ..................705 40.1 Resetting the Device ..................705 40.2 Remotely Resetting Device using SIP NOTIFY ..........707 40.3 Locking and Unlocking the Device ..............
  • Page 15 49.2 Viewing Trunk Utilization ..................782 49.3 Viewing Quality of Experience ................783 49.4 Viewing Average Call Duration ................784 50 VoIP Status ...................... 787 50.1 Viewing Trunks & Channels Status ..............787 Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 16 52.2 Configuring Syslog ..................... 840 52.2.1 Syslog Message Format ..................840 52.2.1.1 Event Representation in Syslog Messages..........842 52.2.1.2 Identifying AudioCodes Syslog Messages using Facility Levels....844 52.2.1.3 Syslog Fields for Answering Machine Detection (AMD) ......845 52.2.1.4 SNMP Alarms in Syslog Messages ............845 52.2.2 Configuring Web User Activities to Report to Syslog ..........846...
  • Page 17 59.3.4 Resource Allocation Indication Parameters............914 59.4 Security Parameters ................... 915 59.4.1 General Security Parameters ................916 59.4.2 HTTPS Parameters ....................917 59.4.3 SRTP Parameters ....................918 59.4.4 TLS Parameters .....................919 59.4.5 SSH Parameters ....................921 59.4.6 IDS Parameters .....................923 Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 18 Mediant 1000B Gateway and E- SBC 59.4.7 OCSP Parameters ....................924 59.5 Quality of Experience Parameters ..............925 59.6 Control Network Parameters ................928 59.6.1 IP Group, Proxy, Registration and Authentication Parameters ......928 59.6.2 Network Application Parameters ................939 59.7 General SIP Parameters ..................942 59.8 Coders and Profile Parameters................
  • Page 19 59.14.4 HTTP-based Services ..................1136 59.14.5 HTTP Proxy Parameters..................1137 60 SBC and DSP Channel Capacity ..............1139 60.1 Signaling-Media Sessions & User Registrations ..........1139 60.2 Mediant 1000B Series ..................1140 60.2.1 Analog (FXS/FXO) Interfaces ................1141 60.2.2 BRI Interfaces ......................1142 60.2.3 E1/T1 Interfaces ....................1143 60.2.4 Media Processing Interfaces ................1144...
  • Page 20 Mediant 1000B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-27044...

  • Page 21: Weee Eu Directive

    This document is subject to change without notice. Date Published: September-25-2016 Trademarks All rights reserved. AudioCodes, AC, HD VoIP, HD VoIP Sounds Better, IPmedia, Mediant, MediaPack, What’s Inside Matters, OSN, SmartTAP, User Management Pack, VMAS, VoIPerfect, VoIPerfectHD, Your Gateway To VoIP, 3GX, VocaNom, AudioCodes One Voice and CloudBond are trademarks or registered trademarks of AudioCodes Limited.

  • Page 22: Related Documentation

    Mediant 1000B Gateway and E- SBC Related Documentation Manual Name SIP CPE Release Notes Mediant 1000B Gateway and E-SBC Hardware Installation Manual Complementary Guides CLI Reference Guide CPE Configuration Guide for IP Voice Mail SNMP User's Guide SBC Design Guide...
  • Page 23 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 24 Mediant 1000B Gateway and E- SBC LTRT Description changed and option names); ProxySet_DNSResolveMethod (new optional value of 3); IP2IPRouting_DestType; IP2IPRouting_DestIPGroupName; xferPrefix; TrunkLifeLineType; EnableSBCMediaSync. 27038 New features: HTTP-based Proxy Services; License Pool Manager; Multi-Line Extensions and Supplementary Services section was updated (ISDNSuppServ_PhoneNumber and [ISDNSuppServ_LocalPhoneNumber were added).
  • Page 25 AUPDCliScriptURL; MaxGeneratedRegistersRate; GeneratedRegistersInterval; UseFacilityInRequest; GWRoutingServer; EnableNonCallCdr. 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 26 Mediant 1000B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-27044...

  • Page 27: Introduction

    Product Overview AudioCodes' Mediant 1000B Gateway and E-SBC (hereafter referred to as device) is a member of AudioCodes family of Enterprise Session Border Controllers (E-SBC), enabling connectivity and security between small medium businesses (SMB) and service providers' VoIP networks.

  • Page 28: Typographical Conventions

    Mediant 1000B Gateway and E- SBC Note: For maximum call capacity figures, see 'SBC and DSP Channel Capacity' on page 1139. The device also provides up to 6 Ethernet ports (2 ports on the CRMX module and 4 ports on the LAN Expansion module). These ports operate in port-pair redundancy, providing up to 3 port-pair groups.

  • Page 29: Getting Familiar With Configuration Concepts And Terminology

    The Media Realm can be associated with the SIP entity, by assigning the Media Realm to the IP Group of the SIP entity, or by assigning it to the SIP Interface associated with the SIP entity. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 30 Mediant 1000B Gateway and E- SBC Configuration Terms Description The SRD is a logical representation of your entire SIP-based VoIP network (Layer 5) containing groups of SIP users and servers. The SRD is in effect, the foundation of your configuration to which all other previously mentioned configuration entities are associated.
  • Page 31 401) is typically relevant for INVITE messages forwarded by the device to a "serving" IP Group. Registration is for REGISTER messages, which are initiated by the device on behalf of the "serving" SIP entity. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 32 Mediant 1000B Gateway and E- SBC The associations between the configuration entities are summarized in the following figure: Figure 1-1: Association of Configuration Entities The main configuration entities and their involvement in the call processing is summarized in following figure. The figure is used only as an example to provide basic understanding of the configuration terminology.

  • Page 33: Gateway Application

    The Media Realm can be associated with the SIP entity, by assigning the Media Realm to the IP Group of the SIP entity, or by assigning it to the SIP Interface associated with the SIP entity. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 34 Mediant 1000B Gateway and E- SBC Configuration Terms Description SRDs The SRD is a logical representation of your entire VoIP network. The SRD is in effect, the foundation of your configuration to which all other previously mentioned configuration entities are associated.
  • Page 35 The figure is used only as an example to provide basic understanding of the configuration terminology. Depending on configuration and network topology, the call process may include additional stages or a different order of stages. Figure 1-3: Gateway Configuration Terminology for Call Processing Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 36 Mediant 1000B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-27044...

  • Page 37: Getting Started With Initial Connectivity

    Part I Getting Started with Initial Connectivity...

  • Page 39: 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 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 40 Mediant 1000B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-27044...

  • Page 41: Default Oamp 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 vlan 1 Interface Name O+M+C Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 42 Mediant 1000B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-27044...

  • Page 43: 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 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 44 Mediant 1000B Gateway and 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 127.

  • Page 45: Cli

    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 Configure the IP address: (network-if-0)# ip-address <IP address> Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 46 Mediant 1000B Gateway and E- SBC 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: (config-voip)# exit...

  • Page 47: Management Tools

    Part II Management Tools...

  • Page 49: 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 881. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 50 Mediant 1000B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-27044...

  • Page 51: Web-Based Management

    ® 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 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 52: Accessing The Web Interface

    Mediant 1000B Gateway and 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 51). In the Web browser, specify the OAMP IP address of the device (e.g., http://10.1.10.10);...

  • Page 53: Areas Of The Gui

    'Navigation Tree' on page 54. 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 57. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 54: Toolbar Description

    Mediant 1000B Gateway and 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 708).

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

    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 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 56: Showing / Hiding The Navigation Pane

    Mediant 1000B Gateway and 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 57: 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 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 58 Mediant 1000B Gateway and 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 59: Modifying And Saving Parameters

    Thus, to ensure parameter changes (whether on-the-fly or not) are retained, save ('burn') them to the device's non-volatile memory, i.e., flash (see 'Saving Configuration' on page 708). Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 60: Working With Tables

    Mediant 1000B Gateway and E- SBC If you enter an invalid value (e.g., not in the range of permitted values) and then click 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...

  • Page 61: Table Toolbar Description

    'Index' column; otherwise, the button is grayed out. For sorting tables, see 'Sorting Tables by Column' on page 63.  The button appears only in certain tables. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 62: Toggling Display Mode Of Table Dialog Boxes

    Mediant 1000B Gateway and E- SBC Button Name Moves a selected row one index up. The index number of the row changes according to its new position in the table. The row that previously occupied the index row and all rows below it are moved one index down in the table.

  • Page 63: Searching Table Entries

    Index column in ascending order (e.g., 1, 2, and 3), you can sort the rows by Index column in descending order (e.g., 3, 2, and 1). By default, most tables are sorted by Index column in ascending order. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 64: Searching For Configuration Parameters

    Mediant 1000B Gateway and E- SBC  To sort table rows by column: Click the heading name of the column that you want to sort the table rows by; the up- down arrows appear alongside the heading name and the up button is bolded (see...
  • Page 65 Table 6-6: Search Description Item # Description Search field for entering search key and Search button for activating the search process. Search results listed in Navigation pane. Found parameter, highlighted on relevant Web page Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 66: Creating A Login Welcome Message

    Mediant 1000B Gateway and E- SBC 6.1.9 Creating a Login Welcome Message You can create a Welcome message box that is displayed on the Web Login page. The figure below displays an example of a Welcome message: Figure 6-15: User-Defined Web Welcome Message after Login To enable and create a Welcome message, use the WelcomeMessage table ini file parameter, as described in the table below.

  • Page 67: Getting Help

    Instead of clicking the Help button for each page you open, you can open it once for a page and then simply leave it open. Each time you open a different page, the Help topic pertaining to that page is automatically displayed. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 68: Logging Off The Web Interface

    Mediant 1000B Gateway and E- SBC 6.1.11 Logging Off the Web Interface The following procedure describes how to log off the Web interface.  To log off the Web interface: On the toolbar, click the Log Off icon; the following confirmation message box...
  • Page 69 (red): Module failure and "Failure" is displayed Port (trunk or channel) status icon. Icon Trunk Description Channel Description (Digital Module) (Analog Module) Disable: Trunk not configured (not Idle: Channel is currently on- in use) hook (grey) Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 70 Mediant 1000B Gateway and E- SBC Item # Description Active - OK: Trunk synchronized Call Connected: Active RTP stream (green) RAI Alarm: Remote Alarm Indication (RAI), also known as the (yellow) Yellow Alarm LOS / LOF Alarm: Loss due to LOS...

  • Page 71: Assigning A Port Name

    Master user. Note: At least one Security Administrator user must exits. Master Read / write privileges for all pages. Can create all user Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 72 Mediant 1000B Gateway and E- SBC Numeric User Level Representation in Privileges RADIUS types, including additional Master users and Security Administrators. It can delete all users except the last Security Administrator. Administrator Read / write privileges for all pages, except security- related pages (read-only).

  • Page 73: 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 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 74 Mediant 1000B Gateway and 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).

  • Page 75: 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-19: Web Users Table Page Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 76 Mediant 1000B Gateway and E- SBC Click Add; the following dialog box is displayed: Figure 6-20: Web Users Table - Add Record Dialog Box Configure a Web user according to the parameters described in the table below. Click Add, and then save ("burn") your settings to flash memory.
  • Page 77 The valid value is 0 to 100000. A value of 0 means no timeout. The default value is according to the settings of the WebSessionTimeout global parameter (see 'Configuring Web Session and Access Settings' on page 80). Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 78 Mediant 1000B Gateway and E- SBC Parameter Description Block Duration Defines the duration (in seconds) for which the user is blocked when the user exceeds a user-defined number of failed login attempts. This block-duration is configured by the 'Deny Access On Fail Count' parameter (see 'Configuring Web Session and Access Settings' on page 80).

  • Page 79: Displaying Login Information Upon Login

    From the 'Secured Web Connection (HTTPS)' drop-down list, select HTTPS Only. To enable two-way authentication whereby both management client and server are authenticated using X.509 certificates, from the 'Requires Client Certificates for HTTPS connection' drop-down list, select Enable. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 80: Configuring Web Session And Access Settings

    Mediant 1000B Gateway and E- SBC In the 'HTTPS Cipher String' field, enter the cipher string for HTTPS (in OpenSSL cipher list format). Click Submit, and then reset the device with a burn-to-flash for your settings to take effect. For more information on secured Web-based management including TLS certificates, see 'TLS for Remote Device Management' on page 119.

  • Page 81: Web Login Authentication Using Smart Cards

    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.  To log in to the Web interface using CAC: Insert the Common Access Card into the card reader.
  • Page 82 Mediant 1000B Gateway and E- SBC To add an authorized IP address, in the 'Add an authorized IP address' field, enter the required IP address, and then click Add New Entry; the IP address you entered is added as a new entry to the Web & Telnet Access List table.

  • Page 83: Cli-Based Management

    Password: <Enable mode password> The Enable mode prompt is "#". Note: The default password for accessing the Enable mode is "Admin" (case- sensitive). To change the password, use the CLIPrivPass ini file parameter. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 84: Using Cli Shortcuts

    Mediant 1000B Gateway and 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:...

  • Page 85: Common Cli Commands

    Displays the configuration of current configuration set. help Displays a short help how-to string. history Displays a list of previously run commands. list Displays the available command list of the current command-set. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 86: Configuring Tables Through Cli

    Mediant 1000B Gateway and E- SBC Command Description | <filter> 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>...

  • Page 87: Understanding Cli Error Messages

    (see 'Creating a Login Welcome Message' on page 66).  To enable Telnet: Open the Telnet/SSH Settings page (Configuration tab > System menu > Management > Telnet/SSH Settings). Version 7.0 Mediant 1000B Gateway and E- SBC...

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

    Mediant 1000B Gateway and E- SBC From the 'Embedded Telnet Server' drop-down list, select Enable Unsecured or Enable Secured (i.e, SSL). In the 'Telnet Server TCP Port' field, enter the port number for the embedded Telnet server. Click Submit, and then reset the device with a burn-to-flash for your settings to take effect.
  • Page 89 Under the 'Authentication parameters' group, click Browse and then locate the private key file that you created and saved in Step 4. Connect to the device with SSH using the username "Admin"; RSA key negotiation occurs automatically and no password is required. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 90: Configuring Maximum Telnet/Ssh Sessions

    Mediant 1000B Gateway and E- SBC  To configure RSA public keys for Linux (using OpenSSH 4.3): Run the following command to create a new key in the admin.key file and to save the public portion to the admin.key.pub file: ssh-keygen -f admin.key -N ""...

  • Page 91: Viewing Current Cli Sessions

    The current session from which this show command was run is displayed with an asterisk (*). Note: The device can display management sessions of up to 24 hours. After this time, the duration counter is reset. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 92: Terminating A User's Cli Session

    Mediant 1000B Gateway and E- SBC Terminating a User's CLI Session You can terminate users that are currently logged in to the device's CLI. This applies to users logged in to the CLI through RS-232 (console), Telnet, or SSH. ...

  • Page 93: 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 94: Configuring Snmp Community Strings

    Mediant 1000B Gateway and E- SBC Configuring SNMP Community Strings The SNMP Community String page lets you configure up to five read-only and up to five read-write SNMP community strings and to configure the community string that is used for sending traps.

  • Page 95: Configuring Snmp Trap Destinations

    Open the SNMP Trap Destinations table (Configuration tab > System menu > Management > SNMP > SNMP Trap Destinations). Figure 8-2: SNMP Trap Destinations Table Configure the SNMP trap manager parameters according to the table below. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 96 Mediant 1000B Gateway and E- SBC Select the check box corresponding to the SNMP Manager that you wish to enable. Click Submit. Notes: • Only row entries whose corresponding check boxes are selected are applied when clicking Submit; otherwise, settings revert to their defaults.

  • Page 97: Configuring Snmp Trusted Managers

    You can also configure it through ini file (SNMPUsers) or CLI (configure system > snmp v3-users).  To configure an SNMP v3 user: Open the SNMPv3 Users table (Configuration tab > System menu > Management > SNMP > SNMP V3 Users). Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 98 Mediant 1000B Gateway and E- SBC Click Add; the following dialog box appears: Figure 8-4: SNMPv3 Users Table - Add Row Dialog Box Configure the SNMP V3 parameters according to the table below. Click Add, and then save ("burn") your settings to flash memory.
  • Page 99 Group The group with which the SNMP v3 user is associated.  group [0] Read-Only (default)  [1] Read-Write [SNMPUsers_Group]  [2] Trap Note: All groups can be used to send traps. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 100 Mediant 1000B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-27044...

  • Page 101: 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 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 102 Mediant 1000B Gateway and 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 "="...

  • Page 103: General Ini File Formatting Rules

    Creating a new ini file that includes only updated configuration: Open a text file editor such as Notepad. Add only the required parameters and their settings. Save the file with the ini file extension name (e.g., myconfiguration.ini). Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 104: 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 105: 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 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 106: Ini Viewer And Editor Utility

    Mediant 1000B Gateway and 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...

  • Page 107: General System Settings

    Part III General System Settings...

  • Page 109: Configuring Ssl/Tls Certificates

    (CSR)  Trusted root certificate authority (CA) store (for validating certificates) When the device establishes a TLS connection (handshake) with a SIP user agent (UA), the TLS Context is determined as follows: Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 110 Mediant 1000B Gateway and E- SBC  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 TLS ('Transport Type' parameter is set to TLS), the TLS Context assigned to the Proxy Set is used.
  • Page 111 [5] TLSv1.0 and TLSv1.2 = Only TLS 1.0 and TLS 1.2.  [6] TLSv1.1 and TLSv1.2 = Only TLS 1.1 and TLS 1.2.  [7] TLSv1.0 TLSv1.1 and TLSv1.2 = Only TLS 1.0, TLS 1.1 and TLS 1.2 (excludes SSL 3.0). Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 112 Mediant 1000B Gateway and E- SBC Parameter Description Ciphers Server Defines the supported cipher suite for the TLS server (in OpenSSL cipher list format). ciphers-server For valid values, refer to URL [TLSContexts_Server http://www.openssl.org/docs/apps/ciphers.html. The default is "AES:RC4". CipherString] For example, use "ALL" for all ciphers suites (e.g., for ARIA encryption for TLS).

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

    Fill in the rest of the request fields according to your security provider's instructions. Click the Create CSR button; a textual certificate signing request is displayed in the area below the button: Figure 10-2: Certificate Signing Request Group Version 7.0 Mediant 1000B Gateway and E- SBC...

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

    Mediant 1000B Gateway and E- SBC 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). 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:...

  • Page 115: 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: Version 7.0 Mediant 1000B Gateway and E- SBC...

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

    Mediant 1000B Gateway and E- SBC • • 1024 (default) • 2048 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.

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

    For the device to trust a whole chain of certificates per TLS Context, you need to add them to the device's Trusted Certificates Store, as described below. Note: Only Base64 (PEM) encoded X.509 certificates can be loaded to the device. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 118: Configuring Mutual Tls Authentication

    Mediant 1000B Gateway and E- SBC  To import certificates into device's Trusted Root Certificate Store: Open the TLS Contexts page (Configuration tab > System menu > TLS Contexts). In the table, select the required TLS Context index row, and then click the TLS Context Trusted Root Certificates button, located below the table;...

  • Page 119: Tls For Remote Device Management

    - the authentication is performed using the X.509 digital signature).  If the user does not have a client certificate from a listed CA or does not have a client certificate, the connection is rejected. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 120: Configuring Tls Server Certificate Expiry Check

    Mediant 1000B Gateway and E- SBC Notes: • The process of installing a client certificate on your PC is beyond the scope of this document. For more information, refer to your operating system documentation, and/or consult your security administrator. •...

  • Page 121: Date And Time

    Application Settings), and then scroll down to the 'NTP Settings' group: Figure 11-2: NTP Authentication Parameters on Application Settings Page Configure NTP message authentication: • In the 'NTP Authentication Key Identifier' field, configure the NTP authentication key identifier. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 122: Configuring Date And Time Manually

    Mediant 1000B Gateway and E- SBC • In the 'NTP Authentication Secret Key' field, configure the secret authentication key shared between the device and the NTP server. Verify that the device has received the correct date and time from the NTP server. The date and time is displayed in the 'UTC Time' read-only field on the Time and Date page.

  • Page 123: Configuring The Time Zone

    Figure 11-5: Configuring DST From the 'Daylight Saving Time' (DayLightSavingTimeEnable) drop-down list, select Enable. From the 'DST Mode' drop-down list, select the range type for configuring the start and end dates for DST: Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 124 Mediant 1000B Gateway and E- SBC • Day of year: The range is configured by exact date (day number of month), for example, from March 30 to October 30. If 'DST Mode' is set to Day of year, in the 'Start Time' (DayLightSavingTimeStart) and 'End Time' (DayLightSavingTimeEnd) drop-down lists, configure the period for which DST is relevant.

  • Page 125: General Voip Configuration

    Part IV General VoIP Configuration...

  • Page 127: Network

    _0_2 00:1e:67:11:7c:28 100Mbps FULL DOWN Note: All the LAN ports (including those of the optional SWX Expansion module) have the same MAC address. This is the MAC address of the device itself. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 128 Mediant 1000B Gateway and E- SBC The following procedure describes how to configure the Ethernet ports through the Web interface. You can also configure it through ini file (PhysicalPortsTable) or CLI (configure voip > physical-port).  To configure the physical Ethernet ports: Open the Physical Ports Settings page (Configuration tab >...

  • Page 129: Configuring Ethernet Port Groups

    Equipment connected to different physical ports is not accessible to one another; the only connection between them can be established by cross connecting them with media streams (VoIP calls). Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 130 Mediant 1000B Gateway and E- SBC Note: The SWX LAN Expansion module is a customer-ordered item. For more information, contact your AudioCodes sales representative. 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 127.
  • Page 131 Note: Before you can re-assign a port to a different Ethernet Group, you [EtherGroupTable_Me must first remove the port from its current Ethernet Group. To remove the mber2] port, either set this field to None or to a different port. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 132: Configuring Underlying Ethernet Devices

    Mediant 1000B Gateway and E- SBC 12.3 Configuring Underlying Ethernet Devices The Ethernet Device table lets you configure up to 16 Ethernet Devices. An Ethernet Device represents a Layer-2 bridging device and is assigned a VLAN ID and an Ethernet Port Group.
  • Page 133 ('Underlying Device' field - see 'Configuring IP Network Interfaces' on page [DeviceTable_Device 135) and/or with a static route in the Static Route table ('Device Name' field Name] - see 'Configuring Static IP Routing' on page 142). Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 134 Mediant 1000B Gateway and E- SBC Parameter Description Tagging Defines VLAN tagging per Ethernet Device.  tagging [0] Untagged = (Default of pre-configured Ethernet Device) The Ethernet Device accepts untagged packets as well as packets with the [DeviceTable_Taggin same VLAN ID as configured for the Ethernet Device. Incoming untagged packets are assigned the VLAN ID of the Ethernet Device.

  • Page 135: Configuring Ip Network Interfaces

    For configuring Quality of Service (QoS), see 'Configuring the QoS Settings' on page 146.  Default Gateway: Traffic from this interface destined to a subnet that does not meet any of the routing rules (local or static) are forwarded to this gateway Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 136 Mediant 1000B Gateway and E- SBC  Primary and secondary domain name server (DNS) addresses (optional)  Underlying Ethernet Device: Layer-2 bridging device and assigned a VLAN ID. As the Ethernet Device is associated with an Ethernet Port Group, this is useful for setting trusted and un-trusted networks on different physical Ethernet ports.
  • Page 137 The prefix length for IPv4 must be set to a value from 0 to 30. The prefix length for IPv6 must be set to a value from 0 to 64. Default Gateway Defines the IP address of the default gateway for the interface. When Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 138 Mediant 1000B Gateway and E- SBC Parameter Description gateway traffic is sent from this interface to an unknown destination (i.e., not in the same subnet and not defined for any static routing rule), it is forwarded to [InterfaceTable_Gatew this default gateway.

  • Page 139: Assigning Ntp Services To Application Types

    Syslog server and falls back to a "safe mode", using a single interface without VLANs. Ensure that you view the Syslog messages that the device sends in system startup to see if any errors occurred. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 140: Networking Configuration Examples

    Mediant 1000B Gateway and E- SBC 12.4.3 Networking Configuration Examples This section provides configuration examples of networking interfaces. 12.4.3.1 One VoIP Interface for All Applications This example describes the configuration of a single VoIP interface for all applications: Interface table: Configured with a single interface for OAMP, Media and Control:...

  • Page 141: Voip Interfaces For Combined Application Types

    For packets sent with DiffServ value of 46, set VLAN priority to 6 ♦ For packets sent with DiffServ value of 40, set VLAN priority to 6 ♦ For packets sent with DiffServ value of 26, set VLAN priority to 4 Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 142: Voip Interfaces With Multiple Default Gateways

    Mediant 1000B Gateway and E- SBC ♦ For packets sent with DiffServ value of 10, set VLAN priority to 2 • Layer-3 QoS values are assigned: ♦ For Media Service class, the default DiffServ value is set to 46 ♦...
  • Page 143 Destination Defines the IP address of the destination host/network. The destination can be a single host or a whole subnet, depending on destination the prefix length configured for this routing rule. [StaticRouteTable_Destination] Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 144: Configuration Example Of Static Ip Routes

    Mediant 1000B Gateway and E- SBC Parameter Description Prefix Length Defines the Classless Inter-Domain Routing (CIDR)-style representation of a dotted-decimal subnet notation of the prefix-length destination host/network. The CIDR-style representation uses a [StaticRouteTable_PrefixLengt suffix indicating the number of bits that are set in the dotted- decimal format.

  • Page 145: Troubleshooting The Routing Table

    To restore connectivity, the device must be accessed locally from the OAMP subnet and the required routes be configured. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 146: Configuring Quality Of Service

    Mediant 1000B Gateway and E- SBC 12.6 Configuring Quality of Service The QoS Settings page lets you configure Layer-2 and Layer-3 Quality of Service (QoS). Differentiated Services (DiffServ) is an architecture providing different types or levels of service for IP traffic. DiffServ (according to RFC 2474), prioritizes certain traffic types based on priority, accomplishing a higher-level QoS at the expense of other traffic types.
  • Page 147 Differentiated Services Defines a DiffServ value. The valid value is 0 to 63. diff-serv [DiffServToVlanPriority_DiffServ] VLAN Priority Defines the VLAN priority level. vlan-priority The valid value is 0 to 7. [DiffServToVlanPriority_VlanPrior ity] Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 148: Configuring Icmp Messages

    Mediant 1000B Gateway and E- SBC Under the Differentiated Services group, configure DiffServ (Layer-3 QoS) values per CoS. Figure 12-5: QoS Settings Page - Differentiated Services 12.7 Configuring ICMP Messages Internet Control Message Protocol (ICMP) is one of the core protocols of the Internet Protocol suite.

  • Page 149: Dns

    Click Add; the following dialog box appears: Figure 12-7: Internal DNS Table - Add Row Dialog Box Configure the DNS rule, as required. For a description of the parameters, see the table below. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 150: Configuring The Internal Srv Table

    Mediant 1000B Gateway and E- SBC Click Add; the DNS rule is added to the table. Table 12-16: Internal DNS Table Parameter Description Parameter Description Domain Name Defines the host name to be translated. domain-name The valid value is a string of up to 31 characters.
  • Page 151 Defines the priority of the target host. A lower value means that it is more preferred. priority-1|2|3 By default, no value is defined. [Srv2Ip_Priority1/2/3] Weight (1-3) Defines a relative weight for records with the same priority. weight-1|2|3 By default, no value is defined. [Srv2Ip_Weight1/2/3] Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 152: Open Solution Network (Osn) Server

    Mediant 1000B Gateway and E- SBC Parameter Description Port (1-3) Defines the TCP or UDP port on which the service is to be found. port-1|2|3 By default, no value is defined. [Srv2Ip_Port1/2/3] 12.9 Open Solution Network (OSN) Server This section describes various networking settings for the OSN server.

  • Page 153: 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 7.0 Mediant 1000B Gateway and E- SBC...

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

    Mediant 1000B Gateway and E- SBC The figure below illustrates the NAT problem faced by the SIP networks where the device is located behind a NAT: Figure 12-9: Device behind NAT and NAT Issues 12.10.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 155 Defines the global (public) IP address. The device adds the address to the SIP Via header, Contact header, 'o=' SDP field, and 'c=' SDP field, in the target-ip- outgoing packet. address [NATTranslation_Targ etIPAddress] Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 156: Remote Ua Behind Nat

    Mediant 1000B Gateway and E- SBC Parameter Description Source Start Port Defines the optional starting port range (1-65536) of the IP interface, used as matching criteria for the NAT rule. If not configured, the match is done src-start-port on the entire port range. Only IP addresses and ports of matched source [NATTranslation_Sour ports will be replaced.
  • Page 157 Note: If the SIP session is established (ACK) and the device (not the UA) sends the first packet, it sends it to the address obtained from the SIP message and only after Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 158 Mediant 1000B Gateway and E- SBC the device receives the first packet from the UA does it determine whether the UA is behind NAT.  [1] Disable NAT: (Default) The device considers the UA as not located behind NAT and sends media packets to the UA using the IP address:port specified in the SDP 'c=' line (Connection) of the first received SIP message.

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

    NoOpEnable and NoOpInterval parameters. 12.11 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.
  • Page 160 Mediant 1000B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-27044...

  • Page 161: Security

    You can also configure it through ini file (AccessList) or CLI (configure voip > access-list).  To configure a Firewall rule: Open the Firewall Settings page (Configuration tab > VoIP menu > Security > Firewall Settings). Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 162 Mediant 1000B Gateway and E- SBC Click Add; the following dialog box appears: Figure 13-1: Firewall Settings Table - Add Row Dialog Box Configure a Firewall rule according to the parameters described in the table below. Click Add, and then reset the device with a burn-to-flash for your settings to take effect.
  • Page 163 This is applicable if you enabled the 'Use Specific Interface' field. network-interface- The list displays interface names as defined in the Interface table in name 'Configuring IP Network Interfaces' on page 135. [AccessList_Interface_x] Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 164 Mediant 1000B Gateway and E- SBC Parameter Description Packet Size Defines the maximum allowed packet size. packet-size The valid range is 0 to 65535. [AccessList_Packet_Size] Note: When filtering fragmented IP packets, this field relates to the overall (re-assembled) packet size, and not to the size of each fragment.

  • Page 165: 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 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 166: Intrusion Detection System

    Mediant 1000B Gateway and 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 167: Enabling Ids

    Open the IDS Policy table (Configuration tab > VoIP menu > Security > Intrusion Detection and Prevention > Policy Table); the table shows the pre-configured IDS policies: Figure 13-4: IDS Policy Table with Default Rules Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 168 Mediant 1000B Gateway and E- SBC Click Add; the following dialog box appears: Figure 13-5: IDS Policy Table - Add Row Dialog Box Configure an IDS Policy name according to the parameters described in the table below. Click Add. Table 13-3: IDS Policy Table Parameter Descriptions...
  • Page 169  Header overflow  [3] Authentication failure =  Local authentication ("Bad digest" errors)  Remote authentication (SIP 401/407 is sent if original message includes authentication)  [4] Dialog establish failure = Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 170 Mediant 1000B Gateway and E- SBC Parameter Description  Classification failure (see 'Configuring Classification Rules' on page 635)  Routing failure  Other local rejects (prior to SIP 180 response)  Remote rejects (prior to SIP 180 response)  [5] Abnormal flow = ...

  • Page 171: 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 Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 172 Mediant 1000B Gateway and E- SBC Parameter Description (e.g., !3,4-7 means all indexes excluding 3, and excluding 4 through 7) Proxy Set ID Defines the Proxy Set(s) to which the IDS Policy is assigned. This indicates the Proxy Sets from where the attacks are coming from.

  • Page 173: Viewing Ids Alarms

    To view the blacklist: # show voip security ids blacklist active For example: Active blacklist entries: 10.33.5.110(NI:0) remaining 00h:00m:10s in blacklist Where SI is the SIP Interface and NI is the network interface. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 174 Mediant 1000B Gateway and E- SBC The device also sends IDS notifications and alarms in Syslog messages to a Syslog server. This occurs only if you have configured Syslog (see 'Enabling Syslog' on page 848). An example of a Syslog message with IDS alarms and notifications is shown below:...

  • Page 175: Media

    To configure gain control using the Web interface: Open the Voice Settings page (Configuration tab > VoIP menu > Media > Voice Settings). Figure 14-1: Voice Volume Parameters in Voice Settings Page Configure the following parameters: Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 176: Silence Suppression (Compression)

    Mediant 1000B Gateway and E- SBC • 'Voice Volume' (VoiceVolume) - Defines the voice gain control (in decibels) of the transmitted signal. • 'Input Gain' (InputGain) - Defines the PCM input gain control (in decibels) of the received signal. Click Submit.

  • Page 177: Fax And Modem Capabilities

    IsFaxUsed parameter and V.152 parameters in Section 'V.152 Support' on page 188. • For a detailed description of the parameters appearing on this page, see 'Configuration Parameters Reference' on page 881. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 178: Fax/Modem Operating Modes

    Mediant 1000B Gateway and 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). Figure 14-4: Fax/Modem/CID Settings Page Configure the parameters, as required. Click Submit.

  • Page 179: Fax/Modem Transport Modes

    T.38 capabilities using a Re-INVITE message. If the far- end device doesn't support T.38, the fax fails. In this mode, the 'Fax Transport Mode' parameter (FaxTransportMode) is ignored. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 180 Mediant 1000B Gateway and E- SBC  To configure T.38 mode using SIP Re-INVITE messages: In the SIP General Parameters page (Configuration tab > VoIP menu > SIP Definitions > General Parameters), set the 'Fax Signaling Method' parameter to T.38 Relay (IsFaxUsed = 1).

  • Page 181: Fax / Modem Transport Mode

    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 182: Fax Fallback

    Mediant 1000B Gateway and E- SBC  Dynamic Jitter Buffer Minimum Delay = 40  Dynamic Jitter Buffer Optimization Factor = 13 After a few seconds upon detection of fax V.21 preamble or super G3 fax signals, the device sends a second Re-INVITE enabling the echo canceller (the echo canceller is disabled only on modem transmission).

  • Page 183: Fax/Modem Bypass Mode

    'Fax Bypass Payload Type' (FaxBypassPayloadType) - in the RTP/RTCP Settings page (Configuration tab > VoIP menu > Media > RTP/RTCP Settings). • ModemBypassPayloadType (ini file). • FaxModemBypassBasicRTPPacketInterval (ini file). • FaxModemBypasDJBufMinDelay (ini file). Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 184: 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 185: Fax / Modem Transparent With Events Mode

    Set the 'Fax Transport Mode' parameter to Disable (FaxTransportMode = 0). Set the 'V.21 Modem Transport Type' parameter to Disable (V21ModemTransportType = 0). Set the 'V.22 Modem Transport Type' parameter to Disable (V22ModemTransportType = 0). Version 7.0 Mediant 1000B Gateway and E- SBC...

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

    Mediant 1000B Gateway and E- SBC 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 187: Bypass Mechanism For V.34 Fax Transmission

    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). Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 188: Support

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

  • Page 189: Configuring Rtp/Rtcp Settings

    - only when the Jitter Buffer is completely empty or completely full. When such condition occurs, the correction is performed by dropping several voice packets simultaneously or by adding several BFI packets simultaneously, so that the Jitter Buffer returns to its normal condition. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 190: Comfort Noise Generation

    Mediant 1000B Gateway and E- SBC The following procedure describes how to configure the jitter buffer using the Web interface.  To configure jitter buffer using the Web interface: Open the RTP/RTCP Settings page (Configuration tab > VoIP menu > Media >...

  • Page 191: Configuring Dtmf Transport Types

    (LBR) coders, the quality of the DTMF digits is reduced. To enable the mode: Set the 'Declare RFC 2833 in SDP' parameter to No (RxDTMFOption = 0). Set the 'First Tx DTMF Option' parameter to Not Supported (FirstTxDTMFOption = 0). Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 192: Configuring Rfc 2833 Payload

    Mediant 1000B Gateway and E- SBC Set the ini file parameter, DTMFTransportType to 2 (i.e., transparent).  Using INFO message according to Korea mode: DTMF digits are sent to the remote side in INFO messages. To enable this mode: Set the 'Declare RFC 2833 in SDP' parameter to No (RxDTMFOption = 0).

  • Page 193: Configuring Rtp Base Udp Port

    (default is 6000) and number of channels is the maximum number of channels purchased from AudioCodes (included in the installed Software License Key). For example, if the base UDP port is set to 6000, the port range for 20 channels is:...

  • Page 194: Event Detection And Notification Using X-Detect Header

    Mediant 1000B Gateway and E- SBC Note: • The RTP port must be different from ports configured for SIP signaling traffic (i.e., ports configured for SIP Interfaces). For example, if the RTP port range is 6000 to 6999, the SIP port can either be less than 6000 or greater than 6999.
  • Page 195 FaxTransportMode parameter to any value other than 0. modem Set the VxxModemTransportType parameter to 3. voice-start Set the EnableDSPIPMDetectors parameter to 1. voice-end Note: PTT is currently not supported for SBC calls. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 196: Sit Event Detection

    Mediant 1000B Gateway and E- SBC 14.4.1 SIT Event Detection The device can detect and report the following Special Information Tones (SIT) types from the PSTN:  SIT-NC (No Circuit found)  SIT-IC (Operator Intercept)  SIT-VC (Vacant Circuit - non-registered number) ...

  • Page 197: Detecting Answering Machine Beeps

     AMD-detected Beep: Type= AMD SubType= Beep  CPT-detected Beep: Type= CPT SubType=Beep Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 198: Sip Call Flow Examples Of Event Detection And Notification

    Mediant 1000B Gateway and E- SBC 14.4.3 SIP Call Flow Examples of Event Detection and Notification Two SIP call flow examples are provided below of event detection and notification:  The following example shows a SIP call flow of the device's AMD and event detection...
  • Page 199 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" <sip:anonymous@anonymous.invalid>;tag=1c25298 To: <sip:101@10.33.2.53;user=phone> Call-ID: 11923@10.33.2.53 CSeq: 1 INVITE Contact: <sip:100@10.33.2.53> X- Detect: Response=AMD,CPT Content-Type: Application/X-Detect Content-Length: xxx Type = CPT Subtype = Beep Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 200: Answering Machine Detection (Amd)

    AudioCodes sales representative for more information on this service. You will be typically required to provide AudioCodes with a database of recorded voices (calls) in the language on which the device's AMD feature can base its voice detector algorithms.
  • Page 201 The device supports up to eight AMD algorithm suites called Parameter Suites, where each suite defines a range of detection sensitivity levels. Sensitivity levels refer to how accurately, based on AudioCodes' voice detection algorithms, the device can detect whether a human or machine has answered the call. Each level supports a different detection sensitivity to human and machine.

  • Page 202: Configuring Amd

    Mediant 1000B Gateway and E- SBC Table 14-4: Approximate AMD High Detection Sensitivity - Parameter Suite 1 (Based on North American English) Performance AMD Detection Sensitivity Success Rate for Live Calls Success Rate for Answering Machine 0 (Best for Answering...

  • Page 203: Enabling Ip-To-Tel Call Disconnection Upon Detection Of Answering Machine

    You can enable this feature for all calls (globally) using the AMDmode parameter, or for specific calls using IP Profiles where the IP Profile parameter 'AMD Mode' (IpProfile_AmdMode) is set to [1] Disconnect on AMD (see 'Configuring IP Profiles' on page 385). Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 204: Automatic Gain Control (Agc)

    Mediant 1000B Gateway and E- SBC 14.6 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 Tel, determined by the 'AGC Redirection' parameter, calculates the essential gain, and then performs amplification.

  • Page 205: Configuring Analog Settings

    TIP lead. The following procedure describes how to configure the Port Ground Start table through the Web interface. You can also configure it through ini file (GroundKeyDetection_x). Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 206: Configuring Dsp Templates

    Mediant 1000B Gateway and E- SBC  To configure signaling method per port: Open the Port Ground Start table (Configuration tab > VoIP menu > Media > Port Ground Start Table). Figure 14-13: Port Ground Start Table Page For each port, select one of the following from the Ground Start drop-down list: •...

  • Page 207: Dsp Channel Resources For Transcoding

    Set the IPmediaChannels parameter to the number of DSP channels that you want to “borrow” (use) from each PRI module. The setting below shows an example of borrowing DSP channels from PRI modules #1 and #2: Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 208: Configuring Media (Srtp) Security

    Mediant 1000B Gateway and E- SBC [IPMediaChannels] FORMAT IPMediaChannels_Index = IPMediaChannels_ModuleID, IPMediaChannels_DSPChannelsReserved; IPMediaChannels 1 = 1, 15; IPMediaChannels 2 = 2, 10; [\IPMediaChannels] Notes: • The value of IPMediaChannels_DSPChannelsReserved must be in multiples of 5. • By default, the MPM module is set to the maximum number of IP media channels.
  • Page 209 For a detailed description of the SRTP parameters, see 'Configuring IP Profiles' on page 385 and 'SRTP Parameters' on page 917. • When SRTP is used, the channel capacity may be reduced. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 210 Mediant 1000B Gateway and E- SBC The procedure below describes how to configure SRTP through the Web interface.  To enable and configure SRTP: Open the Media Security page (Configuration tab > VoIP menu > Media > Media Security). Figure 14-15: Media Security Page From the 'Media Security' drop-down list (EnableMediaSecurity), select Enable to enable SRTP.

  • Page 211: Services

    IP Address Lease Time Option 1 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 Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 212 Mediant 1000B Gateway and E- SBC DHCP Option Code DHCP Option Name Option 2 Time Offset Option 66 TFTP Server Name Option 67 Boot file Name Option 120 SIP Server Once you have configured the DHCP server, you can configure the following: ...
  • Page 213 IP address pool range used by the DHCP server to allocate start-address addresses. [DhcpServer_StartIPAddr The default value is 192.168.0.100. ess] Note: The IP address must belong to the same subnet as the associated interface’s IP address. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 214 Mediant 1000B Gateway and E- SBC Parameter Description End IP Address Defines the ending IP address (IPv4 address in dotted-decimal format) of the IP address pool range used by the DHCP server to allocate end-address addresses. [DhcpServer_EndIPAddre The default value is 192.168.0.149.
  • Page 215 Server). After defining the parameter, use the 'SIP server type' parameter (see below) to define the type of address (FQDN or IP address). The valid value is a string of up to 256 characters. The default is 0.0.0.0. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 216: 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 217: Configuring Additional Dhcp Options

    In the table, select the row of the desired DHCP server for which you want to configure additional DHCP Options, and then click the DHCP Option Table link, located below the table; the DHCP Option table opens. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 218 Mediant 1000B Gateway and E- SBC Click Add; the following dialog box appears: Figure 15-3: DHCP Option Table - Add Row Dialog Box Configure additional DHCP Options for the DHCP server according to the parameters described in the table below.

  • Page 219: Configuring Static Ip Addresses For Dhcp Clients

    In the table, select the row of the desired DHCP server for which you want to configure static IP addresses for DHCP clients, and then click the DHCP Static IP Table link, located below the table; the DHCP Static IP table opens. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 220: Viewing And Deleting Dhcp Clients

    Mediant 1000B Gateway and E- SBC Click Add; the following dialog box appears: Figure 15-4: DHCP Static IP Table - Add Row Dialog Box Configure a static IP address for a specific DHCP client according to the parameters described in the table below.
  • Page 221 Select the table row index of the DHCP client that you want to delete. Click the Action button, and then from the drop-down menu, choose Delete; a confirmation message appears. Click OK to confirm deletion. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 222: Radius-Based Services

    Mediant 1000B Gateway and E- SBC 15.2 RADIUS-based Services The device supports Remote Authentication Dial In User Service (RADIUS), by acting as a RADIUS client. You can use RADIUS for the following:  Authentication and authorization of management users (login username and password) to gain access to the device's management interface.
  • Page 223 To enable and configure RADIUS-based accounting, see 'Configuring RADIUS Accounting' on page 827.  To configure a RADIUS server: Open the RADIUS Servers table (Configuration tab > System menu > Management > RADIUS Servers). Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 224 Mediant 1000B Gateway and E- SBC Click Add; the following dialog box appears: Figure 15-7: RADIUS Servers Table - Add Row Dialog Box Configure a RADIUS server according to the parameters described in the table below. Click Add. Table 15-6: RADIUS Servers Table Parameter Descriptions...

  • Page 225: Configuring Interface For Radius Communication

    (authorization). When a management user (client) tries to access the device, the device sends the RADIUS server the user's username and password for authentication. The RADIUS server replies with an acceptance Version 7.0 Mediant 1000B Gateway and E- SBC...

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

    Mediant 1000B Gateway and E- SBC or a rejection notification. During the RADIUS authentication process, the device’s Web interface is blocked until an acceptance response is received from the RADIUS server. Note that communication between the device and the RADIUS server is done by using a shared secret, which is not transmitted over the network.

  • Page 227: Configuring Radius-Based User Authentication

    15.2.5.2 Configuring RADIUS-based User Authentication The following procedure describes how to configure the RADIUS parameters specific to login authentication. For a detailed description of the RADIUS parameters, see 'RADIUS Parameters' on page 1131. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 228 Mediant 1000B Gateway and E- SBC  To configure RADIUS parameters for login authentication: Open the Authentication Settings page (Configuration tab > System menu > Management > Authentication Settings). Figure 15-9: Authentication Settings Page - RADIUS Configuration From the 'Use RADIUS for Web/Telnet Login' drop-down list, select Enable to enable RADIUS authentication for Web and Telnet login.

  • Page 229: Securing Radius Communication

    Web interface's login screen. 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 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 230: Radius-Based Cdr Accounting

    Mediant 1000B Gateway and E- SBC 15.2.6 RADIUS-based CDR Accounting Once you have configured a RADIUS server(s) for accounting in 'Configuring RADIUS Servers' on page 222, you need to enable and configure RADIUS-based CDR accounting (see 'Configuring RADIUS Accounting' on page 827).

  • Page 231: Enabling The Ldap Service

    Figure 15-10: 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 7.0 Mediant 1000B Gateway and E- SBC...

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

    Mediant 1000B Gateway and E- SBC 15.3.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 233 LDAP server. timeout The valid range is 0 to 35791. The default is 1200. If set to 0, the LDAP [LdapServersGroup_Cac entry is always valid. heEntryTimeout] Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 234: Configuring Ldap Servers

    Mediant 1000B Gateway and E- SBC Parameter Description Cache Entry Removal Defines the duration (in hours) after which the LDAP entry is deleted from Timeout the device's LDAP cache. cache-entry- The valid range is 0 to 596. The default is 0 (i.e., the entry is never removal-timeout deleted).
  • Page 235 Click Add; the following dialog box appears: Figure 15-13: LDAP Configuration Table - Add Row Dialog Box Configure an LDAP server according to the parameters described in the table below. Click Add. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 236 Mediant 1000B Gateway and E- SBC Table 15-8: LDAP Configuration Table Parameter Descriptions Parameter Description Index Defines an index number for the new table row. [LdapConfiguration_Inde Note: Each row must be configured with a unique index. LDAP Servers Group Assigns the LDAP server to an LDAP Server Group, configured in the...
  • Page 237 By default, no value is defined (None) and the device uses the OAMP [LdapConfiguration_Inter network interface, configured in the Interface table. face] For configuring IP network interfaces, see 'Configuring IP Network Interfaces' on page 135. Note: The parameter is mandatory. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 238 Mediant 1000B Gateway and E- SBC Parameter Description Management Attribute Defines the LDAP attribute name to query, which contains a list of groups to which the user is a member. For Active Directory, this attribute is mgmt-attr typically "memberOf". The attribute's values (groups) are used to [LdapConfiguration_Mng determine the user's management access level;...

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

    The valid value is a string of up to 256 characters. [LdapServersSearchDNs _Base_Path] For example: OU=NY,DC=OCSR2,DC=local. In this example, the DN path is defined by the LDAP names, OU (organizational unit) and DC (domain component). Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 240: Configuring The Ldap Search Filter Attribute

    Mediant 1000B Gateway and E- SBC 15.3.6 Configuring the LDAP Search Filter Attribute When the LDAP-based login username-password authentication succeeds, the device searches the LDAP server for all groups of which the user is a member. The LDAP query is based on the following LDAP data structure: ...

  • Page 241: Configuring Access Level Per Management Groups Attributes

    'Management Attribute' parameter in the LDAP Configuration table. The LDAP response includes all the groups of which the specific user is a member, for example: CN=\# Support Dept,OU=R&D Groups,OU=Groups,OU=APC,OU=Japan,OU=ABC,DC=corp,DC=abc,DC=com CN=\#AllCellular,OU=Groups,OU=APC,OU=Japan,OU=ABC,DC=corp,DC=abc,D C=com Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 242 Mediant 1000B Gateway and E- SBC The device searches this LDAP response for the group names that you configured in the Management LDAP Groups table in order to determine the user's access level. If the device finds a group name, the user is assigned the corresponding access level and login is permitted;...

  • Page 243: Configuring The Device's Ldap Cache

    LDAP queries of a cached key whose cached Attributes include a, b , c, and d, where a is the oldest and d the most recent Attribute: Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 244: Refreshing The Ldap Cache

    Mediant 1000B Gateway and E- SBC Table 15-11: Example of LDAP Query for Cached Attributes Attributes Requested in New Attributes Sent in LDAP Query Attributes Saved in Cache after LDAP Query for Cached Key to LDAP Server LDAP Response e, a, b, c, d...
  • Page 245 Click Refresh; if a request with the specified key exists in the cache, a request is sent to the LDAP server for the Attributes associated in the cache with the search key. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 246: Clearing The Ldap Cache

    Mediant 1000B Gateway and E- SBC 15.3.8.2 Clearing the LDAP Cache You can remove (clear) all LDAP entries in the device's LDAP cache for a specific LDAP Server Group, as described in the following procedure.  To clear the LDAP cache: Open the LDAP Settings page (Configuration tab >...

  • Page 247: Ldap-Based Login Authentication Example

    (access level), and assumes that you are familiar with other aspects of LDAP configuration (e.g., LDAP server's address). The LDAP server's entry data structure schema in the example is as follows: Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 248 Mediant 1000B Gateway and E- SBC  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-22: Base Path (DN) in LDAP Server User's Manual Document #: LTRT-27044...
  • Page 249 (where the attribute's value equals the username): Figure 15-23: Username Found using sAMAccount Attribute Search Filter  Management Attribute: memberOf. The attribute contains the member groups of the user: Figure 15-24: User's memberOf Attribute Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 250 Mediant 1000B Gateway and E- SBC  Management Group: mySecAdmin. The group to which the user belongs, as listed under the memberOf attribute: Figure 15-25: User's mySecAdmin Group in memberOf Management Attribute The configuration to match the above LDAP data structure schema is as follows: ...
  • Page 251 The management group and its corresponding access level is configured in the Management LDAP Groups table (see 'Configuring Access Level per Management Groups Attributes' on page 241): Figure 15-30: Configuring Management Group Attributes for Determining Access Level Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 252: Enabling Ldap Searches For Numbers With Characters

    Mediant 1000B Gateway and E- SBC 15.3.11 Enabling LDAP Searches for Numbers with Characters Typically, the device performs LDAP searches in the AD for complete numbers where the digits are adjacent to one another (e.g., 5038234567). However, if the number is defined in the AD with characters (such as spaces, hyphens and periods) separating the digits (e.g.,...

  • Page 253: Querying The Ad And Routing Priority

    If the query is found: The AD returns up to four attributes - Lync, PBX / IP PBX, private (only if it equals Primary or Secondary key), and mobile. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 254 Mediant 1000B Gateway and E- SBC The device adds unique prefix keywords to the query results in order to identify the query type (i.e., IP domain). These prefixes are used as the prefix destination number value in the Tel-to-IP Routing table to denote the IP domains: •...
  • Page 255 Figure 15-31: LDAP Query Flowchart Note: If you are using the device's local LDAP cache, see 'Configuring the Device's LDAP Cache' on page 243 for the LDAP query process. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 256: Configuring Ad-Based Routing Rules

    Mediant 1000B Gateway and E- SBC 15.3.12.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 234.
  • Page 257 10.33.45.100) upon successful AD query result for the Mobile attribute.  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). Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 258: Querying The Ad For Calling Name

    Mediant 1000B Gateway and E- SBC  Rule 6: Sends query for original destination number of received call to the LDAP server.  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 •...

  • Page 259: Least Cost Routing

    10 minutes: Table 15-15: Call Cost Comparison between Cost Groups for different Call Durations Total Call Cost per Duration Connection Cost Group Minute Cost Cost 1 Minute 10 Minutes 80.3 Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 260 Mediant 1000B Gateway and E- SBC If four matching routing rules are located in the routing table and each one is assigned a different Cost Group as listed in the table above, then the rule assigned Cost Group "D" is selected.

  • Page 261: Configuring Lcr

    Time Bands per Cost Group. Up to 10 Cost Groups can be configured. The following procedure describes how to configure Cost Groups through the Web interface. You can also configure it through ini file (CostGroupTable) or CLI (configure voip > services least-cost-routing cost-group). Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 262: Configuring Time Bands For Cost Groups

    Mediant 1000B Gateway and E- SBC  To configure a Cost Group: Open the Cost Group table (Configuration tab > VoIP menu > Services > Least Cost Routing > Cost Group Table). Click Add; the following dialog box appears: Configure a Cost Group according to the parameters described in the table below.
  • Page 263 For example, SAT:22:00 denotes Saturday at 10 pm. End Time Defines the day and time of day until when this time band is applicable. For a description of the valid values, see the parameter above. end-time [CostGroupTimebands_ EndTime] Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 264: Assigning Cost Groups To Routing Rules

    Mediant 1000B Gateway and E- SBC Parameter Description Connection Cost Defines the call connection cost during this time band. This is added as a fixed charge to the call. connection-cost The valid value range is 0-65533. The default is 0.

  • Page 265: Http-Based Remote Services

    Routing: Call routing service, whereby the remote host (e.g., routing server) determines the next hop of an incoming call on the path to the final destination. For more information on employing a third-party, remote routing server or AudioCodes ARM, see 'Centralized Third-Party Routing Server or ARM' on page 270.
  • Page 266 Mediant 1000B Gateway and E- SBC The following procedure describes how to configure HTTP Remote Services through the Web interface. You can also configure it through ini file (HTTPRemoteServices).  To configure an HTTP-based service Open the HTTP Remote Services table (Configuration tab > VoIP menu > Services >...
  • Page 267 Number of Sockets Defines how many sockets (connection) are established per remote host. [HTTPRemoteServices_Nu mOfSockets] The valid value is 1 to 10. The default is 1. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 268 Mediant 1000B Gateway and E- SBC Parameter Description Username Defines the username for HTTP authentication. [HTTPRemoteServices_Au The valid value is a string of up to 80 characters. The default is "user". thUserName] Password Defines the password for HTTP authentication. [HTTPRemoteServices_Au The valid value is a string of up to 80 characters.

  • Page 269: Configuring Remote Http Hosts

    The valid value is a string of up to 40 characters. By default, no value is defined. Notes:  Each row must be configured with a unique name.  The parameter is mandatory. Address Defines the address (IP address or FQDN) of the host. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 270: Centralized Third-Party Routing Server Or Arm

    (ARM) routing server to handle call routing decisions in deployments consisting of multiple AudioCodes devices. The routing server can be used to handle SBC, Tel-to-IP, and IP-to- Tel calls. Employing a routing server replaces the need for the device's routing tables (IP- to-IP Routing table for SBC calls, and Tel-to-IP Routing table and IP-to-Tel Routing table for Tel-to-IP and IP-to-Tel calls respectively) to determine call destination.
  • Page 271 The routing server can also manipulate call data such as calling name, if required. It can also create new IP Groups and associated configuration entities, if necessary for routing. Multiple routing servers can also be employed, whereby each device in the chain path can Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 272 Mediant 1000B Gateway and E- SBC use a specific routing server. Alternatively, a single routing server can be employed and used for all devices ("stateful" routing server). The device automatically updates (sends) the routing server with its' configuration topology regarding SIP routing-related entities (Trunk Groups, SRDs, SIP Interfaces, and IP Groups) that have been configured for use by the routing server.

  • Page 273: Http-Based Proxy Services

     HTTP-based EMS Services for AudioCodes Equipment behind NAT: You can configure the device to act as an HTTP Proxy that enables AudioCodes EMS to manage AudioCodes equipment (such as IP Phones) over HTTP when the equipment is located behind NAT (e.g., in the LAN) and EMS is located in a public domain (e.g., in the WAN).

  • Page 274: Enabling The Http Proxy Application

    Mediant 1000B Gateway and E- SBC 15.6.1 Enabling the HTTP Proxy Application Before you can configure HTTP-based proxy services, you must enable the HTTP Proxy application, as described in the following procedure. Once enabled, the Web interface displays menus in the Navigation pane that are relevant to the HTTP Proxy application.
  • Page 275 This is also configured for the associated TLS Context.  Note: The parameter is applicable only if the connection protocol is HTTPS (defined using the 'Protocol' parameter, above). Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 276: Configuring Http Proxy Services

    Mediant 1000B Gateway and E- SBC 15.6.3 Configuring HTTP Proxy Services The HTTP Proxy Services table lets you configure up to 10 HTTP Proxy Services. The following procedure describes how to configure HTTP Proxy Services through the Web interface. You can also configure it through ini file (HTTPProxyService) or CLI (configure system >...

  • Page 277: Configuring Http Proxy Hosts

    HTTP Proxy > HTTP Proxy Services). In the table, select the required HTTP Proxy Service index row, and then click the HTTP Proxy Hosts link, located below the table; the HTTP Proxy Hosts table appears. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 278 Mediant 1000B Gateway and E- SBC Click Add; the following dialog box appears: Figure 15-39: HTTP Proxy Hosts Table - Add Row Dialog Box Configure an HTTP Proxy Host according to the parameters described in the table below. Click Add, and then save ("burn") your settings to flash memory.

  • Page 279: Configuring An Http-Based Ems Service

    You can also configure it through ini file (EMSService) or CLI (configure system > http-proxy > ems-serv).  To configure an EMS Service: Open the EMS Services table (Configuration tab > VoIP menu > Services > HTTP Proxy > EMS Services). Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 280 Mediant 1000B Gateway and E- SBC Click Add; the following dialog box appears: Figure 15-40: EMS Services Table - Add Row Dialog Box Configure an EMS Service according to the parameters described in the table below. Click Add, and then save ("burn") your settings to flash memory.

  • Page 281: Configuring Call Setup Rules

    This is done using the 'Call Setup Rules Set ID' field in the routing table:  SBC IP-to-IP routing - see Configuring SBC IP-to-IP Routing Rules on page 643  Tel-to-IP routing rules - see Configuring Tel-to-IP Routing Rules on page 483 Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 282 Mediant 1000B Gateway and E- SBC  IP-to-Tel routing rules - see 'Configuring IP-to-Trunk Group Routing Rules' on page If an incoming call matches the characteristics of a routing rule, the device first runs the assigned Call Setup Rules Set ID before routing the call according to the rule. The device uses the routing rule to route the call, depending on the result of the Call Setup Rules Set ...
  • Page 283 PrivateLine")  ldap.found !exists (LDAP record not found)  ldap.err exists (LDAP error exists) Action Subject Defines the element (header, parameter, or body) upon which you want to perform the action. action-subject Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 284 Mediant 1000B Gateway and E- SBC Parameter Description [CallSetupRules_ActionSu The valid value is a string of up to 100 characters (case-insensitive). bject] Examples:  header.from contains '1234' (SBC calls only)  param.call.dst.user (called number)  param.call.src.user (calling number)  param.call.src.name (calling name) ...

  • Page 285: Call Setup Rule Examples

    'Action Type': Modify ♦ 'Action Value': ldap.attr. displayName • Routing table configuration: A single routing rule is assigned the Call Setup Rule Set ID. ♦ Index 1:  'Call Setup Rules Set Id': 2 Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 286 Mediant 1000B Gateway and E- SBC  Example 3: This example configures the device to route the incoming call according to whether or not the source number of the incoming call also exists in the AD server. The device queries the AD server for the attribute record, "telephoneNumber" whose value is the same as the received source number (e.g., telephoneNumber=4064").

  • Page 287: Enhanced 9-1-1 Support For Lync Server

    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 (hereafter referred to as Lync Server) and AudioCodes' device's ELIN interworking capabilities, which provides the SIP Trunk or ISDN (or CAMA) connectivity to the E9-1-1 emergency service provider.

  • Page 288: Microsoft Lync Server And E9-1-1

    The figure below illustrates the routing of an E9-1-1 call to the PSAP: The VoIP user dials 9-1-1. AudioCodes' ELIN device eventually sends the call to the emergency service provider over the PSTN or SIP Trunk (PSAP server). The emergency service provider identifies the call is an emergency call and sends it to an E9-1-1 Selective Router in the Emergency Services provider's network.
  • Page 289 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 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 290: Adding Elins To The Location Information Server

    Mediant 1000B Gateway and E- SBC For a Lync client that moves inside the corporate network such as a soft phone on a laptop that connects wirelessly to the corporate network, Lync Server can determine which subnet the phone belongs to or which WAP / SSID is currently serving the soft- client.

  • Page 291: Passing Location Information To The Pstn Emergency Provider

    ERL for each floor of the building. The ELIN is used as the phone number for 911 callers within this ERL. The figure below illustrates the use of ERLs and ELINs, with an E9-1-1 call from floor 2 at the branch office: Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 292: Audiocodes Elin Device For Lync Server E9-1-1 Calls To Pstn

    ELIN when dialing 9-1-1. 15.8.3 AudioCodes ELIN Device for Lync Server E9-1-1 Calls to PSTN 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 293: Detecting And Handling E9-1-1 Calls

    User's Manual 15. Services The figure below illustrates an AudioCodes ELIN device deployed in the Lync Server environment for handling E9-1-1 calls between the Enterprise and the emergency service provider. 15.8.3.1 Detecting and Handling E9-1-1 Calls The ELIN device identifies E9-1-1 calls and translates their incoming E9-1-1 calling numbers into ELIN numbers, sent toward the PSAP.
  • Page 294 Mediant 1000B Gateway and E- SBC ELIN Time Count Index Call From 4257275999 22:11:57 4258359444 4257275615 22:12:03 4258359555 4257275616 22:11:45 4258359777 The ELIN table stores this information for a user-defined period (see 'Configuring the E9-1-1 Callback Timeout' on page 297), starting from when the E9-1-1 call, established with the PSAP, terminates.

  • Page 295: Pre-Empting Existing Calls For E9-1-1 Calls

    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 device to translate the ELIN number back into the E9-1-1 caller's extension number. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 296: Selecting Elin For Multiple Calls Within Same Erl

    Mediant 1000B Gateway and E- SBC In the ELIN table of the device, 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 device translates the called number (i.e., ELIN) received from the PSAP to the corresponding E9-1-1 caller's extension...

  • Page 297: Location Based Emergency Routing

    Location-based emergency routing is applicable only to the Gateway application. 15.8.4 Configuring AudioCodes ELIN Device This section describes E9-1-1 configuration of the AudioCodes ELIN Gateway deployed in the Lync Server environment. 15.8.4.1 Enabling the E9-1-1 Feature By default, the ELIN device feature for E9-1-1 emergency call handling in a Lync environment is disabled.

  • Page 298: Configuring The Sip Release Cause Code For Failed E9-1-1 Calls

    Mediant 1000B Gateway and E- SBC terminated. By default, an ELIN can be used for PSAP callback within 30 minutes after the call is terminated. You can change this to any value between 0 and 60:  To configure the E9-1-1 callback timeout Open the Advanced Parameters page (Configuration tab >...
  • Page 299 (Configuration tab > VoIP menu > Gateway > Manipulations > Dest Number IP- >Tel), add the following two rules for manipulating the destination number of incoming emergency calls, based on ELIN numbers: Figure 15-44: Destination Number Manipulation Rules for Location-Based Emergency Routing Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 300: Viewing The Elin Table

    Mediant 1000B Gateway and E- SBC Index 0 manipulates the destination number for London emergency callers; Index 1 manipulates the destination number for Manchester emergency callers. 15.8.4.6 Viewing the ELIN Table To view the ELIN table:  # show voip e911...

  • Page 301: 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 302: 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 303: Configuring Quality Of Experience Profiles

     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 the SEM Server' on page 301.
  • Page 304 Mediant 1000B Gateway and E- SBC Note: For your convenience, the device provides pre-configured Quality of Experience Profiles. One of these pre-configured profiles is the default Quality of Experience Profile. Therefore, if you do not configure a Quality of Experience Profile, this default is used.
  • Page 305  [1] Delay [QOEColorRules_monitoredPara  [2] Packet Loss  [3] Jitter  [4] RERL [Echo] Direction Defines the monitoring direction.  direction [0] Device Side (default)  [1] Remote Side [QOEColorRules_direction] Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 306 Mediant 1000B Gateway and E- SBC Parameter Description Sensitivity Level Defines the sensitivity level of the thresholds.  sensitivity-level [0] User Defined = Need to define the thresholds in the parameters described below. [QOEColorRules_profile]  [1] Low = Pre-configured low sensitivity threshold values.

  • Page 307: Configuring Bandwidth Profiles

    You can also configure it through ini file (BWProfile) or CLI (configure voip > qoe bw-profile).  To configure Bandwidth Profiles: Open the Bandwidth Profile page (Configuration tab > VoIP menu > Quality of Experience > Bandwidth Profile). Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 308 Mediant 1000B Gateway and E- SBC Click Add; the following dialog box appears: Figure 16-4: Bandwidth Profile Table - Add Row Dialog Box The figure above shows a configuration example where if the outgoing voice traffic threshold of 64,000 increases by 80% (70% warning threshold plus 10% hysteresis) to 115,200 (64,000 plus 51,200), a Yellow state occurs and an alarm is sent.
  • Page 309 If enabled, an alarm is sent if one of the following scenarios occurs:  Warning threshold is exceeded (Warning severity - Yellow threshold).  Any configured bandwidth threshold is exceeded (Major severity - Red threshold). Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 310: Configuring Media Enhancement Profiles

    Mediant 1000B Gateway and E- SBC 16.4 Configuring Media Enhancement Profiles Media Enhancement Profiles provides support for access control and media quality enhancements based on call quality measurements (configured in 'Configuring Quality of Experience Profiles' on page 303) and bandwidth utilization (configured in 'Configuring Bandwidth Profiles' on page 307).
  • Page 311 Profile index row, and then click the Media Enhancement Rules link located below the table; the Media Enhancement Rules page appears. Click Add; the following dialog box appears: Figure 16-6: Media Enhancement Rules Table - Add Row Dialog Box Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 312 Mediant 1000B Gateway and E- SBC Configure a Media Enhancement Rule according to the parameters described in the table below. Click Add, and then reset the device with a save ("burn") to flash memory. Table 16-5: Media Enhancement Rules Table Parameter Descriptions...

  • Page 313: Control Network

    You can also configure it through ini file (CpMediaRealm) or CLI (configure voip > voip-network realm).  To configure a Media Realm: Open the Media Realm table (Configuration tab > VoIP menu > VoIP Network > Media Realm Table). Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 314 Mediant 1000B Gateway and E- SBC Click Add; the following dialog box appears: Figure 17-1: Media Realm Table - Add Row Dialog Box Configure the Media Realm according to the parameters described in the table below. Click Add. Table 17-1: Media Realm Table Parameter Descriptions...
  • Page 315 If you do not configure the parameter (i.e., the parameter is No for all Media Realms), the device uses the first Media Realm in the table as the default.  If the table is not configured, the default Media Realm includes all configured media interfaces. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 316: Configuring Remote Media Subnets

    Mediant 1000B Gateway and E- SBC Parameter Description QoE Profile Assigns a QoE Profile to the Media Realm. qoe-profile By default, no value is defined (None). [CpMediaRealm_QoeP For configuring QoE Profiles, see 'Configuring Quality of Experience rofile] Profiles' on page 303.
  • Page 317 Defines the subnet mask in Classless Inter-Domain Routing (CIDR) notation. For example, 16 denotes 255.255.0.0. prefix-length The default is 16. [RemoteMediaSubnet_ PrefixLength] Address Family Defines the IP address protocol.  address-family [2] IPv4 (default)  [10] IPv6 [RemoteMediaSubnet_ AddressFamily] Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 318: Configuring Media Realm Extensions

    Mediant 1000B Gateway and E- SBC Parameter Description Destination IP Defines the IP address of the destination. dst-ip-address The default is 0.0.0.0. [RemoteMediaSubnet_ DstIPAddress] QOE Profile Name Assigns a Quality of Experience Profile to the Remote Media Subnet. By default, no value is defined (None).
  • Page 319 For more information, see 'Configuring RTP Base UDP Port' on page 193.  The port range must not overlap with any other media port range that you have configured in the table or in the Media Realm table. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 320: Configuring Srds

    Mediant 1000B Gateway and E- SBC Parameter Description Port Range End Defines the last (upper) port in the range of media UDP ports for the Media Realm Extension. [MediaRealmExtension _PortRangeEnd] Note: It is unnecessary to configure the parameter. The device...
  • Page 321 Interface would represent a specific Layer-3 network (IP PBX, SIP Trunk, or far-end users) in your environment. The following figure provides an example of such a deployment: Figure 17-6: Deployment using a Single SRD Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 322 Mediant 1000B Gateway and E- SBC Notes: • It is recommended to use a single-SRD configuration topology, unless you are deploying the device in a multi-tenant environment, in which case, multiple SRDs are required. • Each SIP Interface, Proxy Set, and IP Group can be associated with only one SRD.
  • Page 323 IP Profile table (SBCRemoteRepresentationMode, SBCKeepVIAHeaders, SBCKeepUserAgentHeader, SBCKeepRoutingHeaders, SBCRemoteMultipleEarlyDialogs).  If the 'SBC Operation Mode' parameter is configured in the IP Group table, the 'SBC Operation Mode' parameter in the SRD table is ignored. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 324 Mediant 1000B Gateway and E- SBC Parameter Description SBC Routing Policy Assigns an SBC Routing Policy to the SRD. sbc-routing- By default, no value is defined (None) if you have configured multiple policy-name SBC Routing Policies. If you have configured only one SBC Routing Policy, the device assigns it to the SRD by default.

  • Page 325: Filtering Tables In Web Interface By Srd

    The device is a real- time multi-tenant system that provides each tenant with optimal real-time performance, as each session received by the device is classified and processed only through the tenant’s “orbit”. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 326 Mediant 1000B Gateway and E- SBC While some enterprises are large enough to justify a dedicated standalone device, many enterprises require only a fraction of the device's capacity and capabilities. Service providers offering SIP Trunking services can funnel multiple enterprises into a single device and thereby, reap significant cost improvements over a device-per-customer model.
  • Page 327 # srd-view <SRD name> Once accessed, the tenant's name (i.e., SRD name) forms part of the CLI prompt, for example: # srd-view datacenter (srd-datacenter)#  To exit the tenant view: # no srd-view Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 328: Cloning Srds

    Mediant 1000B Gateway and E- SBC 17.2.3 Cloning SRDs You can clone (duplicate) existing SRDs. This is especially useful when operating in a multi-tenant environment and you need to add new tenants (SRDs). The new tenants can quickly and easily be added by simply cloning one of the existing SRDs. Once cloned, all you need to do is tweak configuration entities associated with the SRD clone.

  • Page 329: Color-Coding Of Srds In Web Interface

    Tel-to-IP and IP-to-Tel calls. You can also configure various optional features for the SIP Interface such as assigning it a Media Realm, blocking calls received on the SIP Interface from users not registered with the device, and enabling direct media. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 330 Mediant 1000B Gateway and E- SBC Each SIP Interface can be associated with only one SRD. As the SRD configuration entity represents your VoIP deployment SIP network (Layer 5), you need to associate your SIP Interfaces with a specific SRD in order to represent your Layer-3 networks. For most deployments (except multi-tenant deployments), your SRD represents your entire network and thus, only one SRD is required.
  • Page 331 [SIPInterface_InterfaceN "SIPInterface_<row index>" (e.g., "SIPInterface_1" when added to Index ame] Network Interface Assigns a Control-type IP network interface to the SIP Interface. By default, no value is defined (None). network-interface [SIPInterface_NetworkInt Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 332 Mediant 1000B Gateway and E- SBC Parameter Description erface] For configuring network interfaces, see 'Configuring IP Network Interfaces' on page 135. Note: The parameter is mandatory. Application Type Defines the application for which the SIP Interface is used.  application-type [0] GW = (Default) Gateway application.
  • Page 333 [0] Disable = Device does not request the client certificate for TLS Authentication] connection on the SIP Interface.  [1] Enable = Device requires receipt and verification of the client certificate to establish the TLS connection on the SIP Interface. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 334 Mediant 1000B Gateway and E- SBC Parameter Description Block Unregistered Enables the device to block (reject) incoming calls (INVITE requests) Users from unregistered users belonging to the SIP Interface.  block-un-reg-users [-1] Not Configured = (Default) The corresponding parameter in the...
  • Page 335 The parameter is applicable only to SBC calls. Message Policy Assigns a SIP message policy to the SIP interface. For configuring SIP Message Policy rules, see 'Configuring SIP Message message-policy Policy Rules'. [SIPInterface_MessageP olicyName] Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 336: Configuring Ip Groups

    (see Configuring Number Manipulation Tables on page 457).  Included in routing decisions by a third-party routing server or AudioCodes ARM. If deemed necessary for routing, the routing server can even create an IP Group. For more information, see Centralized Third-Party Routing Server or ARM on page 270.
  • Page 337 Click Add; the following dialog box appears: Figure 17-10: IP Group Table - Add Row Dialog Box Configure an IP Group according to to the parameters described in the table below. Click Add. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 338 Mediant 1000B Gateway and E- SBC Table 17-6: IP Group Table Parameter Descriptions Parameter Description Common Parameters Index Defines an index for the new table row. [IPGroup_Index] Note: Each row must be configured with a unique index. Assigns an SRD to the IP Group.
  • Page 339 [IPGroup_MediaRealm] By default, no value is defined (None). For configuring Media Realms, see Configuring Media Realms on page 313. Notes:  For the parameter to take effect, a device reset is required. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 340 Mediant 1000B Gateway and E- SBC Parameter Description  If you delete a Media Realm from the Media Realm table that is assigned to the IP Group, the parameter value reverts to None. SIP Group Name Defines the SIP Request-URI host name in INVITE and REGISTER...
  • Page 341 [0] Standard = INVITE messages that are generated as a result of Transfer or Redirect are sent directly to the URI, according to the Refer-To header in the REFER message or Contact header in the Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 342 Mediant 1000B Gateway and E- SBC Parameter Description 3xx response.  [1] Proxy = Sends a new INVITE to the Proxy. This is applicable only if a Proxy server is used and the parameter AlwaysSendtoProxy is set to 0. ...
  • Page 343 If no contact answers, the call fails or is routed to an alternative destination, if configured. Note: The device can also fork INVITE messages received for a Request-URI of a specific contact (user) registered in the database to Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 344 Mediant 1000B Gateway and E- SBC Parameter Description all other users located under the same AOR as the specific contact. This is configured using the SBCSendInviteToAllContacts parameter. Inbound Message Assigns a Message Manipulation Set (rule) to the IP Group for SIP Manipulation Set message manipulation on the inbound leg.
  • Page 345 The valid value is a string of up to 51 characters. By default, no IPGroup_Password] password is defined. Notes:  The parameter is applicable only to Server-type IP Groups and when the 'Authentication Mode' parameter is set to SBC as Server (i.e., Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 346 Mediant 1000B Gateway and E- SBC Parameter Description 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. Source URI Input Defines the SIP header in the incoming INVITE that is used for call matching characteristics based on source URIs.
  • Page 347 (gateway) if registered with the device; otherwise, the field is blank. Note: The field is applicable only to Gateway-type IP Groups (i.e., the 'Type' parameter is configured to Gateway). GW Group Registered (Read-only field) Displays whether the IP Group entity (gateway) is Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 348: Configuring Proxy Sets

    Mediant 1000B Gateway and E- SBC Parameter Description Status registered with the device ("Registered" or "Not Registered"). Note: The field is applicable only to Gateway-type IP Groups (i.e., the 'Type' parameter is configured to Gateway). 17.5 Configuring Proxy Sets The Proxy Sets table lets you configure up to 102 Proxy Sets. A Proxy Set defines the address and transport type (e.g., UDP or TCP) of a SIP server (e.g., SIP proxy and SIP...
  • Page 349 Click Add; the following dialog box appears: Figure 17-12: Proxy Address Table - Add Row Dialog Box Configure the address of the Proxy Set according to the parameters described in the table below. Click Add. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 350 Mediant 1000B Gateway and E- SBC Table 17-7: Proxy Sets Table and Proxy Address Table Parameter Description Parameter Description Proxy Sets Table Index Defines an index number for the new table row. configure voip > Note: Each row must be configured with a unique index.
  • Page 351 Note: The parameter is applicable only if the 'Proxy Keep-Alive' parameter AliveTime] is set to Using Options. Redundancy Mode Determines whether the device switches from a redundant proxy to the primary proxy when the primary proxy becomes available again. proxy- Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 352 Mediant 1000B Gateway and E- SBC Parameter Description  [-1] Not configured = (Default) Proxy redundancy method is according redundancy-mode to the settings of the global parameter, ProxyRedundancyMode. [ProxySet_ProxyRedu  [0] Parking = The device continues operating with the redundant (now ndancyMode] active) proxy even if the primary proxy returns to service.
  • Page 353 Set. If a SIP response is received and this response code is defined in the 'Keep-Alive Failure Responses' parameter (in this table), the device assumes the proxy is down and sends the message again; otherwise, Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 354 Mediant 1000B Gateway and E- SBC Parameter Description the device assumes the proxy is up and does not send the message again. Each time a defined response code is received, the device re- sends the message. This can occur until a user-defined maximum...
  • Page 355 Defines the transport type for communicating with the proxy.  transport-type [0] UDP  [1] TCP [ProxyIp_TransportTy  [2] TLS  [-1] = (Default) The transport type is according to the settings of the global parameter, SIPTransportType. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 356 Mediant 1000B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-27044...

  • Page 357: Sip Definitions

    'UserName' and 'Password' parameters on the Proxy & Registration page The following procedure describes how to configure Accounts through the Web interface. You can also configure it through ini file (Account) or CLI (configure voip > sip-definition account). Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 358 Mediant 1000B Gateway and E- SBC  To configure an Account: Open the Account table (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 359 "served" entry in the table. If a matching row exists, the device authenticates the INVITE by providing the corresponding MD5 authentication username and password to the "serving" IP Group.  [1] Regular = Regular registration process. For more information, see Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 360: Regular Registration Mode

    Mediant 1000B Gateway and E- SBC Parameter Description 'Regular Registration Mode' on page 360.  [2] GIN = Registration for legacy PBXs, using Global Identification Number (GIN). For more information, see 'Single Registration for Multiple Phone Numbers using GIN' on page 360.
  • Page 361 'gin'. The Supported header contains the token 'path' and the URI in the Contact header contains the parameter 'bnc' without a user part: Contact: <sip:198.51.100.3;bnc>; The figure below illustrates the GIN registration process: The figure below illustrates an incoming call using GIN: Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 362: Configuring Proxy And Registration Parameters

    Mediant 1000B Gateway and E- SBC 18.3 Configuring Proxy and Registration Parameters The Proxy & Registration page allows you to configure the Proxy server and registration parameters. For a description of the parameters appearing on this page, see 'Configuration Parameters Reference' on page 881.

  • Page 363: Sip Message Authentication Example

    SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 10.2.1.200 From: <sip:122@10.2.2.222 >;tag=1c17940 To: <sip:122@10.2.2.222 > Call-ID: 634293194@10.1.1.200 Cseq: 1 REGISTER Date: Mon, 30 Jul 2012 15:33:54 GMT Server: Columbia-SIP-Server/1.17 Content-Length: 0 WWW-Authenticate: Digest realm="audiocodes.com", nonce="11432d6bce58ddf02e3b5e1c77c010d2", stale=FALSE, algorithm=MD5 Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 364 • 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 365: Configuring Sip Message Manipulation

    These elements can include SIP headers, SIP header parameters, and SDP body fields. The SIP message manipulation feature supports the following:  Manipulation on SIP message type (Method, Request/Response, and Response type) Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 366 Mediant 1000B Gateway and E- SBC  Addition of new SIP headers  Removal of SIP headers ("black list")  Modification of SIP header components such as values, header values (e.g., URI value of the P-Asserted-Identity header can be copied to the From header), call's parameter values ...
  • Page 367 User's Manual 18. SIP Definitions The figure below illustrates a SIP message manipulation example: Figure 18-2: SIP Header Manipulation Example Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 368 Mediant 1000B Gateway and E- SBC Notes: • For a detailed description of the syntax used for configuring Message Manipulation rules, refer to the SIP Message Manipulations Quick Reference Guide. • For the SBC application, Inbound message manipulation is done only after the Classification, inbound/outbound number manipulations, and routing processes.
  • Page 369 = rule applies to SUBSCRIBE confirmation responses Note: Currently, SIP 100 Trying messages cannot be manipulated. Condition Defines the condition that must exist for the rule to apply. The valid value is a string (case-insensitive). condition Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 370 Mediant 1000B Gateway and E- SBC Parameter Description [MessageManipulations_ For example: Condition]  header.from.url.user== '100' (indicates that the user part of the From header must have the value "100")  header.contact.param.expires > '3600'  header.to.url.host contains 'domain'  param.call.dst.user != '100'...

  • Page 371: Configuring Sip Message Policy Rules

    You can also configure it through ini file (MessagePolicy) or CLI (configure voip > sbc message-policy).  To configure SIP Message Policy rules: Open the Message Policy table (Configuration tab > VoIP menu > SIP Definitions > Msg Policy & Manipulation > Message Policy Table). Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 372 Mediant 1000B Gateway and E- SBC Click Add; the following dialog box appears: Figure 18-5: Message Policy Table - Add Row Dialog Box Configure a Message Policy rule according to the parameters described in the table below. Click Add. Table 18-3: Message Policy Table Parameter Descriptions...
  • Page 373 'Body List' parameter (above). body-list-type  [0] Policy Blacklist =The specified SIP body is rejected. [MessagePolicy_BodyLis  [1] Policy Whitelist = (Default) Only the specified SIP body is allowed; tType] the others are rejected. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 374 Mediant 1000B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-27044...

  • Page 375: Coders And Profiles

    Notes: • Some coders are license-dependent and are available only if purchased from AudioCodes and included in the Software License Key installed on your device. For more information, contact your AudioCodes sales representative. • Only the packetization time of the first coder in the coder list is declared in INVITE/200 OK SDP, even if multiple coders are defined.
  • Page 376 Mediant 1000B Gateway and E- SBC  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.
  • Page 377 [1] Enable  [0] Disable GSM-EFR 0, 20 (default), 30, 40, 50, 12.2 Dynamic [gsmEnhancedFull 60, 80, 100  [1] Enable Rate]  [0] Disable MS-GSM 40 (default) [gsmMS]  [1] Enable Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 378 Mediant 1000B Gateway and E- SBC Coder Name Packetization Time (msec) Rate (kbps) Payload Silence Type Suppression   [0] 4.75 [0] Disable 20 (default) Dynamic [Amr]   [1] 5.15 [1] Enable  [2] 5.90  [3] 6.70 ...

  • Page 379: Configuring Coder Groups

    Profiles or IP Profiles, see 'Configuring Default Coders' on page 375. This group of coders is termed the Default Coder Group. • For a list of supported coders, see 'Configuring Default Coders' on page 375. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 380 Mediant 1000B Gateway and E- SBC The following procedure describes how to configure the Coders table through the Web interface. You can also configure it through ini file (CodersGroup) or CLI (configure voip > coders-and-profiles coders-group).  To configure a Coder Group: Open the Coder Group Settings page (Configuration tab >...

  • Page 381: Configuring Tel Profile

     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: Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 382 Mediant 1000B Gateway and E- SBC Configure a Tel Profile according to the parameters described in the table below. For a description of each parameter, refer to the corresponding "global" parameter. Click Add. Table 19-4: Tel Profile Table Parameters and Corresponding Global Parameters...
  • Page 383 [TelProfile_SigIPDiffServ] Enable Early Media EnableEarlyMedia early-media [TelProfile_EnableEarlyMedia] Progress Indicator to IP ProgressIndicator2IP prog-ind-to-ip [TelProfile_ProgressIndicator2IP] Channel Dynamic Jitter Buffer Minimum Delay DJBufMinDelay jitter-buffer-minimum-delay [TelProfile_JitterBufMinDelay] Dynamic Jitter Buffer Optimization Factor DJBufOptFactor jitter-buffer-optimization- factor [TelProfile_JitterBufOptFactor] Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 384 Mediant 1000B Gateway and E- SBC Tel Profile Parameter Global Parameter DTMF Volume DTMFVolume dtmf-volume [TelProfile_DtmfVolume] Input Gain InputGain input-gain [TelProfile_InputGain] Voice Volume VoiceVolume voice-volume [TelProfile_VoiceVolume] Echo Canceler EnableEchoCanceller echo-canceller [TelProfile_EnableEC] Enable AGC EnableAGC enable-agc [TelProfile_EnableAGC] EC NLP Mode ECNLPMode...

  • Page 385: Configuring Ip Profiles

     To configure an IP Profile: Open the IP Profile Settings table (Configuration tab > VoIP menu > Coders and Profiles > IP Profile Settings). Click Add; the following dialog box appears: Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 386 Mediant 1000B Gateway and E- SBC Configure an IP Profile according to the parameters described in the table below. Click Add. Table 19-5: IP Profile Settings Table Parameter Descriptions Parameter Description Common Index Defines an index number for the new table row.
  • Page 387 When enabled, you can configure the payload type, using the RFC2198PayloadType parameter.  For the Gateway application only: The RTP redundancy dynamic payload type can be included in the SDP, by using the EnableRTPRedundancyNegotiation parameter.  The corresponding global parameter is Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 388 Mediant 1000B Gateway and E- SBC Parameter Description RTPRedundancyDepth. Echo Canceler Enables the device's Echo Cancellation feature (i.e., echo from voice calls is removed). echo-canceller  [0] Disable [IpProfile_EnableEchoCanceller]  [1] Line (default) For a detailed description of the Echo Cancellation feature, see Configuring Echo Cancellation on page 176.
  • Page 389 The IP addressing version is determined according to the first SDP "m=" field.  The feature is applicable to any type of media (e.g., audio and video) that has an IP address.  The corresponding global parameter is Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 390 Mediant 1000B Gateway and E- SBC Parameter Description MediaIPVersionPreference. Symmetric MKI Enables symmetric MKI negotiation.  enable-symmetric-mki [0] Disable = (Default) The device includes the MKI in its SIP 200 OK response according to the SRTPTxPacketMKISize [IpProfile_EnableSymmetricMKI] parameter (if set to 0, it is not included; if set to any other value, it is included with this value).
  • Page 391 For any Parameter Suite other than 0, the valid range is 0 to 15, where 0 is for best detection of an answering machine and 15 for best detection of a live call. Note: The corresponding global parameter is AMDSensitivityLevel. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 392 Mediant 1000B Gateway and E- SBC Parameter Description AMD Max Greeting Time Defines the maximum duration (in 5-msec units) that the device can take to detect a greeting message. amd-max-greeting-time The valid range value is 0 to 51132767. The default is 300.
  • Page 393 ISDN Information messages received by the device for each digit are sent in the voice channel to the IP network as DTMF signals, according to the settings of the parameter. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 394 Mediant 1000B Gateway and E- SBC Parameter Description  The corresponding global parameter is FirstTxDTMFOption. Second Tx DTMF Option Defines the second preferred transmit DTMF negotiation method. For a description, see IpProfile_FirstTxDtmfOption second-tx-dtmf-option (above). [IpProfile_SecondTxDtmfOption] Note: The corresponding global parameter is SecondTxDTMFOption.
  • Page 395 G.711 coders is a standard one (8 for G.711 A-Law and 0 for G.711 -Law). The parameters defining payload type for the 'old' Bypass mode FaxBypassPayloadType and ModemBypassPayloadType are not used with NSE Bypass. The Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 396 Mediant 1000B Gateway and E- SBC Parameter Description bypass packet interval is configured according to the FaxModemBypassBasicRtpPacketInterval parameter. 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 397 Digital: For IP-to-Tel calls, if the parameter EnableEarlyMedia is set to 1, the device sends 180 Ringing with SDP in response to an ISDN Alerting or it sends a 183 Session Progress message with SDP in Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 398 Mediant 1000B Gateway and E- SBC Parameter Description response to only the first received ISDN Proceeding or Progress message after a call is placed to PBX/PSTN over the trunk.  [8] PI = 8: same as PI = 1. Note: The corresponding global parameter is ProgressIndicator2IP.
  • Page 399 Q.931 Setup message to the Tel. 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 Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 400 Mediant 1000B Gateway and E- SBC Parameter Description number to the SIP Diversion header, and then performs IP-to- Tel destination phone number manipulation. Thus, the called (i.e., SIP To header) and redirect (i.e., SIP Diversion header) numbers are different. Note: The corresponding global parameter is CopyDest2RedirectNumber.
  • Page 401 [0] Not Supported = UPDATE message is not supported. [IpProfile_SBCRemoteUpdateSu  [1] Supported Only After Connect = UPDATE message is pport] supported only after the call is connected.  [2] Supported = (Default) UPDATE message is supported Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 402 Mediant 1000B Gateway and E- SBC Parameter Description during call setup and after call establishment. Remote re-INVITE Defines whether the destination UA of the re-INVITE request supports re-INVITE messages and if so, whether it supports re- sbc-rmt-re-invite-supp INVITE with or without SDP.
  • Page 403  [2] IP Group Name = Sets the host part in the REFER message to the name defined for the IP Group (in the IP Group table). Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 404 Mediant 1000B Gateway and E- SBC Parameter Description  [3] Handle Locally = Handles the incoming REFER request itself without forwarding the REFER. The device generates a new INVITE to the alternative destination according to the rules in the IP-to-IP Routing table (the 'Call Trigger' field must be set to REFER).
  • Page 405 (e.g., INVITE) using one or more alternative URIs included in the 3xx response. The device sends the new request to the alternative destination according to the IP-to-IP Routing table (the 'Call Trigger' field must be set to 3xx). Notes: Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 406 Mediant 1000B Gateway and E- SBC Parameter Description  When the parameter is changed from 1 to 0, new 3xx Contact headers remain unchanged. However, requests with the special prefix continue using the device's database to locate the new destination.
  • Page 407 The device forwards 18x and RTP as is. aRTP]  [1] By Media = After sending 18x response, the remote client waits before sending RTP (e.g., Microsoft Lync environment). For the device's handling of this remote UA support, see Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 408 Mediant 1000B Gateway and E- SBC Parameter Description Interworking SIP Early Media on page 612. Remote RFC 3960 Support Defines whether the destination UA is capable of receiving 18x messages with delayed RTP. sbc-rmt-rfc3960-supp  [0] Not Supported = (Default) UA does not support receipt of [IpProfile_SBCRemoteSupportsR 18x messages with delayed RTP.
  • Page 409 [-1] According to Operation Mode = (Default) Depends on the setting of the 'Operation Mode' in the IP Group or SRD table:  B2BUA: Device operates as if the parameter is set to Disable [0]. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 410 Mediant 1000B Gateway and E- SBC Parameter Description  Call State-full Proxy: Device operates as if the parameter is set to Enable [1].  [0] Disable = Device removes the Record-Route headers received in requests and responses from the other side, in the outgoing SIP message sent to the SIP entity.
  • Page 411 Coders. The coders in the original SDP offer are listed after the Allowed coders.  [2] Restriction and Preference = Performs both Restriction and Preference. Notes:  The parameter is applicable only if Allowed coders are Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 412 Mediant 1000B Gateway and E- SBC Parameter Description assigned to the IP Profile (using the 'Allowed Coders' or 'Allowed Video Coders Group ID' parameters).  For more information on the Allowed Coders feature, see Restricting Coders on page 598. Allowed Video Coders Assigns an Allowed Video Coders Group.
  • Page 413 DTMF packets (RFC 2833), detection and generation of DTMF methods requires DSP resources. RFC 2833 DTMF Payload Type Defines the payload type of DTMF digits for the SIP entity Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 414 Mediant 1000B Gateway and E- SBC Parameter Description sbc-2833dtmf-payload associated with the IP Profile. This enables the interworking of the DTMF payload type for RFC 2833 between different SBC call [IpProfile_SBC2833DTMFPayloa legs. For example, if two entities require different DTMF payload...
  • Page 415 [2] Preferred Value= Use preferred ptime for negotiation, if configured by the 'Preferred Ptime' parameter. Preferred Ptime Defines the packetization time (in msec) for the SIP entity associated with the IP Profile if the 'SBC SDP Ptime Answer' sbc-preferred-ptime Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 416 Mediant 1000B Gateway and E- SBC Parameter Description [IpProfile_SBCPreferredPTime] parameter (see above) is set to Preferred Value. The valid range is 0 to 200. The default is 0 (i.e., preferred ptime is not used). Use Silence Suppression Defines silence suppression support for the SIP entity associated...
  • Page 417 RTCP attribute (regardless if present or not).  [1] Add = The device adds the 'a=rtcp' attribute to the outgoing SDP offer sent to the SIP entity if the attribute was Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 418 Mediant 1000B Gateway and E- SBC Parameter Description not present in the original incoming SDP offer.  [2] Remove = The device removes the 'a=rtcp' attribute, if present in the incoming SDP offer received from the other SIP entity, before sending the outgoing SDP offer to the SIP entity.
  • Page 419 596. Note: If you enable direct media for the IP Profile, make sure that your Media Realm provides sufficient ports, as media may traverse the device for mid-call services (e.g., call transfer). Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 420 Mediant 1000B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-27044...

  • Page 421: Gateway Application

    Part V Gateway Application...

  • Page 423: Introduction

    CO or the PBX) and connects to analog telephones, dial-up modems, and fax machines. The FXS is designed to supply line voltage and ringing current to these telephone devices. An FXS VoIP device interfaces between the analog telephone devices and the Internet. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 424: Call Processing Summary

    Mediant 1000B Gateway and E- SBC 20.1 Call Processing Summary The device's call processing for Gateway calls is shown in the following flowcharts.  IP-to-Tel Call: Figure 20-1: IP-to-Tel Call Processing Flowchart User's Manual Document #: LTRT-27044...
  • Page 425 User's Manual 20. Introduction  Tel-to-IP Call: Figure 20-2: Tel-to-IP Call Processing Flowchart Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 426 Mediant 1000B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-27044...

  • Page 427: Digital Pstn

    Creating a Loopback Line: You can create (and remove) remote loopback for DS1 lines. This is done by clicking the Create Loopback button. To remove the loopback, click the Remove Loopback button. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 428 Release Notes). • The ISDN BRI North American variants (NI-2, DMS-100, and 5ESS) are partially supported by the device. Please contact your AudioCodes sales representative before implementing this protocol. • 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.
  • Page 429 The bar initially displays the first eight trunk number icons (i.e., trunks 1 through 8). To scroll through the trunk number icons (i.e., view the next/last or previous/first group of eight trunks), see the figure below: Figure 21-1: Trunk Scroll Bar (Used Only as an Example) Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 430 Mediant 1000B Gateway and E- SBC Note: If the Trunk scroll bar displays all available trunks, the scroll bar buttons are unavailable. After you have selected a trunk, the following is displayed: • The read-only 'Module ID' field displays the module number to which the trunk belongs.

  • Page 431: Tdm And Timing

    This section provides a brief description for configuring synchronization based on recovering clock from the PSTN line interface. For a full description of the clock parameters, see 'PSTN Parameters' on page 1027. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 432: Configuring Internal Clock As Clock Source

    Mediant 1000B Gateway and E- SBC  To configure synchronization based on clock from PSTN line: In the TDM Bus Settings page, do the following: Set the 'TDM Bus Clock Source' parameter (TDMBusClockSource) to Network to recover the clock from the line interface.

  • Page 433: Configuring Cas State Machines

    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 705). Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 434 Mediant 1000B Gateway and 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 435 Defines which Signaling System to use in both directions [CasStateMachineDigitSign (detection\generation). alingSystem]  [0] DTMF = Uses DTMF signaling.  [1] MF = Uses MF signaling (default).  [-1] Default = Default value - use value from CAS state machine. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 436: Configuring Digital Gateway Parameters

    Mediant 1000B Gateway and 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 881.  To configure the digital gateway parameters: Open the Digital Gateway Parameters page (Configuration tab >...

  • Page 437: Tunneling Applications

    Time between successive INVITEs sent from the same trunk.  Time between call release and the new INVITE that is sent on the same channel. The call can be released if the device receives a 4xx or 5xx response. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 438 Mediant 1000B Gateway and E- SBC By utilizing the ‘Profiles’ mechanism (see 'Coders and Profiles' on page 375), you can configure the TDM Tunneling feature to choose different settings based on a timeslot or groups of timeslots. For example, you can use low-bit-rate vocoders to transport voice and ‘Transparent’...
  • Page 439 TrunkGroup 0 = 0,3,3,16,16,7003,2; [\TrunkGroup] [ CodersGroup0 ] FORMAT CodersGroup0_Index = CodersGroup0_Name, CodersGroup0_pTime, CodersGroup0_rate, CodersGroup0_PayloadType, CodersGroup0_Sce, CodersGroup0_CoderSpecific; CodersGroup0 0 = g7231; CodersGroup0 1 = Transparent; [ \CodersGroup0 ] [TelProfile] FORMAT TelProfile_Index = TelProfile_ProfileName, TelProfile_TelPreference, TelProfile_CodersGroupID, Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 440: Dsp Pattern Detector

    Mediant 1000B Gateway and E- SBC 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] 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.
  • Page 441 INFO message with Setup Ack encapsulated in its MIME body. The PBX sends QSIG Information messages (to complete the Called Party Number) only after it receives the Setup Ack. The device relays these Information messages encapsulated in SIP INFO messages to the remote party. Version 7.0 Mediant 1000B Gateway and E- SBC...

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

    Mediant 1000B Gateway and E- SBC 21.6 ISDN Non-Facility Associated Signaling (NFAS) In regular T1 ISDN trunks, a single 64 kbps channel carries signaling for the other 23 B- channels of that particular T1 trunk. This channel is called the D-channel and usually resides on timeslot # 24.

  • Page 443: Working With Dms-100 Switches

    NFASGroupNumber_1 = 1 NFASGroupNumber_2 = 1 NFASGroupNumber_3 = 1 DchConfig_0 = 0 ;Primary T1 trunk DchConfig_1 = 2 ;B-Channel NFAS trunk DchConfig_2 = 2 ;B-Channel NFAS trunk DchConfig_3 = 2 ;B-channel NFAS trunk Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 444: Creating An Nfas-Related Trunk Configuration

    Mediant 1000B Gateway and E- SBC 21.6.3 Creating an NFAS-Related Trunk Configuration The procedures for creating and deleting an NFAS group must be performed in the correct order, as described below.  To create an NFAS Group: If there’s a backup (‘secondary’) trunk for this group, it must be configured first.

  • Page 445: Isdn Overlap Dialing

    A match is found with the defined digit map (configured by the DigitMapping parameter). Relevant parameters (described in 'PSTN Parameters' on page 1027):  ISDNRxOverlap_x = 1 (can be configured per trunk)  TimeBetweenDigits  MaxDigits Version 7.0 Mediant 1000B Gateway and E- SBC...

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

    Mediant 1000B Gateway and E- SBC  MuteDTMFInOverlap  DigitMapping For configuring ISDN overlap dialing using the Web interface, see 'Configuring Trunk Settings' on page 427. 21.7.2 Interworking ISDN Overlap Dialing with SIP According to RFC 3578 With overlap dialing disabled, the device expects to receive the digits all at once (enbloc) or with very little delay between digits and then sends the complete number in a single message.
  • Page 447 USER SENDING COMPLETE [2]. For more information on the above mentioned parameters, see PSTN Parameters on page 1027. For configuring ISDN overlap dialing using the Web interface, see ''Configuring Trunk Settings'' on page 427. Version 7.0 Mediant 1000B Gateway and E- SBC...

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

    Mediant 1000B Gateway and E- SBC 21.8 Redirect Number and Calling Name (Display) The following tables define the device's redirect number and calling name (Display) support for various ISDN variants according to NT (Network Termination) / TE (Termination Equipment) interface direction:...

  • Page 449: Trunk Groups

    To unregister the Trunk Groups, click the Unregister button, located below the Trunk Group table. Table 22-1: Trunk Group Table Parameter Descriptions Parameter Description Module Defines the telephony interface module for which you want to define the Trunk Group. module [TrunkGroup_Module] Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 450 Mediant 1000B Gateway and E- SBC Parameter Description From Trunk Defines the starting physical Trunk number in the Trunk Group. The number of listed Trunks depends on the device's hardware first-trunk-id configuration. [TrunkGroup_FirstTrunkId] Note: The parameter is applicable only to PRI and BRI modules.

  • Page 451: Configuring Trunk Group Settings Table

    To configure Trunk Group settings: Open the Trunk Group Settings table (Configuration tab > VoIP menu > Gateway > Trunk Group > Trunk Group Settings). Click Add; the following dialog box appears: Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 452 Mediant 1000B Gateway and E- SBC Configure a Trunk Group according to the parameters described in the table below. Click Add. Table 22-2: Trunk Group Settings Table Parameter Descriptions Parameter Description Index Defines an index number for the new table row.
  • Page 453 FXS ports (channels) in the Hunt Group (i.e., a ringing group). When a call is received for the Hunt Group, all telephones connected to the FXS ports belonging to the Hunt Group start Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 454 Mediant 1000B Gateway and E- SBC Parameter Description ringing. The call is eventually received by whichever telephone first answers the call (after which the other phones stop ringing). This option is applicable only to FXS interfaces.  [10] Select Trunk by Supplementary Services Table = The BRI...
  • Page 455 If the PreferRouteTable parameter is set to 1 (see 'Configuring Proxy and Registration Parameters' on page 362), the routing rules in the Tel-to-IP Routing table take precedence over the selected Serving IP Group ID. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 456 Mediant 1000B Gateway and E- SBC Parameter Description MWI Interrogation Type Defines message waiting indication (MWI) QSIG-to-IP interworking for interrogating MWI supplementary services: mwi-interrogation-  type [255] Not Configured  [0] None = Disables the feature. [TrunkGroupSettings_MWI InterrogationType]  [1] Use Activate Only = MWI Interrogation messages are not sent and only "passively"...

  • Page 457: Manipulation

    1 and "55" for rule index 2, the device uses rule index 1 for numbers that start with 551 and uses rule index 2 for numbers that start with 550, 552, 553, and so on until 559. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 458 Mediant 1000B Gateway and E- SBC 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 numbers that start with 551.
  • Page 459 Rule 5: When the destination number has the prefix 6, 7, or 8 (e.g., 85262146), source number prefix 2001, it is changed to 3146. Parameter Rule 1 Rule 2 Rule 3 Rule 4 Rule 5 Destination [6,7,8] Prefix Source Prefix 1001 123451001# [30-40]x 2001 Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 460 Mediant 1000B Gateway and E- SBC Parameter Rule 1 Rule 2 Rule 3 Rule 4 Rule 5 Stripped Digits from Left Stripped Digits from Right Prefix to Add Suffix to Add Number of Digits to Leave Presentation Allowed Restricted Table 23-1: Number Manipulation Tables Parameter Descriptions...
  • Page 461 For example, if you enter 9 and the phone number prefix-to-add is 1234, the new number is 91234. [Prefix2Add] Suffix to Add Defines the number or string that you want added to the end of the Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 462 Mediant 1000B Gateway and E- SBC Parameter Description suffix-to-add telephone number. For example, if you enter 00 and the phone number is 1234, the new number is 123400. [Suffix2Add] Defines the Type of Number (TON).  If you selected 'Unknown' for the NPI, you can select Unknown [0].

  • Page 463: Manipulating Number Prefix

    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 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 464: Sip Calling Name Manipulations

    Mediant 1000B Gateway and 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 465 100, 101 or 105. You can also use the $ sign to denote calls without a calling number. For a description of available notations, see 'Dialing Plan Notation for Routing and Manipulation Tables' on page 877. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 466 Mediant 1000B Gateway and E- SBC Parameter Description The default value is the asterisk (*) symbol (i.e., any source prefix). Calling Name Prefix Defines the caller name (i.e., caller ID) prefix. You can use special notations for denoting the prefix. For example, to calling-name-prefix denote calls without a calling name, use the $ sign.

  • Page 467: Configuring Redirect Number Ip To Tel

    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. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 468 Mediant 1000B Gateway and E- SBC • The device uses the 'Redirect Prefix' parameter before it manipulates the prefix. The following procedure describes how to configure redirect number manipulation rules through the Web interface. You can also configure these rules using the following management tools: ...
  • Page 469 For example, if you enter 3 and the redirect number is remove-from-left 5551234, the new number is 1234. [_RemoveFromLeft] Stripped Digits From Right Defines the number of digits to remove from the right of the redirect Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 470 Mediant 1000B Gateway and E- SBC Parameter Description remove-from-right number prefix. For example, if you enter 3 and the redirect number is 5551234, the new number is 5551. [_RemoveFromRight] Number of Digits to Leave Defines the number of digits that you want to retain from the right of the redirect number.

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

    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 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.80A.227.005 Version 7.0 Mediant 1000B Gateway and E- SBC...

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

    Mediant 1000B Gateway and E- SBC 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 473: Configuring Release Cause Mapping

    Mapping of SIP Response to ISDN Release Reason' on page 474. When the device receives a SIP response from the IP side, it searches the table for a matching SIP response. If found, the device sends the corresponding Q.850 Release Cause to the Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 474 Mediant 1000B Gateway and E- SBC PSTN. If the SIP response is not configured in the table, the default, fixed SIP-to-ISDN release reason mapping is used. Note: For Tel-to-IP calls, you can also map less commonly used SIP responses to a single, default ISDN release cause code, using the DefaultCauseMapISDN2IP parameter.

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

    Not acceptable here Normal, unspecified Server internal error Temporary failure Not implemented Network out of order Bad gateway Network out of order Service unavailable Temporary failure Server timeout Recovery on timer expiry Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 476: Isdn-To-Sip Release Cause Mapping

    Mediant 1000B Gateway and E- SBC ISDN Release Description Description Response Reason 505* Version not supported Interworking Busy everywhere User busy Decline Call rejected Does not exist anywhere Unallocated number 606* Not acceptable Network out of order * Messages and responses were created because the ‘ISUP to SIP Mapping’ draft does not specify their cause code mapping.

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

    No route to network Not found No route to destination Not found Channel unacceptable Not acceptable Call awarded and being delivered in an Server internal error established channel Normal call clearing User busy Busy here Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 478 Mediant 1000B Gateway and E- SBC ISDN Release Description Description Reason Response No user responding Request timeout No answer from the user Temporarily unavailable Call rejected Forbidden Number changed w/o diagnostic Gone Non-selected user clearing Not found Destination out of order...

  • Page 479: Configuring Isdn-To-Isdn Release Cause Mapping

    Cause ISDN to ISDN table and the Release Cause Mapping ISDN to SIP table, the mapping rule with the originally received code in the Release Cause Mapping ISDN to SIP table is ignored; the device uses only the mapping rule in the Release Cause Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 480 Mediant 1000B Gateway and E- SBC Mapping ISDN to SIP table that matches the new ISDN cause code. For example, if you configure a mapping rule in the Release Cause ISDN to ISDN table to change a received 127 code to 16, the device searches for a rule in the Release Cause Mapping ISDN to SIP table for an ISDN code of 16 (ignoring any entry with code 127).

  • Page 481: Reason Header

    The parameter defines Q.931 release causes. Its default value is 3, which is mapped to the SIP 404 response. By changing its value to 34, the SIP 503 response is sent. Other causes can be used as well. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 482: Numbering Plans And Type Of Number

    Mediant 1000B Gateway and 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 483: 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. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 484 Mediant 1000B Gateway and E- SBC You can configure the routing rule with one or more of the following incoming Tel characteristics:  Source Trunk Group (from where the call is received)  Source (calling) and destination (called) telephone number prefix and suffix You can configure the IP destination to one of the following: ...
  • Page 485 SRD. As one of the attributes of a SIP Interface is an SRD and as you can configure multiple SIP Interfaces per SRD, the specific SIP Interface not only determines the above-mentioned attributes, but also the SRD for routing the call. Figure 24-1: Locating SRD Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 486 Mediant 1000B Gateway and E- SBC Note: When using a proxy server, it is unnecessary to configure routing rules in the Tel-to-IP Routing table, unless you require one of the following: • Fallback (alternative) routing when communication with the proxy server fails.
  • Page 487 Notes: • Instead of using the table for Tel-to-IP routing, you can employ a third-party Routing server or AudioCodes ARM to handle the routing decisions. For more information, see Centralized Third-Party Routing Server or ARM on page 270. • You can configure up to three alternative routing rules per "main" routing rule in the Tel-to-IP Routing table.
  • Page 488 Mediant 1000B Gateway and E- SBC associated with Rule 1.  Rule 3 (IP Group destination): For all callers (*), if the called phone number prefix is 20, the call is sent to IP Group "ITSP-ZA". User's Manual Document #: LTRT-27044...
  • Page 489 The valid value is a string of up to 20 characters. By default, no value is defined. [PREFIX_RouteNam Note: Each row must be configured with a unique name. Rule Tab - Matching Call Characteristics Source Trunk Group Defines the Trunk Group from where the call is received. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 490 Mediant 1000B Gateway and E- SBC Parameter Description To denote any Trunk Group, use the asterisk (*) symbol. By default, no Trunk Group is defined (-1). src-trunk- group-id [PREFIX_SrcTrunkG roupID] Source Phone Prefix Defines the prefix and/or suffix of the calling (source) telephone number. You can use special notations for denoting the prefix.
  • Page 491 Defines the transport layer type used for routing the call:  [-1] = (Default) Not defined - transport type is according to the settings of transport-type the global parameter, SIPTransportType. [PREFIX_TransportT  [0] UDP ype] Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 492 Mediant 1000B Gateway and E- SBC Parameter Description  [1] TCP  [2] TLS IP Profile Assigns an IP Profile to the routing rule in the outgoing direction. The IP Profile allows you to assign various configuration attributes (e.g., voice ip-profile-id coder) per routing rule.
  • Page 493 'Destination IP Address' and 'Destination IP Group' fields respectively. For IP Groups, the status indicates the connectivity with the SIP proxy server's address configured for the Proxy Set that is associated with the IP Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 494: Configuring Ip-To-Trunk Group Routing Rules

    Mediant 1000B Gateway and E- SBC Parameter Description Group. For the status to be displayed, the Proxy Keep-Alive feature, which monitors the connectivity with proxy servers per Proxy Set, must be enabled for the Proxy Set (see 'Configuring Proxy Sets' on page 348). If a Proxy Set...
  • Page 495 Notes: • Instead of using the table for IP-to-Tel routing, you can employ a third-party Routing server or AudioCodes ARM to handle the routing decisions. For more information, see Centralized Third-Party Routing Server or ARM on page 270. • You can configure up to three alternative routing rules per "main" routing rule in the table.
  • Page 496 Mediant 1000B Gateway and E- SBC Click Add; the following dialog box appears: Figure 24-3: IP to Trunk Group Table - Add Row Dialog Box Configure a routing rule according to the parameters described in the table below. Click Add.
  • Page 497 100 to 199 and ends with 100, 101 or 105. To denote any prefix, use the asterisk (*) symbol. To denote calls without a calling number, use the $ sign. For a description of available notations, Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 498 Mediant 1000B Gateway and E- SBC Parameter Description see 'Dialing Plan Notation for Routing and Manipulation Tables' on page 877. By default, no value is defined. Note: If the P-Asserted-Identity header is present in the incoming INVITE message, the value of the parameter is compared to the P- Asserted-Identity URI host name (and not the From header).

  • Page 499: Configuring A Gateway Routing Policy Rule

    Click Add; the following dialog box appears: Figure 24-4: Gateway Routing Policy Table - Edit Row Dialog Box Configure the Gateway Routing Policy rule according to the parameters described in the table below. Click Add. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 500 Mediant 1000B Gateway and E- SBC Table 24-5: Gateway Routing Policy Table Parameter Descriptions Parameter Description Index (Read-only) Displays the index number of the table row. [GwRoutingPolicy_Index] Name Defines an arbitrary name to easily identify the row. name The default value is "GwRoutingPolicy".

  • Page 501: Ip Destinations Connectivity Feature

    IP destination, it is resolved into an IP address by a DNS server. The device checks network connectivity and QoS of the resolved IP address. If the DNS host name is unresolved, the device considers the connectivity of the IP destination as unavailable. Version 7.0 Mediant 1000B Gateway and E- SBC...

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

    Mediant 1000B Gateway and E- SBC You can view the connectivity status of IP destinations in the following Web interface pages:  Tel-to-IP Routing table: The connectivity status of the IP destination per routing rule is displayed in the 'Status' column. For more information, see 'Configuring Tel-to-IP Routing Rules' on page 483.

  • Page 503: Alternative Routing Based On Sip Responses

    (configured in the Quality of Experience Profile table) and/or media bandwidth (configured in the Bandwidth profile table). When this occurs, the device sends a SIP 480 (Temporarily Unavailable) response to the SIP entity. This is Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 504 Mediant 1000B Gateway and E- SBC configured by 1) assigning an IP Group a QoE and/or Bandwidth profile that rejects calls if the threshold is crossed, 2) configuring 806 in the Reasons for Tel-to-IP Alternative Routing table and 3) configuring an alternative routing rule.
  • Page 505 Note: Each row must be configured with a unique index. [AltRouteCauseTel2Ip_Ind Release Cause Defines a SIP response code that if received, the device attempts to route the call to an alternative destination (if configured). rel-cause [AltRouteCauseTel2Ip_Rel easeCause] Version 7.0 Mediant 1000B Gateway and E- SBC...

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

    Mediant 1000B Gateway and E- SBC Enable alternative routing based on SIP responses, by setting the 'Redundant Routing Mode' parameter in the Proxy & Registration page to one of the following: • Routing Table: Tel-to-IP Routing table is used for alternative routing.

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

    For analog interfaces: For information on mapping PSTN release causes to SIP responses, see PSTN Release Cause to SIP Response Mapping on page 481. • For mapping SIP-to-Q.931 and Q.931-to-SIP release causes, see Configuring Release Cause Mapping on page 473. Version 7.0 Mediant 1000B Gateway and E- SBC...

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

    Mediant 1000B Gateway and E- SBC The following procedure describes how to configure alternative routing reasons for IP-to- Tel calls through the Web interface. You can also configure it through ini file (AltRouteCauseIP2Tel) or CLI (configure voip/gw routing alt-route-cause-ip2tel). ...
  • Page 509 Defines an index number for the new table row. [ForwardOnBusyTrunkD Note: Each row must be configured with a unique index. est_Index] Trunk Group ID Defines the Trunk Group ID to which the IP call is destined to. trunk-group-id [ForwardOnBusyTrunkD Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 510: Alternative Routing Upon Isdn Disconnect

    SIP Trunk. This is configured using the ini file parameter, TR104FXOSwitchover. Note: For more information on this application, please contact your AudioCodes sales representative. User's Manual...

  • Page 511: Configuring Dtmf And Dialing

    (collected number) upon any of the following scenarios:  Maximum number of digits is received. You can define (using the MaxDigits parameter) the maximum number of collected destination number digits that can be Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 512 Mediant 1000B Gateway and E- SBC received (i.e., dialed) from the 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.

  • Page 513: 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 724. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 514: Interworking Keypad Dtmfs For Sip-To-Isdn Calls

    Mediant 1000B Gateway and E- SBC 25.2 Interworking Keypad DTMFs for SIP-to-ISDN Calls The device can interwork DTMF tones received from the IP to the PSTN, using the ISDN Keypad Facility information element (IE) in Q.931 INFORMATION messages. This feature is applicable only to the Euro ISDN variant (User side).

  • Page 515: Configuring Supplementary Services

    'Configuration Parameters Reference' on page 881.  To configure supplementary services parameters: Open the Supplementary Services page (Configuration tab > VoIP menu > Gateway > DTMF & Supplementary > Supplementary Services). Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 516 Mediant 1000B Gateway and 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 708.

  • Page 517: Call Hold And Retrieve

    (or any other hold tone) is played (over IP) by the remote party. You can also configure the device to keep a call on-hold for a user-defined time after which the call is disconnected, using the HeldTimeout parameter. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 518 Mediant 1000B Gateway and E- SBC The device also supports "double call hold" for FXS interfaces where the called party, which has been placed on-hold by the calling party, can then place the calling party on hold as well and make a call to another destination. The flowchart below provides an example of...

  • Page 519: Call Pickup

    (suspending the call) and then reconnected again (resuming the call). If the phone user does not resume the call within a user-defined interval (configured using the HeldTimeout parameter), the device releases the call. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 520: Consultation Feature

    Mediant 1000B Gateway and E- SBC Note: Only one call can be suspended per trunk. If another suspend request is received from a BRI phone while there is already a suspended call (even if done by another BRI phone connected to the same trunk), the device rejects this suspend request.

  • Page 521: Consultation Transfer For Qsig Path Replacement

    "A" performs a blind transfer to PSTN phone "C". It does this as follows: "A" sends a SIP REFER message (with the phone number of "C" in the Refer-To header) to the device. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 522: Call Forward

    Mediant 1000B Gateway and E- SBC The device sends a Q.931 Setup message to "C". This feature enables manipulating the called party number in this outgoing Setup message. The manipulation is done as follows: If you configure a value for the xferPrefix parameter, then this value (string) is added as a prefix to the number in the Refer-To header.

  • Page 523: Call Forward Reminder Ring

    The reminder-ring tone can be defined by using the parameter CallForwardRingToneID, which points to a ring tone defined in the Call Progress Tone file. The following parameters are used to configure this feature:  EnableNRTSubscription  ASSubscribeIPGroupID  NRTSubscribeRetryTime  CallForwardRingToneID Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 524: Call Forward Reminder (Off-Hook) Special Dial Tone

    Mediant 1000B Gateway and E- SBC 26.6.2 Call Forward Reminder (Off-Hook) Special Dial Tone The device plays a special dial tone (stutter dial tone - Tone Type #15) to a specific FXS endpoint when the phone is off-hooked and when a third-party Application server (AS), e.g., a softswitch is used to forward calls intended for the endpoint, to another destination.

  • Page 525: Bri Call Forwarding

    (Diversion) from the BRI phone, the device indicates the call forwarding service in the Request-URI header using a proprietary parameter “facility=<call forward service>”, where call forward service can be one of the following:  “cfu-activate”: Call Forwarding Unconditional activated  “cfu-deactivate”: Call Forwarding Unconditional deactivated Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 526: Call Waiting

    Mediant 1000B Gateway and E- SBC  “cfb-activate”: Call Forward on Busy activated  “cfb-deactivate”: Call Forward on Busy deactivated  “cfnr-activate”: Call Forward on No Reply activated  “cfnr-deactivate”: Call Forward on No Reply deactivated For example: INVITE sip:400@10.33.2.48;user=phone;facility=cfu-activate SIP/2.0 To enable the feature, configure the UseFacilityInRequest ini file parameter to 1.
  • Page 527 (in the Trunk Group Settings table), which determines the device's handling of MWI Interrogation messages. The process for sending the MWI status upon request from a softswitch is as follows: The softswitch sends a SIP SUBSCRIBE message to the device. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 528: Caller Id

    Mediant 1000B Gateway and E- SBC The device responds by sending an empty SIP NOTIFY to the softswitch, and then sending an ISDN Setup message with Facility IE containing an MWI Interrogation request to the PBX. The PBX responds by sending to the device an ISDN Connect message containing Facility IE with an MWI Interrogation result, which includes the number of voice messages waiting for the specific user.

  • Page 529: Debugging A Caller Id Detection On Fxo

    <IP address of PC to collect the debug traces sent from the device> AddChannelIdTrace ALL-WITH-PCM <port number, which starts from 0> Start Make a call to the FXO. To stop the DR recording, at the CLI prompt, type STOP. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 530: Caller Id On The Ip Side

    FXS port initiates a call and invites two remote IP- based participants. The device also supports multiple, concurrent three-way conference calls. The device supports the following three-way conference modes:  Conference Managed by External, AudioCodes Conferencing (Media) Server: User's Manual Document #: LTRT-27044...
  • Page 531 Conferencing server. This feature includes local mixing and transcoding of the 3-Way Call legs on the device, and even allowing multi-codec conference calls. The number of simultaneous, on-board conferences can be limited using the MaxInBoardConferenceCalls parameter. Each on-board three-way Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 532 Mediant 1000B Gateway and E- SBC conference uses two DSP channels. As one channel is already provided by the FXS port interface to which the calling party (initiator of the three-way conference) is connected, the device obtains an additional DSP channel from another FXS port interface that is idle.

  • Page 533: Emergency E911 Phone Number Services

    The wink can be delayed by configuring the parameter DelayBeforeDIDWink to 200 (for 200 msec or a higher value). The switch detects the wink and then sends the MF Spill digits with ANI and (optional) Pseudo-ANI (P ANI). Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 534 Mediant 1000B Gateway and E- SBC The FXS device collects the MF digits, and then sends a SIP INVITE message to the PSAP with all collected MF digits in the SIP From header as one string. The FXS device generates a mid-call wink signal (two subsequent polarity reversals) toward the E911 tandem switch upon either detection of an RFC 2833 "hookflash"...
  • Page 535 If the device receives the SIP INFO message below, it then generates a "hookflash" mid- call Wink signal: INFO sip:4505656002@192.168.13.40:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.13.2:5060 From: port1vega1 <sip:06@192.168.13.2:5060> To: <sip:4505656002@192.168.13.40:5060>;tag=132878796- 1040067870294 Call-ID: 0010-0016-D69A7DA8-1@192.168.13.2 CSeq:2 INFO Content-Type: application/broadsoft Content-Length: 17 event flashhook Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 536: Fxo Device Interworking Sip E911 Calls From Service Provider's Ip Network To Psap Did Lines

    Mediant 1000B Gateway and E- SBC 26.11.2 FXO Device Interworking SIP E911 Calls from Service Provider's IP Network to PSAP DID Lines The device's FXO interface can interwork SIP emergency E911 calls from the Service Provider's IP network to the analog PSAP DID lines. The standards that define this interface include TR-TSY-000350 or Bellcore’s GR-350-Jun2003.
  • Page 537 None "KPnnSTP" "nn" MF dialed "KPnST" "n" For example: "From: <sip:8>@xyz.com>" generates device MF spill of KP 8 ST Table notes:  For all other cases, a SIP 484 response is sent. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 538 Mediant 1000B Gateway and E- SBC  KP is for .  ST is for #.  STP is for B. The MF duration of all digits, except for the KP digit is 60 msec. The MF duration of the KP digit is 120 msec.

  • Page 539: Pre-Empting Existing Calls For E911 Ip-To-Tel Calls

    For FXO interfaces, the preemption is done only on existing IP-to-Tel calls. In other words, if all the current FXO channels are busy with calls that were answered by the FXO device (i.e., Tel-to-IP calls), new incoming emergency IP-to- Tel calls are rejected. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 540: Multilevel Precedence And Preemption

    Mediant 1000B Gateway and E- SBC 26.12 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 541 Table 5.3.2.12-4 (Mapping of RPH r-priority Field to PRI Precedence Level Value): Table 26-5: 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 Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 542: Mlpp Preemption Events In Sip Reason Header

    Mediant 1000B Gateway and E- SBC MLPP Precedence Level PRI Precedence Level SIP Resource-Priority Header Field Flash Flash Override  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").

  • Page 543: Precedence Ring Tone

    200 OK is received from the remote destination. When a 200 OK is received, a double answer is sent from the FXO line. • Ensure that the PSTN side is configured to identify this double-answer signal. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 544: Configuring Multi-Line Extensions And Supplementary Services

    Mediant 1000B Gateway and E- SBC 26.14 Configuring Multi-Line Extensions and Supplementary Services The Supplementary Services table lets you configure up to 100 supplementary services for endpoints connected to the device. These endpoints include analog FXS phones and Integrated Services Digital Network (ISDN) Basic Rate Interface (BRI) phones.
  • Page 545 'Registration Mode' parameter located in the Trunk Group Settings page (see 'Configuring Trunk Group Settings' on page 451).  To register or un-register an endpoint: Select the required table row in which the endpoint is configured. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 546 Mediant 1000B Gateway and E- SBC From the 'Action' drop-down list, select Register. To unregister the endpoint, select Un-Register. Table 26-6: Supplementary Services Table Parameter Description Parameter Description Index Defines an index number for the new table row. Note: Each row must be configured with a unique index.

  • Page 547: 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 548: Configuring Charge Codes

    Mediant 1000B Gateway and E- SBC If "currency", the following parameters are available: ♦ currency=<string> ♦ currency-type="iso4217-a" or <string> ♦ amount=<number> ♦ multiplier=("0.001","0.01","0.1","1","10","100","1000") If "pulse", the following parameter is available: ♦ recorded-units=<number> • TELES proprietary method • Cirpack proprietary methods For more information on the proprietary methods, see the PayPhoneMeteringMode parameter in 'Metering Tone Parameters' on page 1075.
  • Page 549 Configure a Charge Code according to the parameters described in the table below. Click Add. Table 26-7: Charge Codes Table Parameter Descriptions Parameter Description Index Defines an index number for the new table row. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 550 Mediant 1000B Gateway and E- SBC Parameter Description Note: Each row must be configured with a unique index. [ChargeCode_Index] End Time (1 - 4) Defines the end of the time period in a 24 hour format, hh. For example, "04" denotes 4 A.M.

  • Page 551: Configuring Voice Mail

    To configure the Voice Mail parameters: Open the Voice Mail Settings page (Configuration tab > VoIP menu > Gateway > Advanced Applications > Voice Mail Settings). Configure the parameters as required. Click Submit. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 552 Mediant 1000B Gateway and E- SBC To save the changes to flash memory, see 'Saving Configuration' on page 708. User's Manual Document #: LTRT-27044...

  • Page 553: Converting Accented Characters From Ip To Tel

    Configure a Character Conversion rule according to the parameters described in the table below. Click Add. Table 26-8: Char Conversion Table Parameter Descriptions Parameter Description Index Defines an index number for the new table row. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 554 Mediant 1000B Gateway and E- SBC Parameter Description Note: Each row must be configured with a unique index. [CharConversion_Index] Character Name Defines an arbitrary name to easily identify the row. char-name The valid value is a string of up to 40 characters.

  • Page 555: Analog Gateway

    The activation of each feature remains in effect until it is deactivated (i.e., not deactivated after a call). • For a description of the keypad parameters, see 'Telephone Keypad Sequence Parameters' on page 1076. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 556: Configuring Metering Tones

    Mediant 1000B Gateway and E- SBC  To configure the keypad features Open the Keypad Features page (Configuration tab > VoIP menu > Gateway > Analog Gateway > Keypad Features). Figure 27-1: Keypad Features Page Configure the keypad features as required.

  • Page 557: Configuring Fxo Settings

    The FXO Settings page allows you to configure the device's specific FXO parameters. For a description of these parameters, see 'Configuration Parameters Reference' on page 881. Note: The FXO Settings page is available only for FXO interfaces. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 558: Configuring Authentication

    Mediant 1000B Gateway and E- SBC  To configure the FXO parameters: Open the FXO Settings page (Configuration tab > VoIP menu > Gateway > Analog Gateway > FXO Settings). Figure 27-3: FXO Settings Page Configure the parameters as required.
  • Page 559 (Read-only) Displays the port type (FXS or FXO). [Authentication_PortType] User Name Defines the user name used for authenticating the port. user-name [Authentication_UserId] Password Defines the password used for authenticating the port. password [Authentication_UserPassw ord] Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 560: Configuring Automatic Dialing

    Mediant 1000B Gateway and E- SBC 27.5 Configuring Automatic Dialing The Automatic Dialing table lets you configure telephone numbers that are automatically dialed when FXS or FXO ports go off-hook. The dialing can be done immediately upon off- hook, or after a user-defined interval after off-hook referred to as Hotline dialing.

  • Page 561: Configuring Caller Display Information

    Caller ID display. • If the device detects Caller ID on an FXO line (EnableCallerID = 1), it uses this Caller ID instead of the Caller ID configured in the Caller Display Information table. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 562 Mediant 1000B Gateway and E- SBC The following procedure describes how to configure caller ID through the Web interface. You can also configure it through ini file (CallerDisplayInfo) or CLI (configure voip > gw analoggw caller-display-info).  To configure Caller display: Open the Caller Display Information table (Configuration tab >...

  • Page 563: Configuring Call Forward

    Gateway > Call Forward). Click Add; the following dialog box appears: Figure 27-5: Call Forward Table - Edit Row Dialog Box Configure call forwarding per port according to the parameters described in the table Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 564: Configuring Caller Id Permissions

    Mediant 1000B Gateway and E- SBC below. Click Add. Table 27-4: Call Forward Table Parameter Descriptions Parameter Description Index (Read-only) Displays the index number of the table row. [FwdInfo_Index] Module (Read-only) Displays the module number on which the port is located.
  • Page 565 (Read-only) Displays the port number. [EnableCallerId_Port] Port Type (Read-only) Displays the port type (e.g., FXS). [EnableCallerId_PortType Caller ID Enables Caller ID generation (FXS) or detection (FXO) per port.  [0] Disable caller-id  [1] Enable [EnableCallerId_IsEnable Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 566: Configuring Call Waiting

    Mediant 1000B Gateway and E- SBC 27.9 Configuring Call Waiting The Call Waiting table lets you enable or disable call waiting per FXS port. Notes: • You can enable or disable call waiting for all the device's ports using the global parameter, 'Enable Call Waiting' in the Supplementary Services page (Configuration tab >...

  • Page 567: Rejecting Anonymous Calls

    INVITE message. If this header is not present in the received INVITE, then this feature is used and the tone played is according to the settings in this table. Note: The table is applicable only to FXS interfaces. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 568 Mediant 1000B Gateway and E- SBC The following procedure describes how to configure tones per FXS through the Web interface. You can also configure it through ini file (ToneIndex) or CLI (configure voip > gw analoggw tone-index).  To configure distinctive ringing and call waiting per FXS port: Open the Tone Index table (Configuration tab >...

  • Page 569: Fxs/Fxo Coefficient Types

    FXS Coefficient type. From the 'FXO Coefficient Type' drop-down list (CountryCoefficients), select the required FXO Coefficient type. Click Submit. Save your settings to the flash memory ("burn") with a device reset. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 570: Fxo Operating Modes

    Mediant 1000B Gateway and E- SBC 27.13 FXO Operating Modes This section provides a description of the device's FXO operating modes:  For IP-to-Tel calls (see 'FXO Operations for IP-to-Tel Calls' on page 570)  For Tel-to-IP calls (see 'FXO Operations for Tel-to-IP Calls' on page 572) ...

  • Page 571: Two-Stage Dialing

    Two-stage dialing implements the Dialing Time feature. Dialing Time allows you to define the time that each digit can be separately dialed. By default, the overall dialing time per digit is 200 msec. The longer the telephone number, the greater the dialing time. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 572: Did Wink

    Mediant 1000B Gateway and E- SBC The relevant parameters for configuring Dialing Time include the following:  DTMFDigitLength (100 msec): time for generating DTMF tones to the PSTN (PBX) side  DTMFInterDigitInterval (100 msec): time between generated DTMF digits to PSTN (PBX) side 27.13.1.3...

  • Page 573: Collecting Digits Mode

    Collecting Digits Mode When automatic dialing is not defined, the device collects the digits. The SIP call flow diagram below illustrates the Collecting Digits Mode. Figure 27-11: Call Flow for Collecting Digits Mode Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 574: Fxo Supplementary Services

    Mediant 1000B Gateway and E- SBC 27.13.2.3 FXO Supplementary Services The FXO supplementary services include the following:  Hold / Transfer toward the Tel side: The ini file parameter LineTransferMode must be set to 0 (default). If the FXO receives a hook-flash from the IP side (using out-of-...

  • Page 575: Call Termination Before Call Establishment

    The operation of Ring Detection Timeout depends on the following:  Automatic dialing is disabled and Caller ID is enabled: if the second ring signal is not received for a user-defined time (using the parameter FXOBetweenRingTime), the Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 576 Mediant 1000B Gateway and E- SBC FXO device doesn’t initiate a call to the IP. User's Manual Document #: LTRT-27044...

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

    FXO interfaces with ports connected directly to the PBX lines (shown in the figure below)  FXS interfaces for the 'remote PBX extension'  Analog phones (POTS)  PBX (one or more PBX loop start lines)  LAN network Version 7.0 Mediant 1000B Gateway and E- SBC...

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

    Mediant 1000B Gateway and E- SBC 27.14.1 Dialing from Remote Extension (Phone at FXS) The following procedure describes how to dial from the 'remote PBX extension' (i.e., phone connected to the FXS interface).  To make a call from the FXS interface: Off-hook the phone and wait for the dial tone from the PBX.

  • Page 579: Call Waiting For Remote Extensions

    To configure the FXS interface: In the Trunk Group table (see Configuring Trunk Groups), assign the phone numbers 100 to 104 to the device's endpoints. Figure 27-12: Assigning Phone Numbers to FXS Endpoints Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 580: Fxo Gateway Configuration

    Mediant 1000B Gateway and E- SBC In the Automatic Dialing page (see 'Configuring Automatic Dialing' on page 560), enter the phone numbers of the FXO device in the ‘Destination Phone Number’ fields. When a phone connected to Port #1 off-hooks, the FXS device automatically dials the number ‘200’.
  • Page 581 IP address of the FXS device (10.1.10.3) in the field ‘IP Address’. Figure 27-17: FXO Tel-to-IP Routing Configuration In the FXO Settings page (see 'Configuring FXO Parameters' on page 557), set the parameter ‘Dialing Mode’ to Two Stages (IsTwoStageDial = 1). Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 582 Mediant 1000B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-27044...

  • Page 583: Session Border Controller Application

    Part VI Session Border Controller Application...

  • Page 585: Sbc Overview

    The device's topology hiding is provided by implementing back-to-back user agent (B2BUA) leg routing: • Strips all incoming SIP Via header fields and creates a new Via value for the outgoing message. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 586: B2Bua And Stateful Proxy Operating Modes

    Mediant 1000B Gateway and E- SBC • Each leg has its own Route/Record Route set. • User-defined manipulation of SIP To, From, and Request-URI host names. • Generates a new SIP Call-ID header value (different between legs). • Changes the SIP Contact header and sets it to the device's address.
  • Page 587 SIP specific headers (e.g., Replaces) or in the message bodies (e.g. Dialog Info in an XML body).  In some setups, the SIP client authenticates using a hash that is performed on one or Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 588 Mediant 1000B Gateway and E- SBC more of the headers that B2BUA changes (removes). Therefore, implementing B2BUA would cause authentication to fail.  For facilitating debugging procedures, some administrators require that the value in the Call-ID header remains unchanged between the inbound and outbound SBC legs.

  • Page 589: Call Processing Of Sip Dialog Requests

    URLs are determined, the user and host parts of the URLs can be used as matching rule characteristics for classification, message manipulation, and call routing. • All SIP requests (e.g., INVITE) except REGISTER: Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 590 Mediant 1000B Gateway and E- SBC ♦ Source URL: Obtained from the From header. If the From header contains the value 'Anonymous', the source URL is obtained from the P-Preferred- Identity header. If the P-Preferred-Identity header does not exist, the source URL is obtained from the P-Asserted-Identity header.

  • Page 591: User Registration

    The device provides a dynamic registration database that it updates according to registration requests traversing it. Each database entry for a user represents a binding Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 592: Classification And Routing Of Registered Users

    Mediant 1000B Gateway and E- SBC between an AOR (obtained from the SIP To header), optional additional AORs, and one or more contacts (obtained from the SIP Contact headers). Database bindings are added upon successful registration responses from the proxy server (SIP 200 OK). The device removes database bindings in the following cases: ...

  • Page 593: General Registration Request Processing

    If you configure this grace period, the device keeps the user in the database (and does not send an un-register to the registrar server), allowing the user to send a "late" re-registration to the device. The device removes the Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 594: Registration Restriction Control

    Mediant 1000B Gateway and E- SBC user from the database only when this additional time expires.  The graceful period is also used before removing a user from the registration database when the device receives a successful unregister response (200 OK) from the registrar/proxy server.

  • Page 595: Media Anchoring

    The Media Realm assigned to the leg's IP Group (in the IP Group table) is used. If not assigned to the IP Group, the Media Realm assigned to the leg's SIP Interface (in the SIP Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 596: Direct Media

    Mediant 1000B Gateway and E- SBC Interface table) is used. The following figure provides an example of SDP handling for a call between a LAN IP Phone 10.2.2.6 and a remote IP Phone 212.179.1.13 on the WAN. Figure 28-3: SDP Offer/Answer Example 28.5.2 Direct Media...
  • Page 597 Server (direct media is required in the Lync environment). For more information, see 'Configuring IP Groups' on page 336. IP Groups of the endpoints use the same SIP Interface and the SIP Interface's 'SBC Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 598: Restricting Audio Coders

    Mediant 1000B Gateway and E- SBC Direct Media' parameter is set to Enable (SIPInterface_SBCDirectMedia = 1). IP Groups of the endpoints use the same SIP Interface and the SIP Interface's 'SBC Direct Media' parameter Enable When Single (SIPInterface_SBCDirectMedia = 2), and the endpoints are located behind the same NAT.

  • Page 599: Coder Transcoding

    The extension coders are configured using Coder Groups (see 'Configuring Coder Groups' on page 379), which you need to then assign to the IP Profile associated with the SIP entity. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 600 Mediant 1000B Gateway and E- SBC The figure below illustrates transcoding between two SIP entities (IP Groups) where one uses G.711 (LAN IP phone) and the other G.729 (WAN IP phone). The initial SDP offer received on the inbound leg from the LAN IP phone includes coder G.711 as the supported coder.
  • Page 601 The device adds the extension coder to the SDP offer and therefore, the SDP offer now includes the G.711, G.729 and G.726 coders. m=audio 6050 RTP/AVP 0 8 18 96 96 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729/8000 a=rtpmap:96 G726-32/8000 a=fmtp:4 annexa=no a=rtpmap:96 telephone-event/8000 Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 602: Transcoding Mode

    Mediant 1000B Gateway and E- SBC a=fmtp:96 0-15 a=ptime:20 a=sendrecv The device applies coder restriction to the SDP offer. As the Allowed Audio Coders Group for coder restriction includes the G.723, G.726, and G.729 coders, the device allows and keeps the G.729 and G.726, but removes the G.711 coder as it does not appear in the Allowed Audio Coders Group for coder restriction.

  • Page 603: Prioritizing Coder List In Sdp Offer

    This is relevant when the MKI and Symmetric MKI parameters are enabled. In other words, both sides need to both encrypt and decrypt the outgoing and incoming SRTP packets, respectively. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 604: Multiple Rtp Media Streams Per Call Session

    Mediant 1000B Gateway and E- SBC DSP resources are not required for RTP-SRTP transcoding. 28.5.8 Multiple RTP Media Streams per Call Session The device's SBC application supports multiple RTP media streams per SBC call session. Up to five different media types can be included in a session: ...

  • Page 605: Interworking Rtcp Attribute In Sdp

    Coders Group Settings table for faxes. However, support for G.711 coders for voice is not dependent upon which fax coders are listed in the Coders Group Settings table. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 606: Limiting Sbc Call Duration

    Mediant 1000B Gateway and E- SBC 28.7 Limiting SBC Call Duration You can define a maximum allowed duration (in minutes) for SBC calls. If an established call reaches this user-defined limit, the device terminates the call. This feature ensures calls are properly terminated, allowing available resources for new calls. This feature is configured using the MaxCallDuration parameter.

  • Page 607: User Authentication Based On Radius

    The device accepts the SIP client's request (sends a SIP 200 OK or forwards the authenticated request) or rejects it (sends another SIP 407 to the SIP client). To configure this feature, set the SBCServerAuthMode ini file parameter to 2. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 608: Interworking Sip Signaling

    Mediant 1000B Gateway and E- SBC 28.9 Interworking SIP Signaling The device supports interworking of SIP signaling messages to ensure interoperability between communicating SIP UAs or entities. This is critical in network environments where the UAs on opposing SBC legs have different SIP signaling support. For example, some UAs may support different versions of a SIP method while others may not event support a specific SIP method.

  • Page 609: Local Handling Of Sip 3Xx

    Routing table rules. (where the 'Call Trigger' field is set to 3xx). It is also possible to specify the IP Group that sent the 3xx request as matching criteria for the re-routing rule in this table ('ReRoute IP Group ID' field). Version 7.0 Mediant 1000B Gateway and E- SBC...

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

    Mediant 1000B Gateway and E- SBC 28.9.2 Interworking SIP Diversion and History-Info Headers This device can be configured to interwork between the SIP Diversion and History-Info headers. This is important, for example, to networks that support the Diversion header but not the History-Info header, or vice versa.

  • Page 611: Interworking Sip Prack Messages

    The device can resolve this mismatch by performing the keep- alive process on behalf of SIP UAs that do not support it. For configuring the handling of session expires, use the IP Profile parameter, 'SBC Session Expires Mode'. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 612: Interworking Sip Early Media

    Mediant 1000B Gateway and E- SBC 28.9.6 Interworking SIP Early Media The device supports early media. Early media is when the media flow starts before the SIP call is established (i.e., before the 200 OK response). This occurs when the first SDP offer- answer transaction completes.
  • Page 613 Media RTP Detection Mode', 'SBC Remote Supports RFC 3960', and 'SBC Remote Can Play Ringback'. See the flowcharts below for the device's handling of such scenarios: Figure 28-7: SBC Early Media RTP 18x without SDP Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 614: Interworking Sip Re-Invite Messages

    Mediant 1000B Gateway and E- SBC Figure 28-8: Early Media RTP - SIP 18x with SDP 28.9.7 Interworking SIP re-INVITE Messages The device supports interworking re-INVITE messages. This enables communication between endpoints that generate re-INVITE requests and those that do not support the receipt of re-INVITEs.

  • Page 615: Interworking Sip Update Messages

    Interworking the play of the held tone for IP entities that cannot play held tones locally. This is configured by the IP Profile parameter, 'SBC Play Held Tone'.  Interworking generation of held tone where the device generates the tone to the held Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 616: Interworking Sip Via Headers

    Mediant 1000B Gateway and E- SBC 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 385. 28.9.12 Interworking SIP Via Headers The device supports the interworking of SIP Via headers between SIP entities.

  • Page 617: Interworking Sip To-Header Tags In Multiple Sdp Answers

    The device supports the interworking of in-dialog, SIP Contact and Record-Route headers between SIP entities. Employing IP Profiles, you can configure this interworking feature per entity, using IpProfile_SBCRemoteRepresentationMode parameter (see 'Configuring IP Profiles' on page 385). Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 618 Mediant 1000B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-27044...

  • Page 619: Enabling The Sbc Application

    Open the Applications Enabling page (Configuration tab > VoIP menu > Applications Enabling > Applications Enabling). From the 'SBC 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 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 620 Mediant 1000B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-27044...

  • Page 621: Utilizing Gateway Channel Resources For Sbc

    To support the feature, the License Key installed on your device must include the "TDMtoSBC" feature key; otherwise, to purchase the feature, contact your AudioCodes sales representative to upgrade your License Key. • The maximum number of SBC sessions that can be supported is according to the device's maximum SBC capacity (see 'Channel Capacity' on page 1139).
  • Page 622 Mediant 1000B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-27044...

  • Page 623: Configuring General Sbc Settings

    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 clients behind the device, the call dialog information sent by the application server reflects Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 624 Mediant 1000B Gateway and E- SBC 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. The device resolves this by replacing the call identifiers received from the application server with the correct call identifiers (e.g., user A and user B).
  • Page 625 User's Manual 31. Configuring General SBC Settings sip:cjones@example.net </identity> <target uri="sip:line3@host3.example.net"> <param pname="actor" pval="attendant"/> <param pname="automaton" pval="false"/> </target> </remote> </dialog> </dialog-info> Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 626 Mediant 1000B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-27044...

  • Page 627: Configuring Admission Control

    (e.g., of 200). Requests that reach the user-defined call limit (maximum concurrent calls and/or call rate) are sent to an alternative route, if configured in the IP-to-IP Routing table. If no alternative Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 628 Mediant 1000B Gateway and E- SBC routing rule is located, the device rejects the SIP request with a SIP 480 "Temporarily Unavailable" response. Note: The device applies the CAC rule for the incoming leg immediately after the Classification process. If the call/request is rejected at this stage, no routing is performed.
  • Page 629 Reserved call capacity must be less than the maximum capacity (limit) configured for the CAC rule.  The total reserved call capacity configured for all the CAC rules must be within the device's total call capacity support. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 630 Mediant 1000B Gateway and E- SBC Parameter Description Limit Defines the maximum number of concurrent SIP dialogs per IP Group, SIP Interface or SRD. You can also use the following special values: limit  [0] 0 = Block all these dialogs.

  • Page 631: Configuring Coder Groups

    The Allowed Audio Coders Group for coder restriction takes precedence over the Coder Group for extension coders. In other words, if an extension coder is not listed as an allowed coder, the device does not add the extension coder to the SDP offer. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 632 Mediant 1000B Gateway and E- SBC The following procedure describes how to configure Allowed Audio Coder Groups through the Web interface. You can also configure it through ini file (AllowedCodersGroup) or CLI (configure voip > sbc allowed-coders-group group-0).  To configure an Allowed Coders Group: Open the Allowed Audio Coders Group page (Configuration tab >...

  • Page 633: Configuring Allowed Video Coder Groups

    The valid value for user-defined coders is a string name of up to 25 characters (case-insensitive). For example, [AllowedVideoCodersGroupX_Na "WOW.789" (but without quotes). Note: Each coder type can be configured only once per Allowed Video Coders Group. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 634 Mediant 1000B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-27044...

  • Page 635: Routing Sbc

    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 329). Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 636 Mediant 1000B Gateway and E- SBC The Classification table is used to classify incoming SIP dialog requests only if the following classification stages fail: Classification Stage 1 - Based on User Registration Database: The device searches its users registration database to check whether the incoming SIP dialog arrived from a registered user.
  • Page 637 You can also configure it through ini file (Classification) or CLI (configure voip > sbc routing classification).  To configure a Classification rule: Open the Classification table (Configuration tab > VoIP menu > SBC > Routing SBC > Classification Table). Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 638 Mediant 1000B Gateway and E- SBC Click Add; the following dialog box appears: Figure 34-2: Classification Table - Add Row Dialog Box Configure the Classification rule according to the parameters described in the table below. Click Add. Table 34-1: Classification Table Parameter Descriptions...
  • Page 639 The URI is typically located in the SIP From header. However, you can [Classification_SrcHost] configure the SIP header from where the device obtains the source URI, in the IP Group table ('Source URI Input' parameter). For more Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 640 Mediant 1000B Gateway and E- SBC Parameter Description information on how the device obtains this URI, see 'Call Processing of SIP Dialog Requests' on page 589. The default is the asterisk (*) symbol, which represents any source host prefix. Note: For REGISTER requests, the source URI is obtained from the To header.

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

    P-Called-Party-ID: <sip:1111@10.33.38.1> User-Agent: Sip Message Generator V1.0.0.5 Content-Length: 0 In the Classification table, add the following classification rules: Source Username Destination Index Destination Host Source IP Group Prefix Username Prefix 1111 2000 10.10.10.10 Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 642: Configuring Message Condition Rules

    Mediant 1000B Gateway and E- SBC In the IP Group table, add the following IP Groups: Index Source URI Input Destination URI Input P-Called-Party-ID Route In this example, a match exists only for Classification Rule #1. This is because the source...
  • Page 643 The valid value is a string of up to 59 characters. name [ConditionTable_Name] Condition Defines the Condition rule of the SIP message. condition The valid value is a string. [ConditionTable_Conditio Note: User and host parts must be enclosed in single quotes. Version 7.0 Mediant 1000B Gateway and E- SBC...

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

    'Routing Based on LDAP Active Directory Queries' on page 230).  Third-party routing server or AudioCodes ARM, which determines the destination (next hop) of the call (IP Group). The IP Group represents the next device in the routing path to the final destination. For more information, see 'Centralized Third-Party Routing Server or ARM' on page 270.
  • Page 645 SIP response code (i.e., 4xx, 5xx, and 6xx SIP responses) configured in the SBC Alternative Routing Reasons table (see 'Configuring SIP Response Codes for Alternative Routing Reasons' on page 655). ♦ SIP 408 Timeout or no response (after timeout). Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 646 Mediant 1000B Gateway and E- SBC • The DNS resolution includes IP addresses that the device has yet to try (for the current call). Messages are re-routed with the same SIP Call-ID and CSeq header fields (increased by 1). ...
  • Page 647 You can also configure it through ini file (IP2IPRouting) or CLI (configure voip > sbc routing ip2ip-routing).  To configure an IP-to-IP routing rule: Open the IP-to-IP Routing table (Configuration tab > VoIP menu > SBC > Routing SBC > IP-to-IP Routing Table). Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 648 Mediant 1000B Gateway and E- SBC Click Add; the following dialog box appears: Figure 34-5: IP-to-IP Routing Table - Add Row Dialog Box Configure an IP-to-IP routing rule according to the parameters described in the table below. Click Add. Table 34-3: IP-to-IP Routing Table Parameter Descriptions...
  • Page 649 For more information, see 'Configuring SBC Routing Policy Rules' on page 656. Request Type Defines the SIP dialog request type (SIP Method) of the incoming SIP dialog. request-type  [0] All (default) [IP2IPRouting_RequestTy  [1] INVITE Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 650 Mediant 1000B Gateway and E- SBC Parameter Description  [2] REGISTER  [3] SUBSCRIBE  [4] INVITE and REGISTER  [5] INVITE and SUBSCRIBE  [6] OPTIONS Source Username Prefix Defines the prefix of the user part of the incoming SIP dialog's source URI (usually the From URI).
  • Page 651 Determines the destination type to which the outgoing SIP dialog is sent. dst-type  [0] IP Group = (Default) The SIP dialog is sent to the IP Group as [IP2IPRouting_DestType] defined in the 'Destination IP Group' Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 652 IP-to-IP routing rule.  [9] Routing Server = Device sends a request to a third-party routing server or AudioCodes ARM for an appropriate destination (next hop) for the matching call.  [10] All Users = Device checks whether the Request-URI (i.e., destination user) in the incoming INVITE is registered in its' users’...
  • Page 653 (user@host) which is used as the destination Request-URI in this routing table. The valid value is a string of up to 50 characters (IP address or FQDN). By default, no value is defined. Notes: Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 654 Mediant 1000B Gateway and E- SBC Parameter Description  The parameter is applicable only if the 'Destination Type' parameter is set to 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 Table' on page 150).

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

    The following procedure describes how to configure the SBC Alternative Routing Reasons table through the Web interface. You can also configure it through ini file (SBCAlternativeRoutingReasons) or CLI (configure voip > sbc routing sbc-alt-routing- reasons). Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 656 Mediant 1000B Gateway and E- SBC  To configure SIP reason codes for alternative IP routing: Open the SBC Alternative Routing Reasons table (Configuration tab > VoIP menu > SBC > Routing SBC > Alternative Routing Reasons). Click Add; the following dialog box appears:...

  • Page 657: Configuring Sbc Routing Policy Rules

    To determine the routing and manipulation rules for the SRD, you need to assign the Routing Policy to routing and manipulation rules. The figure below shows the configuration entities to which Routing Policies can be assigned: Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 658 Mediant 1000B Gateway and E- SBC Typically, assigning a Routing Policy to a Classification rule is not required, as when an incoming call is classified it uses the Routing Policy associated with the SRD to which it belongs. However, if a Routing Policy is assigned to a Classification rule, it overrides the Routing Policy assigned to the SRD.
  • Page 659 Assigns an LDAP Server Group to the Routing Policy. Routing rules in Name the IP-to-IP Routing table that are associated with the Routing Policy and that are configured with LDAP and/or Call Setup Rules, use the LDAP ldap-srv-group- Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 660 Mediant 1000B Gateway and E- SBC Parameter Description name server(s) configured for this LDAP Server Group. [SBCRoutingPolicy_ By default, no value is defined (None). LdapServersGroupNa For more information on LDAP Server Groups, see 'Configuring LDAP Server Groups' on page 232.

  • Page 661: Sbc Manipulations

    Below is an example of a call flow and consequent SIP URI manipulations:  Incoming INVITE from LAN: INVITE sip:1000@10.2.2.3;user=phone;x=y;z=a SIP/2.0 Via: SIP/2.0/UDP 10.2.2.6;branch=z9hGLLLLLan From:<sip:7000@10.2.2.6;user=phone;x=y;z=a>;tag=OlLAN;paramer1 =abe To: <sip:1000@10.2.2.3;user=phone> Call-ID: USELLLAN@10.2.2.3 CSeq: 1 INVITE Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 662 Mediant 1000B Gateway and E- SBC Contact: <sip:7000@10.2.2.3> Supported: em,100rel,timer,replaces Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK User-Agent: Sip Message Generator V1.0.0.5 Content-Type: application/sdp Content-Length: 155 o=SMG 791285 795617 IN IP4 10.2.2.6 s=Phone-Call c=IN IP4 10.2.2.6 t=0 0 m=audio 6000 RTP/AVP 8 a=rtpmap:8 pcma/8000 a=sendrecv a=ptime:20 ...

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

    Groups (see 'Configuring IP Groups' on page 336). The following procedure describes how to configure IP-to-IP Inbound Manipulation rules through interface. also configure through file (IPInboundManipulation) or CLI (configure voip > sbc manipulations ip-inbound- manipulation). Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 664 Mediant 1000B Gateway and E- SBC  To configure an IP-to-IP Inbound Manipulation rule: Open the IP to IP Inbound Manipulation table (Configuration tab > VoIP menu > SBC > Manipulations SBC > IP-to-IP Inbound). Click Add; the following dialog box appears:...
  • Page 665 The default is the asterisk (*) symbol (i.e., any destination host name). n_DestHost] Request Type Defines the SIP request type to which the manipulation rule is applied. CLI: request-type  [0] All = (Default) All SIP messages. [IPInboundManipulatio Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 666 Mediant 1000B Gateway and E- SBC Parameter Description  n_RequestType] [1] INVITE = All SIP messages except REGISTER and SUBSCRIBE.  [2] REGISTER = Only REGISTER messages.  [3] SUBSCRIBE = Only SUBSCRIBE messages.  [4] INVITE and REGISTER = All SIP messages except SUBSCRIBE.

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

    (IPOutboundManipulation) or CLI (configure voip > sbc manipulations ip-outbound- manipulation).  To configure IP-to-IP outbound manipulation rules: Open the IP to IP Outbound Manipulation table (Configuration tab > VoIP menu > SBC > Manipulations SBC > IP-to-IP Outbound). Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 668 Mediant 1000B Gateway and E- SBC Click Add; the following dialog box appears: Figure 35-3: IP to IP Outbound Manipulation Table- Add Row Dialog Box Configure an IP-to-IP outbound manipulation rule according to the parameters described in the table below.
  • Page 669 The prefix can be a single digit or a range of digits. For prefix available notations, see 'Dialing Plan Notation for Routing and [IPOutboundManipulatio Manipulation' on page 877. n_DestUsernamePrefix] Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 670 Mediant 1000B Gateway and E- SBC Parameter Description Note: If you need to manipulate calls of many different destination URI user names, you can use tags (see 'Destination Tags' parameter below) instead of this parameter. Destination Host Defines the destination SIP URI host name - full name, typically located in the Request-URI and To headers.
  • Page 671 [0] Transparent = (Default) No intervention in SIP privacy.  [1] Don't change privacy = The user identity remains the same as in [IPOutboundManipulatio the incoming SIP dialog. If a restricted number exists, the restricted n_PrivacyRestrictionMod Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 672 Mediant 1000B Gateway and E- SBC Parameter Description presentation is normalized as follows:  From URL header: anonymous@anonymous.invalid.  If a P-Asserted-Identity header exists (either in the incoming SIP dialog or added by the device), a Privacy header is added with the value "id".

  • Page 673: Configuring Dial Plans

     Prefix: The prefix is matched against the source and/or destination number of the incoming SIP dialog-initiating request.  Tag: The tag corresponds to the matched prefix of the source and/or destination Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 674 Mediant 1000B Gateway and E- SBC number and is the categorization result. You can use various syntax notations for configuring the prefix numbers in dial plan rules. You can configure the prefix as a complete number (all digits) or as a partial number using some digits and various syntax notations (patterns) to allow the device to match a dial pan rule for similar source and/or destination numbers.
  • Page 675 In the Dial Plan table, select the row for which you want to configure dial plan rules, and then click the Dial Plan Rule link located below the table; the Dial Plan Rule table appears. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 676 Mediant 1000B Gateway and E- SBC Click New; the following dialog box appears: Figure 36-3: Dial Plan Rule Table Configure a dial plan rule according to the parameters described in the table below. Click New, and then save ("burn") your settings to flash memory.

  • Page 677: Importing And Exporting Dial Plans

    Dial Plan itself remains). The Dial Plan names in the imported file must be identical to the existing Dial Plan names on the device; otherwise, the specific Dial Plan is not imported. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 678: Creating Dial Plan Files

    Mediant 1000B Gateway and E- SBC For creating Dial Plans in a CSV file for import, see 'Creating Dial Plan Files for Import' on page 678. 36.2 Creating Dial Plan Files You can configure Dial Plans in an external file (*.csv) and then import them into the device, as described in 'Importing and Exporting Dial Plans' on page 677.
  • Page 679 'Source Tags' parameter (IP2IPRouting_SrcTags): tag denoting the calling user • 'Destination Tags' parameter (IP2IPRouting_DestTags): tag denoting the called user An example of a routing rule using a destination tag "LOC" is shown below: Figure 36-4: Assigning Tag to Routing Rule Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 680: Dial Plan Backward Compatibility

    Mediant 1000B Gateway and E- SBC 36.3.1 Dial Plan Backward Compatibility Note: This section is for backward compatibility only. It is recommended to migrate your Dial Plan configuration to the latest Dial Plan feature (see 'Using Dial Plan Tags for IP-to-IP Routing' on page 729).
  • Page 681 Click the Action tab, and then in the 'Remove from Left' or 'Remove from Right' fields (depending on whether you added the tag at the beginning or end of the URI user part, respectively), enter the number of characters making up the tag. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 682: Using Dial Plan Tags For Outbound Manipulation

    Mediant 1000B Gateway and E- SBC 36.4 Using Dial Plan Tags for Outbound Manipulation You can use Dial Plan tags to denote source and/or destination URI user names in Outbound Manipulation rules in the IP-to-IP Outbound Manipulation table. The following procedure describes how to configure Outbound Manipulation based on tags.

  • Page 683: Advanced Sbc Features

    In the Message Condition table, configure a Message Condition rule to identify incoming emergency calls. See above for examples. For more information on Message Conditions, see 'Configuring Message Condition Rules' on page 642. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 684: Emergency Call Routing Using Ldap To Obtain Elin

    Mediant 1000B Gateway and E- SBC Open the SBC General Settings page (Configuration tab > VoIP > SBC > SBC General Settings), and then scroll down the page to the Call Priority and Preemption group: Figure 37-2: Configuring Emergency SBC Call Preemption From the 'SBC Preemption Mode' drop-down list (SBCPreemptionMode), select Enable to enable the SBC call preemption feature.

  • Page 685: Call Forking

    UAs. Several UAs may answer and the device may therefore, receive several replies (responses) for the single INVITE request. Each response has a different 'tag' value in the SIP To header. Version 7.0 Mediant 1000B Gateway and E- SBC...

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

    Mediant 1000B Gateway and E- SBC During call setup, forked SIP responses may result in a single SDP offer with two or more SDP answers. The device "hides" all the forked responses from the INVITE-initiating UA, except the first received response ("active" UA) and it forwards only subsequent requests and responses from this active UA to the INVITE-initiating UA.

  • Page 687: Call Survivability

    Below is an example of an XML body received from the BroadWorks server: <?xml version="1.0" encoding="utf-8"?> <BroadsoftDocument version="1.0" content="subscriberData"> <phoneNumbers> <phoneNumber>2403645317</phoneNumber> <phoneNumber>4482541321</phoneNumber> </phoneNumbers> <aliases> <alias>sip:bob@broadsoft.com</alias> <alias>sip:rhughes@broadsoft.com</alias> </aliases> <extensions> <extension>5317</extension> <extension>1321</extension> </extensions> </BroadSoftDocument> Version 7.0 Mediant 1000B Gateway and E- SBC...

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

    Mediant 1000B Gateway and E- SBC 37.4.2 BroadSoft's Shared Phone Line Call Appearance for SBC Survivability The device can provide redundancy for BroadSoft's Shared Call Appearance feature. When the BroadSoft application server switch (AS) fails or does not respond, or when the network connection between the device and the BroadSoft AS is down, the device manages the Shared Call Appearance feature for the SIP clients.

  • Page 689: Call Survivability For Call Centers

    The SBC can handle a sequence of up to five users, after which the session is timed out and the call is dropped. Figure 37-6: Normal Operation in Call Center Application Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 690 Mediant 1000B Gateway and E- SBC Figure 37-7: Call Survivability for Call Center  To configure call survivability for a call center application: In the IP Group table (see 'Configuring IP Groups' on page 336), add IP Groups for the following entities: •...

  • Page 691: Survivability Mode Display On Aastra Ip Phones

    When this feature is enabled and the SBC device is in Survivability mode, it responds to SIP REGISTER messages from the IP phones with a SIP 200 OK containing the following XML body: Content-Type: application/xml <?xml version="1.0" encoding="utf-8"?> <LMIDocument version="1.0"> <LocalModeStatus> <LocalModeActive>true</LocalModeActive> <LocalModeDisplay>StandAlone Mode</LocalModeDisplay> </LocalModeStatus> </LMIDocument> Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 692: Alternative Routing On Detection Of Failed Sip Response

    Mediant 1000B Gateway and E- SBC 37.5 Alternative Routing on Detection of Failed SIP Response The device can detect failure of a sent SIP response (e.g., TCP timeout, and UDP ICMP). In such a scenario, the device re-sends the response to an alternative destination. This support is in addition to alternative routing if the device detects failed SIP requests.

  • Page 693: Cloud Resilience Package

    Part VII Cloud Resilience Package...

  • Page 695: 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 696 Mediant 1000B Gateway and E- SBC Survivability Quality of Experience/Service Security dynamically in the registration process)  Survivability indication to IP phone  Call hold and retrieve  Call transfer (if IP phone initiates REFER)  Basic Shared Line Appearance (excluding correct busy line indications) ...

  • Page 697: 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 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 698: Configuring Call Survivability Mode

    Mediant 1000B Gateway and E- SBC 39.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.

  • Page 699: 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 336. Version 7.0 Mediant 1000B Gateway and E- SBC...

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

    Mediant 1000B Gateway and E- SBC 39.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 698.

  • Page 701: 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 702). Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 702: Configuring Pstn Fallback

    Mediant 1000B Gateway and E- SBC 39.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 703: Maintenance

    Part VIII Maintenance...

  • Page 705: Basic Maintenance

    Description' on page 53) to indicate that a device reset is required. • After you reset the device, the Web GUI is displayed in Basic view (see 'Displaying Navigation Tree in Basic and Full View' on page 55). Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 706 Mediant 1000B Gateway and E- SBC  To reset the device: Open the Maintenance Actions page (see 'Basic Maintenance' on page 705). Under the 'Reset Configuration' group, from the 'Burn To FLASH' drop-down list, select one of the following options: •...

  • Page 707: Remotely Resetting Device Using Sip Notify

    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. 40.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 708: Saving Configuration

    Mediant 1000B Gateway and E- SBC the time has not yet expired, the device locks immediately. Click the LOCK button; a confirmation message box appears requesting you to confirm device lock. 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.

  • Page 709: Replacing Modules

    Click OK to confirm removal; after a few seconds, the module is software- removed, the module status icon turns to grey, and the name of the module is suffixed with the word 'Reserved': Physically remove the module (refer to the Installation Manual). Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 710 Mediant 1000B Gateway and E- SBC Insert the replaced module, by performing the following: Physically insert the replaced module (refer to the Installation Manual) into the same slot in which the previous module resided. In the Home page, click the title of the module ("<module type> Reserved") that you want to replace;...

  • Page 711: Channel Maintenance

    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 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 712: Restarting A B-Channel

    Mediant 1000B Gateway and E- SBC 42.3 Restarting a B-Channel You can restart a specific B-channel belonging to an ISDN or CAS trunk, using the SNMP MIB variable, acTrunkISDNCommonRestartBChannel. This may be useful, for example, for troubleshooting specific voice channels.
  • Page 713 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. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 714 Mediant 1000B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-27044...

  • Page 715: Software Upgrade

    Web interface - see 'Loading Auxiliary Files through Web Interface' on page 716  CLI - see Loading Auxiliary Files through CLI on page 717  TFTP - see 'Loading Auxiliary Files through ini File using TFTP' on page 717 Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 716: Loading Auxiliary Files Through Web Interface

    Mediant 1000B Gateway and E- SBC Notes: • You can schedule automatic loading of updated Auxiliary files using HTTP/HTTPS. For more information, see Automatic Update Mechanism. • Saving Auxiliary files to flash memory may disrupt traffic on the device. To avoid this, disable all traffic on the device by performing a graceful lock as described in 'Locking and Unlocking the Device' on page 707.

  • Page 717: Loading Auxiliary Files Through Cli

    Reset the device (you can power off and then power on the device); the device loads the ini file and then the Auxiliary files as defined in the ini file, through TFTP. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 718: Deleting Auxiliary Files

    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 719 First Signal On Time [10 msec]: 'Signal On' period (in 10 msec units) for the first cadence on-off cycle. For continuous tones, the parameter defines the detection period. For burst tones, it defines the tone's duration. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 720 Mediant 1000B Gateway and E- SBC • First Signal Off Time [10 msec]: 'Signal Off' period (in 10 msec units) for the first cadence on-off cycle (for cadence tones). For burst tones, the parameter defines the off time required after the burst tone ends and the tone detection is reported.

  • Page 721: Distinctive Ringing

    INVITE message. For example: Alert-Info:<Bellcore-dr2>, or Alert-Info:<http://…/Bellcore-dr2> 'dr2' defines ringing pattern #2. If the Alert-Info header is missing, the default ringing tone (0) is played. An example of a ringing burst definition is shown below: Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 722: Prerecorded Tones File

    Mediant 1000B Gateway and E- SBC #Three ringing bursts followed by repeated ringing of 1 sec on and 3 sec off. [NUMBER OF DISTINCTIVE RINGING PATTERNS] Number of Ringing Patterns=1 [Ringing Pattern #0] Ring Type=0 Freq [Hz]=25 First Burst Ring On Time [10msec]=30...

  • Page 723: Voice Prompts File

    For SBC calls, the PRT file supports only the ringback tone and hold tone. The prerecorded tones can be created using standard third-party, recording utilities such as Adobe Audition, and then combined into a single file (PRT file) using AudioCodes DConvert utility (refer to the document, DConvert Utility User's Guide for more information).

  • Page 724: Cas Files

    Mediant 1000B Gateway and E- SBC  To generate and load the VP file: Prepare one or more voice files using standard utilities. Use the DConvert utility to generate the voiceprompts.dat file from the pre-recorded voice messages. For more information, refer to DConvert Utility User's Guide.

  • Page 725: Dialing Plans For Digit Collection

    User's Manual 43. Software Upgrade 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 715.
  • Page 726 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 715.

  • Page 727: Dial Plan Prefix Tags For Routing

    Each prefix tag type - called or calling - must be configured in a dedicated Dial Plan index number. For example, Dial Plan 1 can be for called prefix tags and Dial Plan 2 for calling prefix tags. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 728 Mediant 1000B Gateway and E- SBC 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 ..Notes: •...

  • Page 729: Obtaining Ip Destination From Dial Plan File

    "0" denotes [PLAN1] in the Dial Plan file, "1" denotes [PLAN2], and so on. • Tel-to-IP Calls (Gateway application): In the Tel-to-IP Routing table, do the following: In the 'Destination Address' field, enter the required Dial Plan index using the following syntax: DialPlan<index> Version 7.0 Mediant 1000B Gateway and E- SBC...

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

    Mediant 1000B Gateway and E- SBC Where "DialPlan0" denotes [PLAN1] in the Dial Plan file, "DialPlan1" denotes [PLAN2], and so on. Note: The "DialPlan" string is case-sensitive. 43.1.7.5 Modifying ISDN-to-IP Calling Party Number The device can use the Dial Plan file to change the Calling Party Number value (source number) of the incoming ISDN call when sending to IP.

  • Page 731: Viewing Information Of Installed Dial Plan File

    Open the Advanced Parameters page (Configuration tab > VoIP menu > SIP Definitions > Advanced Parameters). Set the 'Enable User-Information Usage' parameter (EnableUserInfoUsage) to Enable. Save this setting to the device with a reset for the setting to take effect. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 732: Gateway User Information For Pbx Extensions And "Global" Numbers

    Mediant 1000B Gateway and E- SBC 43.1.8.2 Gateway User Information for PBX Extensions and "Global" Numbers The GW User Info table contains user information that can be used for the following Gateway-related features:  Mapping (Manipulating) PBX Extension Numbers with Global Phone Numbers: maps PBX extension number, connected to the device, with any "global"...
  • Page 733 Action button's drop-down list , choose Un-Register. Table 43-2: GW User Info Table Parameter Descriptions Parameter Description Index Defines an index number for the new table row. Note: Each row must be configured with a unique index. [GWUserInfoTable_Index] Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 734 Mediant 1000B Gateway and E- SBC Parameter Description PBX Extension Defines the PBX extension number. [GWUserInfoTable_PBXE The valid value is a string of up to 10 characters. xtension] Note: The parameter is mandatory. Global Phone Number Defines the "global" phone number for the IP side.
  • Page 735 To modify the GW User Info table using a User Info file, you need to load to the device a new User Info file containing your modifications. Below is an example of a configured User Info file: [ GW ] FORMAT PBXExtensionNum,GlobalPhoneNum,DisplayName,UserName,Password 401,638001,Mike,miked,1234 402,638002,Lee,leem,4321 403,638003,Sue,suer,8790 404,638004,John,johnd,7694 405,638005,Pam,pame,3928 406,638006,Steve,steveg,1119 Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 736: User Information File For Sbc User Database

    Mediant 1000B Gateway and E- SBC 407,638007,Fred,frede,8142 408,638008,Maggie,maggiea,9807 43.1.8.3 User Information File for SBC User Database You can use the SBC User Info table for the following:  Registering each user to an external registrar server.  Authenticating (for any SIP request and as a client) each user if challenged by an external server.
  • Page 737 To delete a specific user, use the no command: (sip-def-proxy-and-reg)# no user-info sbc-user-info <index, e.g., 1>  To view all table entries: (sip-def-proxy-and-reg)# user-info sbc-user-info display ---- sbc-user-info-0 ---- local-user (JohnDee) username (userJohn) password (s3fn+fn=) Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 738 Mediant 1000B Gateway and E- SBC ip-group-id (1) status (not-resgistered) ---- sbc-user-info-1 ---- local-user (SuePark) username (userSue) password (t6sn+un=) ip-group-id (1) status (not-resgistered)  To view a specific entry (example): (sip-def-proxy-and-reg)# user-info sbc-user-info <index, e.g., 0> (sbc-user-info-0)# display local-user (JohnDee)

  • Page 739: Viewing The Installed User Info File Name

    The XML-to-binary format conversion can be done using AudioCodes DConvert utility. For more information on using this utility, refer to DConvert Utility User's Guide. Only one AMD Sensitivity file can be installed on the device.

  • Page 740: Obtaining The Software License Key File

    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 741: Installing The Software License Key

    Install the Software License Key on the device, as described in 'Installing the Software License Key' on page 741. 43.2.2 Installing the Software License Key Once you have received your Software License Key file from your AudioCodes representative, you can install it on the device using one of the following management tools: ...

  • Page 742: Installing Software License Key Through Cli

    Manager Server The device can receive SBC capacity licenses from a centralized pool of SBC resources managed by the License Pool Manager Server running on AudioCodes EMS. The License Pool Manager Server can dynamically allocate and de-allocate SBC capacity licenses from the pool to devices in the network to meet capacity demands of each device whenever required.
  • Page 743 Figure 43-6: Software Upgrade Key Status Page Displaying Licenses from License Pool  If communication with the License Pool Manager Server is lost for a long duration, the device discards the allocated SBC license (i.e., expires) and resets with its initial, "local" Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 744: Software Upgrade Wizard

    .cmp file is mandatory through the wizard and before you can load any other type of file, the .cmp file must be loaded. Notes: • You can obtain the latest software files from AudioCodes Web site at http://www.audiocodes.com/downloads. • When you start the wizard, the rest of the Web interface is unavailable. After the files are successfully installed with a device reset, access to the full Web interface is restored.
  • Page 745 User's Manual 43. Software Upgrade 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. • Instead of manually upgrading the device, you can use the device's Automatic Update feature for automatic provisioning (see 'Automatic Provisioning' on page 751).
  • Page 746 Mediant 1000B Gateway and E- SBC Click Start Software Upgrade; the wizard starts, prompting you to load a .cmp file: Figure 43-8: Software Upgrade Wizard - Load CMP File Note: At this stage, you can quit the Software Upgrade Wizard without having to reset the device, by clicking Cancel .
  • Page 747 If you use the wizard to load an ini file, parameters excluded from the ini file are assigned default values (according to the .cmp file running on the device) and thereby, overwrite values previously configured for these parameters. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 748 Mediant 1000B Gateway and E- SBC When you have completed loading all the desired files, click Next until the last wizard page appears (the FINISH button is highlighted in the left pane): Figure 43-10: Software Upgrade Wizard - Files Loaded Click Reset to burn the files to the device's flash memory;...

  • Page 749: Backing Up And Loading Configuration File

    To save the ini file to a folder on your computer: Click the Save INI File button; the File Download dialog box appears. Click the Save button, navigate to the folder where you want to save the file, and then click Save. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 750 Mediant 1000B Gateway and E- SBC To load the ini file to the device: Click the Browse button, navigate to the folder where the file is located, select the file, and then click Open; the name and path of the file appear in the field beside the Browse button.

  • Page 751: Automatic Provisioning

    Open the Application Settings page (Configuration tab > System menu > Application Settings). Figure 44-1: Enabling DHCP - Application Settings Page From the 'Enable DHCP" drop-down list, select Enable. Click Submit. To activate the DHCP process, reset the device. Version 7.0 Mediant 1000B Gateway and E- SBC...

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

    Mediant 1000B Gateway and E- SBC 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 10.31.4.75. TFTP is assumed to be on the same computer as the DHCP server (alternatively, the "next-server"...

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

    The only configuration required is to preconfigure the device(s) with the URL of the initial (master) ini file. This can be done using one of the following methods:  DHCP as described in 'DHCP-based Provisioning' on page 751 or via TFTP at a Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 754: Ftp-Based Provisioning

    752 is that the protocol in the URL is "ftp" (instead of "http"). 44.1.4 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 755: Files Provisioned By Automatic Update

    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' on Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 756: 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 757 SIP Definitions > Advanced Parameters). Under the Misc Parameters group, set the 'SIP Remote Reset' parameter to Enable. Click Submit. To enable through CLI: configure voip > sip-definition advanced-settings > sip- remote-reset. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 758: Access Authentication With Http Server

    Mediant 1000B Gateway and E- SBC 44.2.4 Access Authentication with HTTP Server You can configure the device to authenticate itself with the HTTP/S server. The device authenticates itself by providing the HTTP/S server with its authentication username and password. You can configure one of the following HTTP authentication schemes: ...
  • Page 759 HTTP 200 OK response, the device may reset itself repeatedly. To overcome this problem, modify the update frequency, using the ini file parameter AutoUpdateFrequency or CLI command configure system > automatic update > update-frequency. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 760: File Download Sequence

    Mediant 1000B Gateway and E- SBC • One-time File Download: This is applicable to software (.cmp) and Auxiliary (e.g., License Key, CPT and Dial Plan) files. The device downloads these files only once, regardless of how many times the device may repeat the Automatic Update process.

  • Page 761: Cyclic Redundancy Check On Downloaded Configuration Files

    If the check values are different, it indicates that the downloaded file is different (i.e., includes updates), and the device installs the downloaded file and applies the new configuration settings. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 762: Mac Address Placeholder In Configuration File Name

    Mediant 1000B Gateway and E- SBC CRC is useful, for example, when the service provider replaces a file, on the provisioning server, with another file whose contents are the same. When the device sends an HTTP Get request during the Automatic Update process, the provisioning server sends the new file to the device.
  • Page 763 File Type Template File <FILE> Placeholder ini file device.ini CLI Script file cliScript.txt CMP file based on timestamp acmp autoFirmware.cmp User Info file usrinf userInfo.txt CMP file firmware.cmp Voice Prompts (VP) file vp.dat Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 764: Automatic Update Configuration Examples

    Mediant 1000B Gateway and E- SBC Keywords for Value Replacing File Type Template File <FILE> Placeholder Feature Key file fk.ini Call Progress Tone (CPT) file cpt.dat Prerecorded Tones (PRT) file prt.dat CAS file cas.dat Dial Plan file dpln dialPlan.dat Answering Machine Detection (AMD) amd.dat...
  • Page 765 Enable Cyclical Redundancy Check (CRC) on downloaded ini file: ♦ ini File: AUPDCheckIfIniChanged = 1 ♦ CLI: # configure system (config-system)# automatic update (automatic-update)# crc-check regular Power down and then power up the device. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 766: Automatic Update From Ftp And Http Servers

    Mediant 1000B Gateway and E- SBC 44.2.10.2 Automatic Update from FTP and HTTP Servers This example describes how to configure the Automatic Update feature where files are stored and downloaded from different file server types. The example scenario includes the following: ...

  • Page 767: Automatic Update For Mass Deployment

    Device queries the provisioning server daily at 24:00 (midnight) for software, configuration and Auxiliary files.  HTTP-based provisioning server at www.company.com for storing the files.  DNS server at 80.179.52.100 for resolving the domain name of the provisioning server. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 768 Mediant 1000B Gateway and E- SBC  To set up automatic provisioning for mass provisioning (example): Create a "master" configuration file template named "master_configuration.ini" with the following settings: • Common configuration for all devices: ♦ ini file: AutoUpdatePredefinedTime = '24:00' CptFileURL = 'https://www.company.com/call_progress.dat'...
  • Page 769 InterfaceTable 0 = 6, 10, 10.15.7.95, 16, 10.15.0.1, 1, "Voice", 80.179.52.100, 0.0.0.0, "vlan 1"; [ \InterfaceTable ] ♦ CLI: # configure voip (config-voip)# interface network-if 0 (network-if-0)# primary-dns 80.179.52.100 Power down and then power up the device. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 770 Mediant 1000B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-27044...

  • Page 771: Restoring Factory Defaults

    Interface table (see 'Configuring IP Network Interfaces' on page 135), as described in the procedure below. This may be important, for example, to maintain connectivity with the device (through the OAMP interface) after factory defaults have been applied. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 772: Restoring Defaults Using Hardware Reset Button

    Mediant 1000B Gateway and E- SBC  To restore factory defaults through Web interface: Open the Configuration File page: • Toolbar: From the Device Actions drop-down list, choose Restore Defaults • Navigation Tree: Maintenance tab > Software Update > Configuration File...

  • Page 773: Archiving The Configuration File

    (for whatever reason). To configure configuration-file archiving, use the following CLI command (root level):  Archiving to a remote server: # write-and-backup to <URL path with file name> Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 774 Mediant 1000B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-27044...

  • Page 775: Status, Performance Monitoring And Reporting

    Part IX Status, Performance Monitoring and Reporting...

  • Page 777: System Status

    Navigation menu tree: Status & Diagnostics tab > System Status menu > Ethernet Port Info • On the Home page, click any Ethernet port on the graphical display of the device (see 'Viewing the Home Page' on page 68) Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 778 Mediant 1000B Gateway and E- SBC Table 47-1: Ethernet Port Information Parameters Parameter Description Port Name Displays the name of the port. Active Displays whether the port is active ("Yes") or not ("No"). Speed Displays the speed (in Mbps) of the Ethernet port.

  • Page 779: Carrier-Grade Alarms

     To view history alarms:  Open the Alarms History table (Status & Diagnostics tab > System Status menu > Carrier-Grade Alarms > Alarms History). Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 780 Mediant 1000B Gateway and E- SBC For each alarm, the following information is provided:  Severity: severity level of the alarm: • Critical (red) • Major (range) • Minor (yellow) • Cleared (green)  Source: unit from which the alarm was raised ...

  • Page 781: 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 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 782: Viewing Trunk Utilization

    Mediant 1000B Gateway and E- SBC 49.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 783: Viewing Quality Of Experience

     Dialog Termination Ratio: displays call termination by reason (e.g., due to no answer).  To view Quality of Experience: Open the Quality Of Experience page (Status & Diagnostics tab > Performance Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 784: Viewing Average Call Duration

    Mediant 1000B Gateway and E- SBC Monitoring menu > Quality Of Experience). Figure 49-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. From the 'Index' drop-down list, select the SRD or IP Group index.
  • Page 785 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 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 786 Mediant 1000B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-27044...

  • Page 787: Voip Status

    Light Orange D-Channel Alarm Dark Orange NFAS Alarm Purple Lower Layer Down (DS3 physical layer is disabled) The status of the channels is depicted by color-coded icons, as described in the table below: Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 788: Viewing Analog Port Information

    Mediant 1000B Gateway and E- SBC Table 50-2: Description of Color-Coded Icons for Channel Status Icon Color Label Description Light blue Inactive Channel is configured, but currently has no calls Active Green Call in progress (RTP traffic) and no alarms...

  • Page 789: 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 50-4: NFAS Group & D-Channel Status Page Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 790: Viewing Active Ip Interfaces

    Mediant 1000B Gateway and E- SBC 50.4 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 135).  To view active IP network interfaces: ...

  • Page 791: Viewing Performance Statistics

    CDR is added, the last CDR entry is removed from the table. Note: If the device is reset, all CDR history information is deleted from memory and subsequently, the CDR History table appears empty. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 792 Mediant 1000B Gateway and E- SBC The following procedure describes how to view CDR history in the Web interface. You can also view CDR history using the following CLI commands:  All CDR history: # show voip calls history ...

  • Page 793: Viewing Call Counters

     GWAPP_REASON_NOT_RELEVANT (0)  GWAPP_NORMAL_CALL_CLEAR (16)  GWAPP_NORMAL_UNSPECIFIED (31) And the internal reasons:  RELEASE_BECAUSE_UNKNOWN_REASON  RELEASE_BECAUSE_REMOTE_CANCEL_CALL  RELEASE_BECAUSE_MANUAL_DISC Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 794 Mediant 1000B Gateway and E- SBC Counter Description  RELEASE_BECAUSE_SILENCE_DISC  RELEASE_BECAUSE_DISCONNECT_CODE Note: When the duration of the call is zero, the release reason GWAPP_NORMAL_CALL_CLEAR increments the 'Number of Failed Calls due to No Answer' counter. The rest of the release reasons increment the 'Number of Failed Calls due to Other Failures' counter.

  • Page 795: Viewing Registered Users

    (such as FXS, FXO and BRI) and SIP Accounts, which are configured in the Accounts table (see 'Configuring Registration Accounts' on page 357).  To view registration status:  Open the Registration Status page (Status & Diagnostics tab > VoIP Status menu > Registration Status). Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 796: Viewing Call Routing Status

    Mediant 1000B Gateway and E- SBC • Registered Per Gateway (applicable only to the Gateway application): Registration of device as one entity - "YES" or "NO" • Ports Registration Status: "REGISTERED" or "NOT REGISTERED" • Accounts Registration Status: ♦ Group Type: served Trunk Group or IP Group ♦...

  • Page 797: Viewing Ip Connectivity

    'Configuring Tel-to-IP Routing Rules' on page 483). Note: he information in columns 'Quality Status' and 'Quality Info' (per IP address) is reset if two minutes elapse without a call to that destination. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 798 Mediant 1000B Gateway and E- SBC  To view IP connectivity information: In the Routing General Parameters page, set the 'Enable Alt Routing Tel to IP' parameter (AltRoutingTel2IPMode) to Enable or Status Only (see 'Configuring General Routing Parameters' on page 483).
  • Page 799 The parameter is reset if no QoS information is received for 2 minutes. DNS Status DNS status can be one of the following:  DNS Disable  DNS Resolved  DNS Unresolved Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 800 Mediant 1000B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-27044...

  • Page 801: 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 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 802 Mediant 1000B Gateway and E- SBC Table 51-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...
  • Page 803 Content-Length: 1066 VQSessionReport CallID=20328634741612201520943@172.17.116.201 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 Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 804 Mediant 1000B Gateway and E- SBC JitterBuffer: JBA=3 JBR=0 JBN=7 JBM=10 JBX=300 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...

  • Page 805: Generating Call Detail Records

    (SBCReportType=CALL_END). CDRs belonging to the same SBC session (both legs) have the same Session ID (SessionId CDR field). CDRs belonging to the same SBC leg have the same SIP Call ID (SIPCallId CDR field). Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 806 Mediant 1000B Gateway and E- SBC For billing applications, the CDR that is sent when the call ends (CALL_END) is usually sufficient. Billing may be based on the following:  Call ID (SIPCallId CDR field)  Source URI (SrcURI CDR field) ...
  • Page 807 String of up to 35 characters ConnectTime Call connect time String of up to 35 characters ReleaseTime Call release time String of up to 35 characters RedirectReason Redirect reason String of up to 15 characters Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 808 Mediant 1000B Gateway and E- SBC CDR Field Name Description Format RedirectURINum Redirection URI String of up to 41 characters RedirectURINumBef Redirect URI number before String of up to 41 characters oreMap manipulation TxSigIPDiffServ Signaling IP DiffServ String of up to 15 characters...

  • Page 809: Cdr Fields For Sbc Media

    InPackets Number of received packets OutPackets Number of sent packets LocalPackLoss Local packet loss RemotePackLoss Remote packet loss RTPdelay RTP delay RTPjitter RTP jitter TxRTPssrc Tx RTP SSRC RxRTPssrc Local RTP SSRC Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 810: Cdr Fields For Gateway Application

    Mediant 1000B Gateway and E- SBC CDR Field Name Description LocalRFactor Local conversation quality Note: If the RTCP XR feature is unavailable (not licensed or disabled), this R-factor VoIP metric is not provided. Instead, the device sends the CDR field with the value 127, meaning that information is unavailable.
  • Page 811 SIP call termination reason (see 'Release Reasons in CDR for Gateway Application' on page 814) Fax transaction during call InPackets Number of incoming packets OutPackets Number of outgoing packets PackLoss Local packet loss RemotePackLoss Number of outgoing lost packets Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 812 Mediant 1000B Gateway and E- SBC Field Name Description SIPCalld Unique SIP call ID SetupTime Call setup time ConnectTime Call connect time ReleaseTime Call release time RTPdelay RTP delay RTPjitter RTP jitter RTPssrc Local RTP SSRC RemoteRTPssrc Remote RTP SSRC...
  • Page 813 127, meaning that information is unavailable. LocalMosCQ Local MOS for conversation quality RemoteMosCQ Remote MOS for conversation quality SigSourcePort SIP source port SigDestPort SIP destination port MediaType Media type - audio, video, or text Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 814 Mediant 1000B Gateway and E- SBC Field Name Description Information relating to the Automatic Machine Detection (AMD) feature:  V - voice  A - answer machine  S - silence  U - unknown Information relating to AMD that shows the success that the answering...
  • Page 815  "GWAPP_INVALID_NUMBER_FORMAT"  "GWAPP_FACILITY_REJECT"  "GWAPP_RESPONSE_TO_STATUS_ENQUIRY"  "GWAPP_NORMAL_UNSPECIFIED"  "GWAPP_CIRCUIT_CONGESTION"  "GWAPP_USER_CONGESTION"  "GWAPP_NO_CIRCUIT_AVAILABLE"  "GWAPP_NETWORK_OUT_OF_ORDER"  "GWAPP_NETWORK_TEMPORARY_FAILURE"  "GWAPP_NETWORK_CONGESTION"  "GWAPP_ACCESS_INFORMATION_DISCARDED"  "GWAPP_REQUESTED_CIRCUIT_NOT_AVAILABLE"  "GWAPP_RESOURCE_UNAVAILABLE_UNSPECIFIED"  "GWAPP_PERM_FR_MODE_CONN_OUT_OF_S"  "GWAPP_PERM_FR_MODE_CONN_OPERATIONAL"  "GWAPP_PRECEDENCE_CALL_BLOCKED" Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 816: Cdr Fields For Locally Stored Sbc

    Mediant 1000B Gateway and E- SBC • "RELEASE_BECAUSE_PREEMPTION_ANALOG_CIRCUIT_RESERVED_FOR_ REUSE" • "RELEASE_BECAUSE_PRECEDENCE_CALL_BLOCKED"  "GWAPP_QUALITY_OF_SERVICE_UNAVAILABLE"  "GWAPP_REQUESTED_FAC_NOT_SUBSCRIBED"  "GWAPP_BC_NOT_AUTHORIZED"  "GWAPP_BC_NOT_PRESENTLY_AVAILABLE"  "GWAPP_SERVICE_NOT_AVAILABLE"  "GWAPP_CUG_OUT_CALLS_BARRED"  "GWAPP_CUG_INC_CALLS_BARRED"  "GWAPP_ACCES_INFO_SUBS_CLASS_INCONS"  "GWAPP_BC_NOT_IMPLEMENTED"  "GWAPP_CHANNEL_TYPE_NOT_IMPLEMENTED"  "GWAPP_REQUESTED_FAC_NOT_IMPLEMENTED"  "GWAPP_ONLY_RESTRICTED_INFO_BEARER"  "GWAPP_SERVICE_NOT_IMPLEMENTED_UNSPECIFIED"  "GWAPP_INVALID_CALL_REF" ...
  • Page 817 SRD Name SrdId (name) SIP Interface ID SIPInterfaceId Proxy Set ID ProxySetId IP Profile ID IpProfileId (name) Media Realm Name MediaRealmId (name) Direct Media DirectMedia SIP Termination Reason SIPTrmReason SIP Termination Description SIPTermDesc Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 818: Customizing Cdrs For Gateway Calls

    Mediant 1000B Gateway and E- SBC CDR Field Title Caller Display ID Caller Callee Display ID Callee 51.2.2 Customizing CDRs for Gateway Calls The Gateway CDR Format table lets you configure CDR customization rules for Gateway- related CDRs that are sent in Syslog messages and/or RADIUS accounting request messages.
  • Page 819 [158] Local Packet Loss; [159] Local Round Trip Delay; [160] Local Jitter; [161] Local SSRC Sender; [162] Remote Input Packets; [163] Remote Output Packets; [164] Remote Input Octets; [165] Remote Output Octets; Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 820 Mediant 1000B Gateway and E- SBC Parameter Description [166] Remote Packet Loss; [167] Remote Round Trip Delay; [168] Remote Jitter; [169] Remote SSRC Sender; [170] Local RTP IP; [171] Local RTP Port; [172] Remote RTP IP; [173] Remote RTP Port; [174] RTP IP DiffServ;...

  • Page 821: Customizing Cdrs For Sbc Calls

    You can also configure it through ini file (SBCCDRFormat) or CLI (configure voip > services cdr > cdr-format sbc-cdr-format).  To customize SBC-related CDRs: Open the SBC CDR Format table (Configuration tab > System menu > Call Detail Record > SBC CDR Format). Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 822 Mediant 1000B Gateway and E- SBC Click Add; the following dialog box appears: Figure 51-4: SBC CDR Format Table - Add Row Dialog Box Configure the CDR according to the parameters described in the table below. Click Add. An example of CDR customization rules configured in the table is shown below:...
  • Page 823 'CDR Type' parameter configured to RADIUS SBC). RADIUS Attribute ID Defines an ID for the RADIUS Attribute. For VSAs, this represents the VSA ID; for standard Attributes, this represents the Attribute ID (first byte Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 824: Configuring Cdr Reporting

    Mediant 1000B Gateway and E- SBC Parameter Description radius-id of the Attribute). [SBCCDRFormat_Radiu The valid value is 0 to 255 (one byte). The default is 0. sID] Notes:  The parameter is applicable only for RADIUS accounting (i.e., 'CDR Type' parameter configured to RADIUS SBC).

  • Page 825: Storing Cdrs On The Device

    Each CDR can contain up to 1023 characters. If it contains more than this, the device removes the extra characters. You can do the following with locally saved CDR files (*.csv), through the CLI (root menu): Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 826 Mediant 1000B Gateway and E- SBC  View stored CDR files: • View all stored CDR files: show storage-history • View all stored, unused CDR files: show storage-history unused  Delete stored CDR files: • Delete all stored files: clear storage-history cdr-storage-history all •...

  • Page 827: Configuring Radius Accounting

    The example shows the attribute in numeric format (32-bit number in 4 bytes). Figure 51-9: Example of Standard RADIUS Attribute Collected by Wireshark  Vendor-specific RADIUS attributes: RADIUS attributes that are specific to the Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 828 Mediant 1000B Gateway and E- SBC device (company) are referred to as Vendor-specific attributes (VSA). The CDR of VSAs are sent with a general RADIUS ID of 26 to indicate that they are vendor- specific (non-standard). In addition, the company's registered vendor ID (as registered with the Internet Assigned Numbers Authority or IANA) is also included in the packet.
  • Page 829 Start Acc type family used on this type=VOIP Stop Acc leg of the call h323- Connect time in NTP String h323- Stop Acc connect-time format connect- time=09:33: 37.657 UTC Mon Dec 08 Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 830 Mediant 1000B Gateway and E- SBC Vendor- Attribute Attribute Specific Value Description Example Name Attribute Format (VSA) ID 2015 h323- Disconnect time in String Stop Acc disconnect- NTP format time h323- Disconnect cause Numeric h323- Stop Acc disconnect- code (Q.850)
  • Page 831 (Standard) A unique accounting String Stop Acc identifier – match start & stop Below is an example of RADIUS Accounting, where non-standard parameters are preceded with brackets: Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 832: Querying Device Channel Resources Using Sip Options

    Mediant 1000B Gateway and E- SBC Accounting-Request (361) user-name = 111 acct-session-id = 1 nas-ip-address = 212.179.22.213 nas-port-type = 0 acct-status-type = 2 acct-input-octets = 4841 acct-output-octets = 8800 acct-session-time = 1 acct-input-packets = 122 acct-output-packets = 220 called-station-id = 201...

  • Page 833: Diagnostics

    Part X Diagnostics...

  • Page 835: Syslog And Debug Recording

    Syslog server (i.e., not to a Debug Recording server), you must enable Syslog functionality, using the 'Enable Syslog' (EnableSyslog) parameter (see ''Enabling Syslog'' on page 848). Enabling Syslog functionality is not required for rules that Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 836 Mediant 1000B Gateway and E- SBC include Syslog messages in the DR sent to a Debug Recording server. • To configure the Syslog server's address, see ''Configuring Address of Syslog Server'' on page 848. To configure additional, global Syslog settings, see Configuring Syslog on page 840.
  • Page 837 (i.e., not per leg). For example, a call between IP Groups 1 and 2 are logged for both legs even if the 'Value' parameter is configured to "!2".  Any to indicate all. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 838 Mediant 1000B Gateway and E- SBC Parameter Description Notes:  You can use the index number or string name to specify the configuration entity for the following 'Filter Types': Tel-to-IP, IP-to-Tel, IP Group, SRD, Classification, IP-to-IP Routing, or SIP Interface. For example, to specify IP Group at Index 2 with the name "SIP Trunk",...

  • Page 839: Filtering Ip Network Traces

    Single expressions for protocol type udp.port, tcp.port Transport layer udp.srcport, tcp.srcport Transport layer for source port udp.dstport, tcp.dstport Transport layer for destination port and, &&, ==, <, > Between expressions Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 840: Configuring Syslog

    Mediant 1000B Gateway and E- SBC Below are examples of configured expressions for the 'Value' parameter:  udp && ip.addr==10.8.6.55  ip.src==10.8.6.55 && udp.port>=5000 and udp.port<6000  ip.dst==10.8.0.1/16  ip.addr==10.8.6.40 For conditions requiring the "or" / "||" expression, add multiple table rows. For example, the Wireshark condition "(ip.src == 1.1.1.1 or ip.src == 2.2.2.2) and ip.dst == 3.3.3.3"...
  • Page 841 The syntax of the session and device identifiers are as follows: [SID=<last 6 characters of device's MAC address>:<number of times device has reset>:<unique SID counter indicating the call session; increments consecutively for each new session; resets to 1 after a device reset>] Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 842: Event Representation In Syslog Messages

    Forked legs and alternative legs share the same session number. Note: You can configure the device to maintain the same SID value for calls traversing multiple AudioCodes' devices. For more information, see 'Maintaining Same Syslog SID/BID over Multiple Devices' on page 844.
  • Page 843 Counts the number of BFI Frames Received From The Host No Available Release Descriptor RTP Reorder Unknown RTP Payload Type RTP SSRC Error Unrecognized Fax Relay Command Invalid Accumulated Packets Counter Invalid Channel ID Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 844: Identifying Audiocodes Syslog Messages Using Facility Levels

    Unknown Aggregation Payload Type Invalid Routing Flag Received 52.2.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.

  • Page 845: Syslog Fields For Answering Machine Detection (Amd)

    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 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 846: Configuring Web User Activities To Report To Syslog

    Mediant 1000B Gateway and E- SBC 52.2.2 Configuring Web User Activities to Report to Syslog The device can report operations (activities) performed in the Web interface by management users, by including them in Syslog messages. The Syslog message indicates these logs with the string, "Activity Log". Each logged user activity includes the following information: ...

  • Page 847: Configuring Syslog Debug Level

    CPU resources during debug reporting, ensuring voice traffic is unaffected. If CPU resources drop (i.e., high CPU usage) to a critical level (user-defined threshold), the device Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 848: Configuring Address Of Syslog Server

    Mediant 1000B Gateway and E- SBC automatically lowers the debug level to free up CPU resources that were required for the previous debug-level functionality. When CPU resources become available again, the device increases the debug level to its' previous setting. For example, if you set...

  • Page 849: Viewing Syslog Messages

    When debug recording is enabled and Syslog messages are also included in the debug recording, to view Syslog messages using Wireshark, you must install AudioCodes' Wireshark plug-in (acsyslog.dll). Once the plug-in is installed, the Syslog messages are decoded as "AC SYSLOG" and displayed using the "acsyslog" filter (instead of the regular "syslog"...

  • Page 850: Viewing Web User Activity Logs

    • 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. 52.2.7 Viewing Web User Activity Logs If you have enabled the reporting of Web user activities, you can view logged activities in the Web interface's Activity Log table (read-only).

  • Page 851: Configuring Debug Recording

    Click Submit. 52.3.2 Collecting Debug Recording Messages To collect debug recording packets, use the open source packet capturing 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 852: Debug Capturing On Physical Voip Interfaces

    Note that the source IP address of the messages is always the OAMP IP address of the device. The device adds the header "AUDIOCODES DEBUG RECORDING" to each debug recording message, as shown below: 52.3.3 Debug Capturing on Physical VoIP Interfaces You can capture traffic on the device's physical (Ethernet LAN) VoIP interfaces (Layer-2 VLAN tagged packets).
  • Page 853 TFTP or FTP server: # debug capture voip physical stop <TFTP/FTP server IP address> If no IP address is defined, the capture is saved on the device for later retrieval. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 854 Mediant 1000B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-27044...

  • Page 855: 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 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 856 Mediant 1000B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-27044...

  • Page 857: 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. You can then provide the files to AudioCodes support team for troubleshooting. ...
  • Page 858 Mediant 1000B Gateway and E- SBC  To save the debug file from the device:  In the Debug Utilities page, click the Save Debug File button. User's Manual Document #: LTRT-27044...

  • Page 859: Fxo Line Testing

    Line polarity (0 = Positive; 1 = Negative)  Message Waiting Indication (0 = Off; 1 = On) Note: Use the Analog Line testing mechanism only for monitoring and never when there are calls in progress. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 860 Mediant 1000B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-27044...

  • Page 861: Testing Sip Signaling Calls

    You can also configure it through ini file (Test_Call) or CLI (configure system > test-call > test-call-table).  To configure a test call: Open the Test Call table (Configuration tab > System menu > Test Call > Test Call Table). Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 862 Mediant 1000B Gateway and E- SBC Click Add; the following dialog box appears: Figure 56-1: Test Call Table - Add Row Dialog Box Configure a test call according to the parameters described in the table below. Click Add, and then save ("burn") your settings to flash memory.
  • Page 863 303. Bandwidth Profile Assigns a Bandwidth Profile to the test call. bandwidth- By default, no value is defined (None). profile To configure Bandwidth Profiles, see 'Configuring Bandwidth Profiles' on [Test_Call_BWProfil page 307. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 864 Mediant 1000B Gateway and E- SBC Parameter Description Authentication Tab Note: These parameters are applicable only if the Call Party parameter is set to Caller. Auto Register Enables automatic registration of the endpoint. The endpoint can register to the device itself or to the 'Destination Address' or 'IP Group' parameter auto-register settings (see above).

  • Page 865: Starting And Stopping Test Calls

    "Running": test call has been started (i.e., the Dial command was clicked)  "Receiving": test call has been automatically activated by calls received for the test call endpoint from the remote endpoint (when all these calls end, the status returns to "Idle") Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 866: Viewing Test Call Statistics

    Mediant 1000B Gateway and E- SBC  "Terminating": test call is in the process of terminating the currently established calls (this occurs if the Drop Call command is clicked to stop the test)  "Done": test call has been successfully completed (or was prematurely stopped by...

  • Page 867: Configuring Dtmf Tones For Test Calls

    The DTMF signaling type (e.g., out-of-band or in-band) can be configured using the 'DTMF Transport Type' parameter. For more information, see 'Configuring DTMF Transport Types' on page 191. • To generate DTMF tones, the device's DSP resources are required. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 868: Configuring Basic Test Call

    Mediant 1000B Gateway and E- SBC  To configure the played DTMF signal to answered test call: Open the Test Call Settings page (Configuration tab > System menu > Test Call > Test Call Settings). Figure 56-3: DTMF in Test Call Settings Page In the 'Test Call DTMF String' field, enter the DTMF string (up to 15 digits).

  • Page 869: Configuring Sbc Test Call With External Proxy

    "101".  To configure SBC call testing: Configure the test call parameters (for a full description, see 'SIP Test Call Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 870: Test Call Configuration Examples

    Mediant 1000B Gateway and E- SBC Parameters' on page 907): Open the Test Call Settings page (Configuration tab > System menu > Test Call > Test Call Settings). Figure 56-7: Test Call Settings Page In the 'Test Call ID' field, enter a prefix number for the simulated test endpoint on the device.
  • Page 871 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 872 Mediant 1000B Gateway and 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 873: Pinging A Remote Host Or Ip Address

    IPv4 address. The ping is done using the following CLI command: # ping <IPv4 ip address or host name> source [voip|data] interface For a complete description of the ping command, refer to the CLI Reference Guide. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 874 Mediant 1000B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-27044...

  • Page 875: Appendix

    Part XI Appendix...

  • Page 877: Dialing Plan Notation For Routing And Manipulation

    4 to 8, and suffix is 234, 235, or 236. The entered value would be the following: [4-8](23[4,5,6]). [n-m] or (n-m) Represents a range of numbers. Examples: Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 878 Mediant 1000B Gateway and E- SBC Notation Description  To depict prefix numbers from 5551200 to 5551300:  [5551200-5551300]#  To depict prefix numbers from 123100 to 123200:  123[100-200]#  To depict prefix and suffix numbers together:  03(100): for any number that starts with 03 and ends with 100.
  • Page 879 "x" wildcards (e.g., xx165xxxxx#); the prefix to add to the number would include the HEX values (e.g., +49 \287303\29 165-). Below is a list of common ASCII characters and their corresponding HEX values: ASCII Character HEX Value Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 880 Mediant 1000B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-27044...

  • Page 881: Configuration Parameters Reference

    The default is 0.0.0.0 (i.e., the device can be accessed from any IP address). For example: WebAccessList_0 = 10.13.2.66 WebAccessList_1 = 10.13.77.7 For a description of the parameter, see 'Configuring Web and Telnet Access List' on page 81. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 882: Web Parameters

    Mediant 1000B Gateway and E- SBC 59.1.2 Web Parameters The Web parameters are described in the table below. Table 59-2: Web Parameters Parameter Description Enable web access from Enables Web access from any of the device's IP network interfaces. all interfaces This feature applies to HTTP and HTTPS protocols.
  • Page 883 = 1, and reset the device with a flash burn (set acSysActionSetResetControl to 1 and acSysActionSetReset to 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 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 884: Telnet Parameters

    Mediant 1000B Gateway and 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 the ini file table parameter is: [WelcomeMessage ]...

  • Page 885: Ini File Parameters

    The valid range is a string of up to 64 characters. auto-send-keep-alive Enables the device to send NAT keep-alive traps to the port of the SNMP network management station (e.g., AudioCodes EMS). Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 886 [SendKeepAliveTrap] 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. It is needed to keep the NAT pinhole open for the SNMP messages sent from EMS to the device.
  • Page 887 For example: 'mngr.corp.mycompany.com'. The valid range is a string of up to 99 characters. SNMP Community String Parameters Community String - Read Only Defines a read-only SNMP community string. Up to five read-only Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 888 Mediant 1000B Gateway and E- SBC Parameter Description configure system > snmp community strings can be configured. > ro-community-string The valid value is a string of up to 19 characters that can include [SNMPReadOnlyCommunityStri only the following: ng_x]  Upper- and lower-case letters (a to z, and A to Z) ...

  • Page 889: Serial Parameters

     [2] = 2-bit Note: For the parameter to take effect, a device reset is required. [SerialFlowControl] Defines the serial communication flow control.  [0] = (Default) None  [1] = Hardware Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 890: Auxiliary And Configuration File Name Parameters

    Mediant 1000B Gateway and E- SBC Parameter Description Note: For the parameter to take effect, a device reset is required. 59.1.7 Auxiliary and Configuration File Name Parameters The configuration files (i.e., Auxiliary files) can be loaded to the device using the Web interface.

  • Page 891: Automatic Update Parameters

    0 is Trunk 1. Dial Plan File Defines the name of the Dial Plan file. This file should be created using AudioCodes DConvert utility (refer to DConvert Utility User's [DialPlanFileName] Guide). For the ini file, the name must be enclosed by single apostrophes, for example, 'dial_plan.dat'.
  • Page 892 Mediant 1000B Gateway and E- SBC Parameter Description Notes:  For the parameter to take effect, a device reset is required.  The actual update time is randomized by five minutes to reduce the load on the Web servers. automatic-update >...
  • Page 893 Defines the name of the cmp file and the path to the server (IP address automatic-update > firmware or FQDN) from where the device can load the cmp file and update itself. The cmp file can be loaded using HTTP/HTTPS. For example, [CmpFileURL] http://192.168.0.1/filename. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 894 Mediant 1000B Gateway and E- SBC Parameter Description Notes:  For the parameter to take effect, a device reset is required.  When the parameter is configured, the device always loads the cmp file after it is reset.  The cmp file is validated before it's burned to flash. The checksum of the cmp file is also compared to the previously burnt checksum to avoid unnecessary resets.

  • Page 895: Networking Parameters

    The table configures the physical Ethernet ports. configure The format of the ini file table parameter is as follows: voip/physical-port [ PhysicalPortsTable ] [PhysicalPortsTable] FORMAT PhysicalPortsTable_Index = PhysicalPortsTable_Port, PhysicalPortsTable_Mode, PhysicalPortsTable_SpeedDuplex, PhysicalPortsTable_PortDescription, PhysicalPortsTable_GroupMember, PhysicalPortsTable_GroupStatus; [ \PhysicalPortsTable ] Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 896: Multiple Voip Network Interfaces And Vlan Parameters

    Mediant 1000B Gateway and E- SBC Parameter Description For a detailed description of the table, see Configuring Physical Ethernet Ports on page 127. Ethernet Group Settings Table Ethernet Group Settings Defines the transmit (Tx) and receive (Rx) settings for the Ethernet port groups.

  • Page 897: Routing Parameters

    Block OSN Port Enables or disables the Ethernet port of the internal switch that interfaces with the OSN. configure system >  [0] Enable (default) interface osn > shutdown  [1] Disable [OSNBlockPort] Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 898: Quality Of Service Parameters

    Mediant 1000B Gateway and E- SBC 59.2.5 Quality of Service Parameters The Quality of Service (QoS) parameters are described in the table below. Table 59-13: QoS Parameters Parameter Description Layer-2 Class Of Service (CoS) Parameters (VLAN Tag Priority Field) DiffServ Table The table configures DiffServ-to-VLAN Priority mapping.

  • Page 899: Nat Parameters

    SendKeepAliveTrap parameter is set to 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 900: Dns Parameters

    Mediant 1000B Gateway and E- SBC Parameter Description The valid range is 0 to 2,592,000. The default is 30. Note: For the parameter to take effect, a device reset is required. [EnableIPAddrTranslation] Enables IP address translation for RTP, RTCP, and T.38 packets.

  • Page 901: Dhcp Parameters

    The parameter is a "hidden" parameter. Once defined and saved to flash memory, its value doesn't revert to default even if the parameter doesn't appear in the ini file. [DHCPSpeedFactor] Defines the device's DHCP renewal speed for a leased IP address from Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 902 Mediant 1000B Gateway and E- SBC Parameter Description a DHCP server.  [0] = Disable  [1] = (Default) Normal  [2] to [10] = Fast When set to 0, the DHCP lease renewal is disabled. Otherwise, the renewal time is divided by this factor. Some DHCP-enabled routers perform better when set to 4.

  • Page 903: Ntp And Daylight Saving Time Parameters

    Secret Key and the NTP server, for authenticating NTP messages. The valid value is a string of up to 32 characters. By default, no key is configure system > ntp > auth-key-md5 defined. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 904 Mediant 1000B Gateway and E- SBC Parameter Description [ntpAuthMd5Key] Regional Clock and Daylight Saving Time Parameters UTC Offset Defines the Universal Time Coordinate (UTC) offset (in seconds) from the local time. utc-offset The valid range is -43200 to 43200. The default is 0.

  • Page 905: Debugging And Diagnostics Parameters

    If the device is in Lifeline mode and the scenario that caused it to enter Lifeline (e.g., power outage) no longer exists (e.g., power returns), the device exists Lifeline and operates as normal.  [0] = (Default) Lifeline is activated upon power outage. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 906 Mediant 1000B Gateway and E- SBC Parameter Description  [1] = Lifeline is activated upon power outage.  [2] = Lifeline is activated upon a power outage network failure (logical link disconnection), or when the Trunk Group is in Busy Out state (see the EnableBusyOut parameter).

  • Page 907: Sip Test Call Parameters

    This can be any string of up to 15 characters. By default, no number is defined. Notes:  The parameter is only for testing incoming calls destined to this prefix number.  This feature is applicable to all applications (Gateway and SBC). Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 908: Syslog, Cdr And Debug Parameters

    Mediant 1000B Gateway and E- SBC Parameter Description SBC Test ID Defines the SBC test call prefix (ID) for identifying SBC test calls that traverse the device to register with an external routing entity such as sbc-test-id an IP PBX or proxy server.
  • Page 909 [3] Update & End Media = Sends a CDR when an update occurs in the media of the call. For example, a call starts and a ringback tone occurs, a re-INVITE is sent for a fax call and as a result, a CDR Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 910 Mediant 1000B Gateway and E- SBC Parameter Description with the MediaReportType field set to "Update" is sent, as the media was changed from voice to T.38. A CDR is also sent upon termination (end) of the media in the call.
  • Page 911 CPU usage decreases to 20% less than the threshold (e.g., 50%), the debug level changes to Detailed (5). Note: The device does not increase the debug level to a level that is higher than what you configured for the 'Debug Level' parameter. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 912 Mediant 1000B Gateway and E- SBC Parameter Description Syslog Facility Number Defines the Facility level (0 through 7) of the device’s Syslog 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’...
  • Page 913 Core Dump Destination IP Defines the IP address of the remote server where you want the device to send the Core Dump file. [CoreDumpDestIP] By default, no IP address is defined. Logging Filters Table Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 914: Resource Allocation Indication Parameters

    Mediant 1000B Gateway and E- SBC Parameter Description Logging Filters Table The table defines logging filtering rules for Syslog messages and debug recordings. configure system > logging > logging- The format of the ini file table parameter is: filters [ LoggingFilters ]...

  • Page 915: Security Parameters

    Defines the time interval (in seconds) that the device periodically checks call resource availability. The valid range is 1 to 200. The default is 10. 59.4 Security Parameters This subsection describes the device's security parameters. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 916: General Security Parameters

    Mediant 1000B Gateway and E- SBC 59.4.1 General Security Parameters The general security parameters are described in the table below. Table 59-22: General Security Parameters Parameter Description Firewall Table Internal Firewall The table defines the device's access list (firewall), which defines network Parameters traffic filtering rules.

  • Page 917: Https Parameters

    Notes:  For the parameter to take effect, a device reset is required.  For a description on implementing client certificates, see 'TLS for Remote Device Management' on page 119. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 918: Srtp Parameters

    Mediant 1000B Gateway and E- SBC 59.4.3 SRTP Parameters The Secure Real-Time Transport Protocol (SRTP) parameters are described in the table below. Table 59-24: SRTP Parameters Parameter Description Media Security Enables Secure Real-Time Transport Protocol (SRTP).  [0] Disable (default)

  • Page 919: Tls Parameters

    > The format of the ini file table parameter is as follows: tls # [ TLSContexts ] FORMAT TLSContexts_Index = TLSContexts_Name, [TLSContexts] TLSContexts_TLSVersion, TLSContexts_ServerCipherString, TLSContexts_ClientCipherString, TLSContexts_OcspEnable, TLSContexts_OcspServerPrimary, TLSContexts_OcspServerSecondary, TLSContexts_OcspServerPort, TLSContexts_OcspDefaultResponse; Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 920 Mediant 1000B Gateway and E- SBC Parameter Description [ \TLSContexts ] For a detailed description of the table, see 'Configuring TLS Certificate Contexts' on page 109. TLS Client Re- Defines the time interval (in minutes) between TLS Re-Handshakes Handshake Interval initiated by the device.

  • Page 921: Ssh Parameters

    Enables the device's embedded SSH server.  [0] Disable (default)  [1] Enable [SSHServerEnable] Server Port Defines the port number for the embedded SSH server. ssh-port Range is any valid port number. The default port is 22. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 922 Mediant 1000B Gateway and E- SBC Parameter Description [SSHServerPort] SSH Admin Key Defines the RSA public key for strong authentication for logging in to the SSH interface (if enabled). ssh-admin-key The value should be a base64-encoded string. The value can be a [SSHAdminKey] maximum length of 511 characters.

  • Page 923: Ids Parameters

    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 the table, see 'Assigning IDS Policies' on page 171. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 924: Ocsp Parameters

    Mediant 1000B Gateway and E- SBC 59.4.7 OCSP Parameters The Online Certificate Status Protocol (OCSP) parameters are described in the table below. Table 59-28: OCSP Parameters Parameter Description Enable OCSP Server Enables or disables certificate checking using OCSP.  [0] Disable (default) enable ...

  • Page 925: Quality Of Experience Parameters

    Note: If a QoE traffic overflow between SEM and the device occurs, the device sends the QoE data only at the end of the call, regardless of the settings of the parameter. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 926 Mediant 1000B Gateway and E- SBC Parameter Description Quality of Experience Profile Table Quality of Experience The table defines Quality of Experience Profiles. Profile The format of the ini file table parameter is as follows: configure voip/qoe [QOEProfile] qoe-profile FORMAT QOEProfile_Index = QOEProfile_Name, [QOEProfile] QOEProfile_SensitivityLevel;...
  • Page 927 The format of the ini file table parameter is as follows: configure voip/qoe [MediaEnhancementRules] media-enhancement- FORMAT MediaEnhancementRules_Index = rules MediaEnhancementRules_MediaEnhancementProfile, [MediaEnhancementRule MediaEnhancementRules_RuleIndex, MediaEnhancementRules_Trigger, MediaEnhancementRules_Color, MediaEnhancementRules_ActionRule, MediaEnhancementRules_ActionValue; [\MediaEnhancementRules] For a detailed description of the table, see 'Configuring Media Enhancement Profiles' on page 309. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 928: Control Network Parameters

    Mediant 1000B Gateway and E- SBC 59.6 Control Network Parameters 59.6.1 IP Group, Proxy, Registration and Authentication Parameters The proxy server, registration and authentication SIP parameters are described in the table below. Table 59-30: Proxy, Registration and Authentication SIP Parameters...
  • Page 929 REGISTER messages sent to these proxies are sent with the same host name. Note: If the parameter is disabled and the ProxyName parameter is not configured, the proxy's IP address is used as the host name in the REGISTER Request-URI. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 930 Mediant 1000B Gateway and E- SBC Parameter Description Redundancy Mode Determines whether the device switches back to the primary Proxy after using a redundant Proxy. redundancy-mode  [0] Parking = (Default) The device continues working with a [ProxyRedundancyMode] redundant (now active) Proxy until the next failure, after which it works with the next redundant Proxy.
  • Page 931 IP addresses each, no additional searches are performed.  [2] NAPTR = NAPTR query is done. If successful, an SRV query is sent according to the information received in the NAPTR response. If Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 932 Mediant 1000B Gateway and E- SBC Parameter Description the NAPTR query fails, an SRV query is done according to the configured transport type. If the Proxy IP address parameter contains a domain name with port definition (e.g., ProxyIP = domain.com:5080), the device performs a regular DNS A-record query.
  • Page 933 ProxySet_EnableProxyKeepAlive, ProxySet_ProxyKeepAliveTime, ProxySet_ProxyLoadBalancingMethod, ProxySet_IsProxyHotSwap, ProxySet_SRDName, ProxySet_ClassificationInput, ProxySet_TLSContextName, ProxySet_ProxyRedundancyMode, ProxySet_DNSResolveMethod, ProxySet_KeepAliveFailureResp, ProxySet_GWIPv4SIPInterfaceName, ProxySet_SBCIPv4SIPInterfaceName, ProxySet_SASIPv4SIPInterfaceName, ProxySet_GWIPv6SIPInterfaceName, ProxySet_SBCIPv6SIPInterfaceName, ProxySet_SASIPv6SIPInterfaceName; [ \ProxySet ] For a description of the table, see 'Configuring Proxy Sets' on page 348. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 934 Mediant 1000B Gateway and E- SBC Parameter Description Registrar Parameters Enable Registration Enables the device to register to a Proxy/Registrar server.  enable-registration [0] Disable = (Default) The device doesn't register to Proxy/Registrar server. [IsRegisterNeeded]  [1] Enable = The device registers to Proxy/Registrar server when the device is powered up and at every user-defined interval (configured by the parameter RegistrationTime).
  • Page 935 100 Trying provisional response (indicative of a home proxy server failure). Note: The parameter is applicable only to the Gateway application. ReRegister On Enables the device to perform SIP re-registration upon TCP/TLS Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 936 Mediant 1000B Gateway and E- SBC Parameter Description Connection Failure connection failure.  reg-on-conn-failure [0] Disable (default)  [1] Enable [ReRegisterOnConnection Failure] Gateway Registration Defines the user name that is used in the From and To headers in SIP Name REGISTER messages.
  • Page 937 (used for example, to keep NAT bindings open). For connection- oriented transports such as TCP/TLS this is based on CRLF. This mechanism uses a client-to-server "ping" keep-alive and a Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 938 Mediant 1000B Gateway and E- SBC Parameter Description corresponding server-to-client "pong" message. This ping-pong sequence allows the client, and optionally the server, to tell if its flow is still active and useful for SIP traffic. If the client does not receive a pong in response to its ping, it declares the flow “dead”...

  • Page 939: Network Application Parameters

    The valid value is 10 to 65,000. The default is 10. Note: TCP keepalive is enabled per SIP Interface in the SIP Interface Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 940 Mediant 1000B Gateway and E- SBC Parameter Description table. [TCPKeepAliveRetry] Defines the number of unacknowledged keep-alive probes to send before considering the connection down. The valid value is 1 to 100. The default is 5. Note: TCP keepalive is enabled per SIP Interface in the SIP Interface table.
  • Page 941 The format of the ini file table parameter is as follows: [ MediaRealmExtension ] FORMAT MediaRealmExtension_Index = MediaRealmExtension_MediaRealmIndex, MediaRealmExtension_ExtensionIndex, MediaRealmExtension_IPv4IF, MediaRealmExtension_IPv6IF, MediaRealmExtension_PortRangeStart, MediaRealmExtension_PortRangeEnd, MediaRealmExtension_MediaSessionLeg; [ \MediaRealmExtension ] For a detailed description of the table, see 'Configuring Media Realm Extensions' on page 318. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 942: General Sip Parameters

    (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. Max SIP Message Length Defines the maximum size (in Kbytes) for each SIP message that can [KB] be sent over the network.
  • Page 943 PR=<voice packets received>  OR=<voice octets received>  PL=<receive packet loss>  JI=<jitter in ms>  LA=<latency in ms> Below is an example of the X-RTP-Stat header in a SIP BYE message: Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 944 Mediant 1000B Gateway and E- SBC Parameter Description BYE sip:302@10.33.4.125 SIP/2.0 Via: SIP/2.0/UDP 10.33.4.126;branch=z9hG4bKac2127550866 Max-Forwards: 70 From: <sip:401@10.33.4.126;user=phone>;tag=1c2113553324 To: <sip:302@company.com>;tag=1c991751121 Call-ID: 991750671245200001912@10.33.4.125 CSeq: 1 BYE X-RTP-Stat: PS=207;OS=49680;;PR=314;OR=50240;PL=0;JI=600;LA=40; Supported: em,timer,replaces,path,resource-priority Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK ,REFER,INFO,SUBSCRIBE,UPDATE User-Agent: Sip-Gateway-/v.6.80A.227.005 Reason: Q.850 ;cause=16 ;text="local" Content-Length: 0...
  • Page 945 The valid range is 1 to 86,400 sec. The default is 0 (i.e., the Session- Expires header is disabled). [SIPSessionExpires] Note: The parameter is applicable only to the Gateway application. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 946 Mediant 1000B Gateway and E- SBC Parameter Description Minimum Session-Expires Defines the time (in seconds) that is used in the Min-SE header. This header defines the minimum time that the user agent refreshes the min-session-expires session. [MinSE] The valid range is 10 to 100,000. The default is 90.
  • Page 947 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 coders, allowing a subsequent bypass (passthrough) session if fax/modem signals are detected during the call. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 948 Mediant 1000B Gateway and E- SBC Parameter Description Note: The 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). fax-vbd-behvr Determines the device's fax transport behavior when G.711 VBD coder is negotiated at call start.
  • Page 949 TCP Timeout Defines the Timer B (INVITE transaction timeout timer) and Timer F (non-INVITE transaction timeout timer), as defined in RFC 3261, when tcp-timeout Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 950 Mediant 1000B Gateway and E- SBC Parameter Description [SIPTCPTimeout] the SIP transport type is TCP. The valid range is 0 to 40 sec. The default is 64 * SipT1Rtx parameter value. For example, if SipT1Rtx is set to 500 msec, then the default of SIPTCPTimeout is 32 sec.
  • Page 951 For IP-to-ISDN calls: - The device interworks the SIP tgrp=hotline parameter (received in INVITE) to ISDN Setup with the Off Hook Indicator IE of “Voice”, and “Speech” Bearer Capability IE. Note that the Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 952 Mediant 1000B Gateway and E- SBC Parameter Description Off Hook Indicator IE is described in UCR 2008 specifications. - The device interworks the SIP tgrp=hotline-ccdata parameter (received in INVITE) to ISDN Setup with an Off Hook Indicator IE of “Data”, and with “Unrestricted 64k” Bearer Capability IE.
  • Page 953 If the REGISTER is per the device’s client (endpoint), it is the MAC address concatenated with the phone number of the client.  If the REGISTER is per device, it is the MAC address only. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 954 When configured, the string <UserAgentDisplayInfo user-agent-info value>/software version' is used, for example: [UserAgentDisplayInfo] User-Agent: myproduct/v.6.80A.227.005 If not configured, the default string, <AudioCodes product- name>/software version' is used, for example: User-Agent: Audiocodes-Sip-Gateway-Medaint 1000B Gateway and SBC/v.6.80A.227.005 The maximum string length is 50 characters.
  • Page 955 'ptime' value in the following precedence: from 'mptime' attribute, from 'ptime' attribute, and then from default value. [EnablePtime] Determines whether the 'ptime' attribute is included in the SDP.  [0] = Remove the 'ptime' attribute from SDP. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 956 Mediant 1000B Gateway and E- SBC Parameter Description  [1] = (Default) Include the 'ptime' attribute in SDP. 3xx Behavior Determines the device's behavior regarding call identifiers when a 3xx response is received for an outgoing INVITE request. The device can...
  • Page 957 [1] = Sets the IP address of the outgoing SDP c= field to the IP address of the device. If the incoming SDP doesn’t contain the "a=inactive" line, the returned SDP contains the "a=recvonly" line. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 958 Mediant 1000B Gateway and E- SBC Parameter Description Enable Delayed Offer Determines whether the device sends the initial INVITE message with or without an SDP. Sending the first INVITE without SDP is typically delayed-offer done by clients for obtaining the far-end's full list of capabilities before [EnableDelayedOffer] sending their own offer.
  • Page 959 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  '8' is the B-channel  'IP=192.168.13.1' is the device's IP address Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 960 Mediant 1000B Gateway and E- SBC Parameter Description Progress Indicator to IP Global parameter that defines the progress indicator (PI) sent to the IP. You can also configure this functionality per specific calls, using IP prog-ind-2ip Profiles (IpProfile_ProgressIndicator2IP) or Tel Profiles. For a detailed...
  • Page 961 SDP received from the remote side.  [0] Disable (default)  [1] Enable Comfort Noise Generation Enables negotiation and usage of Comfort Noise (CN) for Gateway Negotiation calls.  com-noise-gen-nego [0] Disable Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 962 Mediant 1000B Gateway and E- SBC Parameter Description  [ComfortNoiseNegotiation [1] Enable (default) The use of CN is indicated by including a payload type for CN on the media description line of the SDP. The device can use CN with a codec whose RTP time stamp clock rate is 8,000 Hz (G.711/G.726).
  • Page 963 INVITE, it generates a ring to the phone and sends a SIP 180 Ringing response to the IP. If the phone is not answered within the time interval set by the parameter, the device cancels the call Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 964 Mediant 1000B Gateway and E- SBC Parameter Description by sending a SIP 408 response. The valid value range is 1 to 600 (in seconds). The default is 180. Note: If per trunk configuration (using TrunkPSTNAlertTimeout) is set to other than default, the PSTNAlertTimeout parameter value is overridden.
  • Page 965 Digital: All trunks (E1/T1/BRI) are automatically taken out-of-service by taking down the D-Channel, or for T1 PRI trunks, by sending a Service Out message supporting these messages (NI-2, 4/5-ESS, DMS-100, and Meridian). Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 966 Mediant 1000B Gateway and E- SBC Parameter Description The above behavior is done upon one of the following scenarios:  The device is physically disconnected from the network (i.e., Ethernet cable is disconnected).  The Ethernet cable is connected, but the device is unable to communicate with any host.
  • Page 967 Graceful out-of-service enabled: The device rejects new incoming calls and only when all channels are idle (when graceful period ends or when all channels become idle before graceful period ends, whichever occurs first), does the device Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 968 Mediant 1000B Gateway and E- SBC Parameter Description send an alarm on the trunk. When connectivity is restored for the Busy Out feature or the Trunk Group is unlocked, the device clears the alarm. Note: For partially configured trunks (only some channels configured), this option only rejects new calls for the trunk;...
  • Page 969 [1] Reorder Tone = (Default) The device plays a reorder tone to the connected phone / PBX.  [2] Polarity Reversal = The device reverses the polarity of the endpoint making it unusable (relevant, for example, for PBX DID Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 970 Mediant 1000B Gateway and E- SBC Parameter Description lines).  [3] Reorder Tone + Polarity Reversal = Same as options [1] and [2].  [4] Current Disconnect = The device disconnects the current to the FXS endpoint. Notes:  A device reset is required for the parameter to take effect when it is set to [2], [3], or [4].

  • Page 971: Coders And Profile Parameters

    For a list of supported coders and a description of the table, see [CodersGroup7] Configuring Default Coders on page 375. [CodersGroup8]  For configuring Coder Groups, see 'Configuring Coder Groups' on [CodersGroup9] page 379. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 972 Mediant 1000B Gateway and E- SBC Parameter Description  The coder name is case-sensitive. IP Profile Settings Table IP Profile Settings Defines the IP Profile table. The format of the ini file table parameter is as follows: configure voip >...
  • Page 973 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 the parameter, see Configuring Tel Profiles on page 381. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 974: Channel Parameters

    Mediant 1000B Gateway and E- SBC 59.9 Channel Parameters This subsection describes the device's channel parameters. 59.9.1 Voice Parameters The voice parameters are described in the table below. Table 59-34: Voice Parameters Parameter Description Input Gain Global parameter that defines the pulse-code modulation (PCM) input (received) gain control level (in decibels).
  • Page 975 [2] = Silence output NLP Note: The parameter can also be configured in a Tel Profile. echo-canceller- Enables the Aggressive NLP at the first 0.5 second of the call. aggressive-NLP  [0] = Disable Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 976: Coder Parameters

    Mediant 1000B Gateway and E- SBC Parameter Description  [1] = (Default) Enable. The echo is removed only in the first [EchoCancellerAggressiveNLP] half of a second of the incoming IP signal. Note: For the parameter to take effect, a device reset is required.

  • Page 977: Dtmf Parameters

    [3] RFC 2833 Relay DTMF = (Default) DTMF digits are removed from the voice stream and are relayed to remote side according to RFC 2833.  [7] RFC 2833 Relay Decoder Mute = DTMF digits are sent Version 7.0 Mediant 1000B Gateway and E- SBC...

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

    Mediant 1000B Gateway and E- SBC Parameter Description according to RFC 2833 and muted when received. Note: The parameter is automatically updated if the parameters FirstTxDTMFOption or RxDTMFOption are configured. DTMF Volume (-31 to 0 dB) Defines the DTMF gain control value (in decibels) to the Tel side.
  • Page 979 Currently, the negotiation of “RED” payload type is not supported and therefore, it should be configured to the same PT value for both parties. RFC 2198 Payload Type Defines the RTP redundancy packet payload type (according to RFC 2198). RTP-redundancy-payload- Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 980 Mediant 1000B Gateway and E- SBC Parameter Description type The valid value is 96 to 127. The default is 104. [RFC2198PayloadType] Note: The parameter is applicable only if the RTPRedundancyDepth parameter is set to 1. Packing Factor N/A. Controlled internally by the device according to the selected coder.
  • Page 981 The default is -1 (i.e., no alerts are issued). R-Value Delay Threshold Defines the voice quality monitoring - end of call low quality alert threshold. [VQMonEOCRValTHR] The default is -1 (i.e., no alerts are issued). Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 982 Mediant 1000B Gateway and E- SBC Parameter Description RTCP XR Packet Interval Defines the time interval (in msec) between adjacent RTCP XR reports. This interval starts from call establishment. Thus, the rtcp-interval device can send RTCP XR reports during the call, in addition to at [RTCPInterval] the end of the call.

  • Page 983: Gateway Application Parameters

    You can also configure this functionality per specific calls, using IP Profiles (IpProfile_VxxTransportType). For more information, see 'Configuring IP Profiles' on page 385. V.34 Modem Transport Type Determines the V.90/V.34 modem transport type.  [0] Disable = Transparent. V34-modem-transport- Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 984 Mediant 1000B Gateway and E- SBC Parameter Description  [2] Enable Bypass (default) type  [3] Events Only = Transparent with Events. [V34ModemTransportType] Note: You can also configure this functionality per specific calls, using IP Profiles (IpProfile_VxxTransportType). For more information, see 'Configuring IP Profiles' on page 385.
  • Page 985 Defines the fax bypass RTP dynamic payload type. The valid range is 96 to 120. The default is 102. fax-bypass-payload-type [FaxBypassPayloadType] modem-bypass-payload- Defines the modem bypass dynamic payload type. type The range is 0-127. The default is 103. [ModemBypassPayloadType] Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 986 Mediant 1000B Gateway and E- SBC Parameter Description volume Defines the fax gain control. [FaxModemRelayVolume] The range is -18 to -3, corresponding to -18 dBm to -3 dBm in 1-dB steps. The default is -6 dBm fax gain control. Fax Bypass Output Gain Defines the fax bypass output gain control.
  • Page 987 To overcome this, the device sends No-Op (“no-signal”) packets to open a pinhole in the NAT for the answering fax machine. The originating fax does not wait for an answer, but immediately starts Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 988: Dtmf And Hook-Flash Parameters

    Mediant 1000B Gateway and E- SBC Parameter Description sending T.38 packets to the terminating fax machine. Note: To enable No-Op packet transmission, use the NoOpEnable and NoOpInterval parameters. 59.10.2 DTMF and Hook-Flash Parameters The DTMF and hook-flash parameters are described in the table below.
  • Page 989 'Configuring IP Profiles' on page 385. 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 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 990 Mediant 1000B Gateway and E- SBC Parameter Description First Tx DTMF Option Defines the first preferred transmit (Tx) DTMF negotiation method.  configure voip > gw [0] Not Supported = (Default) No negotiation - DTMF digits are dtmf-and-suppl sent according to the parameters DTMFTransportType and dtmf-and-dialing >...
  • Page 991 (before or during dialing of destination phone number). Therefore, the parameter IsWaitForDialTone (configurable for the entire device) is ignored.  For analog interfaces: The FXS interface send SIP 200 OK responses only after the DTMF dialing is complete. Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 992: Digit Collection And Dial Plan Parameters

    Mediant 1000B Gateway and E- SBC Parameter Description  The parameter can also be configured in a Tel Profile. replace-nb-sign-w- Determines whether to replace the number sign (#) with the escape character (%23) in outgoing SIP messages for Tel-to-IP calls.
  • Page 993 ISDN overlap dialing is used (ISDNRxOverlap is set to 1).  If the DialPlanIndex parameter is configured (to select a Dial Plan index), then the device first attempts to locate a matching Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 994 Mediant 1000B Gateway and E- SBC Parameter Description digit pattern in the Dial Plan file, and if not found, then attempts to locate a matching digit pattern in the Digit Map rules configured by the DigitMapping parameter.  For more information on digit mapping, see 'Digit Mapping' on page 511.

  • Page 995: Voice Mail Parameters

    If the device receives a Request-URI that includes a 'target' and 'cause' parameter, the 'target' is mapped to the Redirect phone number and the 'cause' is mapped to the Redirect number reason. Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 996 Mediant 1000B Gateway and E- SBC Parameter Description [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 997 MWI Source Number Defines the calling party's phone number used in the Q.931 MWI Setup message to PSTN. If not configured, the channel's phone mwi-source-number number is used as the calling number. [MWISourceNumber] Version 7.0 Mediant 1000B Gateway and E- SBC...
  • Page 998 Mediant 1000B Gateway and E- SBC Parameter Description mwi-subs-ipgrpid Defines the IP Group ID used when subscribing to an MWI server. The 'The SIP Group Name' field value of the IP Group table is used [MWISubscribeIPGroupID as the Request-URI host name in the outgoing MWI SIP SUBSCRIBE message.
  • Page 999 The valid range is a 120-character string. [DigitPatternInternalCall] External Call Digit Pattern Defines the digit pattern used by the PBX to indicate an external call. ext-call-dig-ptrn The valid range is a 120-character string. [DigitPatternExternalCall] Version 7.0 Mediant 1000B Gateway and E- SBC...

  • Page 1000: Supplementary Services Parameters

    Mediant 1000B Gateway and E- SBC Parameter Description Disconnect Call Digit Defines a digit pattern that when received from the Tel side, indicates Pattern the device to disconnect the call. disc-call-dig-ptrn The valid range is a 25-character string. [TelDisconnectCode] Digit To Ignore Digit...
  • Page 1001 Caller ID detection for Britain [4] is not supported on the device’s FXO ports. Only FXS ports can generate the Britain [4] Caller ID.  To select the Bellcore Caller ID sub standard, use the BellcoreCallerIDTypeOneSubStandard parameter. To select the Version 7.0 1001 Mediant 1000B Gateway and E- SBC...
  • Page 1002 Mediant 1000B Gateway and E- SBC Parameter Description ETSI Caller ID substandard, use the ETSICallerIDTypeOneSubStandard parameter.  To select the Bellcore MWI sub standard, use the BellcoreVMWITypeOneStandard parameter. To select the ETSI MWI sub standard, use the ETSIVMWITypeOneStandard parameter. ...
  • Page 1003 The 200 OK response can contain the connected party CallerID - Connected Number and Connected Name. For example, if the call is answered by the device, the 200 OK response includes the P- Version 7.0 1003 Mediant 1000B Gateway and E- SBC...
  • Page 1004 Mediant 1000B Gateway and E- SBC Parameter Description Asserted-Identity with Caller ID. The device interworks (in some ISDN variants), the Connected Party number and name from Q.931 Connect message to SIP 200 OK with the P-Asserted-Identity header. In the opposite direction, if the ISDN device receives a 200 OK with P- Asserted-Identity header, it interworks it to the Connected party number and name in the Q.931 Connect message, including its...

  • Page 1005: Call Waiting Parameters

    CallWaitingPerPort 1 = 1,1,2; (call waiting enabled for Port 2 of Module Notes:  The parameter is applicable only to FXS ports.  For a detailed description of the table, see Configuring Call Waiting on page 566. Version 7.0 1005 Mediant 1000B Gateway and E- SBC...
  • Page 1006 Mediant 1000B Gateway and E- SBC Parameter Description Number of Call Waiting Defines the number of call waiting indications that are played to the Indications called telephone that is connected to the device for Call Waiting. nb-of-cw-ind The valid range is 1 to 100 indications. The default is 2.

  • Page 1007: Call Forwarding Parameters

    FwdInfo 1 = 1,2003@10.5.1.1,30,1,2; For a detailed description of the table, see Configuring Call Forward on page 563. Note: The parameter is applicable only to FXS and FXO interfaces. Call Forward Reminder Ring Parameters Version 7.0 1007 Mediant 1000B Gateway and E- SBC...

  • Page 1008: Message Waiting Indication Parameters

    Mediant 1000B Gateway and E- SBC Parameter Description Notes:  These parameters are applicable only to FXS interfaces.  For a description of this feature, see Call Forward Reminder Ring on page 523. Enable NRT Enables endpoint subscription for Ring reminder event notification feature.
  • Page 1009 Determines the ETSI Visual Message Waiting Indication (VMWI) Type 1 etsi-vmwi-type- one-standard sub-standard.  [ETSIVMWITypeOneSt [0] = (Default) ETSI VMWI between rings andard]  [1] = ETSI VMWI before ring DT_AS Version 7.0 1009 Mediant 1000B Gateway and E- SBC...

  • Page 1010: Call Hold Parameters

    Mediant 1000B Gateway and E- SBC Parameter Description  [2] = ETSI VMWI before ring RP_AS  [3] = ETSI VMWI before ring LR_DT_AS  [4] = ETSI VMWI not ring related DT_AS  [5] = ETSI VMWI not ring related RP_AS ...

  • Page 1011: Call Transfer Parameters

    Notes:  To use call transfer, the devices at both ends must support this option.  To use call transfer, set the parameter EnableHold to 1. Version 7.0 1011 Mediant 1000B Gateway and E- SBC...
  • Page 1012 Mediant 1000B Gateway and E- SBC Parameter Description Transfer Prefix Defines the string that is added as a prefix to the transferred/forwarded called number when the REFER/3xx message is received. transfer-prefix Notes: [xferPrefix]  The number manipulation rules apply to the user part of the Refer-To and/or Contact URI before it is sent in the INVITE message.

Table of Contents