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

Gateway & enterprise 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

See also: Quick Manual
User's Manual
AudioCodes Family of Media Gateways & Session Border Controllers (SBC)
Mediant™ 1000B
Gateway & Enterprise SBC
Version 7.2

Advertisement

Table of Contents
loading

Related Manuals for AudioCodes Mediant 1000B

Summary of Contents for AudioCodes Mediant 1000B

  • Page 1 User's Manual AudioCodes Family of Media Gateways & Session Border Controllers (SBC) Mediant™ 1000B Gateway & Enterprise SBC Version 7.2...

  • Page 3: Table Of Contents

    6.2.2 Customizing the Product Name ................69 6.2.3 Customizing the Favicon ..................70 6.2.4 Creating a Login Welcome Message ............... 71 Configuring Additional Management Interfaces ............. 72 Configuring Management User Accounts .............. 74 Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 4 Mediant 1000B Gateway & E-SBC Displaying Login Information upon Login ............... 78 Viewing Logged-In User Information ..............79 Configuring Web Session and Access Settings ............. 79 Changing Login Password for Administrator and Monitor Users ......80 Configuring Secured (HTTPS) Web ............... 81 6.10 Web Login Authentication using Smart Cards ............
  • Page 5 12.11.1 Configuring Native VLAN for OSN Server .............167 12.11.2 Disabling Internal Switch Port for OSN ..............168 12.12 Robust Receipt of Media Streams by Media Latching ......... 169 12.13 Multiple Routers Support ..................169 Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 6 Mediant 1000B Gateway & E-SBC 13 Security ......................171 13.1 Configuring Firewall Settings ................171 13.2 Configuring General Security Settings ..............175 13.3 Intrusion Detection System .................. 176 13.3.1 Enabling IDS ......................177 13.3.2 Configuring IDS Policies ..................177 13.3.3 Assigning IDS Policies ...................181 13.3.4 Viewing IDS Alarms ....................183...
  • Page 7 15.7.1 About E9-1-1 Services ...................292 15.7.2 Microsoft Skype for Business and E9-1-1 .............293 15.7.2.1 Gathering Location Information of Skype for Business Clients for 911 Calls 15.7.2.2 Adding ELINs to the Location Information Server ......... 295 Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 8 Mediant 1000B Gateway & E-SBC 15.7.2.3 Passing Location Information to the PSTN Emergency Provider ..296 15.7.3 AudioCodes ELIN Device for Skype for Business E9-1-1 Calls to PSTN .....297 15.7.3.1 Detecting and Handling E9-1-1 Calls ............ 298 15.7.3.2 Pre-empting Existing Calls for E9-1-1 Calls .......... 300 15.7.3.3 PSAP Callback to Skype for Business Clients for Dropped E9-1-1 Calls...
  • Page 9 22.8 Redirect Number and Calling Name (Display) ............. 500 23 Trunk Groups ....................503 23.1 Configuring Trunk Groups ..................503 23.2 Configuring Trunk Group Settings Table .............. 505 24 Routing ......................511 24.1 Configuring Tel-to-IP Routing Rules ..............511 Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 10 Mediant 1000B Gateway & E-SBC 24.2 Configuring IP-to-Tel Routing Rules ..............520 24.3 Configuring a Gateway Routing Policy Rule ............525 24.4 Alternative Routing for Tel-to-IP Calls ..............527 24.4.1 IP Destinations Connectivity Feature ..............527 24.4.2 Alternative Routing Based on IP Connectivity ............528 24.4.3 Alternative Routing Based on SIP Responses ............530...
  • Page 11 28.13.1 FXO Operations for IP-to-Tel Calls ................631 28.13.1.1 One-Stage Dialing ................. 632 28.13.1.2 Two-Stage Dialing ................. 633 28.13.1.3 DID Wink ....................633 28.13.2 FXO Operations for Tel-to-IP Calls ................634 28.13.2.1 Automatic Dialing .................. 634 Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 12 Mediant 1000B Gateway & E-SBC 28.13.2.2 Collecting Digits Mode................635 28.13.2.3 FXO Supplementary Services ............... 635 28.13.3 Call Termination on FXO Devices .................636 28.13.3.1 Calls Termination by PBX ..............636 28.13.3.2 Call Termination before Call Establishment .......... 637 28.13.3.3 Ring Detection Timeout ................. 637 28.14 Remote PBX Extension between FXO and FXS Devices ........
  • Page 13 38.1 Configuring Call Preemption for SBC Emergency Calls ........753 38.2 Emergency Call Routing using LDAP to Obtain ELIN .......... 754 38.3 Enabling Interworking of SIP and SIP-I Endpoints ..........755 38.4 Call Forking ......................757 Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 14 Mediant 1000B Gateway & E-SBC 38.4.1 Initiating SIP Call Forking ..................757 38.4.2 Configuring SIP Forking Initiated by SIP Proxy .............758 38.4.3 Configuring Call Forking-based IP-to-IP Routing Rules ........758 38.5 Call Survivability ....................758 38.5.1 Enabling Auto-Provisioning of Subscriber-Specific Information of BroadWorks Server for Survivability ......................759...
  • Page 15 47.1.1.2 Provisioning from TFTP Server using DHCP Option 66 ....... 831 47.1.2 HTTP-based Provisioning ..................832 47.1.3 FTP-based Provisioning ..................833 47.1.4 Provisioning using AudioCodes EMS ..............833 47.2 HTTP/S-Based Provisioning using the Automatic Update Feature ...... 833 47.2.1 Files Provisioned by Automatic Update ..............834 47.2.2 File Location for Automatic Update ...............834...
  • Page 16 Mediant 1000B Gateway & E-SBC 47.2.10.3 Automatic Update for Mass Deployment ..........845 48 SBC Configuration Wizard ................849 48.1 Starting the SBC Configuration Wizard ..............850 48.2 General Setup Page ..................... 851 48.3 System Page ......................853 48.4 Interfaces Page ....................854 48.5 IP-PBX Page ......................
  • Page 17 58.2.1 Syslog Message Format ..................960 58.2.1.1 Event Representation in Syslog Messages .......... 963 58.2.1.2 Identifying AudioCodes Syslog Messages using Facility Levels ..964 58.2.1.3 Syslog Fields for Answering Machine Detection (AMD) ....... 965 58.2.1.4 SNMP Alarms in Syslog Messages ............965 58.2.2 Enabling Syslog .....................966...
  • Page 18 Mediant 1000B Gateway & E-SBC 59 Self-Testing ...................... 973 60 Debugging Web Services ................975 61 Creating Core Dump and Debug Files upon Device Crash ......977 62 Analog Line Testing ..................979 62.1 FXS Line Testing ....................979 62.2 FXO Line Testing ....................980 63 Testing SIP Signaling Calls ................
  • Page 19 IP Connectivity Parameters ................1218 65.10.14 Alternative Routing Parameters ..............1220 65.10.15 Number Manipulation Parameters ..............1222 65.11 SBC Parameters ....................1232 65.11.1 Supplementary Services ..................1251 65.12 IP Media Parameters ..................1252 65.13 Services ......................1257 Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 20 Mediant 1000B Gateway & E-SBC 65.13.1 RADIUS and LDAP Parameters ................. 1257 65.13.1.1 General Parameters ................1257 65.13.1.2 RADIUS Parameters ................1258 65.13.1.3 LDAP Parameters ................1260 65.13.2 Least Cost Routing Parameters ................. 1263 65.13.3 Call Setup Rules Parameters ................1264 65.13.4 HTTP-based Services ..................

  • Page 21: Weee Eu Directive

    Customer Support Customer technical support and services are provided by AudioCodes or by an authorized AudioCodes Service Partner. For more information on how to buy technical support for AudioCodes products and for contact information, please visit our Web site at www.audiocodes.com/support.
  • Page 22 Some of the features listed in this document are available only if the relevant License Key has been purchased from AudioCodes and installed on the device. For a list of License Keys that can be purchased, please consult your AudioCodes sales representative.
  • Page 23 Buyer may receive such source code by contacting AudioCodes, by following the instructions available on AudioCodes website.
  • Page 24 Mediant 1000B Gateway & E-SBC LTRT Description Group load balancing); MAC Address Placeholder in Configuration File Name; Technical Specifications (AMR-WB removed).  New sections: Configuring IP Group Sets.  Updated parameters: SIPInterface_SBCDirectMedia; IPProfile_SBCDirectMediaTag; IpProfile_DisconnectOnBrokenConnection; IP2IPRouting_DestType; IPOutboundManipulation_PrivacyRestrictionMode; BrokenConnectionEventTimeout.  New parameters: IP2IPRouting_IPGroupSetName; EnableNonCallCdr; PGroupSet;...
  • Page 25 IpProfile_SBCPlayHeldTone; IP2IPRouting_Trigger (6); IP2IPRouting_DestType (12); DialPlanRule_Tag; SBCCDRFormat_FieldType (818); Test_Call_RouteBy; Test_Call_Play (tone); KeepAliveTrapPort (default); SBCtestID (removed); ProxyIPListRefreshTime; RegistrationRetryTime (note); EnableReansweringINFO; EnablePChargingVector (note); EnableTDMoverIP (2); EnableSBCApplication (default).  New parameters: DeviceTable_MTU; SRD_SBCDialPlanName; SIPInterface_PreParsingManSetName; IPGroup_Tags; Account_RegistrarStickiness; Account_RegistrarSearchMode; Account_RegEventPackageSubscription; Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 26 EnableWebAccessFromAllInterfaces; DefaultTerminalWindowHeight; ActiveAlarmTableMaxSize; SBCRemoveSIPSFromNonSecuredTransport 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. User's Manual...

  • Page 27: Introduction

    User's Manual 1. Introduction Introduction This User's Manual describes how to configure and manage your AudioCodes product (hereafter, referred to as device). This document is intended for the professional person responsible for installing, configuring and managing the device. Product Overview...

  • Page 28: Typographical Conventions

    Mediant 1000B Gateway & E-SBC  Optional Open Solution Network (OSN) server module for hosting value-added applications Note: For maximum call capacity figures, see ''Channel Capacity'' on page 1273. Typographical Conventions This document uses the following typographical conventions to convey information:...
  • Page 29 Multiple SRDs are required only for multi-tenant deployments, where it "splits" the device into multiple logical devices. For multiple SRDs, the SRD can be configured with a Sharing Policy. The Sharing Policy simply Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 30 Mediant 1000B Gateway & E-SBC Configuration Terms Description means whether the SRD's resources (SIP Interfaces, IP Groups, and Proxy Sets) can be used by other SRDs. For example, if all tenants route calls with the same SIP Trunking service provider, the SRD of the SIP Trunk would be configured as a Shared Sharing Policy.
  • Page 31 "serving" IP Group. Registration is for REGISTER messages, which are initiated by the device on behalf of the "serving" SIP entity. The associations between the configuration entities are summarized in the following figure: Figure 1-1: Association of Configuration Entities Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 32: Gateway Application

    Mediant 1000B Gateway & E-SBC 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. Depending on configuration and network topology, the call process may include additional stages or a different order of stages.
  • Page 33 Trunk Group, or calling or called telephone number prefix and suffix. The SIP entity can be denoted by an IP Group or other IP destinations such as IP address, FQDN, E.164 Telephone Number Mapping (ENUM service), and Lightweight Directory Access Protocol (LDAP). Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 34 Mediant 1000B Gateway & E-SBC Configuration Terms Description IP-to-Tel (Trunk Group) IP-to-Tel routing rules are used to route incoming IP calls to Trunk Routing Rules Groups. The specific channel pertaining to the Trunk Group to which the call is routed can also be configured.

  • Page 35: Getting Started With Initial Connectivity

    Part I Getting Started with Initial Connectivity...

  • Page 37: 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.2 Mediant 1000B Gateway & E-SBC...
  • Page 38 Mediant 1000B Gateway & E-SBC This page is intentionaly left blank. User's Manual Document #: LTRT-27055...

  • Page 39: 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 24 (255.255.255.0) Default Gateway 192.168.0.1 Ethernet Device vlan 1 Interface Name O+M+C Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 40 Mediant 1000B Gateway & E-SBC This page is intentionaly left blank. User's Manual Document #: LTRT-27055...

  • Page 41: Configuring Voip Lan Interface For Oamp

    Ethernet cable. Change the IP address and subnet mask of your computer to correspond with the default OAMP IP address and subnet mask of the device. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 42 Mediant 1000B Gateway & E-SBC Access the Web interface: On your computer, start a Web browser and in the URL address field, enter the default 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").

  • Page 43: Cli

    At the prompt, type the password again: Password: Admin Access the Network configuration mode: # configure network Access the IP Interfaces table: (config-network)# interface network-if 0 Configure the IP address: (network-if-0)# ip-address <IP address> Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 44 Mediant 1000B Gateway & 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> Apply your settings: (network-if-0)# activate Cable the device to your network. You can now access the device's management interface using this new OAMP IP address.

  • Page 45: Management Tools

    Part II Management Tools...

  • Page 47: Introduction

    Configuration ini file - see ''INI File-Based Management'' on page 101 Note: • Some configuration settings can only be done using a specific management tool. • For a list and description of all the configuration parameters, see ''Configuration Parameters Reference'' on page 1273. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 48 Mediant 1000B Gateway & E-SBC This page is intentionaly left blank. User's Manual Document #: LTRT-27055...

  • Page 49: Web-Based Management

    (Versions 5.02 or later) • Google Chrome (Version 50 or later)  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.2 Mediant 1000B Gateway & E-SBC...

  • Page 50: Accessing The Web Interface

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

  • Page 51: Areas Of The Gui

    6.1.3 Areas of the GUI The areas of the Web interface's GUI are shown in the figure below and described in the subsequent table. Figure 6-2: Main Areas of the Web Interface GUI Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 52 Mediant 1000B Gateway & E-SBC Table 6-1: Description of the Web GUI Areas Item # Description Company logo. Menu bar containing the menus. Toolbar providing frequently required command buttons.  Save: Saves configuration changes to the device's flash memory (without resetting the device).

  • Page 53: Accessing Configuration Pages From Navigation Tree

    The items of the Navigation tree depend on the menu-tab combination, selected from the menu bar and tab bar, respectively. The menus and their respective tabs are listed below:  Setup menu: • IP Network tab Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 54 Mediant 1000B Gateway & E-SBC • Signaling & Media tab • Administration tab  Monitor menu: Monitor tab  Troubleshoot menu: Troubleshoot tab When you open the Navigation tree, folders containing commonly required items are opened by default, allowing quick access to their pages.

  • Page 55: Configuring Stand-Alone Parameters

    Modify the parameter's value as desired. Click Apply; the changes are saved to the device's volatile memory (RAM). Save the changes to the device's non-volatile memory (flash): • If a device reset is not required: Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 56: Configuring Table Parameters

    Mediant 1000B Gateway & E-SBC On the toolbar, click Save; a confirmation message box appears: Figure 6-4: Save Configuration Confirmation Box Click Yes to confirm; the changes are save to flash memory. • If a device reset is required: On the toolbar, click Reset; the Maintenance Actions page opens.

  • Page 57: Adding Table Rows

    Configure the parameters of the row as desired. For information on configuring parameters that are assigned a value which is a row referenced from another table, see ''Assigning Rows from Other Tables'' on page 58. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 58: Assigning Rows From Other Tables

    Mediant 1000B Gateway & E-SBC Click Apply to add the row to the table or click Cancel to ignore your configuration. If the Save button is surrounded by a red border, you must save your settings to flash memory, otherwise they are discarded if the device resets (without a save to flash) or powers off.

  • Page 59: Modifying Table Rows

    (without a save to flash) or powers off. 6.1.6.4 Deleting Table Rows The following procedure describes how to delete a row from a table. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 60: Invalid Value Indications

    Mediant 1000B Gateway & E-SBC  To delete a table row: Select the row that you want to delete. Click the delete icon, located on the table's toolbar; a confirmation message box appears requesting you to confirm deletion, as shown in the example below: Click Yes, Delete;...
  • Page 61 Proxy Set #1 with indicating that it has a parameter that is referenced to a row of another table that has an invalid value: Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 62: Viewing Table Rows

    Mediant 1000B Gateway & E-SBC Figure 6-13: Invalid Icon Display in Drop-Down List of Parameter Referencing Other Rows Note: If you assign a non-mandatory parameter with a referenced row and then later delete the referenced row (in the table in which the row is configured), the parameter's value automatically changes to an empty field (i.e., no row assigned).

  • Page 63: Sorting Tables By Column

    Changing row position is supported only by certain tables (e.g., IP-to-IP Routing table).  To change the position of a row: Click the 'Index' column header so that the rows are sorted in ascending order (e.g., 0. 1, 2, and so on). Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 64: Searching Table Entries

    Mediant 1000B Gateway & E-SBC Select the row that you want to move. Do one of the following: • To move one index up (e.g., from Index 3 to 2): Click the up arrow; the row moves one index up in the table (e.g., to 2) and the row that originally occupied the index is moved one index down (e.g., to 3).
  • Page 65 Parameter's value • Brief description of parameter Figure 6-17: Search Result Window Click the link of the navigation path corresponding to the required found parameter to open the page on which the parameter appears. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 66: Getting Help

    Mediant 1000B Gateway & E-SBC 6.1.8 Getting Help The Web interface provides you with context-sensitive pop-up help of standalone parameters. When you hover your mouse over a parameter's field, a pop-up appears with a short description of the parameter, as shown in the following example: Figure 6-18: Viewing Context-Sensitive Help for a Parameter 6.1.9...

  • Page 67: Replacing The Corporate Logo

    User's Manual 6. Web-Based Management 6.2.1 Replacing the Corporate Logo You can replace the default corporate logo image (i.e., AudioCodes logo) that is displayed in the Web interface. The logo appears in the following Web areas:  Web Login screen: Figure 6-20: Corporate Logo on Web Login Screen ...

  • Page 68: Replacing The Corporate Logo With Text

    Mediant 1000B Gateway & E-SBC the device's IP address (e.g., http://10.1.229.17/AdminPage). Log in with your credentials; the Admin page appears. On the left pane, click Image Load to Device; the right pane displays the following: Figure 6-23: Customizing Web Logo Use the Browse button to select your logo file, and then click Send File;...

  • Page 69: Customizing The Product Name

    UserProductName = < name > Load the ini file using the Auxiliary Files page (see Loading Auxiliary Files on page 787). Reset the device with a save-to-flash for your settings to take effect. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 70: Customizing The Favicon

    6.2.3 Customizing the Favicon You can replace the default favicon (i.e., AudioCodes) with your own personalized favicon. Depending on the browser, the favicon is displayed in various areas of your browser, for example, in the URL address bar, on the page tab, and when bookmarked: Figure 6-26: Favicon Display in Browser ...

  • Page 71: Creating A Login Welcome Message

    Reset the device with a save-to-flash for your settings to take effect.  To remove the welcome message: Load an empty ini file, using the Auxiliary Files page. Reset the device with a save-to-flash for your settings to take effect. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 72: Configuring Additional Management Interfaces

    Mediant 1000B Gateway & E-SBC Configuring Additional Management Interfaces The Additional Management Interfaces table lets you configure up to 16 management interfaces, in addition to the OAMP management interface in the IP Interfaces table. Multiple management interfaces lets you access the device's management interfaces (e.g., Web interface and CLI) remotely through different IP addresses.
  • Page 73 [2] Use global definition = The type of management connection (HTTP and HTTPS, or HTTPS Only) depends on the configuration of the global parameter, HTTPSOnly (see Configuring Secured (HTTPS) Web on page 81). Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 74: Configuring Management User Accounts

    Mediant 1000B Gateway & E-SBC Configuring Management User Accounts The Local Users table lets you configure up to 10 management user accounts for the device's Web interface and CLI. You configure each user account with login credentials (username and password) and with a management user level which defines the level of read and write privileges.
  • Page 75 Click Apply, and then save your settings to flash memory. Table 6-7: Local Users Table Parameter Descriptions Parameter Description General Index Defines an index number for the new table row. [WebUsers_Index] Note: Each row must be configured with a unique index. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 76 Mediant 1000B Gateway & E-SBC Parameter Description Username Defines the Web user's username. user The valid value is a string of up to 40 alphanumeric characters, including the period ".", underscore "_", and hyphen "-" signs. [WebUsers_Username] Password Defines the Web user's password.
  • Page 77 (see the 'Session Timeout' parameter below). The valid value is 0 to 5. The default is 2. Note: Up to five users can be concurrently logged in to the Web interface. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 78: Displaying Login Information Upon Login

    Mediant 1000B Gateway & E-SBC Parameter Description Session Timeout Defines the duration (in minutes) of inactivity of a logged-in user in the Web interface, after which the user is automatically logged off the session-timeout Web session. In other words, the session expires when the user has...

  • Page 79: Viewing Logged-In User Information

    To configure Web user sessions and access security: Open the Web Settings page (Setup menu > Administration tab > Web & CLI folder > Web Settings). Under the Session group, configure the following parameters: Figure 6-33: Configuring Web User Sessions Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 80: Changing Login Password For Administrator And Monitor Users

    Mediant 1000B Gateway & E-SBC • 'Password Change Interval': Duration (in minutes) of the validity of the Web login passwords. When the duration expires, the user must change the password in order to log in again. • 'User Inactivity Timeout': If the user has not logged into the Web interface within this duration, the status of the user becomes inactive and the user can no longer access the Web interface.

  • Page 81: Configuring Secured (Https) Web

    Click Apply, and then reset the device with a save-to-flash for your settings to take effect. For more information on secure Web-based management including TLS certificates, see ''TLS for Remote Device Management'' on page 122. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 82: 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 83 When deleting all the IP addresses, make sure that you delete the IP address of the computer from which you are currently logged into the device, last; otherwise, access from your computer will be immediately denied. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 84 Mediant 1000B Gateway & E-SBC  To delete an IP address from the Access List: Select the Delete Row check box corresponding to the IP address that you want to delete. Click Delete Selected Addresses. User's Manual Document #: LTRT-27055...

  • Page 85: Cli-Based Management

    'Telnet Server TCP Port': Enter the port number of the embedded Telnet server. • 'Telnet Server Idle Timeout': Enter the duration of inactivity in the Telnet session after which the session automatically ends. Version 7.2 Mediant 1000B Gateway & E-SBC...

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

    Mediant 1000B Gateway & E-SBC Click Apply, and then reset the device with a save-to-flash for your settings to take effect. For a detailed description of the Telnet parameters, see ''Telnet Parameters'' on page 1005. 7.1.2 Enabling SSH with RSA Public Key for CLI Unless configured for TLS, Telnet is not secure as it requires passwords to be transmitted in clear text.
  • Page 87 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 Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 88: Configuring Maximum Telnet/Ssh Sessions

    Mediant 1000B Gateway & E-SBC occurs automatically and no password is required.  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:...

  • Page 89: 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.2 Mediant 1000B Gateway & E-SBC...

  • Page 90: Terminating A User's Cli Session

    Mediant 1000B Gateway & 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.  To terminate the CLI session of a specific CLI user: Establish a CLI session with the device.
  • Page 91 When this mode is configured, each time you change the height of the terminal window using your mouse (i.e., dragging one of the window's borders or corners), the number of displayed output command lines is changed accordingly. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 92 Mediant 1000B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-27055...

  • Page 93: Snmp-Based Management

    8. SNMP-Based Management SNMP-Based Management The device provides an embedded SNMP agent that lets you manage it using AudioCodes Element Management System (EMS) or a third-party SNMP manager. The SNMP agent supports standard and proprietary Management Information Base (MIBs). All supported MIB files are supplied to customers as part of the release.
  • Page 94 Mediant 1000B Gateway & E-SBC For detailed descriptions of the SNMP parameters, see ''SNMP Parameters'' on page 1006.  To configure SNMP community strings: Open the SNMP Community Settings page (Setup menu > Administration tab > SNMP folder > SNMP Community Settings).

  • Page 95: Configuring Snmp Trap Destinations With Ip Addresses

    SNMPv3 destination. By default, traps are sent unencrypted using SNMPv2. The following procedure describes how to configure SNMP trap destinations through the Web interface. You can also configure it through ini file (SNMPManager) or CLI (configure system > snmp trap-destination). Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 96 Mediant 1000B Gateway & E-SBC  To configure SNMP trap destinations: Open the SNMP Trap Destinations table (Setup menu > Administration tab > SNMP folder > SNMP Trap Destinations). Figure 8-2: SNMP Trap Destinations Table Configure the SNMP trap manager according to the table below.

  • Page 97: Configuring An Snmp Trap Destination With Fqdn

    (as long as the community string is correct). The following procedure describes how to configure SNMP Trusted Managers through the Web interface. You can also configure it through ini file (SNMPTrustedMgr_x) or CLI (configure system > snmp settings > trusted-managers). Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 98: Enabling Snmp Traps For Web Activity

    Mediant 1000B Gateway & E-SBC  To configure SNMP Trusted Managers: Open the SNMP Trusted Managers table (Setup menu > Administration tab > SNMP folder > SNMP Trusted Managers). Figure 8-3: SNMP Trusted Managers Table Configure an IP address (in dotted-decimal notation) for one or more SNMP Trusted Managers.
  • Page 99 [0] None (default)  [1] DES [SNMPUsers_PrivProtocol]  [2] 3DES  [3] AES-128  [4] AES-192  [5] AES-256 Authentication Key Authentication key. Keys can be entered in the form of a text password Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 100 Mediant 1000B Gateway & E-SBC Parameter Description auth-key or long hex string. Keys are always persisted as long hex strings and keys are localized. [SNMPUsers_AuthKey] Privacy Key Privacy key. Keys can be entered in the form of a text password or long hex string.

  • Page 101: Ini File-Based Management

    An exception is Index fields, which are mandatory. • The Format line must end with a semicolon ";".  Data line(s): Contain the actual values of the columns (parameters). The values are interpreted according to the Format line. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 102 Mediant 1000B Gateway & E-SBC • The first word of the Data line must be the table’s string name followed by the Index field. • Columns must be separated by a comma ",". • A Data line must end with a semicolon ";".

  • Page 103: General Ini File Formatting Rules

    (!), for example: !CpMediaRealm 1 = "ITSP", "Voice", "", 60210, 2, 6030, 0, "", ""; • To restore the device to default settings through the ini file, see ''Restoring Factory Defaults'' on page 863. Version 7.2 Mediant 1000B Gateway & 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 $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.2 Mediant 1000B Gateway & E-SBC...

  • Page 106: Ini Viewer And Editor Utility

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

  • Page 107: General System Settings

    Part III General System Settings...

  • Page 109: Configuring Ssl/Tls Certificates

    You can configure the device to check whether a peer's certificate has been revoked, using the OCSP. When OCSP is enabled, the device queries the OCSP server for revocation information whenever a Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 110 Mediant 1000B Gateway & E-SBC peer certificate is received (TLS client mode, or TLS server mode with mutual authentication). Note: • The device does not query OCSP for its own certificate. • Some PKIs do not support OCSP, but generate Certificate Revocation Lists (CRLs).
  • Page 111 Defines the supported cipher suite for the TLS server (in OpenSSL cipher list format). ciphers-server The default is AES:RC4. For valid values, visit the OpenSSL [TLSContexts_ServerCipherString] website at https://www.openssl.org/docs/man1.0.2/apps/ciphers.html. Cipher Client Defines the supported cipher suite for TLS clients. Version 7.2 Mediant 1000B Gateway & E-SBC...

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

    Mediant 1000B Gateway & E-SBC Parameter Description ciphers-client The default is DEFAULT. For possible values and additional details, visit the OpenSSL website at [TLSContexts_ClientCipherString] https://www.openssl.org/docs/man1.0.2/apps/ciphers.html. Strict Certificate Extension Validation Enables the validation of the extensions (keyUsage and extentedKeyUsage) of peer certificates. The validation...
  • Page 113 When the CA sends you a server certificate, save the certificate to a file (e.g., cert.txt). Make sure that the file is a plain-text file containing the"‘BEGIN CERTIFICATE" header, as shown in the example of a Base64-Encoded X.509 Certificate below: -----BEGIN CERTIFICATE----- MIIDkzCCAnugAwIBAgIEAgAAADANBgkqhkiG9w0BAQQFADA/MQswCQYDVQQGEw JGUjETMBEGA1UEChMKQ2VydGlwb3N0ZTEbMBkGA1UEAxMSQ2VydGlwb3N0ZSBT ZXJ2ZXVyMB4XDTk4MDYyNDA4MDAwMFoXDTE4MDYyNDA4MDAwMFowPzELMAkGA1 UEBhMCRlIxEzARBgNVBAoTCkNlcnRpcG9zdGUxGzAZBgNVBAMTEkNlcnRpcG9z Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 114: Viewing Certificate Information

    Mediant 1000B Gateway & E-SBC dGUgU2VydmV1cjCCASEwDQYJKoZIhvcNAQEBBQADggEOADCCAQkCggEAPqd4Mz iR4spWldGRx8bQrhZkonWnNm`+Yhb7+4Q67ecf1janH7GcN/SXsfx7jJpreWUL f7v7Cvpr4R7qIJcmdHIntmf7JPM5n6cDBv17uSW63er7NkVnMFHwK1QaGFLMyb FkzaeGrvFm4k3lRefiXDmuOe+FhJgHYezYHf44LvPRPwhSrzi9+Aq3o8pWDguJ uZDIUP1F1jMa+LPwvREXfFcUW+w== -----END CERTIFICATE----- Scroll down to the Upload certificates files from your computer group, click the Browse button corresponding to the 'Send Device Certificate...' field, navigate to the cert.txt file, and then click Load File.
  • Page 115 User's Manual 10. Configuring SSL/TLS Certificates Select a TLS Context row, and then click the Certificate Information link located below the table; the Certificate Information page appears: Figure 10-3: Viewing Certificate Information Version 7.2 Mediant 1000B Gateway & E-SBC...

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

    Mediant 1000B Gateway & E-SBC 10.4 Assigning Externally Created Private Keys to TLS Contexts The following procedure describes how to assign an externally created private key to a TLS Context.  To assign an externally created private key to a TLS Context: Obtain a private key in either textual PEM (PKCS #7) or PFX (PKCS #12) format (typically provided by your security administrator).

  • Page 117: Generating Private Keys For Tls Contexts

    If you don't want to encrypt the file, make the field blank. The default passphrase is "audc". The passphrase can be up to 32 characters. Click Generate Private-Key; a message appears requesting you to confirm key generation. Version 7.2 Mediant 1000B Gateway & E-SBC...

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

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

  • Page 119: Importing Certificates Into Trusted Certificate Store

    CA certificate. The CA vouches for the identity of the child certificate by signing it. A client certificate is considered trusted if one of the CA certificates up the certificate chain is found in the server certificate directory. For the device to trust a whole Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 120 Mediant 1000B Gateway & E-SBC chain of certificates per TLS Context, you need to add them to the device's Trusted Certificates Store, as described below. Figure 10-10: Certificate Chain Hierarchy You can also import multiple TLS root certificates in bulk from a single file. Each certificate in the file must be Base64 encoded (PEM).
  • Page 121 Save certificates to a folder on your PC: Select the required certificate, click Export, and then in the Export Certificate dialog box, browse to the folder on your PC where you want to save the file and click Export. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 122: Configuring Mutual Tls Authentication

    Mediant 1000B Gateway & E-SBC 10.8 Configuring Mutual TLS Authentication This section describes how to configure mutual (two-way) TLS authentication. 10.8.1 TLS for SIP Clients When Secure SIP (SIPS) is implemented using TLS, it is sometimes required to use two- way (mutual) authentication between the device and a SIP user agent (client).

  • Page 123: Configuring Tls Server Certificate Expiry Check

    Open the TLS Contexts table (see ''Configuring TLS Certificate Contexts'' on page 109). Select the required TLS Context index row, and then click the Change Certificate link located below the table; the Chnage Certificates page appears. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 124 Mediant 1000B Gateway & E-SBC Scroll down the page to the TLS Expiry Settings group: Figure 10-12: TLS Expiry Settings Group In the 'TLS Expiry Check Start' field, enter the number of days before the installed TLS server certificate is to expire when the device sends an SNMP trap event to notify of this.

  • Page 125: Date And Time

    In the 'NTP Authentication Key Identifier' field, configure the NTP authentication key identifier. • In the 'NTP Authentication Secret Key' field, configure the secret authentication key shared between the device and the NTP server. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 126: Configuring Date And Time Manually

    Mediant 1000B Gateway & E-SBC 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 under the Time Zone group. Note: If the device does not receive a response from the NTP server, it polls the NTP server for 10 minutes.

  • Page 127: Configuring The Time Zone

    Open the Time & Date page (Setup menu > Administration tab > Time & Date), and then scroll down to the Time Zone group: Figure 11-4: Configuring Daylight Savings From the 'Day Light Saving Time' (DayLightSavingTimeEnable) drop-down list, select Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 128 Mediant 1000B Gateway & E-SBC Enable. From the 'DST Mode' drop-down list, select the range type for configuring the start and end dates for DST: • Day of year: The range is configured by exact date (day number of month), for example, from March 30 to October 30.

  • Page 129: General Voip Configuration

    Part IV General VoIP Configuration...

  • Page 131: Network

    The areas of the Network view is shown in the example below and described in the subsequent table. Note: The below figure is used only as an example; your device may show different Ethernet Groups and Ethernet ports. Figure 12-1: Network View (Example) Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 132 Mediant 1000B Gateway & E-SBC Table 12-1: Description of Network View Item # Description Configures and displays IP Interfaces. The IP Interface appears as an icon, displaying the application type ("OCM" for OAMP, "C" for Control, and "M" for Media), row index number, name, and IP address, as shown in the...
  • Page 133 The connectivity status of the port is indicated by the color of the icon:  Green: Network connectivity exists through port (port connected to network).  Red: No network connectivity through port (e.g., cable disconnected). Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 134: Configuring Physical Ethernet Ports

    Mediant 1000B Gateway & E-SBC Item # Description To refresh the status indication, click the Refresh Network View button (described below in Item #5). To open the Physical Ports table, click any port icon, and then from the drop-down menu, choose View List.
  • Page 135 Open the Physical Ports table (Setup menu > IP Network tab > Core Entities folder > Physical Ports). Select a port that you want to configure, and then clicking Edit; the following dialog box appears: Configure the port according to the parameters described in the table below. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 136: Configuring Ethernet Port Groups

    Mediant 1000B Gateway & E-SBC Click Apply, and then save your settings to flash memory. Table 12-2: Physical Ports Table Parameter Descriptions Parameter Description General Index (Read-only) Displays the index number for the table row. Name (Read-only) Displays the Ethernet port number. See the figure...
  • Page 137 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 Groups 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 134.
  • Page 138 Mediant 1000B Gateway & E-SBC Configure the Ethernet Group according to the parameters described in the table below. Click Apply, and then save your settings to flash memory. Table 12-3: Ethernet Groups Table Parameter Descriptions Parameter Description Index (Read-only) Displays the index number for the table row.

  • Page 139: Configuring Underlying Ethernet Devices

    > network-dev).  To configure an Ethernet Device: Open the Ethernet Devices table (Setup menu > IP Network tab > Core Entities folder > Ethernet Devices). Click New; the following dialog box appears: Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 140 Mediant 1000B Gateway & E-SBC Configure an Ethernet Device according to the parameters described in the table below. Click Apply. Table 12-4: Ethernet Devices Table Parameter Descriptions Parameter Description Index Defines an index number for the new table row. [DeviceTable_Index] Note: Each row must be configured with a unique index.
  • Page 141 Group. For example, if VLAN 1 is configured with the highest MTU (100 bytes) out of all your VLANs, you can configure an untagged VLAN with an MTU value of either 100 bytes or greater. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 142: Configuring Ip Network Interfaces

    Mediant 1000B Gateway & E-SBC 12.5 Configuring IP Network Interfaces You can configure a single VoIP network interface for all applications, including OAMP (management traffic), call control (SIP signaling messages), and media (RTP traffic), or you can configure multiple logical, IP network interfaces for these applications. You may need to logically separated network segments for these applications for administration and security.
  • Page 143 IP Interfaces). Click New; the following dialog box appears: Figure 12-3: IP Interfaces Table - Dialog Box Configure the IP network interface according to the parameters described in the table below. Click Apply. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 144 Mediant 1000B Gateway & E-SBC Note: • If you modify the OAMP interface's address, after clicking Apply you will lose connectivity with the device and need to access the device with the new address. • If you edit or delete an IP interface, current calls using the interface are immediately terminated.
  • Page 145 Defines the secondary DNS server's IP address (in dotted-decimal notation), which is used for translating domain names into IP secondary-dns addresses for the interface. [InterfaceTable_SecondaryDN By default, no IP address is defined. SServerIPAddress] Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 146: Assigning Ntp Services To Application Types

    Mediant 1000B Gateway & E-SBC 12.5.1 Assigning NTP Services to Application Types You can associate the Network Time Protocol (NTP) application with the OAMP or Control application type. This is done using the EnableNTPasOAM ini file parameter. For more information on NTP, see ''Configuring Automatic Date and Time using SNTP'' on page 125.

  • Page 147: One Voip Interface For All Applications

    211.211.85.14 211.211.85.1 myMediaIF Manual Static Routes table: A routing rule is required to allow remote management from a host in 176.85.49.0 / 24: Table 12-9: Example Static Routes Table Destination Prefix Length Gateway Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 148: Voip Interfaces For Combined Application Types

    Mediant 1000B Gateway & E-SBC Destination Prefix Length Gateway 176.85.49.0 192.168.11.1 All other parameters are set to their respective default values. The NTP application remains with its default application types. 12.5.3.3 VoIP Interfaces for Combined Application Types This example describes the configuration of multiple interfaces for the following applications: ...

  • Page 149: Voip Interfaces With Multiple Default Gateways

    You can also configure it through ini file (StaticRouteTable) or CLI (configure network > static).  To configure static IP routes: Open the Static Routes table (Setup menu > IP Network tab > Core Entities folder > Static Routes). Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 150 Mediant 1000B Gateway & E-SBC Click New; the following dialog box appears: Configure a static route according to the parameters described in the table below. The address of the host/network you want to reach is determined by an AND operation that is applied to the fields 'Destination' and 'Prefix Length'.

  • Page 151: Configuration Example Of Static Ip Routes

    IP Interfaces table. This is done by configuring the 'Ethernet Output Name' field in the Static Routes table to the same value as configured in the 'Ethernet Device' field in the IP Interfaces table. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 152: Troubleshooting The Static Routes Table

    Mediant 1000B Gateway & E-SBC  The static route's Gateway address in the Static Routes table is in the same subnet as the IP address of the IP network interface in the IP Interfaces table. Figure 12-4: Example of using a Static Route 12.6.2 Troubleshooting the Static Routes Table...

  • 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 IP Interfaces table. Note: The priority list above is applicable only to Gateway calls. Version 7.2 Mediant 1000B Gateway & E-SBC...

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

    Mediant 1000B Gateway & E-SBC The figure below illustrates the NAT problem faced by SIP networks when the device is located behind a NAT: Figure 12-5: Device behind NAT and NAT Issues 12.7.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: Configuring Nat Translation Per Ip Interface

    Interfaces table) to the rule. Outgoing packets sent from the src-interface-name specified network interface are NAT'ed. [NATTranslation_SrcIPInterfaceName] By default, no value is defined. To configure IP network interfaces, see ''Configuring IP Network Interfaces'' on page 142. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 156: Remote Ua Behind Nat

    Mediant 1000B Gateway & E-SBC Parameter Description Source Start Port Defines the optional starting port range (0-65535) of the IP interface, used as matching criteria for the NAT rule. If not src-start-port configured, the match is done on the entire port range. Only...

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

    IP address:port (i.e., allocated by the NAT server). Therefore, to ensure that the media reaches the UA, the device must send it to the public address. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 158 Mediant 1000B Gateway & E-SBC The device identifies whether the UA is located behind NAT by comparing the source IP address of the first received media packet with the IP address and UDP port of the first received SIP message (INVITE) when the SIP session was started. This is done for each media type--RTP, RTCP and T.38--and therefore, they can have different destination IP...

  • Page 159: Configuring Quality Of Service

    Media Premium: RTP packets sent to the LAN  Control Premium: Control protocol (SIP) packets sent to the LAN  Gold: HTTP streaming packets sent to the LAN  Bronze: OAMP packets sent to the LAN Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 160 Mediant 1000B Gateway & E-SBC The mapping of an application to its CoS and traffic type is shown in the table below: Table 12-16: Traffic/Network Types and Priority Application Traffic / Network Types Class-of-Service (Priority) Debugging interface Management Bronze Telnet...

  • Page 161: Configuring Diffserv-To-Vlan Priority Mapping

    Web interface. You can also configure it through ini file (DiffServToVlanPriority) or CLI (configure network > qos vlan-mapping).  To configure DiffServ-to-VLAN priority mapping: Open the QoS Mapping table (Setup menu > IP Network tab > Quality folder > QoS Mapping). Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 162: Configuring Icmp Messages

    Mediant 1000B Gateway & E-SBC Click New; the following dialog box appears: Figure 12-12: QoS Mapping Table - Add Dialog Box Configure a DiffServ-to-VLAN priority mapping rule according to the parameters described in the table below. Click Apply, and then save your settings to flash memory.

  • Page 163: Dns

    You can also configure it through ini file (DNS2IP) or CLI (configure network > dns dns-to-ip).  To configure the device's DNS table: Open the Internal DNS table (Setup menu > IP Network tab > DNS folder > Internal DNS). Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 164: Configuring The Internal Srv Table

    Mediant 1000B Gateway & E-SBC Click New; the following dialog box appears: Figure 12-14: Internal DNS Table - Add Dialog Box Configure a DNS rule according to the parameters described in the table below. Click Apply. Table 12-19: Internal DNS Table Parameter Description...
  • Page 165 The valid value is a string of up to 31 characters. By default, no value is defined. [Srv2Ip_InternalDomain] Transport Type Defines the transport type.  transport-type [0] UDP (default)  [1] TCP [Srv2Ip_TransportType]  [2] TLS Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 166 Mediant 1000B Gateway & E-SBC Parameter Description 1st/2nd/3rd Entry DNS Name (1-3) Defines the first, second or third DNS A-Record to which the host name is translated. dns-name-1|2|3 By default, no value is defined. [Srv2Ip_Dns1/2/3] Priority (1-3) Defines the priority of the target host. A lower value means that it is more preferred.

  • Page 167: Open Solution Network (Osn) Server

    VLAN configured in the Ethernet Devices table (see ''Configuring Underlying Ethernet Devices'' on page 139), which is assigned to a Media and/or Control application in the IP Interfaces table. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 168: Disabling Internal Switch Port For Osn

    Mediant 1000B Gateway & E-SBC 12.11.2 Disabling Internal Switch Port for OSN You can enable or disable the Ethernet port of the device's internal switch, which interfaces with the OSN server. If the port is not blocked, you can optionally access the OSN server through any Ethernet port on the device's front panel (instead of through the OSN module's Ethernet ports located on the rear panel).

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

    12. Network 12.12 Robust Receipt of Media Streams by Media Latching The Robust Media mechanism (or media latching) is an AudioCodes proprietary mechanism to filter out unwanted media (RTP, RTCP, SRTP, SRTCP, and T.38) streams that are sent to the same port number of the device. Media ports may receive additional multiple unwanted media streams (from multiple sources of traffic) as result of traces of previous calls, call control errors, or deliberate malicious attacks (e.g., Denial of Service).
  • Page 170 Mediant 1000B Gateway & E-SBC This page is intentionaly left blank. User's Manual Document #: LTRT-27055...

  • Page 171: Security

    To block all traffic, use the following firewall rule: √ Source IP: 0.0.0.0 √ Prefix Length: 0 (i.e., rule matches all IP addresses) √ Start Port - End Port: 0-65535 √ Protocol: Any √ Action Upon Match: Block Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 172 Mediant 1000B Gateway & E-SBC The following procedure describes how to configure firewall rules through the Web interface. You can also configure it through ini file (AccessList) or CLI (configure network > access-list).  To configure a firewall rule: Open the Firewall table (Setup menu > IP Network tab > Security folder> Firewall).
  • Page 173 Interface' field. The list displays interface names as defined in [AccessList_Interface_x] the IP Interfaces table in ''Configuring IP Network Interfaces'' on page 142. Action Action Upon Match Defines the firewall action to be performed upon rule match. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 174 Mediant 1000B Gateway & E-SBC Parameter Description  allow-type "Allow" = (Default) Permits the packets.  "Block" = Rejects the packets [AccessList_Allow_Type] 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 175: Configuring General Security Settings

    Assign the TLS Context to a Proxy Set or SIP Interface (see ''Configuring Proxy Sets'' on page 367 and ''Configuring SIP Interfaces'' on page 345, respectively). Configure a SIP Interface with a TLS port number. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 176: Intrusion Detection System

    Mediant 1000B Gateway & E-SBC Configure various SIPS parameters in the Security Settings page (Setup menu > IP Network tab > Security folder > Security Settings). Figure 13-2: Configuring TLS For a description of the TLS parameters, see ''TLS Parameters'' on page 1039.

  • Page 177: Enabling Ids

    The device provides the following pre-configured IDS Policies that can be used in your deployment (if they meet your requirements):  "DEFAULT_FEU": IDS Policy for far-end users in the WAN Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 178 Mediant 1000B Gateway & E-SBC  "DEFAULT_PROXY": IDS Policy for proxy server  "DEFAULT_GLOBAL": IDS Policy with global thresholds Note: The default IDS Policies are read-only and cannot be modified. The following procedure describes how to configure IDS Policies through the Web interface.
  • Page 179 Defines an index number for the new table record. rule-id [IDSRule_RuleID] Reason Defines the type of intrusion attack (malicious event).  reason [0] Any = All events listed below are considered as attacks and are counted together. [IDSRule_Reason] Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 180 Mediant 1000B Gateway & E-SBC Parameter Description  [1] Connection abuse = (Default) TLS authentication failure.  [2] Malformed message =  Message exceeds a user-defined maximum message length (50K)  Any SIP parser error  Message Policy match (see ''Configuring SIP Message Policy Rules'') ...

  • Page 181: Assigning Ids Policies

    You can also configure it through ini file (IDSMatch) or CLI (configure voip > ids match).  To configure an IDS Policy-Matching rule: Open the IDS Matches table (Setup menu > Signaling & Media tab > Intrusion Detection folder > IDS Matches). Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 182 Mediant 1000B Gateway & E-SBC Click New; the following dialog box appears: Figure 13-7: IDS Matches Table - Add Dialog Box The figure above shows a configuration example where the IDS Policy "SIP Trunk" is applied to SIP Interfaces 1 and 2, and to all source IP addresses outside of subnet 10.1.0.0/16 and IP address 10.2.2.2.

  • Page 183: Viewing Ids Alarms

    Policies'' on page 177). For example, if you set IDSAlarmClearPeriod to 20 sec and 'Threshold Window' to 15 sec, the IDSAlarmClearPeriod parameter is ignored and the alarm is cleared only after 30 seconds (2 x 15 sec). Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 184 Mediant 1000B Gateway & E-SBC The figure below displays an example of IDS alarms in the Active Alarms table (''Viewing Active Alarms'' on page 877). In this example, a Minor threshold alarm is cleared and replaced by a Major threshold alarm: Figure 13-8: IDS Alarms in Active Alarms Table ...
  • Page 185  establish-malicious- signature-db-reject   Requests and responses without a matching flow-no-match-tu Abnormal Flow transaction user (except ACK requests)  flow-no-match-  Requests and responses without a matching transaction transaction (except ACK requests) Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 186 Mediant 1000B Gateway & E-SBC This page is intentionaly left blank. User's Manual Document #: LTRT-27055...

  • Page 187: Media

    Non Linear Processor (NLP) is used, as well as a double-talk (two people speak at the same time) detector that prevents false adaptation during near-end speech. The following procedure describes how to configure echo cancellation through the Web interface: Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 188: Fax And Modem Capabilities

    Mediant 1000B Gateway & E-SBC  To configure echo cancellation: Configure line echo cancellation: Open the Voice Settings page (Setup menu > Signaling & Media tab > Media folder > Voice Settings). Figure 14-2: Enabling Echo Cancellation From the 'Echo Canceller' drop-down list (EnableEchoCanceller), select Enable.

  • Page 189: Fax/Modem Operating Modes

    NSE Cisco’s Pass-through bypass mode for fax and modem (see ''Fax / Modem NSE Mode'' on page 195)  Transparent with events: passing the fax / modem signal in the current voice coder Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 190: Fax Relay Mode

    Mediant 1000B Gateway & E-SBC with adaptations (see ''Fax / Modem Transparent with Events Mode'' on page 196)  Transparent: passing the fax / modem signal in the current voice coder (see ''Fax / Modem Transparent Mode'' on page 196) ...
  • Page 191 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 192: Fax / Modem Transport Mode

    0-15  AudioCodes Call Party with non-AudioCodes Party: The device uses the standard T.38-over-RTP method, which encapsulates the T.38 payload only, without its headers (i.e., includes only fax data) in the sent RTP packet (RFC 4612). The T.38-over-RTP method also depends on call initiator: ...

  • Page 193: Fax Fallback

    'Fax/Modem Bypass Coder Type' parameter (FaxModemBypassCoderType). The channel is also automatically reconfigured with the following fax / modem adaptations:  Disables silence suppression Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 194 Mediant 1000B Gateway & E-SBC  Enables echo cancellation for fax  Disables echo cancellation for modem  Performs certain jitter buffering optimizations The network packets generated and received during the bypass period are regular voice RTP packets (per the selected bypass coder), but with a different RTP payload type according to the following parameters: ...

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

    Mediant 1000B Gateway & E-SBC 14.2.2.6 Fax / Modem Transparent with Events Mode In this mode, fax and modem signals are transferred using the current voice coder with the following automatic adaptations:  Echo Canceller = on (or off for modems) ...

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

    'CNG Detector Mode' parameter (CNGDetectorMode) to Disable. 14.2.3.1 Bypass Mechanism for V.34 Fax Transmission In this proprietary scenario, the device uses bypass (or NSE) mode to transmit V.34 faxes, enabling the full utilization of its speed. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 198: Relay Mode For T.30 And V.34 Faxes

    Mediant 1000B Gateway & E-SBC  To use bypass mode for T.30 and V.34 faxes: On the Fax/Modem/CID Settings page, do the following: Set the 'Fax Transport Mode' parameter to Bypass (FaxTransportMode = 2). Set the 'V.22 Modem Transport Type' parameter to Enable Bypass (V22ModemTransportType = 2).

  • Page 199: Configuring Rtp/Rtcp Settings

    The default settings of 10 msec Minimum delay and 10 Optimization Factor should provide a good compromise between delay and error rate. The jitter buffer ‘holds’ incoming packets for 10 msec before making them available for decoding into voice. The coder polls frames Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 200: Comfort Noise Generation

    Mediant 1000B Gateway & E-SBC from the buffer at regular intervals in order to produce continuous speech. As long as delays in the network do not change (jitter) by more than 10 msec from one packet to the next, there is always a sample in the buffer for the coder to use. If there is more than 10 msec of delay at any time during the call, the packet arrives too late.

  • Page 201: Configuring Dtmf Transport Types

    Type' parameter is automatically set to Mute DTMF).  Using NOTIFY messages according to IETF Internet-Draft draft-mahy-sipping- signaled-digits-01: DTMF digits are sent to the remote side using NOTIFY messages. To enable the mode: Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 202: Configuring Rfc 2833 Payload

    Mediant 1000B Gateway & E-SBC Set the 'Declare RFC 2833 in SDP' parameter to No (RxDTMFOption = 0). Set the 'First Tx DTMF Option' parameter to NOTIFY (FirstTxDTMFOption = 2). Note: DTMF digits are removed from the audio stream (and the 'DTMF Transport Type' parameter is automatically set to Mute DTMF).

  • Page 203: Configuring Rtp Base Udp Port

    The following procedure describes how to configure the RTP base UDP port through the Web interface.  To configure the RTP base UDP port: Open the RTP/RTCP Settings page (Setup menu > Signaling & Media tab > Media folder > RTP/RTCP Settings). Version 7.2 Mediant 1000B Gateway & E-SBC...

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

    Mediant 1000B Gateway & E-SBC In the 'RTP Base UDP Port' field, configure the lower boundary of the UDP port range. Figure 14-11: Configuring RTP Base UDP Port Click Apply, and then reset the device with a save-to-flash for your settings to take effect.
  • Page 205 Set the IsFaxUsed parameter to 0 and the 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 Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 206: Sit Event Detection

    Mediant 1000B Gateway & 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 207: Detecting Answering Machine Beeps

    Upon detection of the answering machine, the device sends the following SIP INFO message to the application server: INFO sip:sipp@172.22.2.9:5060 SIP/2.0 Via: SIP/2.0/UDP 172.22.168.249;branch=z9hG4bKac1566945480 Max-Forwards: 70 From: sut <sip:3000@172.22.168.249:5060>;tag=1c1505895240 To: sipp <sip:sipp@172.22.2.9:5060>;tag=1 Call-ID: 1-29758@172.22.2.9 CSeq: 1 INFO Contact: <sip:56700@172.22.168.249> Supported: em,timer,replaces,path,resource-priority Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 208 Mediant 1000B Gateway & E-SBC Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,I NFO,SUBSCRIBE,UPDATE User-Agent: Audiocodes-Sip-Gateway/v.7.20A.000.038 Content-Type: application/x-detect Content-Length: 30 Type= AMD SubType= AUTOMATA Upon detection of the start of voice (i.e., the greeting message of the answering machine), the device sends the following INFO message to the application server: INFO sip:sipp@172.22.2.9:5060 SIP/2.0...

  • Page 209: Answering Machine Detection (Amd)

    The device's default AMD feature is based on voice detection for North American English (see note below). It uses AudioCodes' sophisticated speech detection algorithms which are based on hundreds of real-life recordings of answered calls by live voice and answering Version 7.2...
  • Page 210 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 211 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 Machine) Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 212: Configuring Amd

    Mediant 1000B Gateway & E-SBC Performance AMD Detection Sensitivity Success Rate for Live Calls Success Rate for Answering Machine 15 (Best for Live Calls) 14.5.1 Configuring AMD You can configure AMD for all calls using global AMD parameters or for specific calls using IP Profiles.
  • Page 213 User's Manual 14. Media Click Apply, and then reset the device with a save-to-flash for your settings to take effect. For a complete list of AMD-related parameters, see ''IP Media Parameters'' on page 1252. Version 7.2 Mediant 1000B Gateway & E-SBC...

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

    Mediant 1000B Gateway & E-SBC 14.5.2 Enabling IP-to-Tel Call Disconnection upon Detection of Answering Machine The device can disconnect an IP-to-Tel call upon detection of an answering machine on the Tel side. Once detected, the device disconnects the call after the receipt of an ISDN Connect from the Tel side and then sends a SIP BYE message to the IP side to disconnect the call.

  • Page 215: Configuring Ground- Or Loop-Start Signaling Per Analog Port

    Configuring Ground- or Loop-Start Signaling per Analog Port The Port Ground Start table lets you configure the signaling control method per analog (FXS or FXO) port. You can set the port to ground-start or loop-start signaling. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 216: Configuring Dsp Templates

    Mediant 1000B Gateway & E-SBC Note: • For ground-start signaling, make sure that the device's chassis houses the FXO G module (and not the regular FXO module). • To support FXO ground-start signaling, set the following additional parameters: √ EnableCurrentDisconnect to 1 √...

  • Page 217: Dsp Channel Resources For Transcoding

    MPM and PRI modules. For example, to achieve 140 channels (with IP media features), you need to use two MPM modules (installed in slots #4 and #5) and one PRI module providing two PRI spans (installed in Slot #1).  Software Configuration: Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 218: Configuring Media (Srtp) Security

    Mediant 1000B Gateway & E-SBC • Set the MediaChannels parameter to the maximum number of required IP media channels, regardless of the module from where the channels are obtained. Note: Setting the MediaChannels parameter to a value that is greater than the available DSP resources that is provided by the MPM module(s) can result in the "stealing"...
  • Page 219 For a detailed description of the SRTP parameters, see ''Configuring IP Profiles'' on page 423 and ''SRTP Parameters'' on page 1038. • When SRTP is used, the channel capacity may be reduced. The procedure below describes how to configure SRTP through the Web interface. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 220 Mediant 1000B Gateway & E-SBC  To enable and configure SRTP: Open the Media Security page (Setup menu > Signaling & Media tab > Media folder > Media Security). Figure 14-17: Configuring Media Security From the 'Media Security' drop-down list (EnableMediaSecurity), select Enable to enable SRTP.

  • Page 221: Services

    Option 51 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.2 Mediant 1000B Gateway & E-SBC...
  • Page 222 Mediant 1000B Gateway & 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 223 Note: The IP address must belong to the same subnet as the associated interface’s IP address. 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 end-address Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 224 Mediant 1000B Gateway & E-SBC Parameter Description [DhcpServer_EndIPAddress] to allocate addresses. The default value is 192.168.0.149. Note: The IP address must belong to the same subnet as the associated interface’s IP address and must be "greater or equal" to the starting IP address defined in 'Start IP Address'.
  • Page 225 SIP requests. The value is sent in DHCP [DhcpServer_SipServer] Option 120 (SIP Server). After defining the parameter, use the 'SIP server type' parameter (see below) to define the type of Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 226: 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 227: Configuring Additional Dhcp Options

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

  • Page 229: Configuring Static Ip Addresses For Dhcp Clients

    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 link located below the table; the DHCP Static IP table opens. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 230: Viewing And Deleting Dhcp Clients

    Mediant 1000B Gateway & E-SBC Click New; the following dialog box appears: Figure 15-4: DHCP Static IP Table - Add Dialog Box Configure a static IP address for a specific DHCP client according to the parameters described in the table below.

  • Page 231: Radius-Based Services

    (CDR) to a RADIUS Accounting server (for third-party billing purposes). 15.2.1 Enabling RADIUS Services Before you can implement any RADIUS services, you must enable the RADIUS feature, as described in the procedure below. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 232: Configuring Radius Servers

    Mediant 1000B Gateway & E-SBC  To enable RADIUS: Open the Authentication Server page (Setup menu > Administration tab > Web & CLI folder > Authentication Server). Figure 15-6: Enabling RADIUS Under the RADIUS group, from the 'Enable RADIUS Access Control' drop-down list, select Enable.
  • Page 233 > RADIUS Servers). Click New; the following dialog box appears: Figure 15-7: RADIUS Servers Table - Add Dialog Box Configure a RADIUS server according to the parameters described in the table below. Click Apply. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 234: Configuring Interface For Radius Communication

    Mediant 1000B Gateway & E-SBC Table 15-6: RADIUS Servers Table Parameter Descriptions Parameter Description Index Defines an index number for the new table row. [RadiusServers_Index] Note: Each row must be configured with a unique index. IP Address Defines the IP address of the RADIUS server (in dotted-decimal notation).

  • Page 235: Configuring The Radius Vendor Id

    Web and Telnet (CLI) servers. Thus, RADIUS also prevents unauthorized access to your device. When RADIUS authentication is not used, the user's login username and password are locally authenticated by the device using the Local Users table (see ''Configuring Version 7.2 Mediant 1000B Gateway & E-SBC...

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

    Mediant 1000B Gateway & E-SBC Management User Accounts'' on page 74). However, you can configure the device to use the Local Users table as a fallback mechanism if the RADIUS server does not respond. When RADIUS authentication is used, the RADIUS server stores the user accounts - usernames, passwords, and access levels (authorization).

  • Page 237: Configuring Radius-Based User Authentication

    Open the Authentication Server page (Setup menu > Administration tab > Web & CLI folder > Authentication Server). From the 'Use RADIUS for Web/Telnet Login' drop-down list, select Enable to enable RADIUS authentication for Web and Telnet login: Figure 15-11: Enabling RADIUS-based Login Authentication Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 238 Mediant 1000B Gateway & E-SBC When implementing Web user access levels, do one of the following: • If the RADIUS server response includes the access level attribute: In the 'RADIUS VSA Access Level Attribute' field, enter the code that indicates the access level attribute in the VSA section of the received RADIUS packet.

  • Page 239: Securing Radius Communication

    For the device to run a search, the path to the directory’s subtree, known as the distinguished name (DN), where the search is to be done must be configured (see ''Configuring LDAP DNs (Base Paths) per LDAP Server'' on page 247). The search Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 240 Mediant 1000B Gateway & E-SBC key (filter), which defines the exact DN to search and one or more attributes whose values must be returned to the device must also be configured. For more information on configuring these attributes and search filters, see ''AD-based Routing for Microsoft Skype for Business'' on page 260.

  • Page 241: Enabling The Ldap Service

    Figure 15-17: Enabling LDAP-based Login Authentication Under the LDAP group, from the 'Use LDAP for Web/Telnet Login' drop-down list, select Enable. Click Apply, and then reset the device with a save-to-flash for your settings to take effect. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 242: Configuring Ldap Server Groups

    Mediant 1000B Gateway & E-SBC 15.3.3 Configuring LDAP Server Groups The LDAP Server Groups table lets you configure up to 41 LDAP Server Groups. An LDAP Server Group is a logical configuration entity that contains up to two LDAP servers. LDAP servers are assigned to LDAP Server Groups in the LDAP Servers table (see ''Configuring LDAP Servers'' on page 244).
  • Page 243 Defines the duration (in hours) after which the LDAP entry is deleted Timeout from the device's LDAP cache. The valid range is 0 to 596. The default is 0 (i.e., the entry is never cache-entry-removal- timeout deleted). [LdapServerGroups_CacheEn tryRemovalTimeout] Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 244: Configuring Ldap Servers

    Mediant 1000B Gateway & E-SBC 15.3.4 Configuring LDAP Servers The LDAP Servers table lets you configure up to 82 LDAP servers. The table defines the address and connectivity settings of the LDAP server. The LDAP server can be configured for SIP-related queries (e.g., routing and manipulation) or LDAP-based management user login authentication and authorization (username-password).
  • Page 245 Note: If the response time expires, you can configure the device to use the Local Users table for authenticating the user. For more information, see ''Configuring Local Database for Management User Authentication'' on page 255. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 246 Mediant 1000B Gateway & E-SBC Parameter Description LDAP Server Domain Name Defines the domain name (FQDN) of the LDAP server. The device tries to connect to the LDAP server according to the IP domain-name address listed in the received DNS query. If there is no...

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

    The following procedure describes how to configure DNs per LDAP server through the Web interface. You can also configure it through ini file (LdapServersSearchDNs) or CLI (configure system > ldap ldap-servers-search-dns). Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 248: Configuring The Ldap Search Filter Attribute

    Mediant 1000B Gateway & E-SBC  To configure an LDAP base path per LDAP server: Open the LDAP Servers table (Setup menu > IP Network tab > RADIUS & LDAP folder > LDAP Servers). In the table, select the row of the LDAP server for which you want to configure DN base paths, and then click the LDAP Servers Search Based DNs link located below the table;...

  • Page 249: Configuring Access Level Per Management Groups Attributes

    The group of which the user is a member is not configured on the device (as described in this section). √ The device is not configured to query the LDAP server for a management attribute (see ''Configuring LDAP Servers'' on page 244). Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 250 Mediant 1000B Gateway & E-SBC Group objects represent groups in the LDAP server of which the user is a member. The access level represents the user account's permissions and rights in the device's management interface (e.g., Web and CLI). The access level can either be Monitor, Administrator, or Security Administrator.

  • Page 251: Configuring The Device's Ldap Cache

    Improves routing decision performance by using local cache for subsequent LDAP queries  Reduces number of queries performed on an LDAP server and corresponding bandwidth consumption  Provides partial survivability in case of intermittent LDAP server failure (or network isolation) Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 252 Mediant 1000B Gateway & E-SBC The handling of LDAP queries using the device's LDAP cache is shown in the flowchart below: Figure 15-23: LDAP Query Process with Local LDAP Cache If an LDAP query is required for an Attribute of a key that is already cached with that same Attribute, instead of sending a query to the LDAP server, the device uses the cache.

  • Page 253: Refreshing The Ldap Cache

    "displayName", "mobile" and "ipPhone" Attributes of this search key. When the device receives the LDAP response, it replaces the old values in the cache with the new values received in the LDAP response. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 254: Clearing The Ldap Cache

    Mediant 1000B Gateway & E-SBC Figure 15-25: LDAP Cache Refresh Flowchart  To refresh the LDAP cache per LDAP Server Group: Open the LDAP Settings page (Setup menu > IP Network tab > RADIUS & LDAP folder > LDAP Settings).

  • Page 255: Configuring Local Database For Management User Authentication

    Server Timeout' drop-down list, select one of the following: ♦ Deny Access: User is denied access to the management platform. ♦ Verify Access Locally (default): The device verifies the user's credentials in the Local Users table. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 256: Ldap-Based Login Authentication Example

    Mediant 1000B Gateway & E-SBC Click Apply, and then reset the device with a save-to-flash for your settings to take effect. 15.3.10 LDAP-based Login Authentication Example To facilitate your understanding on LDAP entry data structure and how to configure the device to use and obtain information from this LDAP directory, a brief configuration example is described in this section.
  • Page 257 (where the attribute's value equals the username): Figure 15-29: Username Found using sAMAccount Attribute Search Filter  Management Attribute: memberOf. The attribute contains the member groups of the user: Figure 15-30: User's memberOf Attribute Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 258 Mediant 1000B Gateway & E-SBC  Management Group: mySecAdmin. The group to which the user belongs, as listed under the memberOf attribute: Figure 15-31: User's mySecAdmin Group in memberOf Management Attribute The configuration to match the above LDAP data structure schema is as follows: ...
  • Page 259 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 249): Figure 15-36: Configuring Management Group Attributes for Determining Access Level Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 260: Enabling Ldap Searches For Numbers With Characters

    Mediant 1000B Gateway & 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 261 (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: • "PRIVATE" (PRIVATE:<private_number>): used to match a routing rule based on query results of the private number (MSLDAPPrivateNumAttributeName) Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 262 Mediant 1000B Gateway & E-SBC • "OCS" (OCS:<Skype for Business_number>): used to match a routing rule based on query results of the Skype for Business client number (MSLDAPOCSNumAttributeName) • "PBX" (PBX:<PBX_number>): used to match a routing rule based on query results of the PBX / IP PBX number (MSLDAPPBXNumAttributeName) •...

  • Page 263: Configuring Ad-Based Routing Rules

    If you are using the device's local LDAP cache, see ''Configuring the Device's LDAP Cache'' on page 251 for the LDAP query process. 15.3.12.2 Configuring AD-Based Routing Rules The following procedure describes how to configure outbound IP routing based on LDAP queries. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 264 Mediant 1000B Gateway & E-SBC  To configure LDAP-based IP routing for Skype for Business: Configure the LDAP server parameters, as described in ''Configuring LDAP Servers'' on page 244. Configure the AD attribute names used in the LDAP query: Open the SIP Definitions General Settings page (Setup menu > Signaling &...
  • Page 265 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.2 Mediant 1000B Gateway & E-SBC...

  • Page 266: Querying The Ad For Calling Name

    Mediant 1000B Gateway & 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 267: Least Cost Routing

    The below table shows an example of call cost when taking into consideration call duration. This example shows four defined Cost Groups and the total call cost if the average call duration is 10 minutes: Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 268 Mediant 1000B Gateway & E-SBC 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 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"...

  • Page 269: Configuring Lcr

    Gateway) and Configuring SBC Routing Policy Rules on page 715 (for SBC). Configure Cost Groups - see ''Configuring Cost Groups'' on page 270. Configure Time Bands for a Cost Group - see ''Configuring Time Bands for Cost Groups'' on page 271. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 270: Configuring Cost Groups

    Mediant 1000B Gateway & E-SBC Assign Cost Groups to outbound IP routing rules - see ''Assigning Cost Groups to Routing Rules'' on page 272. 15.4.2.1 Configuring Cost Groups The Cost Groups table lets you configure up to 10 Cost Groups. A Cost Group defines a fixed call connection cost and a call rate (charge per minute).
  • Page 271 Time Band link located below the table; the Time Band table for the selected Cost Group appears. Click New; the following dialog box appears: Configure a Time Band according to the parameters described in the table below. Click Apply, and then save your settings to flash memory. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 272: Assigning Cost Groups To Routing Rules

    Mediant 1000B Gateway & E-SBC Table 15-17: Time Band Table Description Parameter Description Index Defines an index number for the new table row. timeband-index Note: Each row must be configured with a unique index. [CostGroupTimebands_TimebandIndex] Start Time Defines the day and time of day from when this time band is applicable.

  • Page 273: Configuring Remote Web Services

     Capture: Recording of signaling and RTP packets, and Syslog. The remote host can be, for example, a Syslog server or AudioCodes SEM.  QoS: Call routing based on QoS. For more information, see Configuring QoS-Based Routing by Routing Server on page 282.
  • Page 274 Mediant 1000B Gateway & E-SBC Services folder > Remote Web Services). Click New; the following dialog box appears: Figure 15-40: Remote Web Services Table - Add Dialog Box Configure a remote Web service according to the parameters described in the table below.
  • Page 275 [1] Enable = (Default) Connection remains open (persistent) even during inactivity. The device uses HTTP keep-alive / HTTP persistent connection messages to keep the connection open. Number of Sockets Defines how many sockets (connection) are established per remote Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 276 Mediant 1000B Gateway & E-SBC Parameter Description http-num-sockets host. [HTTPRemoteServices_NumOf The valid value is 1 to 10. The default is 1. Sockets] Login Login Needed Enables the use of proprietary REST API Login and Logout commands for connecting to the remote host. The commands http-login-needed verify specific information (e.g., software version) before allowing...

  • Page 277: Configuring Remote Http Hosts

    Figure 15-41: HTTP Remote Hosts Table - Add Dialog Box Configure an HTTP remote host according to the parameters described in the table below. Click Apply, and then save your settings to flash memory. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 278 Mediant 1000B Gateway & E-SBC Table 15-19: HTTP Remote Hosts Table Parameter Descriptions Parameter Description Index Defines an index number for the new table row. rest-servers Note:  [HTTPRemoteHosts_RemoteHostindex] Each row must be configured with a unique index.  The parameter is mandatory.

  • Page 279: Enabling Topology Status Services

    15.5.3 Centralized Third-Party Routing Server You can employ a remote, third-party 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...
  • Page 280 Mediant 1000B Gateway & E-SBC Once the device receives the resultant destination hop from the Routing server, it sends the call to that destination. The Routing server can provide the device with an appropriate route or reject the call. However, if for the initial request (first sent Get Route request for the call) the Routing server cannot find an appropriate route for the call or it does not respond, for example, due to connectivity loss (i.e., the Routing server sends an HTTP 404...
  • Page 281 (see ''Configuring Management User Accounts'' on page 74), which is used by the Routing server (REST client) to log in to the device's management interface. Configure the address and connection settings of the Routing server, referred to as a Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 282: Configuring Qos-Based Routing By Routing Server

    Mediant 1000B Gateway & E-SBC Remote Web Service and HTTP remote host (see ''Configuring Remote Web Services'' on page 273). You must configure the 'Type' parameter of the Remote Web Service to Routing, as shown in the following example: Figure 15-45: Configuring Remote Web Service for Routing Server...

  • Page 283: Http-Based Proxy Services

    Define the URL prefix for accessing the equipment's management interface (see ''Configuring HTTP Proxy Services'' on page 287). To access the equipment's management interface, the administrator needs to enter the following URL in a Web browser: http://<device's WAN IP address:port>/url prefix/ Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 284: Enabling The Http Proxy Application

     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 285: Configuring Http Interfaces

    The HTTP Interfaces table lets you configure up to 10 HTTP Interfaces. An HTTP Interface represents a local, listening interface for receiving HTTP/S requests from HTTP-based (Web) clients such as managed equipment (e.g., IP Phones) and/or AudioCodes EMS management tool for HTTP/S-based services.
  • Page 286 Mediant 1000B Gateway & E-SBC Table 15-20: HTTP Interfaces Table Parameter Descriptions Parameter Description General Index Defines an index number for the new table row. [HTTPInterface_Index] Note:  Each row must be configured with a unique index.  The parameter is mandatory.

  • Page 287: Configuring Http Proxy Services

    The valid value is a string of up to 40 characters. By default, [HTTPProxyService_ServiceName] no value is defined. Note:  Each row must be configured with a unique name. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 288: Configuring Http Proxy Hosts

    Mediant 1000B Gateway & E-SBC Parameter Description  The parameter is mandatory. Listening Interface Assigns an HTTP Interface to the HTTP Proxy service. To configure HTTP Interfaces, see ''Configuring HTTP listening-int Interfaces'' on page 285. [HTTPProxyService_ListeningInterface] Note: The parameter is mandatory.
  • Page 289 Defines the protocol type.  [0] HTTP (default) protocol  [1] HTTPS [HTTPProxyHost_Protocol] HTTP Port Defines the port of the managed equipment. http-port The default is 0. [HTTPProxyHost_Port] Note: The parameter is mandatory. Security Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 290: Configuring An Http-Based Ems Service

    Mediant 1000B Gateway & E-SBC Parameter Description TLS Context Assigns a TLS Context for the TLS connection with the HTTP Proxy host. tls-context By default, the default TLS Context (Index 0) is assigned. [HTTPProxyHost_TLSContext] To configure TLS Contexts, see ''Configuring TLS Certificate Contexts'' on page 109.
  • Page 291 Assigns an HTTP Interface (local, listening HTTP interface:port) for communication with the client. To configure dev-login-int HTTP Interfaces, see ''Configuring HTTP Interfaces'' on page [EMSService_DeviceLoginInterface] 285. By default, no value is defined. Note: The parameter is mandatory. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 292: E9-1-1 Support For Microsoft Skype For Business

    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 Skype for Business 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. This section also describes the configuration of the device for interoperating between the Skype for Business environment and the E9-1-1 emergency provider.

  • Page 293: Microsoft Skype For Business And E9-1-1

    15. Services The VoIP user dials 9-1-1. AudioCodes' ELIN device 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 294 Mediant 1000B Gateway & E-SBC the location of each network element in the enterprise. Immediately after the Skype for Business client registration process or when the operating system detects a network connection change, each Skype for Business client submits a request to the LIS for a location.

  • Page 295: Adding Elins To The Location Information Server

    (CSV) file containing the column formats listed in the table below. Table 15-24: Columns in the LIS Database Network Columns Element <BSSID>,<Description>,<Location>,<CompanyName>,<HouseNumber>,<HouseNumb Wireless access erSuffix>,<PreDirectional>,…<StreetName>,<StreetSuffix>,<PostDirectional>,<City>,<S point tate>,<PostalCode>,<Country> <Subnet>,<Description>,<Location>,<CompanyName>,<HouseNumber>,<HouseNumb Subnet erSuffix>,<PreDirectional>,…<StreetName>,<StreetSuffix>,<PostDirectional>,<City>,<S tate>,<PostalCode>,<Country> <ChassisID>,<PortIDSubType>,<PortID>,<Description>,<Location>,<CompanyName>, Port <HouseNumber>,<HouseNumberSuffix>,…<PreDirectional>,<StreetName>,<StreetSuffi Version 7.2 Mediant 1000B Gateway & E-SBC...

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

    Mediant 1000B Gateway & E-SBC Network Columns Element x>,<PostDirectional>,<City>,<State>,<PostalCode>,<Country> <ChassisID>,<Description>,<Location>,<CompanyName>,<HouseNumber>,<HouseNu Switch mberSuffix>,<PreDirectional>,…<StreetName>,<StreetSuffix>,<PostDirectional>,<City> ,<State>,<PostalCode>,<Country> For the ELIN number to be included in the SIP INVITE (XML-based PIDF-LO message) sent by the Mediation Server to the ELIN device, the administrator must add the ELIN number to the <CompanyName>...

  • Page 297: Audiocodes Elin Device For Skype For Business E9-1-1 Calls To Pstn

    Therefore, IP phones, for example, on a specific floor are in the same subnet and therefore, use the same ELIN when dialing 9-1-1. 15.7.3 AudioCodes ELIN Device for Skype for Business 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 298: Detecting And Handling E9-1-1 Calls

    Mediant 1000B Gateway & E-SBC The figure below illustrates an AudioCodes ELIN device deployed in the Skype for Business environment for handling E9-1-1 calls between the Enterprise and the emergency service provider. 15.7.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 299 IP4 Client t=0 0 m=audio 30684 RTP/AVP 114 111 112 115 116 4 3 8 0 106 97 c=IN IP4 172.29.105.23 a=rtcp:60423 a=label:Audio a=rtpmap:3 GSM/8000/1 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=rtpmap:0 PCMU/8000 Version 7.2 Mediant 1000B Gateway & E-SBC...

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

    Mediant 1000B Gateway & E-SBC a=rtpmap:8 PCMA/8000 a=ptime:20 ------=_NextPart_000_4A6D_01CAB3D6.7519F890 Content-Type: application/pidf+xml Content-ID: <voip_911_user1@contoso.com> <?xml version="1.0" encoding="utf-8"?> <presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:bp="urn:ietf:params:xml:ns:pidf:geopriv10:basicPolicy" xmlns:ca="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr" xmlns:ms="urn:schema:Rtc.LIS.msftE911PidfExtn.2008" entity="sip:voip_911_user1@contoso.com"><tuple id="0"><status><gp:geopriv><gp:location- info><ca:civicAddress><ca:country>US</ca:country><ca:A1>WA</ca:A1> <ca:A3>Redmond</ca:A3><ca:RD>163rd</ca:RD><ca:STS>Ave</ca:STS><ca: POD>NE</ca:POD><ca:HNO>3910</ca:HNO><ca:LOC>40/4451</ca:LOC> <ca:NAM>1111-222-333; 1234567890 </ca:NAM> <ca:PC>98052</ca:PC></ca:civicAddress></gp:location- info><gp:usage-rules><bp:retransmission- allowed>true</bp:retransmission-allowed></gp:usage- rules></gp:geopriv><ms:msftE911PidfExtn><ms:ConferenceUri>sip:+142 55550199@contoso.com;user=phone</ms:ConferenceUri><ms:ConferenceMo de>twoway</ms:ConferenceMode><LocationPolicyTagID xmlns="urn:schema:Rtc.Lis.LocationPolicyTagID.2008">user- tagid</LocationPolicyTagID ></ms:msftE911PidfExtn></status><timestamp>1991-09- 22T13:37:31.03</timestamp></tuple></presence>...

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

    If all the ELINs in the list are in use by active calls, the device selects the ELIN number as follows: The ELIN with the lowest count (i.e., lowest number of active calls currently using this ELIN). Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 302: Location Based Emergency Routing

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

  • Page 303: Configuring The E9-1-1 Callback Timeout

    'Emergency Special Release Cause' drop-down list (EmergencySpecialReleaseCause), select Enable. Figure 15-56: Configuring SIP Release Code for Failed E9-1-1 Calls Click Apply. Note: The feature is applicable only to the Gateway application (digital interfaces). Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 304: Configuring Sbc Ip-To-Ip Routing Rule For E9-1-1

    Mediant 1000B Gateway & E-SBC 15.7.4.4 Configuring SBC IP-to-IP Routing Rule for E9-1-1 To route incoming E9-1-1 calls to the emergency service provider's PSAP server, you need to configure routing rules in the IP-to-IP Routing table for routing between the emergency callers' IP Group and the PSAP server's IP Group.
  • Page 305 ELIN numbers: Figure 15-59: Configuring Destination Number Manipulation Rules for Location-Based Emergency Routing Index 0 manipulates the destination number for London emergency callers; Index 1 manipulates the destination number for Manchester emergency callers. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 306: Viewing The Elin Table

    Mediant 1000B Gateway & E-SBC 15.7.4.6 Viewing the ELIN Table To view the ELIN table:  # show voip e911 ELIN Time Count Index Call From ------------------------------------------------------------ 4257275678 22:11:52 0 4258359333 4257275999 22:11:57 0 4258359444 4257275615 22:12:03 0 4258359555 4257275616...
  • Page 307 SIP-ETag value of last 200 OK) and Expires header value set to "0", as shown in the following example: PUBLISH sip:john.doe@sfb.example SIP/2.0 From: <sip:john.doe@sfb.example>;tag=1c1654434948 To: <sip:john.doe@sfb.example> CSeq: 1 PUBLISH Contact: <sip:john.doe@10.33.221.57:5061;transport=tls> Event: presence Expires: 0 Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 308: Configuring Skype For Business Server For Presence

    Mediant 1000B Gateway & E-SBC User-Agent: sur1-vg1.ecarecenters.net/v.7.20A.001.080 SIP-If-Match: 2545777538-1-1 Content-Length: 0 The following figure shows a basic illustration of the device's integration into Microsoft Skype for Business Presence feature for third-party endpoints. 15.8.1 Configuring Skype for Business Server for Presence On the Skype for Business Server side, you need to define the device in the Skype for Business Topology as a Trusted Application.

  • Page 309: Configuring The Device For Skype For Business Presence

    Enable the Microsoft presence feature: open the SIP Definitions General Settings page (Setup menu > Signaling & Media tab > SIP Definitions folder > SIP Definitions General Settings), and then from the 'Enable MsPresence message' Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 310 Mediant 1000B Gateway & E-SBC drop-down list, select Enable: Figure 15-60: Enabling Microsoft Presence Integration Configure a TLS Context (TLS certificate) for secured communication (mutual authentication) between the device and the Skype for Business Server (see Configuring TLS Certificate Contexts on page 109).
  • Page 311 Call Setup Rules (Set ID) that you configured in Step 7 (above). For Gateway calls: Assign the group of Call Setup Rules (Set ID) that you configured in Step 7 (above) to your Tel-to-IP Routing rules (see Configuring Tel-to-IP Routing Rules on page 511). Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 312 Mediant 1000B Gateway & E-SBC This page is intentionaly left blank. User's Manual Document #: LTRT-27055...

  • Page 313: 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 314: 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 315: Configuring Quality Of Experience Profiles

    (i.e., change in color state). Hysteresis is used to avoid false reports being sent by the device. Hysteresis is used only for threshold crossings toward a lesser severity (i.e., from Red to Yellow, Red to Green, or Yellow to Green). Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 316  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). To configure the SEM server's address, see ''Configuring the SEM Server'' on page 313.
  • Page 317 The valid value is a string of up to 20 characters. [QOEProfile_Name] Sensitivity Level Defines the pre-configured threshold profile to use.  sensitivity-level [0] User Defined = Need to define thresholds per monitored parameter in the Quality of Experience Color Rules table. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 318 Mediant 1000B Gateway & E-SBC Parameter Description  [QOEProfile_SensitivityLevel] [1] Low = Pre-configured low sensitivity thresholds.  [2] Medium = (Default) Pre-configured medium sensitivity thresholds.  [3] High = Pre-configured high sensitivity thresholds. Reporting is done for small fluctuations in parameter values.
  • Page 319 MOS values are in multiples of 10. For example, to denote a MOS of 3.2, the value 32 (i.e., 3.2*10) must be entered.  Delay values are in msec.  Packet Loss values are in percentage (%).  Jitter is in msec. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 320: Configuring Bandwidth Profiles

    Mediant 1000B Gateway & E-SBC Parameter Description  Echo measures the Residual Echo Return Loss (RERL) in Major Hysteresis (Red) Defines the amount of fluctuation (hysteresis) from the Major threshold, configured by the 'Major Threshold (Red)' parameter major-hysteresis-red in order for the threshold to be considered as crossed. The...
  • Page 321 Minor threshold with [32,000 - (10% x hysteresis. 64,000)] Red to Green (alarm cleared) The change occurs if the current bandwidth 25,600 Kbps crosses the configured Minor threshold with [32,000 - (10% x hysteresis. 64,000)] Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 322 Mediant 1000B Gateway & E-SBC The following procedure describes how to configure Bandwidth Profiles through the Web interface. You can also configure it through ini file (BWProfile) or CLI (configure voip > qoe bw-profile).  To configure a Bandwidth Profile: Open the Bandwidth Profile table (Setup menu >...
  • Page 323 Yellow-to-Green (Green-alarm cleared): 25,600 Kbps [32,000 - (10% x 64,000)] Generate Alarm Enables the device to send an SNMP alarm if a bandwidth threshold is crossed. generate-alarms  [0] Disable (default) [BWProfile_GenerateAlarms]  [1] Enable Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 324: Configuring Quality Of Service Rules

    Mediant 1000B Gateway & E-SBC 16.4 Configuring Quality of Service Rules The Quality of Service Rules table lets you configure up to 510 Quality of Service rules. A Quality of Service rule defines an action to perform when the threshold (major or minor) of a specific performance monitoring call metric is crossed for a specific IP Group.
  • Page 325 [1] Minor Note: If you configure the 'Rule Metric' parameter to ACD, ASR or NER, you must configure the parameter to Major. For all other 'Rule Metric' parameter values, you can configure the parameter Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 326 Mediant 1000B Gateway & E-SBC Parameter Description to any value. Action Rule Action Defines the action to be done if the rule is matched.  rule-action [0] Reject Calls = (Default) New calls destined to the specified IP Group are rejected for a user-defined duration. To configure...

  • Page 327: Control Network

    You can also configure it through ini file (CpMediaRealm) or CLI (configure voip > realm).  To configure a Media Realm: Open the Media Realms table (Setup menu > Signaling & Media tab > Core Entities folder > Media Realms). Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 328 Mediant 1000B Gateway & E-SBC Click New; the following dialog box appears: Figure 17-1: Media Realms Table - Add Dialog Box Configure the Media Realm according to the parameters described in the table below. Click Apply. Table 17-1: Media Realms table Parameter Descriptions...
  • Page 329 RTP port 6000, the RTCP port and T.38 port for the session is 6001 and 6002, respectively. However, you can configure the device to use the same port for RTP and T.38 packets, by configuring the Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 330: Configuring Remote Media Subnets

    Mediant 1000B Gateway & E-SBC Parameter Description T38UseRTPPort parameter to 1. For more information on local UDP port range, see ''Configuring RTP Base UDP Port'' on page 203. Default Media Realm Defines the Media Realm as the default Media Realm. The...
  • Page 331 Open the Media Realms table (see ''Configuring Media Realms'' on page 327). Select the Media Realm row for which you want to add Remote Media Subnets, and then click the Remote Media Subnet link located below the table; the Remote Media Subnet table appears. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 332 Mediant 1000B Gateway & E-SBC Click New; the following dialog box appears: Figure 17-3: Remote Media Subnet Table - Add Dialog Box Configure the Remote Media Subnet according to the parameters described in the table below. Click Apply. Table 17-2: Remote Media Subnet Table Parameter Descriptions...

  • Page 333: Configuring Media Realm Extensions

    Open the Media Realms table (see ''Configuring Media Realms'' on page 327). Select the Media Realm for which you want to add Remote Media Extensions, and then click the Media Realm Extension link located below the table; the Media Realm Extension table appears. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 334 Mediant 1000B Gateway & E-SBC Click New; the following dialog box appears: Figure 17-5: Media Realm Extension Table - Add Dialog Box Configure the Media Realm Extension according to the parameters described in the table below. Click Apply. Table 17-3: Media Realm Extension Table Parameter Descriptions...

  • Page 335: Configuring Srds

    As the device is shipped with a default SRD ("DefaultSRD" at Index 0), if your deployment requires only one SRD, you can use the default SRD instead of creating a new one. When Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 336 Mediant 1000B Gateway & E-SBC only one SRD is employed and you create other related configuration entities (e.g., SIP Interfaces), the default SRD is automatically assigned to the new configuration entity. Therefore, when employing a single-SRD configuration topology, there is no need to handle SRD configuration (i.e., transparent).
  • Page 337 Open the SRDs table (Setup menu > Signaling & Media tab > Core Entities folder > SRDs). Click New; the following dialog box appears: Figure 17-7: SRDs Table - Add Dialog Box Configure an SRD according to the parameters described in the table below. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 338 Mediant 1000B Gateway & E-SBC Click Apply. Table 17-4: SRDs table Parameter Descriptions Parameter Description General Index Defines an index for the new table row. [SRD_Index] Note: Each row must be configured with a unique index. Name Defines a descriptive name, which is used when associating the row in other tables.
  • Page 339 IP address. The verification is performed before any of the device's call handling processes (i.e., Classification, Manipulation and Routing). Note:  The parameter is applicable only to calls belonging to User-type IP Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 340 Mediant 1000B Gateway & E-SBC Parameter Description Groups.  The feature is not applicable to REGISTER requests.  The option, Accept Registered Users from Same Source [2] does not apply to registration refreshes. These requests are accepted even if the source address is different to that registered with the device.

  • Page 341: Filtering Tables In Web Interface By Srd

    Tenant size in a multi-tenant architecture can vary and therefore, the instance CPU, memory and interface allocations should be optimized so as not to waste resources for small-sized Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 342 Mediant 1000B Gateway & E-SBC tenants on the one hand, and not to allocate too many instances for a single tenant/customer on the other. For example, it would be a waste to allocate a capacity of 100 concurrent sessions to a small tenant for which 10 concurrent sessions suffice.

  • Page 343: Cloning Srds

    When an SRD is cloned, the device adds the new SRD clone to the next available index row in the SRDs table. The SRD clone is assigned a unique name in the following syntax format: <unique clone ID>_<original SRD index>_CopyOf_<name, or index if no name, of Version 7.2 Mediant 1000B Gateway & E-SBC...

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

    Mediant 1000B Gateway & E-SBC original SRD>. For example, if you clone SRD "SIP-Trunk" at index 2, the new SRD clone is assigned the name, "36454371_2_CopyOf_SIP-Trunk". The SRD clone has identical settings as the original SRD. In addition, all configuration entities associated with the original SRD are also cloned and these clones are associated with the SRD clone.

  • Page 345: Automatic Configuration Based On Srd

     SBC application: • IP-to-IP Routing rules for specifying the destination SIP Interface to where you want to route the call. For more information, see Configuring SBC IP-to-IP Routing Rules on page 695. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 346 Mediant 1000B Gateway & E-SBC • Classification rules for specifying the SIP Interface as a matching characteristic of the incoming call. This is especially useful for the single SRD-configuration topology, where each SIP Interface represents a Layer-3 network (SIP entity).
  • Page 347 The port must be different from ports configured for RTP traffic (i.e., ports configured for Media Realms). For example, if the RTP port range is 6000 to 6999, the SIP port can either be less than Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 348 Mediant 1000B Gateway & E-SBC Parameter Description 6000 or greater than 6999.  The base UDP port number (BaseUDPPort parameter) for RTP traffic must be greater than the highest UDP port configured for a SIP Interface. For example, if your highest configured UDP port for a SIP Interface is 6060, you must configure the BaseUDPPort parameter to any value greater than 6060.
  • Page 349 "calls" so that the attacker assumes that no device exists at such an IP address and port. Note:  The parameter is applicable only if you configure the device to Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 350 Mediant 1000B Gateway & E-SBC Parameter Description reject unclassified calls, which is done using the 'Unclassified Calls' parameter (see Configuring Classification Rules on page 687).  The parameter is applicable only to the SBC application. Pre Classification Assigns a Message Manipulation Set ID to the SIP Interface. This...
  • Page 351 All other requests are rejected. The device verifies whether the IP address and port are different only if the transport protocol is UDP; otherwise, the device verifies only the IP address. The verification is performed before any of the Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 352 Mediant 1000B Gateway & E-SBC Parameter Description device's call handling processes (i.e., Classification, Manipulation and Routing). Note:  The parameter is applicable only to calls belonging to User-type IP Groups.  The feature is not applicable to REGISTER requests. ...

  • Page 353: Configuring Ip Groups

    Bandwidth Profile: Bandwidth utilization thresholds can be applied per IP Group. For example, if bandwidth thresholds are crossed, the device can reject any new calls on this IP Group. To configure Bandwidth Profiles, see ''Configuring Bandwidth Profiles'' on page 320. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 354 Mediant 1000B Gateway & E-SBC Note: • For the Gateway application: IP Group ID 0 cannot be associated with Proxy Set ID 0. • If you delete an IP Group or modify the 'Type' or 'SRD' parameters, the device immediately terminates currently active calls that are associated with the IP Group.
  • Page 355  The IP Group cannot be defined as a User-type since the SIP Contact header of the incoming REGISTER does not represent a specific user. The Request-URI user part can change and Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 356 Mediant 1000B Gateway & E-SBC Parameter Description therefore, the device is unable to identify an already registered user and therefore, adds an additional record to the database. The IP address of the Gateway-type IP Group is obtained dynamically from the host part of the Contact header in the REGISTER request received from the IP Group.
  • Page 357 Enables the IP Group to be used by a third-party routing server for call routing decisions. used-by-routing-server  [0] Not Used (default) [IPGroup_UsedByRoutingSe  [1] Used rver] For more information on the third-party routing server feature, see Centralized Third-Party Routing Server on page 279. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 358 Mediant 1000B Gateway & E-SBC Parameter Description Proxy Set Connectivity (Read-only field) Displays the connectivity status with Server-type IP Groups. As the Proxy Set defines the address of the IP Group, the show voip proxy sets status connectivity check (keep-alive) by the device is done to this address.
  • Page 359 Note: The device can also fork INVITE messages received for a Request-URI of a specific contact (user) registered in the database to all other users located under the same AOR as the specific contact. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 360 Mediant 1000B Gateway & E-SBC Parameter Description This is configured using the SBCSendInviteToAllContacts parameter. Advanced Local Host Name Defines the host name (string) that the device uses in the SIP message's Via and Contact headers. This is typically used to define an local-host-name FQDN as the host name.
  • Page 361 Group according to the received IP address. For requests routed to the IP Group users, the device replaces the Request-URI header with the incoming To header (which contains the remote phone number).  [0] No (default) Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 362 Mediant 1000B Gateway & E-SBC Parameter Description  [1] Yes Note: The parameter is applicable only to User-type IP Groups. SBC PSAP Mode Enables E9-1-1 emergency call routing in a Microsoft Skype for Business environment. sbc-psap-mode  [0] Disable (default) [IPGroup_SBCPSAPMode] ...
  • Page 363 [IPGroup_MsgManUserDef1 The valid value is a string of up to 30 characters. By default, no value is defined. To configure Message Manipulation rules, see ''Configuring SIP Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 364 Mediant 1000B Gateway & E-SBC Parameter Description Message Manipulation'' on page 401. Message Manipulation User- Defines a value for the SIP user part that can be used in Message Defined String 2 Manipulation rules configured in the Message Manipulations table. The...
  • Page 365 [2] SBC as Server = The device acts as an Authentication server:  Authenticates SIP clients, using the usernames and passwords in the User Information table (see SBC User Information for SBC User Database on page 809). This is applicable only to Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 366 Mediant 1000B Gateway & E-SBC Parameter Description User-type IP Groups.  Authenticates SIP severs. This is applicable only to Server- type IP Groups. Authentication Method List Defines SIP methods received from the IP Group that must be challenged by the device when the device acts as an Authentication authentication-method-list server.

  • Page 367: Configuring Proxy Sets

    OPTIONS or REGISTER messages for the keep-alive. The keep-alive feature is required when using the proxy load-balancing or redundancy feature. For load-balancing, the device performs keep-alive on all proxies. For Parking-type redundancy, the device performs Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 368 Mediant 1000B Gateway & E-SBC keep-alive only on the currently active proxy. For Homing-type redundancy, the device performs keep-alive on the current proxy as well as the "main" proxy. When using SIP OPTIONS, you can configure the device to consider the proxy as offline if specific SIP response codes are received from the keep-alive messages.
  • Page 369 Assigns an SRD to the Proxy Set. voip-network proxy-set > srd-id Note:  [ProxySet_SRDName] The parameter is mandatory and must be configured first before you can configure the other parameters in the table. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 370 Mediant 1000B Gateway & E-SBC Parameter Description  To configure SRDs, see Configuring SRDs on page 335. General Index Defines an index number for the new table row. configure voip > voip-network Note: Each row must be configured with a unique index.
  • Page 371 If you enable this Proxy Keep-Alive feature, the device can operate with multiple proxy servers (addresses) for redundancy and load balancing (see the 'Proxy Load Balancing Method' parameter). Proxy Keep-Alive Time Defines the interval (in seconds) between keep-alive messages Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 372 Mediant 1000B Gateway & E-SBC Parameter Description proxy-keep-alive-time sent by the device when the Proxy Keep-Alive feature is enabled (see the 'Proxy Keep-Alive' parameter in this table). [ProxySet_ProxyKeepAliveTime The valid range is 5 to 2,000,000. The default is 60. Note: The parameter is applicable only if the 'Proxy Keep-Alive' parameter is set to Using Options.
  • Page 373  [2] Random Weights = The outgoing requests are not distributed equally among the Proxies. The weights are received from the DNS server, using SRV records. The device sends the Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 374 Mediant 1000B Gateway & E-SBC Parameter Description requests in such a fashion that each proxy receives a percentage of the requests according to its' assigned weight. A single FQDN should be configured as a proxy IP address. Random Weights Load Balancing is not used in the following scenarios: ...
  • Page 375 15 IP addresses. However, the device supports up to 30 DNS-resolved IP addresses. If the device receives more than this number of IP addresses, it uses the first 30 IP addresses in the received list and ignores the rest. Proxy Address Table Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 376 Mediant 1000B Gateway & E-SBC Parameter Description Index Defines an index number for the new table row. proxy-ip-index Note: Each row must be configured with a unique index. [ProxyIp_ProxyIpIndex] Proxy Address Defines the address of the proxy. proxy-address Up to 10 addresses can be configured per Proxy Set. The address can be defined as an IP address in dotted-decimal notation (e.g.,...

  • Page 377: Building And Viewing Sip Entities In Topology View

    Click the demarcation name; the name becomes editable in a text box, as shown in the example below: Type a name as desired, and then click anywhere outside of the text box to apply the Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 378 Mediant 1000B Gateway & E-SBC Item # Description name. You can use demarcation to visually separate your voice network to provide a clearer understanding of your topology. This is especially useful for IP Groups, SIP Interfaces, and Media Realms, where you can display them on the top or bottom border of the Topology view (as shown in the figure below for callouts #1 and #2, respectively).
  • Page 379 The Media Realms table opens with a new dialog box for adding a Media Realm to the next available index row. Configure the Media Realm as desired, and then click Apply; the Media Realms table closes and you are returned to the Topology View, displaying the new Media Realm. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 380 Mediant 1000B Gateway & E-SBC Item # Description For more information on configuring Media Realms, see ''Configuring Media Realms'' on page 327. Configured IP Groups. Each IP Group is displayed using the following "IP Group [Server]" or "IP Group [User]" titled icon (depending on whether it's a Server- or User-type IP Group...
  • Page 381 Item #6 above. To configure a trunk (BRI or E1/T1), do the following: Click the icon, and then from the drop-down menu, choose Trunk Settings; the Trunk Settings page appears. Configure the trunk as desired. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 382 Mediant 1000B Gateway & E-SBC Item # Description For more information on configuring trunk settings, see Configuring Trunk Settings on page 479. Links to Web pages relating to commonly required Gateway configuration:  Number Manipulation: Opens the Destination Phone Number Manipulation for IP-to-Tel Calls table where you can configure destination phone number manipulation rules for IP-to-Tel calls (see Configuring Number Manipulation Tables on page 541).

  • Page 383: Sip Definitions

    You can also configure it through ini file (Account) or CLI (configure voip > sip-definition account).  To configure an Account: Open the Accounts table (Setup menu > Signaling & Media tab > SIP Definitions folder > Accounts). Click New; the following dialog box appears: Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 384 Mediant 1000B Gateway & E-SBC Configure an account according to the parameters described in the table below. Click Apply. Once you have configured Accounts, you can register or un-register them, as described below:  To register or un-register an Account: In the table, select the required Account entry row.
  • Page 385 'SIP Group Name' parameter value configured in the IP Groups table is used instead. Register Enables registration.  register [0] No= (Default) The device only performs authentication (not registration). Authentication is Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 386 Mediant 1000B Gateway & E-SBC Parameter Description [Account_Register] typically done for INVITE messages sent to the "serving" IP Group. If the device receives a SIP 401 (Unauthorized) in response to a sent INVITE, the device checks for a matching "serving" and "served"...
  • Page 387 If the device's physical Ethernet link to the proxy goes down, the device re-registers this Account with the proxy when the link comes up again. Re-registration occurs even if proxy keep-alive is disabled. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 388: Regular Registration Mode

    Mediant 1000B Gateway & E-SBC Parameter Description Note: The parameter is applicable only if you have enabled the Registrar Stickiness feature (in this table):  'Register' parameter to Regular or GIN.  'Registrar Stickiness' parameter to Enable. Reg Event Package Subscription...

  • Page 389: Single Registration For Multiple Phone Numbers Using Gin

    '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.2 Mediant 1000B Gateway & E-SBC...

  • Page 390: Registrar Stickiness

    Mediant 1000B Gateway & E-SBC 18.1.3 Registrar Stickiness You can enable the Registrar Stickiness feature per Account. Registrar Stickiness binds an Account to one of the IP addresses (configured or DNS-resolved) in the Proxy Set associated with the Serving IP Group. Once an Account registers successfully to one of the IP addresses (i.e., SIP registrar server) in the Proxy Set, the device routes all subsequent...

  • Page 391: Sip Message Authentication Example

    Upon receipt of this request, the Registrar/Proxy returns a 401 Unauthorized response: 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 Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 392 • 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 393: Configuring Call Setup Rules

    For example, tags can be used to categorize calls by department (source user) within a company, where only certain departments are allowed to place Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 394 Mediant 1000B Gateway & E-SBC international calls.  Manipulation (similar to the Message Manipulations table) of call parameters (such as source number, destination number, and redirect number) and SBC SIP messages.  Conditions for routing, for example, if the source number equals a specific value, then use the call routing rule.
  • Page 395 The valid value is 0 to 9. The default is 0. Query Type Defines the type of query.  query-type [0] None (default)  [1] LDAP = The Call Setup rule performs an LDAP query [CallSetupRules_QueryType] Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 396 Mediant 1000B Gateway & E-SBC Parameter Description with an LDAP server.  [2] Dial Plan = The Call Setup rule performs a query with the Dial Plan. To specify an LDAP server or Dial Plan, use the 'Query Target' parameter (see below).
  • Page 397 Defines the type of action to perform.  action-type [0] Add (default) = Adds new message header, parameter or body elements. [CallSetupRules_ActionType]  [1] Remove = Removes message header, parameter, or body elements. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 398: Call Setup Rule Examples

    Mediant 1000B Gateway & E-SBC Parameter Description  [2] Modify = Sets element to the new value (all element types).  [3] Add Prefix = Adds value at the beginning of the string (string element only).  [4] Add Suffix = Adds value at the end of the string (string element only).
  • Page 399 Routing table configuration: Two routing rules are assigned with the same matching characteristics. Only the main routing rule is assigned a Call Setup Rules Set ID. ♦ Index 1:  'Call Setup Rules Set ID': 3 Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 400 Mediant 1000B Gateway & E-SBC  'Destination IP Group ID': 3 (IP Group for Skype for Business) ♦ Index 2:  'Destination IP Group ID': 4 (IP Group of PBX)  Example 4: The example enables routing based on LDAP queries and destination tags.

  • Page 401: 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.2 Mediant 1000B Gateway & E-SBC...
  • Page 402 Mediant 1000B Gateway & 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 403 User's Manual 19. SIP Message Manipulation The figure below illustrates a SIP message manipulation example: Figure 19-2: SIP Header Manipulation Example Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 404 Mediant 1000B Gateway & E-SBC Note: • 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 405 Previous Condition, Index 4 and 5 use the condition configured for Index 3. A configuration example is shown in the beginning of this section. The option allows you to use the same condition for multiple manipulation rules. Note: Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 406 Mediant 1000B Gateway & E-SBC Parameter Description  When configured to Use Previous Condition, the 'Message Type' and 'Condition' parameters are not applicable and if configured are ignored.  When multiple manipulation rules apply to the same header, the next rule applies to the resultant string of the previous rule.

  • Page 407: Configuring Message Condition Rules

    Web interface. You can also configure it through ini file (ConditionTable) or CLI (configure voip > sbc routing condition-table).  To configure a Message Condition rule: Open the Message Conditions table (Setup menu > Signaling & Media tab > Message Manipulation folder > Message Conditions). Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 408: Configuring Sip Message Policy Rules

    Mediant 1000B Gateway & E-SBC Click New; the following dialog box appears: Figure 19-5: Message Conditions Table - Add Dialog Box Configure a Message Condition rule according to the parameters described in the table below. Click Apply. An example of configured Message Condition rules is shown in the figure below: Figure 19-6: Example of Configured SIP Message Conditions ...
  • Page 409 You can also configure it through ini file (MessagePolicy) or CLI (configure voip > message message-policy).  To configure SIP Message Policy rules: Open the Message Policies table (Setup menu > Signaling & Media tab > Message Manipulation folder > Message Policies). Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 410 Mediant 1000B Gateway & E-SBC Click New; the following dialog box appears: Figure 19-7: Message Policies Table - Add Dialog Box Configure a Message Policy rule according to the parameters described in the table below. Click Apply. Table 19-3: Message Policies Table Parameter Descriptions...
  • Page 411 Defines the policy (blacklist or whitelist) for the SIP body specified in the 'Body List' parameter (above). body-list-type  [0] Policy Blacklist =The specified SIP body is [MessagePolicy_BodyListType] rejected.  [1] Policy Whitelist = (Default) Only the specified Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 412: Configuring Pre-Parsing Manipulation Rules

    Mediant 1000B Gateway & E-SBC Parameter Description SIP body is allowed; the others are rejected. Malicious Signature Malicious Signature Database Enables the use of the Malicious Signature database (signature-based detection). signature-db-enable  [0] Disable (default) [MessagePolicy_UseMaliciousSignatureDB]  [1] Enable To configure Malicious Signatures, see ''Configuring Malicious Signatures'' on page 751.
  • Page 413 Click New; the following dialog box appears: Figure 19-9: Pre-Parsing Manipulation Rules Table - Add Dialog Box Configure a rule according to the parameters described in the table below. Click New, and then save your settings to flash memory. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 414 Mediant 1000B Gateway & E-SBC Pre-Parsing Manipulation Rules Table Parameter Descriptions Parameter Description Match Index Defines an index number for the new table row. [PreParsingManipulationRules_R Note: Each row must be configured with a unique index. uleIndex] Message Type Defines the SIP message type to which you want to apply the rule.

  • Page 415: Coders And Profiles

    For supported audio coders, see ''Supported Audio Coders'' on page 417. • Some coders are license-dependent and are available only if purchased from AudioCodes and included in the License Key installed on your device. For more information, contact your AudioCodes sales representative. •...
  • Page 416 Mediant 1000B Gateway & E-SBC The following procedure describes how to configure the Coder Groups table through the Web interface. You can also configure it through ini file (AudioCodersGroups and AudioCoders) or CLI (configure voip > coders-and-profiles audio-coders-groups).  To configure a Coder Group: Open the Coder Groups table (Setup menu >...

  • Page 417: Supported Audio Coders

    [90] 64 8 or 50, 60, 80, 100, 120 Dynamic g711a-law-vbd (default 118) [23] G.711U-law_VBD 10, 20 (default), 30, 40, [90] 64 0 or 50, 60, 80, 100, 120 Dynamic g711u-law-vbd (default 110) [24] Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 418 Mediant 1000B Gateway & E-SBC Coder Name Packetization Time Rate (kbps) Payload Silence (msec) Type Suppression [1] 10, [2] 20, [3] 30, [4] 40, [5] 50, [6] 60, [8] 80, [9] 90, [10] 100, [12] 120 G.722 20 (default), 40, 60, 80,...

  • Page 419: Configuring Allowed Audio Coder Groups

    G.711 is listed first, and sends the SIP message containing only the G.711 and G.729 coders in the SDP. To apply an Allowed Audio Coders Group for restricting coders to a SIP entity: Configure an Allowed Audio Coders Group in the Allowed Audio Coders Groups table Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 420 Mediant 1000B Gateway & E-SBC (see description below). In the IP Profile associated with the SIP entity (see ''Configuring IP Profiles'' on page 423): • Assign the Allowed Audio Coders Group (using the IpProfile_SBCAllowedAudioCodersGroupName parameter). • Enable the use of Allowed Audio Coders Groups (by configuring the IpProfile_SBCAllowedCodersMode parameter to Restriction or Restriction and Preference).
  • Page 421 Defines a user-defined coder. user-define-coder The valid value is a string of up to 24 characters (case-insensitive). For example, "HD.123" [AllowedAudioCoders_UserDefineCoder] (without quotes). Note: Each coder can be configured only once per Allowed Audio Coders Group. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 422: Configuring Allowed Video Coder Groups

    Mediant 1000B Gateway & E-SBC 20.3 Configuring Allowed Video Coder Groups The Allowed Video Coders Groups table lets you configure up to four Allowed Video Coders Groups for SBC calls. Each Allowed Video Coders Group can be configured with up to 10 coders. An Allowed Video Coders Group defines a list of video coders that can be used when forwarding video streams to a specific SIP entity.

  • Page 423: Configuring Ip Profiles

    (e.g., SIP message terminations such as REFER) and media (e.g., coder type). An IP Profile can later be assigned to specific IP calls (inbound and/or outbound). Thus, IP Profiles provide high-level adaptation Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 424 Mediant 1000B Gateway & E-SBC when the device interworks between different IP entities, each of which may require different handling by the device. This can include, for example, transcoding or even transrating (of packetization time). For example, if a specific IP entity uses the G.711 coder only, you can configure an IP Profile with G.711 for this IP entity.
  • Page 425 If two SBC legs (after offer-answer negotiation) use different security types (i.e., one RTP and the other SRTP), the device performs RTP- SRTP transcoding. To transcode between RTP and SRTP, the following prerequisites must be met: Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 426 Mediant 1000B Gateway & E-SBC Parameter Description  At least one supported SDP "crypto" attribute and parameters.  EnableMediaSecurity must be set to 1. If one of the above transcoding prerequisites is not met, then:  any value other than “As is” is discarded.
  • Page 427 ROC index (and other SRTP fields) as done by the server, resulting in a synchronized SRTP. Note:  If this feature is disabled and the server resets the ROC upon a Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 428 Mediant 1000B Gateway & E-SBC Parameter Description re-key generation, one-way voice may occur.  The corresponding global parameter is ResetSRTPStateUponRekey. Generate SRTP Keys Mode Enables the device to generate a new SRTP key upon receipt of a re-INVITE with the SIP entity associated with the IP Profile.
  • Page 429 (non-standard). The parameter enables the device to forward multiple answers to the SIP entity associated with the IP Profile. The sbc-multi-answers parameter is applicable only when the [IpProfile_SBCRemoteMultiple IpProfile_SBCRemoteMultipleEarlyDialogs parameter is disabled. AnswersMode] Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 430 Mediant 1000B Gateway & E-SBC Parameter Description  [0] Disable = (Default) Device always sends the same SDP answer, which is based on the first received answer that it sent to the SIP entity, for all forked responses (even if 'Forking Handling Mode' is Sequential), and thus, may result in transcoding.
  • Page 431 Allowed Audio Coders Group or Allowed Video Coders Group. The coders in the original SDP offer are listed after the Allowed coders.  [2] Restriction and Preference = Performs both Restriction and Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 432 Mediant 1000B Gateway & E-SBC Parameter Description Preference. Note:  The parameter is applicable only if Allowed coders are assigned to the IP Profile (see the 'Allowed Audio Coders' or 'Allowed Video Coders' parameters).  For more information on the Allowed Coders feature, see Restricting Coders on page 658.
  • Page 433 SIP re-INVITE (or UPDATE) from the SIP entity to where the SIP INFO is being sent (and keep sending the DTMF digits using the RFC 2833 method). This is done using AudioCodes proprietary SIP header X-AC-Action and a Message Manipulation...
  • Page 434 Mediant 1000B Gateway & E-SBC Parameter Description If the IP Profile name contains one or more spaces, you must enclose the name in double quotation marks, for example: X-AC-Action: 'switch-profile;profile-name="My IP Profile"' The Message Manipulation rule adds the proprietary header with the...
  • Page 435 Whether RTP redundancy is implemented depends on the subsequent incoming SDP answer from the SIP entity. The device does not modify the incoming SDP offer received from the SIP entity, but if RTP redundancy is required, it will be supported. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 436 Mediant 1000B Gateway & E-SBC Parameter Description Select the option if the SIP entity requires RTP redundancy.  [2] Disable = The device removes the RTP redundancy payload (if present) from the SDP offer/answer for calls received from or sent to the SIP entity. Select the option if the SIP entity does not support RTP redundancy.
  • Page 437 Note: The corresponding global parameter is PremiumServiceClassMediaDiffServ. Signaling DiffServ Defines the DiffServ value for Premium Control CoS content (Call Control applications). signaling-diffserv The valid range is 0 to 63. The default is 40. [IpProfile_SigIPDiffServ] Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 438 Mediant 1000B Gateway & E-SBC Parameter Description Note: The corresponding global parameter is PremiumServiceClassControlDiffServ. Jitter Buffer Dynamic Jitter Buffer Defines the minimum delay (in msec) of the device's dynamic Jitter Minimum Delay Buffer. jitter-buffer-minimum-delay The valid range is 0 to 150. The default delay is 10.
  • Page 439  [2] Not Supported = The device does not allow a session timer with this SIP entity.  [3] Supported = The device enables the session timer with this Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 440 Mediant 1000B Gateway & E-SBC Parameter Description SIP entity. If the incoming SIP message does not include any session timers, the device adds the session timer information to the sent message. You can configure the value of the Session- Expires and Min-SE headers, using the SBCSessionExpires and SBCMinSE parameters, respectively.
  • Page 441 Enables interworking SIP User-Agent headers between SIP entities. The parameter defines the device's handling of User-Agent headers sbc-keep-user-agent for response/request messages sent to the SIP entity associated [IpProfile_SBCKeepUserAgen with the IP Profile. tHeader] Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 442 Mediant 1000B Gateway & E-SBC Parameter Description  [-1] According to Operation Mode = (Default) Depends on the setting of the 'Operation Mode' parameter in the IP Group or SRDs table:  B2BUA: Device operates as if this parameter is set to Disable [0].
  • Page 443 [0] Regular = (Default) SIP Refer-To header value is unchanged ehavior] and the device forwards the REFER message as is.  [1] Database URL = SIP Refer-To header value is changed so that the re-routed INVITE is sent through the device: Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 444 Mediant 1000B Gateway & E-SBC Parameter Description Before forwarding the REFER request, the device changes the host part to the device's IP address and adds a special prefix ("T~&R_") to the Contact user part. The incoming INVITE is identified as a REFER-resultant INVITE according to this special prefix.
  • Page 445 (FEU) located in another subnet. For example, a far-end user (FEU) in the WAN sends a SIP request via the device to a Redirect server in the LAN, Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 446 Mediant 1000B Gateway & E-SBC Parameter Description and the Redirect server replies with a SIP 3xx response to a PBX in the LAN in the Contact header. If the device sends this response as is (i.e., with the original Contact header), the FEU is unable to reach the new destination.
  • Page 447 IP Profile for all re-INVITE offer-answer transactions (except for initial INVITE). Note: The fax settings in the IP Profile include IpProfile_SBCFaxCodersGroupName, IpProfile_SBCFaxOfferMode, and IpProfile_SBCFaxAnswerMode. Fax Offer Mode Defines the coders included in the outgoing SDP offer (sent to the Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 448 Mediant 1000B Gateway & E-SBC Parameter Description sbc-fax-offer-mode called "fax") for the SIP entity associated with the IP Profile.  [IpProfile_SBCFaxOfferMode] [0] All coders = (Default) Use only (and all) the coders of the selected Coder Group configured using the SBCFaxCodersGroupID parameter.
  • Page 449 Media IP Version Preference Defines the preferred RTP media IP addressing version for outgoing SIP calls (according to RFC 4091 and RFC 4092). The RFCs media-ip-version-preference concern Alternative Network Address Types (ANAT) semantics in the [IpProfile_MediaIPVersionPref Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 450 Mediant 1000B Gateway & E-SBC Parameter Description erence] SDP to offer groups of network addresses (IPv4 and IPv6) and the IP address version preference to establish the media stream. The IP address is indicated in the "c=" field (Connection) of the SDP.
  • Page 451 Enables the device to send SIP 183 responses with SDP to the IP upon receipt of INVITE messages. enable-early-183  [0] Disable (default) [IpProfile_EnableEarly183]  [1] Enable = By sending the 183 response, the device opens an Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 452 Mediant 1000B Gateway & E-SBC Parameter Description RTP channel before receiving the "progress" tone from the ISDN side. The device sends RTP packets immediately upon receipt of an ISDN Progress, Alerting with Progress indicator, or Connect message according to the initial negotiation without sending the 183 response again, thereby saving response time and avoiding early media clipping.
  • Page 453 Hold/Retrieve supplementary service from ISDN to SIP (digital enable-hold interfaces). For analog: The Call Hold feature allows users, [IpProfile_EnableHold] connected to the device, to place a call on hold (or remove from hold), using the phone's Hook Flash button. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 454 Mediant 1000B Gateway & E-SBC Parameter Description  [0] Disable  [1] Enable (default) Note:  Digital interfaces: To interwork the Hold/Retrieve supplementary service from SIP to ISDN (QSIG and Euro ISDN), set the EnableHold2ISDN parameter to 1.  Analog interfaces: To use the call hold service, the devices at both ends must support this option.
  • Page 455 [5] INFO (Korea) = Sends DTMF digits according to the Korea Telecom format. Note:  When out-of-band DTMF transfer is used ([1], [2], [3], or [5]), the DTMFTransportType parameter is automatically set to 0 (DTMF Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 456 Mediant 1000B Gateway & E-SBC Parameter Description digits are removed from the RTP stream).  If an ISDN phone user presses digits (e.g., for interactive voice response / IVR applications such as retrieving voice mail messages), 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.
  • Page 457 (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 bypass packet interval is configured according to the FaxModemBypassBasicRtpPacketInterval Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 458 Mediant 1000B Gateway & E-SBC Parameter Description parameter. The SDP contains the following line: 'a=rtpmap:100 X-NSE/8000'. Note:  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 459: Configuring Tel Profile

    Tel Profiles provide high-level adaptation when the device interworks between different equipment and protocols (at both the Tel and IP sides), each of which may require different Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 460 Mediant 1000B Gateway & E-SBC handling by the device. For example, if specific channels require the use of the G.711 coder, you can configure a Tel Profile with this coder and assign it to these channels. To use your Tel Profile for specific calls, you need to assign it to specific channels (trunks) in the Trunk Group table (see Configuring Trunk Groups on page 503)).
  • Page 461 1007766 as the destination number, then after the call is answered it waits 1.5 seconds ('p') and plays the rest of the number (100) as DTMF digits. Additional examples: 1664wpp102, 66644ppp503, and Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 462 Mediant 1000B Gateway & E-SBC Tel Profile Parameter Global Parameter 7774w100pp200. Note:  For the parameter to take effect, a device reset is required.  Analog interfaces: The called number can include characters 'p' (1.5 seconds pause) and 'd' (detection of dial tone). If character 'd' is used, it must be the first 'digit' in the called number.
  • Page 463 Defines the duration (in seconds) that the device plays a busy or reorder tone before releasing the line. time-for-reorder-tone [TelProfile_TimeForReorderTone] Analog interfaces: Typically, after playing the busy or reorder tone for this duration, the device starts playing an offhook Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 464 Mediant 1000B Gateway & E-SBC Tel Profile Parameter Global Parameter warning tone. The valid range is 0 to 254. The default is 0 seconds for analog interfaces and 10 seconds for digital interfaces. Note that the Web interface denotes the default value (for analog and digital interfaces) as a string value of "255".
  • Page 465 Note:  The parameter is applicable to FXS and FXO interfaces.  The current disconnect duration is configured by the CurrentDisconnectDuration parameter.  The current disconnect threshold (FXO only) is configured by Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 466 Mediant 1000B Gateway & E-SBC Tel Profile Parameter Global Parameter the CurrentDisconnectDefaultThreshold parameter.  The frequency at which the analog line voltage is sampled is configured by the TimeToSampleAnalogLineVoltage parameter.  The corresponding global parameter is EnableCurrentDisconnect. DID Wink Enables Direct Inward Dialing (DID) using Wink-Start signaling,...
  • Page 467  For more information on DiffServ, see ''Configuring Class-of- Service QoS'' on page 159.  The corresponding global parameter is PremiumServiceClassControlDiffServ. Enable Early Media Enables the Early Media feature, which sends media (e.g., Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 468 Mediant 1000B Gateway & E-SBC Tel Profile Parameter Global Parameter early-media ringing) before the call is established.  [TelProfile_EnableEarlyMedia] [0] Disable (default)  [1] Enable  Digital: The device sends a SIP 18x response with SDP, allowing the media stream to be established before the call is answered.
  • Page 469 The valid range is 0 to 12. The default factor is 10. [TelProfile_JitterBufOptFactor] For more information on Jitter Buffer, see ''Configuring the Dynamic Jitter Buffer'' on page 199. Note:  For data (fax and modem) calls, configure the parameter to Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 470 Mediant 1000B Gateway & E-SBC Tel Profile Parameter Global Parameter  The corresponding global parameter is DJBufOptFactor. Analog MWI MWI Analog Lamp Enables the visual display of message waiting indications (MWI). mwi-analog-lamp  [0] Disable (default). [TelProfile_MWIAnalog]  [1] Enable = Enables visual MWI by supplying line voltage of approximately 100 VDC to activate the phone's lamp.
  • Page 471  Hook-flash generation period upon detection of a SIP INFO message containing a hook-flash signal.  FXO interfaces: Hook-flash generation period. The valid range is 25 to 3,000. The default is 700. Note: Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 472 Mediant 1000B Gateway & E-SBC Tel Profile Parameter Global Parameter  The parameter is applicable to FXS and FXO interfaces  For FXO interfaces, a constant of 100 msec must be added to the required hook-flash period. For example, to generate a 450 msec hook-flash, configure the parameter to 550.

  • Page 473: Gateway Application

    Part V Gateway Application...

  • Page 475: Introduction

    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. 21.1 Call Processing Summary The device's call processing for Gateway calls is shown in the following flowcharts. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 476 Mediant 1000B Gateway & E-SBC  IP-to-Tel Call: Figure 21-1: IP-to-Tel Call Processing Flowchart User's Manual Document #: LTRT-27055...
  • Page 477 User's Manual 21. Introduction  Tel-to-IP Call: Figure 21-2: Tel-to-IP Call Processing Flowchart Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 478 Mediant 1000B Gateway & E-SBC This page is intentinally left blank. User's Manual Document #: LTRT-27055...

  • Page 479: Digital Pstn

    Release Note). • 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 480 Mediant 1000B Gateway & E-SBC  To configure trunks: Open the Trunk Settings page (Setup menu > Signaling & Media tab > Gateway folder > Trunks & Groups > Trunks). On the top of the page, a bar with Trunk number icons displays the status of each trunk according to the following color codes: •...

  • Page 481: Tdm And Timing

    22.2.1.1 Recovering Clock from PSTN Line Interface 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 1152. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 482: Configuring Internal Clock As Clock Source

    Mediant 1000B Gateway & E-SBC  To configure synchronization based on clock from PSTN line: Open the TDM Bus Settings page (Setup menu > Signaling & Media tab > Media folder > TDM Bus Settings), and then do the following:...

  • Page 483: 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 Apply, and then reset the device. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 484 Mediant 1000B Gateway & E-SBC Note: • 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 485: Configuring Digital Gateway Parameters

    Open the Digital Gateway Settings page (Setup menu > Signaling & Media tab > Gateway folder > Digital Gateway > Digital Gateway Settings). Figure 22-4: Digital Gateway Parameters Page Configure the parameters as required. Click Apply. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 486: Tunneling Applications

    Mediant 1000B Gateway & E-SBC 22.5 Tunneling Applications This section discusses the device's support for VoIP tunneling applications. 22.5.1 TDM Tunneling The device's TDM Tunneling feature allows you to tunnel groups of digital trunk spans or timeslots (B-channels) over the IP network. TDM Tunneling utilizes the device's internal...
  • Page 487 TrunkGroup 1 = 0,0,0,1,31,1000,1; TrunkGroup 1 = 0,1,1,1,31,2000,1; TrunkGroup 1 = 0,2,2,1,31,3000,1; TrunkGroup 1 = 0,3,3,1,31,4000,1; TrunkGroup 1 = 0,0,0,16,16,7000,2; TrunkGroup 1 = 0,1,1,16,16,7001,2; TrunkGroup 1 = 0,2,2,16,16,7002,2; TrunkGroup 1 = 0,3,3,16,16,7003,2; [/TrunkGroup] Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 488 Mediant 1000B Gateway & E-SBC [ AudioCodersGroups ] FORMAT AudioCodersGroups_Index = AudioCodersGroups_Name; AudioCodersGroups 0 = "AudioCodersGroups_0"; AudioCodersGroups 1 = "AudioCodersGroups_1"; [ \AudioCodersGroups ] [ AudioCoders ] AudioCoders 0 = "AudioCodersGroups_0", 0, 0, 3, 7, -1, 0, ""; AudioCoders 1 = "AudioCodersGroups_1", 0, 7, 2, 90, 56, 0, "";...

  • Page 489: Dsp Pattern Detector

    (commonly called Ringdown circuits). No dialing is necessary; the user simply picks up the handset or pushes a button and a dedicated line is seized. Thus, many turrets have multiple handsets Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 490 Mediant 1000B Gateway & E-SBC and multi-channel speaker units, allowing immediate connection with multiple parties (e.g., 30 channels). These channels remain constantly open throughout the trading day. Today, private wire services are evolving from digital TDM architectures to IP-based architectures. The device can be used for interworking between these two architectures, where you have the PSTN switch (PBX) using the E1/T1 CAS protocol on one side, and a SIP-based private wire (turret system) trunk on the other side.
  • Page 491 <xsd:sequence> <xsd:choice> <xsd:element ref="ringDown" /> <xsd:element ref="hookSwitch" /> <xsd:any namespace="##other" minOccurs="0" maxOccurs="unbounded" processContents="lax" /> </xsd:choice> </xsd:sequence> <xsd:anyAttribute namespace="##other" processContents="lax" /> </xsd:complexType> <xsd:element name="pwSignal" type="pwSignallingType"/> <!-- ringDown --> <xsd:complexType name="ringDownType"> <xsd:sequence> <xsd:any namespace="##other" minOccurs="0" Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 492 Mediant 1000B Gateway & E-SBC maxOccurs="unbounded" processContents="lax" /> </xsd:sequence> <xsd:attribute name="signal" type="ringDownSignalType" use="required"/> <xsd:anyAttribute namespace="##other" processContents="lax" /> </xsd:complexType> <xsd:element name="ringDown" type="ringDownType"/> <!-- hookSwitch --> <xsd:complexType name="hookSwitchType"> <xsd:sequence> <xsd:any namespace="##other" minOccurs="0" maxOccurs="unbounded" processContents="lax" /> </xsd:sequence> <xsd:attribute name="signal" type="hookSwitchSignalType" use="required"/> <xsd:anyAttribute namespace="##other" processContents="lax" />...
  • Page 493 E1 or T1 CAS Trunk. Make sure that you select the CAS table file that you loaded in the previous step, in the 'CAS Table per Trunk' field: Figure 22-9: Selecting CAS File for Trunk - Private Wire Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 494: Qsig Tunneling

    Mediant 1000B Gateway & E-SBC In the Trunk Group table (see Configuring Trunk Groups on page 503), configure the Trunk Group ID for the E1/T1 CAS Trunk, as shown in the following example: Figure 22-10: Configuring Trunk Group for Private Wire...

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

    D-channel fails. The device supports up to 12 NFAS groups. Each group can comprise up to 10 T1 trunks and each group must contain different T1 trunks. Each T1 trunk is called an "NFAS Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 496: Nfas Interface Id

    Mediant 1000B Gateway & E-SBC member". The T1 trunk whose D-channel is used for signaling is called the "Primary NFAS Trunk". The T1 trunk whose D-channel is used for backup signaling is called the "Backup NFAS Trunk". The primary and backup trunks each carry 23 B-channels while all other NFAS trunks each carry 24 B-channels.

  • Page 497: Working With Dms-100 Switches

    Stop or delete (by setting ProtocolType to 0, i.e., 'None') all NFAS (‘slave’) trunks. Stop or delete (by setting ProtocolType to 0, i.e., 'None') the backup trunk if a backup trunk exists. Stop or delete (by setting ProtocolType to 0, i.e., 'None') the primary trunk. Version 7.2 Mediant 1000B Gateway & E-SBC...

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

    Mediant 1000B Gateway & E-SBC Note: • All trunks in the group must be configured with the same values for trunk parameters TerminationSide, ProtocolType, FramingMethod, and LineCode. • After stopping or deleting the backup trunk, delete the group and then reconfigure 22.6.4 Performing Manual D-Channel Switchover in NFAS Group...

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

    Tel-to-IP calls: • ISDNRxOverlap: Enables Tel-to-IP overlap dialing and defines how the device sends the collected digits to the IP side - in SIP re-INVITE [2] or INFO messages [3]. Version 7.2 Mediant 1000B Gateway & E-SBC...

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

    Mediant 1000B Gateway & E-SBC • MinOverlapDigitsForRouting: Defines the minimum number of overlap digits to collect from the Tel side before the device can send the first SIP message (INVITE) for routing the call to the IP side. • MaxDigits: Defines the maximum number of collected digits that can be received from the Tel side (if ISDN Sending Complete IE is not received).
  • Page 501 4/5ESS Euro ISDN QSIG TE-to-NT Table 22-3: Redirect Number NT/TE Interface DMS-100 NI-2 4/5ESS Euro ISDN QSIG NT-to-TE TE-to-NT Yes* * When using ETSI DivertingLegInformation2 in a Facility IE (not Redirecting Number IE). Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 502 Mediant 1000B Gateway & E-SBC This page is intentionaly left blank. User's Manual Document #: LTRT-27055...

  • Page 503: Trunk Groups

    ''Configuring Trunk Group Settings'' on page 505).  To register the Trunk Groups, click the Register button located below the Trunk Group table.  To unregister the Trunk Groups, click the Unregister button located below the Trunk Group table. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 504 Mediant 1000B Gateway & E-SBC Table 23-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] From Trunk Defines the starting physical Trunk number in the Trunk Group.

  • Page 505: Configuring Trunk Group Settings Table

    To configure Trunk Group settings: Open the Trunk Group Settings table (Setup menu > Signaling & Media tab > Gateway folder > Trunks & Groups > Trunk Group Settings). Click New; the following dialog box appears: Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 506 Mediant 1000B Gateway & E-SBC Configure a Trunk Group according to the parameters described in the table below. Click Apply. Table 23-2: Trunk Group Settings Table Parameter Descriptions Parameter Description General Index Defines an index number for the new table row.
  • Page 507 (after which the other phones stop ringing). This option is applicable only to FXS interfaces.  [10] Select Trunk by Supp-Serv Table = The BRI port/module is selected according to the settings in the Supplementary Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 508 Mediant 1000B Gateway & E-SBC Parameter Description Services table (see Configuring Multi-Line Extensions and Supplementary Services on page 604), allowing the routing of IP-to-Tel calls to specific BRI endpoints according to extension number. This option is applicable only to FXS and BRI interfaces.
  • Page 509 'SIP Group Name' parameter configured in the IP Groups table (see ''Configuring IP Groups'' on page 353). Note:  If the parameter is not configured, the INVITE messages are Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 510 Mediant 1000B Gateway & E-SBC Parameter Description sent to the default Proxy or according to the Tel-to-IP Routing table (see ''Configuring Tel-to-IP Routing Rules'' on page 511).  If the PreferRouteTable parameter is set to 1 (see ''Configuring Proxy and Registration Parameters'' on page 390), the routing rules in the Tel-to-IP Routing table take precedence over the selected Serving IP Group ID.

  • Page 511: Routing

    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. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 512 Mediant 1000B Gateway & E-SBC The device searches the table from top to bottom for the first rule that matches the characteristics of the incoming call. If it finds a matching rule, it sends the call to the IP destination configured for that rule. If it doesn't find a matching rule, it rejects the call.
  • Page 513 The following procedure describes how to configure Tel-to-IP routing rules through the Web interface. You can also configure it through ini file (Prefix) or CLI (configure voip > gateway routing tel2ip-routing). Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 514 Mediant 1000B Gateway & E-SBC  To configure Tel-to-IP routing rules: Open the Tel-to-IP Routing table (Setup menu > Signaling & Media tab > Gateway folder > Routing > Tel > IP Routing). Click New; the following dialog box appears: Figure 24-2: Tel-to-IP Routing Table - Add Dialog Box Configure a routing rule according to the parameters described in the table below.
  • Page 515 Source Trunk Group ID Defines the Trunk Group from where the call is received. src-trunk-group-id To denote any Trunk Group, use the asterisk (*) symbol. By default, no Trunk Group is defined (-1). [PREFIX_SrcTrunkGroupID] Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 516 Mediant 1000B Gateway & E-SBC Parameter Description Source Phone Prefix Defines the prefix and/or suffix of the calling (source) telephone number. You can use special notations for denoting the prefix. src-phone-prefix For example, [100-199](100,101,105) denotes a number that [PREFIX_SourcePrefix] starts with 100 to 199 and ends with 100, 101 or 105. To denote any prefix, use the asterisk (*) symbol (default) or to denote calls without a calling number, use the $ sign.
  • Page 517 (e.g., when DHCP is used), enter IP address 127.0.0.1.  When using domain names, enter the DNS server's IP address or alternatively, configure these names in the Internal DNS table (see ''Configuring the Internal DNS Table'' on page 163). Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 518 Mediant 1000B Gateway & E-SBC Parameter Description IP Profile Assigns an IP Profile to the routing rule in the outgoing direction. The IP Profile allows you to assign various configuration attributes ip-profile-id (e.g., voice coder) per routing rule. To configure IP Profiles, see [PREFIX_ProfileName] ''Configuring IP Profiles'' on page 423.
  • Page 519 LCR (see ''Configuring a Gateway Routing Policy Rule'' on page 525). If LCR is disabled, the device ignores the parameter.  The Routing Policy also determines whether matched routing Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 520: Configuring Ip-To-Tel Routing Rules

    Mediant 1000B Gateway & E-SBC Parameter Description rules that are not assigned Cost Groups are considered as a higher or lower cost route compared to matching routing rules that are assigned Cost Groups. For example, if the 'Default Call Cost' parameter in the Routing Policy is configured to...
  • Page 521 SNMP trap, GWAPP_TRAP_BUSYOUT_LINK notifying of the out- of-service state for the specific FXO line or trunk number. When the FXO port or physical trunk is physically reconnected, this trap is sent notifying of the back-to- service state. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 522 Mediant 1000B Gateway & E-SBC Note: • Instead of using the table for IP-to-Tel routing, you can employ a third-party Routing server to handle the routing decisions. For more information, see ''Centralized Third-Party Routing Server'' on page 279. • You can configure up to three alternative routing rules per "main" routing rule in the table.
  • Page 523 The default is Any (i.e., any SIP Interface). [PstnPrefix_SrcSIPInterfaceName] To configure SIP Interfaces, see Configuring SIP Interfaces on page 345. Note: If the incoming INVITE is received on the specified SIP Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 524 Mediant 1000B Gateway & E-SBC Parameter Description Interface and the SIP Interface associated with the specified IP Group in the 'Source IP Group' parameter (in this table) is different, the incoming SIP call is rejected. If the 'Source IP Group' parameter is not defined, the SIP Interface associated with the default SRD (Index 0) is used.

  • Page 525: Configuring A Gateway Routing Policy Rule

    Enables Least Cost Routing (LCR), and defines default call cost (highest or lowest) and average call duration for Tel-to-IP routing rules that are not assigned LCR Cost Groups. The default call cost determines whether matched routing rules that are not Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 526 Mediant 1000B Gateway & E-SBC assigned a Cost Group are considered as a higher or lower cost route compared to other matching routing rules that are assigned Cost Groups. If you disable LCR, the device ignores the Cost Groups assigned to Tel-to-IP routing rules in the Tel-to-IP Routing table.

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

    The device supports the following methods for checking the connectivity of IP destinations:  Network Connectivity: The device checks the network connectivity of the IP destination configured by the 'Alt Routing Tel to IP Connectivity Method' parameter: • Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 528: Alternative Routing Based On Ip Connectivity

    Mediant 1000B Gateway & E-SBC • SIP OPTIONS: The device sends "keep-alive" SIP OPTIONS messages to the IP destination. If the device receives a SIP 200 OK in response, it considers the destination as available. If the destination does not respond to the OPTIONS message, then it is considered unavailable.
  • Page 529 Tel-to-IP Routing table to re-route the initial Tel-to-IP call. Table 24-6: Alternative Routing based on IP Connectivity Example Destination IP Connectivity IP Destination Rule Used? Phone Prefix Status Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 530: Alternative Routing Based On Sip Responses

    Mediant 1000B Gateway & E-SBC Destination IP Connectivity IP Destination Rule Used? Phone Prefix Status Main Route 10.33.45.68 "No Connectivity" Alternative Route #1 10.33.45.70 "QoS Low" Alternative Route #2 10.33.45.72 "ok" The following procedure describes how to configure alternative Tel-to-IP routing based on IP connectivity.
  • Page 531 If the destination of a routing rule in the Tel-to-IP Routing table is an IP Group, the device routes the call to the IP destination configured for the Proxy Set associated with the IP Group. If the first IP destination of the Proxy Set is unavailable, Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 532 Mediant 1000B Gateway & E-SBC the device attempts to re-route the call to the next proxy destination, and so on until an available IP destination is located. To enable the Proxy Redundancy feature for a Proxy Set, set the IsProxyHotSwap parameter to 1 and the EnableProxyKeepAlive parameter to 1.

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

    3xx responses using one of the following methods:  The device tries each contact sequentially, listed in the Contact headers, until a successful destination is found. If a contact responds with a SIP 486 or 600, the Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 534: Pstn Fallback

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

  • Page 535: 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 567. • For mapping SIP-to-Q.931 and Q.931-to-SIP release causes, see Configuring Release Cause Mapping on page 559. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 536 Mediant 1000B Gateway & 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 > gateway routing alt-route-cause-ip2tel).

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

    Trunk Group ID 1 to destination IP address 10.13.5.67 if conditions mentioned earlier exist. Configure a rule according to the parameters described in the table below. Click Apply, and then reset the device with a save-to-flash for your settings to take effect. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 538: Alternative Routing Upon Isdn Disconnect

    Mediant 1000B Gateway & E-SBC Table 24-10: Forward on Busy Trunk Destination Parameter Descriptions Parameter Description Index Defines an index number for the new table row. [ForwardOnBusyTrunkDest_Index] Note: Each row must be configured with a unique index. Trunk Group ID Defines the Trunk Group ID to which the IP call is destined to.

  • Page 539: Alternative Routing From Fxo To Ip

    SIP Trunk. This is configured using the ini file parameter, TR104FXOSwitchover. For more information on this application, please contact your AudioCodes sales representative. Version 7.2...
  • Page 540 Mediant 1000B Gateway & E-SBC This page is intentionaly left blank. User's Manual Document #: LTRT-27055...

  • Page 541: Manipulation

    Source Phone Number Manipulation for Tel-to-IP Calls (up to 120 entries) • Destination Phone Number Manipulation for Tel-to-IP Calls (up to 120 entries)  IP-to-Tel calls: • Source Phone Number Manipulation for IP-to-Tel Calls (up to 120 entries) Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 542 Mediant 1000B Gateway & E-SBC • Destination Phone Number Manipulation for IP-to-Tel Calls (up to 120 entries) Configuration of number manipulation rules includes two areas:  Match: Defines the matching characteristics of the incoming call (e.g., prefix of destination number).
  • Page 543 Source Phone Number Manipulation for Tel-to-IP Calls table: Table 25-1: Configuration Examples of Source Phone Number Manipulation for Tel-to-IP Calls Parameter Rule 1 Rule 2 Rule 3 Rule 4 Rule 5 [6,7,8] Destination Prefix Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 544 Mediant 1000B Gateway & E-SBC Parameter Rule 1 Rule 2 Rule 3 Rule 4 Rule 5 Source Prefix 1001 123451001# [30-40]x 2001 Stripped Digits From Left Stripped Digits From Right Prefix to Add Suffix to Add Number of Digits to Leave...
  • Page 545 The default is Any (i.e., any IP Group). [_SrcIPGroupID] Note: The parameter is applicable only to the Destination Phone Number Manipulation for IP-to-Tel Calls table and Source Phone Number Manipulation for IP-to-Tel Calls table. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 546 Mediant 1000B Gateway & E-SBC Parameter Description Action Stripped Digits From Left Defines the number of digits to remove from the left of the telephone number prefix. For example, if you enter 3 and the phone number is remove-from-left 5551234, the new phone number is 1234.

  • Page 547: Manipulating Number Prefix

    = location (number of digits counted from the left of the number) of a specific string in the original destination or source number. • l = number of digits that this string includes.  y = prefix to add at the specified location. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 548: Sip Calling Name Manipulations

    Mediant 1000B Gateway & E-SBC For example, assume that you want to manipulate an incoming IP call with destination number "+5492028888888" (i.e., area code "202" and phone number "8888888") to the number "0202158888888". To perform such manipulation, the following configuration is...
  • Page 549 Click New; the following dialog box appears: Figure 25-3: Calling Name Manipulation for IP-to-Tel Calls Table (Example) - Add Dialog Box Configure a manipulation rule according to the parameters described in the table below. Click Apply. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 550 Mediant 1000B Gateway & E-SBC Table 25-4: Calling Name Manipulation Tables Parameter Descriptions Parameter Description General Index Defines an index number for the new table row. [_Index] Note: Each row must be configured with a unique index. Name Defines a descriptive name, which is used when associating the row in other tables.

  • Page 551: Configuring Redirect Number Ip To Tel

    SIP messages. The redirect number manipulation tables include:  Redirect Number IP-to-Tel table: (Applicable only ISDN) Defines IP-to-Tel redirect number manipulation. You can manipulate the value of the received SIP Diversion, Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 552 Mediant 1000B Gateway & E-SBC Resource-Priority, or History-Info headers, which is then added to the Redirecting Number Information Element (IE) in the ISDN Setup message sent to the Tel side. This also includes the reason for the call redirection. ...
  • Page 553 Defines the redirect telephone number prefix. redirect-prefix The default value is the asterisk (*) symbol (i.e., any number prefix). [_RedirectPrefix] Source Trunk Group ID Defines the Trunk Group from where the Tel call is received. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 554 Mediant 1000B Gateway & E-SBC Parameter Description src-trunk-group-id To denote any Trunk Group, leave this field empty. The value -1 indicates that this field is ignored in the rule. [_SrcTrunkGroupID] Note: The parameter is applicable only to the Redirect Number Tel-to- IP table.
  • Page 555 Note: If you configure the parameter to Restricted and the 'AssertedIdMode' parameter to Add P-Asserted-Identity, the From header in the INVITE message includes the following: From: 'anonymous' <sip: anonymous@anonymous.invalid> and 'privacy: id' header. Version 7.2 Mediant 1000B Gateway & E-SBC...

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

    Mediant 1000B Gateway & E-SBC 25.6 Manipulating Redirected and Diverted Numbers for Call Diversion You can configure manipulation rules to manipulate the Diverted-to and Diverting numbers received in the incoming Call Redirection Facility message for call diversion, which is interworked to outgoing SIP 302 responses.

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

    > Manipulation > Phone Contexts). Click New; the following dialog box appears: Figure 25-5: Phone Contexts Table - Add Dialog Box Configure a mapping rule according to the parameters described in the table below. Click Apply. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 558 Mediant 1000B Gateway & E-SBC Note: • You can configure multiple rows with the same NPI/TON or same SIP 'phone- context'. In such a configuration, a Tel-to-IP call uses the first matching rule in the table. • To add the incoming SIP 'phone-context' parameter as a prefix to the outgoing...

  • Page 559: Configuring Release Cause Mapping

    To configure a SIP-to-ISDN release cause mapping rule: Open the Release Cause Mapping from SIP to ISDN table (Setup menu > Signaling & Media tab > Gateway folder > Manipulation > Release Cause SIP > ISDN). Version 7.2 Mediant 1000B Gateway & E-SBC...

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

    Mediant 1000B Gateway & E-SBC Click New; the following dialog box appears: Figure 25-6: Release Cause Mapping from SIP to ISDN Table - Add Dialog Box Configure a mapping rule according to the parameters described in the table below. Click Apply.
  • Page 561 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. Version 7.2 Mediant 1000B Gateway & E-SBC...

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

    Mediant 1000B Gateway & E-SBC 25.8.2 ISDN-to-SIP Release Cause Mapping 25.8.2.1 Configuring ISDN-to-SIP Release Cause Mapping The Release Cause Mapping from ISDN to SIP table lets you configure up to 12 ISDN ITU- T Q.850 release cause code (call failure) to SIP response code mapping rules. The table lets you override the default ISDN-to-SIP release cause mappings, listed in ''Fixed Mapping of ISDN Release Reason to SIP Response'' on page 563.

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

    Exchange Routing Error Bad Request Non-selected user clearing Not found Destination out of order Bad gateway Address incomplete Address incomplete Facility rejected Not implemented Response to status enquiry 501* Not implemented Normal unspecified Temporarily unavailable Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 564 Mediant 1000B Gateway & E-SBC ISDN Release Description Description Reason Response Circuit Congestion Server internal error User Congestion Server internal error No circuit available Service unavailable Network out of order Service unavailable Permanent Frame Mode Connection Service unavailable Out-of-Service Permanent Frame Mode Connection...

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

    ISDN cause code also appears in the Release Cause Mapping ISDN to SIP table (see ''Configuring ISDN-to-SIP Release Cause Mapping'' on page 562), the device maps it to the corresponding SIP response code, which it sends to the IP side. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 566 Mediant 1000B Gateway & E-SBC Note: If the originally received ISDN cause code is configured in both the Release 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;...

  • Page 567: Reason Header

    25.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 Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 568 Mediant 1000B Gateway & E-SBC supports all NPI/TON classifications used in the ETSI ISDN variant, as shown in the table below: Table 25-13: NPI/TON Values for ETSI ISDN Variant Description Unknown [0] Unknown [0] A valid classification, but one that has no information about the numbering plan.

  • Page 569: Configuring Dtmf And Dialing

    998 can never be matched. But when the digit map is 99s|998, then after dialing the first two 9 digits, the device waits another two seconds within which the caller can enter the digit 8. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 570: External Dial Plan File

    Mediant 1000B Gateway & E-SBC Below is an example of a digit map pattern containing eight rules: DigitMapping = 11xS|00[1- 7]xxx|8xxxxxxx|#xxxxxxx|*xx|91xxxxxxxxxx|9011x|xx.T In the example, the rule "00[1-7]xxx" denotes dialed numbers that begin with 00, and then any digit from 1 through 7, followed by three digits (of any number). Once the device receives these digits, it does not wait for additional digits, but starts sending the collected digits (dialed number) immediately.

  • Page 571: Configuring Hook Flash

    (in msec) for detection of a hook-flash event from an FXS interface. Detection is guaranteed for hook-flash periods of at least 60 msec (when configuring the period to 25). The device ignores hook-flash signals lasting a shorter period of time. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 572 Mediant 1000B Gateway & E-SBC ♦ 'Max. Flash-Hook Detection Period' (FlashHookPeriod): Defines the maximum hook-flash period (in msec) for Tel and IP sides for FXS and FXO interfaces. For more information, see the Telprofile_FlashHookPeriod parameter in Configuring Tel Profiles on page 459.

  • Page 573: Configuring Supplementary Services

    (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.2 Mediant 1000B Gateway & E-SBC...
  • Page 574 Mediant 1000B Gateway & 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 575: 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 by the HeldTimeout parameter), the device releases the call. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 576: Consultation Feature

    Mediant 1000B Gateway & 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 577: Consultation Transfer For Qsig Path Replacement

    Q.931 Disconnect messages to the PBX, notifying the PBX that it can disconnect the ISDN calls (of user "A"). This feature is enabled by the QSIGPathReplacementMode parameter. Note: The feature is applicable only to digital interfaces. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 578: Blind Call Transfer

    Mediant 1000B Gateway & E-SBC 27.5.3 Blind Call Transfer Blind call transfer is done (using SIP REFER messages) after a call is established between call parties A and B, and party A decides to immediately transfer the call to C without first speaking to C.

  • Page 579: Enabling Call Forwarding

    624. 27.6.2 Call Forward Reminder Ring The device supports the Call Forward Reminder Ring feature for FXS interfaces whereby the device's FXS endpoint emits a short ring burst when a third-party Application server Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 580 Mediant 1000B Gateway & E-SBC (e.g., softswitch) forwards an incoming call to another destination. The ring is emitted only when the endpoint is in on-hook state. The feature is useful in that it notifies the endpoint user that a call forwarding service is currently being performed.

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

    The special dial tone is used as a result of the device receiving a SIP NOTIFY message from a third-party softswitch providing the call forwarding service with the following SIP Alert-Info header: Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 582: Remote Handling Of Bri Call Forwarding

    Mediant 1000B Gateway & E-SBC Alert-Info: <http://127.0.0.1/Tono-Espec-Invitacion>;lpi- aviso=Desvio-Inmediato This special tone is a stutter dial tone (Tone Type = 15), as defined in the CPT file (see ''Call Progress Tones File'' on page 789). The FXS phone user, connected to the device, activates the call forwarding service by dialing a special number (e.g., *21*xxxxx) and as a result, the device sends a regular SIP...
  • Page 583 INVITE sip:*72100@10.33.8.53;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.33.2.5:5060;branch=z9hG4bKWDSUKUHWFEXQSVOUVJGM From: <sip:400@10.33.2.5;user=phone>;tag=DUOROSXSOYJJLNBFRQTG To: <sip:*72100@10.33.8.53;user=phone> Call-ID: GMNOVQRRXUUCYCQSFAHS@10.33.2.5 CSeq: 1 INVITE Contact: <sip:400@10.33.2.5:5060> Supported: em,100rel,timer,replaces Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUB SCRIBE User-Agent: Sip Message Generator V1.0.0.5 User-to-User: 31323334;pd=4 Content-Type: application/sdp Content-Length: 155 Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 584: Local Handling Of Bri Call Forwarding

    Mediant 1000B Gateway & E-SBC 27.6.6 Local Handling of BRI Call Forwarding You can configure the device to handle BRI call forwarding per BRI extension line, using the Supplementary Services table. Upon receipt of an ISDN Facility message from the BRI phone user, the device retrieves and stores the user's call forwarding information.

  • Page 585: Enabling Call Waiting

    To enable and configure call waiting: Open the Supplementary Services Settings page (Setup menu > Signaling & Media tab > Gateway folder > DTMF & Supplementary > Supplementary Services Settings). Figure 27-7: Configuring Call Waiting Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 586: Message Waiting Indication

    Mediant 1000B Gateway & E-SBC From the 'Enable Call Waiting' drop-down list (EnableCallWaiting), select Enable. Configure call waiting indication and call waiting ringback tones in the Call Progress Tones file (see ''Call Progress Tones File'' on page 789). You can configure up to four call waiting indication tones (see the FirstCallWaitingToneID parameter).
  • Page 587 • Send MWI Interrogation message, but don't use its result. Instead, wait for MWI Activate requests from the PBX. • Send MWI Interrogation message, use its result, and use the MWI Activate requests. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 588: Caller Id

    Mediant 1000B Gateway & E-SBC 27.9 Caller ID This section describes the device's Caller ID support. Note: The Caller ID feature is applicable only to FXS/FXO interfaces. 27.9.1 Enabling Caller ID Generation and Detection on Tel Side The device's Caller ID support depends on the type of analog interface: ...

  • Page 589: Debugging A Caller Id Detection On Fxo

    ID. If the above does not solve the problem, you need to record the caller ID signal (and send it to AudioCodes), as described below.  To record the caller ID signal using the debug recording mechanism: Access the FAE page (by appending "FAE"...

  • Page 590: Three-Way Conferencing

    The device supports the following three-way conference modes:  Conference Managed by External, AudioCodes Conferencing (Media) Server: The conference-initiating INVITE sent by the device uses the ConferenceID concatenated with a unique identifier as the Request-URI. This same Request-URI is set as the Refer-To header value in the REFER messages that are sent to the two remote parties.
  • Page 591 DSP channel from the module. If the device is not installed with any MPM modules and all FXS ports are busy, the three-way conference call cannot be made. The mode is configured by setting the 3WayConferenceMode parameter to 2. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 592 Mediant 1000B Gateway & E-SBC Note: • If the device houses three MPMs or more, no other telephony interface module can be installed in the device. • Instead of using the flash-hook button to establish a three-way conference call, you can dial a user-defined hook-flash code (e.g., "*1"), configured by the HookFlashCode parameter.

  • Page 593: Emergency E911 Phone Number Services

    27.11.1 FXS Device Emulating PSAP using DID Loop-Start Lines The device's FXS interface can be configured to emulate PSAP (using DID loop start lines), according to the Telcordia GR-350-CORE specification. Figure 27-10: FXS Device Emulating PSAP using DID Loop-Start Lines Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 594 Mediant 1000B Gateway & E-SBC The call flow of an E911 call to the PSAP is as follows: The E911 tandem switch seizes the line. The FXS device detects the line seize, and then generates a wink signal (nominal 250 msec).
  • Page 595 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.2 Mediant 1000B Gateway & E-SBC...

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

    Mediant 1000B Gateway & E-SBC 27.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 597 Number (ANI) MF dialed "KPnnnnnnnnST" "nnnnnnnn" None "KPnnnnnnnnnnnnSTP" "nnnnnnnnnnnn" "KPnnnnnnnnnnnnSTKPmmmmmmmmmmST" "nnnnnnnnnnnn" "mmmmmmmmmm" (pANI) None "KPnnSTP" "nn" MF dialed "KPnST" "n" For example: "From: <sip:8>@xyz.com>" generates device MF spill of KP 8 ST Table notes: Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 598 Mediant 1000B Gateway & E-SBC  For all other cases, a SIP 484 response is sent.  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 599: Pre-Empting Existing Calls For E911 Ip-To-Tel Calls

    (Optional) Configure emergency telephone numbers (e.g., 911). Open the Priority & Emergency page (Setup menu > Signaling & Media tab > SIP Definitions folder > Priority Emergency), then 'Emergency Number' fields (EmergencyNumbers), configure the emergency numbers: Figure 27-13: Emergency Numbers Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 600: Multilevel Precedence And Preemption

    Mediant 1000B Gateway & E-SBC The device identifies the IP-to-Tel call as an emergency call if the destination number matches one of these configured emergency numbers. For E911, you must configure the parameter to "911". Note: • The device also identifies emergency calls if the Priority header of the incoming SIP INVITE message contains the “emergency”...
  • Page 601 Department of Defense (DoD) Unified Capabilities (UC) Requirements (UCR 2008, Changes 3) document, as shown below: Table 27-4: NI Digits in ISDN Precedence Level IE Network Domain in SIP Resource-Priority Header 0000 0001 Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 602 Mediant 1000B Gateway & E-SBC Level IE Network Domain in SIP Resource-Priority Header 0002 0003 nato Note: • If the received ISDN message contains NI digits that are not listed in the translation table, the device sets the network-domain to "uc" in the outgoing SIP message.

  • Page 603: Mlpp Preemption Events In Sip Reason Header

    The softswitch sends the device a SIP 488 (Not Acceptable Here) response code with this Reason cause code. The device initiates the release procedures for the B-channel associated with the call request and maps the preemption cause to ISDN Cause = #8 ‘Preemption’. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 604: Precedence Ring Tone

    Mediant 1000B Gateway & E-SBC The device deactivates any user signaling (e.g., ringback tone) and when the call is terminated, it sends a SIP ACK message to the softswitch. 27.12.2 Precedence Ring Tone You can assign a ring tone that is defined in the CPT file to be played when a precedence call is received from the IP side.
  • Page 605 (configure voip > gateway digital isdn-supp-serv).  To configure endpoint supplementary services: Open the Supplementary Services table (Setup menu > Signaling & Media tab > Gateway folder > DTMF & Supplementary > Supplementary Services). Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 606 Mediant 1000B Gateway & E-SBC Click New; the following dialog box appears: Figure 27-14: Supplementary Services Table - Add Dialog Box Configure a supplementary service according to the parameters described in the table below. Click Apply. You can also register and un-register an endpoint configured in the table: ...
  • Page 607 The parameter is applicable only to BRI interfaces.  To enable BRI call forwarding services, see the BRICallForwardHandling parameter. For more information on configuring local handling of BRI call forwarding, see Local Handling of BRI Call Forwarding on page 584. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 608: Detecting Collect Calls

    Mediant 1000B Gateway & E-SBC Parameter Description No Reply Time Defines the timeout (in seconds) that if the BRI extension does not answer before it expires, the device forwards the call to the no-reply-time phone number as defined by the 'CFNR Phone Number' [ISDNSuppServ_NoReplyTime] parameter (see above).

  • Page 609: Advice Of Charge Services For Euro Isdn

    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 610: Configuring Charge Codes

    Mediant 1000B Gateway & E-SBC 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 1201.
  • Page 611 Note: Each row must be configured with a unique name. End Time (1 - 4) Defines the end of the time period in a 24 hour format, hh. For example, "04" denotes 4 A.M. end-time-<1-4> Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 612: Configuring Voice Mail

    Mediant 1000B Gateway & E-SBC Parameter Description [ChargeCode_EndTime<1-4>] Note:  The first time period always starts at midnight (00).  It is mandatory that the last time period of each rule end at midnight (00). This prevents undefined time frames in a day.
  • Page 613 • 'Forward on No Answer Digit Pattern Internal' (DigitPatternForwardOnNoAnswer): Defines the digit pattern to indicate 'call forward on no answer' when the original call is received from an internal extension. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 614 Mediant 1000B Gateway & E-SBC • 'Forward on Do Not Disturb Digit Pattern Internal' (DigitPatternForwardOnDND): Defines the digit pattern to indicate 'call forward on do not disturb' when the original call is received from an internal extension. • 'Forward on No Reason Digit Pattern Internal' (DigitPatternForwardNoReason): Defines the digit pattern to indicate 'call forward with no reason' when the original call is received from an internal extension.

  • Page 615: Converting Accented Characters From Ip To Tel

    Figure 27-18: Char Conversion Table - Add Dialog Box The figure above shows a configuration example where ä is converted to ae. Configure a Character Conversion rule according to the parameters described in the table below. Click Apply. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 616 Mediant 1000B Gateway & E-SBC Table 27-8: Char Conversion Table Parameter Descriptions Parameter Description Index Defines an index number for the new table row. [CharConversion_Index] Note: Each row must be configured with a unique index. Character Name Defines a descriptive name, which is used when associating the row in other tables.

  • Page 617: Analog Gateway

    To configure keypad sequences: Open the Keypad Features page (Setup menu > Signaling & Media tab > Gateway folder > Analog Gateway > Keypad Features). Figure 28-1: Configuring Phone Key Sequences to Activate Various Services Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 618: Configuring Metering Tones

    Mediant 1000B Gateway & E-SBC Configure the keypad features as required. Click Apply. 28.2 Configuring Metering Tones The FXS interfaces can generate 12/16 KHz metering pulses toward the Tel side (e.g., for connection to a pay phone or private meter). Tariff pulse rate is according to the device's Charge Codes table.

  • Page 619: Configuring Authentication

    For all endpoints: Open the Proxy & Registration page (Setup menu > Signaling & Media tab > SIP Definitions folder > Proxy & Registration), and then configure the 'Authentication Mode' (AuthenticationMode) parameter to Per Endpoint: Figure 28-4: Enabling Authentication per Endpoint Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 620 Mediant 1000B Gateway & E-SBC • Endpoints per Trunk Group: Open the Trunk Group Settings table (see ''Configuring Trunk Group Settings'' on page 505), and then for the required Trunk Group ID, configure the 'Registration Mode' parameter to Per Endpoint (TrunkGroupSettings_RegistrationMode).

  • Page 621: Configuring Automatic Dialing

    [TargetOfChannel_Module] Port (Read-only) Displays the port number. port [TargetOfChannel_Port] Port Type (Read-only) Displays the port type (FXS or FXO). [TargetOfChannel_PortType] Destination Phone Number Defines the destination telephone number to automatically dial. dst-number Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 622: Configuring Caller Display Information

    Mediant 1000B Gateway & E-SBC Parameter Description [TargetOfChannel_Destination] Auto Dial Status Enables automatic dialing.  auto-dial-status [0] Disable = Automatic dialing for the specific port is disabled. [TargetOfChannel_Type]  [1] Enable = (Default) Automatic dialing is enabled and the phone number configured in the 'Destination Phone...
  • Page 623 "Anonymous", Caller ID is restricted and the settings of the 'Presentation' parameter is ignored. Presentation Enables the sending of the caller ID string.  presentation [0] Allowed = The caller ID string is sent when a Tel-to-IP call is made. [CallerDisplayInfo_IsCidRestricted] Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 624: Configuring Call Forward

    Mediant 1000B Gateway & E-SBC Parameter Description  [1] Restricted = The caller ID string is not sent. The Caller ID is sent to the remote side using only the SIP P-Asserted- Identity or P-Preferred-Identity headers, according to the AssertedIdMode parameter.
  • Page 625 'No Reply Time' field.  [5] Don't Disturb = Immediately reject incoming calls. Call Forward Forward Destination Defines the telephone number or URI (<number>@<IP address>) to where the call is forwarded. destination Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 626: Configuring Caller Id Permissions

    Mediant 1000B Gateway & E-SBC Parameter Description [FwdInfo_Destination] Note: If the parameter is configured with only a telephone number and a Proxy isn't used, this forwarded-to phone number must be specified in the Tel-to-IP Routing table (see ''Configuring Tel-to-IP Routing Rules'' on page 511).

  • Page 627: Configuring Call Waiting

    The section is applicable only to FXS interfaces. The following procedure describes how to configure call waiting per port through the Web interface. You can also configure it through ini file (CallWaitingPerPort) or CLI (configure voip > gateway analog call-waiting). Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 628: Rejecting Anonymous Calls

    Mediant 1000B Gateway & E-SBC  To enable call waiting per port: Open the Call Waiting table (Setup menu > Signaling & Media tab > Gateway folder > Analog Gateway > Call Waiting). Select the row corresponding to the port that you want to configure, and then click Edit;...

  • Page 629: Configuring Fxs Distinctive Ringing And Call Waiting Tones Per Source/Destination Number

    4 when a call is received from a calling (source) number with prefix 2. Configure distinctive ringing and call waiting tones per port according to the parameters described in the table below. Click Apply. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 630: Fxs/Fxo Coefficient Types

    Mediant 1000B Gateway & E-SBC Table 28-7: Tone index Table Parameter Description Parameter Description Index Defines the table index entry. Up to 50 entries can be defined. FXS Port First Defines the first port in the FXS port range. fxs-port-first...

  • Page 631: Fxo Operating Modes

    Waiting for dial tone (see ''Two-Stage Dialing'' on page 633) • Time to wait before dialing • Answer supervision  Two-stage dialing (see ''Two-Stage Dialing'' on page 633)  Dialing time: DID wink (see ''DID Wink'' on page 633) Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 632: One-Stage Dialing

    Mediant 1000B Gateway & E-SBC 28.13.1.1 One-Stage Dialing One-stage dialing is when the FXO device receives an IP-to-Tel call, off-hooks the PBX line connected to the telephone, and then immediately dials the destination telephone number. In other words, the IP caller doesn't dial the PSTN number upon hearing a dial tone.

  • Page 633: Two-Stage Dialing

    DID wink enables the originating end to seize the line by going off-hook. It waits for acknowledgment from the other end before sending digits. This serves as an integrity check that identifies a malfunctioning trunk and allows the network to send a re-order tone to the calling party. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 634: Fxo Operations For Tel-To-Ip Calls

    Mediant 1000B Gateway & E-SBC The "start dial" signal is a wink from the PBX to the FXO device. The FXO then sends the last four to five DTMF digits of the called number. The PBX uses these digits to complete the routing directly to an internal station (telephone or equivalent).

  • Page 635: Collecting Digits Mode

    Refer-To header), and then drops the line (on-hook). Note that the time between flash to dial is according to the WaitForDialTime parameter. • PBX performs the transfer internally  Hold / Transfer toward the IP side: The FXO device doesn't initiate hold / transfer as Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 636: Call Termination On Fxo Devices

    Mediant 1000B Gateway & E-SBC a response to input from the Tel side. If the FXO receives a REFER request (with or without replaces), it generates a new INVITE according to the Refer-To header. 28.13.3 Call Termination on FXO Devices This section describes the device's call termination capabilities for its FXO interfaces: ...

  • Page 637: Call Termination Before Call Establishment

    To call a remote office worker, a PBX user or a PSTN caller simply dials the PBX extension that is mapped to the remote FXS port. Version 7.2 Mediant 1000B Gateway & E-SBC...

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

    Mediant 1000B Gateway & E-SBC This section provides an example on how to implement a remote telephone extension through the IP network, using FXO andFXS interfaces. In this configuration, the FXO device routes calls received from the PBX to the ‘Remote PBX Extension’ connected to the FXS device.

  • Page 639: Dialing From Pbx Line Or Pstn

    ID to the relevant port for display. The remote extension connected to the FXS device can toggle between calls using the Hook Flash button. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 640: Fxs Gateway Configuration

    Mediant 1000B Gateway & E-SBC 28.14.5 FXS Gateway Configuration The following procedure describes how to configure the FXS interface (at the 'remote PBX extension').  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 FXS ports.

  • Page 641: Fxo Gateway Configuration

    IP address of the FXS device (10.1.10.3) in the field ‘IP Address’. Figure 28-18: FXO Tel-to-IP Routing Configuration In the FXO Settings page (see ''Configuring FXO Parameters'' on page 618), set the parameter ‘Dialing Mode’ to Two Stages (IsTwoStageDial = 1). Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 642 Mediant 1000B Gateway & E-SBC This page is intentinally left blank. User's Manual Document #: LTRT-27055...

  • Page 643: Session Border Controller Application

    Part VI Session Border Controller Application...

  • Page 645: Sbc Overview

    (B2BUA) leg routing: • Strips all incoming SIP Via header fields and creates a new Via value for the outgoing message. • Each leg has its own Route/Record Route set. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 646: B2Bua And Stateful Proxy Operating Modes

    Mediant 1000B Gateway & E-SBC • 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 647 In some setups, the SIP client authenticates using a hash that is performed on one or 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 Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 648 Mediant 1000B Gateway & E-SBC the Call-ID header remains unchanged between the inbound and outbound SBC legs. As B2BUA changes the Call-ID header, such debugging requirements would fail. The operating mode can be configured per the following configuration entities: ...

  • Page 649: Call Processing Of Sip Dialog Requests

    The device obtains the source and destination URLs from certain SIP headers. Once the 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. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 650 Mediant 1000B Gateway & E-SBC • All SIP requests (e.g., INVITE) except REGISTER: ♦ 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 651: User Registration

    REGISTER messages. For example, you can limit REGISTER requests from a specific IP Group or SRD. Note that this applies only to concurrent REGISTER dialogs and not concurrent registrations in the device's registration database. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 652: Classification And Routing Of Registered Users

    Mediant 1000B Gateway & E-SBC 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 between an AOR (obtained from the SIP To header), optional additional AORs, and one or more contacts (obtained from the SIP Contact headers).

  • Page 653: 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.2 Mediant 1000B Gateway & E-SBC...

  • Page 654: Registration Restriction Control

    Mediant 1000B Gateway & 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 655: Media Anchoring

    The Media Realm assigned to the leg's IP Group (in the IP Groups 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.2 Mediant 1000B Gateway & E-SBC...

  • Page 656: Direct Media

    Mediant 1000B Gateway & E-SBC Interfaces 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 29-3: SDP Offer/Answer Example 29.5.2 Direct Media...
  • Page 657 Microsoft Server (direct media is required in the Skype for Business environment). For more information, see ''Configuring IP Groups'' on page 353. IP Groups of the endpoints use the same SIP Interface and the SIP Interface's 'SBC Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 658: Restricting Audio Coders

    Mediant 1000B Gateway & 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 659: Coder Transcoding

    Since this coder was not included in the original incoming SDP offer from the LAN IP phone, the device performs G.729-G.711 transcoding between the inbound and outbound legs. Figure 29-5: Transcoding using Extended Coders (Example) Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 660 Mediant 1000B Gateway & E-SBC Note: • If you assign a SIP entity an Allowed Audio Coders Group for coder restriction (allowed coders) and a Coders Group for extension coders, the allowed coders take precedence over the 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.
  • Page 661 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. m=audio 6050 RTP/AVP 18 96 96 a=rtpmap:18 G729/8000 Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 662: Transcoding Mode

    Mediant 1000B Gateway & E-SBC a=rtpmap:96 G726-32/8000 a=fmtp:4 annexa=no a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-15 a=ptime:20 a=sendrecv The device includes only the G.729 and G.726 coders in the SDP offer that it sends from the outgoing leg to the outbound SIP entity. The G.729 is listed first as the Allowed Audio Coders Group for coder restriction takes precedence over the extension coder.

  • Page 663: 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. DSP resources are not required for RTP-SRTP transcoding. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 664: Multiple Rtp Media Streams Per Call Session

    Mediant 1000B Gateway & E-SBC 29.5.8 Multiple RTP Media Streams per Call Session The device's SBC application supports multiple RTP media streams per SBC call session. It supports the negotiation of up to five media streams ('m=' line) in the SDP offer/answer model per session.

  • Page 665: Interworking Rtcp Attribute In Sdp

    (i.e., after 200 OK) and within a user-defined interval. If detected, it can then handle the subsequent fax renegotiation by sending re-INVITE messages to both SIP entities (originating and terminating faxes). For more information, see the parameter in ''Configuring IP Profiles'' on page 423. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 666: Limiting Sbc Call Duration

    Mediant 1000B Gateway & E-SBC Note: The voice-related coder configuration (Allowed and Extension coders) is independent of the fax-related coder configuration, with the exception of the G.711 coder. If the G.711 coder is restricted by the Allowed Audio Coders Groups table, it is not used for fax processing even if it is listed in the Coder Groups table for faxes.

  • Page 667: User Authentication Based On Radius

    SIP method. The configuration method for assigning specific SIP message handling modes to UAs, includes configuring an IP Profile with the required interworking mode, and then assigning the IP Profile to the relevant IP Group. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 668: Interworking Sip 3Xx Redirect Responses

    Mediant 1000B Gateway & E-SBC This section describes some of the device's support for handling SIP methods to ensure interoperability. 29.9.1 Interworking SIP 3xx Redirect Responses The device supports interworking of SIP 3xx redirect responses. By default, the device's handling of SIP 3xx responses is to send the Contact header unchanged. However, some SIP UAs may support different versions of the SIP 3xx standard while others may not even support SIP 3xx.

  • Page 669: 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.2 Mediant 1000B Gateway & E-SBC...

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

    Mediant 1000B Gateway & E-SBC 29.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. Therefore, mapping between these headers is crucial for preserving the information in the SIP dialog regarding how and why (e.g., call...

  • Page 671: Interworking Sip Prack Messages

    29.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- Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 672 Mediant 1000B Gateway & E-SBC answer transaction completes. The offer-answer options can be included in the following SIP messages:  Offer in first INVITE, answer on 180, and no or same answer in the 200 OK  Offer in first INVITE, answer on 180, and a different answer in the 200 OK (not standard) ...
  • Page 673 User's Manual 29. SBC Overview Figure 29-8: SBC Early Media RTP 18x without SDP Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 674: Interworking Sip Re-Invite Messages

    Mediant 1000B Gateway & E-SBC Figure 29-9: Early Media RTP - SIP 18x with SDP 29.9.7 Interworking SIP re-INVITE Messages The device supports interworking of SIP 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 675: Interworking Sip Re-Invite To Update

    Interworking generation of held tone where the device generates the tone to the held party instead of the call hold initiator. This is configured by the IP Profile parameter, 'SBC Reliable Held Tone Source'. To configure IP Profiles, see ''Configuring IP Profiles'' on page 423. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 676: Interworking Sip Via Headers

    Mediant 1000B Gateway & E-SBC 29.9.12 Interworking SIP Via Headers The device supports the interworking of SIP Via headers between SIP entities. For the outgoing message sent to a SIP entity, the device can remove or retain all the Via headers received in the incoming SIP request from the other side.

  • Page 677: Enabling The Sbc Application

    Open the Applications Enabling page (Setup menu > Signaling & Media tab > Core Entities folder > Applications Enabling). From the 'SBC Application' drop-down list, select Enable: Click Apply, and then reset the device with a save-to-flash for your settings to take effect. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 678 Mediant 1000B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-27055...

  • Page 679: 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 1273).
  • Page 680 Mediant 1000B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-27055...

  • Page 681: Configuring General Sbc Settings

    XML body. Below is an example of an XML body where the call-id, tags, and URIs have been replaced by the device: <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="10" state="partial" entity="sip:alice@example.com"> <dialog id="zxcvbnm3" call-id="67402270@10.132.10.150" local-tag="1c137249965" Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 682 Mediant 1000B Gateway & E-SBC remote-tag="CCDORRTDRKIKWFVBRWYM" direction="initiator"> <state event="replaced">terminated</state> </dialog> <dialog id="sfhjsjk12" call-id="67402270@10.132.10.150" local-tag="1c137249965" remote-tag="CCDORRTDRKIKWFVBRWYM" direction="receiver"> <state reason="replaced">confirmed</state> <replaces call-id="67402270@10.132.10.150" local-tag="1c137249965" remote-tag="CCDORRTDRKIKWFVBRWYM"/> <referred-by> sip:bob-is-not-here@vm.example.net </referred-by> <local> <identity display="Jason Forster"> sip:jforsters@home.net </identity> <target uri="sip:alice@pc33.example.com"> <param pname="+sip.rendering" pval="yes"/> </target> </local> <remote> <identity display="Cathy Jones">...

  • Page 683: 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.2 Mediant 1000B Gateway & E-SBC...
  • Page 684 Mediant 1000B Gateway & E-SBC routing rule exists, 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 685 Reserved call capacity must be less than the maximum capacity (limit) configured for the CAC rule (see the 'Limit' parameter below).  The total reserved call capacity configured for all CAC rules must be within the device's total call capacity support. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 686 Mediant 1000B Gateway & 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 687: Routing Sbc

     To configure the action for unclassified calls: Open the SBC General Settings (Setup menu > Signaling & Media tab > SBC folder > SBC General Settings). Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 688 Mediant 1000B Gateway & E-SBC From the 'Unclassified Calls' drop-down list, select Reject to reject unclassified calls or Allow to accept unclassified calls: Figure 34-1: Configuring Action for Classification Failure Click Apply. If you configure the parameter to Allow, the incoming SIP dialog is assigned to an IP Group as follows: The device determines on which SIP listening port (e.g., 5061) the incoming SIP...
  • Page 689 Proxy Set feature). • The device saves incoming SIP REGISTER messages in its registration database. If the REGISTER message is received from a User-type IP Group, the device sends the message to the configured destination. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 690 Mediant 1000B Gateway & E-SBC The flowchart below illustrates the classification process: Figure 34-2: Classification Process (Identifying IP Group or Rejecting Call) The following procedure describes how to configure Classification rules through the Web interface. You can also configure it through ini file (Classification) or CLI (configure voip >...
  • Page 691 Source SIP Interface Assigns a SIP Interface to the rule as a matching characteristic for the incoming SIP dialog. src-sip-interface-name The default is Any (i.e., all SIP Interfaces belonging to the SRD [Classification_SrcSIPInterfa Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 692 Mediant 1000B Gateway & E-SBC Parameter Description ceName] assigned to the rule). Note: The SIP Interface must belong to the SRD assigned to the rule (see the 'SRD' parameter in the table). Source IP Address Defines a source IP address as a matching characteristic for the incoming SIP dialog.
  • Page 693 To configure IP Groups, see ''Configuring IP Groups'' on page 353. ame] Note: The IP Group must be associated with the assigned SRD (see the 'SRD' parameter in the table). IP Profile Assigns an IP Profile to the matched incoming SIP dialog. Version 7.2 Mediant 1000B Gateway & E-SBC...

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

    Mediant 1000B Gateway & E-SBC Parameter Description ip-profile-id The assigned IP Profile overrides the IP Profile assigned to the IP Group (in the IP Groups table) to which the SIP dialog is classified. [Classification_IpProfileNam Therefore, assigning an IP Profile during classification allows you to assign different IP Profiles to specific users (calls) that belong to the same IP Group (User or Server type).

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

    Request-URI of incoming SIP dialog-initiating requests.  Any registered user in the registration database. If the Request-URI of the incoming INVITE exists in the database, the call is sent to the corresponding contact address specified in the database. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 696 Mediant 1000B Gateway & E-SBC  According to result of an ENUM query.  Hunt Group - used for call survivability of call centers (see ''Configuring Call Survivability for Call Centers'' on page 761).  According to result of LDAP query (for more information on LDAP-based routing, see ''Routing Based on LDAP Active Directory Queries'' on page 239).
  • Page 697 (i.e., first-matched rule) is used. If a selected route is unavailable, the device uses the next least-cost routing rule. However, even if a matched rule is not assigned a Cost Group, the device Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 698 Mediant 1000B Gateway & E-SBC can select it as the preferred route over other matched routing rules that are assigned Cost Groups, according to the default LCR settings configured for the assigned Routing Policy (see ''Configuring SBC Routing Policy Rules'' on page 715).
  • Page 699 Defines an index number for the new table row. [IP2IPRouting_Index] Note: Each row must be configured with a unique index. Name Defines a descriptive name, which is used when associating the row in other tables. route-name Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 700 Mediant 1000B Gateway & E-SBC Parameter Description [IP2IPRouting_RouteName] The valid value is a string of up to 40 characters. By default, no value is defined. Alternative Route Options Determines whether this routing rule is the main routing rule or an alternative routing rule (to the rule defined directly above it in alt-route-options the table).
  • Page 701 The default is the asterisk (*) symbol (i.e., any prefix). If this rule is not required, leave this field empty. Note: If you need to route calls of many different destination URI user names to the same destination, you can use tags (see Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 702 Mediant 1000B Gateway & E-SBC Parameter Description 'Source Tags' parameter below) instead of this parameter. Destination Host Defines the host part of the incoming SIP dialog’s destination URI (usually the Request-URI). dst-host The default is the asterisk (*) symbol (i.e., any destination host).
  • Page 703 ; called prefix 200 is routed to destination 10.33.8.52 201,0,10.33.8.52 300,0,itsp.com ; called prefix 300 is routed to destination itsp.com Once the Dial Plan is defined, you need to assign it (0 to 7) Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 704 Mediant 1000B Gateway & E-SBC Parameter Description to the routing rule as the destination in the 'Destination Address' parameter, where "0" denotes [PLAN1], "1" denotes [PLAN2], and so on.  [7] LDAP = LDAP-based routing. Make sure that the Routing...
  • Page 705 Dest Address [1] or ENUM [3]; otherwise, the parameter is ignored.  When using domain names, enter a DNS server IP address or alternatively, define these names in the Internal DNS table Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 706 Mediant 1000B Gateway & E-SBC Parameter Description (see ''Configuring the Internal SRV Table'' on page 164).  To terminate SIP OPTIONS messages at the device (i.e., to handle them locally), set the parameter to "internal". Destination Port Defines the destination port to where the call is sent.
  • Page 707 Redirect (response=’300’, contact=’sip:102@host’)  The device redirects the call from the sender to a SIP Recording Server (SRS): Redirect(response='302',contact='sip:'+header .to.url.user+'@siprecording.com') Note:  The parameter can be used for normal and alternative Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 708: Configuring Rerouting Of Calls To Fax Destinations

    Mediant 1000B Gateway & E-SBC Parameter Description routing.  The response code for redirect messages can only be 3xx. 34.2.1 Configuring Rerouting of Calls to Fax Destinations You can configure the device to reroute incoming SBC calls identified as fax calls to a new IP destination.

  • Page 709: Configuring Specific Udp Ports Using Tag-Based Routing

    UDP port on which the message was received. On the leg interfacing with the IP PBXs, the device uses the same local UDP port (e.g., 5060) for all IP PBXs (send and receive). Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 710 Mediant 1000B Gateway & E-SBC To configure this feature, you need to configure the SIP Interface of the proxy server with a special UDP port range, and use tag-based routing with Call Setup Rules to specify the exact UDP port you want assigned to each SIP entity (IP PBX), from the SIP Interface port range.
  • Page 711 Uses the value of the "Type" tag name, configured in the IP Group's 'Tags' parameter, as the source tag: General Index Rule Set ID Action Action Subject srctags.Type Action Type Modify Action Value param.ipg.src.tags.Type Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 712 Mediant 1000B Gateway & E-SBC • If the source tag name "Type" equals "PBX" (i.e., SIP message from an IP Group belonging to one of the IP PBXs), then use the value of the "Port" tag name, configured in the 'Tags' parameter of the classified IP Group, as the local UDP...

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

    SIP entity. This is 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 Alternative Routing Reasons table and 3) configuring an alternative routing rule. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 714 Mediant 1000B Gateway & E-SBC The device also generates the response code when it rejects a call based on Quality of Service rules due to crossed Voice Quality and Bandwidth thresholds (see ''Configuring Quality of Service Rules'' on page 324). If the response code is configured in the table and the device rejects a call due to threshold crossing, it searches in the IP-to-IP Routing table for an alternative routing rule.

  • Page 715: Configuring Sbc Routing Policy Rules

    Routing Policy with newly added configuration entities that can be associated with the Routing Policy (as mentioned later in this section, except for Classification rules). This facilitates configuration, eliminating the need to handle the Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 716 Mediant 1000B Gateway & E-SBC Routing Policy configuration entity (except if you need to enable LCR and/or assign an LDAP server to the Routing Policy). In such a setup, where only one Routing Policy is used, single routing and manipulation tables are employed for all SRDs.
  • Page 717 > Routing > Routing Policies). Click New; the following dialog box appears: Figure 34-7: Routing Policies Table - Add Dialog Box Configure the Routing Policy rule according to the parameters described in the table below. Click Apply. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 718 Mediant 1000B Gateway & E-SBC Table 34-4: Routing Policies table Parameter Descriptions Parameter Description General Index Defines an index number for the new table row. Note: Each row must be configured with a unique index. Name Defines a descriptive name, which is used when associating the row in other tables.

  • Page 719: Configuring Ip Group Sets

    IP Group Set.  Child table: IP Group Set Member table, which assigns IP Groups to IP Group Sets. You can assign up to five IP Groups per IP Group Set. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 720 Mediant 1000B Gateway & E-SBC The following procedure describes how to configure IP Group Sets through the Web interface. You can also configure it through other management platforms:  IP Group Set Table: ini file (IPGroupSet) or CLI (configure voip > sbc routing ip- group-set) ...
  • Page 721 Figure 34-9: IP Group Set Member Table - Dialog Box Configure IP Group Set members according to the parameters described in the table below. Click Apply, and then save your settings to flash memory. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 722 Mediant 1000B Gateway & E-SBC IP Group Set Member 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. index [IPGroupSetMember_IPGroupSe tMemberIndex] IP Group Assigns an IP Group to the IP Group Set.

  • Page 723: Sbc Manipulations

    IP Groups respectively (if any, in the IP Groups table). 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 Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 724 Mediant 1000B Gateway & E-SBC CSeq: 1 INVITE 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...

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

    Routing Policy ("Default_SBCRoutingPolicy"), when only one Routing Policy is required, the device automatically assigns the default Routing Policy to the routing rule. If you are implementing LDAP-based routing (with or without Call Setup Rules) and/or Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 726 Mediant 1000B Gateway & E-SBC Least Cost Routing (LCR), you need to configure these settings for the Routing Policy (regardless of the number of Routing Policies employed). For more information on Routing Policies, see ''Configuring SBC Routing Policy Rules'' on page 715.
  • Page 727 [2] REGISTER = Only REGISTER messages.  [3] SUBSCRIBE = Only SUBSCRIBE messages.  [4] INVITE and REGISTER = All SIP messages except SUBSCRIBE.  [5] INVITE and SUBSCRIBE = All SIP messages except REGISTER. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 728 Mediant 1000B Gateway & E-SBC Parameter Description Source IP Group Defines the IP Group from where the incoming INVITE is CLI: src-ip-group-name received. [IPInboundManipulation_SrcIp The default is Any (i.e., any IP Group). GroupName] Source Username Prefix Defines the prefix of the source SIP URI user name (usually in CLI: src-user-name-prefix the From header).

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

    IP Groups, respectively. The following procedure describes how to configure Outbound Manipulations rules through the Web interface. You can also configure it through ini file (IPOutboundManipulation) or CLI (configure voip > sbc manipulation ip-outbound-manipulation). Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 730 Mediant 1000B Gateway & E-SBC  To configure Outbound Manipulation rules: Open the Outbound Manipulations table (Setup menu > Signaling & Media tab > SBC folder > Manipulation > Outbound Manipulations). Click New; the following dialog box appears: Figure 35-3: Outbound Manipulations Table- Add Dialog Box Configure an Outbound Manipulation rule according to the parameters described in the table below.
  • Page 731 The default value is the asterisk (*) symbol (i.e., any source [IPOutboundManipulation_Src username prefix). The prefix can be a single digit or a range of digits. UsernamePrefix] For available notations, see ''Dialing Plan Notation for Routing and Manipulation'' on page 999. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 732 Mediant 1000B Gateway & E-SBC Parameter Description Note: If you need to manipulate calls of many different source URI user names, you can use tags (see 'Source Tags' parameter below) instead of this parameter. Source Host Defines the source SIP URI host name - full name, typically in the From header.
  • Page 733 Defines the number or string to add at the end of the manipulated item. For example, if you enter '01' and the user name is "john", the suffix-to-add new user name is "john01". [IPOutboundManipulation_Suf If you set the 'Manipulated Item' parameter to Source URI or Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 734 Mediant 1000B Gateway & E-SBC Parameter Description fix2Add] Destination URI, you can configure the parameter to a string of up 49 characters. If you set the 'Manipulated Item' parameter to Calling Name, you can configure the parameter to a string of up 36 characters.

  • Page 735: Configuring Dial Plans

    Dial Plan for a rule that matches the destination number. If matching dial plan rules are found, the tags configured for these rules are used in the routing and/or manipulation processes as source and/or destination tags. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 736 Mediant 1000B Gateway & E-SBC Note: When tags are used in the IP-to-IP Routing table to determine destination IP Groups (i.e., 'Destination Type' parameter configured to Destination Tag), the device searches the Dial Plan for a matching destination (called) prefix number only.
  • Page 737  For incoming calls with prefix number "53124", the rule with tag C is chosen (longest suffix - C has three digits, B two digits and A one digit): Prefix 53([2-4]) 53([01-99]) 53([001-999]) Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 738 Mediant 1000B Gateway & E-SBC  For incoming calls with prefix number "53124", the rule with tag B is chosen (suffix is more specific for digit "4"): Prefix 53([2-4]) 53(4),B Dial Plans are configured using two tables with parent-child type relationship: ...
  • Page 739 #: (Pound or hash symbol) When used at the end of the prefix it denotes the end of the number. For example, "54324#" represents a 5-digit number that starts with the digits 54324. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 740: Importing And Exporting Dial Plans

    Mediant 1000B Gateway & E-SBC Parameter Description  .: (Period) Denotes any letter or digit.  [n-m], (n-m), or ([n1-m1,n2-m2,a,b,c,n3-m3]): Represents a mixed notation of single numbers and multiple ranges. To represent the prefix, the notation is enclosed by square brackets [...];...
  • Page 741 The following procedures describe how to import a Dial Plan file.  To overwrite all existing Dial Plans with imported Dial Plan file:  Web interface (from a local folder): Open the Dial Plan table. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 742 Mediant 1000B Gateway & E-SBC From the 'Action' drop-down menu, choose Import; the following dialog box appears: Figure 36-5: Importing Dial Plan Rules for Specific Dial Plan Use the Browse button to select the Dial Plan file on your PC, and then click OK.

  • Page 743: Creating Dial Plan Files

     Prefix: Source or destination number prefix.  Tag: Result of the user categorization and can be used as matching characteristics for routing and outbound manipulation For example: DialPlanName,Name,Prefix,Tag PLAN1,rule_100,5511361xx,A PLAN1,rule_101,551136184[4000-9999]#,B MyDialPlan,My_rule_200,5511361840000#,itsp_1 MyDialPlan,My_rule_201,66666#,itsp_2 Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 744: Using Dial Plan Tags For Ip-To-Ip Routing

    Mediant 1000B Gateway & E-SBC 36.3 Using Dial Plan Tags for IP-to-IP Routing You can use Dial Plan tags with IP-to-IP Routing rules in the IP-to-IP Routing table, where tags can be used for the following:  Matching routing rules by source and/or destination prefix numbers (see Using Dial Plan Tags for Matching Routing Rules on page 744) ...

  • Page 745: Using Dial Plan Tags For Routing Destinations

    The device searches the IP Groups table and IP Group Set table for an IP Group whose 'Tags' parameter is configured with the same tag as selected from the Dial Plan rule. If found, the device routes the call to this IP Group. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 746 Mediant 1000B Gateway & E-SBC The following figure displays the device's SIP dialog processing when Dial Plan tags are used to determine the destination IP Group: Figure 36-7: SIP Dialog Handling for Tag-Based Routing The following procedure describes how to configure routing to destination IP Groups determined by Dial Plan tags.
  • Page 747 √ Tag names with values (i.e., name=value) must be unique within a Dial Plan rule. In the above example, "Country=England" is a tag name with value. Configuring the parameter with "Country=England;Country=Scotland" is invalid. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 748: Dial Plan Backward Compatibility

    Mediant 1000B Gateway & E-SBC A valid configuration would be "Country=England;Country1=Scotland". • Configure the 'Routing Tag Name' parameter with only the name of the tag (i.e., without the value, if exists). For example, instead of "Country=England", configure it as "Country" only.

  • Page 749: Using Dial Plan Tags For Outbound Manipulation

    Dial Plan in Step 1. The tags are assigned using the following parameters: • 'Source Tags' parameter (IPOutboundManipulation_SrcTags): tag denoting the calling users Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 750: Using Dial Plan Tags For Call Setup Rules

    Mediant 1000B Gateway & E-SBC • 'Destination Tags' parameter (IPOutboundManipulation_DestTags): tag denoting the called users 36.5 Using Dial Plan Tags for Call Setup Rules You can use Dial Plan tags in Call Setup rules, configured in the Call Setup Rules table (see Configuring Call Setup Rules on page 393).

  • Page 751: Configuring Malicious Signatures

    (i.e., IP Group). To configure Message Policies, see ''Configuring SIP Message Policy Rules''. The following procedure describes how to configure Malicious Signatures through the Web interface. You can also configure it through ini file (MaliciousSignatureDB) or CLI (configure voip > sbc malicious-signature-database). Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 752 Mediant 1000B Gateway & E-SBC  To configure a Malicious Signature: Open the Malicious Signature table (Setup menu > Signaling & Media tab > SBC folder > Malicious Signature). Click New; the following dialog box appears: Figure 37-1: Malicious Signature Table - Add Dialog Box Configure a Malicious Signature according to the parameters described in the table below.

  • Page 753: Advanced Sbc Features

    Experience (QoE).  To configure SBC emergency call preemption: In the Message Conditions table (see ''Configuring Message Condition Rules'' on page 695), configure a Message Condition rule to identify incoming emergency calls. See Version 7.2 Mediant 1000B Gateway & E-SBC...

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

    Mediant 1000B Gateway & E-SBC above for examples. Open the SBC General Settings page (Setup menu > Signaling & Media tab > SBC folder > SBC General Settings), and then scroll down to the Call Priority and Preemption group: Figure 38-2: Configuring Emergency SBC Call Preemption From the 'Preemption Mode' drop-down list (SBCPreemptionMode), select Enable to enable call preemption.

  • Page 755: Enabling Interworking Of Sip And Sip-I Endpoints

    SIP-I is SIP encapsulated with ISUP and the interworking is between SIP signaling and ISUP signaling. This allows you to deploy the device in a SIP environment where part of the call path involves the PSTN. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 756 Mediant 1000B Gateway & E-SBC The SIP-I sends calls, originating from the SS7 network, to the SIP network by adding ISUP messaging in the SIP INVITE message body. The device can receive such a message from the SIP-I and remove the ISUP information before forwarding the call to the SIP endpoint.

  • Page 757: Call Forking

    ''Configuring SIP Message Manipulation'' on page 401). For a complete description of the ISUP manipulation syntax, refer to the SIP Message Manipulation Reference Guide. In addition, you can use AudioCodes proprietary SIP header X-AC-Action in Message Manipulation rules to support the following call actions (e.g., SIP-I SUS and RES messages) for the ISUP SPIROU variant: ...

  • Page 758: Configuring Sip Forking Initiated By Sip Proxy

    Mediant 1000B Gateway & E-SBC 38.4.2 Configuring SIP Forking Initiated by SIP Proxy The device can handle the receipt of multiple SIP 18x responses as a result of SIP forking initiated by a proxy server. This occurs when the device forwards an INVITE, received from a user agent (UA), to a proxy server and the proxy server then forks the INVITE request to multiple UAs.

  • Page 759: Enabling Auto-Provisioning Of Subscriber-Specific Information Of Broadworks Server For Survivability

    To enable the BroadWorks survivability feature: Open the SBC General Settings page (Setup menu > Signaling & Media tab > SBC folder > SBC General Settings). From 'BroadWorks Survivability Feature' drop-down list (SBCExtensionsProvisioningMode), select Enable: Click Apply. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 760: Configuring Broadsoft's Shared Phone Line Call Appearance For Survivability

    Mediant 1000B Gateway & E-SBC 38.5.2 Configuring BroadSoft's Shared Phone Line Call Appearance for 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 761: Configuring 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 38-7: Normal Operation in Call Center Application Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 762 Mediant 1000B Gateway & E-SBC Figure 38-8: Call Survivability for Call Center  To configure call survivability for a call center application: In the IP Groups table (see ''Configuring IP Groups'' on page 353), add IP Groups for the following entities: •...

  • Page 763: Enabling Survivability Display On Aastra Ip Phones

    <?xml version="1.0" encoding="utf-8"?> <LMIDocument version="1.0"> <LocalModeStatus> <LocalModeActive>true</LocalModeActive> <LocalModeDisplay>StandAlone Mode</LocalModeDisplay> </LocalModeStatus> </LMIDocument>  To enable survivability display on Aastra phones: Load an ini file to the device that includes the following parameter setting: SBCEnableSurvivabilityNotice = 1 Version 7.2 Mediant 1000B Gateway & E-SBC...

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

    Mediant 1000B Gateway & E-SBC 38.6 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 765: Cloud Resilience Package

    Part VII Cloud Resilience Package...

  • Page 767: Crp Overview

    Test call agent registering users and device, or any other route to responding server  Short number dialog (short numbers are learned dynamically in the registration process)  Survivability indication to IP phone Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 768 Mediant 1000B Gateway & E-SBC Survivability Quality of Experience/Service Security  Call hold and retrieve  Call transfer (if IP phone initiates REFER)  Basic Shared Line Appearance (excluding correct busy line indications)  Call waiting (if supported by IP phone) One of the main advantages of CRP is that it enables quick-and-easy configuration.

  • Page 769: Crp Configuration

    Click Apply, and then reset the device with a save-to-flash for your settings to take effect. 40.2 Configuring Call Survivability Mode The CRP can be configured to operate in one of the following call survivability modes: Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 770 Mediant 1000B Gateway & E-SBC  Normal (Default): The CRP interworks between the branch users and the IP PBX located at headquarters. The CRP forwards all requests (such as for registration) from the branch users to the IP PBX, and routes the calls based on the IP-to-IP routing rules.

  • Page 771: Pre-Configured Ip Groups

    The IP Groups can be edited, except for the fields listed above, which are read-only. • For accessing the IP Groups table and for a description of its parameters, see ''Configuring IP Groups'' on page 353. Version 7.2 Mediant 1000B Gateway & E-SBC...

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

    Mediant 1000B Gateway & E-SBC 40.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 769.

  • Page 773: Emergency Mode

    Route Ignore Inputs #1 [CRP IP Group #3 [CRP Alternative Users] Gateway] Route Ignore Inputs #2 [CRP IP Group #1 [CRP Route Row Proxy] Users] #2 [CRP IP Group #3 [CRP Route Row Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 774: Configuring Pstn Fallback

    Mediant 1000B Gateway & E-SBC Mode Index Source IP Request Type Destination Destination Destination Alternative Group Type IP Group Address Route Options Proxy] Gateway] #3 [CRP IP Group #2 [CRP Route Row Gateway] Proxy] #3 [CRP IP Group #1 [CRP...

  • Page 775: Maintenance

    Part VIII Maintenance...

  • Page 777: Basic Maintenance

    Timeout' field (see next step). During this interval, no new traffic is accepted. If no traffic exists and the time has not yet expired, the device resets immediately. • No: Reset begins immediately, regardless of traffic. Any existing traffic is immediately terminated. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 778: Remotely Resetting Device Using Sip Notify

    Remotely Resetting Device using SIP NOTIFY The device can be remotely reset upon the receipt of a SIP NOTIFY that contains an Event header that is set to 'check-sync;reboot=true' (proprietary to AudioCodes), as shown in the example below: NOTIFY sip:<user>@<dsthost> SIP/2.0 To: sip:<user>@<dsthost>...

  • Page 779: Locking And Unlocking The Device

    'Gateway Operational State' read-only field displays "LOCKED" and the device does not process any calls.  To unlock the device:  Click the UNLOCK button; the device unlocks immediately and accepts new incoming calls. The 'Gateway Operational State' read-only field displays "UNLOCKED". Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 780: Saving Configuration

    Mediant 1000B Gateway & E-SBC 41.4 Saving Configuration When you configure parameters and tables in the Web interface and then click the Apply button on the pages in which the configurations are done, changes are saved to the device's volatile memory (RAM). These changes revert to their previous settings if the device subsequently resets (hardware or software) or powers down.

  • Page 781: Replacing Modules

    Click OK; after a few seconds, the module is software-removed, the module's port status icons turn gray and the name of the module is suffixed with the word "Reserved": Physically remove the module from the chassis. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 782 Mediant 1000B Gateway & E-SBC Insert the new module: Physically insert the new module into the same chassis slot in which the previous module was housed (refer to the Hardware Installation Manual). On the Monitor home page, click the title of the module ("<module type>...

  • Page 783: Channel Maintenance

    B-channel is restarted. • B-channel restart can only be done if the D-channel of the trunk to which it belongs is synchronized (Layer 2). • B-channel restart does not affect the B-channel's configuration. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 784: Locking And Unlocking Trunk Groups

    Mediant 1000B Gateway & E-SBC 43.3 Locking and Unlocking Trunk Groups You can lock a Trunk Group to take its trunks (and their channels) out of service. When you initiate a lock, the device rejects all new incoming calls for the Trunk Group and immediately terminates active calls (busy channels), eventually taking the entire Trunk Group out of service.

  • Page 785: Disconnecting Active Calls

    To add a port description: Open the Monitor home page (see ''Viewing Device Status on Monitor Page'' on page 868). Click the required port icon; a shortcut menu appears: Figure 43-3: Choosing Port Description Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 786 Mediant 1000B Gateway & E-SBC From the shortcut menu, choose Port Description; the following dialog box appears: Figure 43-4: Configuring Analog Port Description Type a brief description for the port, and then click Submit. User's Manual Document #: LTRT-27055...

  • Page 787: Software Upgrade

    CLI - see Loading Auxiliary Files through CLI on page 789  TFTP - see Loading Auxiliary Files through ini File using TFTP  EMS (Software Manager) – refer to the EMS User’s Manual Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 788: Loading Auxiliary Files Through Web Interface

    Mediant 1000B Gateway & E-SBC Note: • You can automatically load Auxiliary files from a remote server using the device's Automatic Update mechanism (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 779.

  • Page 789: Loading Auxiliary Files Through Cli

    44.1.3 Call Progress Tones File The Call Progress Tones (CPT) and Distinctive Ringing (analog interfaces only) Auxiliary file contains definitions of the CPT (levels and frequencies) that are detected and generated by the device. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 790 (in any standard text editor) to suit your specific requirements and then convert the modified ini file into binary dat file format, using AudioCodes DConvert utility. For more information, refer to the DConvert Utility User's Guide.
  • Page 791 1 to 128 Hz). • Signal Level [-dBm]: Level of the tone for AM tones. • AM Factor [steps of 0.02]: Amplitude modulation factor (valid range from 1 to 50). Recommended values from 10 to 25. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 792: Distinctive Ringing

    Mediant 1000B Gateway & E-SBC Note: • When the same frequency is used for a continuous tone and a cadence tone, the 'Signal On Time' parameter of the continuous tone must have a value that is greater than the 'Signal On Time' parameter of the cadence tone. Otherwise, the continuous tone is detected instead of the cadence tone.
  • Page 793 #Regular North American Ringing Pattern [Ringing Pattern #0] Ring Type=0 Freq [Hz]=20 First Ring On Time [10msec]=200 First Ring Off Time [10msec]=400 #GR-506-CORE Ringing Pattern 1 [Ringing Pattern #1] Ring Type=1 Freq [Hz]=20 Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 794: Prerecorded Tones File

    Audition), and then combined into a single and loadable PRT file (.dat) using the latest version of AudioCodes DConvert utility (refer to the DConvert Utility User's Guide). Once created, you need to install the PRT file on the device (flash memory), using the Web interface (see 'Loading Auxiliary Files' on page 787) or CLI.

  • Page 795: Voice Prompts File

    (CASTableIndex_x) and different CAS tables can be assigned to different B-channels (CASChannelIndex). To load CAS files see ''Loading Auxiliary Files'' on page 787. Note: All CAS files loaded together must belong to the same trunk type (i.e., either E1 or T1). Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 796: Dial Plan File

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

  • Page 797: Dialing Plans For Digit Collection

    • To use the Dial Plan file, you must also use a special CAS .dat file that supports this feature. For more information, contact your AudioCodes sales representative. • For E1 CAS MFC-R2 variants, which don't support terminating digit for the called party number, usually I-15, the Dial Plan file and the DigitMapping parameter are ignored.
  • Page 798 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 787.

  • Page 799: Dial Plan Prefix Tags For Ip-To-Tel Routing

    Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 800 Mediant 1000B Gateway & E-SBC Note: • When using prefix tags, you need to configure manipulation rules to remove the tags before the device sends the calls to their destinations. • Called and calling prefix tags can be used in the same routing rule.

  • Page 801: Obtaining Ip Destination From Dial Plan File

    Create the Dial Plan file. The syntax of the Dial Plan index for this feature is as follows: <destination / called prefix number>,0,<IP destination> Note: The second parameter "0" is not used and ignored. Version 7.2 Mediant 1000B Gateway & E-SBC...

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

    Mediant 1000B Gateway & E-SBC An example of a configured Dial Plan (# 6) in the Dial Plan file is shown below: [ PLAN6 ] 200,0,10.33.8.52 ; called prefix 200 is routed to 10.33.8.52 201,0,10.33.8.52 300,0,itsp.com ; called prefix 300 is routed to itsp.com Convert the file to a loadable file and then load it to the device (see ''Creating a Dial Plan File'' on page 796).

  • Page 803: Viewing Information Of Installed Dial Plan File

    Searching a prefix number: You can check whether a specific prefix number is defined in a specific Dial Plan (and view the corresponding tag if the Dial Plan implements tags), by entering the following CLI command (in Enable mode): Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 804: User Information File

    Mediant 1000B Gateway & E-SBC # debug auxilary-files dial-plan match-number <Dial Plan number> <prefix number> For example, the following checks whether the called prefix number 2000 is defined in Dial Plan 1, which is used for obtaining the destination IP address (tag):...
  • Page 805 44.1.8.2.1 Configuring GW User Info Table through Web Interface The following procedure describes how to configure and register users in the GW User Info table through the Web interface. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 806 Mediant 1000B Gateway & E-SBC Note: • To configure the User Info table, make sure that you have enabled the feature, as described in Enabling the User Info Table on page804. • If a User Info file is loaded to the device (as described in ''Configuring GW User...
  • Page 807 (Ext405) username (user405) password (0aGzoKfh5uI=) status (not-resgistered)  To search a user by pbx-ext: (sip-def-proxy-and-reg)# user-info find <pbx-ext e.g., 405> 405: Found at index 0 in GW user info table, not registered Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 808 Mediant 1000B Gateway & E-SBC Note: To configure the User Info table, make sure that you have enabled the feature, as described in Enabling the User Info Table on page 804. 44.1.8.2.3 Configuring GW User Info Table in Loadable Text File The GW User Info table can be configured as a User Info file using a text-based file (*.txt).

  • Page 809: User Information File For Sbc User Database

    User Info file.  To configure the SBC User Info table through the Web interface: Open the SBC User Info table (Setup menu > Signaling & Media tab > SBC folder > User Information). Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 810 Mediant 1000B Gateway & E-SBC Click New; the following dialog box appears: Figure 44-7: SBC User Info Table - Add Dialog Box Configure a user according to the table below. Click Apply. To register a user, select the user's table entry, and then from the Action drop-down list, choose Register.
  • Page 811 The SBC User Info table can be configured as a User Info file using a text-based file (*.txt). This file can be created using any text-based program such as Notepad. This User Info file Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 812: Viewing The Installed User Info File Name

    Mediant 1000B Gateway & E-SBC is the same file used for the GW User Info table. Thus, this file can include both Gateway and SBC user information. You can load the User Info file using any of the following methods: ...

  • Page 813: Amd Sensitivity File

    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 814 Mediant 1000B Gateway & E-SBC This page is intentionaly left blank. User's Manual Document #: LTRT-27055...

  • Page 815: License Key

    License Key The License Key determines the device's supported features and call capacity, as ordered from your AudioCodes sales representative. You can upgrade or change your device's supported features and capacity, by purchasing and installing a new License Key that match your requirements.

  • Page 816: Installing A New License Key

     Serial Number: Device's serial number.  Board Type: AudioCodes internal identification number of the type of your device.  Remote License Server / Remote License Server IP: For more information, see Upgrading SBC Capacity Licenses by License Pool Manager Server on page 820.

  • Page 817: Installing A License Key String

    The License Key page uses color-coded icons to indicate the changes between the previous License Key and the newly loaded License Key (for more information, see Installing License Key through Web Interface on page 816). Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 818: Installing A License Key File

    Mediant 1000B Gateway & E-SBC Click Apply New License Key; the following message box appears: Figure 45-4: Apply New License Key Message Click Reset; the device begins to save the file to flash memory with a reset and the following progress message box appears:...
  • Page 819 Click Reset; the device begins to save the file to flash memory with a reset and the following progress message box appears: Figure 45-8: Reset in Progress for License Key When installation completes, the following message box appears: Figure 45-9: Reset and Save-to-Flash Success Message Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 820: Installing License Key Through Cli

    Manager Server The device can receive SBC capacity (session) 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 licenses from the pool to devices in the network to meet capacity demands of each device, whenever required.
  • Page 821 The device sends the following SNMP alarms relating to the allocation/de-allocation of SBC licenses by the License Pool Manager Server:  acLicensePoolInfraAlarm (OID 1.3.6.1.4.1.5003.9.10.1.21.2.0.106)  acLicensePoolApplicationAlarm (OID 1.3.6.1.4.1.5003.9.10.1.21.2.0.107)  acLicensePoolOverAllocationAlarm (OID 1.3.6.1.4.1.5003.9.10.1.21.2.0.125) For more information on the alarms, refer to the SNMP Reference Guide. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 822: Backing Up The License Key

    Viewing the Device's Product Key The Product Key identifies a specific purchase of your device installation for the purpose of subsequent communication with AudioCodes (e.g., for support and software upgrades). The Product Key is your chassis' serial number--"S/N(Product Key)"--which also appears on the product label affixed to the chassis.

  • Page 823: Software Upgrade Wizard

    Once loaded, you can select other file types to load. Note: • 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 824 Mediant 1000B Gateway & E-SBC • Navigation tree: Setup menu > Administration tab > Maintenance folder > Software Upgrade. Figure 45-13: Starting Software Upgrade Wizard Click Start Software Upgrade; the wizard starts, prompting you to load a .cmp file: Figure 45-14: Loading CMP File in Software Upgrade Wizard...
  • Page 825 Restore configuration to factory defaults: Clear the 'Use existing configuration' check box. • Retain the existing configuration (default): Select the 'Use existing configuration' check box. Figure 45-16: Load an INI File in the Software Upgrade Wizard Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 826 Mediant 1000B Gateway & E-SBC Note: 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) and thereby, overwrite values previously configured for these parameters.

  • Page 827: Configuration File

    The following procedure describes how to load a configuration file from a folder on your PC to the device. You can load any of the following configuration file types:  ini file  CLI Script file  CLI Startup Script file Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 828 Mediant 1000B Gateway & E-SBC Warning: • When loading an ini file as described in this section, parameters not included in the ini file are restored to default settings. If you want to keep the device's current configuration settings and also apply the settings specified in the ini file, load the file through the Auxiliary Files page, as described in Loading Auxiliary Files through Web Interface on page 788.

  • Page 829: Automatic Provisioning

    Open the Network Settings page (Setup menu > IP Network tab > Advanced folder > Network Settings). From the 'Enable DHCP" drop-down list, select Enable. Figure 47-1: Enabling DHCP Client Functionality Click Apply. To activate the DHCP process, reset the device. Version 7.2 Mediant 1000B Gateway & E-SBC...

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

    Mediant 1000B Gateway & 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 831: Provisioning From Tftp Server Using Dhcp Option 66

    Provisioning the device from a third-party TFTP server is suitable when the network in which the device is deployed includes a provisioning TFTP server for all network equipment, without the capability of distinguishing between AudioCodes and non- AudioCodes devices. Upon startup, the device checks for DHCP Option 66 in the DHCP response received from the DHCP server.

  • Page 832: Http-Based Provisioning

    Mediant 1000B Gateway & E-SBC Enable the device to include DHCP Option 66 in DHCP Option 55 (Parameter Request List) when requesting TFTP provisioning parameters from a DHCP server, using the following ini file parameter: DHCPRequestTFTPParams = 1 Reset the device with a save-to-flash for your settings to take effect.

  • Page 833: Ftp-Based Provisioning

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

    Mediant 1000B Gateway & E-SBC 47.2.1 Files Provisioned by Automatic Update You can use the Automatic Update feature to update the device with any of the following files:  Software file (cmp)  Auxiliary files (e.g., Call Progress Tones, SSL Certificates, SSL Private Key) ...

  • Page 835: Mac Address Placeholder In Configuration File Name

    URL address of the provisioning server it uses a placeholder for the file names which is replaced by hardcoded file names and extensions according to file type, as described in more detail below. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 836 Mediant 1000B Gateway & E-SBC Note: • Unlike the parameters that define specific URLs for Auxiliary files (e.g., CptFileURL), the file template feature always retains the URLs after each automatic update process. Therefore, with the file template the device always attempts to download the files upon each automatic update process.

  • Page 837: Triggers For Automatic Update

    Interval between Automatic Updates (e.g., every 60 minutes), configured by the ini file parameter AutoUpdateFrequency or CLI command configure system > automatic-update > update-frequency.  Centralized provisioning server request: • Upon receipt of an SNMP request from the provisioning server. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 838: Access Authentication With Http Server

    Mediant 1000B Gateway & E-SBC • 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 839 To enable the automatic software (.cmp) file download method based on this timestamp method, use the ini file parameter, AutoCmpFileUrl or CLI command, Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 840 Mediant 1000B Gateway & E-SBC configure system > automatic-update > auto-firmware <URL>. The device uses the same configured URL to download the .cmp file for each subsequent Automatic Update process. You can also enable the device to run a CRC on the downloaded configuration file (ini) to determine whether the file has changed in comparison to the previously downloaded file.

  • Page 841: File Download Sequence

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

  • Page 842: Cyclic Redundancy Check On Downloaded Configuration Files

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

  • Page 843: Automatic Update Configuration Examples

    Automatic Update of software file (.cmp): ♦ ini File: AutoCmpFileUrl = 'https://www.company.com/sw.cmp' ♦ CLI: # configure system (config-system)# automatic update (automatic-update)# auto-firmware 'http://www.company.com/sw.cmp' Automatic Update of Call Progress Tone file: ♦ ini File: Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 844: Automatic Update From Remote Servers

    Mediant 1000B Gateway & E-SBC CptFileURL = 'https://www.company.com/call_progress.dat' ♦ CLI: # configure system (config-system)# automatic update (automatic-update)# call-progress-tones 'http://www.company.com/call_progress.dat' Automatic Update of ini configuration file: ♦ ini File: IniFileURL = 'https://www.company.com/config.ini' ♦ CLI: # configure system (config-system)# automatic update (automatic-update)# voice-configuration 'http://www.company.com/config.ini'...

  • Page 845: Automatic Update For Mass Deployment

    (automatic-update)# update-frequency 03:00 47.2.10.3 Automatic Update for Mass Deployment This example describes how to configure the Automatic Update feature for updating multiple devices (i.e., mass deployment) using an HTTP provisioning server. In this Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 846 Mediant 1000B Gateway & E-SBC example, all the devices are configured to download the same "master" configuration file. This file serves as the configuration template and instructs the devices which files to download and how often to perform the Automatic Update process. In addition, the master file also instructs each device to download an ini configuration file whose file name contains the MAC address of the device.
  • Page 847 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 network (config-network)# interface network-if 0 (network-if-0)# primary-dns 80.179.52.100 Power down and then power up the device. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 848 Mediant 1000B Gateway & E-SBC This page is intentionaly left blank. User's Manual Document #: LTRT-27055...

  • Page 849: Sbc Configuration Wizard

    SBC Configuration Wizard, their new settings are used. • On some wizard pages, the availability of certain fields depends on the selected application. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 850: Starting The Sbc Configuration Wizard

    Figure 48-1: SBC Configuration Wizard - Welcome Page If desired, the SBC Configuration Wizard allows you to share usage statistics with AudioCodes in order to help us improve our software. To agree, select the 'Report usage statistics' check box, and then fill in the subsequent fields.

  • Page 851: General Setup Page

    SIP REGISTER, SUBSCRIBE and NOTIFY messages. If you selected the SIP Trunk application in Step 1, do the following: From the 'IP-PBX' drop-down list, select the IP PBX model. If the model is not listed, select Generic IP-PBX. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 852 Mediant 1000B Gateway & E-SBC From the 'SIP-Trunk' drop-down list, select the SIP trunk provider. If the provider is not listed, select Generic SIP Trunk. To generate a configuration template based on the individual properties of the selected IP PBX and SIP Trunk, instead of using the existing template for the specific combination, select the 'Override template' check box.

  • Page 853: System Page

    DNS server and the IP PBX or ITSP require the use of hostnames instead of IP addresses. Select the 'Apply local DNS' check box, and then configure the following parameters: Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 854: Interfaces Page

    Mediant 1000B Gateway & E-SBC ♦ 'Domain Name': Domain name to resolve into an IP address. ♦ 'First IP address': IP address of the domain name. ♦ 'Secondary IP address': Second IP address of the domain name (optional). For more information on configuring the device's DNS table, see Configuring the Internal DNS Table on page 163.

  • Page 855: Ip-Pbx Page

    IP PBX. The field is applicable only when the device is connected to a router that performs NAT.  To configure IP PBX settings: Under the IP-PBX group, configure the following: Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 856 Mediant 1000B Gateway & E-SBC • 'Address': Configure the IP address (or hostname) of the IP PBX. Note that for the One port: WAN network topology, when the device is assigned a public IP address, you must use the public IP address (of the Enterprise router) instead of the private address of the IP PBX, and configure the Enterprise router to forward VoIP traffic from the device to the IP PBX.

  • Page 857: Sip Trunk Page

    Under the SIP Trunk group, configure the following: • 'Address': Configures the IP address or hostname of the SIP Trunk. • 'Backup Address': (Optional) Configures the backup IP address or hostname of the SIP Trunk. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 858 Mediant 1000B Gateway & E-SBC • 'SIP Domain': Configures the SIP domain name for communicating with the SIP Trunk. The domain name is used in the following SIP message headers: ♦ Outbound calls: Request-URI and To headers ♦ Inbound calls: From header •...

  • Page 859: Number Manipulation Page

    'Password': Password for communication with ARM. Click Next; the Remote Users (FEU) page appears (see Remote Users Page on page 860). The example below changes the number "+15033311432" to "03311432":  Prefix: "+1503" Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 860: Remote Users Page

    Mediant 1000B Gateway & E-SBC  Remove:"4"  Add: "0" 48.8 Remote Users Page The Remote Users (FEU) wizard page configures the remote users settings. Note: This page is applicable only to IP PBXs that support such configuration. Figure 48-8: SBC Configuration Wizard - Remote Users Page ...

  • Page 861: Summary Page

    You can later load the file to the device (see Loading an ini File to the Device on page 827). Click Next; the Congratulations page appears (see Congratulations Page on page 862). Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 862: Congratulations Page

    Mediant 1000B Gateway & E-SBC 48.10 Congratulations Page The Congratulations wizard page is the last wizard page and allows you to complete configuration. Figure 48-10: SBC Configuration Wizard - Congratulations Page  To complete the SBC Configuration Wizard:  Click Apply & Reset to apply configuration to the device or click Save INI File to save configuration as an ini file on your PC.

  • Page 863: Restoring Factory Defaults

    IP Interfaces table (see ''Configuring IP Network Interfaces'' on page 142), 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.2 Mediant 1000B Gateway & E-SBC...

  • Page 864: Restoring Defaults Using Hardware Reset Button

    Mediant 1000B Gateway & E-SBC  To restore factory defaults through Web interface: Open the Configuration File page: • Toolbar: From the Actions drop-down menu, choose Configuration File. • Navigation tree: Setup menu > Administration tab > Maintenance folder >...

  • Page 865: Status, Performance Monitoring And Reporting

    Part IX Status, Performance Monitoring and Reporting...

  • Page 867: System Status

    Product Key, which identifies the specific device purchase. The Product Key also appears on the product label that is affixed to the chassis, as "S/N(Product Key)". For more information, see Viewing the Device's Product Key on page 822. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 868: Viewing Device Status On Monitor Page

    Mediant 1000B Gateway & E-SBC Parameter Description Board Type Product name of the device. Device Up Time Duration that the device has been up and running since the last reset. The duration is displayed in the following format: dd:hh:mm:ss:100th of a second Device Administrative State Administrative status ("Unlocked"...
  • Page 869 Note: The displayed number and type of telephony interfaces depends on the ordered hardware configuration. Table 50-1: Description of Graphical Display of Device Item # Description Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 870 Mediant 1000B Gateway & E-SBC Item # Description Displays the highest severity of an active alarm raised (if any) by the device:  Green: No alarms  Red: Critical alarm  Orange: Major alarm  Yellow: Minor alarm To view active alarms, click the Alarms area to open the Active Alarms page (see Viewing Active Alarms on page 877).

  • Page 871: Viewing Port Information

    Open the Monitor home page (see ''Viewing Device Status on Monitor Page'' on page 868). On the graphical display of the device, click a port; a shortcut menu appears. From the shortcut menu, choose Port Status. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 872 Mediant 1000B Gateway & E-SBC • For digital ports: The Trunks & Channel Status page appears (see Viewing Trunk and Channel Status on page 905). Click a channel; the following page appears with the Basic tab selected: • For analog ports: The following page appears with the Basic tab selected:...
  • Page 873 ''Configuring DTMF Transport Types'' on page 201. Basic Channel Identifier: Channel identifier number. Status Status of port:  "Inactive": No call  "Active": Active call Call ID See above. Endpoint ID ID of endpoint:  "Not Available" Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 874 Mediant 1000B Gateway & E-SBC Field Description Call Duration Call duration (in seconds) from when call was established. Call Type Type of call:  "Voice": Voice call  "Fax": Fax call Call Destination IP address of called party. Coder Coder type used for the call.
  • Page 875 Displays the volume gain (in dB). Voice Volume Displays the voice volume gain (in dB). DTMF Transport Type Displays the DTMF transport type. Enabled Detectors Displays enabled detectors (e.g., AMD). Fax Transport Type Displays the fax transport type. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 876 Mediant 1000B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-27055...

  • Page 877: Viewing Carrier-Grade Alarms

     Major (orange)  Minor (yellow) Source Component of the device from which the alarm was raised. Description Brief description of the alarm. Date Date (DD/MM/YYYY) and time (HH:MM:SS) the alarm was raised. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 878: Viewing History Alarms

    Mediant 1000B Gateway & E-SBC 51.2 Viewing History Alarms You can view all SNMP alarms, in the Web interface's Alarms History table, that have been raised (active alarms) as well as cleared (resolved). One of the benefits of this is that you can view alarms that may have been raised and then cleared on a continuous basis.
  • Page 879 Date (DD/MM/YYYY) and time (HH:MM:SS) the alarm was raised.  To delete all the alarms in the table: Click the Delete History Table button; a confirmation message box appears. Click OK to confirm. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 880 Mediant 1000B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-27055...

  • Page 881: Viewing Management User Activity Logs

    Username of the user account that performed the activity. Interface Protocol used for connecting to the management interface (e.g., Telnet, SSH, Web, or HTTP). Client IP address of the client PC from where the user accessed the management interface. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 882 Mediant 1000B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-27055...

  • Page 883: Viewing Performance Monitoring

    Open the Trunk Utilization page (Monitor menu > Monitor tab > Performance Monitoring folder > Trunk Utilization). Figure 53-1: Viewing Trunk Utilization From the 'Trunk' drop-down list, select the trunk for which you want to view active channels. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 884: Viewing Call Success And Failure Ratio

    Mediant 1000B Gateway & E-SBC For more graph functionality, see the following table: Table 53-1: Additional Graph Functionality for Trunk Utilization Button Description Add button Displays additional trunks in the graph. Up to five trunks can be displayed simultaneously. To view another trunk, click the button and then from the new 'Trunk' drop-down list, select the required trunk.
  • Page 885 If there is no data for the charts, the chart appears gray and "No Data" is displayed to the right of the chart.  To refresh the charts:  Click Refresh.  To reset the counters:  Click Reset Counters. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 886: Viewing Average Call Duration

    Mediant 1000B Gateway & E-SBC 53.3 Viewing Average Call Duration You can view the number of currently active calls and the average call duration (ACD) in the Web interface's Average Call Duration page. You can filter display by a specific SRD or IP Group.

  • Page 887: Configuring Performance Profiles

    Yellow: Indicates fair call quality  Red: Indicates poor call quality When the threshold of a voice metric is crossed, the device changes the alarm severity and corresponding color-coded quality state of the call: Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 888 Mediant 1000B Gateway & E-SBC  Minor Threshold (Yellow): Lower threshold that indicates changes from Green or Red to Yellow.  Major Threshold (Red): Higher threshold that indicates changes from Green or Yellow to Red. The device also uses hysteresis to determine whether the threshold has indeed being crossed.
  • Page 889 Defines a configuration entity type to which you want to apply the rule. entity  [0] Global = (Default) The device calculates call metrics [PerformanceProfile_Entity] for all calls.  [1] SRD = Assigns an SRD. To specify the SRD, use the Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 890 Mediant 1000B Gateway & E-SBC Parameter Description 'SRD' parameter (see below).  [2] IP Group = Assigns an IP Group. To specify the IP Group, use the 'IP Group' parameter (see below). IP Group Assigns an IP Group to the rule.
  • Page 891 (see 'Minimum Samples' parameter). For example, if the parameter is configured to five minutes, but the number of calls during the interval is less than the configured minimum samples, no calculation is done. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 892 Mediant 1000B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-27055...

  • Page 893: Viewing Voip Status

    Calls than zero:  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  RELEASE_BECAUSE_SILENCE_DISC Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 894 Mediant 1000B Gateway & E-SBC Counter Description  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 895: Viewing Sbc Registered Users

    10 seconds from the proxy/registrar server.  CLI: • SBC users: # show voip register db sbc list • SBC contacts of a specified AOR: # show voip register db sbc user <Address Of Record> Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 896: Viewing Proxy Set Status

    Mediant 1000B Gateway & E-SBC 54.3 Viewing Proxy Set Status You can view the status of Proxy Sets that are used in your call routing topology. Proxy Sets that are not associated with any routing rule are not displayed. To configure proxy Sets, see Configuring Proxy Sets on page 367.
  • Page 897 "NOT RESOLVED": Proxy address is configured as an FQDN, but the DNS resolution has failed.  Empty field: Keep-alive for the proxy is disabled or the device has yet to send a keep-alive to the proxy. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 898: Viewing Registration Status

    Mediant 1000B Gateway & E-SBC 54.4 Viewing Registration Status You can view the registration status of the device's endpoints (FXS, FXO and BRI) and SIP Accounts. The registration mode (i.e., per device, endpoint, account. or no registration) is configured in the Trunk Group Settings table (see Configuring Trunk Group Settings on page 505) or using the TrunkGroupSettings ini file parameter.

  • Page 899: Viewing Ip Connectivity

    ''Alternative Routing Based on IP Connectivity'' on page 528. Quality Status Displays the QoS (according to packet loss and delay) of the destination:  "Unknown": Recent quality information isn't available. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 900 Mediant 1000B Gateway & E-SBC Column Name Description  "OK"  "Poor" Note:  The parameter is applicable only if the parameter 'Alt Routing Tel to IP Mode' is set to 'QoS' or 'Both' (AltRoutingTel2IPMode = 2 or 3). ...

  • Page 901: Viewing Gateway Cdr History

    Displays the direction of the call with regards to IP and Tel sides:  "Incoming": IP-to-Tel call  "Outgoing": Tel-to-IP call Remote IP Displays the IP address of the call party. For an "Incoming" call, this is Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 902 Mediant 1000B Gateway & E-SBC Field Description the source IP address; for an "Outgoing" call, this is the destination IP address. Duration Displays the duration of the call, displayed in the format hh:mm:ss, where hh is hours, mm minutes and ss seconds. For example, 00:01:20 denotes 1 minute and 20 seconds.

  • Page 903: Viewing Sbc Cdr History

    IP address; for an "Outgoing" call, this is the destination IP address. Displays the duration of the call, displayed in the format hh:mm:ss, Duration where hh is hours, mm minutes and ss seconds. For example, 00:01:20 Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 904 Mediant 1000B Gateway & E-SBC Field Description denotes 1 minute and 20 seconds. Termination Reason Displays the reason for the call being released (ended). For example, "NORMAL_CALL_CLEAR" indicates a normal termination. Session ID Displays the SIP session ID of the call.

  • Page 905: Viewing Pstn Status

    Table 55-1: Description of Color-Coded Icons for Trunk Status Trunk Icon Color Label Gray Disabled Green Active - OK Yellow RAI Alarm LOS / LOF Alarm Blue AIS Alarm Light Orange D-Channel Alarm Dark Orange NFAS Alarm Version 7.2 Mediant 1000B Gateway & E-SBC...

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

    Mediant 1000B Gateway & E-SBC The status of the channels is depicted by color-coded icons, as described in the table below: Table 55-2: Description of Color-Coded Icons for Channel Status Icon Color Label Description Light blue Inactive Channel is configured, but currently has no calls...
  • Page 907 To view the status of the D-channels and NFAS groups:  Open the NFAS Group & D-Channel Status page (Monitor menu > Monitor tab > PSTN Status folder > NFAS Group & D-Channel Status). Figure 55-1: NFAS Group & D-Channel Status Page Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 908 Mediant 1000B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-27055...

  • Page 909: Viewing Network Status

    Navigation tree: Monitor menu > Monitor tab > Network Status folder > Ethernet Port Information. • Monitor home page: Click an Ethernet port on the graphical display of the device (see ''Viewing Device Status on Monitor Page'' on page 868). Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 910: Viewing Static Routes Status

    Mediant 1000B Gateway & E-SBC Table 56-1: Ethernet Port Information Table Description 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 of the Ethernet port.

  • Page 911: Reporting Information To External Party

    The type of RTCP XR report event (VQReportEvent) supported by the device is VQSessionReport (SessionReport). The device can include local and remote metrics in the RTCP XR. Local metrics are generated by the device while remote metrics are provided by Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 912 Mediant 1000B Gateway & E-SBC the remote endpoint. The following table lists the supported voice metrics (parameters) published in the RTCP XR. Table 57-1: RTCP XR Published VoIP Metrics Metric Parameter Description CallID Call ID - call ID from the SIP dialog...
  • Page 913 MOS-LQ - estimated mean opinion score for listening voice quality on a scale from 1 to 5, in which 5 represents excellent and 1 represents unacceptable MOSLQEstAlg MOS-LQ Est. Algorithm - name (string) of the algorithm used to estimate MOSLQ Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 914 Mediant 1000B Gateway & E-SBC Metric Parameter Description MOSCQ MOS-CQ - estimated mean opinion score for conversation voice quality on a scale from 1 to 5, in which 5 represents excellent and 1 represents unacceptable MOSCQEstAlg MOS-CQ Est. Algorithm - name (string) of the algorithm used to...
  • Page 915 RTCP XR reports. • (Gateway Application Only) 'Gateway RTCP XR Report Mode' (RTCPXRReportMode) - enables RTCP XR reports and defines the interval at which they are sent. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 916: Generating Call Detail Records

    Mediant 1000B Gateway & E-SBC • (SBC Application Only) 'SBC RTCP XR Report Mode' (SBCRtcpXrReportMode) - enables the sending of RTCP XR reports of QoE metrics at the end of each call session (i.e., after a SIP BYE). Figure 57-2: Configuring RTCP XR Collection Server Click Apply, and then reset the device with a save-to-flash for your settings to take effect.
  • Page 917  "DIALOG_START"  "DIALOG_END" EPTyp Endpoint type: "SBC" String SIPMethod SIP message type String (up to characters) SIPCallId Unique ID of call String (up to characters) SessionId Unique Session ID String (up to Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 918 Mediant 1000B Gateway & E-SBC CDR Field Description CDR Report Type Format (SBCReportType) characters) LegId Unique ID number of the call leg within a "CALL_START", String specific call session. "CALL_CONNECT" (decimal) and "CALL_END" A basic call consists of two legs (incoming...
  • Page 919  "GWAPP_RESOUUCE_UNAVAIL ABLE_UNSPECIFIED"  "RELEASE_BECAUSE_NO_CON FERENCE_RESOURCES_LEFT"  "RESOURCE_BECAUSE_NO_TR ANSCODING_RESOURCES_LEF T"  "RELEASE_BECAUSE_GW_LOC KED"  NO_MATCH:  "RELEASE_BECAUSE_UNMATC HED_CAPABILITIES"  FORWARDED:  "RELEASE_BECAUSE_FORWAR D"  GENERAL_FAILED: Any other reason Calls with duration:  NORMAL_CALL_CLEAR: Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 920 Mediant 1000B Gateway & E-SBC CDR Field Description CDR Report Type Format (SBCReportType)  "GWAPP_NORMAL_CALL_CLEA R"  "ABNORMALLY_TERMINATED": Anything else N/A - Reasons not belonging to above categories. SetupTime Call setup time String (up to characters) ConnectTime Call connect time "CALL_CONNECT"...
  • Page 921 |17:00:49.052 UTC Thu Oct 14 2014 |17:01:04.953 UTC Thu Oct 14 2014 |-1 | | |40 |1 |0 (SRD_GW) |1 |1 |1 () |0 (MR_1) |no |BYE |Q.850 ;cause=16 ;text="loc |user 9928019 | Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 922: Cdr Fields For Sbc Media

    Mediant 1000B Gateway & E-SBC 57.2.1.2 CDR Fields for SBC Media The default CDR fields for SBC media are listed in the following table. The media CDRs are published for each active media stream, thereby allowing multiple media CDRs, where each media CDR has a unique call ID corresponding to the signaling CDR.
  • Page 923 Instead, the device sends the CDR field with the value 127, meaning that information is unavailable. RemoteRFactor 0 to 120 (127 if information is Remote conversation quality unavailable) Note: If the RTCP XR feature is Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 924: Cdr Fields For Sbc Local Storage

    Mediant 1000B Gateway & E-SBC CDR Field Range Description 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. LocalMosCQ 10 to 46 (127 if information is...

  • Page 925: Cdr Fields For Gateway Application

    "CALL_START": CDR is sent upon an INVITE message.  "CALL_CONNECT": CDR is sent upon a 200 OK response (i.e., call is established).  "CALL_END": CDR is sent upon a BYE message (i.e., call ends). Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 926 Mediant 1000B Gateway & E-SBC The CDR types and the SIP dialog stages are shown in the following figure: Figure 57-5: Gateway CDR Report Types Table 57-5: Default CDR Fields for Gateway Calls CDR Field Description GWReportType (CDR Report Type)
  • Page 927 Source number before manipulation Destination phone number type Destination phone number plan DstPhoneNum Destination phone number DstNumBeforeMap Destination number before manipulation Durat Call duration "CALL_END" Selected coder "CALL_CONNE Coder CT" and "CALL_END" Intrv Packet interval "CALL_END" Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 928 Mediant 1000B Gateway & E-SBC CDR Field Description GWReportType (CDR Report Type) RtpIp RTP IP address "CALL_END" Port Remote RTP port "CALL_END" TrmSd Initiator of call release (IP, Tel, or Unknown) "CALL_END" TrmReason SIP call termination reason (see ''Release Reasons in CDR "CALL_END"...
  • Page 929 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. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 930 Mediant 1000B Gateway & E-SBC CDR Field Description GWReportType (CDR Report Type) RemoteRFactor Remote R-factor "CALL_END" 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 931  "RELEASE_BECAUSE_FAIL"  "RELEASE_BECAUSE_FORWARD"  "RELEASE_BECAUSE_ANONYMOUS_SOURCE"  "RELEASE_BECAUSE_IP_PROFILE_CALL_LIMIT"  "GWAPP_UNASSIGNED_NUMBER"  "GWAPP_NO_ROUTE_TO_TRANSIT_NET"  "GWAPP_NO_ROUTE_TO_DESTINATION"  "GWAPP_CHANNEL_UNACCEPTABLE"  "GWAPP_CALL_AWARDED_AND "  "GWAPP_PREEMPTION"  "PREEMPTION_CIRCUIT_RESERVED_FOR_REUSE"  "GWAPP_NORMAL_CALL_CLEAR"  "GWAPP_USER_BUSY"  "GWAPP_NO_USER_RESPONDING"  "GWAPP_NO_ANSWER_FROM_USER_ALERTED"  "MFCR2_ACCEPT_CALL" Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 932 Mediant 1000B Gateway & E-SBC  "GWAPP_CALL_REJECTED"  "GWAPP_NUMBER_CHANGED"  "GWAPP_NON_SELECTED_USER_CLEARING"  "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" ...

  • Page 933: Cdr Fields For Gateway Local Storage

    Source phone number type Source phone number plan Source phone number SrcPhoneNum Source number before manipulation SrcNumBeforeMap Destination phone number type Destination phone number plan Destination phone number DstPhoneNum Destination number before manipulation DstNumBeforeMap Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 934 Mediant 1000B Gateway & E-SBC CDR Field Title Call duration Durat Selected coder Coder RTP IP address RtpIp Remote RTP port Port Initiator of call release TrmSd SIP call termination reason TrmReason Fax transaction during call Number of incoming packets...

  • Page 935: Customizing Cdrs For Gateway Calls

    CDRs (media and SIP signaling) sent in Syslog messages. For CDRs sent in Syslog messages, you can customize the name of CDR fields. The table lets you configure up to 128 Syslog CDR customization rules. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 936 Mediant 1000B Gateway & E-SBC  CDRs related to RADIUS accounting and sent in RADIUS accounting request messages. For RADIUS accounting CDRs, you can customize the RADIUS Attribute's prefix name and ID, for standard RADIUS Attributes and vendor-specific RADIUS Attributes (VSA). For example, instead of the default VSA name, "h323-connect-time"...
  • Page 937 Trunk Group ID; [504] Metering Pulses Generated; [505] Fax On Call; [506] Source Number Before Manipulation; [507] Source Number; [508] Source Number Type; [509] Source Number Plan; [510] Destination Number Before Manipulation; [511] Destination Number; [512] Destination Number Type; [513] Destination Number Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 938 Mediant 1000B Gateway & E-SBC Parameter Description Plan; [514] Redirect Number Before Manipulation; [515] Redirect Number; [526] Redirect Number Type; [527] Redirect Number Plan; [516] Source Host Name Before Manipulation; [517] Source Host Name; [518] Destination Host Name Before Manipulation; [519] Destination Host Name;...

  • Page 939: Customizing Cdrs For Sbc Calls

    CDRs (CDR fields, Local R Factor and Remote R Factor) generated by the device. Instead, these CDR fields are sent with the value 127, meaning that information is unavailable. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 940 Mediant 1000B Gateway & E-SBC The following procedure describes how to customize SBC-related CDRs through the Web interface. You can also configure it through ini file (SBCCDRFormat) or CLI (configure troubleshoot > cdr > cdr-format sbc-cdr-format).  To customize SBC-related CDRs: Open the SBC CDR Format table (Troubleshoot menu >...
  • Page 941 Defines a new name for the CDR field (for Syslog or local storage) or for the RADIUS Attribute prefix name (for RADIUS accounting) title that you selected in the 'Column Type' parameter. [SBCCDRFormat_Title] Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 942 Mediant 1000B Gateway & E-SBC Parameter Description The valid value is a string of up to 31 characters. You can configure the name to be enclosed by apostrophes (single or double). For example, if you want the CDR field name to appear as 'Phone Duration', you must configure the parameter to 'Phone Duration'.

  • Page 943: Configuring Cdr Reporting

    SUBSCRIBE, OPTIONS, and REGISTER), use the EnableNonCallCdr parameter. 57.2.5 Storing CDRs on the Device The CDRs of Gateway and SBC calls generated by the device can also be stored locally on the device (RAM). Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 944 Mediant 1000B Gateway & E-SBC Note: When the device is reset or powered off, locally stored CDRs are deleted. You can specify the calls (configuration entities) for which you wish to create CDRs and store locally. This is done using Logging Filter rules in the Logging Filters table. For example, you can configure a rule to create CDRs for traffic belonging only to IP Group 2 and store the CDRs locally.

  • Page 945: Configuring Radius Accounting

    57.3 Configuring RADIUS Accounting The device can send accounting data of SIP calls as call detail records (CDR) to a RADIUS Accounting server. CDR-based accounting messages can be sent upon call release, call Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 946 Mediant 1000B Gateway & E-SBC connection and release, or call setup and release. This section lists the CDR attributes for RADIUS accounting. The following figure shows the interface between the device and the RADIUS server, based on the RADIUS Accounting protocol. For each CDR that the device sends to the RADIUS server, it sends an Accounting-Request Stop with all the CDR attributes.
  • Page 947 RADIUS accounting messages are sent to the RADIUS accounting server. • From the 'AAA Indications' drop-down list (AAAIndications), select whether you want Authentication, Authorization and Accounting (AAA) indications. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 948 Mediant 1000B Gateway & E-SBC For a detailed description of the parameters, see ''RADIUS Parameters'' on page 1258. Figure 57-16: Configuring RADIUS Accounting Click Apply, and then reset the device with a save-to-flash for your settings to take effect. The table below lists the RADIUS Accounting CDR attributes included in the communication packets transmitted between the device and a RADIUS server.
  • Page 949 Stop call-terminator Terminator of the String call-terminator=yes Stop call:  "yes": Call terminated by the Tel side (Gateway) or outgoing leg (SBC)  "no": Call terminated by the IP side (Gateway) or Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 950 Mediant 1000B Gateway & E-SBC Vendor- Attribute Attribute Specific Value Description Example Name Attribute Format (VSA) ID incoming leg (SBC) terminator Terminator of the String terminator=originate Stop call:  "answer": Call originated from the IP side (Gateway) or incoming leg (SBC) ...
  • Page 951 = 1 acct-input-packets = 122 acct-output-packets = 220 called-station-id = 201 calling-station-id = 202 // Accounting non-standard parameters: (4923 33) h323-gw-id = (4923 23) h323-remote-address = 212.179.22.214 (4923 1) h323-ivr-out = h323-incoming-conf-id:02102944 600a1899 Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 952: Querying Device Channel Resources Using Sip Options

    Mediant 1000B Gateway & E-SBC 3fd61009 0e2f3cc5 (4923 30) h323-disconnect-cause = 22 (0x16) (4923 27) h323-call-type = VOIP (4923 26) h323-call-origin = Originate (4923 24) h323-conf-id = 02102944 600a1899 3fd61009 0e2f3cc5 57.4 Querying Device Channel Resources using SIP OPTIONS The device reports its maximum and available channel resources in SIP 200 OK responses upon receipt of SIP OPTIONS messages.

  • Page 953: Diagnostics

    Part X Diagnostics...

  • Page 955: Syslog And Debug Recording

    CDRs. Disabling a rule is useful, for example, if you no longer require the rule, but may need it in the future. Thus, instead of deleting the rule entirely, you can simply disable it. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 956 Mediant 1000B Gateway & E-SBC Note: • If you want to configure a Log Filter rule that logs Syslog messages to a 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 966).
  • Page 957 For example, to specify IP Groups 1, 3 and 9, configure the parameter to "1,3,9" (without apostrophes).  Trunks/FXO/FXS pertaining to a module, using the syntax module number/port or port, for example: Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 958 Mediant 1000B Gateway & E-SBC Parameter Description  "1/2" (without apostrophes), means module 1, port 2  "1/[2-4]" (without apostrophes), means module 1, ports 2 through 4  The exclamation (!) wildcard character can be used for excluding a specific configuration entity from the filter. For example, to...

  • Page 959: Filtering Ip Network Traces

    HTTP. When the IP Trace option is selected, only the ‘Value’ parameter is applicable; the 'Syslog' and 'Capture Type' parameters are not relevant. The 'Value' parameter configures the Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 960: Configuring Syslog

    Mediant 1000B Gateway & E-SBC Wireshark-like filtering expressions for your IP trace. The following Wireshark-like expressions are supported: Table 58-2: Supported Wireshark-like Expressions for 'Value' Parameter Expression Description ip.src, ip.dst Source and destination IP address ip.addr IP address - up to two IP addresses can be entered ip.proto...
  • Page 961 #0:DIGIT_EV [File: Line:-1] 18:38:14. 83 : 10.33.45.72 : NOTICE: [S=237][SID:2ed1c8:96:5] (lgr_flow)(621) #0:DIGIT_EV [File: Line:-1] 18:38:14.958 : 10.33.45.72 : NOTICE: [S=301][SID:2ed1c8:96:5] (lgr_flow)(625) #0:DIGIT_EV [File: Line:-1] You can disable the inclusion of the message sequence Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 962 Mediant 1000B Gateway & E-SBC Message Item Description number in Syslog messages, by setting the 'CDR Syslog Sequence Number' parameter to Disable (see ''Configuring Syslog'' on page 966). Log Number Ignore this number; it has been replaced by the Message (lgr)(number) Sequence Number (described previously).

  • Page 963: Event Representation In Syslog Messages

    Invalid CID Error Invalid G723 Code Invalid payload length Invalid RTCP Packet Invalid SID Length Transmitter Received Illegal Command Lost Fax Frames In High Speed Mode Lost Modem Frames In High Speed Mode Misalignment Error Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 964: Identifying Audiocodes Syslog Messages Using Facility Levels

    Unknown Aggregation Payload Type Invalid Routing Flag Received 58.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 965: Syslog Fields For Answering Machine Detection (Amd)

    Info1:/ Additional Info2:/ Additional Info3 The Messages’ Severity is as follows: Table 58-6: Syslog Message Severity ITU Perceived Severity AudioCodes' Syslog Severity (SNMP Alarm’s Severity) Critical RecoverableMsg Major RecoverableMsg Minor RecoverableMsg Warning Notice Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 966: Enabling Syslog

    Mediant 1000B Gateway & E-SBC ITU Perceived Severity AudioCodes' Syslog Severity (SNMP Alarm’s Severity) Indeterminate Notice Cleared Notice  Cleared Alarms: CLEAR-ALARM: <Alarm Name>; Textual Description: <Textual Description>; Severity <Alarm Severity>; Source <Alarm Source>; Unique ID: <Alarm Unique ID >; If exists Additional Info1:/ Additional Info2:/ Additional Info3: 58.2.2 Enabling Syslog...

  • Page 967: Configuring Reporting Of Management User Activities

    The following example shows a Web-user activity log (indicating a login action) with the above-mentioned information: 14:07:46.300 : 10.15.7.95 : Local 0 :NOTICE : [S=3149] [BID=3aad56:32] Activity Log: WEB: Successful login at 10.15.7.95:80. User: Admin. Session: HTTP (10.13.22.54) Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 968 Mediant 1000B Gateway & E-SBC The device can report the following user activities:  Modifications of individual parameters, for example: 14:33:00.162 : 10.15.7.95 : Local 0 :NOTICE : [S=3403] [BID=3aad56:32] Activity Log: Max Login Attempts was changed from '3' to '2'. User: Admin. Session: HTTP (10.13.22.54) ...

  • Page 969: 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 970: Configuring Debug Recording

    You can select the Syslog messages displayed on the 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. 58.3 Configuring Debug Recording This section describes how to configure debug recording and how to collect debug recording packets.

  • Page 971: Collecting Debug Recording Messages

    Click Apply. 58.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. Note: • The default debug recording port is 925. You can change the port in Wireshark (Edit menu >...

  • Page 972: Debug Capturing On Physical Voip Interfaces

    Mediant 1000B Gateway & E-SBC The device adds the header "AUDIOCODES DEBUG RECORDING" to each debug recording message, as shown below: 58.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 973: 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.2 Mediant 1000B Gateway & E-SBC...
  • Page 974 Mediant 1000B Gateway & E-SBC This page is intentionaly left blank. User's Manual Document #: LTRT-27055...

  • Page 975: Debugging Web Services

    Open the Web Service Settings page (Setup menu > IP Network tab > Web Services folder > Web Service Settings). In the 'Debug Level' field (RestDebugMode), enter the debug level (or disable debugging by configuring it to 0): Click Apply. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 976 Mediant 1000B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-27055...

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

    The files may assist you in identifying the cause of the 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 978 Mediant 1000B Gateway & E-SBC You can also delete the core dump file through CLI, as described in the following procedure:  To delete the core dump file:  Navigate to the root CLI directory (enable mode), and then enter the following...

  • Page 979: Analog Line Testing

    Access the FXS interface command set: (config-voip)# interface fxs-fxo Type the following command: (fxs-fxo)# fxs-line-testing < Module/Port > {66|70} For example, to test FXS port 4 on FXS module 1 with coefficient type USA: (fxs-fxo)# fxs-line-testing 1/4 70 Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 980: Fxo Line Testing

    Mediant 1000B Gateway & E-SBC 62.2 FXO Line Testing The device can test the telephone lines connected to its FXO ports through SNMP using the SNMP acAnalogFxoLineTestTable table. The tests provide various line measurements. In addition to the tests, a keep-alive test is also done every 100 msec on each of the analog ports to detect communication problems with the analog equipment: ...

  • Page 981: Testing Sip Signaling Calls

    You can also configure it through ini file (Test_Call) or CLI (configure troubleshoot > test- call test-call-table).  To configure a test call: Open the Test Call Rules table (Troubleshooting tab > Troubleshooting menu > Test Call folder > Test Call Rules). Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 982 Mediant 1000B Gateway & E-SBC Click New; the following dialog box appears: Figure 63-1: Test Call Rules Table - Add Dialog Box Configure a test call according to the parameters described in the table below. Click Apply, and then save your settings to flash memory.
  • Page 983 Defines the transport type for outgoing calls.  dst-transport [-1] = Not configured (default)  [0] UDP [Test_Call_DestTransportType]  [1] TCP  [2] TLS Note: The parameter is applicable only if the 'Route By' parameter Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 984 Mediant 1000B Gateway & E-SBC Parameter Description is set to Dest Address. QoE Profile Assigns a QoE Profile to the test call. qoe-profile By default, no value is defined. [Test_Call_QOEProfile] To configure QoE Profiles, see ''Configuring Quality of Experience Profiles'' on page 315.
  • Page 985 Defines the interval (in minutes) between automatic outgoing test calls. schedule-interval The valid value range is 0 to 100000. The default is 0 (i.e., [Test_Call_ScheduleInterval] scheduling is disabled). Note: The parameter is applicable only if you configure 'Call Party' to Caller. Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 986: Starting And Stopping Test Calls

    Mediant 1000B Gateway & E-SBC 63.2 Starting and Stopping Test Calls The following procedure describes how to start, stop, and restart test calls.  To start, stop, and restart a test call: In the Test Call Rules table, select the required test call entry.

  • Page 987: Viewing Test Call Statistics

    Remote Disconnections Count Average CPS Average calls per second. Elapsed Time Duration of the test call since it was started (or restarted). Status (brief description) as displayed in the 'Test Status' field Test Status Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 988 Mediant 1000B Gateway & E-SBC Statistics Field Description (see ''Viewing Test Call Status'' on page 986). Detailed Status Displays a detailed description of the test call status:  "Idle": Test call is currently not active.  "Scheduled - Established Calls: <number of established calls>, ASR: <ASR>%": Test call is planned to run...

  • Page 989: Configuring Dtmf Tones For Test Calls

    The figure below displays a basic test call example: Figure 63-4: Incoming Test Call Example  To configure basic call testing: Open the Test Call Settings page (Troubleshooting tab > Troubleshooting menu > Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 990 Mediant 1000B Gateway & E-SBC Test Call folder > Test Call Settings). In the 'Test Call ID' field, enter a prefix for the simulated endpoint: Figure 63-5: Configuring Basic Test Calls Click Apply. Note: • The device can play DTMF tones to the remote endpoint. For more information, see Configuring DTMF Tones for Test Calls on page 989.

  • Page 991: Test Call Configuration Examples

    Call Party: Caller • Tel-to-IP Routing table configuration: ♦ Destination Phone Prefix: 201 (i.e., the Called URI user-part) ♦ Source Phone Prefix: 101 (i.e., the Endpoint URI user-part) ♦ Destination IP Address: 10.30.40.1 Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 992 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 993 Route By: Dest Address ♦ Destination Address: "10.13.4.12" (this is the IP address of the device itself) ♦ SIP Interface: SIPInterface_0 ♦ Auto Register: Enable ♦ User Name: "testuser" ♦ Password: "12345" ♦ Call Party: Caller Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 994 Mediant 1000B Gateway & E-SBC This page is intentionaly left blank. User's Manual Document #: LTRT-27055...

  • Page 995: 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] interface For a complete description of the ping command, refer to the CLI Reference Guide. Version 7.2 Mediant 1000B Gateway & E-SBC...
  • Page 996 Mediant 1000B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-27055...

  • Page 997: Appendix

    Part XI Appendix...

  • Page 999: Configuration Parameters Reference

    (i.e., the device [WebAccessList_x] can be accessed from any IP address). The default is 0.0.0.0 (i.e., the device can be accessed from any IP address). For example: Version 7.2 Mediant 1000B Gateway & E-SBC...

  • Page 1000: Web Parameters

    Mediant 1000B Gateway & E-SBC Parameter Description 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 82. Local Users Table Local Users The table defines management users. configure system >...
  • Page 1001 The valid value is 0 to 100000, where 0 means that login is not denied regardless of number of failed login attempts. The default is 60. Display Last Login Information Enables display of user's login information on each successful login attempt. [DisplayLoginInformation] Version 7.2 1001 Mediant 1000B Gateway & E-SBC...
  • Page 1002 Mediant 1000B Gateway & E-SBC Parameter Description  [0] Disable (default)  [1] Enable [EnableMgmtTwoFactorAuthentication] Enables Web login authentication using a third-party, smart card.  [0] = Disable (default)  [1] = Enable When enabled, the device retrieves the Web user’s login username from the smart card, which is automatically displayed (read-only) in the Web Login screen;...
  • Page 1003 69. [UserProductName] Defines a name for the device instead of the default name. The value can be a string of up to 29 characters. For more information, see Customizing the Product Name Version 7.2 1003 Mediant 1000B Gateway & E-SBC...
  • Page 1004 Mediant 1000B Gateway & E-SBC Parameter Description on page 69. Note: To enable customization of the device name, see the UseProductName parameter. [UseWebLogo] Defines whether the Web interface displays a logo image or text.  [0] = (Default) The Web interface displays a logo image, configured by the LogoFileName parameter.

  • Page 1005: Telnet Parameters

    “—MORE—" prompt is displayed (at which you can press the spacebar to display the next four output lines). Note: You can override this parameter for a specific CLI session Version 7.2 1005 Mediant 1000B Gateway & E-SBC...

  • Page 1006: Ini File Parameters

    > snmp trap > auto- Enables the device to send NAT keep-alive traps to the port send-keep-alive of the SNMP network management station (e.g., AudioCodes EMS). This is used for NAT traversal, and allows SNMP [SendKeepAliveTrap] communication with AudioCodes EMS management platform,...
  • Page 1007 Entry Limit MIB (located in the Notification Log MIB). The valid range is 50 to 1000. The default is 500. Note: For the parameter to take effect, a device reset is required. Version 7.2 1007 Mediant 1000B Gateway & E-SBC...
  • Page 1008 Mediant 1000B Gateway & E-SBC Parameter Description [ActiveAlarmTableMaxSize] Defines the maximum number of currently active alarms that can be displayed in the Active Alarms table. When the table reaches this user-defined maximum capacity (i.e., full), the device sends the SNMP trap event, acActiveAlarmTableOverflow.
  • Page 1009 SNMP V3 Users The table defines SNMP v3 users. configure system > snmp v3-users The format of the ini file table parameter is: [SNMPUsers] [SNMPUsers] FORMAT SNMPUsers_Index = SNMPUsers_Username, SNMPUsers_AuthProtocol, SNMPUsers_PrivProtocol, SNMPUsers_AuthKey, SNMPUsers_PrivKey, Version 7.2 1009 Mediant 1000B Gateway & E-SBC...

  • Page 1010: Serial Parameters

    Mediant 1000B Gateway & E-SBC Parameter Description SNMPUsers_Group; [\SNMPUsers] For example: SNMPUsers 1 = v3admin1, 1, 0, myauthkey, -, 1; The example above configures user 'v3admin1' with security level authNoPriv(2), authentication protocol MD5, authentication text password 'myauthkey', and ReadWriteGroup2. For more information, see ''Configuring SNMP V3 Users'' on page 98.

  • Page 1011: Auxiliary And Configuration File Name Parameters

    CAS files by repeating the parameter. Each CAS file can be associated with one or more of the device's trunks, using the parameter CASTableIndex or it can be associated per B-channel using the parameter CASChannelIndex. Version 7.2 1011 Mediant 1000B Gateway & E-SBC...

  • Page 1012: 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'.

Table of Contents