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

AudioCodes Mediant 800 User Manual

Gateways & session border controllers
Hide thumbs Also See for Mediant 800:
1
2
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: Configuration Manual , Installation Manual
User's Manual
AudioCodes Series of Gateways & Session Border Controllers
Mediant 800 Gateway &
E-SBC
Version 7.2

Advertisement

Table of Contents
loading

Related Manuals for AudioCodes Mediant 800

Summary of Contents for AudioCodes Mediant 800

  • Page 1 User's Manual AudioCodes Series of Gateways & Session Border Controllers Mediant 800 Gateway & E-SBC Version 7.2...
  • Page 2 Please contact your local recycling authority for disposal of this product. 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 contact...
  • Page 3 If any open source software is provided in object code, and its accompanying license requires that it be provided in source code as well, Buyer may receive such source code by contacting AudioCodes , by following the instructions available on AudioCodes website.
  • Page 4 Notice Mediant 800 Gateway & E-SBC | User's Manual Document Name Utility Guides INI Viewer & Editor Utility User's Guide DConvert User's Guide CLI Wizard User's Guide Document Revision Record LTRT Description 10297 Initial document release for Version 7.2. 10298 ■...
  • Page 5 Notice Mediant 800 Gateway & E-SBC | User's Manual LTRT Description ■ Updated parameters: TLSContexts_TLSVersion; InterfaceTable_ InterfaceName; IPGroup_MediaRealm (Web name); CallSetupRules_ AttributesToQuery (Web name); IPProfile_SBCIceMode (value); IPProfile_SBCRTCPFeedback (values); IpProfile_ MediaIPVersionPreference; ForwardOnBusyTrunkDest_ ForwardDestination (note); ConditionTable_Name (max. chars); Test_ Call_RouteBy (default, values); CLIPrivPass; NATMode (values);...
  • Page 6 Notice Mediant 800 Gateway & E-SBC | User's Manual LTRT Description ■ Updated sections: CLI (telnet removed); Areas of the GUI (SBC Wizard); Assigning Rows from Other Tables (search, add new, and view); Invalid Value Indications; Creating a Login Welcome Message;...
  • Page 7 Notice Mediant 800 Gateway & E-SBC | User's Manual LTRT Description 10626 ■ Updated sections: Configuring VoIP LAN Interface for OAMP (CLI); Configuring Management User Accounts (typo);  Enabling SNMP; Configuring IP Network Interfaces; SIP-based Media Recording (multiple SRS); Configuring LDAP Servers (max. and cache);...
  • Page 8 Notice Mediant 800 Gateway & E-SBC | User's Manual LTRT Description ■ Updated sections: Areas of the GUI (Configuration Wizard button); Enabling Disabling SNMP; Viewing Certificate Information (screen); Assigning Externally Created Private Keys to TLS Contexts (pass- phrase); Generating Private Keys for TLS Contexts (pass-phrase);...
  • Page 9 Notice Mediant 800 Gateway & E-SBC | User's Manual LTRT Description ■ Updated sections: Configuring the LDAP Search Filter Attribute (Web path); Enabling LDAP Searches for Numbers with Characters; Microsoft Skype for Business Presence of Third-Party Endpoints; Configuring the Device for Skype for Business Presence (example);...
  • Page 10 Notice Mediant 800 Gateway & E-SBC | User's Manual LTRT Description ■ Updated sections: Configuring Management User Accounts; Device Located behind NAT; Configuring a Static NAT IP Address for All Interfaces (removed); SIP-based Media Recording (URL of France reg.; note on SRS redundancy); Configuring SIP Recording Rules (note re timestamp);...
  • Page 11 Notice Mediant 800 Gateway & E-SBC | User's Manual LTRT Description ■ Updated sections: Replacing the Corporate Logo with an Image (logo width removed); Replacing the Corporate Logo with Text; Customizing the Favicon (default); Creating a Login Welcome Message (no reset);...
  • Page 12 Notice Mediant 800 Gateway & E-SBC | User's Manual LTRT Description ■ Updated Sections: Default OAMP IP Address; Configuring Management User Accounts (max.); Assigning CSR-based Certificates to TLS Contexts (SAN); Creating Self-Signed Certificates for TLS Contexts (SAN); DNS; Configuring Remote Web Services (Capture removed);...
  • Page 13 Notice Mediant 800 Gateway & E-SBC | User's Manual LTRT Description ■ New Parameters: SRD_AdmissionProfile; MessageManipulations_ ActionSubject SIPInterface_AdmissionProfile; IPGroup_ AdmissionProfile; PREFIX_DestTags; PREFIX_SrcTags; PstnPrefix_ SrcTags; PstnPrefix_DestTags; SBCAdmissionRule_ MaxBurstPerUser; Rate Per User; GWUserInfoFileUrl; SBCUserInfoFileUrl; UserInfoFileURL; ConfPackageURL; DefaultPrimaryDnsServerIp; DefaultSecondaryDnsServerIp; MaxStreamingCalls; GWUserInfoTable; Tel2IPDialPlanName; IP2TelDialPlanName; SBCAdmissionProfile; SBCAdmissionRule;...
  • Page 14 Notice Mediant 800 Gateway & E-SBC | User's Manual LTRT Description ■ Updated Parameters: SNMPUsers_PrivProtocol (4 and 5 removed); InterfaceTable_InterfaceName (default); "Prefix" replaced with "Pattern" for Web parameters and CLI commands and descriptions updated; CpMediaRealm_MediaRealmName (range); CpMediaRealm_ PortRangeStart (note); MediaRealmExtension_PortRangeStart (note);...
  • Page 15 Notice Mediant 800 Gateway & E-SBC | User's Manual LTRT Description ■ Updated Parameters: EtherGroupTable_Mode; HTTPRemoteServices_ HTTPType (8); HTTPRemoteServices_Policy; HTTPRemoteServices_ PersistentConnection; HTTPRemoteServices_NumOfSockets (removed); HTTPRemoteServices_LoginNeeded (removed); IPGroup_ Tags; ProxySet_EnableProxyKeepAlive; ProxySet_ ProxyRedundancyMode; ProxySet_IsProxyHotSwap; ProxySet_ ProxyLoadBalancingMethod; ProxySet_DNSResolveMethod; CallSetupRules_RulesSetID; CallSetupRules_QueryType (4); CallSetupRules_QueryTarget; TelProfile_EnableDigitDelivery (no reset);...
  • Page 16 Notice Mediant 800 Gateway & E-SBC | User's Manual LTRT Description 10782 ■ Updated sections: Configuring Voice Mail; Call Processing of SIP Dialog Requests; RADIUS-based Management User Authentication (CLI); Enabling LDAP-based Web/CLI User Login Authentication and Authorization; Media Cluster (time); Collecting Debug Recording Messages;...
  • Page 17 Notice Mediant 800 Gateway & E-SBC | User's Manual LTRT Description ■ Updated parameters: CliScriptURL (typo); CLIStartupScriptUrl (typo); AccessList_Protocol ("sip" removed); IDSRule_Reason (CAC, exclusion of SIP cause codes); IPGroup_SIPConnect (options and descriptions); IPGroup_MethodList ("setup-invite"); IpProfile_ SBCRemote3xxBehavior (new options 3 and 4); IPProfile_ LocalRingbackTone (PRT userdefine);...
  • Page 18 Notice Mediant 800 Gateway & E-SBC | User's Manual LTRT Description ■ Updated sections: Accessing Files on Redundant Device from Active through SSH (note added); Areas of the GUI (password on toolbar and hostname); Assigning CSR-based Certificates to TLS Contexts;...
  • Page 19 Notice Mediant 800 Gateway & E-SBC | User's Manual LTRT Description ■ New parameters: MatrixCsvFileUrl; IpProfile_ CreatedByRoutingServer; HTTPRemoteServices_LoginNeeded; HTTPRemoteServices_VerifyCertificateSubjectName; Test_Call_ OfferedCodersGroupName; Test_Call_ AllowedAudioCodersGroupName; Test_Call_AllowedCodersMode; Test_Call_MediaSecurityMode; Test_Call_PlayDTMFMethod; Test_ Call_MediaSecurityMode; QOESettings_ VerifyCertificateSubjectName; Hostname; HAMaintenanceIFDiffServValue; HAOperationalStateDelayInSec; ShortCallSeconds; FXSOffhookTimeoutAlarm; SyslogLogLevel; CallEndCDRSIPReasonsFilter; CallEndCDRZeroDurationFilter; KeyPortConfigure; CLIEnableModePassword; CliObscuredPassword ■...

  • Page 20: Table Of Contents

    Content Mediant 800 Gateway & E-SBC | User's Manual Table of Contents 1 Introduction Product Overview Typographical Conventions Getting Familiar with Configuration Concepts and Terminology SBC Application Gateway Application Part I Getting Started with Initial Connectivity 2 Introduction 3 Default IP Address...
  • Page 21 Content Mediant 800 Gateway & E-SBC | User's Manual Replacing the Corporate Logo with Text Restoring the Default Corporate Logo Image Customizing the Browser Tab Label Customizing the Product Name Customizing the Favicon Creating a Login Welcome Message Configuring Additional Management Interfaces...
  • Page 22 Content Mediant 800 Gateway & E-SBC | User's Manual Loading an ini File to the Device Secured Encoded ini File Configuring Password Display in ini File INI Viewer and Editor Utility 10 REST-Based Management Part III General System Settings 11 Date and Time...
  • Page 23 Content Mediant 800 Gateway & E-SBC | User's Manual Configuring Native VLAN for OSN Server Disabling Internal Switch Port for OSN IP Multicasting 14 Security Configuring SSL/TLS Certificates Configuring TLS Certificate Contexts Assigning CSR-based Certificates to TLS Contexts Viewing Certificate Information...
  • Page 24 Content Mediant 800 Gateway & E-SBC | User's Manual Simultaneous Negotiation of Fax (T.38) and Modem (V.150.1) Relay V.152 Support Configuring RTP/RTCP Settings Configuring the Dynamic Jitter Buffer Comfort Noise Generation Configuring DTMF Transport Types Configuring RFC 2833 Payload Configuring RTP Base UDP Port...
  • Page 25 Content Mediant 800 Gateway & E-SBC | User's Manual RADIUS-based CDR Accounting LDAP-based Management and SIP Services Enabling the LDAP Service Enabling LDAP-based Web/CLI User Login Authentication and Authorization Configuring LDAP Server Groups Configuring LDAP Servers Configuring LDAP DNs (Base Paths) per LDAP Server...
  • Page 26 Gathering Location Information of Skype for Business Clients for 911 Calls Adding ELINs to the Location Information Server Passing Location Information to the PSTN Emergency Provider AudioCodes ELIN Device for Skype for Business E9-1-1 Calls to PSTN Detecting and Handling E9-1-1 Calls Pre-empting Existing Calls for E9-1-1 Calls...
  • Page 27 Content Mediant 800 Gateway & E-SBC | User's Manual 19 Coders and Profiles Configuring Coder Groups Supported Audio Coders Configuring Various Codec Attributes Configuring Allowed Audio Coder Groups Configuring Allowed Video Coder Groups Configuring IP Profiles Configuring Tel Profile 20 SIP Definitions...
  • Page 28 Content Mediant 800 Gateway & E-SBC | User's Manual Part V Gateway Application 22 Introduction Call Processing Summary 23 Digital PSTN Configuring Trunk Settings TDM and Timing TDM Bus Clock Settings Recovering Clock from PSTN Line Interface Configuring Internal Clock as Clock Source...
  • Page 29 Content Mediant 800 Gateway & E-SBC | User's Manual Alternative Routing from FXO to IP 26 Manipulation Configuring Redirect Reasons Configuring Source-Destination Number Manipulation Rules Manipulating Number Prefix SIP Calling Name Manipulations Configuring Redirect Number Manipulation Manipulating Redirected and Diverted Numbers for Call Diversion...
  • Page 30 Content Mediant 800 Gateway & E-SBC | User's Manual Message Waiting Indication Caller ID Enabling Caller ID Generation and Detection on Tel Side Debugging a Caller ID Detection on FXO Caller ID on the IP Side Three-Way Conferencing Emergency E911 Phone Number Services...
  • Page 31 Content Mediant 800 Gateway & E-SBC | User's Manual Calls Termination by PBX Call Termination before Call Establishment Ring Detection Timeout Remote PBX Extension between FXO and FXS Devices Dialing from Remote Extension (Phone at FXS) Dialing from PBX Line or PSTN...
  • Page 32 Content Mediant 800 Gateway & E-SBC | User's Manual OAuth2-based User Authentication Interworking SIP Signaling Interworking SIP 3xx Redirect Responses Resultant INVITE Traversing Device Local Handling of SIP 3xx Interworking SIP Diversion and History-Info Headers Interworking SIP REFER Messages Interworking SIP PRACK Messages...
  • Page 33 Content Mediant 800 Gateway & E-SBC | User's Manual Configuring Dual Registration for SIP Entity Handling Registered AORs with Same Contact URIs Enabling Interworking of SIP and SIP-I Endpoints Configuring SBC MoH from External Media Source WebRTC SIP over WebSocket...
  • Page 34 Content Mediant 800 Gateway & E-SBC | User's Manual Step 3: Initialize HA on the Devices Quick-and-Easy Initial HA Configuration Configuration while HA is Operational Configuring Firewall Allowed Rules Configuring DiffServ for HA Maintenance Traffic Monitoring IP Entities and HA Switchover upon Ping Failure...
  • Page 35 Content Mediant 800 Gateway & E-SBC | User's Manual 47 License Key Viewing the License Key Obtaining License Key for Initial Activation Local License Key Installing License Key through Web Interface Installing a License Key String Installing a License Key File...
  • Page 36 Content Mediant 800 Gateway & E-SBC | User's Manual Starting the SBC Configuration Wizard General Setup Page System Page Interfaces Page IP-PBX Page SIP Trunk Page Number Manipulation Page Remote Users Page Summary Page Congratulations Page 52 Restoring Factory Defaults...
  • Page 37 Content Mediant 800 Gateway & E-SBC | User's Manual 59 Viewing PSTN Status 1022 Viewing Trunks & Channels Status 1022 Viewing NFAS Groups and D-Channel Status 1023 60 Viewing Network Status 1025 Viewing Active IP Interfaces 1025 Viewing Ethernet Device Status...
  • Page 38 Content Mediant 800 Gateway & E-SBC | User's Manual Collecting Debug Recording Messages 1116 Debug Capturing on Physical VoIP Interfaces 1116 Debug Capturing on VoIP Interfaces 1117 63 Self-Testing 1119 64 Creating Core Dump and Debug Files upon Device Crash...
  • Page 39 Content Mediant 800 Gateway & E-SBC | User's Manual Quality of Service Parameters 1179 NAT and STUN Parameters 1180 DNS Parameters 1182 DHCP Parameters 1183 NTP and Daylight Saving Time Parameters 1184 Debugging and Diagnostics Parameters 1186 General Parameters 1186...
  • Page 40 Content Mediant 800 Gateway & E-SBC | User's Manual General Parameters 1333 TDM Bus and Clock Timing Parameters 1337 CAS Parameters 1340 ISDN Parameters 1342 ISDN and CAS Interworking Parameters 1345 Tone Parameters 1360 Telephony Tone Parameters 1360 Tone Detection Parameters...

  • Page 41: Introduction

    Gateway & E-SBC (hereafter, referred to as device). Product Overview The Mediant 800 Gateway & E-SBC (hereafter referred to as device) offers a complete connectivity solution for small-to-medium sized enterprises. The device connects IP-PBXs to any SIP trunking service provider. It offers superior performance in connecting any SIP to SIP environment, legacy TDM-based PBX systems to IP networks, and IP-PBXs to the PSTN.

  • Page 42: Getting Familiar With Configuration Concepts And Terminology

    CHAPTER 1    Introduction Mediant 800 Gateway & E-SBC | User's Manual Table 1-1: Typographical Conventions Convention Description Example Text enclosed by a Indicates Web interface parameters. From the 'Debug Level' single apostrophe drop-down list, select '...' Basic. Boldface font Indicates one of the following Web-based Click the Add button.
  • Page 43 CHAPTER 1    Introduction Mediant 800 Gateway & E-SBC | User's Manual Table 1-2: Configuration Concepts and Terminology Configuration Description Terms IP Group The IP Group is a logical representation of the SIP entity (UA) with which the device receives and sends calls. The SIP entity can be a server (e.g., IP PBX or SIP Trunk) or it can be a group of users (e.g., LAN IP phones).
  • Page 44 CHAPTER 1    Introduction Mediant 800 Gateway & E-SBC | User's Manual Configuration Description Terms 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 means whether the SRD's resources (SIP Interfaces, IP Groups, and Proxy Sets) can be used by other SRDs.
  • Page 45 CHAPTER 1    Introduction Mediant 800 Gateway & E-SBC | User's Manual Configuration Description Terms Inbound manipulation lets you manipulate the user part of the SIP URI for source (e.g., in the SIP From header) and destination (e.g., in the Request- URI line) in the incoming SIP dialog request. Outbound manipulation lets you manipulate the user part of the Request-URI for source (e.g., in the SIP From...

  • Page 46: Gateway Application

    CHAPTER 1    Introduction Mediant 800 Gateway & E-SBC | User's Manual The main configuration entities and their involvement in the call processing is summarized in following figure. The figure is used only as an example to provide basic understanding of the configuration terminology.
  • Page 47 CHAPTER 1    Introduction Mediant 800 Gateway & E-SBC | User's Manual The following table describes the main configuration concepts and terminology. Table 1-3: Configuration Concepts and Terminology Configuration Terms Description IP Groups The IP Group is a logical representation of the SIP entity (UA) with which the device receives and sends calls.
  • Page 48 CHAPTER 1    Introduction Mediant 800 Gateway & E-SBC | User's Manual Configuration Terms Description IP Profiles The IP Profile is an optional configuration entity that defines a wide range of call settings for a specific SIP entity (IP Group). The IP...

  • Page 49: Part I

    Part I Getting Started with Initial Connectivity...

  • Page 50: Introduction

    CHAPTER 2    Introduction Mediant 800 Gateway & E-SBC | User's Manual 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. - 10 -...

  • Page 51: Default Ip Address

    CHAPTER 3    Default IP Address Mediant 800 Gateway & E-SBC | User's Manual Default IP Address The device is shipped with a factory default networking address for operations, administration, maintenance, and provisioning (OAMP), through its LAN interface, as shown in the table below.

  • Page 52: Configuring Voip Lan Interface For Oamp

    CHAPTER 4    Configuring VoIP LAN Interface for OAMP Mediant 800 Gateway & E-SBC | User's Manual Configuring VoIP LAN Interface for OAMP You can change the device's default OAMP IP address, using any of the following methods: ■ Embedded HTTP/S-based Web server (see Web Interface) ■...

  • Page 53: Changing Oamp Address Through Cli

    CHAPTER 4    Configuring VoIP LAN Interface for OAMP Mediant 800 Gateway & E-SBC | User's Manual In the 'Username' and 'Password' fields, enter the case-sensitive, default login username ("Admin") and password ("Admin"). Click Log In. Configure the Ethernet port(s) that you want to use for the OAMP interface: In the Ethernet Groups table, configure an Ethernet Group by assigning it up to two ports (two ports provide optional, port-pair redundancy).
  • Page 54 CHAPTER 4    Configuring VoIP LAN Interface for OAMP Mediant 800 Gateway & E-SBC | User's Manual ➢ To configure the OAMP IP address through CLI: Connect the RS-232 port of the device to the serial communication port on your computer. For more information, refer to the Hardware Installation Manual.

  • Page 55: Changing Oamp Address Through Ini File

    CHAPTER 4    Configuring VoIP LAN Interface for OAMP Mediant 800 Gateway & E-SBC | User's Manual (network-if-0)# ip-address <IP address> Configure the prefix length: (network-if-0)# prefix-length <prefix length / subnet mask, e.g., 16> Configure the Default Gateway address: (network-if-0)# gateway <IP address>...

  • Page 56: Management Tools

    Part II Management Tools...

  • Page 57: Introduction

    CHAPTER 5    Introduction Mediant 800 Gateway & E-SBC | User's Manual Introduction This part describes the various management tools that you can use to configure the device: ■ Embedded HTTP/S-based Web server - see Web-based Management ■ Embedded Command Line Interface (CLI) - see CLI-Based Management ■...

  • Page 58: Web-Based Management

    CHAPTER 6    Web-Based Management Mediant 800 Gateway & E-SBC | User's Manual Web-Based Management The device provides an embedded Web server (hereafter referred to as Web interface), supporting fault management, configuration, accounting, performance, and security (FCAPS). The Web interface provides a user-friendly, graphical user interface (GUI), which can be accessed using any standard Web browser.

  • Page 59: Areas Of The Gui

    CHAPTER 6    Web-Based Management Mediant 800 Gateway & E-SBC | User's Manual In the 'Username' and 'Password' fields, enter the username and password, respectively. If you want the Web browser to remember your username, select the 'Remember Me' check box and then agree to the browser's prompt (depending on your browser). On your next login attempt, the 'Username' field is automatically populated with your username.
  • Page 60 CHAPTER 6    Web-Based Management Mediant 800 Gateway & E-SBC | User's Manual Table 6-1: Description of the Web GUI Areas Item# Description Company logo. To customize the logo, see Replacing the Corporate Logo. If you click the logo, the Topology View page opens (see...
  • Page 61 CHAPTER 6    Web-Based Management Mediant 800 Gateway & E-SBC | User's Manual Item# Description ✔ Configuration Wizard: Opens the SBC Configuration Wizard, which is used for quick-and-easy configuration of the device (see SBC Configuration Wizard). Alarm bell icon displaying the number of active alarms generated by the device. The color of the number indicates the highest severity of an active alarm.

  • Page 62: Accessing Configuration Pages From Navigation Tree

    CHAPTER 6    Web-Based Management Mediant 800 Gateway & E-SBC | User's Manual Item# Description ✔ IP Network tab ✔ Signaling & Media tab ✔ Administration tab ■ Monitor menu: Monitor tab ■ Troubleshoot menu: Troubleshoot tab SRD filter. When your configuration includes multiple SRDs, you can filter tables in the Web interface by SRD.
  • Page 63 CHAPTER 6    Web-Based Management Mediant 800 Gateway & E-SBC | User's Manual ● 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 64: Configuring Stand-Alone Parameters

    CHAPTER 6    Web-Based Management Mediant 800 Gateway & E-SBC | User's Manual Depending on the access level (e.g., Monitor level) of your Web user account, certain pages may not be accessible or may be read-only (see Configuring Management User Accounts). For read-only privileges: ●...

  • Page 65: Configuring Table Parameters

    CHAPTER 6    Web-Based Management Mediant 800 Gateway & E-SBC | User's Manual 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. Click Reset; the device saves the changes to flash memory and then resets.

  • Page 66: Adding Table Rows

    CHAPTER 6    Web-Based Management Mediant 800 Gateway & E-SBC | User's Manual Item# Button Description Adds a new row to the table (see Adding Table Rows). Modifies the selected row (see Modifying Table Rows). Adds a new row with similar settings as the selected row (i.e., clones the row).

  • Page 67: Assigning Rows From Other Tables

    CHAPTER 6    Web-Based Management Mediant 800 Gateway & E-SBC | User's Manual 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 68: Modifying Table Rows

    CHAPTER 6    Web-Based Management Mediant 800 Gateway & E-SBC | User's Manual The table (e.g., IP Groups table) and dialog box in which the Add new option was selected is minimized to the bottom-left corner of the Web interface and a dialog box appears for adding a new row in the referenced-table (e.g., Proxy Sets table).

  • Page 69: Invalid Value Indications

    CHAPTER 6    Web-Based Management Mediant 800 Gateway & E-SBC | User's Manual Click Yes, Delete; the row is removed from the table and the total number of configured rows that is displayed next to the page title and page item in the Navigation tree is updated to reflect the deletion.
  • Page 70 CHAPTER 6    Web-Based Management Mediant 800 Gateway & E-SBC | User's Manual ■ Parameters that reference rows of other configuration tables that are configured with invalid values: If a row has a parameter that references a row of another table that has a...

  • Page 71: Viewing Table Rows

    CHAPTER 6    Web-Based Management Mediant 800 Gateway & E-SBC | User's Manual 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 auto- matically changes to an empty field (i.e., no row assigned).

  • Page 72: Changing Index Position Of Table Rows

    CHAPTER 6    Web-Based Management Mediant 800 Gateway & E-SBC | User's Manual To sort the column in descending order, click the column name again; only the down arrow is displayed in a darker shade of color, indicating that the column is sorted in descending order: Changing Index Position of Table Rows You can change the position (index) of rows in tables.

  • Page 73: Searching For Configuration Parameters

    CHAPTER 6    Web-Based Management Mediant 800 Gateway & E-SBC | User's Manual Table 6-4: Table Search Tool Description Item# Description 'Specify Columns' drop-down list for selecting the table column (parameter) in which to do the search. By default, the search is done in all columns.

  • Page 74: Getting Help

    CHAPTER 6    Web-Based Management Mediant 800 Gateway & E-SBC | User's Manual The search key can include only alphanumerics, periods, and spaces. The use of other characters are invalid. ➢ To search for a parameter: In the search box, enter the search key (parameter name or value).

  • Page 75: Customizing The Web Interface

    SDP "o" line (see the SIPSDPSessionOwner parameter), and Subject header (see the SIPSubject parameter). 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: ■...

  • Page 76: Replacing The Corporate Logo With An Image

    CHAPTER 6    Web-Based Management Mediant 800 Gateway & E-SBC | User's Manual You can replace the logo with one of the following: ■ A different image (see Replacing the Corporate Logo with an Image) ■ Text (see Replacing the Corporate Logo with...

  • Page 77: Restoring The Default Corporate Logo Image

    You can customize the label that appears on the tab of the Web browser that you use to open the device's Web interface. By default, the tab displays "AudioCodes". You can change this to display either the IP address of the device or any customized text.

  • Page 78: Customizing The Product Name

    CHAPTER 6    Web-Based Management Mediant 800 Gateway & E-SBC | User's Manual If you have never configured the WebLogoText parameter, you can omit it from the ini file. If you have configured it before, then set it to an empty value, as shown above.

  • Page 79: Customizing The Favicon

    CHAPTER 6    Web-Based Management Mediant 800 Gateway & E-SBC | User's Manual UseProductName = 1 UserProductName = < name > Load the ini file using the Auxiliary Files page (see Loading Auxiliary Files). Reset the device with a save-to-flash for your settings to take effect.

  • Page 80: Creating A Login Welcome Message

    CHAPTER 6    Web-Based Management Mediant 800 Gateway & E-SBC | User's Manual Click Cmd Shell. In the 'Command Line' field, type the following, and then click Enter: CTACI FAVICON Creating a Login Welcome Message You can create a personalized welcome message that is displayed on the Web Login screen. The message always begins with the title "Note"...

  • Page 81: Configuring Additional Management Interfaces

    CHAPTER 6    Web-Based Management Mediant 800 Gateway & E-SBC | User's Manual Configuring Additional Management Interfaces The Additional Management Interfaces table lets you configure up to 16 management interfaces, in addition to the OAMP management interface configured in the IP Interfaces table. Multiple management interfaces lets you remotely access the device's management interfaces (see note below) through different IP addresses.

  • Page 82: Configuring Management User Accounts

    CHAPTER 6    Web-Based Management Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ Only Control- and/or Media-type IP network interfaces can be associated with additional management interfaces. ■ An IP network interface can be associated with only one additional management interface.
  • Page 83 CHAPTER 6    Web-Based Management Mediant 800 Gateway & E-SBC | User's Manual Numeric User Level Representation Privileges in RADIUS Note: Only Master users can delete Master users. If only one Master user exists, it can be deleted only by itself. Administrator...
  • Page 84 CHAPTER 6    Web-Based Management Mediant 800 Gateway & E-SBC | User's Manual The following procedure describes how to configure user accounts through the Web interface. You can also configure it through ini file [WebUsers] or CLI (configure system > user). ➢...
  • Page 85 CHAPTER 6    Web-Based Management Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ For security, password characters are not shown in the Web interface and ini file. In the Web interface, they are displayed as dots when you enter the password and then once applied, the password is displayed as an asterisk (*) in the table.
  • Page 86 CHAPTER 6    Web-Based Management Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ Valid = User can log in to the Web interface as normal. ■ Failed Login = The state is automatically set for users that exceed a user-defined number of failed login attempts, set by...
  • Page 87 CHAPTER 6    Web-Based Management Mediant 800 Gateway & E-SBC | User's Manual Parameter Description Note: After logging in with your new password, you must save your settings, by clicking the Save button on the Web interface's toolbar. If not, the next time you attempt to log in, you will be prompted again to change the expired password.

  • Page 88: Customizing Access Levels Per Web Page

    CHAPTER 6    Web-Based Management Mediant 800 Gateway & E-SBC | User's Manual Parameter Description The valid value is 0 to 100000, where 0 means that the user can do as many login failures without getting blocked. The default is according to the settings of the 'Deny Authentication Timer'...
  • Page 89 CHAPTER 6    Web-Based Management Mediant 800 Gateway & E-SBC | User's Manual Page Name Read-Write Access Level Read-Only Access Level Description Firewall Security Administrator Monitor Assigns read- write privileges to Security Administrator users for the Firewall page. As this is the...

  • Page 90: Displaying Login Information Upon Login

    CHAPTER 6    Web-Based Management Mediant 800 Gateway & E-SBC | User's Manual Configure the rule according to the parameters described in the table below. Click Apply, and then save your settings to flash memory. Table 6-9: Customize Access Level Table Parameter Descriptions...

  • Page 91: Viewing Logged-In User Information

    CHAPTER 6    Web-Based Management Mediant 800 Gateway & E-SBC | User's Manual Once enabled, each time you login to the device, the Login Information window is displayed, as shown in the example below: To close the window, click Close. Viewing Logged-In User Information The username of the currently logged in user is displayed in the top-right corner of the Web interface.

  • Page 92: Changing Login Password By All User Levels

    CHAPTER 6    Web-Based Management Mediant 800 Gateway & E-SBC | User's Manual You can only perform the configuration described in this section if you are a management user with Security Administrator level or Master level. For more information, see Configuring Management User Accounts.

  • Page 93: Configuring Secured (Https) Web

    CHAPTER 6    Web-Based Management Mediant 800 Gateway & E-SBC | User's Manual ● Users with Security Administrator level or Master level can also change passwords for themselves and for other user levels in the Local Users table (see Configuring Management User Accounts).

  • Page 94: Configuring Csrf Protection

    CHAPTER 6    Web-Based Management Mediant 800 Gateway & E-SBC | User's Manual ➢ To configure secure (HTTPS) Web access: Open the Web Settings page (Setup menu > Administration tab > Web & CLI folder > Web Settings). Under the General group, configure the following: From the 'Secured Web Connection (HTTPS)' drop-down list, select HTTPS Only.

  • Page 95: Configuring Web And Telnet Access List

    CHAPTER 6    Web-Based Management Mediant 800 Gateway & E-SBC | User's Manual ➢ To log in to the Web interface using CAC: Insert the Common Access Card into the card reader. Enter the password only. As some browsers require that the username be provided, it’s recommended to enter the username with an arbitrary value.

  • Page 96: Cli-Based Management

    CHAPTER 7    CLI-Based Management Mediant 800 Gateway & E-SBC | User's Manual CLI-Based Management This chapter provides an overview of the CLI-based management and provides configuration relating to CLI management. ● By default, CLI is disabled for security purposes. ● The CLI provides two access modes - Basic mode (basic commands) and Privileged mode (all commands).

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

    CHAPTER 7    CLI-Based Management Mediant 800 Gateway & E-SBC | User's Manual Enabling SSH with RSA Public Key for CLI Unless configured for TLS, Telnet is not secure as it requires passwords to be transmitted in clear text. To overcome this, you can use Secure SHell (SSH) which is the de-facto standard for secure CLI.

  • Page 98: Configuring Maximum Telnet/Ssh Sessions

    CHAPTER 7    CLI-Based Management Mediant 800 Gateway & E-SBC | User's Manual On the CLI Settings page, do the following: From the 'Enable SSH Server' drop-down list, select Enable. For additional security, you can configure the 'Public Key' field to Enable. This ensures that SSH access is only possible by using the RSA key and not by username and password.

  • Page 99: Establishing A Cli Session

    CHAPTER 7    CLI-Based Management Mediant 800 Gateway & E-SBC | User's Manual ● Before changing the setting, make sure that not more than the number of sessions that you want to configure are currently active; otherwise, the new setting will not take effect.

  • Page 100: Viewing Current Cli Sessions

    CHAPTER 7    CLI-Based Management Mediant 800 Gateway & E-SBC | User's Manual > enable At the prompt, type the password again, and then press Enter: Password: Admin Viewing Current CLI Sessions You can view users that are currently logged in to the device's CLI. This applies to users logged in to the CLI through RS-232 (console), Telnet, or SSH.

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

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

  • Page 102: Configuring Password Display In Cli

    CHAPTER 7    CLI-Based Management Mediant 800 Gateway & E-SBC | User's Manual Configuring Password Display in CLI You can enable the deviceto display passwords in the CLI's show running-config output in encrypted (obscured) format instead of in plain text. When passwords are displayed encrypted, the word "obscured"...

  • Page 103: Snmp-Based Management

    Mediant 800 Gateway & E-SBC | User's Manual SNMP-Based Management The device provides an embedded SNMP agent that lets you manage it using AudioCodes One Voice Operations Center (OVOC) 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 104 CHAPTER 8    SNMP-Based Management Mediant 800 Gateway & E-SBC | User's Manual Configure SNMP community strings for access privileges: ● Under the Read Only Community Strings group, configure read-only community strings (see the table below). ● Under the Read/Write Community Strings group, configure read-write community strings (see the table below).

  • Page 105: Configuring Snmp Trap Destinations With Ip Addresses

    CHAPTER 8    SNMP-Based Management Mediant 800 Gateway & E-SBC | User's Manual Parameter Description The default is "public". For ini file configuration, x is 0 for the 'Read-Only 1' parameter. Read-Write Community Strings Defines read-write SNMP community strings. Up to five read-write community configure system >...
  • Page 106 CHAPTER 8    SNMP-Based Management Mediant 800 Gateway & E-SBC | User's Manual Configure the SNMP trap manager according to the table below. Select the check boxes corresponding to the configured SNMP managers that you want to enable. Click Apply. ● Rows whose corresponding check boxes are cleared revert to default settings when you click Apply.

  • Page 107: Configuring An Snmp Trap Destination With Fqdn

    CHAPTER 8    SNMP-Based Management Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Trap Enable' Activates the sending of traps to the SNMP Manager. [SNMPManagerTrapSendingEnable_ ■ [0] Disable ■ [1] Enable (default) Configuring an SNMP Trap Destination with FQDN Instead of configuring SNMP trap destinations (managers) with IP addresses in dotted-decimal...

  • Page 108: Enabling Snmp Traps For Web Activity

    CHAPTER 8    SNMP-Based Management Mediant 800 Gateway & E-SBC | User's Manual Configure an IP address (in dotted-decimal notation) for one or more SNMP Trusted Managers. Select the check boxes corresponding to the configured SNMP Trusted Managers that you want to enable.
  • Page 109 CHAPTER 8    SNMP-Based Management Mediant 800 Gateway & E-SBC | User's Manual Configure the SNMP V3 parameters according to the table below. Click Apply, and then reset the device with a save-to-flash for your settings to take effect. Table 8-3: SNMPv3 Users Table Parameters Description...

  • Page 110: Customizing Snmp Alarm Severity

    CHAPTER 8    SNMP-Based Management Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Privacy Key' Privacy key. Keys can be entered in the form of a text password or long hex string. Keys are always persisted as long hex strings and keys are priv-key localized.
  • Page 111 CHAPTER 8    SNMP-Based Management Mediant 800 Gateway & E-SBC | User's Manual 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. Table 8-4: Alarms Customization Parameter Descriptions...
  • Page 112 CHAPTER 8    SNMP-Based Management Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ✔ If configured to any value other than Suppressed, the device always sends the alarm with the configured severity (regardless of condition). ■ [1] Indeterminate ■ [2] Warning ■...
  • Page 113 CHAPTER 8    SNMP-Based Management Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ✔ To suppress the sending of a specific alarm severity: If the alarm has multiple severity levels (based on conditions), configure the 'Original Severity' parameter to the severity that you don't want the device to send.

  • Page 114: Ini File-Based Management

    CHAPTER 9    INI File-Based Management Mediant 800 Gateway & E-SBC | User's Manual INI File-Based Management You can configure the device through an ini file, which is a text-based file with an *.ini file extension name, created using any standard text-based editor such as Notepad. Once you have created an ini file with all your configuration settings, you need to install (load) it to the device to apply the configuration.
  • Page 115 CHAPTER 9    INI File-Based Management Mediant 800 Gateway & E-SBC | User's Manual ● A Data line must end with a semicolon ";". ■ End-of-Table Mark: Indicates the end of the table. The same string used for the table’s title, preceded by a backslash "\", e.g., [\MY_TABLE_NAME].

  • Page 116: General Ini File Formatting Rules

    CHAPTER 9    INI File-Based Management Mediant 800 Gateway & E-SBC | User's Manual Do not include read-only parameters in the table ini file parameter. This can cause an error when loading the file to the device. General ini File Formatting Rules The ini file must adhere to the following formatting rules: ■...

  • Page 117: Loading An Ini File To The Device

    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. For more information, refer to the DConvert Utility User's Guide.

  • Page 118: Ini Viewer And Editor Utility

    CHAPTER 9    INI File-Based Management Mediant 800 Gateway & E-SBC | User's Manual ● When you load an ini file to the device containing obscured passwords, the passwords are parsed and applied to the device. ● When you load an ini file to the device containing hidden passwords, the passwords are ignored.

  • Page 119: Rest-Based Management

    CHAPTER 10    REST-Based Management Mediant 800 Gateway & E-SBC | User's Manual REST-Based Management You can manage the device through the Representational State Transfer (REST) architecture. REST is a Web-based access service, allowing you to access the device's management interface over HTTP/S. Developers can use the device's REST API to integrate the device into their solution and allow administrators to perform management and configuration tasks through automation scripts.
  • Page 120 CHAPTER 10    REST-Based Management Mediant 800 Gateway & E-SBC | User's Manual ● If you know the URL of the resource, instead of accessing each resource menu, you can access it directly using the full URL path (e.g., /api/v1/alarms/active). ● For more information on REST API, refer to the document, REST API for Mediant Devices.

  • Page 121: General System Settings

    Part III General System Settings...

  • Page 122: Date And Time

    CHAPTER 11    Date and Time Mediant 800 Gateway & E-SBC | User's Manual Date and Time The date and time of the device can be configured manually or it can be obtained automatically from a Simple Network Time Protocol (SNTP) server.

  • Page 123: Configuring Date And Time Manually

    CHAPTER 11    Date and Time Mediant 800 Gateway & E-SBC | User's Manual If the device does not receive a response from the NTP server, it polls the NTP server for 10 minutes. If there is still no response after this duration, the device declares the NTP server as unavailable and raises an SNMP alarm (acNTPServerStatusAlarm).

  • Page 124: Configuring Daylight Saving Time

    CHAPTER 11    Date and Time Mediant 800 Gateway & E-SBC | User's Manual In the 'UTC Offset' fields (NTPServerUTCOffset), configure the time offset in relation to the UTC. For example, if your region is GMT +1 (an hour ahead), enter "1" in the 'Hours' field.

  • Page 125: Configuring A Hostname For The Device

    The device's SNMP interface's SysName object (under MIB-2) is set to the hostname. ■ TLS certificates used by the device for HTTPS-based communication with AudioCodes OVOC are issued with a hostname (instead of an IP address). For certificate signing requests (CSR) with a Certification Authority (CA), the hostname is used as the Common Name (CN or Subject Name) and Subject Alternative Name (SAN).

  • Page 126: General Voip Configuration

    Part IV General VoIP Configuration...

  • Page 127: Network

    CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual Network This section describes network-related configuration. Building and Viewing your Network Topology The Network view lets you easily build and view your voice network topology entities, including IP network interfaces, Ethernet Devices (VLANs), Ethernet Groups, and physical Ethernet ports. The Topology view graphically displays these entities and the associations between them, giving you a better understanding of your network topology and configuration.
  • Page 128 CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual Item Description 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...
  • Page 129 CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual Item Description Configure the Ethernet Devices as desired, and then click Apply; the Ethernet Devices table closes and you are returned to the Network View, displaying the newly added Ethernet Device.

  • Page 130: Configuring Physical Ethernet Ports

    CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual Item Description 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).
  • Page 131 CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual Select a port that you want to configure, and then click Edit; the following dialog box appears: Configure the port according to the parameters described in the table below. Click Apply, and then reset the device with a burn-to-flash for your settings to take effect.

  • Page 132: Configuring Ethernet Port Groups

    CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual Parameter Description [PhysicalPortsTable_ GroupMember] 'Group Status' (Read-only) Displays the status of the port: ■ "Active": Active port. When the Ethernet Group includes two ports group-status and their transmit/receive mode is configured to 2RX 1TX or 2RX [PhysicalPortsTable_ 2TX, both ports show "Active".
  • Page 133 CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual The following procedure describes how to configure Ethernet Groups through the Web interface. You can also configure it through ini file [EtherGroupTable] or CLI (configure network > ether-group). ➢ To configure Ethernet Groups: Open the Ethernet Groups table (Setup menu >...

  • Page 134: Configuring Underlying Ethernet Devices

    CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [5] Single = Select this option if the Ethernet Group contains only one port. ■ [6] None = Select this option to remove all ports from the Ethernet Group.
  • Page 135 CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual You cannot delete an Ethernet Device that is associated with an IP network interface (in the IP Interfaces table). You can only delete it once you have disassociated it from the IP network interface.
  • Page 136 CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Underlying Assigns an Ethernet Group to the Ethernet Device. To configure Interface' Ethernet Groups, see Configuring Ethernet Port Groups. Note: The parameter is mandatory. underlying-if [DeviceTable_ UnderlyingInterface] 'Tagging' Defines VLAN tagging for the Ethernet Device.

  • Page 137: Configuring Ip Network Interfaces

    CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual 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.
  • Page 138 CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual ■ Ethernet Device: Layer-2 bridging device and assigned a VLAN ID. As the Ethernet Device is associated with an Ethernet Group, this is useful for setting trusted and un-trusted networks on different physical Ethernet ports.
  • Page 139 CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual ➢ To configure IP network interfaces: Open the IP Interfaces table (Setup menu > IP Network tab > Core Entities folder > IP Interfaces). Click New; the following dialog box appears: Configure the IP network interface according to the parameters described in the table below.
  • Page 140 CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ The parameter value cannot contain a forward slash (/). 'Application Type' Defines the applications allowed on the IP interface. ■ [0] OAMP = Operations, Administration, Maintenance application-type and Provisioning (OAMP) applications (e.g., Web,...

  • Page 141: Networking Configuration Examples

    CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Prefix Length' Defines the prefix length of the related IP address. This is a Classless Inter-Domain Routing (CIDR)-style prefix-length representation of a dotted-decimal subnet notation. The [InterfaceTable_PrefixLength] CIDR-style representation uses a suffix indicating the number of bits which are set in the dotted-decimal format.
  • Page 142 CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual ■ Single IP network interface for all applications: The IP Interfaces table is configured with a single interface for OAMP, Media and Control: Inter- Prefix Inde- Applic- Eth- Default Name...
  • Page 143 CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual Pre- Applic- Inter- Ind- Eth- Default Name ation face IP Address ernet Leng- Gateway Type Mode Device Mgmt OAMP IPv4 192.168.0.2 192.168.0. Manual MediaCntrl1 Media + IPv4 200.200.85.14 200.200.8 Control...

  • Page 144: Configuring Static Ip Routes

    CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual Inter- Prefix Inde- Applic- Eth- Default Name face IP Address Lengt- ation Type ernet Gateway Mode Device Mgmt OAMP IPv4 192.168.0.2 192.168.0.1 Manual CntrlMedi Media & IPv4 200.200.85.1 200.200.85. Control...
  • Page 145 CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual 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 146: Configuration Example Of Static Ip Routes

    CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ IPv6: 0 to 128 'Ethernet Output Associates an IP network interface through which the static route's Device' Gateway is reached. The association is done by assigning the...

  • Page 147: Troubleshooting The Static Routes Table

    CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual Troubleshooting the Static Routes Table When adding a new static route to the Static Routes table, the added rule passes a validation test. If errors are found, the static route is rejected and not added to the table. Failed static route validations may result in limited connectivity (or no connectivity) to the destinations specified in the incorrect static route.

  • Page 148: Device Located Behind Nat

    CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual The design of SIP creates a problem for VoIP traffic to pass through NAT. SIP uses IP addresses and port numbers in its message body. However, the NAT server is unable to modify the SIP messages and thus, can’t change local addresses to global addresses.

  • Page 149: Configuring Nat Translation Per Ip Interface

    CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual Figure 13-2: Configuring Static NAT IP Address Click Apply. The feature is applicable only to the Gateway application. Configuring NAT Translation per IP Interface The NAT Translation table lets you configure up to 32 network address translation (NAT) rules for translating source IP addresses into NAT IP addresses (global -public) when the device is located behind NAT.

  • Page 150: Remote Ua Behind Nat

    CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Source Interface' Assigns an IP network interface (configured in the IP Interfaces table) to the rule. Outgoing packets sent from the specified network src-interface- interface are NAT'ed. name By default, no value is defined.

  • Page 151: Sip Signaling Messages

    CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual SIP Signaling Messages By default, the device resolves NAT issues for SIP signaling, using its NAT Detection mechanism. The NAT Detection mechanism checks whether the endpoint is located behind NAT by comparing the source IP address of the incoming UDP/TCP packet (in which the SIP message is received) with the IP address in the SIP Contact header.
  • Page 152 CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual First Incoming Packet Mechanism In scenarios where the remote user agent (UA) resides behind a NAT server, it’s possible that the device, if not configured for NAT traversal, will send the media (RTP, RTCP and T.38) streams to an invalid IP address and UDP port.
  • Page 153 CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual Configure the time interval during which the device sends No-Op packets when silence occurs (i.e., no RTP or T.38 traffic), using the [NoOpInterval] parameter. For RTP No-Op packets, configure the payload type of the No-Op packets, using the [RTPNoOpPayloadType] parameter.
  • Page 154 CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual The device's support for ICE-Lite means that it does not initiate the ICE process. Instead, it supports remote endpoints that initiate ICE to discover their workable public IP address with the device.

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

    CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual Robust Receipt of Media Streams by Media Latching The device's Robust Media feature (or media latching) filters 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...

  • Page 156: Configuring Quality Of Service

    CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual Click Apply, and then save your settings to flash memory. Configuring Quality of Service This section describes how to configure Layer-2 and Layer-3 Quality of Service (QoS). Configuring Class-of-Service QoS The QoS Settings page lets you configure Layer-3 Class-of-Service Quality of Service (QoS).
  • Page 157 CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual Class-of-Service Application Traffic / Network Types (Priority) T.38 traffic Media Media Premium Control Control Premium SIP over TLS (SIPS) Control Control Premium Syslog Management Bronze SNMP Traps Management Bronze DNS client...

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

    CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual Parameter Description Note: You can also configure the the parameter per IP Profile (IpProfile_IPDiffServ) or Tel Profile (TelProfile_IPDiffServ). 'Control Premium QoS' Defines the DiffServ value for Premium Control CoS content (Call Control applications).

  • Page 159: Configuring Icmp Messages

    CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual 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. Table 13-10:QoS Mapping Table Parameter Descriptions...

  • Page 160: Dns

    CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual ● To enable sending and receipt of ICMP Redirect messages, configure the 'Send and Received ICMP Redirect Messages' [DisableICMPRedirects] parameter to Enable. ● To enable sending of ICMP Destination Unreachable messages, configure the 'Don't Send ICMP Unreachable Messages' [DisableICMPUnreachable] parameter to Disable.

  • Page 161: Configuring The Internal Dns Table

    CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual In the 'Default Primary DNS Server IP' field, configure the address of the default primary DNS server. In the 'Default Secondary DNS Server IP' field, configure the address of the default secondary DNS server.

  • Page 162: Configuring The Internal Srv Table

    CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual Click Apply. Table 13-11:Internal DNS Table Parameter Description Parameter Description 'Index' Defines an index number for the new table row. Note: Each row must be configured with a unique index.
  • Page 163 CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual Configure an SRV rule according to the parameters described in the table below. Click Apply, and then save your settings to flash memory. Table 13-12:Internal SRV Table Parameter Descriptions Parameter...

  • Page 164: Open Solution Network (Osn) Server

    CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Weight (1-3)' Defines a relative weight for records with the same priority. By default, no value is defined. weight-1|2|3 [Srv2Ip_ Weight1/2/3] 'Port (1-3)' Defines the TCP or UDP port on which the service is to be found.

  • Page 165: Ip Multicasting

    CHAPTER 13    Network Mediant 800 Gateway & E-SBC | User's Manual You can also view the status of the port (Up or Down), by running the following CLI command: # show system interface osn ➢ To enable / disable the internal switch's Ethernet port interfacing with OSN: Open the Network Settings page (Setup menu >...

  • Page 166: Security

    CHAPTER 14    Security Mediant 800 Gateway & E-SBC | User's Manual Security This section describes the VoIP security-related configuration. Configuring SSL/TLS Certificates The TLS Contexts table lets you configure X.509 certificates which are used for secure management of the device, secure SIP transactions, and other security applications.
  • Page 167 CHAPTER 14    Security Mediant 800 Gateway & E-SBC | User's Manual ■ Online Certificate Status Protocol (OCSP). Some Public-Key Infrastructures (PKI) can revoke a certificate after it has been issued. 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 peer certificate is received (TLS client mode, or TLS server mode with mutual authentication).
  • Page 168 CHAPTER 14    Security Mediant 800 Gateway & E-SBC | User's Manual Configure the TLS Context 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. Table 14-1: TLS Contexts Parameter Descriptions...
  • Page 169 CHAPTER 14    Security Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [1] DTLSv1.0 ■ [2] DTLSv1.2 For more information on WebRTC, see WebRTC. Note: The parameter is applicable only to the SBC application. 'Cipher Server' Defines the supported cipher suite for the TLS server (in OpenSSL cipher list format).

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

    CHAPTER 14    Security Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Secondary OCSP Server' Defines the IP address (in dotted-decimal notation) of the secondary OCSP server (optional). ocsp-server-secondary The default is 0.0.0.0. [TLSContexts_ OcspServerSecondary] 'OCSP Port' Defines the OCSP server's TCP port number.
  • Page 171 CHAPTER 14    Security Mediant 800 Gateway & E-SBC | User's Manual ● Fill in the fields according to you security provider's instructions. ● If you leave the 'Common Name [CN]' field empty, the device generates the CSR with the default Common Name (CN=ACL_<6-digit serial number of device>).

  • Page 172: Viewing Certificate Information

    CHAPTER 14    Security Mediant 800 Gateway & E-SBC | User's Manual Select the required TLS Context row. Click the Certificate Information link located below the table. Make sure that the 'Status' field displays "OK"; otherwise, consult with your security administrator: ●...

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

    CHAPTER 14    Security Mediant 800 Gateway & E-SBC | User's Manual 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 174: Generating Private Keys For Tls Contexts

    CHAPTER 14    Security Mediant 800 Gateway & E-SBC | User's Manual Open the TLS Contexts table (see Configuring TLS Certificate Contexts). In the table, select the required TLS Context index row, and then click the Change Certificate link located below the table; the Change Certificates page appears.

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

    CHAPTER 14    Security Mediant 800 Gateway & E-SBC | User's Manual From the 'Private Key Size' drop-down list, select the desired private key size (in bits) for RSA public-key encryption for newly self-signed generated keys: ● ● ● 1024 (default) ●...

  • Page 176: Importing Certificates Into Trusted Root Certificate Store

    CHAPTER 14    Security Mediant 800 Gateway & E-SBC | User's Manual Under the Certificate Signing Request group, in the 'Common Name [CN]' field, enter the fully-qualified DNS name (FQDN) as the certificate subject. Alternatively (or in addition), if you want to generate a self-signed SAN certificate (with multiple subject alternate names), then from the 'Subject Alternative Name [SAN]' drop-down list, select the type of SAN (e-mail address, DNS hostname, URI, or IP address), and then enter the relevant value.

  • Page 177: Configuring Mutual Tls Authentication

    CHAPTER 14    Security Mediant 800 Gateway & E-SBC | User's Manual You can also import multiple TLS root certificates in bulk from a single file. Each certificate in the file must be Base64 encoded (PEM). When copying-and-pasting the certificates into the file, each Base64 ASCII encoded certificate string must be enclosed between "-----BEGIN CERTIFICATE---...

  • Page 178: Tls For Sip Clients

    CHAPTER 14    Security Mediant 800 Gateway & E-SBC | User's Manual 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). When the device acts as the TLS server in a specific connection, the device demands the authentication of the SIP client’s...

  • Page 179: Configuring Tls Server Certificate Expiry Check

    CHAPTER 14    Security Mediant 800 Gateway & E-SBC | User's Manual When a user connects to the secured Web interface of the device: ■ If the user has a client certificate from a CA that is listed in the Trusted Root Certificate file, the connection is accepted and the user is prompted for the system password.
  • Page 180 Protocol: Any ✔ Action Upon Match: Block ● If the device needs to communicate with AudioCodes OVOC, you must also add rules to allow incoming traffic from OVOC. For more information, see Configuring Firewall Rules to Allow Incoming OVOC Traffic on page 144.
  • Page 181 CHAPTER 14    Security Mediant 800 Gateway & E-SBC | User's Manual Configure a firewall 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. Table 14-2: Firewall Table Parameter Descriptions...
  • Page 182 CHAPTER 14    Security Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Start Port' Defines the first UDP/TCP port in the range of ports on the device on which the incoming packet is received. From the perspective of the remote IP start-port entity, this is the destination port.
  • Page 183 CHAPTER 14    Security Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Packet Size' Defines the maximum allowed packet size. The valid range is 0 to 65535. packet- size Note: When filtering fragmented IP packets, this field relates to the overall [AccessList_ (re-assembled) packet size, and not to the size of each fragment.

  • Page 184: Configuring Firewall Rules To Allow Incoming Ovoc Traffic

    Rule 5: Blocks all other traffic. Configuring Firewall Rules to Allow Incoming OVOC Traffic If the device needs to communicate with AudioCodes OVOC, you need to configure the device's firewall (Firewall table) with the below "allow" firewall rules to permit incoming traffic from OVOC.

  • Page 185: Configuring Tls For Sip

    CHAPTER 14    Security Mediant 800 Gateway & E-SBC | User's Manual Acti- Pre- Pac- Byt- Sou- Spe- Inter- Sour- Pro- Upo- Index cific face ce IP Len- tocol Siz- Port Inter- Name Mat- face <OV Enabl <inter- Allo (HTT OC IP...
  • Page 186 CHAPTER 14    Security Mediant 800 Gateway & E-SBC | User's Manual ● When a TLS connection with the device is initiated by a SIP client, the device also responds using TLS, regardless of whether or not TLS was configured. ● The device regulates the number of new concurrent TLS connections that can be established per second.

  • Page 187: Intrusion Detection System

    CHAPTER 14    Security Mediant 800 Gateway & E-SBC | User's Manual Intrusion Detection System The device's Intrusion Detection System (IDS) feature detects malicious attacks on the device and reacts accordingly. A remote host is considered malicious if it has reached or exceeded a user- defined threshold (counter) of specified malicious attacks.

  • Page 188: Configuring Ids Policies

    CHAPTER 14    Security Mediant 800 Gateway & E-SBC | User's Manual Click Apply. Configuring IDS Policies An IDS Policy is configured using two tables with "parent-child" type relationship: ■ IDS Policies table ("parent"): Defines a name and provides a description for the IDS Policy.
  • Page 189 CHAPTER 14    Security Mediant 800 Gateway & E-SBC | User's Manual Click Apply. Table 14-5: IDS Policies 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.
  • Page 190 CHAPTER 14    Security Mediant 800 Gateway & E-SBC | User's Manual Parameter Description [IDSRule_RuleID] 'Reason' Defines the type of intrusion attack (malicious event). ■ [0] Any = All events listed below are considered as attacks and reason are counted together. [IDSRule_Reason] ■...
  • Page 191 CHAPTER 14    Security Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ✔ Requests and responses without a matching transaction user (except ACK requests) ✔ Requests and responses without a matching transaction (except ACK requests) 'Threshold Scope' Defines the source of the attacker to consider in the device's detection count.

  • Page 192: Assigning Ids Policies

    CHAPTER 14    Security Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Deny Period' Defines the duration (in sec) to keep the attacker on the blacklist, if configured using the 'Deny Threshold' parameter. deny-period The valid range is 0 to 1,000,000. The default is -1 (i.e., not [IDSRule_DenyPeriod] configured).
  • Page 193 CHAPTER 14    Security Mediant 800 Gateway & E-SBC | User's Manual Parameter Description [IDSMatch_SIPInterface] The valid value is the ID of the SIP Interface. The following syntax is supported: ■ A comma-separated list of SIP Interface IDs (e.g., 1,3,4) ■ A hyphen "-" indicates a range of SIP Interfaces (e.g., 3,4-7 means IDs 3, and 4 through 7) ■...

  • Page 194: Viewing Ids Alarms

    CHAPTER 14    Security Mediant 800 Gateway & E-SBC | User's Manual Viewing IDS Alarms For the IDS feature, the device sends the following SNMP traps: ■ Traps that notify the detection of malicious attacks: ● acIDSPolicyAlarm: The device sends this alarm whenever a threshold of a specific IDS Policy rule is crossed.
  • Page 195 CHAPTER 14    Security Mediant 800 Gateway & E-SBC | User's Manual The device also sends IDS notifications and alarms in Syslog messages to a Syslog server. This occurs only if you have configured Syslog (see Enabling Syslog). An example of a Syslog message...

  • Page 196: Configuring Sip Response Codes To Exclude From Ids

    CHAPTER 14    Security Mediant 800 Gateway & E-SBC | User's Manual Reason Description Syslog String Abnormal Flow Requests and responses without a matching flow-no-match-tu transaction user (except ACK requests) Requests and responses without a matching flow-no-match-transaction transaction (except ACK requests) Configuring SIP Response Codes to Exclude from IDS You can specify SIP response codes (reject reasons) that you want the IDS mechanism to ignore in its' count as reasons for SIP-dialog establishment failures.

  • Page 197: Media

    CHAPTER 15    Media Mediant 800 Gateway & E-SBC | User's Manual Media This section describes media-related configuration. Configuring Voice Settings The section describes various voice- related configuration such as voice volume, silence suppression, and DTMF transport type. For a detailed description of these parameters, see Configuration Parameters Reference.
  • Page 198 CHAPTER 15    Media Mediant 800 Gateway & E-SBC | User's Manual The device also supports acoustic echo cancellation for SBC calls. These echoes are composed of undesirable acoustical reflections (non-linear) of the received signal (i.e., from the speaker) which find their way from multiple reflections such as walls and windows into the transmitted signal (i.e., microphone).

  • Page 199: Fax And Modem Capabilities

    CHAPTER 15    Media Mediant 800 Gateway & E-SBC | User's Manual 'Max Reference Delay' (AcousticEchoSuppMaxRefDelayx10ms) - defines the ◆ acoustic echo suppressor maximum reference delay Open the IP Profiles table, and configure the 'Echo Canceller' parameter to Acoustic (see Configuring IP Profiles).

  • Page 200: Fax/Modem Transport Modes

    CHAPTER 15    Media Mediant 800 Gateway & E-SBC | User's Manual ■ Voice-band data (VBD) mode for V.152 implementation (see V.152 Support): fax/modem capabilities are negotiated between the device and the remote endpoint at the establishment of the call. During a call, when a fax/modem signal is detected, transition from voice to VBD (or T.38) is automatically performed and no additional SIP signaling is required.
  • Page 201 CHAPTER 15    Media Mediant 800 Gateway & E-SBC | User's Manual Switching to T.38 Mode using SIP Re-INVITE In the Switching to T.38 Mode using SIP Re-INVITE mode, upon detection of a fax signal the terminating device negotiates T.38 capabilities using a Re-INVITE message. If the far-end device doesn't support T.38, the fax fails.
  • Page 202 Call Parties belong to AudioCodes Devices: T.38-over-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 203: G.711 Fax / Modem Transport Mode

    CHAPTER 15    Media Mediant 800 Gateway & E-SBC | User's Manual G.711 Fax / Modem Transport Mode In this mode, when the terminating device detects fax or modem signals (CED or AnsAM), it sends a Re-INVITE message to the originating device, requesting it to re-open the channel in G.711 VBD with the following adaptations: ■...

  • Page 204: Fax/Modem Bypass Mode

    CHAPTER 15    Media Mediant 800 Gateway & E-SBC | User's Manual a=gpmd:0 vbd=yes;ecan=on ■ For G.711 µ-law: a=gpmd:8 vbd=yes;ecan=on In this mode, the 'Fax Transport Mode' (FaxTransportMode) parameter is ignored and automatically set to Disable (transparent mode). ➢ To configure fax fallback mode: Open the Gateway General Settings page (Setup menu >...

  • Page 205: Fax / Modem Nse Mode

    G.711 packets with standard payload type (8 for G.711 A-Law and 0 for G.711 Mu-Law). In this mode, no Re-INVITE messages are sent. The voice channel is optimized for fax/modem transmission (same as for usual bypass mode). The following parameters that configure the payload type for the AudioCodes proprietary Bypass mode used...

  • Page 206: Fax / Modem Transparent With Events Mode

    CHAPTER 15    Media Mediant 800 Gateway & E-SBC | User's Manual On the Fax/Modem/CID Settings page, do the following: ● Set the 'Fax Transport Mode' parameter to Bypass (FaxTransportMode = 2). ● Set the 'V.21 Modem Transport Type' parameter to Enable Bypass (V21ModemTransportType = 2).

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

    CHAPTER 15    Media Mediant 800 Gateway & E-SBC | User's Manual ➢ To configure fax / modem transparent mode: Open the Gateway General Settings page (Setup menu > Signaling & Media tab > Gateway folder > Gateway General Settings), and then from the 'Fax Signaling Method' drop-down list (IsFaxUsed), select No Fax.

  • Page 208: V.34 Fax Support

    CHAPTER 15    Media Mediant 800 Gateway & E-SBC | User's Manual V.34 Fax Support V.34 fax machines can transmit data over IP to the remote side using various methods. The device supports the following modes for transporting V.34 fax data over IP: ■...

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

    CHAPTER 15    Media Mediant 800 Gateway & E-SBC | User's Manual ● Set the 'V.32 Modem Transport Type' parameter to Enable Bypass [V32ModemTransportType = 2]. ● Set the 'V.34 Modem Transport Type' parameter to Enable Bypass [V34ModemTransportType = 2]. Configure the [V34FaxTransportType] parameter to [2] (Bypass).
  • Page 210 CHAPTER 15    Media Mediant 800 Gateway & E-SBC | User's Manual ● 'V.21 Modem Transport Type' to Disable (V21ModemTransportType = 0). ● 'V.22 Modem Transport Type' to Disable (V22ModemTransportType = 0). ● 'V.23 Modem Transport Type' to Disable (V23ModemTransportType = 0).

  • Page 211: V.150.1 Modem Relay

    CHAPTER 15    Media Mediant 800 Gateway & E-SBC | User's Manual a=T38FaxMaxBuffer:1024 a=T38FaxMaxDatagram:122 a=T38FaxRateManagement:transferredTCF a=T38FaxUdpEC:t38UDPRedundancy V.150.1 Modem Relay The device can be configured to transfer modem calls using a subset of the ITU-T V.150.1 Modem Relay protocol. The device also supports V.150.1 modem relay coder negotiation in the initial SIP INVITE and 200 OK, using the SDP body according to the USA Department of Defense (DoD) UCR-2008, Change 2 specification.

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

    CHAPTER 15    Media Mediant 800 Gateway & E-SBC | User's Manual Simultaneous Negotiation of Fax (T.38) and Modem (V.150.1) Relay The device can negotiate fax relay (T.38) and modem relay (V.150.1) sessions in the same, already established call channel. Fax relay sessions require bypass answering tone (CED) while modem relay requires RFC 2833 answering tone.

  • Page 213: Configuring Rtp/Rtcp Settings

    CHAPTER 15    Media Mediant 800 Gateway & E-SBC | User's Manual Configuring RTP/RTCP Settings This section describes configuration relating to Real-Time Transport Protocol (RTP) and RTP Control Protocol (RTCP). Configuring the Dynamic Jitter Buffer Voice frames are transmitted at a fixed rate. If the frames arrive at the other end at the same rate, voice quality is perceived as good.

  • Page 214: Comfort Noise Generation

    CHAPTER 15    Media Mediant 800 Gateway & E-SBC | User's Manual ➢ To configure jitter buffer using the Web interface: Open the RTP/RTCP Settings page (Setup menu > Signaling & Media menu > Media folder > RTP/RTCP Settings). The relevant parameters are listed under the General group, as...
  • Page 215 CHAPTER 15    Media Mediant 800 Gateway & E-SBC | User's Manual ■ Using INFO message according to Nortel IETF draft: DTMF digits are sent to the remote side in INFO messages. To enable the mode: Set the 'Declare RFC 2833 in SDP' parameter to No (RxDTMFOption = 0).

  • Page 216: Configuring Rfc 2833 Payload

    CHAPTER 15    Media Mediant 800 Gateway & E-SBC | User's Manual Set the 'First Tx DTMF Option' parameter to Not Supported (FirstTxDTMFOption = 0). Set the ini file parameter, DTMFTransportType to 2 (i.e., transparent). ■ Using INFO message according to Korea mode: DTMF digits are sent to the remote side in INFO messages.

  • Page 217: Configuring Invalid Rtp/Rtcp Packet Handling

    CHAPTER 15    Media Mediant 800 Gateway & E-SBC | User's Manual The consecutive port offset from the RTP port for RTCP and T.38 traffic is one and two, respectively. For example, if the voice session uses RTP port 6000, the device allocates ports 6001 and 6002 for RTCP and T.38, respectively.

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

    CHAPTER 15    Media Mediant 800 Gateway & E-SBC | User's Manual Click Apply. Invalid packet handling configuration is applicable only to the SBC application. Event Detection and Notification using X-Detect Header The device can detect certain events in the media stream and notify of their detection to a remote application server, using the SIP X-Detect header.
  • Page 219 CHAPTER 15    Media Mediant 800 Gateway & E-SBC | User's Manual Content-Type: Application/X-Detect Type = [event type] Subtype = [subtype of each event type] The table below lists the event types and subtypes that can be detected by the device. The text shown in the table are the strings used in the X-Detect header.

  • Page 220: Sit Event Detection

    CHAPTER 15    Media Mediant 800 Gateway & E-SBC | User's Manual 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 221: Detecting Answering Machine Beeps

    CHAPTER 15    Media Mediant 800 Gateway & E-SBC | User's Manual Call-ID: AIFHPETLLMVVFWPDXUHD@10.33.2.36 CSeq: 1 INFO Contact: <sip:2206@10.33.45.65> Supported: em,timer,replaces,path,resource-priority Content-Type: application/x-detect Content-Length: 28 Type= CPT SubType= SIT-IC Detecting Answering Machine Beeps The device can detect the "beep" sound played by an answering machine that indicates the end of the answering machine's greeting message.
  • Page 222 CHAPTER 15    Media Mediant 800 Gateway & E-SBC | User's Manual ■ Example 1: This example shows a SIP call flow of the device's AMD and event detection feature, whereby the device detects an answering machine and the subsequent start and end...
  • Page 223 CHAPTER 15    Media Mediant 800 Gateway & E-SBC | User's Manual CSeq: 1 INFO Contact: <sip:56700@172.22.168.249> Supported: em,timer,replaces,path,resource-priority Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,I NFO,SUBSCRIBE,UPDATE User-Agent: AudioCodes-Sip-Gateway/7.20A.252.011 Content-Type: application/x-detect Content-Length: 34 Type= PTT SubType= SPEECH-END The application server sends its message to leave on the answering message.

  • Page 224: Answering Machine Detection (Amd)

    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 225 Mediant 800 Gateway & E-SBC | User's Manual Once you have provided AudioCodes with your database of recordings, AudioCodes compiles it into a loadable file. For a brief description of the file format and for installing the file on the device, AMD Sensitivity File.

  • Page 226: Configuring Amd

    CHAPTER 15    Media Mediant 800 Gateway & E-SBC | User's Manual Table 15-4: Approximate AMD High Detection Sensitivity - Parameter Suite 1 (Based on North Amer- ican English) AMD Detection Sensitivity Performance Level Success Rate for Live Success Rate for Answering...

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

    CHAPTER 15    Media Mediant 800 Gateway & E-SBC | User's Manual Scroll down to the Answer Machine Detector group: Select the AMD algorithm suite: In the 'Answer Machine Detector Sensitivity Parameter Suite' field, select the required Parameter Suite included in the installed AMD Sensitivity file.

  • Page 228: Automatic Gain Control (Agc)

    CHAPTER 15    Media Mediant 800 Gateway & E-SBC | User's Manual Automatic Gain Control (AGC) Automatic Gain Control (AGC) adjusts the energy of the output signal to a required level (volume). This feature compensates for near-far gain differences. AGC estimates the energy of the incoming signal from the IP or Tel side, determined by the 'AGC Redirection' parameter, calculates the essential gain, and then performs amplification.

  • Page 229: Configuring Media (Srtp) Security

    CHAPTER 15    Media Mediant 800 Gateway & E-SBC | User's Manual Configuring Media (SRTP) Security The device supports Secured RTP (SRTP) according to RFC 3711. SRTP is used to encrypt RTP and RTCP transport for protecting VoIP traffic. SRTP requires a cryptographic key exchange mechanism to negotiate the keys.

  • Page 230: Srtp Using Dtls Protocol

    CHAPTER 15    Media Mediant 800 Gateway & E-SBC | User's Manual The device also supports symmetric MKI negotiation, whereby it can forward the MKI size received in the SDP offer 'a=crypto' line in the SDP answer. You can enable symmetric MKI globally (using the EnableSymmetricMKI parameter) or per SIP entity (using the IP Profile parameter, IpProfile_ EnableSymmetricMKI and for SBC calls, IpProfile_SBCEnforceMKISize).
  • Page 231 CHAPTER 15    Media Mediant 800 Gateway & E-SBC | User's Manual DTLS support is important for deployments with WebRTC. WebRTC requires that media channels be encrypted through DTLS for SRTP key exchange. Negotiation of SRTP keys through DTLS is done during the DTLS handshake between WebRTC client and peer. For more information on WebRTC, see WebRTC.

  • Page 232: Services

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Services This section describes configuration for various supported services. DHCP Server Functionality The device can serve as a Dynamic Host Configuration Protocol (DHCP) server that assigns and manages IP addresses from a user-defined address pool for DHCP clients. The DHCP server can also be configured to supply additional information to the requesting client such as the IP address of the TFTP server, DNS server, NTP server, and default router (gateway).
  • Page 233 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual DHCP Option Code DHCP Option Name Option 42 Network Time Protocol Server 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 234 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Configure a DHCP server according to the parameters described in the table below. Click Apply. Table 16-2: DHCP Servers Table Parameter Descriptions Parameter Description General 'Index' Defines an index number for the new table row.
  • Page 235 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'DNS Server 2' Defines the IP address (IPv4) of the secondary DNS server that the DHCP server assigns to the DHCP client. The value is sent in dns-server-2 DHCP Option 6 (Domain Name Server).
  • Page 236 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Boot File Name' Defines the name of the boot file image for the DHCP client. The boot file stores the boot image for the client. The boot image is...

  • Page 237: 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 238: Configuring Additional Dhcp Options

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Vendor Class Identifier' Defines the value of the VCI DHCP Option 60. The valid value is a string of up to 80 characters. By default, no vendor-class value is defined.
  • Page 239 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Table 16-4: DHCP Option Table Parameter Descriptions Parameter Description 'Index' Defines an index number for the new table row. Note: Each row must be configured with a unique dhcp option index.

  • Page 240: Configuring Static Ip Addresses For Dhcp Clients

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ <IP>: Replaced by the IP address assigned by the DHCP server to the client. For example, the parameter can be set to: http://192.168.3.155:5000/provisioning/cfg_ <IP>.txt 'Expand Value' Enables the use of the special placeholder strings, "<MAC>"...

  • Page 241: Viewing And Deleting Dhcp Clients

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Table 16-5: DHCP Static IP 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.

  • Page 242: Sip-Based Media Recording

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual ➢ To view or delete DHCP clients: Open the DHCP Servers table (see Configuring the DHCP Server). Select the row of the desired DHCP server for which you want to view DHCP clients, and then click the DHCP Clients link located below the table;...
  • Page 243 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual ● The SIP-based Media Recording feature is available only if the device is installed with a License Key that includes this feature. The License Key specifies the maximum number of supported SIP recording sessions. For installing a License...
  • Page 244 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual The device can send recorded SBC calls to multiple SRSs. To achieve this, you can configure up to three groups of SRSs, where each group can contain one SRS (standalone), or two SRSs operating in an active-standby (1+1) mode for SRS redundancy.
  • Page 245 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual ● The device can send recordings (media) to up to three active SRSs. In other words, any one of the following configurations are supported: ✔ Up to three standalone (active) SRSs.
  • Page 246 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual You can configure the format of the recording metadata (i.e., based on RFC 7865 or "legacy") that is generated by the device. For more information, see Configuring Format of SIPRec Metadata on page 212.
  • Page 247 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual ■ Legacy XML metadata: <?xml version="1.0" encoding="UTF-8"?> <recording xmlns='urn:ietf:params:xml:ns:recording'> <datamode>complete</datamode> <group id="00000000-0000-0000-0000-00003a36c4e3"> <associate-time>2010-01-24T01:11:57Z</associate-time> </group> <session id="0000-0000-0000-0000-00000000d0d71a52"> <group-ref>00000000-0000-0000-0000-00003a36c4e3</group-ref> <start-time>2010-01-24T01:11:57Z</start-time> <ac:AvayaUCID xmlns="urn:ietf:params:xml:ns:Avaya">FA080030C4E34B5B9E59</ac:AvayaUCID> </session> <participant id="1056" session="0000-0000-0000-0000-00000000d0d71a52"> <nameID aor="1056@192.168.241.20"></nameID> <associate-time>2010-01-24T01:11:57Z</associate-time> <send>00000000-0000-0000-0000-1CF23A36C4E3</send> <recv>00000000-0000-0000-0000-BF583A36C4E3</recv> </participant>...

  • Page 248: Configuring Sip Recording Rules

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual </participant> <stream stream_id="mBfiAAAAAL1hFQENAPA=" session_id="OWc4Md2PHao="> <label>1</label> </stream> <stream stream_id="hBfiAAAAAL1hFQENAPA=" session_id="OWc4Md2PHao="> <label>2</label> </stream> <sessionrecordingassoc session_id="OWc4Md2PHao="> <associate-time>2018-04-17T09:35:41</associate-time> </sessionrecordingassoc> <participantsessionassoc participant_id="MjAw" session_id="OWc4Md2PHao="> <associate-time>2018-04-17T09:35:41</associate-time> </participantsessionassoc> <participantsessionassoc participant_id="MTAw" session_id="OWc4Md2PHao="> <associate-time>2018-04-17T09:35:41</associate-time> </participantsessionassoc> <participantstreamassoc participant_id="MjAw"> <send>mBfiAAAAAL1hFQENAPA=</send> <recv>hBfiAAAAAL1hFQENAPA=</recv> </participantstreamassoc>...
  • Page 249 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual The following configuration records calls made by IP Group "ITSP" to IP Group "IP-PBX" that have the destination number prefix "1800". The device records the calls from the leg interfacing with IP Group "IP PBX"...
  • Page 250 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Description The default value is the asterisk (*) symbol, meaning any source number or URI. 'Recorded Destination Pattern' Defines calls to record based on destination number or URI. You can use special patterns (notations) to denote the recorded-dst-prefi number or URI.

  • Page 251: Using Conditions For Starting A Siprec Session

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Redundant Recording Server Defines the IP Group of the redundant SRS in the active- (SRS) IP Group' standby pair for SRS redundancy. By default, no value is defined.

  • Page 252: Configuring Format Of Siprec Metadata

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual In the SIP Recording Rules table, configure a SIP Recording rule as desired and assign it the Message Condition rule that you configured in the previous step: ● 'Recorded IP Group': ITSP ●...

  • Page 253: Genesys

    SIP INVITE from Avaya, it adds the UCID value, received in the User-to-User SIP header to the AudioCodes proprietary tag in the XML metadata of the SIP INVITE that it sends to the recording server. For example, if the received SIP header is: User-to-User: 00FA080019001038F725B3;encoding=hex...
  • Page 254 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Value Index Name Store My-header in var.session Manipulation Set ID Message Type Condition Header.My-header exists And Header.My-header != '' Action Subject Var.Session.0 Action Type Modify Action Value Header.My-header Index...
  • Page 255 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Value Action Type Modify Action Value Header.My-header1+','+ Header.My-header2+','+ Header.My- header3 Row Rule Use Current Condition Index Name Send My-header1 to SRS Manipulation Set ID Message Type Invite.Request Condition Var.Session.0 regex (.*),(.*),(.*) Action Subject Header.My-header1...

  • Page 256: Radius-Based Services

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Value Action Value Row Rule Use Previous Condition Assign the above manipulation rules to the relevant IP Groups: In the IP Group of the recorded call leg which sends this header, configure the ◆...
  • Page 257 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual For each RADIUS server, the IP address, port, and shared secret can be configured. Each RADIUS server can be defined for RADIUS-based login authentication and/or RADIUS-based accounting. By setting the relevant port (authentication or accounting) to "0" disables the corresponding functionality.
  • Page 258 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual ➢ To configure a RADIUS server: Open the RADIUS Servers table (Setup menu > IP Network tab > RADIUS & LDAP folder > RADIUS Servers). Click New; the following dialog box appears: Configure a RADIUS server according to the parameters described in the table below.

  • Page 259: Configuring Interface For Radius Communication

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Description The valid value is up to 48 characters. By default, no value is defined. Configuring Interface for RADIUS Communication The device can communicate with the RADIUS server through its' OAMP (default) or SIP Control network interface.

  • Page 260: Radius-Based Management User Authentication

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual ➢ To configure the RADIUS Vendor ID: Open the Authentication Server page (Setup menu > Administration tab > Web & CLI folder > Authentication Server). Under the RADIUS group, in the 'RADIUS VSA Vendor ID' field, enter the same vendor ID number as set on the third-party RADIUS server.

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

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual ■ Set up a RADIUS server (third-party) to communicate with the device - see Setting Up a Third- Party RADIUS Server ■ Configure the device as a RADIUS client for communication with the RADIUS server - see...

  • Page 262: Configuring Radius-Based User Authentication

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Record and retain the IP address, port number, shared secret code, vendor ID, and VSA access level identifier (if access levels are implemented) used by the RADIUS server. Configuring RADIUS-based User Authentication The following procedure describes how to configure RADIUS-based login authentication.

  • Page 263: Securing Radius Communication

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual ● Always: First attempts to authenticate the user using the Local Users table, but if not found, it authenticates the user with the RADIUS server. Click Apply, and then reset the device with a save-to-flash for your settings to take effect.
  • Page 264 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual 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...

  • Page 265: Enabling The Ldap Service

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual If the device finds a group, it assigns the user the corresponding access level and permits login; otherwise, login is denied. Once the LDAP response has been received (success or failure), the device ends the LDAP session.

  • Page 266: Configuring Ldap Server Groups

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual If you enable LDAP- based user login authentication, when users with Security Administrator privilege level log in to the device’s CLI, they are automatically given access to the CLI privileged mode (“#”). For all other user privilege levels, the user needs to run the enable command and then enter the password to access the CLI privileged mode.
  • Page 267 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual device provides preconfigured LDAP Server Group ("DefaultCTRLServersGroupin") in the LDAP Server Groups table, which can be modified or deleted. ➢ To configure an LDAP Server Group: Open the LDAP Server Groups table (Setup menu > IP Network tab > RADIUS & LDAP folder >...

  • Page 268: Configuring Ldap Servers

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Server Search Method' Defines the method for querying between the two LDAP servers in the group. server-search-method ■ [0] Parallel = (Default) The device queries the LDAP [LdapServerGroups_ servers at the same time.
  • Page 269 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual When you configure an LDAP server, you need to assign it an LDAP Server Group. Therefore, before you can configure an LDAP server in the table, you must first configure at least one LDAP Server Group in the LDAP Server Groups table (see Configuring LDAP Server Groups).
  • Page 270 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Use TLS' Enables the device to encrypt the username and password (for Control and Management related queries) use-tls using TLS when sending them to the LDAP server. [LdapConfiguration_useTLS] ■...
  • Page 271 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Description Note: If the 'LDAP Server IP' parameter is configured, the 'LDAP Server Domain Name' parameter is ignored. Thus, if you want to use an FQDN, leave the 'LDAP Server IP' parameter undefined.
  • Page 272 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ The parameter is mandatory. ■ By default, the device sends the password in clear- text format. You can enable the device to encrypt the password using TLS (see the 'Use SSL' parameter below).

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

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'No Op Timeout' Defines the timeout (in minutes) of inactivity in the connection between the device and the LDAP server, noop-timeout after which the device sends an LDAP "abandon"...

  • Page 274: Configuring The Ldap Search Filter Attribute

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Description Note: Each row must be configured with a unique index. set internal-index [LdapServersSearchDNs_ Index] 'Base DN' Defines the full path (DN) to the objects in the AD where the query is done.

  • Page 275: Configuring Access Level Per Management Groups Attributes

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Configuring Access Level per Management Groups Attributes The Management LDAP Groups table lets you configure LDAP group objects and their corresponding management user access level. The table is a "child" of the LDAP Servers table...

  • Page 276: Configuring The Device's Ldap Cache

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual The following procedure describes how to configure an access level per management groups through the Web interface. You can also configure it through ini file [MgmntLDAPGroups] or CLI (configure system > ldap mgmt-ldap-groups).
  • Page 277 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual ■ Provides partial survivability in case of intermittent LDAP server failure (or network isolation) The handling of LDAP queries using the device's LDAP cache is shown in the flowchart below: 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 278: Refreshing The Ldap Cache

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual ● The LDAP Cache feature is applicable only to LDAP-based SIP queries (Control). ● The maximum LDAP cache size is 10,000 entries. ● The device can save up to six LDAP Attributes in the cache per searched LDAP key.

  • Page 279: Clearing The Ldap Cache

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual ➢ To refresh the LDAP cache per LDAP Server Group: Open the LDAP Settings page (Setup menu > IP Network tab > RADIUS & LDAP folder > LDAP Settings). Under the Cache Actions group, do the following:...

  • Page 280: Configuring Local Database For Management User Authentication

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Click Clear Group. Configuring Local Database for Management User Authentication You can configure the device to use the Local Users table (local database) to authenticate management users based on username-password combination. You can configure the device to...
  • Page 281 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual ■ DN (base path): OU=testMgmt,OU=QA,DC=testqa,DC=local. The DN path to search for the username in the directory is shown below: ■ Search Attribute Filter: (sAMAccountName=$). The login username is found based on this...
  • Page 282 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual ■ Management Attribute: memberOf. The attribute contains the member groups of the user: ■ Management Group: mySecAdmin. The group to which the user belongs, as listed under the memberOf attribute:...
  • Page 283 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual The configuration to match the above LDAP data structure schema is as follows: ■ LDAP-based login authentication (management) is enabled in the LDAP Server Groups table (see Configuring LDAP Server Groups): ■...

  • Page 284: Enabling Ldap Searches For Numbers With Characters

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual ■ The group management attribute is configured by the 'Management Attribute' parameter in the LDAP Servers table: ■ The management group and its corresponding access level is configured in the Management...

  • Page 285: Ad-Based Routing For Microsoft Skype For Business

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual To enable the device to search the AD for numbers that may contain characters between its digits, you need to specify the Attribute (up to five) for which you want to apply this functionality, using the LDAPNumericAttributes parameter.
  • Page 286 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Queried User Query or Query Result Parameter Domain Example (Attribute) in AD MSLDAPOCSNumAttributeName Mediation Server / msRTCSIP- Skype for Line=john.smith@company.co Business client number (e.g., "msRTCSIP- Line") MSLDAPMobileNumAttributeNam Mobile number mobile=+3247647156 (e.g., "mobile")
  • Page 287 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual The device adds unique prefix keywords to the query results in order to identify the query type (i.e., IP domain). These prefixes are used as the prefix destination number value in the Tel-to- IP Routing table to denote the IP domains: ●...

  • Page 288: Configuring Ad-Based Routing Rules

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual If you are using the device's local LDAP cache, see Configuring the Device's LDAP Cache for the LDAP query process. Configuring AD-Based Routing Rules The following procedure describes how to configure outbound IP routing based on LDAP queries.
  • Page 289 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Configure the LDAP attribute names as desired. Gateway application: Configure AD-based Tel-to-IP routing rules: Open the Tel-to-IP Routing table (see Configuring Tel-to-IP Routing Rules). Configure query-result routing rules for each IP domain (private, PBX / IP PBX, Skype for...
  • Page 290 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Table 16-14:AD-Based Tel-to-IP Routing Rule Configuration Examples Index Destination Phone Prefix Destination IP Address PRIVATE: 10.33.45.60 PBX: 10.33.45.65 OCS: 10.33.45.68 MOBILE: 10.33.45.100 LDAP_ERR 10.33.45.80 LDAP 10.33.45.72 The table below shows an example for configuring AD-based SBC routing rules in the IP-to-IP...

  • Page 291: Querying The Ad For Calling Name

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual ● LDAP query is successful but call fails (due to, for example, busy line) to all the relevant attribute destinations (private, Skype for Business, PBX, and mobile), and a relevant Tel-...

  • Page 292: Overview

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Overview The LCR feature enables the device to choose the outbound IP destination routing rule based on lowest call cost. This is useful in that it enables service providers to optimize routing costs for customers.
  • Page 293 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Below are a few examples of how you can implement LCR: ■ Example 1: This example uses two different Cost Groups for routing local calls and international calls: Two Cost Groups are configured as shown below:...

  • Page 294: Configuring Lcr

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Cost Group Time Band Start Time End Time Connection Cost Minute Cost CG Local 16:00 17:00 17:00 18:00 Assume that the call duration is 10 minutes, occurring between 16:55 and 17:05. In other words, the first 5 minutes occurs in time band "TB1"...
  • Page 295 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Configure a Cost Group according to the parameters described in the table below. Click Apply, and then save your settings to flash memory. Table 16-17:Cost Groups Table Parameter Descriptions Parameter...
  • Page 296 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual ● You cannot configure overlapping Time Bands. ● If a Time Band is not configured for a specific day and time range, the default connection cost and default minute cost configured for the Cost Group in the Cost Groups table is applied.

  • Page 297: Assigning Cost Groups To Routing Rules

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'End Time' Defines the day and time of day until when this time band is applicable. For a description of the valid values, see the parameter end-time above.
  • Page 298 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual ● Configuration Status: Status is reported when IP Groups, Trunk Groups, (Gateway application only) or SIP Interfaces that are configured to be used by remote Web-based services (i.e., the UsedByRoutingServer parameter is set to 1 - Used) are created or deleted.
  • Page 299 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Index' Defines an index number for the new table row. [HTTPRemoteServices_ Note: Index] ■ Each row must be configured with a unique index. ■ The parameter is mandatory.
  • Page 300 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Description [HTTPRemoteServices_ ■ [0] Round Robin = (Default) The device does load Policy] balancing of traffic across all the hosts in the group. Every consecutive message is sent to the next available host.
  • Page 301 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [1] Enable = (Default) The device creates the HTTP connection once you have configured the service. If the server closes the connection, the device re-opens it. If...
  • Page 302 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [1] Enable = The device verifies the authentication of the certificate received from the HTTPS peer. The device authenticates the certificate against the trusted root certificate store associated with the associated TLS Context (see 'TLS Context' parameter above) and if ok, allows communication with the HTTPS peer.

  • Page 303: Configuring Remote Http Hosts

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Status' (Read-only) Displays the status of the host associated with the Web service. ■ "Connected": At least one of the hosts is connected. ■ "Disconnected": All hosts are disconnected.
  • Page 304 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Table 16-20:HTTP Remote Hosts Table Parameter Descriptions Parameter Description General 'Index' Defines an index number for the new table row. Note: rest-servers [HTTPRemoteHosts_ ■ Each row must be configured with a unique index.

  • Page 305: Enabling Topology Status Services

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [0] HTTP (default) rest-transport- type ■ [1] HTTPS [HTTPRemoteHosts_ HTTPTransportType] Grouping 'Group ID' Defines the host's group ID. The group number (ID) reflects the priority of the group. The device sends traffic to host groups according...

  • Page 306: 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 need for the device's routing tables--IP-to-IP Routing table for SBC calls , and Tel-to-IP Routing table and IP-to-Tel Routing table for Tel-to-IP and IP-to-Tel calls respectively--to determine call destination.
  • Page 307 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual The Routing server can also manipulate call data such as calling name, if required. It can also create new IP Groups and associated configuration entities, if necessary for routing. Multiple Routing servers can also be employed, whereby each device in the chain path can use a specific Routing server.
  • Page 308 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual ■ Call Status: The device can report call status to the Routing server to indicate whether a call has successfully been established and/or failed (disconnected). The device can also report when an IP Group (Proxy Set) is unavailable, detected by the keep-alive mechanism, or when the CAC thresholds permitted per IP Group have been crossed.

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

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Configuring QoS-Based Routing by Routing Server You can configure the device to allow the routing server to route calls based on QoS metrics (media and signaling). The device collects QoS metrics per IP Group that you have configured to operate with the routing server ('Used by Routing Server' parameter configured to Used in the IP Groups table).
  • Page 310 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual ➢ To configure an HTTP GET operation: Open the Remote Web Services table, and then configure a Remote Web Service for the HTTP server: ● 'Name': MyHTTP ● 'Type': General ●...

  • Page 311: Http-Based Proxy Services

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual HTTP/1.1 200 OK Access-Control-Allow-Origin: * Cache-Control: max-age=0 Content-Type: text/html Date: Thu, 07 Dec 2017 14:35:21 GMT Server: nginx/1.8.1 Content-Length: 6 Connection: keep-alive Alice Outgoing SIP message: INVITE sip:2000@10.7.7.246;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.7.7.246:5060;branch=z9hG4bKac1693897511 Max-Forwards: 70 From: Alice <sip:+15551234567@10.7.2.15;user=phone>;tag=1c1900944531...
  • Page 312 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Another example is to use the HTTP Proxy to intermediate between IP Phones and remote servers for file download. The figure below illustrates this example where IP Phones (clients) retrieve their configuration and firmware files from remote file servers (Upstream Hosts) and where the device (HTTP Proxy) intermediates between the two.

  • Page 313: Enabling The Http Proxy Application

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual ■ HTTP-based OVOC service for AudioCodes equipment located behind NAT that are managed by the AudioCodes OVOC server: For more information, see Configuring an HTTP-based OVOC Service on page 288 Enabling the HTTP Proxy Application Before you can configure HTTP- based proxy services, you must enable the HTTP Proxy application, as described in the following procedure.

  • Page 314: Configuring Http Proxy Servers

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual In the 'Primary DNS Server IP' field, enter the IP address of your main DNS server. (Optional) In the 'Secondary DNS Server IP' field, enter the IP address of the secondary DNS server.
  • Page 315 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Description [HTTPServer_Index] Note: ■ Each row must be configured with a unique index. ■ The parameter is mandatory. 'Name' Defines a descriptive name, which is used when associating the row in other tables.

  • Page 316: Configuring Http Locations

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Description Verify Client Enables the verification of the client TLS certificate, where the client Certificate is the device or user that issues the HTTPS request. ■ [0] No = (Default) No certificate verification is done.
  • Page 317 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual The HTTP Locations table is a "child" of the HTTP Proxy Servers table (see Configuring HTTP Proxy Servers on page 274), reflecting the nesting of Location contexts within Server contexts in the NGINX configuration file.
  • Page 318 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [1] Exact = Defines an exact pattern to match, for example, "/abc/def" matches only the file "/abc/def". For NGINX, this option is specified using the "=" modifier.
  • Page 319 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ The NGINX directive for this parameter is "proxy_bind". 'Additional Directive Assigns an NGINX directive set for the HTTP location. To configure Set' NGINX directives, see Configuring HTTP Directive Sets page 286.

  • Page 320: Configuring Tcp-Udp Proxy Servers

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Configuring TCP-UDP Proxy Servers The TCP/UDP Proxy Servers table lets you configure up to 10 TCP/UDP proxy servers. This table allows you to configure the device as a proxy for other applications that are not based on HTTP. For example, it can be used to intermediate between clients and a DNS server for DNS lookup or between clients and an NTP server for clock synchronization.
  • Page 321 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Listening Interface' Assigns a local IP network interface for the listening (source) interface for communication with the TCP-UDP proxy server. To listen-interface configure IP Interfaces, see Configuring IP Network Interfaces [TcpUdpServer_ on page 97.

  • Page 322: Configuring Upstream Groups

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Description Note: ■ The parameter is mandatory. ■ The NGINX directive for this parameter is "proxy_bind". 'Upstream Side SSL' Enables SSL for securing connection requests with the Upstream Group.
  • Page 323 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual An Upstream Group is a set of one or more hosts (Upstream Host) that can serve a particular set of data. The HTTP Proxy distributes the requests among the members (hosts) of the Upstream Group according to the specified load balancing mode.

  • Page 324: Configuring Upstream Hosts

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ To assign the Upstream Group to a TCP/UDP Proxy Server, configure the parameter to TCP/UDP. To configure TCP/UDP Proxy Servers, see Configuring TCP-UDP Proxy Servers page 280. ■...
  • Page 325 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Configure an Upstream Host according to the parameters described in the table below. Click Apply, and then save your settings to flash memory. Table 16-25:Upstream Hosts Table Parameter Descriptions Parameter...

  • Page 326: Configuring Http Directive Sets

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Description Note: The NGINX directive for this parameter is "server ip:port max_conns=n". 'Backup' Enables the host to serve as a backup host. The backup host does not receive any requests unless all backup the primary hosts in the Upstream Group are down.

  • Page 327: Configuring Http Directives

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual ➢ To configure an HTTP Directive Set: Open the HTTP Directive Sets table (Setup menu > IP Network tab > HTTP Proxy folder > HTTP Directive Sets). Click New; the following dialog box appears: Configure an HTTP Directive Set according to the parameters described in the table below.

  • Page 328: Configuring An Http-Based Ovoc Service

    Make sure that you end the directive with a semicolon (;). Configuring an HTTP-based OVOC Service The OVOC Services table lets you configure a single HTTP- based AudioCodes One Voice Operations Center (OVOC) service. You can configure the device to act as an HTTP Proxy that enables OVOC to manage AudioCodes equipment (such as IP Phones) over HTTP when the equipment is located behind NAT (e.g., in the LAN) and OVOC is located in a public domain (e.g., in...
  • Page 329 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual ➢ To configure an OVOC Service: Open the OVOC Services table (Setup menu > IP Network tab > HTTP Proxy folder > OVOC Services). Click New; the following dialog box appears: Configure an OVOC Service according to the parameters described in the table below.
  • Page 330 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Device Scheme' Defines the protocol for communication with the requesting client. device-scheme ■ [0] HTTP (default) [OVOCService_ DeviceScheme] ■ [1] HTTPS Note: If configured to HTTPS, you must assign a TLS Context (see the 'Device Login TLS Context' parameter, below).
  • Page 331 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Description [OVOCService_ ■ [1] HTTPS EMSScheme] Note: ■ If configured to HTTPS, you must assign a TLS Context (see the 'OVOC Interface TLS Context' parameter, below). ■ The NGINX directive for this parameter is "proxy_pass scheme://upstream".

  • Page 332: Troubleshooting Nginx Configuration

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Troubleshooting NGINX Configuration Troubleshooting may be necessary when configuring your HTTP or TCP/UDP proxy services with NGINX directives. Due to the large and complex dictionary of directives supported by NGINX and their complex grammatical structure, the device assists you by validating your configured directives.

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

    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 334: Microsoft Skype For Business And E9-1-1

    Mediant 800 Gateway & E-SBC | User's Manual The VoIP user dials 9-1-1. The 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 335: Gathering Location Information Of Skype For Business Clients For 911 Calls

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Gathering Location Information of Skype for Business Clients for 911 Calls When a Microsoft Skype for Business client is enabled for E9-1-1, the location data that is stored on the client is sent during an emergency call. This stored location information is acquired automatically from the Microsoft Location Information Server (LIS).

  • Page 336: Adding Elins To The Location Information Server

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Link Layer Discovery Protocol-Media Endpoint Discovery (LLDP-MED) chassis ID ◆ and port ID For a Skype for Business client that moves inside the corporate network such as a soft phone...

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

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual <ChassisID>,<Description>,<Location>,<CompanyName>, <HouseNum- ber>,<HouseNumberSuffix>,<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 338: Audiocodes Elin Device For Skype For Business E9-1-1 Calls To Pstn

    ELIN. This ensures that the call is routed to an appropriate PSAP, based on ELIN-address match lookup in the emergency service provider's ALI database. The figure below illustrates an AudioCodes ELIN device deployed in the Skype for Business environment for handling E9-1-1 calls between the company and the emergency service provider.

  • Page 339: Detecting And Handling E9-1-1 Calls

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual 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. The device handles the received E9-1-1 calls as follows: The device identifies E9-1-1 calls if the incoming SIP INVITE message contains a PIDF-LO XML message body.
  • Page 340 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual ELIN Time Count Index Call From 4257275616 22:11:45 4258359777 The ELIN table stores this information for a user-defined period (see Configuring the E9-1-1 Callback Timeout), starting from when the E9-1-1 call, established with the PSAP, terminates.

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

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual <?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>Red mond</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:+14255550199@con toso.com;user=phone</ms:ConferenceUri><ms:ConferenceMode>twoway</ms:Conferen ceMode><LocationPolicyTagID xmlns="urn:schema:Rtc.Lis.LocationPolicyTagID.2008">user-tagid</LocationPolicyTagID ></ms:msftE911PidfExtn></status><timestamp>1991-09- 22T13:37:31.03</timestamp></tuple></presence> ------=_NextPart_000_4A6D_01CAB3D6.7519F890-- Pre-empting Existing Calls for E9-1-1 Calls...

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

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual In the ELIN table of the device, the temporarily stored From header value of the SIP INVITE message originally received from the E9-1-1 caller is used for PSAP callback. When the PSAP makes a callback to the E9-1-1 caller, the device translates the called number (i.e., ELIN) received...

  • Page 343: Location Based Emergency Routing

    Routing. Location-based emergency routing is applicable only to the Gateway application. Configuring AudioCodes ELIN Device This section describes E9-1-1 configuration of the AudioCodes ELIN Gateway deployed in the Skype for Business environment. 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 344: Configuring The Sip Release Cause Code For Failed E9-1-1 Calls

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual ➢ To configure the E9-1-1 callback timeout Open the Priority & Emergency page (Setup menu > Signaling & Media tab > SIP Definitions folder > Priority and Emergency). In the 'E911 Callback Timeout' field (E911CallbackTimeout), enter the required callback timeout.

  • Page 345: Configuring Location-Based Emergency Routing

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Configuring Location-Based Emergency Routing The device identifies the geographical location of emergency callers by their ELIN numbers, which is present in the PIDF-LO XML body of received SIP INVITE messages. Therefore, you need to configure the device to route emergency calls to a destination (i.e., emergency center such as...

  • Page 346: Viewing The Elin Table

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual In the Destination Phone Number Manipulation for IP-to-Tel Calls table (see Configuring Source/Destination Number Manipulation), add the following two rules for manipulating the destination number of incoming emergency calls, based on ELIN numbers: Index 0 manipulates the destination number for London emergency callers;...
  • Page 347 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual The device notifies the Skype for Business Server of a user's presence status, by using SIP PUBLISH messages. The message transactions between the device and Skype for Business Server is as follows: The device routes a call between two Skype for Business users and when connected, sends a PUBLISH message with the Event header set to "presence", Expires header set to "600",...

  • Page 348: Configuring Skype For Business Server For Presence

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual When the call ends, the device sends a PUBLISH message to cancel the user's online presence status (and the user's previous presence state is restored). The message is sent with a SIP-If-Match header set to the matching entity tag (SIP-ETag) value (i.e., SIP-ETag value of...

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

    CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Obtain the Site ID Run the following cmdlet to retrieve the SiteId property of the site: Get-CsSite Create a Trusted Application Pool Run the following cmdlet to create a new pool to host the presence application: New-CsTrustedApplicationPool -Identity <Pool FQDN>...
  • Page 350 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual The device uses a Call Setup Rule to perform LDAP queries on the Microsoft Active Directory to retrieve Skype for Business usernames (Request URIs) for the corresponding calling (source) and/or called (destination) number. For SBC calls, the Call Setup Rule is associated with the classified source IP Group (in the IP Groups table).
  • Page 351 CHAPTER 16    Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Rule 1 Rule 2 'Request Type' LDAP LDAP 'Request Key' 'mobile=+' + param.call.dst.user 'mobile=+' + param.call.src.user 'Attributes To Get' ipPhone ipPhone 'Condition' ldap.attr.ipPhone exists ldap.attr.ipPhone exists 'Action Subject' presence.dst presence.src...

  • Page 352: Quality Of Experience

    This chapter describes how to configure the Quality of Experience feature. Reporting Voice Quality of Experience to OVOC The device can be configured to report voice (media) Quality of Experience (QoE) to AudioCodes' One Voice Operations Center (OVOC). The reports include real-time metrics of the quality of the actual call experience, which are then processed by OVOC.

  • Page 353: Configuring The Ovoc Server For Qoe

    CHAPTER 17    Quality of Experience Mediant 800 Gateway & E-SBC | User's Manual ● For SNMP v3: In the SNMPv3 Users table (see Configuring SNMP V3 Users), configure an SNMPv3 user for authentication and privacy. In the SNMP Trap Destinations table (see Configuring SNMP Trap Destinations with IP Addresses), configure OVOC (defined by IP address and port) as the destination to where the device sends traps.
  • Page 354 CHAPTER 17    Quality of Experience Mediant 800 Gateway & E-SBC | User's Manual Click Apply, and then reset the device with a save-to-flash for your settings to take effect. Table 17-1: Quality of Experience Settings Parameter Descriptions Parameter Description General 'Index' Defines an index number for the new table row.
  • Page 355 CHAPTER 17    Quality of Experience Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'TLS Context' Assigns a TLS Context (certificate) for the TLS connection with the OVOC server. tls-context-name The default is the default TLS Context (ID 0). [QOESettings_ContextName] Note: The parameter is applicable only if the 'Use TLS' parameter is configured to Enable.

  • Page 356: Configuring Clock Synchronization Between Device And Ovoc

    Enabling RTCP XR Reporting to OVOC For the device to be able to send voice metric reports to AudioCodes OVOC, you need to enable the RTP Control Protocol Extended Reports (RTCP XR) VoIP management protocol. RTCP XR defines a set of voice metrics that contain information for assessing VoIP call quality and diagnosing problems.
  • Page 357 CHAPTER 17    Quality of Experience Mediant 800 Gateway & E-SBC | User's Manual ■ Packet Loss: Lost packets are RTP packets that are not received by the voice endpoint. Packet loss can result in choppy voice transmission. ■ Jitter: Jitter can result from uneven delays between received voice packets. To space evenly, the device's jitter buffer adds delay.
  • Page 358 Each time a voice metric threshold is crossed (i.e., color changes), the device can do the following depending on configuration: ■ Report the change in the measured metrics to AudioCodes' OVOC. OVOC displays this call quality status for the associated link (IP Group, Media Realm, or Remote Media Subnet). To configure the OVOC's address, see Configuring the SEM Server.
  • Page 359 CHAPTER 17    Quality of Experience Mediant 800 Gateway & E-SBC | User's Manual Configure a QoE Profile according to the parameters described in the table below. Click Apply. Table 17-3: Quality of Experience Profile Table Parameter Descriptions Parameter Description 'Index' Defines an index number for the new table row.
  • Page 360 CHAPTER 17    Quality of Experience Mediant 800 Gateway & E-SBC | User's Manual Click New, and then save your settings to flash memory. Table 17-4: Quality of Experience Color Rules Table Parameter Descriptions Parameter Description General 'Index' Defines an index number for the new table row.

  • Page 361: Configuring Bandwidth Profiles

    CHAPTER 17    Quality of Experience Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ Echo measures the Residual Echo Return Loss (RERL) in dB. 'Minor Hysteresis Defines the amount of fluctuation (hysteresis) from the Minor (Yellow)' threshold, configured by the 'Minor Threshold (Yellow)' parameter in order for the threshold to be considered as crossed.
  • Page 362 ■ Send an SNMP alarm (acMediaRealmBWThresholdAlarm). The device clears the alarm when bandwidth utilization returns to normal (Green). AudioCodes One Voice Operations Center (OVOC) displays bandwidth utilization using color- coded states: ■ Green: Indicates bandwidth utilization is within normal range.
  • Page 363 CHAPTER 17    Quality of Experience Mediant 800 Gateway & E-SBC | User's Manual Table 17-5: Threshold Crossings based on Threshold and Hysteresis Threshold Threshold Calculation based on Crossing Example Green to The change occurs if the current bandwidth crosses the 32,000 Kbps Yellow (Minor configured Minor threshold only (i.e., hysteresis is not...
  • Page 364 CHAPTER 17    Quality of Experience Mediant 800 Gateway & E-SBC | User's Manual Configure a rule according to the parameters described in the table below. Click Apply, and then reset the device with a save to flash memory. Table 17-6: Bandwidth Profile Table Parameter Descriptions...
  • Page 365 CHAPTER 17    Quality of Experience Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Total Egress Bandwidth' Defines the major (total) threshold for video and audio outgoing bandwidth (in Kbps). total-egress-bandwidth [BWProfile_ TotalEgressBandwidth] 'Total Ingress Bandwidth' Defines the major (total) threshold for video and audio incoming bandwidth (in Kbps).

  • Page 366: Configuring Quality Of Service Rules

    CHAPTER 17    Quality of Experience Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [1] Enable 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 367 CHAPTER 17    Quality of Experience Mediant 800 Gateway & E-SBC | User's Manual 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.
  • Page 368 CHAPTER 17    Quality of Experience Mediant 800 Gateway & E-SBC | User's Manual Parameter Description Action 'Rule Action' Defines the action to be done if the rule is matched. ■ [0] Reject Calls = (Default) New calls destined to the rule-action specified IP Group are rejected for a user-defined duration.

  • Page 369: Core Entities

    CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Core Entities This section describes configuration of core SIP entities. Configuring Media Realms The Media Realms table lets you configure a pool of up to 12 SIP media interfaces, termed Media Realms.
  • Page 370 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Configure the Media Realm according to the parameters described in the table below. Click Apply. Table 18-1: Media Realms table Parameter Descriptions Parameter Description General 'Index' Defines an index number for the new table row.
  • Page 371 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description To configure IP network interfaces, see Configuring IP Network ipv6if Interfaces. [CpMediaRealm_ IPv6IF] 'Port Range Start' Defines the starting port for the range of media interface UDP ports.

  • Page 372: Configuring Remote Media Subnets

    CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Default Media Defines the Media Realm as the default Media Realm. The default Realm' Media Realm is used for SIP Interfaces and IP Groups for which you have not assigned a Media Realm.
  • Page 373 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual The following procedure describes how to configure Remote Media Subnets through the Web interface. You can also configure it through ini file [RemoteMediaSubnet] or CLI (configure voip > remote-media-subnet).

  • Page 374: Configuring Media Realm Extensions

    CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description [RemoteMediaSubnet_ Note: Each row must be configured with a unique index. RemoteMediaSubnetIndex] 'Name' Defines a descriptive name, which is used when associating the row in other tables.
  • Page 375 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Media Realm Extensions can be useful, for example, to overcome limitations of the maximum number of media ports supported per interface. Instead of configuring only a single Media Realm in...
  • Page 376 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Table 18-3: Media Realm Extension Table Parameter Descriptions Parameter Description 'Index' Defines an index number for the new table row. [MediaRealmExtension_ Note: Each row must be configured with a unique index.

  • Page 377: Configuring Srds

    CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ The port range must not overlap with any other media port range configured for other Media Realm Extensions, Media Realms, or SIP Interfaces that are associated with the same IP network interface.
  • Page 378 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual ● It is recommended to use a single-SRD configuration topology, unless you are deploying the device in a multi-tenant environment, in which case multiple SRDs are required. ● Each SIP Interface, Proxy Set, and IP Group can be associated with only one SRD.
  • Page 379 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Configure an SRD according to the parameters described in the table below. Click Apply. Table 18-4: SRDs table Parameter Descriptions Parameter Description General 'Index' Defines an index for the new table row.
  • Page 380 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'SBC Operation Mode' Defines the device's operational mode for the SRD. ■ [0] B2BUA = (Default) Device operates as a sbc-operation-mode back-to-back user agent (B2BUA), changing the...
  • Page 381 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ The parameter is applicable only to the SBC application. 'Used By Routing Server' Enables the SRD to be used by a third-party routing server for call routing decisions.
  • Page 382 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [2] Accept Registered Users from Same Source = Accepts requests only from registered users whose source address is the same as that registered with the device (during the REGISTER message process).

  • Page 383: Filtering Tables In Web Interface By Srd

    CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description In normal operation scenarios in which the proxy server is available, the device forwards the REGISTER request to the proxy and if authenticated by the proxy (i.e., device receives a success response), the device adds the user to its registration database.

  • Page 384: Multiple Srds For Multi-Tenant Deployments

    CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual The filter is applied throughout the Web GUI. When you select an SRD for filtering, the Web interface displays only table rows associated with the filtered SRD. When you add a new row to a table, the filtered SRD is automatically selected as the associated SRD.
  • Page 385 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual To create a multi-tenant configuration topology that is as non-bleeding as possible, you can configure an SRD (tenant) as Isolated and Shared: ■ Isolated SRD: An Isolated SRD has its own dedicated SIP resources (SIP Interfaces, Proxy Sets, and IP Groups).
  • Page 386 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual To facilitate multi-tenant configuration through CLI, you can access a specific tenant "view". Once in a specific tenant view, all configuration commands apply only to the currently viewed tenant.

  • Page 387: Cloning Srds

    CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Cloning SRDs You can clone (duplicate) existing SRDs. This is especially useful when operating in a multi-tenant environment and you need to add new tenants (SRDs). The new tenants can quickly and easily be added by simply cloning one of the existing SRDs.

  • Page 388: Automatic Configuration Based On Srd

    CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Automatic Configuration based on SRD To facilitate configuration and eliminate possible flaws in configuration due to invalid associations between configuration entities, the Web interface automatically configures configuration entities based on SRD: ■...
  • Page 389 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual ■ (SBC application only) 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.
  • Page 390 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Table 18-5: SIP Interfaces table Parameter Descriptions Parameter Description 'SRD' Assigns an SRD to the SIP Interface. If only one SRD is configured in the SRDs table, the srd-name SRD is assigned to the SIP Interface by default.
  • Page 391 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'UDP Port' Defines the device's listening and source port for SIP signaling traffic over UDP. udp-port The valid range is 1 to 65534. The default is 5060.
  • Page 392 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ Assigning a unique port per registered user (User- type IP Group) on the leg interfacing with the proxy server (Server-type IP Group). For enabling this feature and for more information, see the 'User UDP Port Assignment' parameter in the IP Groups table.
  • Page 393 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ The maximum number of ports in the range is limited to the maximum number of licensed registered SBC users as specified in the License Key installed on the device, or the maximum...
  • Page 394 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ For static port allocation (i.e., using additional UDP ports feature for assigning a specific local port to each SIP entity), configure the parameter to Always Open.
  • Page 395 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ The device performs Pre-Parsing Manipulation before Pre-Classification Manipulation and Classification. 'CAC Profile' Assigns a Call Admission Control Profile (CAC rules) to the SIP Interface. cac-profile By default, no value is defined.
  • Page 396 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description Note: ■ The Message Manipulation Set assigned to a SIP Interface that is associated with an outgoing call, is ignored. Only the Message Manipulation Set assigned to the associated IP Group is applied to the outgoing call.
  • Page 397 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ Call Setup Rules can be used to generated source and destination tags. For classification, only source tags are used. ■ The parameter is applicable only to the SBC application.
  • Page 398 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ If you enable direct media for the SIP Interface, make sure that your Media Realm provides sufficient ports, as media may traverse the device for mid-call services (e.g., call transfer).
  • Page 399 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [1] Accept Registered Users = Accepts requests only from users registered with the device. Requests from users not registered are rejected. ■ [2] Accept Registered Users from Same...
  • Page 400 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description In normal operation scenarios in which the proxy server is available, the device forwards the REGISTER request to the proxy and if authenticated by the proxy (i.e., device receives a success response), the device adds the user to its registration database.

  • Page 401: Configuring Ip Groups

    CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Configuring IP Groups The IP Groups table lets you configure up to 80 IP Groups. An IP Group represents a SIP entity in the network with which the device communicates. This can be a server (e.g., IP PBX or ITSP) or a group of users (e.g., LAN IP phones).
  • Page 402 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual ➢ To configure an IP Group: Open the IP Groups table (Setup menu > Signaling & Media tab > Core Entities folder > IP Groups). Click New; the following dialog box appears: Configure an IP Group according to to the parameters described in the table below.
  • Page 403 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description [IPGroup_TopologyLocation] ■ [0] Down = (Default) The IP Group element is displayed on the lower border of the view. ■ [1] Up = The IP Group element is displayed on the upper border of the view.
  • Page 404 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ✔ 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...
  • Page 405 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'IP Profile' Assigns an IP Profile to the IP Group. By default, no value is defined. ip-profile-name [IPGroup_ProfileName] To configure IP Profiles, see Configuring IP Profiles. 'Media Realm' Assigns a Media Realm to the IP Group.
  • Page 406 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ The parameter overrides inbound message manipulation rules that manipulate the host name in Request-URI, To, and/or From SIP headers. If you configure the parameter and you want to manipulate...
  • Page 407 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ "Connected": Keep-alive success (i.e., connectivity with the IP Group). The connectivity status is also displayed in the Topology View page (see Building and Viewing SIP Entities in Topology View).
  • Page 408 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ For security, it is recommended to classify SIP dialogs based on Proxy Set only if the IP address of the IP Group is unknown. In other words, if the Proxy Set associated with the IP Group is configured with an FQDN.
  • Page 409 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description For more information on B2BUA and Stateful Proxy modes, see B2BUA and Stateful Proxy Operating Modes. Note: If configured, the parameter overrides the 'SBC Operation Mode' parameter in the SRDs table.
  • Page 410 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description If the parameter is not configured, these headers are populated with the device's dotted-decimal IP address of the network interface on which the message is sent. By default, no value is defined.
  • Page 411 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [2] Request-URI ■ [3] P-Asserted - First Header ■ [4] P-Asserted - Second Header ■ [5] P-Preferred ■ [6] Route ■ [7] Diversion ■ [8] P-Associated-URI ■...
  • Page 412 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [8] P-Associated-URI ■ [9] P-Called-Party-ID ■ [10] Contact ■ [11] Referred-by Note: ■ The parameter is applicable only when classification is done according to the Classification table.
  • Page 413 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description The device classifies incoming non-REGISTER SIP dialog requests (e.g., INVITEs) from this IP Group, by first using the regular user search method in the registration database by Contact-AoR pair matching.
  • Page 414 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [0] No = (Default) The device creates a new Call-ID value for the outgoing message. ■ [1] Yes = The device uses the same Call-ID value received in the incoming message for the Call-ID in the outgoing message.
  • Page 415 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description The valid value is a string of up to 70 characters. You can configure the parameter with up to five tags, where each tag is separated by a semicolon (;). Each tag can have a name and value (e.g., Country=Ireland) or only a...
  • Page 416 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ The IPGroup_SIPGroupName parameter overrides inbound message manipulation rules (assigned to the IPGroup_InboundManSet parameter) that manipulate the host name in Request-URI, To, and/or From SIP headers. If you want to manipulate...
  • Page 417 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [0] Disable = (Default) The IP Group's settings are not applied to the OPTIONS messages. ■ [1] Enable = The following IP Group settings are applied (if configured) to the proxy keep-alive SIP OPTIONS messages: ✔...
  • Page 418 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [0] Disable = After a successful initial registration of the user to a registrar, whenever the device receives a SIP request or registration refresh from the user, the device sends the request to whichever registrar (IP address of the Proxy Set) is currently active.
  • Page 419 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ The Proxy Set's Hot-Swap feature (for proxy redundancy) is not supported for users that are already bound to a registrar. However, you can achieve proxy "hot-swap" for failed initial (non- bounded) REGISTER requests.
  • Page 420 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description The device assigns a unique port upon the first REGISTER request received from the user. Sub- sequent SIP messages other than REGISTER mes- sages (e.g., INVITE) from the user are sent to the proxy server on this unique local port.
  • Page 421 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description If there is no Account in the Accounts table for the Served IP Group and Serving IP Group (i.e., the IP Group you are now configuring), the...
  • Page 422 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description [IPGroup_ ■ [-1] According to Global Parameter = (Default) TypeSBCServerAuthType] Authentication is according to the settings of the SBCServerAuthMode parameter. ■ [0] Authentication is performed locally = The device authenticates incoming SIP requests locally.
  • Page 423 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description Note: If you configure the 'Authentication Mode' parameter to SBC as Server, you can specify the SIP request (method) types (e.g., INVITE) that must be challenged by the device, using the IP Group's 'Authentication Method List' parameter.

  • Page 424: Configuring Proxy Sets

    CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description GW Group Status 'GW Group Registered IP Address' (Read-only field) Displays the IP address of the IP Group entity (gateway) if registered with the device; otherwise, the field is blank.
  • Page 425 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual To use a configured Proxy Set, you need to assign it to an IP Group in the IP Groups table (see Configuring IP Groups). When the device sends INVITE messages to an IP Group, it sends it to the address configured for the Proxy Set.
  • Page 426 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Configure the address of the Proxy Set according to the parameters described in the table below. Click Apply. Table 18-7: Proxy Sets Table and Proxy Address Table Parameter Description...
  • Page 427 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'SBC IPv4 SIP Assigns an IPv4-based SIP Interface for SBC calls to the Proxy Interface' Set. Note: sbcipv4-sip-int- name ■ At least one SIP Interface must be assigned to the Proxy Set.
  • Page 428 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Proxy Keep-Alive' Enables the device's Proxy Keep-Alive feature, which checks connectivity with all the proxy servers of the Proxy Set, by sending proxy-enable- keep-alive messages. keep-alive ■...
  • Page 429 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description [ProxySet_ Note: The parameter is applicable only if the 'Proxy Keep-Alive' ProxyKeepAliveTime] parameter is set to Using Options. 'Keep-Alive Failure Defines SIP response codes that if any is received in response to a...
  • Page 430 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description Redundancy 'Redundancy Mode' Enables the proxy redundancy mode. ■ [-1] = Not configured (Default). Proxy redundancy method is proxy-redundancy- according to the settings of the global parameter mode [ProxyRedundancyMode].
  • Page 431 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ✔ No response is received from the proxy each time the device re-sends it. The number of retransmissions is configured by the [HotSwapRtx] parameter. In such a scenario, the device issues itself the SIP response code 408 (Request Timeout).
  • Page 432 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Min. Active Servers for Defines the minimum number of proxies in the Proxy Set that must Load Balancing' be online for the device to consider the Proxy Set as online, when proxy load balancing is used.
  • Page 433 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ✔ If no match is found for above, it selects the Proxy Set whose IP address match the source of the incoming SIP request (if the parameter is configured to IP Address Only).
  • Page 434 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [3] Microsoft Skype for Business = An SRV query is done as required by Microsoft when the device is deployed in a Microsoft Skype for Business environment. The device sends a...
  • Page 435 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ If you are configuring the Proxy Sets with IP addresses, it is highly recommended to configure each Proxy Set with a unique IP address. Configuring multiple Proxy Sets with the same IP address can cause problems classifying incoming SIP requests to source IP Groups based on Proxy Set.

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

    CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ The parameter is applicable to load balancing (see the 'Proxy Load Balancing Method' parameter), and homing and parking redundancy (see the 'Redundancy Mode' parameter). 'Proxy Random Weight' Defines the weight of the proxy.
  • Page 437 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Table 18-8: Description of Topology View Item # Description Demarcation area of the topology. By default, the Topology view displays the following names to represent the different demarcations of your voice configuration: ■...
  • Page 438 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Item # Description By default, configuration entities are displayed on the bottom border. To define the position, use the 'Topology Location' parameter when configuring the entity, where Down is the bottom border and Up the top border: Configured SIP Interfaces.
  • Page 439 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Item # Description If you hover your mouse over the icon, a pop-up appears displaying the following basic information (example): If you click the icon, a drop-down menu appears listing the following commands: ■...
  • Page 440 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Item # Description ■ Edit: Opens a dialog box in the IP Groups table to modify the IP Group. ■ Show List: Opens the IP Groups table. ■ Delete: Opens the IP Groups table where you are prompted to confirm deletion of the IP Group.
  • Page 441 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Item # Description ■ Routing: Opens the IP-to-IP Routing table where you can configure IP-to-IP routing rules (see Configuring SBC IP-to-IP Routing Rules). ■ SBC Settings: Opens the SBC General Settings page where you can configure miscellaneous settings.
  • Page 442 CHAPTER 18    Core Entities Mediant 800 Gateway & E-SBC | User's Manual Item # Description ■ GW Settings: Opens the Gateway General Settings page where you can configure general gateway related settings. - 402 -...

  • Page 443: Coders And Profiles

    CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Coders and Profiles This section describes configuration of coders and SIP profiles. Configuring Coder Groups The Coder Groups table lets you configure up to 11 Coder Groups. The Coder Group determines the audio (voice) coders used for calls.
  • Page 444 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual ● For supported audio coders, see Supported Audio Coders. ● Some coders are license-based and are available only if included in the License Key installed on your device. For more information, contact the sales representative of your purchased device.
  • Page 445 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual ➢ To delete a Coder Group: From the 'Coder Group Name' drop-down list, select the Coder Group that you want to delete. Click Delete Group. Table 19-1: Coder Groups Table Parameter Descriptions...

  • Page 446: Supported Audio Coders

    CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description Note: The AMR payload type can be configured globally using the AmrOctetAlignedEnable parameter. However, the Coder Group configuration overrides the global parameter. Supported Audio Coders The table below lists the coders supported by the device.
  • Page 447 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Packetization Time (msec) Coder Silence [1] 10, [2] 20, [3] 30, [4] Rate (kbps) Payload Type Name Suppression 40, [5] 50, [6] 60, [8] 80, [9] 90, [10] 100, [12] 120 ■...
  • Page 448 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Packetization Time (msec) Coder Silence [1] 10, [2] 20, [3] 30, [4] Rate (kbps) Payload Type Name Suppression 40, [5] 50, [6] 60, [8] 80, [9] 90, [10] 100,...

  • Page 449: Configuring Various Codec Attributes

    CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Packetization Time (msec) Coder Silence [1] 10, [2] 20, [3] 30, [4] Rate (kbps) Payload Type Name Suppression 40, [5] 50, [6] 60, [8] 80, [9] 90, [10] 100,...

  • Page 450: Configuring Allowed Audio Coder Groups

    CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Configuring Allowed Audio Coder Groups The Allowed Audio Coders Groups table lets you configure up to 10 Allowed Audio Coders Groups for SBC calls. For each Allowed Audio Coders Group, you can configure up to 10 audio coders. The coders can include pre-defined coders and user-defined (string) coders for non-standard or unknown coders.
  • Page 451 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Click New; the following dialog box appears: Configure a name for the Allowed Audio Coders Group according to the parameters described in the table below. Click Apply. Select the new row that you configured, and then click the Allowed Audio Coders link located below the table;...

  • Page 452: Configuring Allowed Video Coder Groups

    CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description Allowed Audio Coders Table 'Index' Defines an index number for the new table row. Note: Each row must be configured with a unique allowed-audio-coders index. <group index/coder index>...
  • Page 453 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Click New; the following dialog box appears: Configure a name for the Allowed Video Coders Group according to the parameters described in the table below. Click Apply. Select the new row that you configured, and then click the Allowed Video Coders link located below the table;...

  • Page 454: Configuring Ip Profiles

    CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Index' Defines an index number for the new table row. Note: Each row must be configured with a unique allowed-video-coders index. <group index/coder index> [AllowedVideoCoders_ AllowedVideoCodersIndex] 'User Define Coder' Defines a user-defined coder.
  • Page 455 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Configure an IP Profile according to the parameters described in the table below. Click Apply. Table 19-5: IP Profiles Table Parameter Descriptions Parameter Description General 'Index' Defines an index number for the new table row.
  • Page 456 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 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: ■...
  • Page 457 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description Note: ■ The parameter is applicable only to the Gateway application. ■ The parameter is applicable only when the EnableMediaSecurity parameter is set to 1. ■...
  • Page 458 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ Gateway application: The device only initiates the MKI size. ■ SBC application: The device can forward MKI size as is for SRTP-to-SRTP flows or override the MKI size during negotiation.
  • Page 459 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ As DTLS has been defined by the WebRTC standard as mandatory for encrypting media channels for SRTP key exchange, the support is important for deployments implementing WebRTC.
  • Page 460 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'SBC Remove Unknown Crypto' Defines whether the device keeps or removes unknown cryptographic suites (encryption and authentication sbc-remove-unknown- algorithms) that are present in the SDP 'a=crypto' attribute...
  • Page 461 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Remote Multiple Early Dialogs' Defines the device's handling of To-header tags in call forking responses (i.e., multiple SDP answers) sent to the sbc-multi-early-diag SIP entity associated with the IP Profile. When the SIP...
  • Page 462 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description Note: If the parameter and the SBCRemoteMultipleAnswersMode parameter are disabled, multiple SDP answers are not reflected to the SIP entity (i.e., the device sends the same SDP answer in multiple 18x and 200 responses).
  • Page 463 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Generate RTP' Enables the device to generate "silence" RTP packets to the SIP entity until it detects audio RTP packets from the sbc-generate-rtp SIP entity. The parameter provides support for interworking...
  • Page 464 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ The corresponding global parameter is TranscodingMode. 'Extension Coders Group' Assigns a Coder Group for extension coders, which are added to the SDP offer in the outgoing leg for the SIP entity sbc-ext-coders-group- associated with the IP Profile.
  • Page 465 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Allowed Video Coders' Assigns an Allowed Video Coders Group. This defines permitted video coders when forwarding video streams to allowed-video-coders- the SIP entity associated with the IP Profile. The video group-name coders are listed in the "video"...
  • Page 466 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [2] Disallow = The device removes RFC 2833 from the incoming offer. Note: If the device interworks between different DTMF methods and one of the methods is in-band DTMF packets (in RTP), detection and generation of DTMF methods requires DSP resources.
  • Page 467 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description If you have enabled the parameter, you can also configure the device to stop sending DTMF digits using the SIP INFO method if the device receives a SIP re-INVITE (or...
  • Page 468 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ✔ Action Value: 'switch-profile;profile-name=ITSP- Profile-1' The Message Manipulation rules must be assigned to the SIP entity's IP Group, using the 'Inbound Message Manipulation Set' parameter. Note: ■...
  • Page 469 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description SDP in outgoing 200 OK: m=audio 6370 RTP/AVP 97 99 a=rtpmap:99 telephone-event/16000/1 a=fmtp:99 0-15 a=sendrecv a=ptime:20 a=maxptime:120 a=rtpmap:97 AMR-WB/16000 a=fmtp:97 mode-change-capability=2;mode- set=0,1,2,3,4,5,6,7, Note: The parameter is applicable only to the SBC application.
  • Page 470 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description Note: The parameter requires DSP resources. 'RTP Redundancy Mode' Enables interworking RTP redundancy negotiation support between SIP entities in the SDP offer-answer exchange sbc-rtp-red-behav (according to RFC 2198). The parameter defines the...
  • Page 471 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'RTCP Mode' Defines how the device handles RTCP packets during call sessions for the SIP entity associated with the IP Profile. sbc-rtcp-mode This is useful for interworking RTCP between SIP entities.
  • Page 472 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description Note: As ICE has been defined by the WebRTC standard as mandatory, the support is important for deployments implementing WebRTC. For more information on WebRTC, see WebRTC.
  • Page 473 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description For multiplexing, the initial SDP offer must include the "a=rtcp-mux" attribute to request multiplexing of RTP and RTCP onto a single port. If the SDP answer wishes to multiplex RTP and RTCP, it must also include the "a=rtcp-...
  • Page 474 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [2] As Is = The device does not involve itself in the feedback, but simply forwards any feedback indication as is. Note: ■ As RTCP-based feedback has been defined by the WebRTC standard as mandatory, the support is important for deployments implementing WebRTC.
  • Page 475 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Dynamic Jitter Buffer Defines the Dynamic Jitter Buffer frame error/delay Optimization Factor' optimization factor. The valid range is 0 to 12. The default factor is 10.
  • Page 476 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [2] Mandatory = PRACK is required for this SIP entity. Calls from endpoints that do not support PRACK are rejected. Calls destined to these endpoints are also required to support PRACK.
  • Page 477 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description For more information on interworking of the History-Info and Diversion headers, see Interworking SIP Diversion and History-Info Headers. 'Session Expires Mode' Defines the required session expires mode for the SIP entity associated with the IP Profile.
  • Page 478 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [1] Supported only with SDP = re-INVITE is supported, but only with SDP. If the incoming re- INVITE arrives without SDP, the device creates an SDP and adds it to the outgoing re-INVITE.
  • Page 479 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Keep Incoming Via Headers' Enables interworking SIP Via headers between SIP entities. The parameter defines the device's handling of Via sbc-keep-via-headers headers for messages sent to the SIP entity associated [IpProfile_ with the IP Profile.
  • Page 480 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Keep User-Agent Header' Enables interworking SIP User-Agent headers between SIP entities. The parameter defines the device's handling sbc-keep-user-agent of User-Agent headers for response/request messages [IpProfile_ sent to the SIP entity associated with the IP Profile.
  • Page 481 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [1] Spirou = SPIROU (ISUP France) 'Max Call Duration' Defines the maximum duration (in minutes) per SBC call that is associated with the IP Profile. If the duration is sbc-max-call-duration reached, the device terminates the call.
  • Page 482 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'NAT TCP Registration Time' Defines the registration time (in seconds) that the device includes in register responses, in response to SIP sbc-usr-tcp-nat-reg- REGISTER requests from users belonging to the SIP time entity associated with the IP Profile.
  • Page 483 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description The special prefix is removed before the resultant INVITE is sent to the destination ((transfer target). ■ [2] IP Group Name = Changes the host part in the REFER message to the name configured for the IP Group (in the IP Groups table).
  • Page 484 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [1] Handle Locally = The SIP entity does not support INVITE messages containing Replaces headers. The device terminates the received INVITE containing the Replaces header and establishes a new call between the SIP entity and the new call party.
  • Page 485 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ The 'Remote Early Media RTP Behavior parameter is set to Delayed (used in the Skype for Business environment), and transfer target sends a 183 Session Progress with SDP offer.
  • Page 486 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [2] Handle Locally = The device handles SIP 3xx responses on behalf of the dialog-initiating UA and retries the request (e.g., INVITE) using one or more alternative URIs included in the 3xx response.
  • Page 487 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [0] Transparent = (Default) Device forwards SDP as ■ [1] Send Only = Device sends SDP with 'a=sendonly'. ■ [2] Send Only Zero Ip = Device sends SDP with 'a=sendonly' and 'c=0.0.0.0'.
  • Page 488 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [2] External = Plays MoH audio streams that originate from an external media source. For more information, Configuring SBC MoH from External Media Source on page 850...
  • Page 489 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Fax Answer Mode' Defines the coders included in the outgoing SDP answer (sent to the calling "fax") for the SIP entity associated with sbc-fax-answer-mode the IP Profile.
  • Page 490 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ This feature is applicable only when both SIP entities do not fully support fax detection (receive or send) and negotiation: one SIP entity must be assigned an IP...
  • Page 491 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ If during a call the source IP address (from where the RTP packets are received by the device) is changed without notifying the device, the device rejects these RTP packets.
  • Page 492 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description If you configure the parameter to a "prefer" option, the outgoing SDP offer contains two medias which are the same except for the "c=" field. The first media is the preferred address type (and this type is also on the session level "c="...
  • Page 493 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description [IpProfile_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 494 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ The parameter is applicable only to digital interfaces. ■ This parameter is applicable only to IP-to-Tel ISDN calls and applies to all calls. ■ To enable this feature, set the [EnableEarlyMedia] parameter to [1].
  • Page 495 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [1] Enable = Plays a ringback tone after a SIP 183 session progress response is sent. Note: ■ To enable the device to send a 183/180+SDP responses, set the EnableEarlyMedia parameter to 1.
  • Page 496 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ✔ Analog: For IP-to-Tel calls, if the EnableEarlyMedia parameter is set to 1, the device sends a 183 Session Progress message with SDP immediately after a call is placed to the analog line.
  • Page 497 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ The feature is similar to that of the EnableISDNTunnelingIP2Tel parameter. If both parameters are configured, the EnableISDNTunnelingIP2Tel parameter takes precedence. ■ The corresponding global parameter is AddIEinSetup.
  • Page 498 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [2] Before Manipulation = Copies the called number before manipulation. The device first copies the original called number to the SIP Diversion header, and then performs IP-to-Tel destination phone number manipulation.
  • Page 499 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description Note: ■ When out-of-band DTMF transfer is used ([1], [2], [3], or [5]), the DTMFTransportType parameter is automatically set to 0 (DTMF digits are removed from the RTP stream).
  • Page 500 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description Note: ■ Fax adaptations (for options 2 and 3): ✔ Echo Canceller = On ✔ Silence Compression = Off ✔ Echo Canceller Non-Linear Processor Mode = Off ✔...
  • Page 501 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description Note: The corresponding global parameter is CNGDetectorMode. 'Vxx Modem Transport Type' Defines the modem transport type. ■ [-1] = (Not Configured) The settings of the global...
  • Page 502 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'AMD Mode' Enables the device to disconnect an IP-to-Tel call upon detection of an answering machine on the Tel side. amd-mode ■ [0] Don't Disconnect = (Default) Device does not...
  • Page 503 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'AMD Sensitivity Level' Defines the AMD detection sensitivity level of the selected AMD Parameter Suite (using the 'AMD Sensitivity amd-sensitivity-level Parameter Suite' parameter). [IpProfile_AMDSensitivityLevel] ■ For Parameter Suite 0: The valid range is 0 to 7 (default is 0), where 0 is for best detection of an answering machine and 7 for best detection of a live call.

  • Page 504: Configuring Tel Profile

    CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description To play user-defined tones, you need to record your tones and then install them on the device using a loadable Prerecorded Tones (PRT) file, which is created using AudioCodes DConvert utility.
  • Page 505 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Table 19-6: Tel Profile Table Parameter Descriptions Parameter Description General 'Index' Defines an index number for the new table row. [TelProfile_Index] Note: Each row must be configured with a unique index.
  • Page 506 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ If the device initiates a fax session using G.711 (option 2 or 3), a 'gpmd' attribute is added to the SDP in the following format: ✔...
  • Page 507 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ Analog interfaces: If the parameter is enabled, it is possible to configure the FXS/FXO interface to wait for dial tone per destination phone number (before or during dialing of destination phone number).
  • Page 508 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description [TelProfile_CallPriorityMode] ■ [1] MLPP = Enables MLPP Priority Call handling. MLPP prioritizes call handling whereby the relative importance of various kinds of communications is strictly defined, allowing higher precedence communication at the expense of lower precedence communications.
  • Page 509 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Time For Reorder Tone' Defines the duration (in seconds) that the device plays a busy or reorder tone before releasing the line. time-for-reorder-tone Analog interfaces: Typically, after playing the busy or...
  • Page 510 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [1] Cut-Through = (Enabled with tones) Calls can be received in off-hook state. When the IP side ends the call, the device can play a reorder tone to the Tel side for a user-defined duration (configured by the CutThroughTimeForReorderTone parameter).
  • Page 511 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description Note: ■ For more information on AGC, see Automatic Gain Control (AGC). ■ The corresponding global parameter is EnableAGC. Analog 'Enable Polarity Reversal' Enables the Polarity Reversal feature for call release.
  • Page 512 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'DID Wink' Enables Direct Inward Dialing (DID) using Wink-Start signaling, typically used for signaling between an E-911 enable-did-wink switch and the PSAP. [TelProfile_EnableDIDWink] ■ [0] Disable (default) ■...
  • Page 513 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ✔ FXO Interfaces: For IP-to-Tel calls: 1) Upon incoming INVITE message, the FXO interface goes off-hook (seizes the line). 2) Upon detection of a Wink signal from the Tel side (instead of a dial tone), the device dials the digits, "KP911ST"...
  • Page 514 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description [TelProfile_IPDiffServ] The valid range is 0 to 63. The default is 46. Note: ■ For more information on DiffServ, see Configuring Class-of-Service QoS. ■ The corresponding global parameter is Premi- umServiceClassMediaDiffServ.
  • Page 515 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ Digital: You can also configure early SIP 183 response immediately upon the receipt of an INVITE, using the EnableEarly183 parameter. ■ Analog: To send a 183 response, you must also set the ProgressIndicator2IP parameter to 1.
  • Page 516 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [1] Line Echo Canceller (default) ■ [2] Acoustic For more information on echo cancellation, see Configuring Echo Cancellation. Note: The corresponding global parameter is EnableEchoCanceller.
  • Page 517 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ The parameter is applicable only to FXS interfaces. ■ The corresponding global parameter is MWIAnalogLamp. 'MWI Display' Enables sending MWI information to the phone display.
  • Page 518 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ The corresponding global parameter is IsTwoStageDial. 'FXO Double Answer' Enables the FXO Double Answer feature, which rejects (disconnects) incoming (FXO) Tel-to-IP collect calls and fxo-double-answer signals (informs) this call denial to the PSTN.
  • Page 519 CHAPTER 19    Coders and Profiles Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ✔ 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.

  • Page 520: Sip Definitions

    CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual SIP Definitions This section describes configuration of various SIP-related functionality. Configuring Registration Accounts The Accounts table lets you configure up to 102 Accounts. An Account defines information for registering and authenticating (digest) Trunk Groups (e.g., PBX) or IP Groups (e.g., IP PBX) with a "serving"...
  • Page 521 CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual ● For the Gateway application: If no match is found in the Accounts table for incoming or outgoing calls, the username and password is taken from: ✔ For FXS interfaces: Authentication table (see...
  • Page 522 CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual ➢ To register or un-register an Account: In the table, select the required Account entry row. From the Action drop-down list, choose one of the following commands: ● Register to register the Account.
  • Page 523 CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ IP-to-Tel calls: The serving IP Group is the 'Source IP Group ID' configured in the IP-to-Tel Routing table (see Configuring IP-to-Tel Routing Rules). Note: ■ By default, only IP Groups associated with the SRD to which the Served IP Group is associated are displayed, as well as IP Groups of Shared SRDs.
  • Page 524 CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [2] GIN = The device performs registration for legacy PBXs, using Global Identification Number (GIN). For more information, see Single Registration for Multiple Phone Numbers using GIN.
  • Page 525 CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [2] Enable for Non-REGISTER Requests = Enables the Register Stickiness feature, as described for the Enable option (above), except for refresh REGISTER messages. When the device initiates a refresh...
  • Page 526 CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ✔ The transaction timeout expires for an INVITE sent to the Serving IP Group. ✔ The device receives an INVITE from the Serving IP Group from an IP address other than the address to which it is currently registered.
  • Page 527 CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual 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.
  • Page 528 CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [1] Enable = The device assigns a unique local port for each Account for which the device initiates registration. The port is taken from a configured UDP port range.

  • Page 529: Regular Registration Mode

    CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual Regular Registration Mode When you configure the registration mode ('Register') in the Accounts table to Regular, the device sends REGISTER requests to the Serving IP Group. The host name (in the SIP From/To headers) and contact user (user in From/To and Contact headers) are taken from the configured Accounts table upon successful registration.

  • Page 530: Registrar Stickiness

    CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual The figure below illustrates an incoming call using GIN: 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.

  • Page 531: Sip Message Authentication Example

    CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual ■ Click Un-Register button to un-register. Instead of registering the entire device, you can register specific entities as listed below by using the Register button located on the page in which these entities are configured: ■...
  • Page 532 ● 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 533: Configuring User Information

    CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual Contact: <sip:122@10.1.1.200>; expires="Thu, 26 Jul 2012 10:34:42 GMT"; action=proxy; q=1.00 Contact: <122@10.1.1.200:>; expires="Tue, 19 Jan 2038 03:14:07 GMT"; action=proxy; q=0.00 Expires: Thu, 26 Jul 2012 10:34:42 GMT Configuring User Information This section describes User Information configuration.

  • Page 534: Configuring Gateway User Information Table Through Web Interface

    CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual If you have configured regular IP- to- Tel manipulation rules (see Configuring Source/Destination Number Manipulation ), the device applies these rules before applying the mapping rules of the User Information table.
  • Page 535 CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual ■ Export the configured users to a .csv file: From the Action drop-down list, choose Export and save the file to a folder on your computer. ■ Register and un-register users: ●...

  • Page 536: Configuring Gateway User Information Table Through Cli

    CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Username' Defines the username for registering the user when authentication is necessary. [GWUserInfoTable_Username] The valid value is a string of up to 60 characters. By default, no value is defined.

  • Page 537: Configuring Gateway User Information Table From A Loadable File

    CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual password (0aGzoKfh5uI=) status (not-resgistered) ■ To view a specific entry (example): (sip-def-proxy-and-reg)# user-info gw-user-info <index, e.g., 0> (gw-user-info-0)# display pbx-ext (405) global-phone-num (405) display-name (Ext405) username (user405) password (0aGzoKfh5uI=) status (not-resgistered) ■...

  • Page 538: Configuring Sbc User Information

    CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual You can load the User Information file using any of the following methods: ■ Web interface - User Information table (see Configuring Gateway User Information Table through Web Interface on page 494)

  • Page 539: Configuring Sbc User Information Table Through Web Interface

    CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual ● For the SBC User Information feature, the device's License Key must include the license "Far End Users (FEU)", which specifies the maximum number of supported far-end users. If no far-end users are licensed, then this feature cannot be used.
  • Page 540 CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual Configure a user according to the table below. Click Apply. Table 20-3: User Information Table Parameter Descriptions Parameter Description 'Index' Defines an index number for the new table row.

  • Page 541: Configuring Sbc User Information Table Through Cli

    CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual Configuring SBC User Information Table through CLI The SBC User Information table can be configured in the CLI using the following commands: ■ To add and/or modify a user (example):...

  • Page 542: Configuring Sbc User Information Table From A Loadable File

    CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual ■ To search a user by local-user: (sip-def-proxy-and-reg)# user-info find <local-user, e.g., JohnDoe> JohnDee: Found at index 0 in SBC user info table, not registered To configure the User Information table, make sure that you have enabled the feature as...

  • Page 543: Configuring Call Setup Rules

    CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual For backward compatibility only: When configuring a User Information file to load through the Auxiliary Files page, use the following syntax: [SBC] FORMAT LocalUser,UserName,Password,IPGroupID For example: [SBC] FORMAT LocalUser,UserName,Password,IPGroupID...
  • Page 544 CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual ■ ENUM queries: For SBC calls, you can use Call Setup rules to query an ENUM server and to handle responses from the ENUM server. ENUM translates ordinary telephone numbers (E.164 telephone numbers) into Internet addresses (SIP URIs), using the ENUM's DNS...
  • Page 545 CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual Condition: ldap.found exists Action Type: Exit Action Value: True ■ Correct: ● Single rule: Condition: ldap.found !exists Action Type: Exit Action Value: False ● Set of rules: Condition: ldap.found exists Action Type: Exit Action Value: True Condition: <leave it blank>...
  • Page 546 CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Request Type' Defines the type of query. ■ [0] None (default) request-type [CallSetupRules_ ■ [1] LDAP = The Call Setup rule performs an LDAP query with an QueryType] LDAP server.
  • Page 547 CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Request Key' Defines the key to query. ■ For LDAP, the key string is queried on the LDAP server. request-key [CallSetupRules_ ■ For Dial Plans, the key string is searched for in the specified Dial AttributesToQuery] Plan.
  • Page 548 CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ The device saves the retrieved attributes' values for future use in other rules until the next LDAP query or until the call is connected. Thus, the device does not need to re-query the same attributes.
  • Page 549 CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ header.from contains '1234' (SBC application only) ■ param.call.dst.user (called number) ■ param.call.src.user (calling number) ■ param.call.src.name (calling name) ■ param.call.redirect (redirect number) ■ param.call.src.host (source host) ■...

  • Page 550: Call Setup Rule Examples

    CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ srctags ■ http.response.body ■ application/x-www-form-urlencoded (for HTTP Content-Type header in HTTP requests) ■ true (if the 'Action Type' is set to Exit) ■ false (if the 'Action Type' is set to Exit) Call Setup Rule Examples Below are configuration examples for using Call Setup Rules.
  • Page 551 CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual 'Action Value': ldap.attr. displayName ◆ ● IP-to-IP Routing table: A single routing rule is assigned the Call Setup Rule Set ID. (Index 1) 'Call Setup Rules Set ID': 2 ◆...

  • Page 552: Configuring Dial Plans

    CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual ● IP Groups table: 'Call Setup Rules Set ID': 4 ● IP-to-IP Routing table: Index 1: ◆ 'Destination Tag': dep-sales ◆ 'Destination IP Group': SALES ◆ Index 2: ◆...
  • Page 553 CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual You can assign a Dial Plan to an IP Group or SRD. After Classification and Inbound Manipulation, the device checks if a Dial Plan is associated with the incoming call. It first checks the source IP Group and if no Dial Plan is assigned, it checks the SRD.
  • Page 554 CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual The device employs a "best- match" method instead of a "first- match" method to match the source/destination numbers to prefixes configured in the dial plan. The matching order is done digit- by-digit and from left to right.
  • Page 555 CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual 5321 ■ For incoming calls with prefix number "53124", the rule with tag B is chosen (more specific for digit "1"): Prefix 53([2-4]) 531(4) ■ For incoming calls with prefix number "321444", the rule with tag A is chosen and for incoming calls with prefix number "32144", the rule with tag B is chosen:...
  • Page 556 CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual Dial Plans are configured using two tables with "parent-child" relationship: ■ Dial Plan table ("parent" table): Defines the name of the Dial Plan. You can configure up to 10 Dial Plans.
  • Page 557 CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual Configure a dial plan rule according to the parameters described in the table below. Click New, and then save your settings to flash memory. Table 20-7: Dial Plan Rule Table Parameter Descriptions...

  • Page 558: Importing Dial Plans

    CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [n-m], (n-m), or ([n1-m1,n2-m2,a,b,c,n3-m3]): Represents a mixed notation of single numbers and multiple ranges for prefixes and suffixes. To represent a prefix, the notation is enclosed by square brackets [...]; to represent a suffix, the notation is enclosed by square brackets which are enclosed by parenthesis ([...]).
  • Page 559 CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual ● For creating Dial Plans in a CSV file for import, see Creating Dial Plan Files for Import. ● The CLI lets you import Dial Plans and Dial Plan rules from a file on a remote server, using the import-csv-from command under (config-voip)# sbc dial-plan.

  • Page 560: Creating Dial Plan Files

    CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual Use the Browse button to select the Dial Plan file on your PC, and then click OK. The rules in the imported file replace all existing rules of the specific Dial Plan.

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

    CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual From the 'Action' drop-down menu, choose Export; the following dialog box appears: Select the Save File option, and then click OK; the file is saved to the default folder on your PC for downloading files.

  • Page 562: Using Dial Plan Tags For Routing Destinations

    CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual ● Source and destination tags can be used in the same routing rule. ● The same tag can be used for source and destination tags in the same routing rule.
  • Page 563 CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual 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.
  • Page 564 CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual In the IP Groups table, configure your IP Groups. Make sure that you assign the source IP Group with the Dial Plan that you configured in Step 1 and that you configure each destination IP Group with one of the required Dial Plan tags.

  • Page 565: Dial Plan Backward Compatibility

    CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual ● Please adhere to the following regarding the 'Tag' parameter in the Dial Plan Rule table: ✔ Only one tag name without a value can be configured. In the above example, "Holland"...

  • Page 566: Using Dial Plan Tags For Sbc Outbound Manipulation

    CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual The following procedure describes how to configure IP-to-IP routing using prefix tags. ➢ To configure IP-to-IP routing using prefix tags: Configure a Dial Plan file with prefix tags, and then load the file to the device.

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

    CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual ● 'Source Tags' parameter (IPOutboundManipulation_SrcTags): tag denoting the calling users ● 'Destination Tags' parameter (IPOutboundManipulation_DestTags): tag denoting the called users 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 ).
  • Page 568 CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual Dial Plan Name Dial Plan Rule Comment Name Prefix TEL2IP Local1 21[2-4] NYPSP0 Denotes local area codes with prefixes 212, 213, and 214 Local2 NYPSP0 Denotes local area code with prefix...

  • Page 569: Using Dial Plan Tags For Message Manipulation

    CHAPTER 20    SIP Definitions Mediant 800 Gateway & E-SBC | User's Manual Open the IP-to-Tel Routing table (see Configuring IP-to-Tel Routing Rules on page 614), and then configure a routing rule with the required destination and whose matching characteristics include the tag(s) that you configured in your Dial Plan for IP-to-Tel routing. The tags are assigned using the 'Source Tag' and 'Destination Tag' parameters.

  • Page 570: Sip Message Manipulation

    CHAPTER 21    SIP Message Manipulation Mediant 800 Gateway & E-SBC | User's Manual SIP Message Manipulation This section describes SIP message manipulation. Configuring SIP Message Manipulation The Message Manipulations table lets you configure up to 100 Message Manipulation rules. A Message Manipulation rule defines a manipulation sequence for SIP messages. SIP message manipulation enables the normalization of SIP messaging fields between communicating network segments.
  • Page 571 CHAPTER 21    SIP Message Manipulation Mediant 800 Gateway & E-SBC | User's Manual The device also supports a built-in SIP message normalization feature that can be enabled per Message Manipulation rule. The normalization feature removes unknown SIP message elements before forwarding the message. These elements can include SIP headers, SIP header parameters, and SDP body fields.
  • Page 572 CHAPTER 21    SIP Message Manipulation Mediant 800 Gateway & E-SBC | User's Manual This manipulation example is done by configuring two Message Manipulation rules, where Rule #1 is assigned to the source IP Group and Rule #2 to the destination IP Group.
  • Page 573 CHAPTER 21    SIP Message Manipulation Mediant 800 Gateway & E-SBC | User's Manual ● For a detailed description of the syntax used for configuring Message Manipulation rules, refer to the Syntax for SIP Message Manipulation Reference Guide. ● For the SBC application: Inbound message manipulation is done only after the Classification, inbound and outbound number manipulation, and routing processes.
  • Page 574 CHAPTER 21    SIP Message Manipulation Mediant 800 Gateway & E-SBC | User's Manual ■ Index 3: If the user part of the From header equals "unknown", then it is changed according to the srcIPGroup call’s parameter. ■ Index 4: Removes the Priority header from an incoming INVITE message.
  • Page 575 CHAPTER 21    SIP Message Manipulation Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ Invite = rule applies to all INVITE requests and responses ■ Invite.Request = rule applies to INVITE requests ■ Invite.Response = rule applies to INVITE responses ■...

  • Page 576: Configuring Message Condition Rules

    CHAPTER 21    SIP Message Manipulation Mediant 800 Gateway & E-SBC | User's Manual Parameter Description [MessageManipulations_ ■ string/<message-element>/<call-param> + ActionValue] ■ string/<message-element>/<call-param> For example: ■ 'itsp.com' ■ header.from.url.user ■ param.call.dst.user ■ param.call.dst.host + '.com' ■ param.call.src.user + '<' + header.from.url.user + '@' + header.p-asserted-id.url.host + '>'...

  • Page 577: Configuring Sip Message Policy Rules

    CHAPTER 21    SIP Message Manipulation Mediant 800 Gateway & E-SBC | User's Manual 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: ■...
  • Page 578 CHAPTER 21    SIP Message Manipulation Mediant 800 Gateway & E-SBC | User's Manual ■ Maximum header length ■ Maximum message body length ■ Maximum number of headers ■ Maximum number of bodies ■ Option to send 400 "Bad Request" response if message request is rejected ■...
  • Page 579 CHAPTER 21    SIP Message Manipulation Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Name' Defines a descriptive name, which is used when associating the row in other tables. name The valid value is a string of up to 40 characters.

  • Page 580: Configuring Pre-Parsing Manipulation Rules

    CHAPTER 21    SIP Message Manipulation Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Method List' Defines SIP methods (e.g., INVITE\BYE) to blacklist or whitelist. method-list Multiple methods are separated by a backslash (\). The method [MessagePolicy_ values are case-insensitive.
  • Page 581 CHAPTER 21    SIP Message Manipulation Mediant 800 Gateway & E-SBC | User's Manual For a detailed description of supported regex syntax, refer to the Syntax for SIP Message Manipulation Reference Guide Pre-Parsing Manipulation is configured using two tables with "parent-child" relationship: ■...
  • Page 582 CHAPTER 21    SIP Message Manipulation Mediant 800 Gateway & E-SBC | User's Manual In the Pre-Parsing Manipulation Sets table, select the row, and then click the Pre-Parsing Manipulation Rules link located below the table; the Pre-Parsing Manipulation Rules table appears. Click New; the following dialog box appears: Configure a rule according to the parameters described in the table below.
  • Page 583 CHAPTER 21    SIP Message Manipulation Mediant 800 Gateway & E-SBC | User's Manual Parameter Description For more information on regex, refer to the Syntax for SIP Message Manipulation Reference Guide. - 543 -...

  • Page 584: Gateway Application

    Part V Gateway Application...

  • Page 585: Introduction

    CHAPTER 22    Introduction Mediant 800 Gateway & E-SBC | User's Manual Introduction This section describes configuration of the Gateway application. The Gateway application refers to IP-to-Tel and Tel-to-IP call routing. The term Tel refers to: ■ Analog: ● FXS equipment such as a fax machine or plain old telephone service (POTS) ●...
  • Page 586 CHAPTER 22    Introduction Mediant 800 Gateway & E-SBC | User's Manual ■ Tel-to-IP Call: - 546 -...
  • Page 587 CHAPTER 22    Introduction Mediant 800 Gateway & E-SBC | User's Manual - 547 -...

  • Page 588: Digital Pstn

    CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual Digital PSTN This section describes the configuration of the device's Gateway application for its' digital interfaces (PSTN). Configuring Trunk Settings The Trunk Settings page allows you to configure the device's PSTN trunks. This includes selecting the PSTN protocol and configuring related parameters.
  • Page 589 CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual ● The parameters displayed on the Trunk Settings page depends on the protocol type (configured by the 'Protocol Type' parameter). ● When modifying an existing |(configured) trunk through the Web interface, some parameters require you to first stop the trunk.
  • Page 590 CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual On the top of the page, a bar with Trunk number icons displays the status of each trunk according to the following color codes: ● Grey: Disabled ● Green: Active ●...
  • Page 591 CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual Table 23-1: Trunk Settings Table Parameter Descriptions Parameter Description General 'Module ID' Displays the module number to which the trunk belongs. 'Trunk ID' Displays the selected trunk ID number.
  • Page 592 CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [17] E1 AUSTEL ISDN = ISDN PRI protocol for the Australian Telecom. ■ [18] E1 HKT ISDN = ISDN PRI (E1) protocol for the Hong Kong - HKT.
  • Page 593 CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [0] Recovered = (Default) Generate the clock according to configure voip > the Rx of the E1/T1 line. interface e1-t1 > clock-masterclock- ■ [1] Generated = Generate the clock according to the master internal TDM bus.
  • Page 594 CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Trace Level' Defines the trace level: ■ [0] No Trace (default) configure voip > interface e1-t1|bri > ■ [1] Full ISDN Trace trace-level ■ [2] Layer 3 ISDN Trace [TraceLevel] ■...
  • Page 595 CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [0] User side = (Default) ISDN User Termination configure voip > Equipment (TE) side. interface e1-t1|bri > isdn-termination-side ■ [1] Network side = ISDN Network Termination (NT) side.
  • Page 596 CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [128] SEND USER CONNECT ACK = The Connect ACK message is sent in response to received Q.931 Connect; otherwise, the Connect ACK is not sent. Note: This option is applicable only to Euro ISDN User side outgoing calls.
  • Page 597 CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [1073741824] QSI ENCODE INTEGER = If this bit is set, INTEGER ASN.1 type is used in operator coding (compliant to new ECMA standards); otherwise, OBJECT IDENTIFIER ASN.1 type is used.
  • Page 598 CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [256] STORE CHAN ID IN SETUP = The device forces the sending of a Channel-Id IE in an outgoing Setup message even if it's not required by the standard (i.e., optional) and no Channel-Id has been specified in the establishment request.
  • Page 599 CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [8192] CHAN ID IN CALL PROC = The device sends Channel ID in a Q.931 Call Proceeding message. ■ [65536] PROGR IND IN SETUP ACK = (Default) The...
  • Page 600 CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual Parameter Description [ISDNGeneralCCBehavior] ■ [2] = Data calls with interworking indication use 64 kbps B- channels (physical only). ■ [8] REVERSE CHAN ALLOC ALGO = Channel ID allocation algorithm.
  • Page 601 CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [65536] GTD5 TBCT = CC implements the VERIZON- GTD-5 Switch variant of the TBCT Supplementary Service, as specified in FSD 01-02-40AG Feature Specification Document from Verizon. Otherwise, TBCT is implemented as specified in GR-2865-CORE specification (default behavior).
  • Page 602 CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual Parameter Description The valid range is 0 to 100. The default interface ID equals the configure voip > trunk's ID. interface e1-t1 > isdn-nfas-interface- Note: ■ If you are modifying the parameter for an existing...
  • Page 603 CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual Parameter Description CASFileName_0 = 'E_M_WinkTable.dat' CASFileName_1 = 'E_M_ImmediateTable.dat' CASTableIndex_0 = 0 CASTableIndex_1 = 0 CASTableIndex_2 = 1 CASTableIndex_3 = 1 Note: You can define CAS tables per B-channel using the parameter CASChannelIndex.
  • Page 604 CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'PSTN Alert Timeout' Defines the Alert Timeout (ISDN T301 timer) in seconds for outgoing calls to PSTN, per trunk. This timer is used between configure voip >...
  • Page 605 CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [1] PI = 1 = The PI value is sent to PSTN in Q.931/Proceeding and Alerting messages. Typically, the PSTN/PBX cuts through the audio channel without playing local ringback tone, enabling the originating party to hear remote Call Progress Tones or network announcements.
  • Page 606 CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ The MaxDigits parameter can be used to limit the length of the collected number for ISDN overlap dialing (if Sending Complete is not received). ■ If a digit map pattern is defined (using the DigitMapping or DialPlanIndex parameters), the device collects digits until a match is found (e.g., for closed numbering schemes) or...
  • Page 607 CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ✔ Graceful out-of-service enabled: The device rejects new incoming calls. If at least one busy channel exists during the graceful period, the device immediately takes all idle channels out-of-service and sends out-of-service Service messages to the other B-channels as soon as they become idle.
  • Page 608 CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ✔ Graceful out-of-service disabled: The device rejects new incoming calls and immediately blocks all channels (idle and busy). The device disconnects busy channels before blocking them. ✔...
  • Page 609 CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ✔ Graceful out-of-service enabled: The device rejects new incoming calls and does the following: - Fully configured trunk (all channels): > If all channels are idle when the graceful period...
  • Page 610 CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ If the ISDN variant does not support the configured out-of- service option of the parameter, the device sets the parameter to Default [0]. ■ The x in the ini file parameter name denotes the trunk number, where 0 is Trunk 1.
  • Page 611 CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Play Ringback Tone to Determines the playing method of the ringback tone to the Trunk' trunk side, per trunk. ■ [-1] Not configured = (Default) The settings of the configure voip >...
  • Page 612 CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ✔ If LocalISDNRBSource is set to 1, the device plays a ringback tone and sends an ISDN Alert with PI = 8 to the ISDN (unless the [ProgressIndicator2ISDN_x] parameter is configured differently).

  • Page 613: Tdm And Timing

    CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Trunk Name' Defines a descriptive name for a trunk. This can be used to help you easily identify the trunk. config-voip > The valid value is a string of up to 40 characters. The following interface <e1|t1|bri>...

  • Page 614: Configuring Internal Clock As Clock Source

    CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual From the 'TDM Bus Clock Source' drop-down list (TDMBusClockSource), select Network to recover the clock from the line interface. In the 'TDM Bus Local Reference' field (TDMBusLocalReference), enter the trunk from which the clock is derived.

  • Page 615: Configuring Cas State Machines

    CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual Configuring CAS State Machines The CAS State Machine table lets you modify various timers and other basic parameters to define the initialization of the CAS state machine without changing the state machine itself (no compilation is required).
  • Page 616 CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual ● 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 617: Configuring Digital Gateway Parameters

    CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'MAX Incoming Address Digits' Defines the limitation for the maximum [CasStateMachineMaxNumOfIncomingAddress address digits that need to be collected. Digits] After reaching this number of digits, the collection of address digits is stopped.

  • Page 618: Tunneling Applications

    CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual Configure the parameters as required. Click Apply. Tunneling Applications This section discusses the device's support for VoIP tunneling applications. 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.
  • Page 619 CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual The device continuously monitors the established connections. If for some reason, one or more calls are released, the device automatically re-establishes these ‘broken’ connections. When a failure in a physical trunk or in the IP network occurs, the device re-establishes the tunneling connections when the network is restored.
  • Page 620 CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual ;Channel selection by Phone number. ChannelSelectMode = 0 ;Profiles can be used do define different coders per B-channels ;such as Transparent ;coder for B-channels (timeslot 16) that carries PRI ;signaling.

  • Page 621: Dsp Pattern Detector

    CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual ProtocolType_2 = 5 ProtocolType_3 = 5 ;Channel selection by Phone number. ChannelSelectMode = 0 [TrunkGroup] FORMAT TrunkGroup_Index = TrunkGroup_TrunkGroupNum, TrunkGroup_ FirstTrunkId, TrunkGroup_LastTrunkId, TrunkGroup_FirstBChannel, TrunkGroup_ LastBChannel, TrunkGroup_FirstPhoneNumber, TrunkGroup_ProfileName, TrunkGroup_Module; TrunkGroup 0 = 0,0,0,1,31,1000,1;...

  • Page 622: Configuring Private Wire Interworking

    CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual ➢ To configure DSP pattern detector: On the DSP Settings page (Setup menu > Signaling & Media tab > Media folder > DSP Settings), do the following: From the 'IPMedia Detectors' drop-down list [EnableDSPIPMDetectors], select Enable.
  • Page 623 CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual SIP-based private wire calls are established as any other INVITE dialog, but with the addition of the following headers: ■ SIP Supported header with the value "pw-info-package" (i.e., Supported: pw-info-package).
  • Page 624 CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual ■ Ring Down (Ring and No Ring states): This event signals a ring or no ring state. An example is when the user lifts the handset or pushes a button on the phone to alert the far-end user, which instantly sends ringing to the far end (even though they are already connected).
  • Page 625 CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual </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" /> </xsd:complexType> <xsd:element name="hookSwitch" type="hookSwitchType"/>...
  • Page 626 CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual ➢ To configure private wire interworking: Enable TDM tunneling for private wire services, by doing one of the following: ● Globally: Open the Digital Gateway Parameters page (Setup menu > Signaling &...

  • Page 627: Qsig Tunneling

    CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual QSIG Tunneling The device supports QSIG tunneling over SIP, according to IETF Internet-Draft draft-elwell-sipping- qsig-tunnel-03 ("Tunnelling of QSIG over SIP") and ECMA-355/ISO/IEC 22535. This is applicable to all ISDN variants. QSIG tunneling can be applied to all calls or to specific calls using IP Profiles.

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

    CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual Configure the ISDNRxOverlap parameter to 0 for tunneling of QSIG overlap-dialed digits (see below for description). The configuration of the ISDNInCallsBehavior and ISDNRxOverlap parameters allows tunneling of QSIG overlap-dialed digits (Tel to IP). In this configuration, the device delays the sending of the QSIG Setup Ack message upon receipt of the QSIG Setup message.

  • Page 629: Nfas Interface Id

    CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual NFAS Interface ID Several ISDN switches require an additional configuration parameter per T1 trunk that is called ‘Interface Identifier’. In NFAS T1 trunks, the Interface Identifier is sent explicitly in Q.931 Setup / Channel Identification IE for all NFAS trunks, except for the B-channels of the Primary trunk (see note below).

  • Page 630: Creating An Nfas-Related Trunk Configuration

    CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual ISDNIBehavior = 512 ;The parameter should be added because of ;ISDNNFASInterfaceID coniguration above NFASGroupNumber_0 = 1 NFASGroupNumber_1 = 1 NFASGroupNumber_2 = 1 NFASGroupNumber_3 = 1 DchConfig_0 = 0 ;Primary T1 trunk DchConfig_1 = 2 ;B-Channel NFAS trunk...

  • Page 631: Isdn Overlap Dialing

    CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual ISDN Overlap Dialing Overlap dialing is a dialing scheme used by several ISDN variants to send and/or receive called number digits one after the other (or several at a time). This is in contrast to en-bloc dialing in which a complete number is sent in one message.

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

    CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual Interworking ISDN Overlap Dialing with SIP According to RFC 3578 With overlap dialing disabled, the device expects to receive the digits all at once (enbloc) or with very little delay between digits and then sends the complete number in a single message. Overlap signaling sends portions of the number in separate messages as it collects the digits from the sender.

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

    CHAPTER 23    Digital PSTN Mediant 800 Gateway & E-SBC | User's Manual For IP-to-Tel overlap dialing, to send ISDN Setup messages without including the Sending Complete IE, you must configure the ISDNOutCallsBehavior parameter to USER SENDING COMPLETE [2]. For more information on the above mentioned parameters, see PSTN Parameters.

  • Page 634: Trunk Groups

    CHAPTER 24    Trunk Groups Mediant 800 Gateway & E-SBC | User's Manual Trunk Groups This section describes Trunk Group configuration. Configuring Trunk Groups The Trunk Group table lets you configure up to 24 Trunk Groups. A Trunk Group is a logical group of physical trunks and channels.
  • Page 635 CHAPTER 24    Trunk Groups Mediant 800 Gateway & E-SBC | User's Manual Table 24-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 636: Configuring The Trunk Group Settings Table

    CHAPTER 24    Trunk Groups Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ This field is ignored if routing of IP-to-Tel calls is done according to the Supplementary Services table, where multiple line extension numbers are configured per port (see Configuring Multi-Line Extensions and Supplementary Services).
  • Page 637 CHAPTER 24    Trunk Groups Mediant 800 Gateway & E-SBC | User's Manual Configure settings for a Trunk Group ID according to the parameters described in the table below. Click Apply. Table 24-2: Trunk Group Settings Table Parameter Descriptions Parameter Description General 'Index' Defines an index number for the new table row.
  • Page 638 CHAPTER 24    Trunk Groups Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [3] Cyclic Descending = The next available channel in descending cyclic order is selected. The next lower channel number in the Trunk Group is always selected. When the device...
  • Page 639 CHAPTER 24    Trunk Groups Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [11] By Dest Number & Ascending = The device allocates a channels to incoming IP-to-Tel calls as follows: The device attempts to route the call to the channel that is associated with the destination (called) number.
  • Page 640 CHAPTER 24    Trunk Groups Mediant 800 Gateway & E-SBC | User's Manual Parameter Description The "SipGroupName" in the Request-URI is configured in the IP Groups table (see Configuring IP Groups). Note: ■ If the parameter is not configured, the registration is performed according to the global registration parameter, ChannelSelectMode.
  • Page 641 CHAPTER 24    Trunk Groups Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Serving IP Group' Assigns an IP Group to where the device sends INVITE messages for calls received from the Trunk Group. The actual destination to serving-ip-group where the INVITE messages are sent is according to the Proxy Set associated with the IP Group.
  • Page 642 CHAPTER 24    Trunk Groups Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ "In Service": Indicates that all channels in the Trunk Group are in service, for example, when the Trunk Group is unlocked or Busy Out state cleared (see the EnableBusyOut parameter for more information).

  • Page 643: Routing

    CHAPTER 25    Routing Mediant 800 Gateway & E-SBC | User's Manual Routing This section describes the configuration of call routing for the Gateway application. Configuring Tel-to-IP Routing Rules The Tel-to-IP Routing table lets you configure up to 180 Tel-to-IP routing rules. Tel-to-IP routing rules are used to route calls from the Tel side to an IP destination.
  • Page 644 CHAPTER 25    Routing Mediant 800 Gateway & E-SBC | User's Manual In addition to normal Tel-to-IP routing, you can configure the following features: ■ Least Cost Routing (LCR): If the LCR feature is enabled, the device searches the routing table for matching routing rules and then selects the one with the lowest call cost. The call cost of the routing rule is done by assigning it a Cost Group.
  • Page 645 CHAPTER 25    Routing Mediant 800 Gateway & E-SBC | User's Manual ■ Alternative Routing (when a proxy isn't used): An alternative IP destination (alternative routing rule) can be configured for specific calls ("main" routing rule). When the "main" route fails (e.g., busy), the device can send the call to the alternative route. You must configure the alternative routing rules in table rows (indices) that are located anywhere below the "main"...
  • Page 646 CHAPTER 25    Routing Mediant 800 Gateway & E-SBC | User's Manual Click New; the following dialog box appears: Configure a routing rule according to the parameters described in the table below. Click Apply. The following table shows configuration examples of Tel-to-IP routing rules:...
  • Page 647 CHAPTER 25    Routing Mediant 800 Gateway & E-SBC | User's Manual Below are descriptions of each rule: ■ Rules 1 and 2(Least Cost Routing): For both rules, the called (destination) phone number prefix is 10, the caller's (source) phone number prefix is 100, and the call is assigned IP Profile "ABC".
  • Page 648 CHAPTER 25    Routing Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ "QoS Low" = Poor Quality of Service (QoS) of the destination. ■ "DNS Error" = No DNS resolution. This status is applicable only when a domain name is used (instead of an IP address).

  • Page 649: Dialing Plan Notation For Routing And Manipulation

    CHAPTER 25    Routing Mediant 800 Gateway & E-SBC | User's Manual Parameter Description You can use special patterns (notations) to denote the number. For example, if you want to match this rule to user parts whose last four digits (i.e., suffix) are 4 followed by any three digits (e.g., 4008), then configure this parameter to "...
  • Page 650 CHAPTER 25    Routing Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ If you select an IP Group, you do not need to configure a destination IP address. However, if both parameters are configured in the table, the INVITE message is sent only to the IP Group.
  • Page 651 CHAPTER 25    Routing Mediant 800 Gateway & E-SBC | User's Manual Parameter Description For LDAP-based routing, enter the string "LDAP" to denote the IP address of the LDAP server. For more information, see Active Directory-based Routing for Microsoft Skype for Business.
  • Page 652 CHAPTER 25    Routing Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Call Setup Rules Set ID' Assigns a Call Setup Rule Set ID to the routing rule. The device performs the Call Setup rules of this Set ID if the call-setup-rules-set- incoming call matches the characteristics of the routing rule.
  • Page 653 CHAPTER 25    Routing Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ Table index entry 1 is defined with Forking Group "1", index entry 2 with Forking Group "2", and index entries 3 and 4 with Forking Group "1": The device first sends the call according to index entries 1, 3, and 4 (all belonging to Forking Group "1"), and if the destination is unavailable...

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

    CHAPTER 25    Routing Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ To implement LCR and its Cost Groups, the Routing Policy must be enabled for LCR (see Configuring a Gateway Routing Policy Rule). If LCR is disabled, the device ignores the parameter.
  • Page 655 CHAPTER 25    Routing Mediant 800 Gateway & E-SBC | User's Manual ■ Routing to an Alternative Trunk Group: If the device sends the IP call to the Tel destination and a subsequent call release reason (cause) code (e.g., 17 for User Busy) is received from the...
  • Page 656 CHAPTER 25    Routing Mediant 800 Gateway & E-SBC | User's Manual Configure a routing rule according to the parameters described in the table below. Click Apply. The following table shows configuration examples of Tel-to-IP routing rules: Table 25-3: Example of IP-to-Tel Routing Rules...

  • Page 657: Source Phone Pattern' Src-Phone-Pattern

    CHAPTER 25    Routing Mediant 800 Gateway & E-SBC | User's Manual Parameter Description To configure SIP Interfaces, see Configuring SIP Interfaces. src-sip- interface-name Note: If the incoming INVITE is received on the specified SIP [PstnPrefix_ Interface and the SIP Interface associated with the specified IP...

  • Page 658: Source Tags

    CHAPTER 25    Routing Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Source Tags' Assigns a Dial Plan tag to denote a group of source URI user names. src-tags The valid value is a string of up to 20 characters. The tag is case [PstnPrefix_SrcTags] insensitive.

  • Page 659: Configuring A Gateway Routing Policy Rule

    CHAPTER 25    Routing Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [0] Trunk Group (default) dst-type [PstnPrefix_ ■ [1] Trunk DestType] 'Trunk Group ID' Defines the Trunk Group ID to where the incoming SIP call is sent. Note: This parameter is applicable only if you configure the trunk-group-id 'Destination Type' parameter (see above) to Trunk Group.
  • Page 660 CHAPTER 25    Routing Mediant 800 Gateway & E-SBC | User's Manual ■ 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...

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

    CHAPTER 25    Routing Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'LCR Feature' Enables the Least Cost Routing (LCR) feature for the Routing Policy. lcr-enable ■ [0] Disable (default) [GWRoutingPolicy_ LCREnable] ■ [1] Enable For more information on LCR, see Least Cost Routing.

  • Page 662: Alternative Routing Based On Ip Connectivity

    CHAPTER 25    Routing Mediant 800 Gateway & E-SBC | User's Manual ● 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 663 CHAPTER 25    Routing Mediant 800 Gateway & E-SBC | User's Manual ● Alternative routing based on IP connectivity is applicable only when a proxy server is not used. ● You can also enable the Busy Out feature, whereby the device can take specified actions if all IP destinations of matching routing rules in the Tel-to-IP Routing table do not respond to connectivity checks.

  • Page 664: Alternative Routing Based On Sip Responses

    CHAPTER 25    Routing Mediant 800 Gateway & E-SBC | User's Manual ➢ To configure alternative Tel-to-IP routing based on IP connectivity: In the Tel-to-IP Routing table (see Configuring Tel-to-IP Routing Rules), add alternative Tel-to- IP routing rules for specific calls. Open the Routing Settings page (Setup menu > Signaling & Media tab > Gateway folder >...
  • Page 665 CHAPTER 25    Routing Mediant 800 Gateway & E-SBC | User's Manual ■ 806 Media Limits Exceeded: The device generates Release Cause Code 806 when the call is terminated due to crossed thresholds of QoE metrics such as MOS, packet delay, and...
  • Page 666 CHAPTER 25    Routing Mediant 800 Gateway & E-SBC | User's Manual ■ Proxy Sets: Proxy Sets are used for Server-type IP Groups (e.g., an IP PBX or proxy), which define the address (IP address or FQDN) of the server (see 'Configuring Proxy Sets' on page 415).

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

    CHAPTER 25    Routing Mediant 800 Gateway & E-SBC | User's Manual Enable alternative routing based on SIP responses: Open the Proxy & Registration page (Setup menu > Signaling & Media tab > SIP Definitions folder > Proxy & Registration). From the 'Redundant Routing Mode' drop-down list, select one of the following: ●...

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

    CHAPTER 25    Routing Mediant 800 Gateway & E-SBC | User's Manual The following procedure describes how to configure alternative Tel-to-IP routing to the PSTN. ➢ To configure alternative Tel-to-IP routing to the PSTN: In the Tel-to-IP Routing table (see Configuring Tel-to-IP Routing Rules), configure an alternative routing rule with the same call matching characteristics (e.g., phone number...
  • Page 669 CHAPTER 25    Routing Mediant 800 Gateway & E-SBC | User's Manual ● If a Trunk is disconnected or not synchronized, the device issues itself the internal Cause Code No. 27. This cause code is mapped (by default) to SIP 502. ●...

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

    CHAPTER 25    Routing Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Release Cause' Defines a Q.931 release code that if received, the device attempts to route the call to an alternative destination (if configured). rel-cause [AltRouteCauseIP2Tel_ ReleaseCause] Alternative Routing to an IP Destination upon a Busy Trunk The Forward on Busy Trunk Destination table lets you configure alternative routing rules for forwarding (i.e., call redirection) IP-to-Tel calls to an alternative IP destination using SIP 3xx...

  • Page 671: Alternative Routing Upon Isdn Disconnect

    CHAPTER 25    Routing Mediant 800 Gateway & E-SBC | User's Manual The figure above displays a configuration that forwards IP-to-Tel calls destined for 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.

  • Page 672: Alternative Routing From Fxo To Ip

    CHAPTER 25    Routing Mediant 800 Gateway & E-SBC | User's Manual ➢ To configure alternative routing upon receipt of ISDN Disconnect: Open the Digital Gateway Parameters page (Setup menu > Signaling & Media tab > Gateway folder > Digital Gateway > Digital Gateway Settings).

  • Page 673: Manipulation

    CHAPTER 26    Manipulation Mediant 800 Gateway & E-SBC | User's Manual Manipulation This section describes configuration of various manipulation processes for the Gateway application. Configuring Redirect Reasons You can manipulate call redirect (diversion) reasons between IP (SIP) and Tel (ISDN). The SIP Diversion header contains the information on the redirection of the call, including the reason (e.g.,...
  • Page 674 CHAPTER 26    Manipulation Mediant 800 Gateway & E-SBC | User's Manual ■ Action: Defines the action that is done if the incoming call matches the characteristics of the rule (e.g., removes a user-defined number of digits from the left of the number).

  • Page 675: Destination Phone Pattern

    CHAPTER 26    Manipulation Mediant 800 Gateway & E-SBC | User's Manual ■ Source Phone Number Manipulation for Tel-to-IP Calls table: ini file [SourceNumberMapTel2IP] or CLI (configure voip > gateway manipulation src- number-map-tel2ip) ➢ To configure a number manipulation rule: Open the required Phone Number Manipulation table (Setup menu > Signaling & Media tab >...
  • Page 676 CHAPTER 26    Manipulation Mediant 800 Gateway & E-SBC | User's Manual Table 26-2: Phone Number 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.
  • Page 677 CHAPTER 26    Manipulation Mediant 800 Gateway & E-SBC | User's Manual Parameter Description [_SrcHost] You can use special patterns (notations) to denote the host part. For example, if you want to match this rule to host parts that end (suffix) in ".com", then configure this parameter to "(.com)". For...
  • Page 678 CHAPTER 26    Manipulation Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Stripped Digits From Defines the number of digits to remove from the right of the Right' telephone number prefix. For example, if you enter 3 and the phone number is 5551234, the new phone number is 5551.

  • Page 679: Manipulating Number Prefix

    CHAPTER 26    Manipulation Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ TON can be used in the SIP Remote-Party-ID header by using the EnableRPIHeader and AddTON2RPI parameters. ■ For more information on available NPI/TON values, see Numbering Plans and Type of Number.

  • Page 680: Sip Calling Name Manipulations

    CHAPTER 26    Manipulation Mediant 800 Gateway & E-SBC | User's Manual ■ [n,l] = defines the location in the original destination or source number where the digits y are added: ● n = location (number of digits counted from the left of the number) of a specific string in the original destination or source number.
  • Page 681 CHAPTER 26    Manipulation Mediant 800 Gateway & E-SBC | User's Manual P-Asserted-Identity: "worker:john" sip:996666@10.13.83.10 The calling name manipulation tables include the following: ■ Calling Name Manipulation for IP-to-Tel Calls table ■ Calling Name Manipulation for Tel-to-IP Calls table Configuration of calling name manipulation rules includes two areas: ■...

  • Page 682: Source Trunk Group Id' Src-Trunk-Group-Id

    CHAPTER 26    Manipulation Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Name' Defines a descriptive name, which is used when associating the row in other tables. manipulation-name The valid value is a string of up to 40 characters. [_ManipulationName] Note: Each row must be configured with a unique name.
  • Page 683 CHAPTER 26    Manipulation Mediant 800 Gateway & E-SBC | User's Manual Parameter Description Note: The parameter is applicable only to the Calling Name Manipulation for IP-to-Tel Calls table. 'Source Host Pattern' Defines the URI host part of the incoming SIP INVITE message in the From header.

  • Page 684: Configuring Redirect Number Manipulation

    CHAPTER 26    Manipulation Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Prefix to Add' Defines the number or string to add at the front of the calling name. prefix-to-add For example, if you enter ITSP and the calling name is [_Prefix2Add] "company:name", the new name is ITSPcompany:john".
  • Page 685 CHAPTER 26    Manipulation Mediant 800 Gateway & E-SBC | User's Manual ➢ To configure a redirect number manipulation rule: Open the required redirect number manipulation table (Setup menu > Signaling & Media tab > Gateway folder > Manipulation > Redirect Number Tel > IP or Redirect Number IP >...
  • Page 686 CHAPTER 26    Manipulation Mediant 800 Gateway & E-SBC | User's Manual Parameter Description The default value is the asterisk (*) symbol, meaning any redirect number. 'Source Trunk Group ID' Defines the Trunk Group from where the Tel call is received. To denote any Trunk Group, leave this field empty. The value -1 src-trunk-group-id indicates that this field is ignored in the rule.
  • Page 687 CHAPTER 26    Manipulation Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Stripped Digits From Left' Defines the number of digits to remove from the left of the redirect number prefix. remove-from-left For example, if you enter 3 and the redirect number is 5551234, [_RemoveFromLeft] the new number is 1234.

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

    CHAPTER 26    Manipulation Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ✔ Network-PSTN Specific ✔ Subscriber-Level0 Regional ✔ Abbreviated For more information on available NPI/TON values, see Numbering Plans and Type of Number. Note: The parameter is applicable only to digital interfaces.
  • Page 689 CHAPTER 26    Manipulation Mediant 800 Gateway & E-SBC | User's Manual The incoming redirection Facility message includes, among other parameters, the Diverted-to number and Diverting number. The Diverted-to number (i.e., new destination) is mapped to the user part in the Contact header of the SIP 302 response. The Diverting number is mapped to the user part in the Diversion header of the SIP 302 response.

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

    CHAPTER 26    Manipulation Mediant 800 Gateway & E-SBC | User's Manual Mapping NPI/TON to SIP Phone-Context The Phone Contexts table lets you configure up to 20 rules for mapping the Numbering Plan Indication (NPI) and Type of Number (TON) to the SIP 'phone-context' parameter, and vice versa.
  • Page 691 CHAPTER 26    Manipulation Mediant 800 Gateway & E-SBC | User's Manual Table 26-7: Phone Contexts table Parameter Description Parameter Description 'Index' Defines an index number for the new table row. [PhoneContext_ Note: Each row must be configured with a unique index.

  • Page 692: Configuring Release Cause Mapping

    CHAPTER 26    Manipulation Mediant 800 Gateway & E-SBC | User's Manual Configuring Release Cause Mapping When a call is disconnected, the reason for the disconnection (or call failure) is sent by the side (IP or Tel) on which the call disconnection occurred. From the IP side, a SIP response is sent (e.g., 406);...

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

    CHAPTER 26    Manipulation Mediant 800 Gateway & E-SBC | User's Manual Click Apply. Table 26-8: Release Cause Mapping from SIP to ISDN Table Parameter Descriptions Parameter Description 'Index' Defines an index number for the new table row. [CauseMapSip2Isdn_ Note: Each row must be configured with a unique index.
  • Page 694 CHAPTER 26    Manipulation Mediant 800 Gateway & E-SBC | User's Manual ISDN Release Description Description Response Reason Request entity too long Interworking Request URI too long Interworking Unsupported media type Service/option not implemented Unknown Resource Interworking Priority Bad extension Interworking Temporarily unavailable...

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

    CHAPTER 26    Manipulation Mediant 800 Gateway & E-SBC | User's Manual ISDN-to-SIP Release Cause Mapping This section shows ISDN-to-SIP release cause mapping. 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.

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

    CHAPTER 26    Manipulation Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Q.850 Causes' Defines the ISDN Q.850 cause code. For example, you can enter "6" (without apostrophes) to represent Cause Code 6 Channel q850-causes Unacceptable. [CauseMapIsdn2Sip_ IsdnReleaseCause] 'SIP Response' Defines the SIP response code.
  • Page 697 CHAPTER 26    Manipulation Mediant 800 Gateway & E-SBC | User's Manual ISDN Release Description Description Response Reason Number changed w/o diagnostic Gone Redirection Bad Request Exchange Routing Error Bad Request Non-selected user clearing Not found Destination out of order Bad gateway...
  • Page 698 CHAPTER 26    Manipulation Mediant 800 Gateway & E-SBC | User's Manual ISDN Release Description Description Response Reason Precedence Call Blocked Acceptable Here Resource unavailable Service unavailable QoS unavailable 503* Service unavailable Facility not subscribed 503* Service unavailable Outgoing Calls Barred within CUG...
  • Page 699 CHAPTER 26    Manipulation Mediant 800 Gateway & E-SBC | User's Manual ISDN Release Description Description Response Reason Call identity in use 503* Service unavailable No call suspended 503* Service unavailable Call having the requested call identity has been 408* Request cleared...

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

    CHAPTER 26    Manipulation Mediant 800 Gateway & E-SBC | User's Manual ISDN Release Description Description Response Reason Interworking unspecified Server internal error * Messages and responses were created because the ‘ISUP to SIP Mapping’ draft doesn’t specify their cause code mapping.

  • Page 701: Sip Reason Header For Release Cause

    CHAPTER 26    Manipulation Mediant 800 Gateway & E-SBC | User's Manual Configure a mapping rule according to the parameters described in the table below. Click Apply. Table 26-12:Release Cause Mapping ISDN to ISDN Table Parameter Descriptions Parameter Description 'Index' Defines an index number for the new table row.

  • Page 702: Mapping Pstn Release Cause To Sip Response For Analog Interfaces

    CHAPTER 26    Manipulation Mediant 800 Gateway & E-SBC | User's Manual Mapping PSTN Release Cause to SIP Response for Analog Interfaces The device's FXO interface interoperates between the SIP network and the PSTN/PBX. This interoperability includes the mapping of PSTN/PBX Call Progress tones to SIP 4xx or 5xx responses for IP-to-Tel calls.
  • Page 703 CHAPTER 26    Manipulation Mediant 800 Gateway & E-SBC | User's Manual Description E.164 Unknown [0] A public number in E.164 format, but no Public [1] information on what kind of E.164 number. International-Level2 Regional [1] A public number in complete international E.164 format, e.g., 16135551234.

  • Page 704: Configuring Dtmf And Dialing

    CHAPTER 27    Configuring DTMF and Dialing Mediant 800 Gateway & E-SBC | User's Manual Configuring DTMF and Dialing This section describes configuration of dual- tone multi- frequency (DTMF) and dialing for the Gateway application. Dialing Plan Features This section describes various dialing plan features.

  • Page 705: Dial Plan Rules

    CHAPTER 27    Configuring DTMF and Dialing Mediant 800 Gateway & E-SBC | User's Manual 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 706: Configuring Hook Flash

    CHAPTER 27    Configuring DTMF and Dialing Mediant 800 Gateway & E-SBC | User's Manual The destination number can be manipulated when this feature is enabled. Note that if manipulation before routing is required, the * and # characters should not be used, as the device will handle them according to the above keypad protocol.

  • Page 707: Configuring Supplementary Services

    CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual Configuring Supplementary Services This section describes the Gateway application's SIP supplementary services that can enhance your telephone service. ● All call participants must support the specific supplementary service that is used.
  • Page 708 CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual The flowchart above describes the following "double" call-hold scenario for analog interfaces: A calls B and establishes a voice path. A places B on hold; A hears a dial tone and B hears a held tone.

  • Page 709: Configuring Moh From External Audio Source

    CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual For analog interfaces: ● If a party that is placed on hold (e.g., B in the above example) is called by another party (e.g., D), then the on-hold party receives a call waiting tone instead of the held tone.
  • Page 710 CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual ➢ To configure MoH from external audio streamer: Connect the external media player to one of the device's FXS ports through an FXS emulator (analog telephone adapter). Open the Tel Profiles table (see Configuring Tel Profile on page 464), and then configure a Tel...

  • Page 711: Call Pickup

    CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual Open the IP-to-Tel Routing table (see Configuring IP-to-Tel Routing Rules on page 614), and then configure a routing rule to route INVITE messages from the remote IP call entity to which you want to play MoH, to the FXS port.

  • Page 712: Bri Suspend And Resume

    CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual The Call Pick-Up feature is supported only for FXS endpoints pertaining to the same Trunk Group ID. ➢ To configure phone keys for call pickup: Open the Gateway Advanced Settings page (Setup menu > Signaling & Media tab >...

  • Page 713: Consultation Call Transfer

    CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual Consultation Call Transfer The device supports Consultation Call Transfer. For analog interfaces: It supports Consultation Call Transfer using the SIP REFER message and the Replaces header. The common method to perform consultation transfer is described in the following example, which assumes three call parties: ■...

  • Page 714: Consultation Transfer For Qsig Path Replacement

    CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual Consultation Transfer for QSIG Path Replacement The device can interwork consultation call transfer requests for ISDN QSIG-to-IP calls. When the device receives a request for a consultation call transfer from the PBX, the device sends a SIP REFER message with a Replaces header to the SIP UA to transfer it to another SIP UA.

  • Page 715: Call Forward

    CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual This source number can also be used as the value for the 'Source Phone Pattern' field in the Destination Phone Number Manipulation for IP-to-Tel Calls table. The local IP address is used as the value for the 'Source IP Address' field.

  • Page 716: Call Forward Reminder Ring

    CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual ➢ To enable call forwarding: Open the Supplementary Services Settings page (Setup menu > Signaling & Media tab > Gateway folder > DTMF & Supplementary > Supplementary Services Settings).

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

    CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual In the 'AS Subscribe IP Group ID' field (ASSubscribeIPGroupID), enter the IP Group ID of the Application server providing the services. In the 'NRT Subscribe Retry Time' field (NRTSubscribeRetryTime), enter the retry period (in seconds) for dialog subscription to the Application server if a previous request fails.

  • Page 718: Call Forward Reminder Dial Tone (Off-Hook) Upon Spanish Sip Alert-Info

    CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual If the MWI service is active, the MWI dial tone overrides this special Call Forward dial tone. Call Forward Reminder Dial Tone (Off-Hook) upon Spanish SIP Alert-Info The device plays a special dial tone to FXS phones in off-hook state that are activated with the call forwarding service.
  • Page 719 CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual To enable the feature, configure the UseFacilityInRequest ini file parameter to 1. ➢ To configure the digit codes for call forwarding services by BRI phones: Open the Supplementary Services Settings page (Setup menu > Signaling & Media tab >...

  • Page 720: Local Handling Of Bri Call Forwarding

    CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual 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. The feature is applicable only to BRI interfaces.

  • Page 721: Enabling Call Waiting

    CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual Open the Trunk Settings page (see Configuring Trunk Settings), and then make sure that you configure the BRI ports with the following settings: ● 'Protocol Type': BRI EURO ISDN ●...

  • Page 722: Message Waiting Indication

    CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual Configure call waiting indication and call waiting ringback tones in the Call Progress Tones file (see Call Progress Tones File). You can configure up to four call waiting indication tones (see the FirstCallWaitingToneID parameter).

  • Page 723: Caller Id

    CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual ■ ISDN BRI: The device supports MWI for its BRI phones, using the Euro ISDN BRI variant. When this feature is activated and a voice mail message is recorded to the mail box of a BRI extension, the softswitch sends a notification to the device.

  • Page 724: Enabling Caller Id Generation And Detection On Tel Side

    CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual The feature is applicable only to analog interfaces. Enabling Caller ID Generation and Detection on Tel Side The device's Caller ID support depends on the type of analog interface: ■...

  • Page 725: Caller Id On The Ip Side

    CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual Verify that the caller ID standard (and substandard) of the device matches the standard of the PBX (using the parameters CallerIDType, BellcoreCallerIDTypeOneSubStandard, and ETSICallerIDTypeOneSubStandard). Define the number of rings before the device starts the detection of caller ID (using the parameter RingsBeforeCallerID).

  • Page 726: Three-Way Conferencing

    CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual ● The ‘Privacy: none’ header is included ● The P-Asserted-Identity (or P-Preferred-Identity) header shows the caller ID The caller ID (and presentation) can also be displayed in the Calling Remote-Party-ID header.
  • Page 727 CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual ● The conference-initiating INVITE sent by the device uses only the ConferenceID as the Request-URI. The Conferencing server sets the Contact header of the 200 OK response to the actual unique identifier (Conference URI) to be used by the participants. The device includes this Conference URI in the SIP Refer-To header value in the REFER messages sent by the device to the remote parties.
  • Page 728 CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual ● Three-way conferencing is applicable only to FXS and BRI interfaces. ● 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 729: Emergency E911 Phone Number Services

    CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual ● In the 'Establish Conference Code' field (ConferenceCode), enter the DTMF digit pattern (e.g., hook flash) that upon detection generates the conference call. ● From the 'Flash Keys Sequence Style' drop-down list (FlashKeysSequenceStyle), select Sequence 1 or Sequence 2 to use the flash + 3 key-combination to create the three way conference call.
  • Page 730 CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual The switch detects the wink and then sends the MF Spill digits with ANI and (optional) Pseudo- ANI (P ANI). The FXS device collects the MF digits, and then sends a SIP INVITE message to the PSAP with all collected MF digits in the SIP From header as one string.

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

    CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual The ANI and the pseudo-ANI numbers are sent to the PSAP either in the From and/or P-AssertedID SIP header. Typically, the MF spills are sent from the E911 tandem switch to the PSAP, as shown in the table...
  • Page 732 CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual When an IP phone subscriber dials 911, the device receives the SIP INVITE message and makes a call to the PSAP as follows: The FXO device seizes the line.
  • Page 733 CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual FirstTxDTMFOption = 4 ◆ RFC2833PayloadType = 101 ◆ ■ TimeToSampleAnalogLineVoltage = 100 ■ WaitForDialTime = 1000 (default is 1 sec) ■ SetDefaultLinePolarityState = 0 (you need to verify that the RJ-11 two-wire cable is connected without crossing, Tip to Tip, Ring to Ring.
  • Page 734 CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual ● Manipulation rules can be configured for the calling (ANI) and called number (but not on the "display" string), for example, to strip 00 from the ANI "00INXXYYYY".

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

    CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual 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 Pre-empting Existing Calls for E911 IP-to-Tel Calls If the device receives an emergency call (E911) from the IP network destined to the Tel and there are unavailable channels (e.g., all busy), the device terminates one of the current calls (arbitrary)

  • Page 736: Multilevel Precedence And Preemption

    CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual ● The feature is applicable to the following interfaces: ✔ ✔ ISDN ✔ ● The device also identifies emergency calls if the Priority header of the incoming SIP INVITE message contains the “emergency” value.
  • Page 737 CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual ● For digital interfaces, MLPP is applicable only to PRI and BRI interfaces. ● The device provides MLPP interworking between SIP and ISDN (both directions). ● For Trunk Groups configured with call preemption, all must be configured to MLPP [1] or all configured to Emergency [2].
  • Page 738 CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual The MLPP Q.931 Setup message contains the Precedence IE. The NI digits are presented by four nibbles found in octets 5 and 6. The device checks the NI digits according to the translation table of...

  • Page 739: Mlpp Preemption Events In Sip Reason Header

    CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual MLPP Preemption Events in SIP Reason Header The device sends the SIP Reason header (as defined in RFC 4411) to indicate the reason and type of a preemption event. The device sends a SIP BYE or CANCEL request, or SIP 480, 486, 488...

  • Page 740: Precedence Ring Tone

    CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual Precedence Ring Tone For analog interfaces: 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. This is configured by the PrecedenceRingingType parameter.
  • Page 741 CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual ■ Routing IP-to-Tel calls (including voice and fax) to specific endpoints based on called line extension number (local number). To enable this functionality, in the Trunk Group Settings...
  • Page 742 CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual Configure a supplementary service according to the parameters described in the table below. Click Apply. The figure below displays an example of multiple-line extensions configured in the Supplementary...
  • Page 743 CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Local Phone Number' Defines a local telephone extension number for the endpoint (e.g., the PBX extension number). The local number is used for local-phone-number the following functionality: [ISDNSuppServ_ ■...

  • Page 744: Detecting Collect Calls

    CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Description [ISDNSuppServ_ ■ The parameter is applicable only to BRI interfaces. CFU2PhoneNumber] ■ To enable BRI call forwarding services, see the BRICallForwardHandling parameter. ■ For more information on configuring local handling of BRI call...

  • Page 745: Advice Of Charge Services For Euro Isdn

    ISDN messages with SIP by converting the AOC messages into SIP INFO (during call) and BYE messages (end of call) using the AudioCodes proprietary SIP AOC header, and vice versa. The device supports both currency (monetary units) and pulse (non- monetary units) AOC messages.
  • Page 746 CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual INFO sip:103@10.10.12.188:5060 SIP/2.0 Via: SIP/2.0/UDP 10.10.12.159:5061;branch=z9hG4bK-1-18439@10.10.12.159;rport From: "2110017: Bob" <sip:4988@10.10.12.188>;tag=1 To: <sip:103@10.10.12.188;user=phone>;tag=pmvsivy1ju Call-ID: 1-18439@10.10.12.159 CSeq: 3 INFO Max-Forwards: 70 Contact: <sip:4988@10.10.12.159:5061;line=qhpks806>;reg-id=1 Content-Type: application/vnd.etsi.aoc+xml Content-Length: 405 <?xml version="1.0" encoding="UTF-8"?>...

  • Page 747: Configuring Charge Codes

    CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual For more information on the proprietary methods, see the PayPhoneMeteringMode parameter in Metering Tone Parameters. ➢ To configure AOC: Make sure that the PSTN protocol for the trunk line is configured to Euro ISDN and network side.
  • Page 748 CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual ● The Charge Codes table is applicable only to the following interfaces: ✔ ✔ Euro ISDN PRI ✔ Euro ISDN BRI ● Analog interfaces: To enable generation of metering tones, see...
  • Page 749 CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Description The valid value is a time in 24-hour format (hh). For example, to denote end-time-<1-4> 4 AM, configure the parameter to "04". [ChargeCode_ EndTime<1-4>] Note: ■...

  • Page 750: Configuring Voice Mail

    CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ Digital interfaces: If you configure the 'Multiplier of Amount' parameter (see below), then the actual charge is the value of the 'Amount On Answer' parameter multiplied by the 'Multiplier of Amount' parameter value.
  • Page 751 CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual Under the General group, configure the following: ● 'Line Transfer Mode' (LineTransferMode): Defines the call transfer method used by the device. ● 'Voice Mail Interface' (VoiceMailInterface): Enables the device's Voice Mail feature and defines the communication method between the device and PBX.

  • Page 752: Converting Accented Characters From Ip To Tel

    CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual ● '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 753 CHAPTER 28    Configuring Supplementary Services Mediant 800 Gateway & E-SBC | User's Manual 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.

  • Page 754: Analog Gateway

    CHAPTER 29    Analog Gateway Mediant 800 Gateway & E-SBC | User's Manual Analog Gateway This section describes configuration of analog settings for the Gateway application. Configuring Keypad Features The Keypad Features page lets you configure key sequences that can be pressed on the keypad of the phones that are connected to the device's FXS ports, for the following features: ■...

  • Page 755: Configuring Metering Tones

    CHAPTER 29    Analog Gateway Mediant 800 Gateway & E-SBC | User's Manual 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 756: Configuring Authentication

    CHAPTER 29    Analog Gateway Mediant 800 Gateway & E-SBC | User's Manual Configure the parameters as required. Click Apply. Configuring Authentication The Authentication table lets you configure an authentication username and password per analog port. ● The feature is applicable to the Gateway application only - FXS and FXO interfaces.

  • Page 757: Configuring Automatic Dialing

    CHAPTER 29    Analog Gateway Mediant 800 Gateway & E-SBC | User's Manual Configure authentication per port according to the parameters described in the table below. Click Apply. Table 29-1: Authentication Table Parameter Descriptions Parameter Description General 'Index' (Read-only) Displays the index number of the table row.
  • Page 758 CHAPTER 29    Analog Gateway Mediant 800 Gateway & E-SBC | User's Manual The feature is applicable only to FXS and FXO interfaces. The following procedure describes how to configure automatic dialing upon off-hook through the Web interface. You can also configure it through ini file [TargetOfChannel] or CLI (configure voip >...

  • Page 759: Configuring Caller Display Information

    CHAPTER 29    Analog Gateway Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Auto Dial Status' Enables automatic dialing. ■ [0] Disable = Automatic dialing for the specific port is disabled. auto-dial-status ■ [1] Enable = (Default) Automatic dialing is enabled and the phone...
  • Page 760 CHAPTER 29    Analog Gateway Mediant 800 Gateway & E-SBC | User's Manual ➢ To configure caller ID: Open the Caller Display Information table (Setup menu > Signaling & Media tab > Gateway folder > Analog Gateway > Caller Display Information). Select the row corresponding to the port that you want to configure, and then click Edit; the following dialog box appears: Configure caller ID per port according to the parameters described in the table below.

  • Page 761: Configuring Call Forward

    CHAPTER 29    Analog Gateway Mediant 800 Gateway & E-SBC | User's Manual Parameter Description [CallerDisplayInfo_ ■ [0] Allowed = The caller ID string is sent when a Tel-to-IP call is IsCidRestricted] made. ■ [1] Restricted = The caller ID string is not sent. The Caller ID is...
  • Page 762 CHAPTER 29    Analog Gateway Mediant 800 Gateway & E-SBC | User's Manual Configure call forwarding per port according to the parameters described in the table below. Click Apply. Table 29-4: Call Forward Table Parameter Descriptions Parameter Description General 'Index' (Read-only) Displays the index number of the table row.

  • Page 763: Configuring Caller Id Permissions

    CHAPTER 29    Analog Gateway Mediant 800 Gateway & E-SBC | User's Manual Parameter Description Note: If the parameter is configured with only a telephone number and a destination 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).

  • Page 764: Configuring Call Waiting

    CHAPTER 29    Analog Gateway Mediant 800 Gateway & E-SBC | User's Manual Table 29-5: Caller ID Permissions Table Parameter Descriptions Parameter Description General 'Index' Defines an index number for the new table row. [EnableCallerId_Index] Note: Each row must be configured with a unique index.
  • Page 765 CHAPTER 29    Analog Gateway Mediant 800 Gateway & E-SBC | User's Manual ➢ 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; the following dialog box appears: Configure call waiting per port according to the parameters described in the table below.

  • Page 766: Rejecting Anonymous Calls

    CHAPTER 29    Analog Gateway Mediant 800 Gateway & E-SBC | User's Manual Rejecting Anonymous Calls The device can reject anonymous calls received from the IP and destined to an FXS port. To configure the functionality, use the ini file parameter, RejectAnonymousCallPerPort. If configured for a specific port and the port receives an anonymous call, the device rejects the call and responds with a SIP 433 (Anonymity Disallowed) response.
  • Page 767 CHAPTER 29    Analog Gateway Mediant 800 Gateway & E-SBC | User's Manual The figure above shows a configuration example for using distinctive ringing and call waiting tones of Index #9 ('Priority Index' 1) in the CPT file for FXS endpoints 1 through 4 when a call is received from a calling (source) number with prefix 2.

  • Page 768: Analog Coefficient Types

    CHAPTER 29    Analog Gateway Mediant 800 Gateway & E-SBC | User's Manual Parameter Description [ToneIndex_ The call waiting tone index is equal to the value of the 'Priority Index' PriorityIndex] parameter plus the value of the FirstCallWaitingToneID parameter (which defines the index of the first call waiting tone in the CPT file). For...

  • Page 769: Fxo Operating Modes

    CHAPTER 29    Analog Gateway Mediant 800 Gateway & E-SBC | User's Manual From the 'FXS Coefficient Type' drop-down list (FXSCountryCoefficients), select the required FXS Coefficient type. From the 'FXO Coefficient Type' drop-down list (CountryCoefficients), select the required FXO Coefficient type. Click Apply, and then reset the device with a save-to-flash for your settings to take effect.

  • Page 770: Two-Stage Dialing

    CHAPTER 29    Analog Gateway Mediant 800 Gateway & E-SBC | User's Manual ■ Waiting for Dial Tone: Enables the device to dial the digits to the Tel side only after detecting a dial tone from the PBX line. The ini file parameter IsWaitForDialTone is used to configure this operation.

  • Page 771: Did Wink

    CHAPTER 29    Analog Gateway Mediant 800 Gateway & E-SBC | User's Manual DID Wink The device's FXO ports support Direct Inward Dialing (DID). DID is a service offered by telephone companies that enables callers to dial directly to an extension on a PBX without the assistance of an operator or automated call attendant.

  • Page 772: Collecting Digits Mode

    CHAPTER 29    Analog Gateway Mediant 800 Gateway & E-SBC | User's Manual To configure Automatic dialing, see Configuring Automatic Dialing). Collecting Digits Mode When automatic dialing is not configured, the device collects the digits. The SIP call flow diagram below illustrates the Collecting Digits Mode.

  • Page 773: Call Termination On Fxo Devices

    CHAPTER 29    Analog Gateway Mediant 800 Gateway & E-SBC | User's Manual ■ Hold / Transfer toward the Tel side: The ini file parameter LineTransferMode must be set to 0 (default). If the FXO receives a hook-flash from the IP side (using out-of-band or RFC 2833), the device sends the hook-flash to the Tel side by performing one of the following: ●...

  • Page 774: Call Termination Before Call Establishment

    CHAPTER 29    Analog Gateway Mediant 800 Gateway & E-SBC | User's Manual This method operates correctly only if silence suppression is not used. ■ Protocol-based termination of the call from the IP side Note: The implemented disconnect method must be supported by the CO or PBX.

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

    CHAPTER 29    Analog Gateway Mediant 800 Gateway & E-SBC | User's Manual This section provides an example on how to implement a remote telephone extension through the IP network, using FXO and FXS interfaces. In this configuration, the FXO device routes calls received from the PBX to the ‘Remote PBX Extension’...

  • Page 776: Message Waiting Indication For Remote Extensions

    CHAPTER 29    Analog Gateway Mediant 800 Gateway & E-SBC | User's Manual ➢ To dial from a telephone directly connected to the PBX or from the PSTN: ■ Dial the PBX subscriber number (e.g., phone number 101) in the same way as if the user’s phone was connected directly to the PBX.

  • Page 777: Fxs Gateway Configuration

    CHAPTER 29    Analog Gateway Mediant 800 Gateway & E-SBC | User's Manual 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 778 CHAPTER 29    Analog Gateway Mediant 800 Gateway & E-SBC | User's Manual In the Tel-to-IP Routing table, enter 10 in the ‘Destination Phone Prefix’ field, and the IP address of the FXS device (10.1.10.3) in the field ‘IP Address’. In the FXO Settings page (see Configuring FXO Parameters), set the parameter ‘Dialing Mode’...

  • Page 779: Session Border Controller Application

    Part VI Session Border Controller Application...

  • Page 780: Sbc Overview

    CHAPTER 30    SBC Overview Mediant 800 Gateway & E-SBC | User's Manual SBC Overview This section provides an overview of the device's SBC application. ● For guidelines on how to deploy your SBC device, refer to the SBC Design Guide document.

  • Page 781: B2Bua And Stateful Proxy Operating Modes

    CHAPTER 30    SBC Overview Mediant 800 Gateway & E-SBC | User's Manual ● Changes the SIP Contact header and sets it to the device's address. ● Layer-3 topology hiding by modifying source IP address in the SIP IP header. ■ SIP normalization: The device supports SIP normalization, whereby the SBC application can overcome interoperability problems between SIP user agents.
  • Page 782 CHAPTER 30    SBC Overview Mediant 800 Gateway & E-SBC | User's Manual In contrast, when the device operates in Stateful Proxy mode, the device by default forwards SIP messages transparently (unchanged) between SIP endpoints (from inbound to outbound legs). The device retains the SIP dialog identifiers and topology headers received in the incoming message and sends them as is in the outgoing message.

  • Page 783: Call Processing Of Sip Dialog Requests

    CHAPTER 30    SBC Overview Mediant 800 Gateway & E-SBC | User's Manual If the operation mode is configured in both tables, the operation mode of the IP Group is applied. Once configured, the device uses default settings in the IP Profiles table for handling the SIP headers, as mentioned previously.
  • Page 784 CHAPTER 30    SBC Overview Mediant 800 Gateway & E-SBC | User's Manual The first stage of the SIP dialog-initiating process is determining source and destination URLs. The SIP protocol has more than one URL in a dialog-initiating request that may represent the source and destination URLs.

  • Page 785: Configuring Dial Plans

    CHAPTER 30    SBC Overview Mediant 800 Gateway & E-SBC | User's Manual You can specify the SIP header from where you want the device to obtain the source URL in the incoming dialog request. This is configured in the IP Groups table using the...

  • Page 786: User Registration

    CHAPTER 30    SBC Overview Mediant 800 Gateway & E-SBC | User's Manual Applying Call Setup Rules for Various Functions: If configured, the device can run Call Setup Rules to apply various functions to the call. The Call Setup Rule is configured in the Call...

  • Page 787: Classification And Routing Of Registered Users

    CHAPTER 30    SBC Overview Mediant 800 Gateway & E-SBC | User's Manual ■ If registration succeeds (replied with 200 OK by the destination server), the device adds a record to its' registration database, which identifies the specific contact of the specific user (AOR).

  • Page 788: General Registration Request Processing

    CHAPTER 30    SBC Overview Mediant 800 Gateway & E-SBC | User's Manual If registrations are destined to the database (using the above rules), the device does not attempt to find a database match, but instead replies with a SIP 200 OK (used for Survivability). Once a match is found, the request is routed either to the contact received in the initial registration or (if the device identifies that the user agent is behind a NAT) to the source IP address of the initial registration.

  • Page 789: Registration Refreshes

    CHAPTER 30    SBC Overview Mediant 800 Gateway & E-SBC | User's Manual Registration Refreshes Registration refreshes are incoming REGISTER requests from users that are registered in the device's registration database. The device sends these refreshes to the serving proxy only if the serving proxy's Expires time is about to expire;...

  • Page 790: Media Handling

    CHAPTER 30    SBC Overview Mediant 800 Gateway & E-SBC | User's Manual # clear voip register db sbc user John@10.33.2.22 # clear voip register db sbc user John ■ To delete all registered users belonging to a specific IP Group: # clear voip register db sbc ip-group <ID or name>...

  • Page 791: Media Anchoring

    CHAPTER 30    SBC Overview Mediant 800 Gateway & E-SBC | User's Manual Media Anchoring By default, the device anchors the media (RTP) traffic. In other words, the media between SIP endpoints traverses the device. You can change this default mode by enabling direct media between SIP endpoints.
  • Page 792 CHAPTER 30    SBC Overview Mediant 800 Gateway & E-SBC | User's Manual ■ Avoids interference in SDP negotiation and header manipulation on RTP/SRTP Direct media is typically implemented for calls between users located in the same LAN or domain, and where NAT traversal is not required and other media handling features such as media transcoding is not required.

  • Page 793: Restricting Audio Coders

    CHAPTER 30    SBC Overview Mediant 800 Gateway & E-SBC | User's Manual IP Groups of the endpoints use the same SIP Interface and the SIP Interface's 'SBC Direct Media' parameter is set to Enable When Single NAT (SIPInterface_SBCDirectMedia = 2), and the endpoints are located behind the same NAT.

  • Page 794: Coder Transcoding

    CHAPTER 30    SBC Overview Mediant 800 Gateway & E-SBC | User's Manual If you assign the SIP entity an Allowed Audio Coders Group for coder restriction and a Coders Group for extension coders (i.e., voice transcoding), 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 795 CHAPTER 30    SBC Overview Mediant 800 Gateway & E-SBC | User's Manual ● 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 796 CHAPTER 30    SBC Overview Mediant 800 Gateway & E-SBC | User's Manual On the inbound leg for the incoming SDP offer: The device allows and keeps the coders in the SDP that also appear in the Allowed Audio Coders Group for coder restriction (i.e., G.711 and G.729).

  • Page 797: Transcoding Mode

    CHAPTER 30    SBC Overview Mediant 800 Gateway & E-SBC | User's Manual Assign the Coders Group to the IP Profile, using the 'Extension Coders Group' parameter (SBCExtensionCodersGroupName). Enable extension coders by configuring the 'Allowed Coders Mode' parameter to Restriction or Restriction and Preference.

  • Page 798: Srtp-Rtp And Srtp-Srtp Transcoding

    CHAPTER 30    SBC Overview Mediant 800 Gateway & E-SBC | User's Manual ■ Outgoing SDP offer: If only Allowed coders are used, the device arranges the coders in the SDP offer as described above. However, if Extension coders are also used, the coder list is arranged according to the SBCPreferencesMode parameter.

  • Page 799: Interworking Miscellaneous Media Handling

    CHAPTER 30    SBC Overview Mediant 800 Gateway & E-SBC | User's Manual The device transparently forwards Binary Floor Control Protocol (BFCP) signaling over UDP between IP entities (RFC 4582). BFCP is a signaling protocol used by some third- party conferencing servers to share content (such as video conferencing, presentations or documents) between conference participants (SIP clients supporting BFCP).

  • Page 800: Interworking Rtcp Attribute In Sdp

    CHAPTER 30    SBC Overview Mediant 800 Gateway & E-SBC | User's Manual Interworking RTCP Attribute in SDP The device supports interworking the RTCP attribute 'a=rtcp' in the SDP between SIP entities. Employing IP Profiles, you can configure RTCP attribute handling (add, remove or transparent) per...

  • Page 801: Limiting Sbc Call Duration

    CHAPTER 30    SBC Overview Mediant 800 Gateway & E-SBC | User's Manual 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 802: Radius-Based User Authentication

    CHAPTER 30    SBC Overview Mediant 800 Gateway & E-SBC | User's Manual The device challenges the received SIP message only if it is configured as a SIP method (e.g., INVITE) for authorization. This is configured in the IP Groups table, using the 'Authentication Method List' parameter.
  • Page 803 CHAPTER 30    SBC Overview Mediant 800 Gateway & E-SBC | User's Manual (This stage does not involve the device.) The client application requires an OAuth Access Token for the user. There are multiple schemes to do this. For example, it may use the Authorization Code method, whereby the client application refers the user to the OAuth Authorization server to request an Authorization Code.
  • Page 804 CHAPTER 30    SBC Overview Mediant 800 Gateway & E-SBC | User's Manual The device authenticates the SIP request, by sending (HTTP POST) an HTTP Introspection request with the user's Access Token to the OAuth Authorization server, as shown in the following example: POST /auth/realms/demo/protocol/openid-connect/token/introspect HTTP/1.1...
  • Page 805 CHAPTER 30    SBC Overview Mediant 800 Gateway & E-SBC | User's Manual Parameter Value Comment 'Name' "OAUth-Server" Any descriptive name. 'Type' General 'Path' "auth/realms/demo/protocol/openid- Relative URL for the connect/token/introspect" introspection service on the server. 'Username' "device234" Username that the device uses...

  • Page 806: Interworking Sip Signaling

    CHAPTER 30    SBC Overview Mediant 800 Gateway & E-SBC | User's Manual Interworking SIP Signaling The device supports interworking of SIP signaling messages to ensure interoperability between communicating SIP UAs or entities. This is critical in network environments where the UAs on opposing SBC legs have different SIP signaling support.

  • Page 807: Local Handling Of Sip 3Xx

    CHAPTER 30    SBC Overview Mediant 800 Gateway & E-SBC | User's Manual The process of this feature is described using an example: The device receives the Redirect server's SIP 3xx response (e.g., Contact: <sip:User- @IPPBX:5060;transport=tcp;param=a>;q=0.5). The device replaces the Contact header value with the special prefix and database key value as user part, and with the device's URL as host part (e.g., Contact: <sip:Prefix_Key_User-...

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

    CHAPTER 30    SBC Overview Mediant 800 Gateway & E-SBC | User's Manual Interworking SIP Diversion and History-Info Headers This device can be configured to interwork between the SIP Diversion and History-Info headers. This is important, for example, to networks that support the Diversion header but not the History- Info header, or vice versa.

  • Page 809: Interworking Sip Refer Messages

    CHAPTER 30    SBC Overview Mediant 800 Gateway & E-SBC | User's Manual SIP Header Present IP Header Present Parameter in incoming SIP Device Action in outgoing SIP Value Message Message 'Diversion Present Diversion added from Present Present Header Mode' present History-Info...

  • Page 810: Interworking Sip Prack Messages

    CHAPTER 30    SBC Overview Mediant 800 Gateway & E-SBC | User's Manual The handling of REFER can be configured for all calls, using the global parameter [SBCReferBehavior]. To configure different REFER handling options for different UAs (i.e., IP Groups), use the IP Profiles table parameter, 'Remote REFER Mode'.
  • Page 811 CHAPTER 30    SBC Overview Mediant 800 Gateway & E-SBC | User's Manual ■ In a SIP dialog life time, media characteristics after originally determined by the first offer- answer transaction can be changed by using subsequent offer-answer transactions. These transactions may be carried either in UPDATE or re-INVITE transactions. The media handling is similar to the original offer-answer handling.
  • Page 812 CHAPTER 30    SBC Overview Mediant 800 Gateway & E-SBC | User's Manual Figure 30-2: SBC Early Media RTP 18x without SDP Figure 30-3: SBC Early Media RTP 18x with SDP - 772 -...

  • Page 813: Interworking Sip Re-Invite Messages

    CHAPTER 30    SBC Overview Mediant 800 Gateway & E-SBC | User's Manual 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 814: Interworking Call Hold

    CHAPTER 30    SBC Overview Mediant 800 Gateway & E-SBC | User's Manual Interworking Call Hold The device supports the interworking of call hold / retrieve requests between SIP entities supporting different call hold capabilities: ■ Interworking SDP call hold formats. This is configured by the IP Profile parameter, 'SBC Remote Hold Format'.

  • Page 815: Utilizing Gateway Channel Resources For Sbc

    CHAPTER 31    Utilizing Gateway Channel Resources for SBC Mediant 800 Gateway & E-SBC | User's Manual Utilizing Gateway Channel Resources for The device can utilize resources of non-configured Gateway channels (analog and digital) for SBC sessions, regardless of whether the device is licensed for SBC functionality. This feature, in essence, allows "call"...

  • Page 816: Configuring General Sbc Settings

    CHAPTER 32    Configuring General SBC Settings Mediant 800 Gateway & E-SBC | User's Manual Configuring General SBC Settings This section describes configuration of various SBC features. Interworking Dialog Information in SIP NOTIFY Messages You can enable the device to interwork dialog information (XML body) received in SIP NOTIFY messages from a remote (WAN) application server.
  • Page 817 CHAPTER 32    Configuring General SBC Settings Mediant 800 Gateway & E-SBC | User's Manual <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>...

  • Page 818: Configuring Call Admission Control

    CHAPTER 33    Configuring Call Admission Control Mediant 800 Gateway & E-SBC | User's Manual Configuring Call Admission Control You can implement Call Admission Control (CAC) to regulate the volume of voice traffic handled by the device. CAC configuration is done using two tables with parent-child type relationship: ■...
  • Page 819 CHAPTER 33    Configuring Call Admission Control Mediant 800 Gateway & E-SBC | User's Manual Your CAC rule can also define a guaranteed number of concurrent calls (reserved capacity) for the assigned SIP entity (see above) . Reserved capacity is especially useful when the device operates with multiple entities.
  • Page 820 CHAPTER 33    Configuring Call Admission Control Mediant 800 Gateway & E-SBC | User's Manual In the Call Admission Control Profile table, select the required row, and then click the Call Admission Control Rule link located below the table; the Call Admission Control Rule table appears.
  • Page 821 CHAPTER 33    Configuring Call Admission Control Mediant 800 Gateway & E-SBC | User's Manual Parameter Description [SBCAdmissionRule_ You can also use the following special values: LimitPerUser] ■ [-1] -1 = (Default) Unlimited. ■ [0] 0 = Block all the SIP dialog types specified in the 'Request Type' parameter (above).
  • Page 822 CHAPTER 33    Configuring Call Admission Control Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Maximum Burst Per User' Defines the maximum number of tokens (SIP dialogs) per user that the bucket can hold (see the 'Maximum Burst' max-burst-per-user parameter for a detailed description).

  • Page 823: Routing Sbc

    CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual Routing SBC This section describes configuration of call routing for the SBC application. Configuring Classification Rules The Classification table lets you configure up to 102 Classification rules. A Classification rule classifies incoming SIP dialog-initiating requests (e.g., INVITE messages) to a "source"...
  • Page 824 CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual From the 'Unclassified Calls' drop-down list, select Reject to reject unclassified calls or Allow to accept unclassified calls: 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 dialog request...

  • Page 825: An Ip Address)

    CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual If classification based on Proxy Set fails (or classification based on Proxy Set is disabled), the device proceeds to classification based on the Classification table. ● For security, it is recommended to classify SIP dialogs based on Proxy Set only if the IP address of the Server-type IP Group is unknown.
  • Page 826 CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual 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 > sbc classification).
  • Page 827 CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual Click Apply. Table 34-1: Classification Table Parameter Descriptions Parameter Description 'SRD' Assigns an SRD to the rule as a matching characteristic for the incoming SIP dialog. srd-name If only one SRD is configured in the SRDs table, the SRD is [Classification_ assigned to the rule by default.
  • Page 828 CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [-1] Any = (Default) All transport types src-transport-type ■ [0] UDP [Classification_ ■ [1] TCP SrcTransportType] ■ [2] TLS 'Source Port' Defines the source port number as a matching characteristic for the incoming SIP dialog.
  • Page 829 CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual Parameter Description [Classification_ The default is the asterisk (*) symbol, which represents any DestHost] destination host prefix. 'Message Condition' Assigns a Message Condition rule to the Classification rule as a matching characteristic for the incoming SIP dialog.

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

    CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ The IP Group must be associated with the assigned SRD (see the 'SRD' parameter in the table). 'IP Group Tag Name' Defines the source tag of the incoming SIP dialog. The tag is used for classifying the SIP dialog to an IP Group.
  • Page 831 CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual Via: SIP/2.0/UDP 10.33.4.226;branch=z9hG4bKVEBTDAHSUYRTEXEDEGJY From: <sip:100@10.33.4.226>;tag=YSQQKXXREVDPYPTNFMWG To: <sip:8000@10.33.4.226> Call-ID: FKPNOYRNKROIMEGBSSKS@10.33.4.226 CSeq: 1 INVITE Contact: <sip:100@10.33.4.226> Route: <sip:2000@10.10.10.10.10>,<sip:300@10.10.10.30> Supported: em,100rel,timer,replaces P-Called-Party-ID: <sip:1111@10.33.38.1> User-Agent: Sip Message Generator V1.0.0.5 Content-Length: 0 In the Classification table, add the following classification rules:...

  • Page 832: Configuring Classification Based On Tags

    CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual Configuring Classification Based on Tags You can classify incoming SIP dialogs to IP Groups, using tags (source tags) that are obtained from Call Setup Rules associated with the SIP Interfaces on which dialogs are received. Using tags can significantly reduce the number of required Classification rules.

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

    CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual General 'Request Type' Dial Plan 'Request Target' ITSP 'Request Key' Param.Call.Src.User 'Condition ' DialPlan.Found exists Action 'Action Subject' SrcTags 'Action Type' Modify 'Action Value' DialPlan.Result Open the SIP Interfaces table (see Configuring SIP Interfaces on page 348), and then...
  • Page 834 CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual ■ Action: Defines the action that is done if the incoming call matches the characteristics of the rule (i.e., routes the call to the specified destination). The device searches the table from top to bottom for the first rule that matches the characteristics of the incoming call.
  • Page 835 CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual ■ Back to the sender of the incoming message, where the reply can be a SIP response code or a 3xx redirection response (with an optional Contact field to where the sender must re-send the message).
  • Page 836 CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual ● The DNS resolution includes IP addresses that the device has yet to try (for the current call). Messages are re-routed with the same SIP Call-ID and CSeq header fields (increased by 1).
  • Page 837 CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual The LCR feature can also be employed with call forking. The device calculates a maximum call cost for each Forking group and routes the call to the Forking group with the lowest cost. Thus, even if the call can successfully be routed to the main routing rule, a different routing rule can be chosen (even an alternative route, if configured) based on LCR.
  • Page 838 CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual Table 34-2: IP-to-IP Routing Table Parameter Descriptions Parameter Description 'Routing Policy' Assigns a Routing Policy to the rule. The Routing Policy associates the rule with an SRD(s). The Routing Policy also defines default...
  • Page 839 CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ The Forking Group members must be configured in a table row that is immediately below the main Forking routing rule, or below an alternative routing rule for the main rule, if configured.
  • Page 840 CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Source Username Defines the user part of the incoming SIP dialog's source URI Pattern' (usually the From URI). You can use special patterns (notations) to denote the user part. For...
  • Page 841 CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual Parameter Description Note: If you need to route calls of many different destination URI user names to the same destination, you can use tags (see 'Source Tags' parameter below) instead of this parameter.
  • Page 842 CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [5] Broken Connection = If the device detects a broken RTP connection during the call and the Broken RTP Connection feature is enabled (IpProfile_DisconnectOnBrokenConnection parameter is configured to [2]), you can use this option as an explicit matching characteristics to route the call to an alternative destination.
  • Page 843 CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [4] Hunt Group = Used for call center survivability. For more information, see Configuring Call Survivability for Call Centers. ■ [5] Dial Plan = (For Backward Compatibility Only - see Note below) The IP destination is determined by a Dial Plan index of the loaded Dial Plan file.
  • Page 844 CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ [10] All Users = Device checks whether the Request-URI (i.e., destination user) in the incoming INVITE is registered in its' users’ database, and if yes, it sends the INVITE to the address of the corresponding contact specified in the database.
  • Page 845 CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ The parameter is applicable only if the 'Destination Type' parameter is configured to IP Group. However, you also need to specify this parameter if the 'Destination Type' parameter is...
  • Page 846 CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ The parameter is applicable only if the 'Destination Type' parameter is configured to Dest Address [1] or ENUM [3]; otherwise, the parameter is ignored. ■ When using domain names, enter the DNS server's IP address...
  • Page 847 CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual Parameter Description ■ To implement LCR and its Cost Groups, you must enable LCR for the Routing Policy assigned to the routing rule (see Configuring SBC Routing Policy Rules). If LCR is disabled, the device ignores the parameter.

  • Page 848: Configuring Rerouting Of Calls To Fax Destinations

    CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual Parameter Description redirect(contact='…',response='<code>') redirect(contact='sip:user@host') Examples: ✔ The device responds to the dialog with a SIP 300 redirect response that includes a contact value: redirect(response=’300’,contact=’sip:102@host’) ✔ The device redirects the call from the sender to a SIP...
  • Page 849 CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual From the 'CNG Detector Mode' drop-down list [CNGDetectorMode], select Event Only. Load an ini file to the device through the Auxiliary Files page (see Loading Auxiliary Files through Web Interface on page 917) with the following parameter setting, which enables in-...

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

    CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual Call Trigger Fax Rerouting Action Destination Type IP Group Destination IP Group Fax (IP Group #2) Configuring Specific UDP Ports using Tag-based Routing You can configure the device to use a specific local UDP port for each SIP entity (e.g., PBX) communicating with a common proxy server (e.g., ITSP).
  • Page 851 CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual ● SIP Interface for leg interfacing with proxy server (specific local UDP ports are later taken from this port range): General Index Name ITSP Network Interface UDP Port 5060...
  • Page 852 CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual General Index Name PBX-3 Type Server SBC Advanced Call Setup Rules Set ID Tags Type=PBX;Port=6003 ● IP Group for the proxy server ("Type" tag is later used to identify proxy server):...
  • Page 853 CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual General Rule Set ID Condition srctags.Type=='PBX' Action Action Subject message.outgoing.local-port Action Type Modify Action Value param.ipg.src.tags.Port ● If the source tag name "Type" equals "ITSP" (i.e., SIP message from the ITSP), then use the value (port number) of the local port on which the incoming message from the proxy server is received by the device, as the value of the destination tag name "Port".

  • Page 854: Configuring A Routing Response Timeout

    CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual ● Routes calls from the ITSP (identified by the source tag name-value "Type=ITSP") to the IP PBXs (identified by the specific port assigned to the IP PBX by the value of the destination tag name "Port"):...
  • Page 855 CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual The device sends (outgoing) a SIP dialog-initiating message (e.g., INVITE, OPTIONS, and SUBSCRIBE) to one of the online proxy servers (addresses) configured for the Proxy Set that is associated with the destination IP Group of the matched IP-to-IP Routing rule.
  • Page 856 CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual ● This section is applicable only to the SBC application. ● The device issues itself the SIP response code 408 when no response is received from a sent SIP message.

  • Page 857: Configuring Sbc Routing Policy Rules

    CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual Parameter Description [4] 4xx; [5] 5xx; [6] 6xx; [400] Bad Request; [402] 402 Payment Required; [403] Forbidden; [404] Not Found; [405] Method Not Allowed; [406] Not Acceptable; [408] Request Timeout (Default); [409] Conflict;...
  • Page 858 CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual If possible, it is recommended to use only one Routing Policy for all SRDs (tenants), unless deployment requires otherwise (i.e., a dedicated Routing Policy per SRD). Once configured, you need to associate the Routing Policy with an SRD(s) in the SRDs table. To determine the routing and manipulation rules for the SRD, you need to assign the Routing Policy to routing and manipulation rules.
  • Page 859 CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual ● The Classification table is used only if classification by registered user in the device's users registration database or by Proxy Set fails. ● If the device receives incoming calls (e.g., INVITE) from users that have already...
  • Page 860 CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual Parameter Description The valid value is a string of up to 40 characters. By default, no name is defined. If you don't configure a name, the device automatically assigns a name in the following format: "SBCRoutingPolicy_<Index>", for example,...

  • Page 861: Configuring Ip Group Sets

    CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual Parameter Description For example, assume the following Cost Groups: ■ "Weekend A": call connection cost is 1 and charge per minute is 6. Therefore, a call of 1 minute cost 7 units.
  • Page 862 CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual ➢ To configure an IP Group Set: Open the IP Group Set table (Setup menu > Signaling & Media tab > SBC folder > Routing > IP Group Set).
  • Page 863 CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual Parameter Description Note: For the Random Weight optional value, use the 'Weight' parameter in the IP Group Set Member table (below) to configure weight value per IP Group. 'Tags' Assigns a Dial Plan tag that is used to determine whether the incoming SIP dialog is sent to IP Groups belonging to this IP Group Set.
  • Page 864 CHAPTER 34    Routing SBC Mediant 800 Gateway & E-SBC | User's Manual Parameter Description [IPGroupSetMember_ IPGroupName] 'Weight' Defines the weight of the IP Group. The higher the weight, the more chance of the IP Group being selected as the destination weight of the call.

  • Page 865: Sbc Manipulations

    CHAPTER 35    SBC Manipulations Mediant 800 Gateway & E-SBC | User's Manual SBC Manipulations This section describes the configuration of the manipulation rules for the SBC application. For additional manipulation features, see the following: ● Configuring SIP Message Policy Rules ●...
  • Page 866 CHAPTER 35    SBC Manipulations Mediant 800 Gateway & E-SBC | User's Manual Content-Type: application/sdp Content-Length: 155 o=SMG 791285 795617 IN IP4 10.2.2.6 s=Phone-Call c=IN IP4 10.2.2.6 t=0 0 m=audio 6000 RTP/AVP 8 a=rtpmap:8 pcma/8000 a=sendrecv a=ptime:20 ■ Outgoing INVITE to WAN: INVITE sip: 9721000@ITSP;user=phone;x=y;z=a SIP/2.0...

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

    CHAPTER 35    SBC Manipulations Mediant 800 Gateway & E-SBC | User's Manual From: <sip:97000@IP_PBX;user=phone;x=y;z=a>;tag=OWan;paramer1=abe ■ Inbound destination SIP URI user name from "1000" to 9721000": INVITE sip:1000@10.2.2.3;user=phone;x=y;z=a SIP/2.0 To: <sip:1000@10.2.2.3;user=phone> INVITE sip:9721000@ITSP;user=phone;x=y;z=a SIP/2.0 To: <sip:9721000@ITSP;user=phone> ■ Destination IP Group name (SIP URI host name) from "10.2.2.3" to "ITSP": INVITE sip:1000@10.2.2.3;user=phone;x=y;z=a SIP/2.0...
  • Page 868 CHAPTER 35    SBC Manipulations Mediant 800 Gateway & E-SBC | User's Manual Configure stricter classification rules higher up in the table than less strict rules to ensure the desired rule is used to manipulate the incoming dialog. Strict refers to the number of matching characteristics configured for the rule.
  • Page 869 CHAPTER 35    SBC Manipulations Mediant 800 Gateway & E-SBC | User's Manual Table 35-1: Inbound Manipulations Table Parameter Descriptions 'Routing Policy' Assigns an Routing Policy to the rule. The Routing Policy associates the rule with an SRD(s). The Routing Policy also...
  • Page 870 CHAPTER 35    SBC Manipulations Mediant 800 Gateway & E-SBC | User's Manual 'Request Type' Defines the SIP request type to which the manipulation rule is applied. request-type ■ [0] All = (Default) All SIP messages. [IPInboundManipulation_ RequestType] ■ [1] INVITE = All SIP messages except REGISTER and SUBSCRIBE.

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

    CHAPTER 35    SBC Manipulations Mediant 800 Gateway & E-SBC | User's Manual 'Remove From Left' Defines the number of digits to remove from the left of the user name prefix. For example, if you enter 3 and the user name is remove-from-left "john", the new user name is "n".
  • Page 872 CHAPTER 35    SBC Manipulations Mediant 800 Gateway & E-SBC | User's Manual ● Configure stricter classification rules higher up in the table than less strict rules to ensure the desired rule is used to manipulate the outbound dialog. Strict refers to the number of matching characteristics configured for the rule.
  • Page 873 CHAPTER 35    SBC Manipulations Mediant 800 Gateway & E-SBC | User's Manual Parameter Description General 'Index' Defines an index number for the new table row. [IPOutboundManipulation_ Note: Each row must be configured with a unique index. Index] 'Name' Defines a descriptive name, which is used when associating the row in other tables.
  • Page 874 CHAPTER 35    SBC Manipulations Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Source IP Group' Defines the IP Group from where the INVITE is received. The default value is Any (i.e., any IP Group). src-ip-group-name [IPOutboundManipulation_ SrcIPGroupName] 'Destination IP Group' Defines the IP Group to where the INVITE is to be sent.
  • Page 875 CHAPTER 35    SBC Manipulations Mediant 800 Gateway & E-SBC | User's Manual Parameter Description You can use special patterns (notations) to denote the user part. dst-user-name- For example, if you want to match this rule to user parts whose pattern last four digits (i.e., suffix) are 4 followed by any three digits [IPOutboundManipulation_ (e.g., 4008), then configure this parameter to "(4xxx)".
  • Page 876 CHAPTER 35    SBC Manipulations Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'ReRoute IP Group' Defines the IP Group that initiated (sent) the SIP redirect response (e.g., 3xx) or REFER message. The parameter is re-route-ip-group- typically used for re-routing requests (e.g., INVITEs) when...

  • Page 877: Using The Proprietary Sip X-Ac-Action Header

    "id". Using the Proprietary SIP X-AC-Action Header You can use AudioCodes proprietary SIP header, X-AC-Action in Message Manipulation rules to trigger certain actions. These actions can be used to support, for example, interworking of SIP-I and SIP endpoints for the ISUP SPIROU variant (see Enabling Interworking of SIP and SIP-I Endpoints).
  • Page 878 CHAPTER 35    SBC Manipulations Mediant 800 Gateway & E-SBC | User's Manual X-AC-Action: 'disconnect' X-AC-Action: 'disconnect;delay=<time in ms>' ■ To resume a previously suspended call: X-AC-Action: 'abort-disconnect' ■ To automatically reply to a message without forwarding the response to the other side: X-AC-Action: 'reply' ■...
  • Page 879 CHAPTER 35    SBC Manipulations Mediant 800 Gateway & E-SBC | User's Manual For example, to use the X-AC-Action header to switch IP Profiles from "ITSP-Profile-1" to "ITSP- Profile-2" during a call for an IP Group (e.g., IP PBX) if the negotiated media port changes to 7550, perform the following configuration: In the IP Profiles table, configure two IP Profiles ("ITSP-Profile-1"...

  • Page 880: Configuring Malicious Signatures

    CHAPTER 36    Configuring Malicious Signatures Mediant 800 Gateway & E-SBC | User's Manual Configuring Malicious Signatures The Malicious Signature table lets you configure up to 30 Malicious Signature patterns. Malicious Signatures are signature patterns that identify SIP user agents (UA) who perform malicious attacks on SIP servers by SIP scanning.
  • Page 881 CHAPTER 36    Configuring Malicious Signatures Mediant 800 Gateway & E-SBC | User's Manual ➢ 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: Configure a Malicious Signature according to the parameters described in the table below.

  • Page 882: Advanced Sbc Features

    CHAPTER 37    Advanced SBC Features Mediant 800 Gateway & E-SBC | User's Manual Advanced SBC Features This section describes configuration of advanced SBC features. Configuring Call Preemption for SBC Emergency Calls The device supports emergency call preemption for SBC calls by prioritizing emergency calls over regular calls.

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

    CHAPTER 37    Advanced SBC Features Mediant 800 Gateway & E-SBC | User's Manual ➢ To configure SBC emergency call preemption: In the Message Conditions table (see Configuring Message Condition Rules), configure a Message Condition rule to identify incoming emergency calls. See above for examples.

  • Page 884: Configuring Dual Registration For Sip Entity

    CHAPTER 37    Advanced SBC Features Mediant 800 Gateway & E-SBC | User's Manual Enable the E9-1-1 feature, by configuring the 'PSAP Mode' parameter to PSAP Server in the IP Groups table for the IP Group of the PSAP server (see Enabling the E9-1-1 Feature).
  • Page 885 CHAPTER 37    Advanced SBC Features Mediant 800 Gateway & E-SBC | User's Manual The device performs SIP message manipulation (Pre-classification Manipulation) on the REGISTER messages to add a special parameter ("ac-int=<value>") to the Contact header to identify the SIP Interface on which each message is received. For example: ●...
  • Page 886 CHAPTER 37    Advanced SBC Features Mediant 800 Gateway & E-SBC | User's Manual ➢ To configure support for dual registration: On the SIP entity (IP Phone), configure the primary and secondary proxy server addresses as the IP address of the device and where each address has a different SIP port number.

  • Page 887: Handling Registered Aors With Same Contact Uris

    CHAPTER 37    Advanced SBC Features Mediant 800 Gateway & E-SBC | User's Manual Classify By Proxy Set: Enable ◆ ● Index 2: Type: User ◆ Name: IP-Phone-A ◆ ● Index 3: Type: User ◆ Name: IP-Phone-B ◆ In the Classification table, configure rules to classify calls from the IP Phones based on SIP Interface: ●...

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

    CHAPTER 37    Advanced SBC Features Mediant 800 Gateway & E-SBC | User's Manual Call-ID: XDRXGAAWNVBTFHBMQCKE@10.33.2.38 CSeq: 1 REGISTER Contact: <sip:300@10.33.2.40> ■ User 2 Registration: REGISTER sip:300@10.33.4.140;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.33.2.40;branch=YHDWUJRMMOEIJRXVYKHD From: <sip:300@domain2;user=phone>;tag=CVYTCHLIVMPBCGNGRTUA To: <sip:300@domain2;user=phone> Call-ID: INRNGFCHFHETRXAQNAIT@10.33.2.38 CSeq: 1 REGISTER Contact: <sip:300@10.33.2.40>...
  • Page 889 CHAPTER 37    Advanced SBC Features Mediant 800 Gateway & E-SBC | User's Manual 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 890: Configuring Sbc Moh From External Media Source

    Manipulation). For a complete description of the ISUP manipulation syntax, refer to the Syntax for SIP Message Manipulation Reference Guide. In addition, you can use the AudioCodes proprietary SIP header X-AC-Action in Message Manipulation rules to support the various call actions (e.g., SIP-I SUS and RES messages) for the ISUP SPIROU variant.
  • Page 891 CHAPTER 37    Advanced SBC Features Mediant 800 Gateway & E-SBC | User's Manual ➢ To configure an external media source: Open the External Media Source table (Setup menu > Signaling & Media tab > SBC folder > External Media Source). Click New; the following dialog box appears: Configure the external media source according to the parameters described in the table below.
  • Page 892 CHAPTER 37    Advanced SBC Features Mediant 800 Gateway & E-SBC | User's Manual ■ Configuring an IP Profile (namely, the 'Extension Coders Group' parameter) and IP Group (namely, the 'IP Profile' parameter) for the media source ■ Designating the media source IP Group as the external media source (in the External Media Source table, as described above) ■...

  • Page 893: Webrtc

    CHAPTER 37    Advanced SBC Features Mediant 800 Gateway & E-SBC | User's Manual WebRTC The device supports interworking of Web Real-Time Communication (WebRTC) and SIP-based VoIP communication. The device interworks WebRTC calls made from a Web browser (WebRTC client) and the SIP destination. The device provides the media interface to WebRTC.
  • Page 894 CHAPTER 37    Advanced SBC Features Mediant 800 Gateway & E-SBC | User's Manual ■ DTLS-SRTP (RFCs 5763/5764): Media channels must be encrypted (secured) through Datagram Transport Layer Security (DTLS) for SRTP key exchange. For more information, see SRTP using DTLS Protocol.

  • Page 895: Sip Over Websocket

    CHAPTER 37    Advanced SBC Features Mediant 800 Gateway & E-SBC | User's Manual The Web page receives Web page elements and JavaScript code for WebRTC from the Web hosting server. The JavaScript code runs locally on the Web browser. When the client clicks the Call button or call link, the browser runs the JavaScript code which sends the HTTP upgrade request for WebSocket in order to establish a WebSocket session with the device.
  • Page 896 CHAPTER 37    Advanced SBC Features Mediant 800 Gateway & E-SBC | User's Manual Sec-WebSocket-Accept: rLHCkw/SKsO9GAH/ZSFhBATDKrU= Sec-WebSocket-Protocol: SIP Server: SBC At this stage, the HTTP connection breaks down and is replaced by a WebSocket connection over the same underlying TCP/IP connection. By default, the WebSocket connection uses the same ports as HTTP (80) and HTTPS (443).

  • Page 897: Configuring Webrtc

    ● For integrating the device's WebRTC functionality into client Web browsers for making calls from their Web browsers through the device, you can use AudioCodes WebRTC client Software Development Kit (SDK) and Application Program Interface (API). For more information, refer to the WebRTC Web Browser Client SDK API Reference Guide.
  • Page 898 CHAPTER 37    Advanced SBC Features Mediant 800 Gateway & E-SBC | User's Manual Configure the keep-alive interval with the WebSocket client: On the Transport Settings page (Setup menu > Signaling & Media tab > SIP Definitions folder > Transport Settings), and then in the 'WebSocket Keep-Alive Period' field (WebSocketProtocolKeepAlivePeriod), enter the keep-alive interval: Click Apply.

  • Page 899: Call Forking

    CHAPTER 37    Advanced SBC Features Mediant 800 Gateway & E-SBC | User's Manual Click Apply. Configure an IP Group for the WebRTC clients: Open the IP Groups table (see Configuring IP Groups). Do the following: From the 'Type' drop-down list, select User.

  • Page 900: Initiating Sip Call Forking

    CHAPTER 37    Advanced SBC Features Mediant 800 Gateway & E-SBC | User's Manual Initiating SIP Call Forking The SBC device supports call forking of an incoming call to multiple SBC users (destinations). Call forking is supported by the device's capability of registering multiple SIP client user phone contacts (mobile and fixed-line extensions) under the same Address of Record (AOR) in its registration database.

  • Page 901: Configuring Call Forking-Based Ip-To-Ip Routing Rules

    CHAPTER 37    Advanced SBC Features Mediant 800 Gateway & E-SBC | User's Manual The device also supports media synchronization for call forking. If the active UA is the first one to send the final response (e.g., 200 OK), the call is established and all other final responses are acknowledged and a BYE is sent if needed.

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

    CHAPTER 37    Advanced SBC Features Mediant 800 Gateway & E-SBC | User's Manual The device saves the users in its registration database with their phone numbers and extensions, enabling future routing to these destinations during survivability mode when communication with the BroadWorks server is lost. When in survivability mode, the device routes the call to the Contact associated with the dialed phone number or extension number in the registration database.

  • Page 903: Configuring Call Survivability For Call Centers

    CHAPTER 37    Advanced SBC Features Mediant 800 Gateway & E-SBC | User's Manual ● The device enables outgoing calls from all equipment that share the same line simultaneously (usually only one simultaneous call is allowed per a specific shared line). ●...
  • Page 904 CHAPTER 37    Advanced SBC Features Mediant 800 Gateway & E-SBC | User's Manual ➢ To configure call survivability for a call center application: In the IP Groups table (see Configuring IP Groups), add IP Groups for the following entities: ● TDM Gateway (Server-type IP Group). This entity forwards the customer calls through the device to the Application server.

  • Page 905: Enabling Survivability Display On Aastra Ip Phones

    CHAPTER 37    Advanced SBC Features Mediant 800 Gateway & E-SBC | User's Manual The figure below displays a routing rule example, assuming IP Group "1" represents the TDM Gateway and IP Group "3" represents the call center agents: Enabling Survivability Display on Aastra IP Phones...

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

    CHAPTER 37    Advanced SBC Features Mediant 800 Gateway & E-SBC | User's Manual 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 907 CHAPTER 37    Advanced SBC Features Mediant 800 Gateway & E-SBC | User's Manual ■ Managed Opus or Managed G.729: If the SBC detects WAN network impairments during a call using the Opus or G.729 coder between the Enterprise SBC and Access SBC, it can adjust the coder's attributes (e.g., bit rate) for that specific call to ensure high voice quality is...
  • Page 908 CHAPTER 37    Advanced SBC Features Mediant 800 Gateway & E-SBC | User's Manual ■ Smart Transcoding: If the SBC (Enterprise or Access SBC) detects WAN network impairments during a call between the Enterprise SBC and Access SBC, the SBC employs voice transcoding by switching the coder from G.711 to Opus for that specific call only.
  • Page 909 CHAPTER 37    Advanced SBC Features Mediant 800 Gateway & E-SBC | User's Manual ■ IP Profiles table - main IP Profile: ● 'Extension Coders Group': Select the Coders Group with G.711 and Opus ● 'Voice Quality Enhancement': Enable ● 'RTP Redundancy Mode': Enable ●...

  • Page 910: Cloud Resilience Package

    Part VII Cloud Resilience Package...

  • Page 911: Crp Overview

    CHAPTER 38    CRP Overview Mediant 800 Gateway & E-SBC | User's Manual CRP Overview The device's Cloud Resilience Package (CRP) application enhances cloud- based or hosted communications environments by ensuring survivability, high voice quality and security at enterprise branch offices and cloud service customer premises. CRP is designed to be deployed at customer sites and branches of: ■...
  • Page 912 CHAPTER 38    CRP Overview Mediant 800 Gateway & E-SBC | User's Manual One of the main advantages of CRP is that it enables quick-and-easy configuration. This is accomplished by its pre-configured routing entities, whereby only minimal configuration is required. For example, defining IP addresses to get the device up and running and deployed in the network.

  • Page 913: Crp Configuration

    If you installed a License Key with the CRP feature and you later want to stop (disable) working with CRP, you need to purchase (from your AudioCodes sales representative) a new License Key without CRP and install it, and then delete all CRP-related configuration (described in this section) or reset the device to factory default settings.

  • Page 914: Pre-Configured Ip Groups

    CHAPTER 39    CRP Configuration Mediant 800 Gateway & E-SBC | User's Manual ■ Auto Answer to Registrations: This mode is the same as the Normal mode, except that the CRP registers the branch users in its registration database instead of forwarding them to the IP PBX.

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

    CHAPTER 39    CRP Configuration Mediant 800 Gateway & E-SBC | User's Manual Table 39-1: Pre-configured IP Groups in the IP Groups Table Index Name Type Description "CRP Users" User LAN users (e.g., IP phones) at the branch office "CRP Proxy" Server Server (e.g., hosted IP PBX at the Enterprise's...

  • Page 916: Emergency Mode

    CHAPTER 39    CRP Configuration Mediant 800 Gateway & E-SBC | User's Manual Source IP Alternative Request Destination Destination Destination Index Group / Route Type Type IP Group Address Emergency Options #1 [CRP IP Group #3 [CRP Alternative Users] Gateway] Route Ignore...

  • Page 917: Auto Answer To Registrations

    CHAPTER 39    CRP Configuration Mediant 800 Gateway & E-SBC | User's Manual The routing rule at Index 5 appears only if the CRPGatewayFallback parameter is enabled (1). Auto Answer to Registrations The pre- configured IP- to- IP routing rules for the Auto Answer to Registrations CRP call...

  • Page 918: Configuring Pstn Fallback

    CHAPTER 39    CRP Configuration Mediant 800 Gateway & E-SBC | User's Manual ● The destination for the routing rule at Index 2 is the source IP Group (i.e., from where the REGISTER message is received). ● Routing rule at Index 7 appears only if the CRPGatewayFallback parameter is...

  • Page 919: High-Availability System

    Part VIII High-Availability System...

  • Page 920: Ha Overview

    Failure. ● HA is supported only on Mediant 800 Gateway & E-SBC H/W Rev. B and C. The figure below illustrates the Active- Redundant HA devices under normal operation. Communication between the two devices is through a Maintenance interface, having a unique IP address for each device.

  • Page 921: Device Switchover Upon Failure

    CHAPTER 40    HA Overview Mediant 800 Gateway & E-SBC | User's Manual In the active device, all logical interfaces (i.e., Media, Control, OAMP, and Maintenance) are active. In the redundant device, only the Maintenance interface is active, which is used for connectivity to the active device.

  • Page 922: Viewing Ha Status On Monitor Web Page

    CHAPTER 40    HA Overview Mediant 800 Gateway & E-SBC | User's Manual ■ Failure in active device: The redundant device initiates a switchover. The failed device resets and the previously redundant device becomes the active device in stand-alone mode. If at a later stage this newly active device detects that the failed device has been repaired, the system returns to HA mode.
  • Page 923 CHAPTER 40    HA Overview Mediant 800 Gateway & E-SBC | User's Manual The Monitor page also displays the HA operational status of the device to which you are currently logged in. This is displayed in the 'HA Status' field under the Device Information pane: ■...

  • Page 924: Ha Configuration

    CHAPTER 41    HA Configuration Mediant 800 Gateway & E-SBC | User's Manual HA Configuration This section describes HA configuration. Initial HA Configuration By default, HA is disabled on the device. When a device is loaded with valid HA configuration and is the first device to be loaded, it becomes the active device. The second device that is loaded with HA configuration becomes the redundant (standby) device.

  • Page 925: Configuring The Ha Devices

    CHAPTER 41    HA Configuration Mediant 800 Gateway & E-SBC | User's Manual ■ For Geographical HA (both units are located far from each other), 2Rx/1Tx port mode connected to a port aggregation switch is the recommended option: ● When two LAN switches are used, the LAN switches must be in the same subnet (i.e., broadcast domain).

  • Page 926: Step 1: Configure The First Device

    CHAPTER 41    HA Configuration Mediant 800 Gateway & E-SBC | User's Manual ● The HA feature is available only if both devices are installed with a License Key that includes this feature. For installing a License Key, see License Key. ●...

  • Page 927: Step 2: Configure The Second Device

    CHAPTER 41    HA Configuration Mediant 800 Gateway & E-SBC | User's Manual If the connection is through a switch, the packets of both interfaces should generally be untagged. To do this, open the Ethernet Devices table (see Configuring Underlying Ethernet Devices ), and then configure the 'Tagging' parameter to Untagged for the Ethernet Device assigned to the Maintenance interface.

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

    CHAPTER 41    HA Configuration Mediant 800 Gateway & E-SBC | User's Manual During this stage, ensure that the first device is powered off or disconnected from the network. ➢ To configure the second device for HA: Connect to the device in the same way as you did with the first device.

  • Page 929: Quick-And-Easy Initial Ha Configuration

    CHAPTER 41    HA Configuration Mediant 800 Gateway & E-SBC | User's Manual When synchronization completes, the redundant device resets to apply the received configuration and software. When both devices become operational in HA, the HA status is indicated as follows: ●...

  • Page 930: Configuration While Ha Is Operational

    CHAPTER 41    HA Configuration Mediant 800 Gateway & E-SBC | User's Manual HARemotePriority = 4 [ InterfaceTable ] FORMAT InterfaceTable_Index = InterfaceTable_ApplicationTypes, InterfaceTable_ InterfaceMode, InterfaceTable_IPAddress, InterfaceTable_PrefixLength, InterfaceTable_Gateway, InterfaceTable_InterfaceName, InterfaceTable_ PrimaryDNSServerIPAddress, InterfaceTable_SecondaryDNSServerIPAddress, InterfaceTable_UnderlyingDevice; InterfaceTable 0 = 6, 10, 10.33.45.40, 16, 10.33.0.1, "Voice", 0.0.0.0, 0.0.0.0, "vlan 1";...

  • Page 931: Configuring Firewall Allowed Rules

    CHAPTER 41    HA Configuration Mediant 800 Gateway & E-SBC | User's Manual If the HA system is already in HA Preempt mode and you want to change the priority of the device, to ensure that system service is maintained and traffic is not disrupted, it is recommended to set the higher priority to the redundant device and then reset it.

  • Page 932: Configuring Diffserv For Ha Maintenance Traffic

    Maintenance interfaces, you must open (allow) the same port ranges as configured in the table above, on that external firewall. ● If the device needs to communicate with AudioCodes OVOC, you must also add rules to allow incoming traffic from OVOC. For more information, see Configuring Firewall Rules to Allow Incoming OVOC Traffic on page 144.
  • Page 933 CHAPTER 41    HA Configuration Mediant 800 Gateway & E-SBC | User's Manual The HA Network Monitor table lets you configure up to 10 monitored rows, where each row can include up to 5 destinations to monitor, defined by hostname (or FQDN), or IP address. You can then configure the device to perform an HA switchover if a user-defined number of monitored rows whose destinations fail to reply to the device's sent pings (i.e., unreachable destinations) is...
  • Page 934 CHAPTER 41    HA Configuration Mediant 800 Gateway & E-SBC | User's Manual Open the HA Network Monitor table (Setup menu > IP Network tab > Core Entities folder > HA Network Monitor). Click New; the following dialog box appears: Configure an HA network monitor entry according to the parameters described in the table below.
  • Page 935 CHAPTER 41    HA Configuration Mediant 800 Gateway & E-SBC | User's Manual Parameter Description 'Ping Timeout' Defines how often (in milliseconds) the device sends ping requests to the destinations configured for the monitored row. This also provides ping-timeout the device time to wait for a reply (if any) from the destination. For...
  • Page 936 CHAPTER 41    HA Configuration Mediant 800 Gateway & E-SBC | User's Manual In the table, select the required index row (monitored row), and then click the HA Network Monitor Peers Status link located below the table; the HA Network Monitor Peers Status...

  • Page 937: Ha Maintenance

    CHAPTER 42    HA Maintenance Mediant 800 Gateway & E-SBC | User's Manual HA Maintenance This section describes HA maintenance. Maintenance of Redundant Device The only interface that is operational on the redundant device is the Maintenance interface. The following protocols can be used for maintenance purposes for this interface: ■...

  • Page 938: Software Upgrade

    CHAPTER 42    HA Maintenance Mediant 800 Gateway & E-SBC | User's Manual ● Toolbar: Click the Actions button, and then from the drop-down menu, choose Switchover. ● Navigation tree: Setup menu > Administration tab > Maintenance folder > High Availability Maintenance.

  • Page 939: Accessing Files On Redundant Device From Active Through Ssh

    CHAPTER 42    HA Maintenance Mediant 800 Gateway & E-SBC | User's Manual Reset the redundant device. The procedure assumes that no network changes were made to both devices' HA Maintenance interface or Ethernet Devices (VLAN); otherwise, the devices may not be able to communicate with each other.

  • Page 940: Backing Up And Restoring Ha Configuration

    CHAPTER 42    HA Maintenance Mediant 800 Gateway & E-SBC | User's Manual Backing Up and Restoring HA Configuration Once you have your HA system up and running, you can make a backup of your HA configuration, by saving an ini configuration file from the active device. If your HA system fails, for whatever reason, you can simply load this file to the devices to restore HA.

  • Page 941: Maintenance

    Part IX Maintenance...

  • Page 942: Basic Maintenance

    CHAPTER 43    Basic Maintenance Mediant 800 Gateway & E-SBC | User's Manual Basic Maintenance This section describes basic maintenance. Resetting the Device You can reset the device through the device's management tools. Device reset may be required for maintenance purposes. Certain parameters require a device reset for their settings to take effect.

  • Page 943: 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 message that contains an Event header 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 944 CHAPTER 43    Basic Maintenance Mediant 800 Gateway & E-SBC | User's Manual From the 'Graceful Option' drop-down list, select one of the following options: ● Yes: The device locks only after a user-defined duration, configured in the 'Lock Timeout' field (see next step). During this interval, no new traffic is accepted, allowing only existing calls to continue until the timeout expires.

  • Page 945: Saving Configuration

    CHAPTER 43    Basic Maintenance Mediant 800 Gateway & E-SBC | User's Manual ➢ 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". Saving Configuration...

  • Page 946: Channel Maintenance

    CHAPTER 44    Channel Maintenance Mediant 800 Gateway & E-SBC | User's Manual Channel Maintenance This chapter describes channel-related maintenance. Disabling Analog Ports You can disable an analog port (FXS or FXO). When disabled, the port cannot be used and signaling is not transmitted through the port. The port's LED is lit red. By default, all analog ports are enabled.

  • Page 947: Locking And Unlocking Trunk Groups

    CHAPTER 44    Channel Maintenance Mediant 800 Gateway & E-SBC | User's Manual ● If a voice call is currently in progress on the B-channel, it is disconnected when the B-channel is restarted. ● B-channel restart can only be done if the D-channel of the trunk to which it belongs is synchronized (Layer 2).

  • Page 948: Disconnecting Active Calls

    Remotely Disconnecting Calls using SIP NOTIFY The device can be triggered to disconnect all current calls upon the receipt of a SIP NOTIFY message containing an Event header with the value 'soft-sync' (proprietary to AudioCodes ), as shown in the example below: NOTIFY sip:<user>@<dsthost>...

  • Page 949: Configuring Names For Telephony Ports

    CHAPTER 44    Channel Maintenance Mediant 800 Gateway & E-SBC | User's Manual Call-ID: 1234@<srchost> Event: soft-sync ➢ To enable remote call disconnect upon receipt of SIP NOTIFY: Open the SIP Definitions General Settings page (Setup menu > Signaling & Media tab > SIP Definitions folder >...

  • Page 950: Upgrading The Device's Software

    CHAPTER 45    Upgrading the Device's Software Mediant 800 Gateway & E-SBC | User's Manual Upgrading the Device's Software You can use the Web interface's Software Upgrade Wizard to easily upgrade the device's software version (.cmp file). You can also use the wizard to load an ini file and Auxiliary files (e.g., CPT file).
  • Page 951 If you upgraded your firmware (.cmp file) and the "SW version mismatch" message appears in the Syslog or Web interface, your License Key does not support the new .cmp file version. If this occurs, contact AudioCodes support team for assistance. ●...
  • Page 952 CHAPTER 45    Upgrading the Device's Software Mediant 800 Gateway & E-SBC | User's Manual ➢ To upgrade the device using the Software Upgrade wizard: Make sure that you have installed a License Key that is compatible with the software version to...
  • Page 953 CHAPTER 45    Upgrading the Device's Software Mediant 800 Gateway & E-SBC | User's Manual When the file is loaded, a message is displayed to inform you that the file was successfully loaded. If your device is in HA mode, select one of the following upgrade options: ●...
  • Page 954 CHAPTER 45    Upgrading the Device's Software Mediant 800 Gateway & E-SBC | User's Manual 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 955 CHAPTER 45    Upgrading the Device's Software Mediant 800 Gateway & E-SBC | User's Manual Click End Process ; the Web Login screen appears, prompting you to log into the device. Log in with your username and password; a message box appears informing you that the device's software has been upgraded (new .cmp file).

  • Page 956: Loading Auxiliary Files

    CHAPTER 46    Loading Auxiliary Files Mediant 800 Gateway & E-SBC | User's Manual Loading Auxiliary Files You can load Auxiliary files to the device using any of the following methods: ■ Web interface - see Loading Auxiliary Files through Web Interface ■...

  • Page 957: Loading Auxiliary Files Through Web Interface

    CHAPTER 46    Loading Auxiliary Files Mediant 800 Gateway & E-SBC | User's Manual ● 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 current traffic on the device. To...

  • Page 958: Loading Auxiliary Files Through Cli

    CHAPTER 46    Loading Auxiliary Files Mediant 800 Gateway & E-SBC | User's Manual Click the Browse button corresponding to the Auxiliary file type that you want to load, navigate to the folder in which the file is located, and then click Open; the name of the file appears next to the Browse button.

  • Page 959: Deleting Auxiliary Files

    (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 960 CHAPTER 46    Loading Auxiliary Files Mediant 800 Gateway & E-SBC | User's Manual You can create up to 32 different Call Progress Tones, each with frequency and format attributes. The frequency attribute can be single or dual-frequency (in the range of 300 to 1980 Hz) or an Amplitude Modulated (AM).
  • Page 961 CHAPTER 46    Loading Auxiliary Files Mediant 800 Gateway & E-SBC | User's Manual ● High Freq [Hz: Frequency (in Hz) of the higher tone component in case of dual frequency tone, or zero (0) in case of single tone (not relevant to AM tones).

  • Page 962: Distinctive Ringing

    CHAPTER 46    Loading Auxiliary Files Mediant 800 Gateway & E-SBC | User's Manual First Signal On Time [10msec]=300; the dial tone is detected after 3 sec First Signal Off Time [10msec]=0 Second Signal On Time [10msec]=0 Second Signal Off Time [10msec]=0 Distinctive Ringing Distinctive Ringing is applicable only to FXS interfaces.
  • Page 963 CHAPTER 46    Loading Auxiliary Files Mediant 800 Gateway & E-SBC | User's Manual In SIP, the Distinctive Ringing pattern is selected according to the Alert-Info header in the INVITE message. For example: Alert-Info:<Bellcore-dr2> --or-- Alert-Info:<http://…/Bellcore-dr2> "dr2" defines ringing pattern #2. If the Alert-Info header is not present, the default ringing tone #0 is played.

  • Page 964: Prerecorded Tones File

    Once recorded, you need to combine the recorded files into a single and loadable PRT file (.dat), using the latest version of AudioCodes DConvert utility. In DConvert, each recording must be added to the PRT file with the tone type "acUserDefineTone<Index>". When you want to specify the tone (ringback or held tone) to play for a specific IP Profile (IPProfile_LocalRingbackTone and IPProfile_LocalHeldTone parameters), you need to use this index number.

  • Page 965: Cas Files

    The AMD Sensitivity file is created in .xml format and then converted to a binary .dat file that can be installed on the device. 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.

  • Page 966: User Info File

    CHAPTER 46    Loading Auxiliary Files Mediant 800 Gateway & E-SBC | User's Manual User Info File For loading User Info (User Information) files, use the Auxiliary Files page for backward compatibility only. If backward compatibility is not needed, load the file or configure...

  • Page 967: License Key

    The local License Key contains all your ordered feature licenses and capacity license. However, the SBC capacity licenses (signaling sessions, media sessions, transcoding sessions, and registered users) can also be provided remotely from AudioCodes OVOC management tool, using the following SBC capacity licensing methods: ■...

  • Page 968: Obtaining License Key For Initial Activation

    AudioCodes (for example, for support and software upgrades). The Product Key is provided in the Order Confirmation e-mail sent to you by AudioCodes upon your purchase, as shown in the example below: - 928 -...

  • Page 969: Local License Key

    Email: Provide one or more e-mail addresses to where you want the License Key ◆ sent. Click Send; after AudioCodes processes your license activation, you will receive an e- mail notification with the License Key file attached. Open the License Key file with any text-based program (such as Notepad) and make sure that the serial number ("S/N") in the License Key is correct and reflects the Serial Number of your...

  • Page 970: Installing A License Key String

    CHAPTER 47    License Key Mediant 800 Gateway & E-SBC | User's Manual Icon Color Description Indicates features from the previous License Key that were not included in the new License Key and are no longer available. After you install the License Key (device reset with a save-to-flash), the icons no longer appear and the License Key page displays only features and capacity of the new License Key.

  • Page 971: Installing A License Key File

    CHAPTER 47    License Key Mediant 800 Gateway & E-SBC | User's Manual Click Apply; the dialog box closes and the "String Uploaded!" message is briefly displayed at the bottom of the page when the License Key successfully loads to the device. The License...
  • Page 972 CHAPTER 47    License Key Mediant 800 Gateway & E-SBC | User's Manual The License Key installation process includes a device reset and is therefore, traffic- affecting. To minimize the disruption of current calls, it is recommended to perform this procedure during periods of low traffic.
  • Page 973 CHAPTER 47    License Key Mediant 800 Gateway & E-SBC | User's Manual Clock Close to close the message box; you are logged out of the Web interface and prompted to log in again. The features and capabilities displayed on the License Key page now reflect the newly installed License Key.
  • Page 974 CHAPTER 47    License Key Mediant 800 Gateway & E-SBC | User's Manual If want to cancel installation, reset the device without a save to flash. For more information, see Resetting the Device. Click Apply New License Key; the following appears: If the new License Key includes changes in licenses for features other than (or in addi- tion to) FEU, SBC, Coder Transcoding, and/or SBC Signaling, then Hitless Upgrade cannot be done.

  • Page 975: Installing License Key Through Cli

    CHAPTER 47    License Key Mediant 800 Gateway & E-SBC | User's Manual When installation completes, the following message box appears: Clock Close to close the message box; you are logged out of the Web interface and prompted to log in again. The features and capabilities displayed on the License Key page now reflect the newly installed License Key.

  • Page 976: Sbc Capacity Licenses From Fixed License Pool

    The device can receive SBC capacity (session) licenses from a centralized pool of SBC resources managed by AudioCodes One Voice Operations Center (OVOC) management tool. The license pool is purchased as one bulk license. The OVOC user can then manually allocate SBC licenses from the pool to devices in the network to meet capacity demands of each device whenever required.

  • Page 977: Sbc Capacity Licenses From Floating License

    CHAPTER 47    License Key Mediant 800 Gateway & E-SBC | User's Manual The device periodically checks with the OVOC license pool for SBC capacity licenses. OVOC identifies the device by serial number. If it has an SBC license for the device, it sends it to the device.
  • Page 978 Floating License. For more information on how this is calculated and for ordering the Floating License, refer to the AudioCodes Fixed Pool and Floating Licenses document. To view the Floating License report (SBC resource consumption) that the device sends OVOC, see...
  • Page 979 To configure the Floating License: Make sure that the following OVOC-related prerequisites have been fulfilled: ● The Floating License has been purchased from AudioCodes with the required SBC license capacities and installed on OVOC. ● The devices for which you want to use the Floating License have been configured on OVOC.
  • Page 980 CHAPTER 47    License Key Mediant 800 Gateway & E-SBC | User's Manual ● 'OVOC Product Key': Displays the Product Key of the OVOC tool that is providing the Floating License. The device connects with OVOC over SNMP. An SNMP manager is automatically added to the SNMP Trap Destinations table for this connection.

  • Page 981: Viewing Floating License Reports

    CHAPTER 47    License Key Mediant 800 Gateway & E-SBC | User's Manual Figure 47-5: Configuring Limits for Allocation Profile Viewing Floating License Reports You can view the SBC resource consumption (signaling sessions, media sessions, transcoding sessions, and far-end user registrations) reports of the Floating License that the device periodically sends to OVOC.

  • Page 982: Viewing The Device's Product 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 983: Configuration File

    CHAPTER 48    Configuration File Mediant 800 Gateway & E-SBC | User's Manual Configuration File This section describes how to save the device's configuration to a file and how to load a configuration file to the device. Saving and Loading an ini Configuration File You can save and load the device's configuration as an ini file.

  • Page 984: Saving And Loading Cli Script Files

    CHAPTER 48    Configuration File Mediant 800 Gateway & E-SBC | User's Manual Click Yes to continue (or No to cancel the file load). If you click Yes, the device loads the file and then resets with a save to flash for the settings to take effect.

  • Page 985: Saving And Loading A Configuration Package File

    CHAPTER 48    Configuration File Mediant 800 Gateway & E-SBC | User's Manual Click the Browse button, and then browse to and select the file on your computer. Click the Load CLI Startup Script button; the following message box appears, informing you that the device will reset after the file is loaded.
  • Page 986 CHAPTER 48    Configuration File Mediant 800 Gateway & E-SBC | User's Manual ● When loading a Configuration Package file, the device needs to reset for the settings to take effect. ● For the certificate files, only the root certificate file (.root) can be saved.

  • Page 987: Automatic Provisioning

    CHAPTER 49    Automatic Provisioning Mediant 800 Gateway & E-SBC | User's Manual Automatic Provisioning This chapter describes automatic provisioning of the device. Automatic Configuration Methods The device supports the following automatic provisioning methods: ■ DHCP (Option 66, Option 67, Option 160) ■...

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

    CHAPTER 49    Automatic Provisioning Mediant 800 Gateway & E-SBC | User's Manual subnet 10.31.0.0 netmask 255.255.0.0 { pool { allow members of "AudioCodes"; range 10.31.4.53 10.31.4.75; filename "SIP_F6.60A.217.003.cmp –fb;device.ini"; option routers 10.31.0.1; option subnet-mask 255.255.0.0; ● If the DHCP server denies the use of the device's current IP address and specifies a different IP address (according to RFC 1541), the device must change its networking parameters.

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

    CHAPTER 49    Automatic Provisioning Mediant 800 Gateway & E-SBC | User's Manual option routers 10.31.0.1; option subnet-mask 255.255.0.0; option domain-name-servers 10.1.0.11; option bootfile-name "INI=http://www.corp.com/master.ini"; option dhcp-parameter-request-list 1,3,6,51,67; ● The value of Option 67 must include the URL address, using the following syntax: "INI=<URL with ini file name>"...

  • Page 990: Provisioning The Device Using Dhcp Option 160

    CHAPTER 49    Automatic Provisioning Mediant 800 Gateway & E-SBC | User's Manual Reset the device with a save-to-flash for your settings to take effect. ● Access to the core network through TFTP is not NAT-safe. ● The TFTP data block size (packets) when downloading a file from a TFTP server for the Automatic Update mechanism can be configured using the AUPDTftpBlockSize parameter.

  • Page 991: Http-Based Provisioning

    CHAPTER 49    Automatic Provisioning Mediant 800 Gateway & E-SBC | User's Manual DhcpOption160Support = 1 Reset the device with a save-to-flash for your settings to take effect. HTTP-based Provisioning An HTTP or HTTPS server can be located in the network in which the device is deployed, storing configuration and software files for the device to download.

  • Page 992: Provisioning Through Ovoc

    Mediant 800 Gateway & E-SBC | User's Manual Provisioning through OVOC AudioCodes One Voice Operations Center (OVOC) server functions as a core-network provisioning server. The device's SNMP Manager should be configured with the IP address of the OVOC server, using one of the methods detailed in the previous sections. As soon as a registered device contacts OVOC through SNMP, OVOC handles all required configuration automatically, upgrading software as needed.

  • Page 993: File Location For Automatic Update

    CHAPTER 49    Automatic Provisioning Mediant 800 Gateway & E-SBC | User's Manual ● CLI Script File: Contains only CLI commands and configures all the device's functionalities (except commands such as show, debug or copy). The file updates the device's configuration only according to the configuration settings in the file. The device's existing configuration settings (not included in the file) are retained.

  • Page 994: Mac Address Placeholder In Configuration File Name

    CHAPTER 49    Automatic Provisioning Mediant 800 Gateway & E-SBC | User's Manual (automatic-update)# feature-key http://www.company.com/License_Key.txt (automatic-update)# auto-firmware http://www.company.com/SIP_F7.20A.008.cmp For configuration files, the file name in the URL can automatically contain the device's MAC address for enabling the device to download a file unique to the device. For more...
  • Page 995 CHAPTER 49    Automatic Provisioning Mediant 800 Gateway & E-SBC | User's Manual ➢ To use a file template for automatic provisioning: Define the file types to download by the file template, using the AupdFilesList parameter. Use the keywords listed in the table below to specify each file type. For example, to specify ini, License Key, and CPT files: ●...

  • Page 996: Triggers For Automatic Update

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

  • Page 997: Applying Downloaded Ini File After Graceful Timeout

    CHAPTER 49    Automatic Provisioning Mediant 800 Gateway & E-SBC | User's Manual From: sip:sipsak@<srchost> CSeq: 10 NOTIFY Call-ID: 1234@<srchost> Event: check-sync;reboot=false To enable the feature: Open the SIP Definitions General Settings page (Setup menu > Signaling & Media tab > SIP Definitions folder > SIP Definitions General Settings).

  • Page 998: Querying Provisioning Server For Updated Files

    CHAPTER 49    Automatic Provisioning Mediant 800 Gateway & E-SBC | User's Manual ■ CLI: # configure system (config-system)# automatic update (automatic-update)# auto-firmware https://JoeD:1234@10.1.1.1/mysw.cmp If you have not included the username and password in the parameters used for configuring the URL of the server with the name of the file that you want downloaded, the device uses the username and password that you configured for the ini file parameter [AUPDUserPassword] or CLI command configure system >...
  • Page 999 CHAPTER 49    Automatic Provisioning Mediant 800 Gateway & E-SBC | User's Manual If you configure the [AupdHttpUserAgent] parameter with the <CONF> variable tag, you must reset the device with a save-to-flash for your settings to take effect. If the provisioning server has relevant files available for the device, the following occurs, depending on file type and configuration: ●...

  • Page 1000: File Download Sequence

    CHAPTER 49    Automatic Provisioning Mediant 800 Gateway & E-SBC | User's Manual CLI: ◆ (config-system)# automatic-update (automatic-update)# call-progress-tones http://www.company.com/call_ progress.dat (automatic-update)# tls-root-cert https://company.com/root.pem Software (.cmp) File: ini: ◆ CmpFileUrl = 'https://www.company.com/device/7.20A.252.011.cmp' CLI: ◆ (config-system)# automatic-update (automatic-update)# firmware https://www.company.com/device/7.20A.252.011.cmp ● For one-time file download, the HTTP Get request sent by the device does not include the If-Modified-Since header.

This manual is also suitable for:

E-sbc

Table of Contents